[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#836139: marked as done (network-manager: plasma-nm wrong icon with network-manager 1.4)

Your message dated Fri, 7 Apr 2017 19:10:07 +0200
with message-id <20170407171007.2l2rxxw3tgf3myco@gnuservers.com.ar>
and subject line Re: Bug#836139: networkmanager: Fails to connect to wifi networks
has caused the Debian Bug report #836139,
regarding network-manager: plasma-nm wrong icon with network-manager 1.4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
836139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836139
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libkf5networkmanagerqt6
Version: 5.25.0-1
Severity: important
File: networkmanager

Dear Maintainer,

Updating nm breaks its ability to connect to Wifi networks.

I am using a broadcom chip with the firmware-sta-dkms package installed.
It worked well until I updated to 5.25.0-1 when, although it saw the
wifi networks around me, it cannot connect to them (log attached)

A work around is to disable mac address randomization as described in
[1]. However while using this work around, the plasma widget in the
system tray shows that the network is not connected (the icon is the blank
wifi symbol with a question mark), however it is actually connected and
working.

I do not know if the fix that has been committed upstream [2] solves
this second issue or not.

Thanks
paddatrapper

[1] https://bugs.archlinux.org/task/50541
[2] https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a3fd48545cf186a7e33aa9df8c3dd2bc016b350d

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libkf5networkmanagerqt6 depends on:
ii  libc6           2.23-5
ii  libqt5core5a    5.6.1+dfsg-3+b1
ii  libqt5dbus5     5.6.1+dfsg-3+b1
ii  libqt5network5  5.6.1+dfsg-3+b1
ii  libstdc++6      6.2.0-1

libkf5networkmanagerqt6 recommends no packages.

libkf5networkmanagerqt6 suggests no packages.

-- no debconf information

-- Log:
Aug 30 22:22:01 kyle-laptop NetworkManager[932]: <info> [1472588521.9907] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 30 22:22:01 kyle-laptop NetworkManager[932]: <info> [1472588521.9909] manager: NetworkManager state is now CONNECTING
Aug 30 22:22:01 kyle-laptop dbus[919]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Aug 30 22:22:01 kyle-laptop NetworkManager[932]: <error> [1472588521.9918] platform-linux: do-change-link[3]: failure changing link: failure 23 (Too many open files in system)
Aug 30 22:22:01 kyle-laptop NetworkManager[932]: <warn> [1472588521.9918] device (wlp2s0): set-hw-addr: failed to set-cloned MAC address to 14:2D:27:E9:B2:F5 (permanent) (unspecified)
Aug 30 22:22:01 kyle-laptop NetworkManager[932]: <info> [1472588521.9925] device (wlp2s0): state change: prepare -> failed (reason 'none') [40 120 0]
Aug 30 22:22:01 kyle-laptop NetworkManager[932]: <info> [1472588521.9927] manager: NetworkManager state is now CONNECTED_LOCAL
Aug 30 22:22:01 kyle-laptop NetworkManager[932]: <warn> [1472588521.9931] device (wlp2s0): Activation: failed for connection 'Robbertze_Wifi'
Aug 30 22:22:01 kyle-laptop NetworkManager[932]: <info> [1472588521.9937] device (wlp2s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Aug 30 22:22:02 kyle-laptop org.kde.kdeconnect[1478]: No such interface org.freedesktop.DBus.Properties on object at path /org/freedesktop/NetworkManager/ActiveConnection/8
Aug 30 22:22:02 kyle-laptop NetworkManager[932]: <error> [1472588521.9942] platform-linux: do-change-link[3]: failure changing link: failure 23 (Too many open files in system)
Aug 30 22:22:02 kyle-laptop NetworkManager[932]: <warn> [1472588521.9942] device (wlp2s0): set-hw-addr: failed to set MAC address to 46:0C:7F:48:80:2D (scanning) (unspecified)
Aug 30 22:22:02 kyle-laptop systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 30 22:22:02 kyle-laptop dbus[919]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 30 22:22:02 kyle-laptop systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 30 22:22:02 kyle-laptop nm-dispatcher: req:1 'connectivity-change': new request (2 scripts)
Aug 30 22:22:02 kyle-laptop nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Aug 30 22:22:02 kyle-laptop nm-dispatcher: req:2 'connectivity-change': new request (2 scripts)
Aug 30 22:22:02 kyle-laptop nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...

--- End Message ---
--- Begin Message --- 
¡Hola!


This part is reported in kde:
https://bugs.kde.org/show_bug.cgi?id=367938 And I can confirm that restarting plasmashell fixes it.
It also mentions that the network-manager issue that causes this was reported here: https://bugzilla.gnome.org/show_bug.cgi?id=770629
So, it seems that https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=923eaa6a478f95a69d1b9ccac429c7ffea3e4af4 needs to be applied in network-manager, and that might be unrelated to the issue mentioned earlier.
This fix is present in network manager for a couple of versions now, so I'm closing this issue. 

Happy hacking,
--
"If a pickpocket meets a saint, he sees only his pockets."
-- Kegley's Law
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: