Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

Tixati 2.43 - 1.99 deb installation error

by Guest on 2016/07/10 07:16:25 AM    
Any ideas why 2.43 or 1.99 Tixati breaks root install on Debian 8?

# dpkg -i tixati_1.99-1_amd64.deb
Selecting previously unselected package tixati.
(Reading database ... 111697 files and directories currently installed.)
Preparing to unpack tixati_1.99-1_amd64.deb ...
Unpacking tixati (1.99-1) ...
Setting up tixati (1.99-1) ...(gconftool-2:8044): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error setting value: No D-BUS daemon running

(gconftool-2:8045): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error setting value: No D-BUS daemon running


(gconftool-2:8046): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error setting value: No D-BUS daemon running


(gconftool-2:8047): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error setting value: No D-BUS daemon running


(gconftool-2:8048): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error setting value: No D-BUS daemon running


(gconftool-2:8049): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error setting value: No D-BUS daemon running

dpkg: error processing package tixati (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for mime-support (3.58) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...
Errors were encountered while processing:
tixati
by Guest on 2016/09/25 07:24:51 AM    
same problem
root@K55n:/home/dino/Descargas# dpkg -i tixati_2.43-1_amd64.deb
(Leyendo la base de datos ... 131721 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar tixati_2.43-1_amd64.deb ...
Desempaquetando tixati (2.43-1) sobre (2.43-1) ...
Configurando tixati (2.43-1) ...

(gconftool-2:2595): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2596): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2597): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2598): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2599): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2600): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución

dpkg: error al procesar el paquete tixati (--install):
el subproceso instalado el script post-installation devolvió el código de salida de error 1
Procesando disparadores para desktop-file-utils (0.22-1) ...
Procesando disparadores para mime-support (3.58) ...
Procesando disparadores para hicolor-icon-theme (0.13-1) ...
Se encontraron errores al procesar:
tixati
root@K55n:/home/dino/Descargas# apt-get install -f
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias      
Leyendo la información de estado... Hecho
0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados.
1 no instalados del todo o eliminados.
Se utilizarán 0 B de espacio de disco adicional después de esta operación.
Configurando tixati (2.43-1) ...

(gconftool-2:2627): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2628): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2629): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2630): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2631): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución


(gconftool-2:2632): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Error al establecer el valor: El demonio de D-Bus no está en ejecución

dpkg: error al procesar el paquete tixati (--configure):
el subproceso instalado el script post-installation devolvió el código de salida de error 1
Se encontraron errores al procesar:
tixati
E: Sub-process /usr/bin/dpkg returned an error code (1)
by Guest on 2016/10/11 01:05:10 PM    
Same problem. gconftool-2 failing

Two things:

1) I'm not running gnome

2) Turns out that gconftool-2 doesn't work as root, which is where the install happens. It does run as 'user'.

Don't have a solution though.

Update:

The issue is in postinst where these commands are run.

gconftool-2 --set --type=string /desktop/gnome/url-handlers/magnet/command 'tixati "%s"'
gconftool-2 --set --type=bool /desktop/gnome/url-handlers/magnet/enabled true
gconftool-2 --set --type=bool /desktop/gnome/url-handlers/magnet/need-terminal false
gconftool-2 --set --type=string /desktop/gnome/url-handlers/dsc/command 'tixati "%s"'
gconftool-2 --set --type=bool /desktop/gnome/url-handlers/dsc/enabled true
gconftool-2 --set --type=bool /desktop/gnome/url-handlers/dsc/need-terminal false

These are only relevant on a Gnome system. They cause install to fail partially on others. I run XFCE.

apt-get install says the .deb is not installed due to this failure. The binary is however in place.

It also causes the gconftool-2 errors to show up every time apt-get install is run which is painful.

Conditional running of these commands would resolve the problem.
by Guest on 2016/11/23 10:25:33 AM    
Same problem with KDE
by Guest on 2017/06/13 07:49:19 PM    
This problem still affects Tixati 2.53-1 and KDE Neon (Ubuntu 16.04 + the KDE repository).
by Guest on 2017/10/23 02:51:42 AM    
Just run:

apt-get install gconf2

and after that run:

apt-get -f install

(run all this commands with priviledges sudo or root)

This fixed this issue with my laptop. By the way... I use the last Ubuntu 17.10 with gnome.
by bodqhrohro on 2018/03/01 01:17:46 PM    
I have gconf2 installed but however have this issue if running APT from root instead of sudo.




This web site is powered by Super Simple Server