Siduction Forum

Siduction Forum => Software - Support => Topic started by: cas on 2015/07/16, 01:32:10

Title: SPSS: GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Post by: cas on 2015/07/16, 01:32:10
Hallo,
ich ärgere mich gerade  mit SPSS herum.
Wenn ich den licencewizard aufrufe kommt folgendes:
root@dino:/opt/spss/bin# ./licensewizard

(process:30808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf-Fehler: D-BUS-Hintergrunddienst läuft nicht


(process:30808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf-Fehler: D-BUS-Hintergrunddienst läuft nicht


(process:30808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf-Fehler: D-BUS-Hintergrunddienst läuft nicht


(process:30808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf-Fehler: D-BUS-Hintergrunddienst läuft nicht

Enter Keys ..Strg


Was heisst das denn eigentlich?
Da ich Schwierigkeiten habe, die SPSS Lizenz zu aktivieren, kann das was damit zu tun haben?

Grüße, Christian
Title: Re: SPSS: GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Post by: piper on 2015/07/16, 03:08:23
What happens when you do

service dbus start
Title: Re: SPSS: GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Post by: cas on 2015/07/16, 10:47:15
Quote from: piper on 2015/07/16, 03:08:23
What happens when you do

service dbus start
the same message willl reappear
Title: Re: SPSS: GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Post by: hendrikL on 2015/07/16, 11:31:11
And whats happens when you do
export $(dbus-launch)
as root?
Title: Re: SPSS: GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Post by: cas on 2015/07/16, 11:58:15
maybe my answer was misleading. When I do these commands, nothing happens.

root# service dbus start
root# export $(dbus-launch)
root#

I think this means, it is already runninig
root:/etc/init.d# ./dbus status
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled)
   Active: active (running) since Do 2015-07-16 09:42:14 CEST; 2h 13min ago
     Docs: man:dbus-daemon(1)
Main PID: 1123 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─1123 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Jul 16 11:45:45 dino dbus[1123]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Jul 16 11:46:17 dino dbus[1123]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Jul 16 11:46:17 dino org.kde.powerdevil.backlighthelper[25139]: QDBusConnection: system D-Bus connection created before QCoreApplic...have.
Jul 16 11:46:17 dino dbus[1123]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Jul 16 11:51:22 dino dbus[1123]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Jul 16 11:51:22 dino org.kde.powerdevil.backlighthelper[3836]: QDBusConnection: system D-Bus connection created before QCoreApplica...have.
Jul 16 11:51:22 dino dbus[1123]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Jul 16 11:51:59 dino dbus[1123]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Jul 16 11:51:59 dino org.kde.powerdevil.backlighthelper[5189]: QDBusConnection: system D-Bus connection created before QCoreApplica...have.
Jul 16 11:51:59 dino dbus[1123]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Hint: Some lines were ellipsized, use -l to show in full.


nevertheless, when I run the SPSS licencewizard, there is still the message, that it is not running?!
Title: Re: SPSS: GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Post by: hendrikL on 2015/07/16, 12:18:10
Muss denn das Programm als # root laufen, bzw. muss root die Lizenz bestätigen?
export $(dbus-launch) ist nur die möglichkeit ein root prozesse mit dbus zu verbinden, wenn root via su aus einer $user Sitzung heraus aufgerufen wird.
Versuch doch mal dbus-launch ./wizzard.....
Title: Re: SPSS: GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Post by: cas on 2015/07/16, 12:59:06
Quote from: hendrikL on 2015/07/16, 12:18:10
Muss denn das Programm als # root laufen, bzw. muss root die Lizenz bestätigen?
export $(dbus-launch) ist nur die möglichkeit ein root prozesse mit dbus zu verbinden, wenn root via su aus einer $user Sitzung heraus aufgerufen wird.
Versuch doch mal dbus-launch ./wizzard.....
ja, dieser wizard bricht als user ab. auch sudo funzt nicht.

cas@dino:/opt/spss/bin$ sudo dbus-launch ./licensewizard
[sudo] Passwort für cas:
Tut mir leid, der Benutzer cas darf '/usr/bin/dbus-launch ./licensewizard' als root auf dino nicht ausführen.


Was ich mich frage, bedeutet diese Fehlermeldung etwas relevantes? Eine eigentlich gültige LIzenz wird nicht akzeptiert.