Growl redirecting notifications from another accounts
16 views
Skip to first unread message
Maciej Tarmas
Jan 27, 2012, 5:37:09 AM1/27/12
to Growl Discuss
I couldn't confirm this earlier due to Growl not working because of
the case-sensitive bug, but now I finally got Growl 1.3.3 running, so
I could check everything and confirm this.
I have two different user accounts - one for me, one for my wife. Most
of the time we are both logged in on our Mac.
Some time ago I've noticed that I'm getting notifications from
MenuWeather (http://menuweather.com/mac) coming from my wife's user
account. It was easy to tell by the language of the notifications,
because I have my account set to English, while my wife has hers set
to Polish.
I first suspected it was the fault of MenuWeather (which I highly
recommend, by the way), but checking the history of Growl
notifications it turns out that I'm also getting duplicate hardware
notifications from HardwareGrowler running on the other account.
After further investigation I discovered that it's the first launched
instance of Growl that is receiving all the notifications. When a
different user logs in to another account, all the notifications are
passed to the first account.
You can easily check this by setting two different user accounts and
enabling Growl (with history) and HardwareGrowler on both. Log in to
the accounts and plug a USB memory stick. You will get all the
notifications on the account that you logged in to first.
Both of the accounts are non-admin, if that makes any difference.
the case-sensitive bug, but now I finally got Growl 1.3.3 running, so
I could check everything and confirm this.
I have two different user accounts - one for me, one for my wife. Most
of the time we are both logged in on our Mac.
Some time ago I've noticed that I'm getting notifications from
MenuWeather (http://menuweather.com/mac) coming from my wife's user
account. It was easy to tell by the language of the notifications,
because I have my account set to English, while my wife has hers set
to Polish.
I first suspected it was the fault of MenuWeather (which I highly
recommend, by the way), but checking the history of Growl
notifications it turns out that I'm also getting duplicate hardware
notifications from HardwareGrowler running on the other account.
After further investigation I discovered that it's the first launched
instance of Growl that is receiving all the notifications. When a
different user logs in to another account, all the notifications are
passed to the first account.
You can easily check this by setting two different user accounts and
enabling Growl (with history) and HardwareGrowler on both. Log in to
the accounts and plug a USB memory stick. You will get all the
notifications on the account that you logged in to first.
Both of the accounts are non-admin, if that makes any difference.
Maciej Tarmas
Jan 27, 2012, 5:49:27 AM1/27/12
to Growl Discuss
Now if I log out from the first account, the second instance of Growl
seems to take over handling the notifications correctly, but as soon
as the first user (the one that has logged in first, than logged out)
logs back in, everything returns to the point where we started.
seems to take over handling the notifications correctly, but as soon
as the first user (the one that has logged in first, than logged out)
logs back in, everything returns to the point where we started.
Daniel Siemer
Jan 27, 2012, 10:24:22 AM1/27/12
to Growl Discuss
We are aware of this issue, and are working to find the best solution,
so that users with multi user environment have as seamless experience
as possible. The new method for talking to Growl, and our method
going forward is GNTP, which was designed as a (mainly) single port
protocol, and once the first user's Growl latches onto that port, the
other user's growl cant get it. Regardless of what we do in the core
Growl.app though, ultimately it will also take updates to the
framework, as even if we cut off Growl's sockets on the first user,
apps from the first user could conceivably than talk to Growl on the
second user's account. As another option, we could use a different
port for each user, but again, the framework would need updating to
support figuring out which port that user's Growl had registered on,
and that second user would be frustrated that none of his apps which
didn't have the updated framework would work properly (they would
still be talking to user 1).
This has been filed as http://code.google.com/p/growl/issues/detail?id=426,
and any further updates on its progress will be there.
so that users with multi user environment have as seamless experience
as possible. The new method for talking to Growl, and our method
going forward is GNTP, which was designed as a (mainly) single port
protocol, and once the first user's Growl latches onto that port, the
other user's growl cant get it. Regardless of what we do in the core
Growl.app though, ultimately it will also take updates to the
framework, as even if we cut off Growl's sockets on the first user,
apps from the first user could conceivably than talk to Growl on the
second user's account. As another option, we could use a different
port for each user, but again, the framework would need updating to
support figuring out which port that user's Growl had registered on,
and that second user would be frustrated that none of his apps which
didn't have the updated framework would work properly (they would
still be talking to user 1).
This has been filed as http://code.google.com/p/growl/issues/detail?id=426,
and any further updates on its progress will be there.
marrie
Jan 27, 2012, 8:26:33 PM1/27/12
to Growl Discuss
Nice. I just bought growl 1.3 from the app store yesterday. I sent a
message to this list at around 12 this afternoon but it looks like it
never got there.
I'm having problems but I'll just send a message from the site
instead.
Take care of yourself and be safe. and thanks for the heads up on the
bug.
Sarah Alawami
If you need editing done on a small narration project go to
http://music.marrie.org/audio_mastering for more info.
If you need to contact me my info is below.
website: http://music.marrie.org
Podcast: http://tffp.marrie.org/podcast
youtube: http://youtube.com/marrie125
On Jan 27, 7:24 am, Daniel Siemer <dan...@growl.info> wrote:
> We are aware of this issue, and are working to find the best solution,
> so that users with multi user environment have as seamless experience
> as possible. The new method for talking to Growl, and our method
> going forward is GNTP, which was designed as a (mainly) single port
> protocol, and once the first user's Growl latches onto that port, the
> other user's growl cant get it. Regardless of what we do in the core
> Growl.app though, ultimately it will also take updates to the
> framework, as even if we cut off Growl's sockets on the first user,
> apps from the first user could conceivably than talk to Growl on the
> second user's account. As another option, we could use a different
> port for each user, but again, the framework would need updating to
> support figuring out which port that user's Growl had registered on,
> and that second user would be frustrated that none of his apps which
> didn't have the updated framework would work properly (they would
> still be talking to user 1).
>
> This has been filed ashttp://code.google.com/p/growl/issues/detail?id=426,
message to this list at around 12 this afternoon but it looks like it
never got there.
I'm having problems but I'll just send a message from the site
instead.
Take care of yourself and be safe. and thanks for the heads up on the
bug.
Sarah Alawami
If you need editing done on a small narration project go to
http://music.marrie.org/audio_mastering for more info.
If you need to contact me my info is below.
website: http://music.marrie.org
Podcast: http://tffp.marrie.org/podcast
youtube: http://youtube.com/marrie125
On Jan 27, 7:24 am, Daniel Siemer <dan...@growl.info> wrote:
> We are aware of this issue, and are working to find the best solution,
> so that users with multi user environment have as seamless experience
> as possible. The new method for talking to Growl, and our method
> going forward is GNTP, which was designed as a (mainly) single port
> protocol, and once the first user's Growl latches onto that port, the
> other user's growl cant get it. Regardless of what we do in the core
> Growl.app though, ultimately it will also take updates to the
> framework, as even if we cut off Growl's sockets on the first user,
> apps from the first user could conceivably than talk to Growl on the
> second user's account. As another option, we could use a different
> port for each user, but again, the framework would need updating to
> support figuring out which port that user's Growl had registered on,
> and that second user would be frustrated that none of his apps which
> didn't have the updated framework would work properly (they would
> still be talking to user 1).
>
Maciej Tarmas
Jun 9, 2012, 4:28:38 AM6/9/12
to growld...@googlegroups.com
Is anyone working on this? The bug is still present in 1.4 :(
Guys, this is really a serious issue.
Guys, this is really a serious issue.
Daniel Siemer
Jun 9, 2012, 10:00:03 AM6/9/12
to growld...@googlegroups.com
If there are any updates on this issue, it will likely happen on the issue I linked. It was never slated for 1.4, and while its listed on 2.0 presently, there is a serious bug in the networking stack that will affect almost all users that needs to be resolved for or before 2.0. It is taking rewriting the networking stack to fix that one, and maybe after its done being rewritten, we can investigate this again.
Reply all
Reply to author
Forward
0 new messages