Opened 7 years ago

Closed 7 years ago

Last modified 2 years ago

#3124 closed bug (Fixed)

deluge-gtk crash when connected to remote server

Reported by: kmr2319 Owned by: Calum
Priority: major Milestone: Future
Component: GTK UI Version: 1.3.15
Keywords: Cc:


Deluge Server: 1.3.15 (running on an Asus Tinkerboard - ARMBIAN 5.34.171023 nightly Ubuntu 16.04.3 LTS 4.13.9-rockchip) LibTorrent: libtorrent-rasterbar8 1.0.11-1

Deluge Client: 1.3.15 (Lubuntu 17.10, but happened on 17.04 as well - x86_64)

The GTK UI crashes on occasion when connected to a remote server. Seems to be random. I haven't narrowed down a paricular action that causes this. Sometimes the UI is minimized to the tray and it has crashed when I check in on things...

Traceback from a /var/crash/*deluge-gtk.crash file (I can provide that in full if you think that will be useful):

Traceback (most recent call last):

File "/usr/lib/python2.7/dist-packages/deluge/ui/gtkui/", line 261, in stabilized

result = sort_func(model, iter1, iter2, data)

File "/usr/lib/python2.7/dist-packages/deluge/ui/gtkui/", line 186, in str_nocase_sort

return strcoll(v1, v2)

TypeError: coercing to Unicode: need string or buffer, NoneType found

I've attempted to start deluge-gtk in trace mode with the following command: /usr/bin/deluge-gtk -L trace -l /home/user/deluge-gtk.log OR /usr/bin/deluge-gtk --loglevel=trace --logfile=/home/user/deluge-gtk.log

But the log file was 0 bytes.

Locale (LANG) on both the client and server are: en_US.UTF-8

Client and server are sitting next to each other connected via a gigabit switch. Server is running OVPN for external access. Server is headless and running nothing else by the OS and deluged.

Storage physically resides on the client system. Server NFS mounts to the client for storage. mount points were created so that both client and server have the same tree: /mnt/data/blah/blah/blah...

Let me know if you require any further info. Thanks in advance!

Change History (4)

comment:1 by Calum, 7 years ago

Milestone: needs verified1.3.16
Owner: set to Calum
Priority: minormajor
Status: newassigned

There is no trace level for logs:

It seems my fix in #2957 wasn't quite enough. It is a tricky one to replicate so thanks for reporting and I can see how to fix it.

comment:2 by Calum, 7 years ago

Resolution: Fixed
Status: assignedclosed

Properly fixed this time: [396417bcd04]

comment:3 by kmr2319, 7 years ago

Fantastic! Thanks for the quick fix! I installed from source and will keep an eye on things. If I encounter any problems, I'll run it in a proper debug level (already confirmed, logging works when using the correct syntax) and open a new ticket.

comment:4 by Calum, 2 years ago

Milestone: 1.3.16Future

Ticket retargeted after milestone deleted

Note: See TracTickets for help on using tickets.