Opened 10 years ago

Closed 9 years ago

#1928 closed bug (Fixed)

Crash if column header is dragged under fluxbox WM

Reported by: cgreco Owned by: Cas
Priority: minor Milestone: 1.3.4
Component: Core Version: 1.3.2
Keywords: Cc: cristian@…, amarao@…

Description

bug forwarded from: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630908

If column header is moved deluge crash with following trace (at the end of letter).

Steps to reproduce:

  1. Use vnc4server, connect to it via vncviewer,
  2. Run fluxbox as WM
  3. run deluge with some torrents
  4. Try to move header of any column

This bug not appear with metacity WM.

Traceback:

File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 793, in runUntilCurrent

call.func(*call.args, call.kw)

File "/usr/lib/python2.6/dist-packages/deluge/core/torrentmanager.py", line 983, in on_alert_save_resume_data

torrent_id = str(alert.handle.info_hash())

exceptions.RuntimeError?: invalid torrent handle used The program 'deluge' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch? (invalid parameter attributes)'.

(Details: serial 3297019 error_code 8 request_code 56 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously;

that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

Change History (2)

comment:1 Changed 10 years ago by Cas

  • Component changed from gtkui to core
  • Milestone changed from Future to 1.3.4
  • Owner set to Cas
  • Status changed from new to accepted

It doesn't make sense why there is a libtorrent error resulting from moving a column, I wonder if it is just a coincidence.

I think the error can be prevented by moving the line 'torrent_id = str(alert.handle.info_hash())' into the try-except block below.

comment:2 Changed 9 years ago by Cas

  • Resolution set to fixed
  • Status changed from accepted to closed

Fix committed to 1.3-stable:f0c4a4c766

Note: See TracTickets for help on using tickets.