HTTrack Website Copier
Free software offline browser - FORUM
Subject: Re: Google Chrome could not connect to debian:8080
Author: Sarit
Date: 04/20/2014 18:47
 
Here is what I had tried. Hope this help new comers.

root@ROCKMAN:/home/sarit# aptitude install webhttrack
The following NEW packages will be installed:
  libhttrack2{a} webhttrack webhttrack-common{a} 
0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 870 kB of archives. After unpacking 2,338 kB will be used.
Do you want to continue? [Y/n/?] y
Get: 1 <http://mirror.kku.ac.th/debian/> wheezy/main libhttrack2 amd64 3.46.1-1
[415 kB]
Get: 2 <http://mirror.kku.ac.th/debian/> wheezy/main webhttrack-common all
3.46.1-1 [396 kB]
Get: 3 <http://mirror.kku.ac.th/debian/> wheezy/main webhttrack amd64 3.46.1-1
[58.7 kB]
Fetched 870 kB in 1s (718 kB/s)      
Selecting previously unselected package libhttrack2.
(Reading database ... 133140 files and directories currently installed.)
Unpacking libhttrack2 (from .../libhttrack2_3.46.1-1_amd64.deb) ...
Selecting previously unselected package webhttrack-common.
Unpacking webhttrack-common (from .../webhttrack-common_3.46.1-1_all.deb) ...
Selecting previously unselected package webhttrack.
Unpacking webhttrack (from .../webhttrack_3.46.1-1_amd64.deb) ...
Processing triggers for man-db ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for menu ...
Setting up libhttrack2 (3.46.1-1) ...
Setting up webhttrack-common (3.46.1-1) ...
Setting up webhttrack (3.46.1-1) ...
Processing triggers for menu ...
                                         
root@ROCKMAN:/home/sarit# webhttrack 
/usr/bin/webhttrack(4656): launching /usr/bin/x-www-browser
/usr/bin/webhttrack(4656): spawning regular browser..

(x-www-browser:4699): GnomeUI-WARNING **: While connecting to session
manager:
None of the authentication protocols specified are supported.

(x-www-browser:4699): 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.

(x-www-browser:4699): 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.

(x-www-browser:4699): 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.

(x-www-browser:4699): 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.

** (x-www-browser:4699): WARNING **: The connection is closed


You will not be able to run it if you were an ordinary user.
You must login by root before proceed on web-copier.
 
Reply Create subthread


All articles

Subject Author Date
Google Chrome could not connect to debian:8080

05/25/2013 14:07
Re: Google Chrome could not connect to debian:8080

05/26/2013 09:44
Re: Google Chrome could not connect to debian:8080

04/20/2014 18:47




5

Created with FORUM 2.0.11