Ticket #2068 (closed bug: invalid)

Opened 15 months ago

Last modified 8 months ago

Window crash when reorganize the table

Reported by: toniboni88 Owned by:
Priority: minor Milestone: 1.3.x
Component: gtkui 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

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

Change History

Changed 15 months ago by toniboni88

  Changed 15 months ago by toniboni88

  • version changed from other (please specify) to 1.3.4
  • milestone changed from 1.3.5 to Future

  Changed 15 months ago by toniboni88

  • milestone changed from Future to 1.3.5

  Changed 15 months 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 15 months ago by toniboni88

  Changed 15 months ago by toniboni88

I've have attach a log file, also:

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

follow-up: ↓ 11   Changed 15 months 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

  Changed 15 months ago by toniboni88

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

  Changed 15 months 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.

follow-up: ↓ 9   Changed 15 months ago by toniboni88

How?

in reply to: ↑ 8   Changed 15 months ago by Cas

Replying to toniboni88:

How?

How what?

  Changed 15 months 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?

in reply to: ↑ 5   Changed 15 months 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.

  Changed 15 months ago by Cas

  • status changed from new to pending
  • milestone changed from 1.3.5 to 1.3.x

  Changed 8 months ago by Cas

  • status changed from pending to closed
  • resolution set to invalid
Note: See TracTickets for help on using tickets.