knetworkmanager - manual configuration doesn't load (kde4)

Bug #211717 reported by Ash on 2008-04-04
12
Affects Status Importance Assigned to Milestone
kdeadmin (Ubuntu)
Undecided
Unassigned
knetworkmanager (Ubuntu)
Undecided
Unassigned
kubuntu-kde4-meta (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: knetworkmanager

Using: Kubuntu 8.04 Beta (KDE 4 Remix)

Right click on knetworkmanager systray icon and choose Manual Configuration...
This prompts for a password and the dialog text show it is going to run "kcmshell kcm_knetworkconfmodule"
After entering the password nothing happens.

Running "kcmshell kcm_knetworkconfmodule" on the command line gives the error:
kcmshell (kdelibs): WARNING: Could not find module 'kcm_knetworkconfmodule'.

Running "kcmshell4 kcm_knetworkconfmodule" does load a gui, but with a error dialog box of:
Could not parse the XML file.

System Settings doesn't have any way to configure the network settings either and if I made the changes to the files manually they would get overwritten by knetworkmanager at some point.

Yuriy Kozlov (yuriy-kozlov) wrote :

Thank you for filing this bug. You can work around this by installing knetworkconf.

Either kubuntu-kde4-desktop should depend on knetworkconf or knetworkmanager should be patched to launch kcmshell4 under kde4.
Or perhaps knetworkmanager even should depend on knetworkconf.

I can confirm the problem with kcmshell4 kcm_knetworkconfmodule as well, but you should file a separate bug about that.

Changed in knetworkmanager:
status: New → Confirmed
Changed in kubuntu-kde4-meta:
status: New → Confirmed
Luka Renko (lure) wrote :

While merging 0.2.2 from debian, will also fix that. Since knetworkmanager calls knetworkconf for Manual Configuration, it is only appropriate to depend on it. This should fix KDE4 session.

Changed in knetworkmanager:
assignee: nobody → lure
status: Confirmed → In Progress
Launchpad Janitor (janitor) wrote :
Download full text (3.2 KiB)

This bug was fixed in the package knetworkmanager - 1:0.2.2-1ubuntu1

---------------
knetworkmanager (1:0.2.2-1ubuntu1) hardy; urgency=low

  * Merge from Debian unstable. Remaining Ubuntu changes:
    - build with -with-pptp --with-dialup options
    - provide dummy knetworkmanager package (needed for dapper upgrade)
    - debian/patches/04-dbus_access.patch dropped: not needed in Ubuntu
    - debian/patches/kubuntu_01_kdepot.patch
    - debian/patches/kubuntu_02_nice_desktop_file.patch
    - debian/patches/kubuntu_03_static_config.patch
    - debian/patches/kubuntu_05_networkstatus.patch
    - debian/patches/kubuntu_07_indicate_manual_config.patch
    - debian/patches/kubuntu_08_ppp_support.patch
    - debian/patches/kubuntu_09_pptp-service-name.patch
  * Dropped patches:
    - debian/patches/kubuntu_10_only_show_in_kde.patch: included upstream
  * Rework debian/patches/kubuntu_08_ppp_support.patch:
    - autodetect Ubuntu properly and use /usr/bin/kppp for ppp support
  * Depend on knetworkconf for Manual Configuration (LP: #211717)

knetworkmanager (1:0.2.2-1) unstable; urgency=low

  * New upstream release.
    - Improved tray icon animation using mng files. Closes: #394815
    - Improved LEAP security. Closes: #470709
  * Removed patches
    - debian/patches/01-fix_french_translation.patch (merged upstream)
    - debian/patches/02-linux_types.patch (obsolete)
    - debian/patches/03-awk_path.patch (fixed upstream)
    - debian/patches/05-desktop_file_fixes.patch (merged upstream)
  * debian/knetworkmanager.linda
    - Remove the linda override file, linda is dead.
  * debian/{knetworkmanager.lintian -> network-manager-kde.lintian-overrides}
    - Rename the lintian override file so it is automatically installed by
      dh_lintian.
  * debian/rules
    - Drop the no longer required install rules for the override files.
    - Drop the install rule for the autostart file. It's provided by upstream
      now.
  * debian/copyright
    - Update the authors list.
  * debian/control
    - Bump Build-Depends on libnl-dev (>= 1.1).
    - Drop Build-Depends on kapptemplate. The upstream tarball ships a proper
      admin/ directory again.
  * debian/watch
    - New download location at ftp.kde.org.

knetworkmanager (1:0.2-3) unstable; urgency=low

  * debian/control
    - Use the new "Homepage:" field to specify the upstream URL.
    - The Vcs-* fields are now officially supported, so remove the XS- prefix.
    - Bump Standards-Version to 3.7.3. No further changes required.
    - Fix a few capitalization errors in the package description.

knetworkmanager (1:0.2-2) unstable; urgency=low

  * Rebuild against network-manager 0.6.5 to enable phase2 and leap
    authentication support.
  * debian/rules
    - Remove debian/stamp-bootstrap on clean. This fixes a FTBFS if package is
      built twice in a row. Closes: #442621
  * debian/control
    - Add Build-Conflicts: autoconf2.13. Closes: #441046
  * debian/menu
    - Set section to Applications/Network/Monitoring which seems to be the
      most appropriate amongst the available sections.
  * debian/patches/05-desktop_file_fixes.patch
    - Fix the *.desktop files to be compliant to the fd.o menu ...

Read more...

Changed in knetworkmanager:
status: In Progress → Fix Released
zephirum (zephirum) wrote :

I have similar problem as well. The IP stays at 0.0.0.0 and the manual configuration button doesn't work....
I'm not so sure about the bug being fixed. I downloaded Kubuntu KDE4 last night, so it doesn't seem to make much sense
 I suspect the bug is still present. I'm gonna use Ubuntu in the mean time :/

Spankin (spankin) wrote :

yep, i got exactly the same that zephirum did, it is a shame, because i have to stay with windows until it is solved somehow

daniel (wrana) wrote :

can confirm this exact behavior on hardy-kde4

Yuriy Kozlov (yuriy-kozlov) wrote :

Despite the commit message above, network-manager-kde still does not depend on knetworkconf:
Depends: kdelibs4c2a (>= 4:3.5.8-1), libc6 (>= 2.4), libdbus-1-3 (>= 1.1.1), libdbus-qt-1-1c2 (>= 0.62.git.20060814), libgcc1, libhal1
         (>= 0.5.8.1), libice6 (>= 1:1.0.0), libnl1, libnm-util0, libpng12-0 (>= 1.2.13-4), libqt3-mt (>= 3:3.3.8-b), libsm6, libstdc++6
         (>= 4.1.1-21), libx11-6, libxext6, network-manager (>= 0.6.2), networkstatus (>= 4:3.5.9), zlib1g (>= 1:1.2.3.3.dfsg-1)
Recommends: kwalletmanager, network-manager-openvpn, network-manager-pptp, network-manager-vpnc

Changed in knetworkmanager:
status: Fix Released → Confirmed
Yuriy Kozlov (yuriy-kozlov) wrote :

@zephirum, spankin, daniel: Does it just not show up or do you get the "Could not parse XML file" message? Do you have knetworkconf-kde4 installed (you should by default).

As a workaround, install knetworkconf and run it with
kdesudo kcmshell kcm_knetworkconfmodule

Changed in kdeadmin:
status: New → Incomplete
Yuriy Kozlov (yuriy-kozlov) wrote :

kubuntu-kde4-desktop depends on knetworkconf-kde4 now, so that part is fixed.

Changed in kubuntu-kde4-meta:
status: Confirmed → Fix Released
zephirum (zephirum) wrote :

Hi, sorry I'm a bit of a Linux noob, so I will try and give as much information as possible, hopefully it will help.
I seemed to have a double problem.

The part where I can't seem to connect to the internet is fixed (partially) apparently it is due to the network controller I'm using - Nvidia MCP55
solution here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/136836

However the Knetworkconf menu thing is a different story. I can confirm that I did have (uninstalled Kubuntu and got Ubuntu instead) Knetworkconf-KDE4, but for some reason, Knetworkmanager would report kcm_knetworkconfmodule missing. I installed Knetworkconf (without the KDE4 part) trying to fall back a version, which successfully brought up a manual configuration menu, but it was odd that the settings won't stick, couldn't set the setting either at DHCP *OR* static ip, the select bullet thing prefers to unselected (you'd think it's one or the other), and somehow I get a static IP address on the configuration field as 169.254.11.86 when it should be around 10.1.1.2. One last thing, when I told kcmshell to list the modules, kcmshell stated there was no module present.

Hopefully that helps, I will stay with Ubuntu or I may use Kubuntu with KDE3 for the time being.

Spankin (spankin) wrote :

I managed somehow to fix this problem, at least for the time beeing.

At shell console:

ipconfig Your_IP_number netmask 255.255.255.0 up
route add default gw Your_gate_number
sudo nano -w /etc/resolv.conf
nameserver Your_DNS_server_1
nameserver Your_DNS_server_2
ctrl+q, Y, enter

now the configuration still shows 0 instead of actual data, and manual configuration works.. or not (depends on whatever), but finally, Internet works :) hope it will work for you as well

thanks for all help, cheers mates :)

Thomas Kluyver (takluyver) wrote :

>kubuntu-kde4-desktop depends on knetworkconf-kde4 now, so that part is fixed.

But knetworkmanager, at least on my computer (with version 1:0.2.2-1ubuntu2) still calls kcm_knetworkconfmodule (i.e. the KDE3 version--understandable while the KDE4 version is not working), so something needs a dependency on that. I do not see that this bug has been fixed in any sense.

I have added the bug with kcm_knetworkconfmodule separately, it is #229366.

Yuriy Kozlov (yuriy-kozlov) wrote :

Closing bug against kdeadmin, see bug 229366.

Changed in kdeadmin:
status: Incomplete → Invalid

This bug is not fixed. network-manager-kde needs to depend directly on knetworkconf. Not everyone installs kubuntu-desktop, and it is intuitive that features a package directly uses (like knetworkmconf) should be direct dependencies.

Luka Renko (lure) on 2009-05-01
Changed in knetworkmanager (Ubuntu):
assignee: Luka Renko (lure) → nobody
Jonathan Thomas (echidnaman) wrote :

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.

Changed in knetworkmanager (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers