Re: Problem in Starting KDE
OK, that one little thing has made it about 80% perfect now. Just three details: 1) It takes an awfully long time to start up. I guess this is related to the next point: 2) The output from 'startx' is still mostly the same as before: xauth: creating new authority file /root/.serverauth.566 ### Standard X startup message ### DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... DCOP Cleaning up dead connections. Reusing existing ksycoca ### Still a pagefull of kbuildsyscoa mime-type warnings ### 3) In the course of using Konqueror, I see kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kio (KLauncher): ERROR: SlavePool: No communication with slave. kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data get written. --- Subhro [EMAIL PROTECTED] wrote: Add this so that the hosts looks like this: On 7/18/06, Sean M. [EMAIL PROTECTED] wrote: Here is /etc/hosts. It's not very spectacular. # # This file should contain the addresses and aliases for local hosts that # share this file. Replace 'my.domain' below with the domainname of your # machine. # # In the presence of the domain name service or NIS, this file may # not be consulted at all; see /etc/nsswitch.conf for the resolution order. # # ::1 localhost localhost.my.domain 127.0.0.1 localhost localhost.my.domain 127.0.0.1 compy compy.my.domain # # Imaginary network. #10.0.0.2 myname.my.domain myname #10.0.0.3 myfriend.my.domain myfriend # # According to RFC 1918, you can use the following IP networks for # private nets which will never be connected to the Internet: # # 10.0.0.0- 10.255.255.255 # 172.16.0.0 - 172.31.255.255 # 192.168.0.0 - 192.168.255.255 # # In case you want to be able to connect to the Internet, you need # real official assigned numbers. Do not try to invent your own network # numbers but instead get one from your network provider (if any) or # from your regional registry (ARIN, APNIC, LACNIC, RIPE NCC, or AfriNIC.) # o.com Your issue is, X does not know how to connect to compy:0. Creating an entry in the hosts tells it the IP to connect. :-) Subhro -- Subhro Kar Security Engineer iViZ Techno Solutions Pvt. Ltd. Dhanshree Bldg, 1st Floor Plot XI-16, Sector V Salt Lake City 700091 India __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem in Starting KDE
Let me have a look at /etc/make.conf and /etc/resolv.conf Subhro On 7/18/06, Sean M. [EMAIL PROTECTED] wrote: OK, that one little thing has made it about 80% perfect now. Just three details: 1) It takes an awfully long time to start up. I guess this is related to the next point: 2) The output from 'startx' is still mostly the same as before: xauth: creating new authority file /root/.serverauth.566 ### Standard X startup message ### DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... DCOP Cleaning up dead connections. Reusing existing ksycoca ### Still a pagefull of kbuildsyscoa mime-type warnings ### 3) In the course of using Konqueror, I see kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kio (KLauncher): ERROR: SlavePool: No communication with slave. kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data get written. --- Subhro [EMAIL PROTECTED] wrote: Add this so that the hosts looks like this: On 7/18/06, Sean M. [EMAIL PROTECTED] wrote: Here is /etc/hosts. It's not very spectacular. # # This file should contain the addresses and aliases for local hosts that # share this file. Replace 'my.domain' below with the domainname of your # machine. # # In the presence of the domain name service or NIS, this file may # not be consulted at all; see /etc/nsswitch.conf for the resolution order. # # ::1 localhost localhost.my.domain 127.0.0.1 localhost localhost.my.domain 127.0.0.1 compy compy.my.domain # # Imaginary network. #10.0.0.2 myname.my.domain myname #10.0.0.3 myfriend.my.domain myfriend # # According to RFC 1918, you can use the following IP networks for # private nets which will never be connected to the Internet: # # 10.0.0.0- 10.255.255.255 # 172.16.0.0 - 172.31.255.255 # 192.168.0.0 - 192.168.255.255 # # In case you want to be able to connect to the Internet, you need # real official assigned numbers. Do not try to invent your own network # numbers but instead get one from your network provider (if any) or # from your regional registry (ARIN, APNIC, LACNIC, RIPE NCC, or AfriNIC.) # o.com Your issue is, X does not know how to connect to compy:0. Creating an entry in the hosts tells it the IP to connect. :-) Subhro -- Subhro Kar Security Engineer iViZ Techno Solutions Pvt. Ltd. Dhanshree Bldg, 1st Floor Plot XI-16, Sector V Salt Lake City 700091 India -- Subhro Kar Security Engineer iViZ Techno Solutions Pvt. Ltd. Dhanshree Bldg, 1st Floor Plot XI-16, Sector V Salt Lake City 700091 India ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem in Starting KDE
/etc/make.conf: # added by use.perl 2006-07-14 05:33:46 PERL_VER=5.8.8 PERL_VERSION=5.8.8 /etc/resolv.conf: search vc.shawcable.net nameserver 64.59.144.92 nameserver 64.59.144.93 --- Subhro [EMAIL PROTECTED] wrote: Let me have a look at /etc/make.conf and /etc/resolv.conf Subhro On 7/18/06, Sean M. [EMAIL PROTECTED] wrote: OK, that one little thing has made it about 80% perfect now. Just three details: 1) It takes an awfully long time to start up. I guess this is related to the next point: 2) The output from 'startx' is still mostly the same as before: xauth: creating new authority file /root/.serverauth.566 ### Standard X startup message ### DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... DCOP Cleaning up dead connections. Reusing existing ksycoca ### Still a pagefull of kbuildsyscoa mime-type warnings ### 3) In the course of using Konqueror, I see kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kio (KLauncher): ERROR: SlavePool: No communication with slave. kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OPENSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: Undefined symbol OpenSSL_add_all_algorithms_conf kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data kio (KIOConnection): ERROR: Could not write data get written. --- Subhro [EMAIL PROTECTED] wrote: Add this so that the hosts looks like this: On 7/18/06, Sean M. [EMAIL PROTECTED] wrote: Here is /etc/hosts. It's not very spectacular. # # This file should contain the addresses and aliases for local hosts that # share this file. Replace 'my.domain' below with the domainname of your # machine. # # In the presence of the domain name service or NIS, this file may # not be consulted at all; see /etc/nsswitch.conf for the resolution order. # # ::1 localhost localhost.my.domain 127.0.0.1 localhost localhost.my.domain 127.0.0.1 compy compy.my.domain # # Imaginary network. #10.0.0.2 myname.my.domain myname #10.0.0.3 myfriend.my.domain myfriend # # According to RFC 1918, you can use the following IP networks for # private nets which will never be connected to the Internet: # # 10.0.0.0- 10.255.255.255 # 172.16.0.0 - 172.31.255.255 # 192.168.0.0 - 192.168.255.255 # # In case you want to be able to connect to the Internet, you need # real official assigned numbers. Do not try to invent your own network # numbers but instead get one from your network provider (if any) or # from your regional registry (ARIN, APNIC, LACNIC, RIPE NCC, or AfriNIC.) # o.com Your issue is, X does not know how to connect to compy:0. Creating an entry in the hosts tells it the IP to connect. :-) Subhro -- Subhro Kar Security Engineer iViZ Techno Solutions Pvt. Ltd. Dhanshree Bldg, 1st Floor Plot XI-16, Sector V Salt Lake City 700091 India -- Subhro Kar Security Engineer iViZ Techno Solutions Pvt. Ltd. Dhanshree Bldg, 1st Floor Plot XI-16, Sector V Salt Lake City 700091 India ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To
Re: Problem in Starting KDE
Here is /etc/hosts. It's not very spectacular. # # This file should contain the addresses and aliases for local hosts that # share this file. Replace 'my.domain' below with the domainname of your # machine. # # In the presence of the domain name service or NIS, this file may # not be consulted at all; see /etc/nsswitch.conf for the resolution order. # # ::1 localhost localhost.my.domain 127.0.0.1 localhost localhost.my.domain # # Imaginary network. #10.0.0.2 myname.my.domain myname #10.0.0.3 myfriend.my.domain myfriend # # According to RFC 1918, you can use the following IP networks for # private nets which will never be connected to the Internet: # # 10.0.0.0- 10.255.255.255 # 172.16.0.0 - 172.31.255.255 # 192.168.0.0 - 192.168.255.255 # # In case you want to be able to connect to the Internet, you need # real official assigned numbers. Do not try to invent your own network # numbers but instead get one from your network provider (if any) or # from your regional registry (ARIN, APNIC, LACNIC, RIPE NCC, or AfriNIC.) # o.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
