public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Gmail <patnjer12@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Disable Notify Bubble?
Date: Sun, 11 May 2008 16:04:19 -0400	[thread overview]
Message-ID: <1210536259.581.7.camel@richard-desktop> (raw)
In-Reply-To: <1210525996.16390.12.camel@violet.holtmann.net>

lol
i do understand this.. it is wrong and i wish i could find a valid fix
for it.  but, no body seems to be able to do this.  before this code i
had to use my wired keyboard and type in sudo /etc/init.d/bluetooth
restart myself.  which is actually the only "fix" known - i.e. everyone
with this keyboard has to just that to use it.... there is no other fix
that i've found. so restarting it every 30 minutes myself, or having the
comp do it every 1 minute automatically... i'm happy with this for
now...

so, but yeah, until we find a cure, can someone just give me some cold
medicine and tell me how to get rid of that notify bubble?  i'm thinking
it is native to ubuntu though, as even with the bluetooth icon turned
off, i now get the bubble at another location of the screen...

On Sun, 2008-05-11 at 19:13 +0200, Marcel Holtmann wrote:
> Hi,
> 
> > sudo crontab -e
> > 
> > then
> > 
> > * * * * * val=`hciconfig -a 2>/dev/null | head -c 1`; [ -z $val ]
> > && /etc/init.d/bluetooth restart
> > 
> > then exit and save
> 
> don't give people ideas. This is wrong. It is simply plain wrong and you
> have no clue what it is actually doing. This script only treats symptoms
> and not the problem. Actually that this works for you is simply pure
> luck.
> 
> Regards
> 
> Marcel
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-05-11 20:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 13:22 [Bluez-users] Disable Notify Bubble? Gmail
2008-05-09 12:38 ` Marcel Holtmann
2008-05-09 21:34   ` RC
2008-05-11 13:30     ` Johannes Luber
2008-05-11 16:01       ` Gmail
2008-05-11 17:13         ` Marcel Holtmann
2008-05-11 20:04           ` Gmail [this message]
2008-05-11 22:48             ` Marcel Holtmann
2008-05-12 11:13             ` Micha
2008-05-11 20:05           ` Dick
2008-05-11 22:47             ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1210536259.581.7.camel@richard-desktop \
    --to=patnjer12@gmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox