Requests - Just A Few Small Requests for GUI

[ghost]

Hi,

First let me say this is a really nice GUI, nice work, and I really hope you're going to be at this for years to come! :)

I have a few requests...

These are my specs;

Slackware 14.1 x86_64 Openbox 3.5.2 tint2

I start cmst from ~/.config/openbox/autostart

sleep 3s && cmst -m &

This is working really great, cmst goes straight to the tray of tint2 minimized.

Now the problem, when I click on the tray icon it always opens up MAXIMIZED in size filling up my entire screen.

Can you please make the gui open in a small default size when opening it back up, and also make the gui so the end-user can size it to the size they want, so it will maintain that size when opening it back up.

Then if you will please consider under the 'Details' tab, under 'Service', when clicking the drop down, for all the wifi connections just list only the ssid there, personally here I think it's easier for the end-user to find networks based on the ssid, and then when someone picks a wifi ssid, then all this information is listed below. The last time I checked the mac gets listed in the bottom with all the details, so it seems a bit redundant having the mac listed in three different places.

wifi_9988782_managed_psk

To be honest even as geeks, do we really need the MAC listed under 'Status' - 'Services' - 'Connection' and the 'Details' drop down menu? It seems a bit overkill for the average user to list all this, no? Isn't just listing the ssid and encryption type enough information? So for all the MAC numbers under the 'Connection', who really needs this information? Just some food for thought, unless this all just comes from connman and there's no way for you to control this output. But again, when an end-user picks the wifi under the 'Details', and clicks on the drop down, then as I mentioned before, under a 'Connection' section you create, then they get all this information, and only in this location. I personally think just the ssid and encryption type being listed under the 'Status' - 'Services' is enough information.

Also I think it's a good idea to remove the ChangeLog from the GUI, it's seems to be common to just keep this in a /doc file, plus the ChangeLog gui fills up my entire screen running from top to bottom, and whatever is being displayed on the bottom is cut off, so you can't read it.

And this is my really big request, hehe, can this PLEASE be made to work with xfce4-notifyd? Which I believe is just a GUI for notify-send for OSD notfications. :)

Thank you very much for your time and consideration for these requests, keep up the great work! :)

[andrew-bibb]

I just uploaded 14.06.07-1 that has wifi symbols in the system tray when connected by wifi. It is done so I can add cell and bluetooth connections if I ever get pages to accomodate those.

I'm thinking I'd like to do a release in next couple of days and then start again on knocking off the GUI things and then looking at the Notifiy enhancement. It occurs to me I should add you to the contributors list. Question then, do you want to be listed as a contributor in the About CMST dialog, and if you do how exactly do you want your name to appear?

[ghost]

Sounds good, can't wait for the gui changes...

Ohhh Contributor, LOL, can't say I do much, guess I could be the 'Details Coordinator' and then you could put me down as HawkEye LMAO, just kidding...

Let me think about this honor, I do like my anonymity, hmm my name plastered on the About section, then the Man can find me! LOL...

[andrew-bibb]

Let me know. You've certainly put in more than enough effort, but totally your call. There is no time limit on the offer.

When writing this I had skipped processing of information sent by the Connman dbus signals. I just used the fact that the signal was emitted to trigger the regeneration all of information displayed. The information (or at least some of it) contained inside the signal is actually what needs to be shown in the notifications. I just worked out how to grab the data contained inside the signal, so the hardest part of implementing notifications should be done.

[ghost]

Offer ok...

Notifications, WoOT! :)

Cheers

[ghost]

Hey you slacking off on me? Five days and no commits... LOL :)

[andrew-bibb]

The four cords of firewood that got delivered starting last Friday have been occupying most of my attention lately. Still got about two left to move and stack. Around here even in summer we are dealing with winter!

Right now my local copy is in a bit of disarray. I'm currently working on phase 2 of the notifications. Phase 1 was actually getting the data out of the dbus signals. Phase 2 is parsing that data and showing it in balloon popups from the system tray icon. Phase 3 will be sending the same parsed data to the notify daemon. In preferences I'll have check boxes to allow the user to send to one or the other, or neither. The phase 2 popups are working, but I tripped on selecting the wired or wireless icon (which actually will only be able to be displayed in the phase 3 notify daemon). If not for that I was going to upload last night and have you check out the progress. Probably be a day or two before my local copy is in a state where I can sync back to github.

[ghost]

Ahh busy being a Lumberjack... hehe :)

Wooo notifications...

check boxes to allow the user to send to one or the other?

What is one or the other?

Can't wait, and keep warm! :)

[andrew-bibb]

Either a popup run by the system tray icon, or a popup run by the notify daemon, you won't be able to have both at the same time. The first is for people don't actually have a notify daemon running but might want to see popups, the second is for people who do have the daemon running and want to use that to show notifications. With neither checked no notifications will be shown.

[ghost]

Ahh ok...

[andrew-bibb]

Just uploaded with the first cut of popups working from the system tray. They need to be enabled from the preferences tab, by default they are disabled. One of the limitations of this method is that icons are limited to the one's that are built into the class.

At this point just mainly interested if you think I'm on the right track.

Stopped raining a half hour ago so back to the firewood.

[ghost]

Ahhh getting there, now go jump some wood! LOL

bugs ---> https://github.com/andrew-bibb/cmst/issues/13

[andrew-bibb]

Nice looking dialog in your last post over in #13. So that is what you can do with theaming? I never knew.

[andrew-bibb]

Ahhh - did an upgrade this morning and my wireless card is now non-functional. First thought it was hacking on CMST, then discovered connmanctl would not work, then went back to a 4 week old version and that would not work. Finally did verify the card is working if I boot from an older linux version on a separate partition, so looked in the journal and it is absolutely flooded with failed probe requests from the kernel.

I'm so frustrated right now. Probably going to pull the card, so I may be relying on your input for wireless connections and any issues with switching connections. Whole day down the drain.

[ghost]

Sorry to hear on your WiFI, no worries my cards are working here! :)

Yes xfce4-notifyd allows you to theme the notifications... :)

[andrew-bibb]

Making progress on reconstructing the slots. Finally figured out the function signature so I get the data, now I just have to figure out how to demarshal it. Have made good progress on the individual technology and service object slots. Figured out how to ID them and both were implemented this evening. Anyway I'll keep plugging.

DIdn't pull the card, figured I blow another couple of hours trying to get it working. Very frustrating, it is there and I can see it, but according to "ip link" it won't pickup a carrier. I'm beginning to think maybe not the kernel upgrade and maybe the card is just fried.

edit: Man was I tired. No reason to pull the card, I've already ascertained it still works with an older kernel. No wonder I was not getting anywhere with it last night.

[ghost]

:)

[andrew-bibb]

Finally managed to demarshal the dbus message from SevicesChanged. Whew, that was fun. Pretty much have everything back together again, and was hoping to upload this evening but I've got one minor issue (name in the service box blips off at random times). Not entirely sure if it if from trying to activate the half dead wireless card or not, but I'm too beat to look at it any more tonight.

My oldest daughter is back in country after 2 years, starting tomorrow, so I'm probably not going to be hanging out here much for the next week.

[ghost]

Go have fun, we'll cry some more later! LOL...

[andrew-bibb]

Can still plug away on this a little bit. Did another system upgrade this morning which updated the kernel again, and my wifi started working. So of course I toggled power on and off like a mad man to test what I've been working on and hosed my wifi connection again. No matter what I try it won't connect, either with CMST or with connmanctl.

[progandy]

When I toggle power for my wifi card (either hw switch, rfkill or connman), it sometimes breaks. A symptom is this:

$ cat /sys/class/net/wlp2s0/carrier          :(
cat: /sys/class/net/wlp2s0/carrier: Invalid argument

After some crazy block/unblock switching with the hardware switch and/or rfkill the interface will fix itself in most cases.

[andrew-bibb]

Something has changed, Mr Green in thread 20 is getting a similar,but yet not the same problem. On his system neither connman nor any other network utility would work until he toggled rfkill. I've tried CMST and the built in connmanctl interface and no luck. The service shows up (sometimes), but can't connect to it and when you try it disappears.

One thing I forgot, in the middle of my upgrade yesterday (the download package stage) we had a 2 hour power failure. When the power came back I finished the upgrade, and then got right onto the wifi service. Of course then I hosed it by playing, but it definetely was working at one point. I want to try unplugging the router overnight to see what happens. No amount of rfkill on and off or anything else I try will work. On my guest partition with an older kernel the newest version of CMST works just fine. I can build it over there and then use it to toggle power on and off all day long with no problem.

I've been looking around the internet and at the Arch forums and maybe it is just me, but there seems to be a lot of wifi problems all of a sudden with recent kernel upgrades. Maybe it is the same level and I never paid attention, but they are out there now.

Moulei: Mr Green, Progandy and I are all using Arch with means are packages are pretty current. I'm on Linux 3.15.2 right now. Your call of course, but if your system is working I'd try to avoid doing a kernel upgrade if you can arrange that.

[ghost]

Hi Andrew,

Not sure I follow, you thinking 3.15.2 has WiFi issues?

What exactly are you guys doing and I can test it here in Slack?

I'm on 3.15.1, but I wanted to compile 3.15.2, let me know...

[ghost]

I was having issues with my wifi after recent kernel updates but had found that in my case it was rfkill that was required to unblock it. Check systemctl status to make sure you do not have conflicts with rfkill or services related that are either not running or giving errors. Do not always rely on journalctl ...

[andrew-bibb]

Thanks for the pointers on systemctl in lieu of journalctl. Up to now I've only been looking through the journal.

Moulei: I noticed the problem first after a kernel upgrade, but I don't actually know if that caused it or something else did. Was just giving a warning on the chance it was. The first upgrade that could possibly have caused (assuming it is kernel related) it was to 3.15.1 that hit the Arch repos on 6/17.

[ghost]

Ok on the kernel...

When clicking wifi on and off crashes too and the wifi and p2p buttons grey out...

Also tray icon many times still shows disconnected when connected.

[andrew-bibb]

You got me, what exactly are p2p buttons?

How many on/off clicks on wifi before the crash? I'm wondering if you picked up the same thing I've got on my main machine. I just, within the last half hour, built the most recent version of CMST here on github on my guest/testing partition (linux 3.13.8 and connman 1.22) and there I can click wifi on and off repeatedly with no problem. I don't even think of trying that on my main partition, it is getting frustrating.

[ghost]

24

[andrew-bibb]

WHooo WHoo back in business! Just completed my weekly system upgrade (new Linux kernel 3.15.5) and wireless works again.

[ghost]

Last couple of upgrades wireless has been flaky, opened up cmst and moved wireless up the list, reconnected and was good to go.... YAY!

On 13 July 2014 14:35, andrew-bibb notifications@github.com wrote:

WHooo WHoo back in business! Just completed my weekly system upgrade (new Linux kernel 3.15.5) and wireless works again.

— Reply to this email directly or view it on GitHub https://github.com/andrew-bibb/cmst/issues/4#issuecomment-48840735.

[ghost]

We're still replying to this thread? LOL...

[andrew-bibb]

You're right of course, we've sort of let this thread become a sort of bulletin board.

I think it is useful that we have a place like that, putting announcements in the front page readme is just me talking - how boring is that. For now I'll close this thread and think of what we can do. Maybe just a generic discussion thread for issues related to Connman and networking. Personally I found the feedback on the WiFi problems to be most helpful, but really had nothing to do with CMST.