Your message dated Wed, 27 Feb 2019 15:26:13 +0100
with message-id <[email protected]>
and subject line Re: network-manager: I think it's the same as #922554. No wifi
connection is possible.
has caused the Debian Bug report #922916,
regarding network-manager: I think it's the same as #922554. No wifi
connection is possible.
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 [email protected]
immediately.)
--
922916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922916
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.14.4-4
Severity: normal
Dear Maintainer,
* What led up to the situation?
Regular maintenance via aptitude (apt update).
* What exactly did you do (or not do) that was effective (or
ineffective)?
Waited for connection to be made.
* What was the outcome of this action?
No connection was made, either to secure or open wireless APs.
* What outcome did you expect instead?
A connection to be made, as was the case before maintenance.
By the way, all our similar systems (3 Lenovo X-220s) running Stretch
9.6 still work fine, unlike the 2 Lenovo X-220s running Buster/Sid.
All were updated via apt today.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages network-manager depends on:
ii adduser 3.118
ii dbus 1.12.12-1
ii init-system-helpers 1.56+nmu1
ii libaudit1 1:2.8.4-2
ii libbluetooth3 5.50-1
ii libc6 2.28-6
ii libcurl3-gnutls 7.64.0-1
ii libglib2.0-0 2.58.3-1
ii libgnutls30 3.6.6-2
ii libjansson4 2.12-1
ii libmm-glib0 1.10.0-1
ii libndp0 1.6-1+b1
ii libnewt0.52 0.52.20-8
ii libnm0 1.14.4-4
ii libpam-systemd 240-5
ii libpolkit-agent-1-0 0.105-25
ii libpolkit-gobject-1-0 0.105-25
ii libpsl5 0.20.2-2
ii libreadline7 7.0-5
ii libselinux1 2.8-1+b1
ii libsystemd0 240-5
ii libteamdctl0 1.28-1
ii libudev1 240-5
ii libuuid1 2.33.1-0.1
ii lsb-base 10.2018112800
ii policykit-1 0.105-25
ii udev 240-5
ii wpasupplicant 2:2.6-21
Versions of packages network-manager recommends:
ii crda 3.18-1
ii dnsmasq-base [dnsmasq-base] 2.80-1
ii iptables 1.8.2-3
ii isc-dhcp-client 4.4.1-2
ii modemmanager 1.10.0-1
ii ppp 2.4.7-2+4
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 27.02.19 um 15:05 schrieb Steve Newcomb:
>> Do you have network-manager-config-connectivity-debian installed or
> enabled connectivity checking via other means?
>
>> Can you provide a debug log of network-manager please.
> See https://wiki.gnome.org/Projects/NetworkManager/Debugging
>
> The good news is that this problem disappeared after the next aptitude
> update.
The log was full off driver error messages. Maybe something got mixed up
in the kernel.
I'd say let's close this issue for now and reopen if it resurfaces.
Thanks for reporting back.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
