Funny behavior for NM and the KDE plasmoid
I am running openSUSE 12.1 KDE using Rev 0.9.1.90-4.6.1-x86_64 ov NetworkManager, and version 0.9.1+0.9.0-1.6.1-x86_64 of the plasmoid-networkmanagement applet. For the most part, any problems that I see are the fault of the underlying wireless drivers; however, I do see one problem. In general, the applet shows whatever APs that show up in a manually-triggered scan. There is, however, one exception. If I have the "Connect Automatically" box checked for one of the APs, that AP rarely shows in the possible connections. The one major exception is when the driver is unloaded, and then reloaded, when the connection is started nearly instantly. I have not tested the nm-applet to see if it shows the same behavior. Are there any steps that I can take to help show where the problem happens? Thanks, Larry ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[ModemManager] Two SMS bugs in the new code
1. When a new single-part message arrives, an "Added" signal is sent but the "Completed" signal is not sent. 2. Multipart messages don't seem to work - the multipart bit isn't getting set correctly somewhere?. See logs: 2012-04-25T16:56:55.500166-07:00 localhost ModemManager[1238]: [1335398215.499970] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): <-- '+CMTI: "ME",10' 2012-04-25T16:56:55.500351-07:00 localhost ModemManager[1238]: [1335398215.500199] [mm-serial-port.c:929] mm_serial_port_open(): (ttyACM1) device open count is 2 (open) 2012-04-25T16:56:55.500554-07:00 localhost ModemManager[1238]: [1335398215.500420] [mm-at-serial-port.c:385] debug_log(): (ttyACM0): <-- '+CMTI: "ME",10' 2012-04-25T16:56:55.500781-07:00 localhost ModemManager[1238]: [1335398215.500646] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): --> 'AT+CMGR=10' 2012-04-25T16:56:55.528526-07:00 localhost ModemManager[1238]: [1335398215.528348] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): <-- '+CMGR: 0,,15907912160130320F5440B916171056429F521405291650569A00500034C0201A9E8F41C949E83C2207B599E07B1DFEE33885E9ED3' 2012-04-25T16:56:55.529131-07:00 localhost ModemManager[1238]: [1335398215.528832] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): <-- '41E4F23C7D7697C920FA1B54C697E5E3F4BC0C6AD7D9F434081E96D341E3303C2C4EB3D3F4BC0B94A483E6E8779D4D06CDD1EF3BA80E0785E7A0B7BB0C6A97E7F3F0B9CC02B9DF7450780EA2DFDF2C50780EA2A3CBA0BA9B5C96B3F369F71954768FDFE4B4FB0C9297E1F2F2BCECA6CF41' 2012-04-25T16:56:55.529514-07:00 localhost ModemManager[1238]: [1335398215.529373] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): <-- 'OK' 2012-04-25T16:56:55.529856-07:00 localhost ModemManager[1238]: [1335398215.529719] [mm-broadband-modem.c:4186] sms_part_ready(): Correctly parsed PDU (10) 2012-04-25T16:56:55.530756-07:00 localhost ModemManager[1238]: [1335398215.530554] [mm-iface-modem-messaging.c:344] mm_iface_modem_messaging_take_part(): Couldn't take part in SMS list: 'This SMS is not a multipart message' 2012-04-25T16:56:55.530851-07:00 localhost ModemManager[1238]: [1335398215.530692] [mm-serial-port.c:969] mm_serial_port_close(): (ttyACM1) device open count is 1 (close) 2012-04-25T16:56:57.392557-07:00 localhost ModemManager[1238]: [1335398217.392363] [mm-at-serial-port.c:385] debug_log(): (ttyACM0): <-- '+CMTI: "ME",11' 2012-04-25T16:56:57.392741-07:00 localhost ModemManager[1238]: [1335398217.392588] [mm-serial-port.c:929] mm_serial_port_open(): (ttyACM1) device open count is 2 (open) 2012-04-25T16:56:57.393086-07:00 localhost ModemManager[1238]: [1335398217.392845] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): <-- '+CMTI: "ME",11' 2012-04-25T16:56:57.393325-07:00 localhost ModemManager[1238]: [1335398217.393184] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): --> 'AT+CMGR=11' 2012-04-25T16:56:57.421656-07:00 localhost ModemManager[1238]: [1335398217.421476] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): <-- '+CMGR: 0,,6307912160130320F6440B916171056429F521405291651569320500034C0202E9E8301D44479741F0B09C3E0785E56590BCCC0ED3C' 2012-04-25T16:56:57.421966-07:00 localhost ModemManager[1238]: [1335398217.421821] [mm-at-serial-port.c:385] debug_log(): (ttyACM1): <-- 'B6410FD0D7ABBCBA0B0FB4D4797E52E10OK' 2012-04-25T16:56:57.422362-07:00 localhost ModemManager[1238]: [1335398217.422207] [mm-broadband-modem.c:4186] sms_part_ready(): Correctly parsed PDU (11) 2012-04-25T16:56:57.423165-07:00 localhost ModemManager[1238]: [1335398217.422971] [mm-iface-modem-messaging.c:344] mm_iface_modem_messaging_take_part(): Couldn't take part in SMS list: 'This SMS is not a multipart message' - Nathan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: After laptop resume NM doesn't come active
Dan Williams wrote: > > On Tue, 2012-04-24 at 08:03 -0700, binro wrote: >> >> binro wrote: >> > >> > After I wakeup my laptop NM re-activates the WiFi connection. That >> works >> > but NM never seems to see the signal that tells it a connection is up >> and >> > to change its status to started (this is a Gentoo system). Hence >> network >> > dependent services never start. Is there some dbus invocation I can use >> to >> > make NM change state? >> > >> > TIA >> > >> > >> I "solved" the problem by plugging in an ether net cable which generated >> an >> event and NM became started. But I don't regard this as a permanent >> solution... ;) > > When this happens, can you run "nmcli nm" and post the output? > > topaz robin # serv NetworkManager status * status: inactive topaz robin # nmcli nm RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connected enabled enabledenabled disabled The network is up and running as I post this, just NM'a status is wrong. -- View this message in context: http://old.nabble.com/After-laptop-resume-NM-doesn%27t-come-active-tp33728260p33746097.html Sent from the Gnome - NetworkManager mailing list archive at Nabble.com. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Nm-applet crashes with assertion `dest_width > 0' failed
Hello, I wonder if you know the solution to the following bug: https://bugs.archlinux.org/task/29277 To sum up, when system tray is smaller than 18px the icon is not shown at all and nm-applet displays "'dest_width > 0' failed " error message. Thanks, Michal pgpJgFiwUUmjd.pgp Description: PGP signature ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
