[Bug 912584] New: WWAN broken after upgrade 13.1 to 13.2
http://bugzilla.opensuse.org/show_bug.cgi?id=912584 Bug ID: 912584 Summary: WWAN broken after upgrade 13.1 to 13.2 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: richard@nod.at QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I can no longer use my WWAN connection. Networkmanager logs: --- 2015-01-10T10:09:48.094382+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2015-01-10T10:09:48.095054+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2015-01-10T10:09:48.095615+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: need-auth -> prepare (reason 'none') [60 40 0] 2015-01-10T10:09:48.096162+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2015-01-10T10:09:48.103749+01:00 sandpuppy NetworkManager[1600]: <warn> (ttyUSB2) failed to connect modem: PolicyKit authorization error: 'authority not found' 2015-01-10T10:09:48.104445+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: prepare -> failed (reason '(null)') [40 120 1] 2015-01-10T10:09:48.105036+01:00 sandpuppy NetworkManager[1600]: <info> NetworkManager state is now CONNECTED_LOCAL 2015-01-10T10:09:48.106073+01:00 sandpuppy NetworkManager[1600]: <info> Disabling autoconnect for connection 'A1/Telekom Austria - A1 Breitband'. 2015-01-10T10:09:48.106571+01:00 sandpuppy NetworkManager[1600]: <warn> Activation (ttyUSB2) failed for connection 'A1/Telekom Austria - A1 Breitband' 2015-01-10T10:09:48.107030+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0] 2015-01-10T10:09:48.107482+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): deactivating device (reason 'none') [0] 2015-01-10T10:10:25.290151+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) starting connection 'A1/Telekom Austria - A1 Breitband' 2015-01-10T10:10:25.291302+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2015-01-10T10:10:25.292154+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2015-01-10T10:10:25.292931+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: disconnected -> prepare (reason 'none') [30 40 0] 2015-01-10T10:10:25.293724+01:00 sandpuppy NetworkManager[1600]: <info> NetworkManager state is now CONNECTING 2015-01-10T10:10:25.294449+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: prepare -> need-auth (reason 'none') [40 60 0] 2015-01-10T10:10:25.295167+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2015-01-10T10:10:25.318331+01:00 sandpuppy NetworkManager[1600]: (NetworkManager:1600): libnm-util-CRITICAL **: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed 2015-01-10T10:10:25.393312+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) scheduled... 2015-01-10T10:10:25.393994+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) started... 2015-01-10T10:10:25.394531+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: need-auth -> prepare (reason 'none') [60 40 0] 2015-01-10T10:10:25.395268+01:00 sandpuppy NetworkManager[1600]: <info> Activation (ttyUSB2) Stage 1 of 5 (Device Prepare) complete. 2015-01-10T10:10:25.402549+01:00 sandpuppy NetworkManager[1600]: <warn> (ttyUSB2) failed to connect modem: PolicyKit authorization error: 'authority not found' 2015-01-10T10:10:25.403277+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: prepare -> failed (reason '(null)') [40 120 1] 2015-01-10T10:10:25.404311+01:00 sandpuppy NetworkManager[1600]: <info> NetworkManager state is now CONNECTED_LOCAL 2015-01-10T10:10:25.404927+01:00 sandpuppy NetworkManager[1600]: <info> Disabling autoconnect for connection 'A1/Telekom Austria - A1 Breitband'. 2015-01-10T10:10:25.405455+01:00 sandpuppy NetworkManager[1600]: <warn> Activation (ttyUSB2) failed for connection 'A1/Telekom Austria - A1 Breitband' 2015-01-10T10:10:25.405993+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0] 2015-01-10T10:10:25.406506+01:00 sandpuppy NetworkManager[1600]: <info> (ttyUSB2): deactivating device (reason 'none') [0] --- Any ideas? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=912584
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=912584
--- Comment #2 from Richard Weinberger
http://bugzilla.opensuse.org/show_bug.cgi?id=912584
--- Comment #3 from Richard Weinberger
http://bugzilla.opensuse.org/show_bug.cgi?id=912584
Frederic Crozat
http://bugzilla.opensuse.org/show_bug.cgi?id=912584
Christian Boltz
BTW: After I got rid of all AppArmor stuff my WWAN works perfectly fine again. Maybe some AppArmor profile is too restrictive...
Please provide the AppArmor logs ;-) - if you have auditd running, /var/log/audit/audit.log - if you use syslog, grep apparmor /var/log/messages - if you only have journald running, journalctl -b | grep apparmor for all messages since this boot (use -b1 for previous boot etc.) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=912584
--- Comment #5 from Richard Weinberger
(In reply to Richard Weinberger from comment #3)
BTW: After I got rid of all AppArmor stuff my WWAN works perfectly fine again. Maybe some AppArmor profile is too restrictive...
Please provide the AppArmor logs ;-) - if you have auditd running, /var/log/audit/audit.log - if you use syslog, grep apparmor /var/log/messages - if you only have journald running, journalctl -b | grep apparmor for all messages since this boot (use -b1 for previous boot etc.)
Sorry, my logs rotated away already. I've reinstalled apparmor, started it but WWAN still worked. Now I'm puzzled what is going on. Fact is that after the upgrade from 13.1 to 13.2 WWAN stopped working. Last week I've uninstalled apparmor and yesterday I noticed that WWAN is working again. Sorry for offering not better debug infos. :-\ -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=912584
Christian Boltz
http://bugzilla.opensuse.org/show_bug.cgi?id=912584
http://bugzilla.opensuse.org/show_bug.cgi?id=912584#c6
Karl Cheng
participants (1)
-
bugzilla_noreply@novell.com