Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
**
Sorry for the delay, the problem was solved with the new version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/763970
Title:
gwibber crashed with SIGSEGV in
Closed then, thanks.
** Changed in: gwibber (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/763970
Title:
gwibber crashed with SIGSEGV in
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/763970
Title:
gwibber crashed with SIGSEGV in
gdk_window_enable_synchronized_configure()
--
ubuntu-bugs mailing
