Re: [growl-discuss] HardwareGrowler 2.0 No Network Notifications.

[Christopher Forsythe]

Obviously we want it to notify about network changes. :) So when you launch HardwareGrowler does it notify at all?

The Growl positioning bug is resolved in Growl 2.0.1, which is submitted to Apple. There is a workaround that Daniel has posted to this list a few times, here it is:

The work workaround til 2.0.1 is released is to set the
display preference to the empty string in our preferences file, either
using the file directly and changing the key GrowlDisplayPluginName to
an empty entry, or the defaults command (in Terminal: defaults write
com.Growl.GrowlHelperApp GrowlDisplayPluginName "").

-- 
Chris Forsythe

@The_Tick

On Nov 22, 2012, at 12:09 PM, Mark Foster <foste...@gmail.com> wrote:

HardwareGrowler 2.0 does not notify of any network changes... at all. The old version worked perfectly. Bug?

Also, Growl 2.0 insists on using the top-right of the screen for starting position regardless of preference settings. Bug?

MacBook Pro (Late 2006) OS X 10.7.5, Growl 2.0.

Any help appreciated, I would really like the network notifications back.

Thank you.

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/06J74AFm-AIJ.
To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

[Daniel Siemer]

Actually, the workaround for positioning in the other locations not
working in Growl 2 is to modify setting(s) on the display
configuration you are using and want in a different location
(duration, opacity, color, that kind of thing).

On Nov 22, 9:36 pm, Christopher Forsythe <ch...@growl.info> wrote:
> Obviously we want it to notify about network changes. :) So when you launch HardwareGrowler does it notify at all?
>
> The Growl positioning bug is resolved in Growl 2.0.1, which is submitted to Apple. There is a workaround that Daniel has posted to this list a few times, here it is:
>
> The work workaround til 2.0.1 is released is to set the
> display preference to the empty string in our preferences file, either
> using the file directly and changing the key GrowlDisplayPluginName to
> an empty entry, or the defaults command (in Terminal: defaults write
> com.Growl.GrowlHelperApp GrowlDisplayPluginName "").
>
> --
> Chris Forsythe
> @The_Tick
>

> On Nov 22, 2012, at 12:09 PM, Mark Foster <fosterma...@gmail.com> wrote:
>
>
>
>
>
>
>
> > HardwareGrowler 2.0 does not notify of any network changes... at all. The old version worked perfectly. Bug?
>
> > Also, Growl 2.0 insists on using the top-right of the screen for starting position regardless of preference settings. Bug?
>
> > MacBook Pro (Late 2006) OS X 10.7.5, Growl 2.0.
>
> > Any help appreciated, I would really like the network notifications back.
>
> > Thank you.
>
> > --
> > You received this message because you are subscribed to the Google Groups "Growl Discuss" group.

> > To view this discussion on the web visithttps://groups.google.com/d/msg/growldiscuss/-/06J74AFm-AIJ.

[Mark Foster]

I am seeing the same problem on my other machine running OSX 10.8.2, Growl 2.0 and HWG 2.0. No network notifications.

On both machines I can switch locations, enable/disable interfaces, plug and unplug ethernet cables and HWG remains completely silent. Other aspects of HWG seem to work OK: USB insert/remove, Volume mount/dismount, keyboard monitor, Firewire monitor. Power monitor works OK on the laptop. It is just the network monitor that seems to be "broken".

Ironically, that is the one monitor that I really use the most because I switch network connections a lot and need to see the changes take effect.

[Mark Foster]

Sorry, I forgot to answer your question.

The answer is no. HWG does not display any notifications at all on launch.

On Friday, November 23, 2012 3:36:20 AM UTC, Christopher Forsythe wrote:

[Thierry Di Lenarda]

Ok, I updated as well this morning, and have no more network status updates with HWG 2.0

I also noticed that HWG was sending notifications to Growl which passed them to NC AND to the NC as well.

I wanted to use NC as much as possible to keep the original app icon into the notification, so I went to Growl's preferences and de-activated HWG, as it was activated directly in the NC system preferences (and Dropbox, VLC, Twitter, Transmission, gfxCardStatus, etc...) Each one allows both the NC or Growl, so tons of duplicate notifications...

[Daniel Siemer]

Notifications for HardwareGrowler on launch are controlled by an
option in HardwareGrowler's preferences pane: Show Connected Devices
on Launch. On just about every mac out there, if you have all of the
main modules enabled, you should get lots of notifications about
current mounted drives, USB devices (including busses and things like
isight cameras), and IP Address, and current network status.

I get network notifications fine for link up/down, airport connect and
disconnect. Can you make sure that the module is enabled in HWG's
preferences, as well as check the event types in Growl under HWG's
application settings: Airport Connected, Airport Disconnected, IP
Address Changed, Network Link Up, Network Link Down. These should all
be on by default, but I just want to be sure something weird but
simple to fix didn't happen.

As for NC and Growl both displaying, if the big NC switch in Growl's
general tab is on, HWG will send to both Growl, and NC, however Growl
disables its visual displays, and knows that HWG has already sent to
NC. It should not be sending to NC twice. If you are using the Bark
plugin to send to NC, there is a known issue in Growl 2.0 with setting
it to not use a visual display (and is fixed for Growl 2.0.1, which is
waiting review at Apple), and can be fixed by the command line
workaround that Chris posted above
defaults write com.Growl.GrowlHelperApp GrowlDisplayPluginName ""

On Nov 23, 4:56 am, Thierry Di Lenarda <thierry.dilena...@gmail.com>
wrote:

[Rudy Richter]

This has been filed as http://code.google.com/p/growl/issues/detail?id=561 if you want to star it to be notified of its resolution.

[Rudy Richter]

Things to check:

1. Is the Network monitor module disabled in hardware growler's preferences window

2. Are the airport, network link up/down and ip address changed notifications disabled or otherwise set to an incorrect display style in Growl.app's application entry for HardwareGrowler?

3. the output of running ifconfig -a in terminal (you can obscure the actual ip addresses in the output as that isn't needed)

-rudy 

[Mark Foster]

Daniel, Rudy,

"Show Connected Devices at Launch" is off. Turning it on and relaunching HWG does show a whole bunch of alerts, including one for the IP address. Leaving it on has no effect on the lack of notifications when switching networks, connecting or disconnecting.

The Network Monitor is enabled in HWG preferences. The only one disabled is the keyboard monitor.

All notification preferences are set to their default values except for the display style which is "Bubbles". Changing this to a different style does not help.

As requested, output of ifconfig -a (hw addrs anonymised, IP addrs NAT anyway):

pointyheed:~ markf$ ifconfig -a

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384

options=3<RXCSUM,TXCSUM>

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 

inet 127.0.0.1 netmask 0xff000000 

inet6 ::1 prefixlen 128 

gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280

stf0: flags=0<> mtu 1280

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>

ether 00:1b:xx:xx:xx:xx 

media: autoselect

status: inactive

fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 2030

lladdr 00:19:e3:ff:xx:xx:xx:xx 

media: autoselect <full-duplex>

status: inactive

en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether 00:17:xx:xx:xx:xx 

inet6 fe80::217:xxxx:xxxx:xxxx%en1 prefixlen 64 scopeid 0x6 

inet 172.16.0.4 netmask 0xffffff00 broadcast 172.16.0.255

media: autoselect

status: active

As mentioned: this all worked perfectly in the previous version.

[Thierry Di Lenarda]

1. Yes ! Screenshot HWG

2. No to both. Growl_xxx screenshots

3. See sceenshot. IPs and MAC adresses have been masked.

The only difference between yesterday and today is the HWG update from 1.3 to 2.0. I never touched any preference, and I always use the Smoke style for all my notifications. And since Growl 2, I always ask to pass everything to the NC.

[Rudy Richter]

that all looks ok, is anything logged to console.app when you perform the actions you feel should be presenting you with notifications? (the reason we're stepping through these hoops is because I'm running the app store build and i get notifications when i wake my computer from sleep as it reestablishes its wifi connection, if i turn wifi off/on, if i change locations in the network prefpane, etc)

so any information you can think of that might make your configuration different would be helpful.

it might also be helpful if you could detail step by step what you're doing when it should be firing a notification, maybe something in your steps will hint at where the problem lies.

-rudy

[Mark Foster]

Nothing out of the ordinary in the console. The log for a network state change looks remarkably the same whether growl is running or not.

I cannot think of anything that makes this MacBook Pro different to your machine any more than it is different to the Mac Pro on my desk at work or the machines of the other people reporting the problem. Mine are both different hardware, different OS versions, different network connection (wi-fi vs eth). The similarity is that they both run Growl 2.0 and HWG 2.0. Both worked up to the point that HWG was updated via the App store.

(Side Note: The App Store model of software downloads means that I cannot revert to the previous, working, version. This is a bad thing. The old way was better.)

On the laptop I would normally expect to see notifications as it joins the network on wake from sleep. I see nothing. The only time I see anything network related is on HWG app startup and only then if the preference is ticked to show connected devices at launch. At that time only do I see a notification about Airport Connected and IP address updated.

On the desktop I would expect to see notifications when switching locations, i.e. switching interface priority so that I can use a different IP address. I would also expect to see notifications when plugging or unplugging interface cables. Again, I see nothing.

I don't really know what else to say. What worked in the previous version does not work now.

[Mark Foster]

Some new information:

Today I used a Huawei Mobile Broadband Stick and, as expected, the USB insert was detected and notified normally. Then followed two network notifications:

Airport Disconnected

(null)

IP Address Updated

No Routable IP Addresses.

 Note: Airport was already disconnected and I got no message. Turning Airport back on, it joins fine but I don't see the Notification until I drop the USB modem connection.

[Christopher Forsythe]

Rudy has a fix he's working on, at this point we don't need anymore "me too" style replies like this one. Thanks for the feedback everyone. :)

Chris

On Tue, Nov 27, 2012 at 4:29 PM, Nathan C <chamber...@gmail.com> wrote:

Same problem here on 10.8.2 Late 2010 MBAir.  No network notifications after installing 2.0.  Worked perfectly before.  All checked except keyboard.  Notifications at startup checked.

On Thursday, November 22, 2012 1:09:36 PM UTC-5, Mark Foster wrote:

HardwareGrowler 2.0 does not notify of any network changes... at all. The old version worked perfectly. Bug?

Also, Growl 2.0 insists on using the top-right of the screen for starting position regardless of preference settings. Bug?

MacBook Pro (Late 2006) OS X 10.7.5, Growl 2.0.

Any help appreciated, I would really like the network notifications back.

Thank you.

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.

To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/CmnkfUoSZfsJ.

To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

--
Chris Forsythe

@The_Tick

[Nat Chamberlain]

Pardon my ignorance.  If it was "tested thoroughly" I would not have needed to send it.

Nat

[Christopher Forsythe]

I wasn't commenting on your ignorance, I was commenting so that anyone else after that would see it and not need to respond. Especially since earlier in this same thread Rudy linked to a ticket made for this specific issue, that says we already have a fix going. Just like I said here. Point blank there was no need for your snark here. Do not reply here in this manner again. We're happy to help, but not be abused.

We tested and had a large amount of people test it. The problem only affects certain models, and does not affect other models. We're already working on it, have found the problem, are working on a fix, and will be testing that. Point blank all software is going to have some kind of problems, and there is no way to test for every single scenario, that's just how it is.

Chris

--
Chris Forsythe

@The_Tick

[Christopher Forsythe]

Growl and HardwareGrowler are both updated, please let us know if these issues are not addressed.

Chris

On Thu, Nov 22, 2012 at 12:09 PM, Mark Foster <foste...@gmail.com> wrote:

HardwareGrowler 2.0 does not notify of any network changes... at all. The old version worked perfectly. Bug?

Also, Growl 2.0 insists on using the top-right of the screen for starting position regardless of preference settings. Bug?

MacBook Pro (Late 2006) OS X 10.7.5, Growl 2.0.

Any help appreciated, I would really like the network notifications back.

Thank you.

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.

To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/06J74AFm-AIJ.

To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

--
Chris Forsythe

@The_Tick