Deluge-gtk crashes upon connection/general protection fault

[graysky]

Working on a Arch Linux (deluge v 2.0.3), I have a headless deluged running via the systemd service (unprivileged deluge user). I connect to this box on a separate box also running Arch via the gtk client, but more very frequently, as soon as I connect to the daemon, the entire deluge-gtk crashes. I see a corresponding entry in dmesg like this:

Code: Select all

[Oct 6 11:57] traps: deluge-gtk[30690] general protection fault ip:7f54e1c526f5 sp:7ffda5d97298 error:0 in libc-2.30.so[7f54e1b16000+14d000]

If I stop the daemon or if I do not connect to it, deluge-gtk sits for hours without a problem. Wondering next steps in troubleshooting. Thanks!

[mhertz]

First step is gathering debug-logs for further troubleshooting, probably by other more knowledge people than me (e.g in python coding etc...)

To be sure to catch everything, probably a debug-log of both the daemon and client would be preferred.

For the client simply add '-L debug - l deluge-gtk.log'.

Now for the daemon on other machine, make new dir and file: '/etc/systemd/system/deluged.service.d/override.conf'.

Code: Select all

 
[Service]
ExecStart=
ExecStart=/usr/bin/deluged -L debug -l /var/log/deluged.log

Afterwards run: 'sudo systemctl daemon-reload'

Now do a test-run and inspect/gather the two logs and post relevant parts here or make new bug-ticket.

After testing/gathering-logs, then delete the dir and override.conf previously made and run again 'sudo systemctl daemon-reload'.

[graysky]

Thanks for the tips... I captured a debug log for each when the core dump takes place.

Ticket #3307 has been created.

...
Now for the daemon on other machine, make new dir and file: '/etc/systemd/system/deluged.service.d/override.conf'.

Code: Select all

 
[Service]
ExecStart=
ExecStart=/usr/bin/deluged -L debug -l /var/log/deluged.log

Afterwards run: 'sudo systemctl daemon-reload'

As an FYI, you can do this is an edit command/no need to manually create or delete override.conf:

Code: Select all

# systemctl edit deluged

[mhertz]

Thanks for the tip mate, nice one Just for that test I guess I instead just could have suggested running 'sudo -u deluge deluged - L debug -l deluged.log', as this usually isn't a systemd issue, but just in case.

Thanks for reporting ticket so we hopefully can get the issue fixed.