Bug 258769 – knetworkconf gives "Could not parse the XML file ()" when trying to open

• Status: RESOLVED DUPLICATE of bug 259840
• Product: Gentoo Linux

[Description M 2009-02-12 19:09:06 UTC]

KDE version 4.2.0, when I try to open knetworkconf via system settings > network settings > network settings (again) I get a popup saying "Could not parse the XML file ()." twice (so two popups in total). When I click them away all the menus and buttons are greyed out. I got the same result on an amd64 system with kdebase-meta and some other kde packages and on an x86 machine with kde-meta installed.

Reproducible: Always

Steps to Reproduce:
1. go to system settings
2. click on network settings
3. click on network settings again

[Comment 1 M 2009-02-12 19:14:32 UTC]

kcmshell output:

isilia@Gentoo ~ $ kcmshell4 kcm_knetworkconfmodule.desktop
--get XML:

XML -d list_ifaces:
isilia@Gentoo ~ $ kcmshell4 kcm_knetworkconfmodule
--get XML:

XML -d list_ifaces:

No change in resuls.

[Comment 2 Hubert FONGARNAND 2009-03-11 08:48:52 UTC]

Apparently fixed with 4.2.1 package... but still no interfaces in ksysguard or network plasmoids...

[Comment 3 Robert Piasek (RETIRED) 2009-03-11 09:05:47 UTC]

kcmshell4 kcm_knetworkconfmodule
--get XML:         
                                         
<?xml version='1.0' encoding='UTF-8' standalone='yes'?>     
<!DOCTYPE network []>                                       

<network>

  <dialinstalled>1</dialinstalled>
  <domain>edigitalresearch.com</domain>
  <smbdesc>Rob&apos;s Samba Server %v</smbdesc>
  <smbinstalled>1</smbinstalled>               
  <smbuse>0</smbuse>                           
  <workgroup>WORKGROUP</workgroup>             

  <nameserver>10.0.0.111</nameserver>

  <searchdomain>edigitalresearch.com</searchdomain>

  <statichost>
    <ip>10.0.1.12</ip>
    <alias>rob.edigitalresearch.com</alias>
    <alias>rob</alias>                     
  </statichost>                            
  <statichost>                             
    <ip>127.0.0.1</ip>                     
    <alias>rob.edigitalresearch.com</alias>
    <alias>localhost.localdomain</alias>   
    <alias>localhost</alias>               
    <alias>localhost</alias>               
    <alias></alias>                        
  </statichost>                            
  <statichost>                             
    <ip>::1</ip>                           
    <alias>localhost</alias>               
  </statichost>                            
  <statichost>                             
    <ip>10.0.1.1</ip>                      
    <alias>core.edigitalresearch.com</alias>
    <alias>core</alias>                     
  </statichost>

  <interface type='modem'>

    <dev>ppp0</dev>
    <enabled>0</enabled>
  </interface>

  <interface type='loopback'>

    <dev>lo</dev>
    <enabled>1</enabled>
  </interface>

  <interface type='ethernet'>

    <dev>eth0</dev>
    <enabled>1</enabled>
    <hwaddr>00:18:f3:03:45:b6</hwaddr>
  </interface>

  <profiledb>
  </profiledb>

</network>

<!-- GST: end of request -->

XML -d list_ifaces: <?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<!DOCTYPE network-ifaces []>

<network-ifaces>

  <interface>
    <addr>127.0.0.1</addr>
    <dev>lo</dev>
    <enabled>1</enabled>
    <mask>255.0.0.0</mask>
    <type>loopback</type>
  </interface>

  <interface>
    <addr>10.0.1.12</addr>
    <bcast>10.0.1.255</bcast>
    <dev>eth0</dev>
    <enabled>1</enabled>
    <hwaddr>00:18:f3:03:45:b6</hwaddr>
    <mask>255.255.255.0</mask>
    <type>ethernet</type>
  </interface>

</network-ifaces>

<!-- GST: end of request -->



*** This bug has been marked as a duplicate of bug 259840 ***