Deluge does not start after force-rebooting (Xubuntu 13.04)

General support for problems installing or using Deluge
Post Reply
Gianfranco Nerdi
New User
New User
Posts: 2
Joined: Sun Oct 13, 2013 8:00 pm

Deluge does not start after force-rebooting (Xubuntu 13.04)

Post by Gianfranco Nerdi »

After installing and running Conky Manager, I had to force-reboot using the sudo reboot command while Deluge was still running because the panel had disappeared making the DE almost unusable; however, after rebooting I could no longer start the application. I ran Deluge via terminal, and the message I got was something about the program not being able to acquire a lock; I deleted the two files in the /home/.config/deluge/ipc directory (just as somebody else suggested), and the program worked until I rebooted. Now I can no longer launch the program either using the shortcut I have assigned to it or the panel launcher...neither have I been able to launch it using the applications menu; launching it from the terminal, gives the following message:
Traceback (most recent call last):

Code: Select all

 File "/usr/bin/deluge", line 9, in <module>
    load_entry_point('deluge==1.3.6', 'gui_scripts', 'deluge')()
  File "/usr/lib/python2.7/dist-packages/deluge/main.py", line 132, in start_ui
    UI(options, args, options.args)
  File "/usr/lib/python2.7/dist-packages/deluge/ui/ui.py", line 150, in __init__
    ui = GtkUI(args)
  File "/usr/lib/python2.7/dist-packages/deluge/ui/gtkui/gtkui.py", line 225, in __init__
    self.ipcinterface = IPCInterface(args)
  File "/usr/lib/python2.7/dist-packages/deluge/ui/gtkui/ipcinterface.py", line 142, in __init__
    reactor.listenUNIX(socket, self.factory, wantPID=True)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/posixbase.py", line 413, in listenUNIX
    p.startListening()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/unix.py", line 273, in startListening
    if not self.lockFile.lock():
  File "/usr/lib/python2.7/dist-packages/twisted/python/lockfile.py", line 127, in lock
    symlink(str(os.getpid()), self.name)
OSError: [Errno 13] Permission denied
However, when I use sudo deluge to launch the application, it does work and start as it normally would.
It also refuses to add a torrent when I double-click on the torrent file or use the context (right click) menu to select the application, even if it's already running.
Is there a way to solve this problem, preferably without having to reinstall the program or use the terminal every time? Because now I have a totally useless panel launcher and cannot launch it from the menu or using the keyboard shortcut.
Update: Now even sudo deluge does not work. Here is what I get when I type the command:

Code: Select all

[ERROR   ] 21:34:05 ipcinterface:156 Deluge restart failed: Couldn't listen on any:/home/arcturus/.config/deluge/ipc/deluge-gtk: Cannot acquire lock.
Cas
Top Bloke
Top Bloke
Posts: 3681
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: Deluge does not start after force-rebooting (Xubuntu 13.

Post by Cas »

You have a permission issue with the deluge config, trying deleting the ipc directory
Gianfranco Nerdi
New User
New User
Posts: 2
Joined: Sun Oct 13, 2013 8:00 pm

Re: Deluge does not start after force-rebooting (Xubuntu 13.

Post by Gianfranco Nerdi »

I managed to delete the ipc directory by launching Thunar as root; while this does allow Deluge to be launched via terminal again, I still cannot launch it by clicking on the panel launcher or by using the app menu, and right clicking (or double-clicking) on a torrent still does not work.
P.S. Oh, and by the way, I use the 64-bit version of Xubuntu 13.04.
Cas
Top Bloke
Top Bloke
Posts: 3681
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: Deluge does not start after force-rebooting (Xubuntu 13.

Post by Cas »

I have no idea what is broken on your system, maybe try reinstalling deluge
Sentinel
Member
Member
Posts: 21
Joined: Sun Oct 26, 2008 10:41 pm

Re: Deluge does not start after force-rebooting (Xubuntu 13.

Post by Sentinel »

rm ~/.config/deluge/ipc/deluge-gtk.lock

Easy peasy. It's the lockfile that prevents multiple instances of the gtk interface that didn't get cleaned up because of a hard reboot.
Post Reply