[solved] I think I lost network-manager on last d-u

[vilde]

After a d-u I manage to install network-manager again, I also installed network-manager-gnome, I think I need the last one in xfce for showing network-manager in system tray (is that right?)

Anyway, I still don't have modemmanager, installation of that caused my network-manager disapear from system-tray the last time.

What do I need modemmanager for?

Code Select Expand

vilde@siductionboxt410:~$ apt-cache policy network-manager
network-manager:
  Installerad: 0.9.8.8-4
  Kandidat:    0.9.8.8-4
  Versionstabell:
*** 0.9.8.8-4 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
vilde@siductionboxt410:~$ apt-cache policy network-manager-gnome
network-manager-gnome:
  Installerad: 0.9.8.8-2
  Kandidat:    0.9.8.8-2
  Versionstabell:
*** 0.9.8.8-2 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

[ayla]

Modemmanager is needed for mobile broadband connections (e.g. GSM UMTS) with network-manager.

It has nothing to do with your disapeared icon in system tray.

Sorry, I don't know what's needed to get it back on XFCE.

[vilde]

@ayla, after todays installation of network-manager and network-manager-gnome I have network-manager working and in system tray.

[ayla]

@vilde: Ah, sorry, I should read more carefully.

Tested again on KDE, no change, no connection with the new networkmanager.

I suggest to let it (and it's companions) on hold on KDE for now.

[vilde]

I don't know if this will help anybody but this s how I did today.

I started with ceni managing my network and network-manager not installed.

I did a d-u

Now I

Code Select Expand

apt-get install network-manager-gnome this will also install network-manager (for kde you probably need plasma-nm instead of network-manager-gnome)

dpgk reported failure to start and configure network-manager, this is because ceni was managing network

I started ceni and removed my settings for in my case wlan0 (this you have to do), then in ceni I choose to "Activate Network Manager" and then "Use Network Manager and quit ceni"

Now I do

Code Select Expand

apt-get install network-manager-gnome again and now apt will configure and start network-manager.

I think I had to reboot to get the nework-manager appear in system tray.

[absolut]

my today's dist-upgrade in kde did not remove network-manager, but installed plasma-nm...
unfortunately, all saved connections configurations were lost

[ayla]

On my system they only seem to be lost, because plasma-nm didn't show them and didn't seem to save anything new.

After I downgraded they were back.

[absolut]

On my system they only seem to be lost, because plasma-nm didn't show them and didn't seem to save anything new.

After I downgraded they were back.

ah, okay, thanks for the info... i'll try to find out how to import these into plasma-nm...

[ayla]

I had nothing to do, just purged NM, modemmanager and plasma-nm and installed them from testing.

modemmanager refused to get purged, so I had to give it's pre-removal script an "exit 0" after the "set -e" line.

[louispolaire]

This morning I was able to upgrade network-manager and it works now on my system (xfce)

Code Select Expand

# apt-cache policy network-manager
network-manager:
  Installé : 0.9.8.0-5
  Candidat : 0.9.8.8-5
Table de version :
     0.9.8.8-5 0
        500 http://ftp.fr.debian.org/debian/ unstable/main amd64 Packages
*** 0.9.8.0-5 0
        100 /var/lib/dpkg/status

maybe the people who upgraded to  0.9.8.8-4 can reinstall network-manager

however it's still not a good idea to dist-upgrade as testdisk is to be removed today...

[ayla]

I can confirm this for KDE

Code Select Expand


apt-mark unhold network-manager plasma-nm modemmanager
apt-get update
apt-get dist-upgrade
apt-cache policy network-manager
network-manager:
  Installiert:           0.9.8.8-5
  Installationskandidat: 0.9.8.8-5
  Versionstabelle:
*** 0.9.8.8-5 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     0.9.8.0-5 0
        500 http://http.debian.net/debian/ testing/main amd64 Packages
cal@neskaya:~cal: apt-cache policy plasma-nm
plasma-nm:
  Installiert:           0.9.3.3-2
  Installationskandidat: 0.9.3.3-2
  Versionstabelle:
*** 0.9.3.3-2 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     0.9.3.2-3 0
        500 http://http.debian.net/debian/ testing/main amd64 Packages
cal@neskaya:~cal: apt-cache policy modemmanager
modemmanager:
  Installiert:           1.0.0-4
  Installationskandidat: 1.0.0-4
  Versionstabelle:
*** 1.0.0-4 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        500 http://http.debian.net/debian/ testing/main amd64 Packages
        100 /var/lib/dpkg/status



Works here as expected.

[melmarker]

@louispolaire: let testdisk go - it only of use if you have crashed or formatted external media - if your main system is destroyed a installed testdisk is not useful - in that case use a live iso, which contain testdisk already.

[louispolaire]

@melmarker : That is a very good comment  . So it's time for a d-u before things get worse...

[GoinEasy9]

While everything seems to be working correctly, it seems that ModemManager has taken the top spot on the systemd-analyze blame chart.

# systemd-analyze blame
         16.393s NetworkManager.service
         16.259s ModemManager.service
         15.819s dirmngr.service
         11.743s cron.service
          8.412s systemd-fsck-root.service
          6.157s acpi-support.service
          6.148s preload.service
          4.549s avahi-daemon.service
          4.543s systemd-logind.service
          4.016s mdadm-raid.service

It used to only take a little over 2 seconds.

[ayla]

hmm...

Code Select Expand

systemd-analyze blame
          1.024s acpi-fakekey.service
           430ms console-setup.service
           410ms vboxdrv.service
           370ms systemd-fsck-root.service
           363ms rpcbind.service
           351ms resolvconf.service
           228ms acpi-support.service
           157ms dirmngr.service
           137ms ModemManager.service
           133ms NetworkManager.service
           110ms avahi-daemon.service
           109ms networking.service
           101ms keyboard-setup.service
ok, this system is startet from a ssd, but such a difference seems odd...

Does journalctl -xn telling something useful?
or may be journalctl -b -p err