Attachments (2)
Change History (16)
by , 14 years ago
| Attachment: | 2012-03-31_123244.png added |
|---|
comment:1 by , 14 years ago
| Milestone: | 1.3.5 → Future |
|---|---|
| Version: | other (please specify) → 1.3.4 |
comment:2 by , 14 years ago
| Milestone: | Future → 1.3.5 |
|---|
comment:3 by , 14 years ago
by , 14 years ago
| Attachment: | log_deluge.txt added |
|---|
follow-up: 11 comment:5 by , 14 years ago
I'm afraid that's an issue outwith Deluge.
To narrow down the issue you need to install gdb and then run deluge with it:
gdb --args python /usr/bin/deluge (gdb) run #after crash (gdb) bt
comment:7 by , 14 years ago
You need to execute backtrace or bt to get the actual backtrace in gdb after the crash has occurred.
Also you should be able to select the console text so you can copy and paste it here rather than taking a screenshot.
comment:10 by , 14 years ago
You need to execute backtrace or bt to get the actual backtrace in gdb after the crash has occurred.
How can I do?
comment:11 by , 14 years ago
As I explained before:
(gdb) run #after the crash (while still in gdb) (gdb) bt
However based upon a similar reported issue in the forum there will probably be no stack to view. The only suggestion is to make sure your Ubuntu is fully updated and possibly try a newer video driver. Failing that it would need to be reported to Ubuntu's bug tracker.
comment:13 by , 14 years ago
| Milestone: | 1.3.5 → 1.3.x |
|---|---|
| Status: | new → pending |
comment:14 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | pending → closed |






can you enable debug logging for the gtkui to see if it reports an error however it could be something that requires a backtrace with gdb.