← Back to team overview

gwibber-bugs team mailing list archive

[Bug 777551] Re: Persistent non-responding status with system freeze

 

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:

* Is this reproducible now ?
* If so, what specific steps should we take to recreate this bug?

** Project changed: gwibber => gwibber (Ubuntu)

** Changed in: gwibber (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/777551

Title:
  Persistent non-responding status with system freeze

Status in “gwibber” package in Ubuntu:
  Incomplete

Bug description:
  **Problem: Gwibber becomes non-responding and freezes the whole system
  upon clicking a previously opened search/twitter user's page.

  **Environment:
  - Ubuntu Linux 10.10, Kernel 2.6.35-28-generic
  - Gwibber 3.1.0~bzr990-0ubuntu1~daily1~maverick
  - Gwibber-service-twitter 3.1.0~bzr990-0ubuntu1~daily1~maverick

  **How to reproduce:
  1-Launch Gwibber
  2-Open a couple of searches and twitter users' pages
  3-Restart Gwibber
  4-Try to view any of the previously opened searches/pages

  **Additional Notes:
  - Attached is the terminal log of the hang and killed by the user eventually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/777551/+subscriptions


References