Opened 9 years ago

Closed 9 years ago

Last modified 5 years ago

#2068 closed bug (Invalid)

Window crash when reorganize the table

Reported by: toniboni88 Owned by:
Priority: minor Milestone:
Component: GTK UI Version: 1.3.4
Keywords: Cc:

Description

I've Deluge 1.3.4 with Ubuntu 11.04. When I try riorganize the table (speed, ratio, peers, filename, ecc) the Gtkui closes by itself. When I get back and try to rearrange the table is closed again.

http://i43.tinypic.com/2ch45s1.jpg

Attachments (2)

2012-03-31_123244.png (4.1 KB) - added by toniboni88 9 years ago.
log_deluge.txt (15.2 KB) - added by toniboni88 9 years ago.

Download all attachments as: .zip

Change History (16)

Changed 9 years ago by toniboni88

comment:1 Changed 9 years ago by toniboni88

  • Milestone changed from 1.3.5 to Future
  • Version changed from other (please specify) to 1.3.4

comment:2 Changed 9 years ago by toniboni88

  • Milestone changed from Future to 1.3.5

comment:3 Changed 9 years ago by Cas

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.

Changed 9 years ago by toniboni88

comment:4 Changed 9 years ago by toniboni88

I've have attach a log file, also:

http://i40.tinypic.com/34sgx7o.jpg

comment:5 follow-up: Changed 9 years ago by Cas

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:6 Changed 9 years ago by toniboni88

http://i44.tinypic.com/20fce2d.jpg

comment:7 Changed 9 years ago by Cas

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:8 follow-up: Changed 9 years ago by toniboni88

How?

comment:9 in reply to: ↑ 8 Changed 9 years ago by Cas

Replying to toniboni88:

How?

How what?

comment:10 Changed 9 years ago by toniboni88

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 in reply to: ↑ 5 Changed 9 years ago by Cas

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 Changed 9 years ago by Cas

  • Milestone changed from 1.3.5 to 1.3.x
  • Status changed from new to pending

comment:14 Changed 9 years ago by Cas

  • Resolution set to invalid
  • Status changed from pending to closed

comment:15 Changed 5 years ago by Cas

  • Milestone 1.3.x deleted

Milestone deleted

Note: See TracTickets for help on using tickets.