[Qa-jenkins-scm] Build failed in Jenkins: reproducible_builder_i386_3 #24521
jenkins at jenkins.debian.net
jenkins at jenkins.debian.net
Fri Dec 2 17:54:12 UTC 2016
https://jenkins.debian.net/job/reproducible_builder_i386_3/24521/------------------------------------------
[...truncated 11956 lines...]
WARNING: failed to install schema `/schemas/apps/guake/general/use_default_font', locale `C': Unable to store a value at key '/schemas/apps/guake/general/use_default_font', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/use_palette_font_and_background_color' to key `/apps/guake/general/use_palette_font_and_background_color'
WARNING: failed to install schema `/schemas/apps/guake/general/use_palette_font_and_background_color', locale `C': Unable to store a value at key '/schemas/apps/guake/general/use_palette_font_and_background_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/use_vte_titles' to key `/apps/guake/general/use_vte_titles'
WARNING: failed to install schema `/schemas/apps/guake/general/use_vte_titles', locale `C': Unable to store a value at key '/schemas/apps/guake/general/use_vte_titles', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/max_tab_name_length' to key `/apps/guake/general/max_tab_name_length'
WARNING: failed to install schema `/schemas/apps/guake/general/max_tab_name_length', locale `C': Unable to store a value at key '/schemas/apps/guake/general/max_tab_name_length', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/cursor_blink_mode' to key `/apps/guake/style/cursor_blink_mode'
WARNING: failed to install schema `/schemas/apps/guake/style/cursor_blink_mode', locale `C': Unable to store a value at key '/schemas/apps/guake/style/cursor_blink_mode', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/cursor_shape' to key `/apps/guake/style/cursor_shape'
WARNING: failed to install schema `/schemas/apps/guake/style/cursor_shape', locale `C': Unable to store a value at key '/schemas/apps/guake/style/cursor_shape', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/font/style' to key `/apps/guake/style/font/style'
WARNING: failed to install schema `/schemas/apps/guake/style/font/style', locale `C': Unable to store a value at key '/schemas/apps/guake/style/font/style', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/font/color' to key `/apps/guake/style/font/color'
WARNING: failed to install schema `/schemas/apps/guake/style/font/color', locale `C': Unable to store a value at key '/schemas/apps/guake/style/font/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/font/palette' to key `/apps/guake/style/font/palette'
WARNING: failed to install schema `/schemas/apps/guake/style/font/palette', locale `C': Unable to store a value at key '/schemas/apps/guake/style/font/palette', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/font/palette_name' to key `/apps/guake/style/font/palette_name'
WARNING: failed to install schema `/schemas/apps/guake/style/font/palette_name', locale `C': Unable to store a value at key '/schemas/apps/guake/style/font/palette_name', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/font/allow_bold' to key `/apps/guake/style/font/allow_bold'
WARNING: failed to install schema `/schemas/apps/guake/style/font/allow_bold', locale `C': Unable to store a value at key '/schemas/apps/guake/style/font/allow_bold', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/background/color' to key `/apps/guake/style/background/color'
WARNING: failed to install schema `/schemas/apps/guake/style/background/color', locale `C': Unable to store a value at key '/schemas/apps/guake/style/background/color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/background/image' to key `/apps/guake/style/background/image'
WARNING: failed to install schema `/schemas/apps/guake/style/background/image', locale `C': Unable to store a value at key '/schemas/apps/guake/style/background/image', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/style/background/transparency' to key `/apps/guake/style/background/transparency'
WARNING: failed to install schema `/schemas/apps/guake/style/background/transparency', locale `C': Unable to store a value at key '/schemas/apps/guake/style/background/transparency', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/compat_backspace' to key `/apps/guake/general/compat_backspace'
WARNING: failed to install schema `/schemas/apps/guake/general/compat_backspace', locale `C': Unable to store a value at key '/schemas/apps/guake/general/compat_backspace', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/compat_delete' to key `/apps/guake/general/compat_delete'
WARNING: failed to install schema `/schemas/apps/guake/general/compat_delete', locale `C': Unable to store a value at key '/schemas/apps/guake/general/compat_delete', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/global/show_hide' to key `/apps/guake/keybindings/global/show_hide'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/global/show_hide', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/global/show_hide', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/reset_terminal' to key `/apps/guake/keybindings/local/reset_terminal'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/reset_terminal', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/reset_terminal', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/quit' to key `/apps/guake/keybindings/local/quit'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/quit', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/quit', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/new_tab' to key `/apps/guake/keybindings/local/new_tab'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/new_tab', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/new_tab', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/close_tab' to key `/apps/guake/keybindings/local/close_tab'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/close_tab', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/close_tab', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/search_on_web' to key `/apps/guake/keybindings/local/search_on_web'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/search_on_web', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/search_on_web', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/move_tab_left' to key `/apps/guake/keybindings/local/move_tab_left'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/move_tab_left', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/move_tab_left', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/move_tab_right' to key `/apps/guake/keybindings/local/move_tab_right'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/move_tab_right', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/move_tab_right', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/previous_tab' to key `/apps/guake/keybindings/local/previous_tab'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/previous_tab', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/previous_tab', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/next_tab' to key `/apps/guake/keybindings/local/next_tab'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/next_tab', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/next_tab', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab1' to key `/apps/guake/keybindings/local/switch_tab1'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab1', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab1', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab2' to key `/apps/guake/keybindings/local/switch_tab2'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab2', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab2', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab3' to key `/apps/guake/keybindings/local/switch_tab3'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab3', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab3', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab4' to key `/apps/guake/keybindings/local/switch_tab4'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab4', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab4', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab5' to key `/apps/guake/keybindings/local/switch_tab5'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab5', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab5', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab6' to key `/apps/guake/keybindings/local/switch_tab6'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab6', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab6', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab7' to key `/apps/guake/keybindings/local/switch_tab7'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab7', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab7', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab8' to key `/apps/guake/keybindings/local/switch_tab8'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab8', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab8', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab9' to key `/apps/guake/keybindings/local/switch_tab9'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab9', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab9', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab10' to key `/apps/guake/keybindings/local/switch_tab10'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab10', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab10', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/switch_tab_last' to key `/apps/guake/keybindings/local/switch_tab_last'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/switch_tab_last', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/switch_tab_last', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/rename_current_tab' to key `/apps/guake/keybindings/local/rename_current_tab'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/rename_current_tab', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/rename_current_tab', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/zoom_in' to key `/apps/guake/keybindings/local/zoom_in'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/zoom_in', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/zoom_in', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/zoom_in_alt' to key `/apps/guake/keybindings/local/zoom_in_alt'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/zoom_in_alt', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/zoom_in_alt', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/zoom_out' to key `/apps/guake/keybindings/local/zoom_out'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/zoom_out', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/zoom_out', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/increase_height' to key `/apps/guake/keybindings/local/increase_height'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/increase_height', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/increase_height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/decrease_height' to key `/apps/guake/keybindings/local/decrease_height'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/decrease_height', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/decrease_height', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/increase_transparency' to key `/apps/guake/keybindings/local/increase_transparency'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/increase_transparency', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/increase_transparency', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/decrease_transparency' to key `/apps/guake/keybindings/local/decrease_transparency'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/decrease_transparency', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/decrease_transparency', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/toggle_transparency' to key `/apps/guake/keybindings/local/toggle_transparency'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/toggle_transparency', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/toggle_transparency', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/clipboard_copy' to key `/apps/guake/keybindings/local/clipboard_copy'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/clipboard_copy', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/clipboard_copy', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/clipboard_paste' to key `/apps/guake/keybindings/local/clipboard_paste'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/clipboard_paste', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/clipboard_paste', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/toggle_fullscreen' to key `/apps/guake/keybindings/local/toggle_fullscreen'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/toggle_fullscreen', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/toggle_fullscreen', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/keybindings/local/toggle_hide_on_lose_focus' to key `/apps/guake/keybindings/local/toggle_hide_on_lose_focus'
WARNING: failed to install schema `/schemas/apps/guake/keybindings/local/toggle_hide_on_lose_focus', locale `C': Unable to store a value at key '/schemas/apps/guake/keybindings/local/toggle_hide_on_lose_focus', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/word_chars' to key `/apps/guake/general/word_chars'
WARNING: failed to install schema `/schemas/apps/guake/general/word_chars', locale `C': Unable to store a value at key '/schemas/apps/guake/general/word_chars', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/show_resizer' to key `/apps/guake/general/show_resizer'
WARNING: failed to install schema `/schemas/apps/guake/general/show_resizer', locale `C': Unable to store a value at key '/schemas/apps/guake/general/show_resizer', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/toolbar_visible_in_fullscreen' to key `/apps/guake/general/toolbar_visible_in_fullscreen'
WARNING: failed to install schema `/schemas/apps/guake/general/toolbar_visible_in_fullscreen', locale `C': Unable to store a value at key '/schemas/apps/guake/general/toolbar_visible_in_fullscreen', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/focus_if_open' to key `/apps/guake/general/focus_if_open'
WARNING: failed to install schema `/schemas/apps/guake/general/focus_if_open', locale `C': Unable to store a value at key '/schemas/apps/guake/general/focus_if_open', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
Attached schema `/schemas/apps/guake/general/custom_command_file' to key `/apps/guake/general/custom_command_file'
WARNING: failed to install schema `/schemas/apps/guake/general/custom_command_file', locale `C': Unable to store a value at key '/schemas/apps/guake/general/custom_command_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
/bin/mkdir -p '/build/guake-0.8.7/debian/guake/usr/share/applications'
/usr/bin/install -c -m 644 guake.desktop guake-prefs.desktop '/build/guake-0.8.7/debian/guake/usr/share/applications'
/bin/mkdir -p '/build/guake-0.8.7/debian/guake/usr/share/man/man1'
/usr/bin/install -c -m 644 guake.1 '/build/guake-0.8.7/debian/guake/usr/share/man/man1'
/bin/mkdir -p '/build/guake-0.8.7/debian/guake/etc/gconf/schemas'
/usr/bin/install -c -m 644 guake.schemas '/build/guake-0.8.7/debian/guake/etc/gconf/schemas'
/bin/mkdir -p '/build/guake-0.8.7/debian/guake/usr/share/dbus-1/services'
/usr/bin/install -c -m 644 org.guake.Guake.service '/build/guake-0.8.7/debian/guake/usr/share/dbus-1/services'
/bin/mkdir -p '/build/guake-0.8.7/debian/guake/usr/share/guake'
/usr/bin/install -c -m 644 about.glade guake.glade prefs.glade '/build/guake-0.8.7/debian/guake/usr/share/guake'
make[4]: Leaving directory '/build/guake-0.8.7/data'
make[3]: Leaving directory '/build/guake-0.8.7/data'
make[2]: Leaving directory '/build/guake-0.8.7/data'
Making install in po
make[2]: Entering directory '/build/guake-0.8.7/po'
linguas="ca cs de el es fa fr gl hr hu id it ja ko nb nl pa pl pt_BR ru sv tr uk zh_CN "; \
for lang in $linguas; do \
dir=/build/guake-0.8.7/debian/guake/usr/share/locale/$lang/LC_MESSAGES; \
/bin/bash /build/guake-0.8.7/install-sh -d $dir; \
if test -r $lang.gmo; then \
/usr/bin/install -c -m 644 $lang.gmo $dir/guake.mo; \
echo "installing $lang.gmo as $dir/guake.mo"; \
else \
/usr/bin/install -c -m 644 ./$lang.gmo $dir/guake.mo; \
echo "installing ./$lang.gmo as" \
"$dir/guake.mo"; \
fi; \
if test -r $lang.gmo.m; then \
/usr/bin/install -c -m 644 $lang.gmo.m $dir/guake.mo.m; \
echo "installing $lang.gmo.m as $dir/guake.mo.m"; \
else \
if test -r ./$lang.gmo.m ; then \
/usr/bin/install -c -m 644 ./$lang.gmo.m \
$dir/guake.mo.m; \
echo "installing ./$lang.gmo.m as" \
"$dir/guake.mo.m"; \
else \
true; \
fi; \
fi; \
done
installing ca.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/ca/LC_MESSAGES/guake.mo
installing cs.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/cs/LC_MESSAGES/guake.mo
installing de.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/de/LC_MESSAGES/guake.mo
installing el.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/el/LC_MESSAGES/guake.mo
installing es.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/es/LC_MESSAGES/guake.mo
installing fa.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/fa/LC_MESSAGES/guake.mo
installing fr.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/fr/LC_MESSAGES/guake.mo
installing gl.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/gl/LC_MESSAGES/guake.mo
installing hr.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/hr/LC_MESSAGES/guake.mo
installing hu.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/hu/LC_MESSAGES/guake.mo
installing id.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/id/LC_MESSAGES/guake.mo
installing it.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/it/LC_MESSAGES/guake.mo
installing ja.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/ja/LC_MESSAGES/guake.mo
installing ko.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/ko/LC_MESSAGES/guake.mo
installing nb.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/nb/LC_MESSAGES/guake.mo
installing nl.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/nl/LC_MESSAGES/guake.mo
installing pa.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/pa/LC_MESSAGES/guake.mo
installing pl.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/pl/LC_MESSAGES/guake.mo
installing pt_BR.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/pt_BR/LC_MESSAGES/guake.mo
installing ru.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/ru/LC_MESSAGES/guake.mo
installing sv.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/sv/LC_MESSAGES/guake.mo
installing tr.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/tr/LC_MESSAGES/guake.mo
installing uk.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/uk/LC_MESSAGES/guake.mo
installing zh_CN.gmo as /build/guake-0.8.7/debian/guake/usr/share/locale/zh_CN/LC_MESSAGES/guake.mo
make[2]: Leaving directory '/build/guake-0.8.7/po'
make[2]: Entering directory '/build/guake-0.8.7'
make[3]: Entering directory '/build/guake-0.8.7'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/build/guake-0.8.7'
make[2]: Leaving directory '/build/guake-0.8.7'
make[1]: Leaving directory '/build/guake-0.8.7'
debian/rules override_dh_install
make[1]: Entering directory '/build/guake-0.8.7'
find /build/guake-0.8.7/ -name "*.la" -exec \
sed -i -e "s,^dependency_libs=.*,dependency_libs=''," {} +
dh_install
make[1]: Leaving directory '/build/guake-0.8.7'
dh_installdocs
dh_installchangelogs
dh_installman
dh_python2
dh_lintian
dh_gconf
dh_icons
dh_perl
dh_link
dh_strip_nondeterminism
dh_compress
dh_fixperms
dh_strip
dh_makeshlibs
dh_shlibdeps
dh_installdeb
dh_gencontrol
dpkg-gencontrol: warning: Depends field of package guake: unknown substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
dpkg-gencontrol: warning: package guake: unused substitution variable ${python:Versions}
dh_md5sums
dh_builddeb
dpkg-deb: building package 'guake' in '../guake_0.8.7-1_i386.deb'.
dpkg-genbuildinfo --build=binary
dpkg-genbuildinfo: warning: File::FcntlLock not available; using flock which is not NFS-safe
dpkg-genchanges --build=binary >../guake_0.8.7-1_i386.changes
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build guake-0.8.7
dpkg-buildpackage: info: binary-only upload (no source included)
I: copying local configuration
I: unmounting /dev/shm filesystem
I: unmounting dev/pts filesystem
I: unmounting run/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: cleaning the build env
I: removing directory /srv/workspace/pbuilder/29956 and its subdirectories
I: Current time: Fri Dec 2 05:52:43 -12 2016
I: pbuilder-time-stamp: 1480701163
245c245
< libperl5.24 (= 5.24.1~rc4-1),
---
> libperl5.24 (= 5.24.1~rc3-3),
355,357c355,357
< perl (= 5.24.1~rc4-1),
< perl-base (= 5.24.1~rc4-1),
< perl-modules-5.24 (= 5.24.1~rc4-1),
---
> perl (= 5.24.1~rc3-3),
> perl-base (= 5.24.1~rc3-3),
> perl-modules-5.24 (= 5.24.1~rc3-3),
371c371
< python-pyorbit (= 2.24.0-7.2),
---
> python-pyorbit (= 2.24.0-7.1+b1),
Error: database is locked
/srv/reproducible-results/rbuild-debian-lEBbiwi7/tmp.I0SZkI9wvC: 89.1% -- replaced with /srv/reproducible-results/rbuild-debian-lEBbiwi7/tmp.I0SZkI9wvC.gz
INFO: Starting at 2016-12-02 17:53:44.672014
INFO: Finished at 2016-12-02 17:54:12.057905, took: 0:00:27.385902
Fri 2 Dec 17:54:12 UTC 2016 - /srv/jenkins/bin/reproducible_build.sh stopped running as /tmp/jenkins-script-poslJTvV, which will now be removed.
Build step 'Execute shell' marked build as failure
More information about the Qa-jenkins-scm
mailing list