KDE network management backend changed on update.

The last couple of KDE updates have caused the network management backend to be changed to wicd. I use NetworkManager 0.9 -- I don't even have wicd installed (but I used to). The network backends listed in System Settings / Information Sources are NetworkManager 0.9, Wicd and Fake Net, but after updating Wicd is moved to the top of the list and NM0.9 to the bottom.
The first time this happened, my wireless stopped working until I worked out what had changed, but when I updated today (KDE 4.6.3-1 to 4.6.3-2), KDE Daemon and Plasma Desktop would crash when I logged in. I was able to start programs from krunner, so ran plasma-desktop from konsole and saw wicd mentioned in the output before it crashed. I changed the network management backend back to NM in systemsettings and now it works.
Can anyone tell me why the backend is changed when I update? Should Wicd even be listed, since it isn't installed?
I also noticed a couple of other weird things after updating today. I'm not sure they are related, but I'll mention them just in case. The arch logo that appears at the start when I boot has changed to a picture of tux, and a modprobe usage message appears just before the line "INIT: version 2.88 starting" (or something like that).

i thought they were the same thing... Tried knetworkmanager and it works fine, thank you very much.

Similar Messages

KDE. network manager "No agents were available for this request"

I think there might be a bug with the networkmanagement plasmoid.
Not sure if this is the right place to post it, or if maybe I should take this to the KDE forms¿??
Anyway, took me quite a while to reproduce this, but it seems that with WPA wireless connections, when setting the "store connection secrets" to: "in secure storage (encrypted)", and then trying to edit the connection, an error is displayed with the following:
"No agents were available for this request"
im running kdeplasma-applets-networkmanagement 1:0.9.0.5-1 with its marked dependencies.
Can anyone explain why this is happening?
Am I missing something (agent??) in order to be able to store secrets in an encrypted file?
Cheers.

Use net-profiles. arch linux wiki recommended that i think. Anyways, kde network manager lose connection every 1 minutes( in 2 machines i have tested ubuntu and arch linux).

Prevent Network Manager from changing my DNS-And good books aboutLinux

-R option here is not working. What should i do?
Also i want to learn more about the Linux. The wiki's are good to make one thing,but they are not getting to details much. I want something deeper. I want every detail,mentioning even the smallest thing. So what can you suggest?
And i've always wondered why Windows booting faster than GNU/Linux systems?In 20-25 seconds the desktop gets
ready.
Last edited by Paingiver (2008-03-13 10:57:15)

I am on the edge. I've been working on this wireless to get work for 1 week. And i am getting frustrated. I have Ralink with rt2500 chipset. For now i am trying the netcfg2. Though the result is same in network-manager.I can connect to wireless network but after 30 seconds i cannot browse any site.It is still seen as connected though.
My rc.conf:
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(lo eth0 wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles
#NET_PROFILES=()
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !netfs crond alsa hal fam network)
My iwconfig:
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
iwlist scan works. And whenever i boot or restart the network i get this:
err, wlan0: timed out
err, wlan0: lease expired 20153 seconds ago
warn, wlan0: using IPV4LL address 169.254.51.42

Allow users to manage and change Automatic Update settings

Server SBS 2011 SP 1
Couldn't find a thread that helped. Hoping to get some light on my situation.
The client has users who they'd like to have full control of their client PCs Windows Automatic Updates. The users would like to go into Control Panel and check updates at will, set times for auto updates to their liking. I haven't found the appropriate
GPO setting to allow users to change update settings.
Is that possible? Will creating an OU without a linked GPO and blocking inheritance provide the answer?
Thanks ALL!

Server SBS 2011 SP 1
The client has users who they'd like to have full control of their client PCs Windows Automatic Updates. The users would like to go into Control Panel and check updates at will, set times for auto updates to their liking. I haven't found the appropriate
GPO setting to allow users to change update settings.
Is that possible? Will creating an OU without a linked GPO and blocking inheritance provide the answer?
the dedicated SBS forums might bet better for your question (since SBS can be finicky about some settings)
https://social.technet.microsoft.com/Forums/en-US/home?category=sbsserver
It will likely depend upon how the implementation is currently setup (there could be various things in place, in a customised fashion).
Basically, when using GPO to deploy WUAgent settings for WSUS, the user interface for WU is disabled for the end-user - this is how classic domain GP works, and is intended to work. (i.e. if the domain admin deploys a setting, end-users are unable to change
that)
You may be able to easily identify the relevant domain GPO that is delivering this setting, but you would (presumably) want to only change the single setting relating to AUOptions, and leave the other settings as they currently are (i.e. continue to use
WSUS to serve the update approvals and update files/patches.
Creating a new OU and not linking/inheriting, may cause other unintended effects/complexity.
(it might be the only way to achieve your goal, but analysing which GPOs are carrying which settings, and then which GPOs you *do* need to be linked/inherited, will be an important step)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

[Solved] Can't find a way to run network manager in kde

Struggling a little to get wi-fi set up on an arch machine running kde
I've installed plasma-applet-networkmanagement but I can't get it to run
There isn't any launcher for the applet on the menu anywhere but I have been able to find a .deskop file for it at: /usr/share/kde4/services/plasma-applet-networkmanagement.desktop
When I try to run it though I get a little dialog box showing the following error
The desktop entry of type
Service
is unknown
I've viewed the .desktop file in kwrite and these are the entries which seem relevant to running it
Type=Service
X-KDE-ServiceTypes=Plasma/Applet
Icon=networkmanager
X-KDE-PluginInfo-EnabledByDefault=true
X-Plasma-NotificationArea=true
The last entry seems to be telling it to place the network manager applet in the tray if I'm understanding it correctly, but this doesn't happen
Anyone able to tell me how to get the kde network manager working?
Last edited by Ecky (2011-12-27 17:47:34)

If you add a widget to the panel, or if you add a widget to the desktop -- in the ribbon that lets you select widgets, you should have one called "Network Management"
If you do, drag it to where you want the control.
If you don't, well... Let's see what happens first

[SOLVED] Network Manager systemd unit fails after update

EDIT: Reinstalling libnm-glib resolved this issue
After updating to the latest version of NetworkManager (networkmanager-0.9.8.10-3), the systemd unit fails to start. It works fine after downgrading back to the previous version though (networkmanager-0.9.8.10-1). I'm not sure if this is a bug or an error on my end; since the previous package works I've just dowgraded for the time being. For the update that doesn't work, here is the output of "systemctl status" and the systemd journal:
>>sudo systemctl daemon-reload
>> sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-06-11 15:28:25 EDT; 10s ago
Process: 24073 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=127)
Main PID: 24073 (code=exited, status=127)
Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
>> journalctl -xn
-- Logs begin at Tue 2014-06-10 12:47:19 EDT, end at Wed 2014-06-11 15:28:36 EDT. --
Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
Jun 11 15:28:25 kyle systemd[1]: Starting Network Manager...
-- Subject: Unit NetworkManager.service has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit NetworkManager.service has begun starting up.
Jun 11 15:28:25 kyle systemd[1]: NetworkManager.service: main process exited, code=exited, status=127/n/a
Jun 11 15:28:25 kyle systemd[1]: Failed to start Network Manager.
-- Subject: Unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit NetworkManager.service has failed.
-- The result is failed.
Jun 11 15:28:25 kyle systemd[1]: Unit NetworkManager.service entered failed state.
Jun 11 15:28:25 kyle sudo[24070]: pam_unix(sudo:session): session closed for user root
Jun 11 15:28:28 kyle dbus[489]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
Jun 11 15:28:36 kyle sudo[24075]: kyle : TTY=pts/2 ; PWD=/var/cache/pacman/pkg ; USER=root ; COMMAND=/usr/bin/systemctl status NetworkManager
Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session opened for user root by kyle(uid=0)
Jun 11 15:28:36 kyle sudo[24075]: pam_unix(sudo:session): session closed for user root
Last edited by T0k3n (2014-07-03 15:18:01)

Check the changes:
https://projects.archlinux.org/svntogit … e192881dc5
https://projects.archlinux.org/svntogit … ee906b6c44
When posting configs, code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Network manager vpn kde

I'm having trouble connecting to a VPN through network manager on KDE. I think my biggest problem is understanding the structure of Network Manager, can anyone help me out.
I have Network Manager running and configuring my wireless client perfectly through networkmanager-plasmoid.
I would like to setup a vpn through pptp. I tried to set this up through the plasmiod but it doesn't really do anything. I understand this is still alpha, so it may just not work.
I have installed networkmanager-pptp through aur. But what is this doing? It seems like in gnome this has a gui. Is this purely a gui or a backend as well.
Should I be manually setting up a vpn with pptp? It seems like the point of networkmanager is to configure this for me (or is network manager only going to start this and tell me when it is running).
Thanks for any help.

Currently, the plasmoid is in heavy development, so I recommend to remove it with pacman -R, and use the gnome networkmanager frontend. Use the connection editor, enter the gateway, username, password, domain, use the special button to choose the authentication method (pap, chap, mschap, mschapv2, choose only one, if the login fails, try another). On the ipv4 tab, use the routing button, and enter the routing info, e.g. 192.168.1.0, 255.255.255.0, and disable automatic routing.
Hope that helps.

How to change a network, managed user to admin user

Im current in a admin, network, managed user of this machine... i will be working from home in a couple of days, i was thinking if im in a network managed account i will not able to log in to my mac. is there a way for me to change it from a network managed user account to a locally admin account?

A network user is automatically converted to a mobile user on a portable Mac at the first login. On a desktop Mac, the conversion is optional. If the conversion is declined and the user opts not to be prompted again, the setting can be undone as follows:
sudo defaults delete /Library/Preferences/com.apple.MCX MobileAccountNeverAsk-username
(substituting the short user name for the string username.)
Credit for this solution to "E.Uncle" on the Apple OS X Server mailing list.

New network manager update disabling my wifi

Hi.
Just want let you know that there is something wrong with new network manager. after last update my network was disabled and I couldn't turn it on, when downgrade to previous version is working again ok.
My network card:
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 2200 (rev c4)
if you need any more info let me know please...

Did you remove the network from the phone and then reset the network settings? Or, did you have to try and select the network again? You also just provided a little more information, you said that you are to the point of entering the password. At first it seemed that you weren't even finding the wifi. If you are getting to the password screen and it is showing an error, try power cycling your router. Unplug the router, leave it off for about 30 seconds and then restart it. After it is restarted, then try connecting the phone.

Network manager kde

I have an intel 3945abg card. And I am running kde 4.3
Network-Manager and the plasmoid dont seem to recognize my wireless
but I can join wireless via the command line.
Any thoughts or suggestions?

Check this link
http://wiki.archlinux.org/index.php/Wireless_Setup

Network Management - Stopping Windows 10 P2P Updates

Skipping all the issues with the non-privacy of Windows 10 how as a network manager can I stop Windows 10 devices from opening up potentially thousands of active P2P connections trying to share their updates?I have businesses which want to provide Guest wifi access with most of those using equipment that meets the need. That means they spent what was required, not more, so that equipment is typically not what ATT has deployed in someplace like Atlanta International Airport. I can see this being a similar problem for places like Starbucks or Panera Bread where a commercial product has been used but is it ready to handle the potentially DDOS type of situation of Win10 P2P updates?If you have 10 Win10 devices show up at a coffee house and MS pushed an update so those 10 devices connect to 100, 500 even a thousand other Win10 devices you...
This topic first appeared in the Spiceworks Community

By Guest Blogger Brad Mathis, Senior Consultant, InformationSecurity It is mid-2015. By now, we have all seen incoming emails claiming we have been bequeathed a huge sum of money from a Nigerian Prince, or we have won a foreign lottery we never entered. Most employees have seen these scam emails long enough to know they are not real. However, What about the seemingly benign email coming in from a recognizable sender? What if this legitimate looking email has an attached PDF or Word document? What if it contains a seemingly real link to a web site? How many of your employees would open the attachment or click on the link? How many employees will assume it is safe since it made it unscathed through all of your layers of security, including email and web content filters? Do your users understand the ramifications of...

Need Suggestions For Network Manager/WICD

Hello again everyone. I seem to be full of issues today. Anyway, I'm a KDE guy and I've been using WICD to manage my network connections since around the time that KDE 4.x premiered, because as far as I know KDE does not have a viable network manager.
WICD works great, it connects before I even finish logging in, it connects to my networks without me having to interact at all, until now. Now, it's just acting strange, and I didn't change anything except whatever is changed during the normal updating of packages.
It started off not connecting to wired connections at all and only wireless at home. If I plugged in a network cable, it would try and try and try and then tell me that it couldn't get an IP address. Sometimes after restarting it would work but not every time. After a few more days, it started to connect to wireless connections only 50% of the time. A reboot would usually clear it up.
Now, as of today, it won't connect to anything. I took it to work as I usually do so I can use it in the lunch room (where there are three wireless AP's in range) and it wouldn't connect at all, and I tried rebooting five times. One of my coworkers had no problem connecting to the same wireless AP on her laptop that I could not connect to.
I've never known WICD to be problematic like this. I didn't change anything and I don't think it's been updated recently.
If there is a network manager for KDE that works more reliably, I'm open to suggestions. I prefer WICD because it (used to) worked so well. At the very least, I prefer having some sort of wireless manager. The one that shipped with Kubuntu in 9.04 is completely terrible so whatever that is I don't know if I want that unless it got drastically improved.

mcsaba77 wrote:
Unfortunately wicd has lots of issues with latest kernel. I've been following and posting in these two threads:
http://bbs.archlinux.org/viewtopic.php? … 33#p695433
http://bbs.archlinux.org/viewtopic.php? … 11#p694311
As for now, I switched to networkmanager. I use the default nm-applet, it works well, but I agree, it's not nearly as neat as wicd, and the icon is an eyesore Maybe a kernel/wicd update in the future will solve these issues, but as of now, too many people (on various hardware) seem to have issues with wicd + kernel 2.32.x.
EDIT>
Knetworkmanager unfortunately depends on kde3, while the plasmoid is completely broken at the moment. Hopefully they'll get it working (or they might have some sort of solution) in 4.4 release...
I also have this issue, really thank you for your threads.

Network Manager fails to connect with Huawei E3276 modem after upgrade

Hi,
I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
Error: failed to connect modem: Only IPv4 is supported by this modem.
I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
I would be grateful for any advice.
After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
Before upgrade (KDE 4.14)
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
Linux Mint 17.1 KDE (works the same like Arch before update)
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
Last edited by Shocker (2015-05-07 19:18:43)

This week, after update, modem works again.
However, there's a new bug in the kernel, which was not there before:
kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
but the modem works and connects to the network.
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.

KDE Printer Manager fails with "client-error-bad-request"

I'm having some trouble with printing on my system. The KDE printer manager shows "client-error-bad-request" and no other information. When I run the KCM from the command line, I also get "kcmshell(17286) KCupsRequest::serverError: status unrecognised: 1024" on the console. I wasn't able to find any useful information on this issue on google or these forums; not even what the 1024 status code means. It seems to me that this may be a bug in the kcm_printer_manager module, but I'd like to rule out other possibilities first. Unfortunately, I don't know what to try from here. I'll provide as much potentially relevant information as I can think of below.
Changes since last successful print job:
Multiple updates to KDE packages
Update to cups that changed systemd unit file names.
Stopped and disbled old units
daemon-reload
Enable and start new units
Other updates to cups since then, if I recall correctly.
Packages and versions:
kdeutils-print-manager 4.14.3-1 (owns kcm_printer_manager module for kcmshell4)
kdebase-runtime 4.14.3-1 (owns kcmshell4 binary)
cups 2.0.1-1
libcups 2.0.1-1
systemd 218-1
linux 3.17.6-1
Let me know if any other information might be helpful.

Anyone please help.
Thanks,
Orton

Trying to use wireless N with iwlwifi & network manager

Have all the h/w necessary to use wireless N:
Intel Centrino-N 1030
Linksys E3200 running Tomato 1.28
Linksys E4200 running dd-wrt 21286
Also updated everything today (pacman -Syu):
>uname -a
Linux hostname 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64 GNU/Linux
So, with either router set up with as an AP at 2.4GHz and N-Only (the centrino 1030 doesn't support 5GHz), and the module defaults loaded, I see odd behavior. First, once connected to either AP, Network Manager still reports the connection to be at B/G.
I checked the module config, and this part is relevant:
>modinfo iwlwifi | grep 11n
parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: agg TX, 4: agg RX (uint)
There's a lot of chatter on the forums about earlier kernels not supporting N w/ iwlwifi, and recommending to disable it with '11n_disable=1' in /etc/modprobe.d/iwlwifi.conf. So I tried explicitly enabling it, and assuming it's a binary value:
>cat /etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=0
After reloading the module(s) (and restarting wpa_supplicant & networkmanager), the thing I'm finding confusing is that I can see evidence of this change take effect:
>cat /sys/module/iwlwifi/parameters/11n_disable
0
...but it doesn't affect the output of modinfo (same as above), nor am I able to connect to either router at N (NM still reports B/G). Also confused how it connects at all when the routers are set to N-Only?

modinfo iwlwifi
That is not supposed to change. It just shows you the parameters and their valid configurations.
options iwlwifi 11n_disable=0
>cat /sys/module/iwlwifi/parameters/11n_disable
0
Did you check that it was not already 0?
...but it doesn't affect the output of modinfo (same as above), nor am I able to connect to either router at N (NM still reports B/G). Also confused how it connects at all when the routers are set to N-Only?
If the card connects with the routers set to n only, then the card is capable of working with n. I usually check with nm-tools and look at the speed indicated.
Here is the thing: Routers and cards sometimes negotiate a lower speed to prevent intereference with other devices. I usually 'get' N-speed only once I start to saturate the link.

KDE network management backend changed on update.

Similar Messages

Maybe you are looking for