| 2006-10-03 07:15:07 |
Thomas Wolfe |
bug |
|
|
added bug |
| 2006-10-20 07:00:21 |
Sebastian Dröge |
banshee: status |
Unconfirmed |
Needs Info |
|
| 2006-10-20 07:00:21 |
Sebastian Dröge |
banshee: statusexplanation |
|
Do you still have this with 0.11.1-0ubuntu2?
Can you please attach gdb to the running banshee process and provide a full backtrace?
gdb --pid `pidof banshee`
thread apply all bt |
|
| 2006-10-20 07:00:28 |
Sebastian Dröge |
banshee: importance |
Undecided |
High |
|
| 2006-10-20 07:00:28 |
Sebastian Dröge |
banshee: statusexplanation |
Do you still have this with 0.11.1-0ubuntu2?
Can you please attach gdb to the running banshee process and provide a full backtrace?
gdb --pid `pidof banshee`
thread apply all bt |
|
|
| 2006-10-20 10:52:38 |
Thomas Wolfe |
bug |
|
|
added attachment 'gdboutput' (outputgdb) |
| 2006-10-20 10:54:32 |
Thomas Wolfe |
bug |
|
|
added attachment 'gdboutput' (correctoutput) |
| 2006-10-20 11:37:23 |
Thomas Wolfe |
bug |
|
|
added attachment 'dboutput2' (outputtry2) |
| 2007-01-21 23:40:49 |
Sebastian Dröge |
banshee: status |
Needs Info |
Fix Released |
|
| 2007-01-21 23:40:49 |
Sebastian Dröge |
banshee: statusexplanation |
|
Ok, apperently this is fixed in feisty... closing this bug then :) |
|
