Re: bug buddy configuration

2005-10-12 Thread Le Lain, Olivier 

Thanks for your quick answers.

Fernando,

Yes indeed , setting GNOME_DISABLE_CRASH_DIALOG is what I do.
I also know   you can't avoid some assistant window. But I wonder if 
there would be a lot of work to do to hack bug-buddy to send bt 
automatically. (I prefer having an opinion before diving in the code :-) )
I already did an awful hack to gnome_segv2 so that it uses a gcore/mail 
pipe instead of bug-buddy.
It worked fine until 2.6.12 kernel which (I dont know why) no more 
include symbols.


Glynn,

Is Sun's hack free ? :-)
I'm obviously very interested. (knowing that we are long time Sun 
customers !! :-) )



Cordialement / Cheers.

-Olivier
CNS



Fernando Herrera wrote:


Hi,

right now you can globally disable bug-buddy dialog setting globally
the env variable GNOME_DISABLE_CRASH_DIALOG (you can do in the system
profile, for example).

You could hack bugzillas xml file to set up another destination
addresses, but there is no way to skip all bug-buddy assistant pages.

Salu2


On 10/11/05, Le Lain, Olivier [EMAIL PROTECTED] wrote:
 


Hello,

I don't know if it's the right place but I didn't find any bug buddy ML.
I just have a little question about bug-buddy.
I'm an admin of around 50 gnome users and unfortunatly I prefer to
disable bug-buddy.Indeed, since they're working, they don't have time to
fill each bug buddy requests. It's far less annoying to have the
application simply restarting. (They don't even know they had a crash
most of the time).

But, I miss usefull informations which bug-buddy can bring.

So here is my question :
Is there an easy way to configure or rewrite some parts of the code (I
insist on easy since I'm an eternal C beginner:-) ), so that bug-buddy
(or gnome_segv2 ?) send automatically a email with the backtrace to a
specified email address (typically the admin one).

Then , I (the admin) could :

* know that a bug occured
* sort it
* check if and how  it's solved  on bugzilla
* eventually open a new bug.

Thank you !


--
Cordialement / Cheers.

-Olivier
CNS

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

   


___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

bug buddy configuration

2005-10-11 Thread Le Lain, Olivier 

Hello,

I don't know if it's the right place but I didn't find any bug buddy ML.
I just have a little question about bug-buddy.
I'm an admin of around 50 gnome users and unfortunatly I prefer to 
disable bug-buddy.Indeed, since they're working, they don't have time to 
fill each bug buddy requests. It's far less annoying to have the 
application simply restarting. (They don't even know they had a crash 
most of the time).


But, I miss usefull informations which bug-buddy can bring.

So here is my question :
Is there an easy way to configure or rewrite some parts of the code (I 
insist on easy since I'm an eternal C beginner:-) ), so that bug-buddy 
(or gnome_segv2 ?) send automatically a email with the backtrace to a 
specified email address (typically the admin one).


Then , I (the admin) could :

* know that a bug occured
* sort it
* check if and how  it's solved  on bugzilla
* eventually open a new bug.

Thank you !


--
Cordialement / Cheers.

-Olivier
CNS

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: bug buddy configuration

2005-10-11 Thread Glynn Foster 
Hey,

On Tue, 2005-10-11 at 14:44 +0200, Fernando Herrera wrote:
 Hi,
 
 right now you can globally disable bug-buddy dialog setting globally
 the env variable GNOME_DISABLE_CRASH_DIALOG (you can do in the system
 profile, for example).
 
 You could hack bugzillas xml file to set up another destination
 addresses, but there is no way to skip all bug-buddy assistant pages.

FWIW, this is actually a feature that we've hacked locally in Sun too -
although with upgrading to 2.10/2.12 we still have to rewrite the patch.

Basically, having customers automatically send bug reports to the
community would be a security concern which is unacceptable, but we're
still anxious to keep on top of stability problems in the desktop by
monitoring an internal alias of bug-buddy reports.


Glynn

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list