DebuggingBanshee
|
Size: 2283
Comment:
|
← Revision 10 as of 2013-02-25 00:42:36 ⇥
Size: 2655
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| 2. Debugging latest release from daily ppa repository, url is at https://launchpad.net/~banshee-team/+archive/banshee-daily 3. Hardware not detected and further information at http://live.gnome.org/Banshee/LibgpodTransition |
1. Debugging latest release from daily ppa repository, url is at https://launchpad.net/~banshee-team/+archive/banshee-daily 1. Hardware not detected and further information at http://live.gnome.org/Banshee/LibgpodTransition or http://banshee.fm/support/faq/ 1. If the issue is an intermittent crash, create a file called ~/.config/banshee-1/always-debug, then the next time banshee crashes, copy out ~/.config/banshee-1/log and upload it. |
| Line 16: | Line 17: |
| = How to Triage = | = How to Triage Issues related to UbuntuOne extension = |
| Line 18: | Line 19: |
| 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. | If you are facing troubles while you are trying to sync your files from UbuntuOne store (7digital) all those reports should be reassigned to '''libubuntuone''' package instead banshee <<BR>> For support issues, you can tell people to ask on https://one.ubuntu.com/support/contact/ as well, if you like so for "i paid for stuff, and am not getting it" complaints, you can send people there for the real support channel |
| Line 22: | Line 29: |
| 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. | In case report doesn't have banshee log file or the user were not using apport 1) Please could you run in a terminal "banshee --debug" and attach all the output information as a separated file (while you are trying to reproduce this issue)? 2) Attach "~/.config/banshee-1/log" file into his report |
| Line 26: | Line 37: |
| 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. | You must file a new report at Gnome Bugzilla for product = "Banshee" or click on https://bugzilla.gnome.org/enter_bug.cgi?product=banshee to jump directly |
| Line 30: | Line 42: |
| 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'. | '''Common Issues''' ||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' || || [[https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/781824|781824]] || Pressing on the "Subscribe" button to download my purchased music didn't work || Banshee U1-extension problem || |
| Line 32: | Line 46: |
| '''Open''' ||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' || || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... || |
|
| Line 36: | Line 47: |
| '''Closed''' ||<rowbgcolor="#eeeeee"> '''Bug''' || '''Subject''' || '''Symptom''' || || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... || |
|
| Line 40: | Line 48: |
| = Non-bugs = | = Workarounds = |
| Line 42: | Line 50: |
| 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. | '''Database Corrupted''' if your logfile has texts like: "Sqlite error 11: database disk image is malformed" run in a terminal: $ cd ~/.config/banshee-1 $ sqlite3 banshee.db ".dump" > dump $ mv banshee.db banshee.db.backup $ cat dump | sqlite3 banshee.db |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Contents |
How to file
Please fill all your bugs using "ubuntu-bug banshee" or from banshee menu.
Debugging procedure
- Debugging Banshee from a terminal, please run "banshee --debug" and attach all output information
Debugging latest release from daily ppa repository, url is at https://launchpad.net/~banshee-team/+archive/banshee-daily
Hardware not detected and further information at http://live.gnome.org/Banshee/LibgpodTransition or http://banshee.fm/support/faq/
- If the issue is an intermittent crash, create a file called ~/.config/banshee-1/always-debug, then the next time banshee crashes, copy out ~/.config/banshee-1/log and upload it.
How to Triage Issues related to UbuntuOne extension
If you are facing troubles while you are trying to sync your files from UbuntuOne store (7digital) all those reports should be reassigned to libubuntuone package instead banshee
For support issues, you can tell people to ask on https://one.ubuntu.com/support/contact/ as well, if you like so for "i paid for stuff, and am not getting it" complaints, you can send people there for the real support channel
Stock Reply
In case report doesn't have banshee log file or the user were not using apport
1) Please could you run in a terminal "banshee --debug" and attach all the output information as a separated file (while you are trying to reproduce this issue)?
2) Attach "~/.config/banshee-1/log" file into his report
How to Forward
You must file a new report at Gnome Bugzilla for product = "Banshee" or click on https://bugzilla.gnome.org/enter_bug.cgi?product=banshee to jump directly
Known bugs
Common Issues
Bug |
Subject |
Symptom |
Pressing on the "Subscribe" button to download my purchased music didn't work |
Banshee U1-extension problem |
Workarounds
Database Corrupted if your logfile has texts like: "Sqlite error 11: database disk image is malformed"
run in a terminal:
$ cd ~/.config/banshee-1 $ sqlite3 banshee.db ".dump" > dump $ mv banshee.db banshee.db.backup $ cat dump | sqlite3 banshee.db
DebuggingBanshee (last edited 2013-02-25 00:42:36 by c-76-25-23-72)