Re: ETA on 2.0.3 .app
Posted: Wed Jul 24, 2019 10:17 am
So reading this thread made me give Deluge v2.0.3 on Mac another try (mainly because I wanted to be able to rename torrents before they download). I tried all the methods before, including Homebrew (which I'd rather avoid to be honest), but all of them failed. But this time I finally got deluge-gtk to run as a Thin Client on macOS 10.13.6, but I had to jump through a lot of hoops (see below).
Though I encountered a few bugs (Torrent Owners were not shown initially, Cmd-Q does not work, Menu -> Quit does), it really feels super fast compared to the old v1.3.15 (which was never great), so you guys did an amazing job, thank you!
Hopefully this will help anyone who might have given up before (like I did).
I am probably not going to be of much help here, but if there is anything I can do to help get a working Deluge v2 macOS app bundle out of the ground, let me know.
# Steps to install as per documentation (√):
1. Install homebrew (√)
2. Install dependencies (√)
2a. brew install pygobject3 gtk+3 adwaita-icon-theme (√)
2b. brew install libtorrent-rasterbar (√)
3. Link gettext (√)
3a. sudo chown -R user:admin /usr/local/share # was needed to finish step three without errors
3b. brew link gettext --force (√)
4. pip3 install deluge (√)
So far things went rather well. But at this point neither deluge-gtk nor deluge-console would run, so I ended up fixing a bunch of things that caused error messages (I hope I am not missing anything because it was a trial and error approach mostly; 'brew doctor' helped a bit, but I was mostly throwing error messages at my favourite search engine and tried to make sense of what I found):
5. Hoops I had to jump through
5a. brew link gtk+3
5b. brew install gdk-pixbuf
5c. brew link Atk
5d. brew install shared-mime-info
5e. brew reinstall gdk-pixbuf
5f. brew link gsettings-desktop-schemas
5g. glib-compile-schemas /usr/local/share/glib-2.0/schemas/
6. Finally, launch a working Deluge v2.0.3 via
6a. deluge-gtk &
At this point, only minor errors were thrown into Terminal (likely caused by wrong server address or wrong passwords).
Awww yiiiis.
I also got to see a lot of beachballs after the App finally started (possibly because I blocked a bunch of outgoing connections to trackers and stuff except to the deluged server sitting in my LAN).
Though I encountered a few bugs (Torrent Owners were not shown initially, Cmd-Q does not work, Menu -> Quit does), it really feels super fast compared to the old v1.3.15 (which was never great), so you guys did an amazing job, thank you!
Hopefully this will help anyone who might have given up before (like I did).
I am probably not going to be of much help here, but if there is anything I can do to help get a working Deluge v2 macOS app bundle out of the ground, let me know.
# Steps to install as per documentation (√):
1. Install homebrew (√)
2. Install dependencies (√)
2a. brew install pygobject3 gtk+3 adwaita-icon-theme (√)
2b. brew install libtorrent-rasterbar (√)
3. Link gettext (√)
3a. sudo chown -R user:admin /usr/local/share # was needed to finish step three without errors
3b. brew link gettext --force (√)
4. pip3 install deluge (√)
So far things went rather well. But at this point neither deluge-gtk nor deluge-console would run, so I ended up fixing a bunch of things that caused error messages (I hope I am not missing anything because it was a trial and error approach mostly; 'brew doctor' helped a bit, but I was mostly throwing error messages at my favourite search engine and tried to make sense of what I found):
5. Hoops I had to jump through
5a. brew link gtk+3
5b. brew install gdk-pixbuf
5c. brew link Atk
5d. brew install shared-mime-info
5e. brew reinstall gdk-pixbuf
5f. brew link gsettings-desktop-schemas
5g. glib-compile-schemas /usr/local/share/glib-2.0/schemas/
6. Finally, launch a working Deluge v2.0.3 via
6a. deluge-gtk &
At this point, only minor errors were thrown into Terminal (likely caused by wrong server address or wrong passwords).
Awww yiiiis.
I also got to see a lot of beachballs after the App finally started (possibly because I blocked a bunch of outgoing connections to trackers and stuff except to the deluged server sitting in my LAN).