[Desktop-packages] [Bug 921342] Re: crashed with SIGSEGV in gtk_widget_get_ancestor()gnome control center cra

2012-03-30 Thread Sebastien Bacher
closing since the submitter can reproduce @Jeremy: your issue is with the privacy capplet and another bug, please submit a new bug report ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages

[Desktop-packages] [Bug 921342] Re: crashed with SIGSEGV in gtk_widget_get_ancestor()gnome control center cra

2012-03-16 Thread Jeremy Lincicome
I can reproduce this bug with the latest updates on 12.04 64 bit. I noticed the crash when trying to change settings in the privacy dialog. 1. Go to System settings. 2. Click onn Privacy. 3. Try to make a change to the settings on the files tab. It might take several tries to cause a crash. The cr

[Desktop-packages] [Bug 921342] Re: crashed with SIGSEGV in gtk_widget_get_ancestor()gnome control center cra

2012-03-16 Thread Jeremy Lincicome
** Tags added: amd64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/921342 Title: crashed with SIGSEGV in gtk_widget_get_ancestor()gnome control center cra Status in “

[Desktop-packages] [Bug 921342] Re: crashed with SIGSEGV in gtk_widget_get_ancestor()gnome control center cra

2012-02-20 Thread Rob Whyte
Hi, seems to be resolved. can not re-produce now. Recommend closing this bug. Thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/921342 Title: crashed with SIGSEGV

[Desktop-packages] [Bug 921342] Re: crashed with SIGSEGV in gtk_widget_get_ancestor()gnome control center cra

2012-02-20 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Visibility changed to: Public ** Cha