You are not logged in.
Recently had some tempermental issues with the nm-applet - just disappearing from the bl-tint2-systray. Made an incorrect assumption that the new volumeicon fix would also fix nm-applet from disappearing.
Here are some wise and instructive threads from the Crunchbang forum for handling nm-applet effectively:
www.crunchbang.org/forums/viewtopic.php?id=39979
www.crunchbang.org/forums/viewtopic.php?id=20183
www.crunchbang.org/forums/viewtopic.php?id=34078
Simple method:
$ nm-applet
Last edited by jalexander9 (2016-08-04 22:42:56)
Offline
Recently had some tempermental issues with the nm-applet - just disappearing from the bl-tint2-systray.
Did you check the content of ~/.xsession-errors for any useful messages?
Does your connection go down when the icon disappears?
Online
Also...I'm curious to know, does the icon completely disappear and it's space is removed? Or does it disappear and there's still a blank spot where it was?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Here is a usefull ~/.xsession-errors message -
(nm-applet:1258): nm-applet-WARNING **: (applet-device-broadband.c:500):broadband_state_to_mb_state: code should not be reached
1470163131168 addons.productaddons ERROR Request failed certificate checks: [Exception... "SSL is required and URI scheme is not https." nsresult: "0x8000ffff (N$
But I would add that there is an unused Ericsson Broadband driver which I never use anymore, but nothing has changed.
Answer #2: Not a complete loss of connection; but it blinks for a moment, then it is fine.
When the nm-applet disappears; like I say,
$ nm-applet
The applet re-appears.
Last edited by jalexander9 (2016-08-02 18:52:55)
Offline
Can we see the full content of ~/.xsession-errors (from a session in which nm-applet has failed), please?
You can also investigate with the systemd journal.
Add your user to the systemd-journal group to view all of the mesages:
sudo gpasswd -a $USER systemd-journal && newgrp systemd-journal
Then open a terminal window and run this command:
journalctl -xf
Then wait for nm-applet to fail and see if any messages are printed to the terminal window.
Online
@Horizon Brave - When it disappears, the systray spacing closes tighter together; however, I can still invoke the CLI to make it re-appear and the systray spacing expands again to show its re-appearance.
Offline
Do you want me to force nm-applet closed?
$ pkill nm-applet
EDIT: Because this is the tempermental part; I don't know when it just disappears.
Last edited by jalexander9 (2016-08-02 19:03:12)
Offline
^ No, just wait for it to fail so that we can observe the error message.
I can wait
Online
Okay, I am going to log-off now; re-boot, and use only Wi-Fi connection because 90% of the time that is when it happens, not always.
Offline
Sorry (maybe this is a good thing) nm-applet does not disappear today with different logins and two internet connections, I just can't reproduce this error.
I have to perform more errands this afternoon. When it fails sometime I will perform your method outlined on your post #5 above.
BTW thanks for the help on this it can be rather annoying! Thanks again.
Offline
If it happens again. Try.
nm-applet >/dev/null 2>1 &
Last edited by kabotage (2016-08-03 11:35:29)
Keeping an empty milk jar is great for piss break if you can't stop the game!
Offline
@kabotage - Well, thanks for this suggestion. Can you tell me a little more about what this will do? Priorities, maybe?
Offline
@HoaS, @HorizonBrave, @kabotage - The nm-applet disappeared this afternoon...without further ado:
Here is the output from the Journalctl -xf:
-- Logs begin at Wed 2016-08-03 13:31:26 CDT. --
Aug 03 13:34:40 thinkp06k22bunsen sudo[1334]: pam_unix(sudo:session): session opened for user root by jalexander06k22(uid=0)
Aug 03 13:36:48 thinkp06k22bunsen wpa_supplicant[911]: wlan0: WPA: Group rekeying completed with d0:59:e4:f5:43:26 [GTK=CCMP]
Aug 03 13:38:57 thinkp06k22bunsen wpa_supplicant[911]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Aug 03 13:41:25 thinkp06k22bunsen sudo[1334]: pam_unix(sudo:session): session closed for user root
Aug 03 13:42:55 thinkp06k22bunsen sudo[1602]: jalexander06k22 : TTY=pts/0 ; PWD=/home/jalexander06k22 ; USER=root ; COMMAND=/usr/bin/gpasswd -a systemd-journal
Aug 03 13:42:55 thinkp06k22bunsen sudo[1602]: pam_unix(sudo:session): session opened for user root by jalexander06k22(uid=0)
Aug 03 13:42:55 thinkp06k22bunsen sudo[1602]: pam_unix(sudo:session): session closed for user root
Aug 03 13:42:57 thinkp06k22bunsen wpa_supplicant[911]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Aug 03 13:44:17 thinkp06k22bunsen sudo[1631]: jalexander06k22 : TTY=pts/0 ; PWD=/home/jalexander06k22 ; USER=root ; COMMAND=/bin/journalctl -xf
Aug 03 13:44:17 thinkp06k22bunsen sudo[1631]: pam_unix(sudo:session): session opened for user root by jalexander06k22(uid=0)
Aug 03 13:44:57 thinkp06k22bunsen wpa_supplicant[911]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Here is the output from ~/.xsession.errors:
(nm-applet:1217): nm-applet-WARNING **: Cannot grab information for modem at /org/freedesktop/ModemManager1/Modem/0: No ModemManager support
Offline
I wonder if I am supposed to lock-down/block/comment-out the Ericsson Broadband device/driver in some way that I have not done as of yet?
I am going to wait before attempted an CLI invoking of nm-applet, and I am still unsure of the suggestion given by @kabotage; (the /dev/null and the '<' redirect I can understand, but not sure what are all of the implications, as of yet.)
Offline
hmm... Gotta punt this to the "eldars" ... I see nothing to my untrained eye.. The WPA thing **looks** to me like some sort of failed authentication? So many if the authentication fails, it drops the connection? Then reattempts and it succeeds? No idea...
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
I wonder if I am supposed to lock-down/block/comment-out the Ericsson Broadband device/driver in some way that I have not done as of yet?
I am going to wait before attempted an CLI invoking of nm-applet, and I am still unsure of the suggestion given by @kabotage; (the /dev/null and the '<' redirect I can understand, but not sure what are all of the implications, as of yet.)
The redirect to dev/null then outputs it to the screen, just so you can see the errors if any...it's a passive command, no harm will be done.
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
For the next twenty minutes going to collect more internet webpages that match essential words related to my problem. The freedesktop.org wiki that will further explain ModemManager no support seems like a good place to start.
Until a few hours later will check back, thanks again for the help Bunsenlab!
Offline
It happened again this afternoon. So, I went ahead and did @kabotage suggestion.
It worked, nm-applet re-appeared; and the output given was:
[1] 1354
Difference being that the terminal is refreshed to a new shell prompt, while nm-applet is visible and running.
Marking this one as solved! Again thanks for this.
EDIT: The "[1] 1354" output turns out to be a report named "1" in the /home directory which details presumably ~/.xsession-errors.
Last edited by jalexander9 (2016-08-06 01:21:27)
Offline
JAlexander, so are you going to add the
nm-applet >/dev/null 2>1 &
to your openbox autostart?
Also how were you starting nm-applet prior to this?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
@Horizon Brave - I believe I will have to shutdown/block/comment-out the Ericsson Broadband card so that it does not try to start up a phony Broadband connection at boot-time. Until then, the bl-tint2-systray boots correctly everytime. The only time nm-applet disappears is when I manually reach (GUI/mouse-click) to toggle-off a Wi-Fi connection. This happens only 10% of those times. I will use @kabotage's suggestion (i.e. nm-applet >/dev/null 2>1 &) when that instance occurs in the future.
Offline