[Ubuntu Wiki] Update of "DebuggingGwibber" by kamus

Ubuntu Wiki noreply at ubuntu.com
Mon Nov 8 20:57:03 UTC 2010


Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The following page has been changed by kamus:
http://wiki.ubuntu.com/DebuggingGwibber?action=diff&rev1=1&rev2=2

------------------------------------------------------------------------------
  
  = Introduction =
  
- Bugs relating to gwibber...
+ Bugs related to gwibber and gwibber-service package
  
  
  = How to file =
  
- Useful for bug-filers and as a boiler-plate advice for triagers.  This is the minimum information required for a bug report.
+ Todo...
  
  = Bug tags =
  
- Bug tags specific to the package or area should be included here for reporters so they can tag their bug report.  It will also be useful for triagers.  The Bugs/Tags wiki page should then be modified to include these tags.
+ Todo...
  
  = Debugging procedure =
  
- In depth debugging procedures for this particular package or subsystem.  This usually is information about the log files to gather and what to look for in them.
+ run in a terminal:
+ 
+ $pkill gwibber-service & gwibber-service -d -o
+ $gwibber --debug
  
  = How to Triage =
  
- Information that will facilitate the triaging of bugs for this package or subsystem.  Remind triagers of the bug tags in use for this particular package.
+ Todo...
  
- == Stock Reply ==
+ == Stock Replies ==
  
- A stock reply to be used for initial bug reports basically asking for the stuff in "How to file".  The Bugs/Responses page should include this reply.
+ '''Gwibber Crashes'''
+ 
+ @Username, Please could you run under latest version of gwibber: gwibber --debug > gwibber-debug.txt and attach resulted output of this file to your report (following your steps to reproduce this issue), Thanks!
+ 
+ '''Gwibber-Service Issues'''
+ 
+ @Username, Please could you run under latest version of gwibber: gwibber-service -d -o and attach all resulted output to a textfile (following your steps to reproduce this issue), Thanks!
+ 
+ '''Try to reproduce it with PPA release'''
+ 
+ Please could you try to reproduce this issue in latest version of gwibber daily ppa (you can get from https://launchpad.net/~gwibber-daily/+archive/ppa) and check if this problem is still affecting you? Thanks in advance!
  
  == How to Forward ==
  
- In the event that the package or subsystem has an upstream bug tracker this section should contain detailed steps to forward a bug to that tracker.  Some packages may just link to the general "How to Forward" page for another bug tracker like Gnome's bugzilla or freedesktop.org's bug tracker.
+ Todo...
  
  = Known bugs =
  
  Description of known bug reports that may receive duplicates and how to recognise them.  This information should be obtained by looking for bugs tagged as 'metabug'. 
  
- '''Open'''
+ '''The Hotest'''
  ||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' ||
- || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... ||
+ || [[https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/614742|614742]] || Facebook problems || Problems related to Facebook authentication and stuffs ||
  
- '''Closed'''
- ||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' ||
- || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... ||
  
- = Non-bugs =
  
- How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses.
+ = Work Arounds =
+ 
+ Some basic procedures to fix some common troubles:
+ 
+ '''Gwibber can't start (using CouchDB as backend >=2.30.x releases)'''
+ 
+ rm -fr ~/.cache/desktop-couch ~/.config/desktop-couch and ~/.local/share/desktop-couch and then start gwibber again. 
+ 
+ '''Avatars not loaded correctly'''
+ 
+ rm -fr ~/.cache/gwibber/avatars/*
+ 
  
  ----
  CategoryBugSquad




More information about the Ubuntu-bugsquad mailing list