lp://staging/~ilkka/gwibber/gtk-find-icon-loading-fix

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp://staging/gwibber

gwibber-committers: Pending requested 2009-10-27

Diff: 23 lines

1 file modified

gwibber/gwui.py (+3/-3)

api

Rejected for merging into lp://staging/~gwibber-committers/gwibber/trunk.merge.backup

Ilkka Laukkanen (community): Disapprove on 2009-10-27

Colin Dean (community): Needs Resubmitting on 2009-10-27

gwibber-committers: Pending requested 2009-10-22

Diff: 266 lines

4 files modified

gwibber/client.py (+3/-0)
gwibber/gwui.py (+3/-3)
gwibber/microblog/laconica.py (+1/-1)
po/ru.po (+33/-23)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #427249: Crashes on start when trying to load gtk-find icon

Undecided

Fix Released

Link a bug report

Related blueprints

479. By Ilkka Laukkanen on 2009-10-27

Merged old gtk-find-icon-loading-fix after rebase on mainline r477

478. By Ilkka Laukkanen on 2009-09-10

Changed default "gtk-find" icon loading to use builtins and bypass
gwibber.resource.load().

477. By Alexander Sack on 2009-10-25

rename Laconi.ca to StatusNet (UI part) in laconica.py (thx @BUGabundo for testing) - lp:419817

476. By Ken VanDine on 2009-10-22

Serge Matveenko 2009-10-09 Update Russian translation

475. By Ken VanDine on 2009-10-22

* When we quit, shutdown the daemon
* Fixed status icon handling

474. By Ken VanDine on 2009-10-22

Fix to match digg API

473. By Alexander Sack on 2009-10-22

unbreak messages sorting caused by bad flickr time format; use ticks() everywhere

472. By Alexander Sack on 2009-10-22

fix gwibber not starting if font settings use a non-integer value for size (LP: #383759)
- patch by Krzysztof Klinikowski

471. By Alexander Sack on 2009-10-22

also make a lightweight/not-threaded OperationResultHandler

+ after this patch all not-blocking operations in gwibber are processed in glib
  main loop; this should reduce the multi-threading problem to the quite well
  confined OperationThread's run method.
+ use OperationResultHandler.process_opdata as glib idle handler for ops
  produced in OperationThread
+ drop all uses of output_queue
+ pass operation result handler to OperationManager constructor now that it
  schedules the proper callback directly
+ accordingly, do not start the Messages result handler in server.py's Microblog
  constructor; instead directly pass it to OperationManager constructor, which
  then will use it as a glib idle handler to run the code in mainloop thread

470. By Alexander Sack on 2009-10-21

make a lightweight OperationManager without a threaded scheduler
+ drop scheduler loop code (aka run)
+ make a source callback out of process_scheduled_operation
+ use glib.add_timeout_seconds to schedule operations
+ use glib.remove_source to unschedule operations
+ stop starting operationmanager thread in Microblog constructor