[Bug 1556828] Re: Glade designer eating Cpu & Ram

2018-06-12 Thread Kalle Raiskila
This bug seems to have been fixed in upstream on 2017-06-13 (according to the link in comment #3). But testing that seems to require GTK+3.20. Perhaps it is time to upgrade to 18.04/bionic beaver... -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1556828] Re: Glade designer eating Cpu & Ram

2017-10-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glade (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556828 Title:

[Bug 1556828] Re: Glade designer eating Cpu & Ram

2016-07-30 Thread Matheus Saraiva
*...version 16.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556828 Title: Glade designer eating Cpu & Ram To manage notifications about this bug go to:

[Bug 1556828] Re: Glade designer eating Cpu & Ram

2016-07-30 Thread Matheus Saraiva
Are there any date predictions for correction? Or we will have to wait for version 10.16 with Glade 3:20? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556828 Title: Glade designer eating Cpu &

[Bug 1556828] Re: Glade designer eating Cpu & Ram

2016-03-14 Thread GreatDanton
I reported it here: https://bugzilla.gnome.org/show_bug.cgi?id=763624 ** Bug watch added: GNOME Bug Tracker #763624 https://bugzilla.gnome.org/show_bug.cgi?id=763624 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1556828] Re: Glade designer eating Cpu & Ram

2016-03-14 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at