Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 49

Thread: Transmission - segmentation fault

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Negatives second part

    1.
    First fucking big problem is that I can not add comment to the torrent. Oh this is real fucking big problem because I am a member of many closed torrent portals and by adding comment to the torrents I was able to see who belongs to who and I was able to keep manageable my stuff.
    2.
    Second big fucking problem is that transmission 1.22 put the torrents in separate directory's.
    For example it put them in a directory of the name of the torrent file.
    Now this shit puts them in a directory unleashed mode.
    This is bad because the old way I was able to manage the files much better.
    3.
    Third fucking big problem is that of putting the files into one directory the files will be open to abuse.
    I do not know what would happen if you have two torrents with one readme.txt in the root.
    Please somebody explain this to me.
    4.
    It takes to me quite long time to upgrade because of the directory problems.
    5.
    I can not see the syslog, log. (Log button missing)
    6.
    I can not get info about the torrent regarding what type
    of files contains. (Info button missing)
    7.
    About button also missing.
    8.
    There is no fucking Fetch option.
    9.
    During download does not shows to how many pears I am uploading.
    Does not show the ratio in this stage.

    In the next post I will write down some tips on how to make a smother upgrade.
    Last edited by Freelancer; 05-10-2008 at 08:50.

  2. #2

    A helpfull post

    This is a quite helpful post regarding how to configure and start the new transmission.
    http://wl500g.info/showpost.php?p=108659&postcount=39
    this post is good on how to write the rc.unslung correctly:
    http://wl500g.info/showpost.php?p=60931&postcount=2

    Now here are some other tips.
    Watch out for the download and the configuration directory's.
    If you decide to start with a new config than do not have this layout:
    "/tmp/hardisk/torrent" -here are going the torrents this is download directory.
    "/tmp/hardisk/torrent/.config" this is the config dir.
    This is bad and pay attention. :-)
    Somebody can create a torrent like this:
    ".config/torrents/infinitecycle.torrent"

    The old 1.22 Transmission had the following default configuration.
    Well he went for the:
    "/tmp/harddisk/torrent" directory as a default.
    From here he had the following standard layout:
    /.config - for the config.
    /source - here you putted your torrents for upload, this was a legacy of the old transmission.
    /target - here were the fully downloaded torrents. This was the seeding place. :-)
    /work - here were the currently active torrents.
    The /.config had the following layout:
    /blocklist
    /resume
    /torrents
    Here were the torrent files that he worked.
    There was no separation between downloaded or working. only working and resume.
    The torrent files were also present in the /target and /work directory's. here was the structure of let's say /target (/work was the same.)
    /Name of the torrent file directory/
    /Name of the torrent file directory/.info
    /Name of the torrent file directory/.status
    /Name of the torrent file directory/Name of the torrent file.torrent.seeding
    /Name of the torrent file directory/* The torrent data *

    This type of directory was more of legacy from the prehistoryk transmission.
    The torrent files were present in many places.
    First:
    .config/resume
    .config/torrents
    target/Name of the torrent file directory/
    work/Name of the torrent file directory/
    and they all had different endings.
    .resume
    .suspended
    .seeding
    or simply torrent.

    Next post the new directory structure of new transmission.
    Last edited by Freelancer; 04-10-2008 at 10:59.

  3. #3

    New directory structure

    Well the new transmission has two main directory's:
    configuration and download.
    configuration by default is around:
    /tmp/local/root/ ...
    This is on the flash so leave it alone and start it as Shouriken said it.
    In the configuration directory you will have the same structure as at Transmission 1.22
    But in the download directory you will have the torrents unleasd so no special directory's for them or info files or whatever.
    This is I think is bad, and what pisses me on that if they correct this in the future I will have to do a lot of work to upgrade and transfer my seeds.

    Now I have a lot of upgrading to do so I'll stop.

  4. #4

    Other fuckups that I've done

    I just realized why the fuck I was not able to reinstall transmission 1.22.
    It is because I installed bash and that fucked the ipkg.
    Now I did all the conversions to my config files. I have the old ones backuped, but I am not going to revert. So I'll stay with this shit. Man I am pissed!

  5. #5

    Couple a days later and smarther

    Hi, there

    Here I am a couple of days later to continue the monologue.
    But hey maybe it will help somebody. :-)

    1.
    First fucking big problem is that I can not add comment to the torrent. Oh this is real fucking big problem because I am a member of many closed torrent portals and by adding comment to the torrents I was able to see who belongs to who and I was able to keep manageable my stuff.
    Well I installed on my PC the Windows Remote UI.
    From here:
    http://users.aber.ac.uk/anf6/projects/transmission/
    And that UI shows the trackers and I can sort them there.
    Visually I can keep track of them by the tracker.
    How ever there is no possibility of the comment which is still bad.
    An other thing, for me the Windows Remote UI did not worked and for this I needed to download the source and to correct it and recompile it.
    I rewrote the following function:
    Code:
    private void Form1_Resize(object sender, EventArgs e)
            {
                if (Program.form != null)
                {
                    if (Program.form.NotifyIcon.Visible && FormWindowState.Minimized == this.WindowState)
                    {
                        this.Hide();
                    }
                }
            }

    2.
    Second big fucking problem is that transmission 1.22 put the torrents in separate directory's.
    For example it put them in a directory of the name of the torrent file.
    Now this shit puts them in a directory unleashed mode.
    This is bad because the old way I was able to manage the files much better.
    3.
    Third fucking big problem is that of putting the files into one directory the files will be open to abuse.
    I do not know what would happen if you have two torrents with one readme.txt in the root.
    Please somebody explain this to me.
    Still a problem.


    4.
    It takes to me quite long time to upgrade because of the directory problems.
    Well yeah this was a pain + the recheck.


    5.
    I can not see the syslog, log. (Log button missing)
    Still looking for a solution.


    6.
    I can not get info about the torrent regarding what type
    of files contains. (Info button missing)
    This was solved by the Windows Remote UI.
    You can see the details here.


    7.
    About button also missing.
    8.
    There is no fucking Fetch option.
    Still a problem.


    9.
    During download does not shows to how many pears I am uploading.
    Does not show the ratio in this stage.
    Well on the Clutch you can see it in the Info panel.
    Windows Remote UI also shows it.

    And there is a 10 problem:
    I can not limit the number of torrents only the upload/download speed.

  6. #6
    Join Date
    Jun 2005
    Location
    Slovenia
    Posts
    736
    If u are dissapointed wint new interface, please open a ticket describing each trouble at http://trac.transmissionbt.com/report

    Meanwhile you can use old transmission now called transmissiond as separate package, that can work along new interface.

  7. #7
    Hello

    I use Openwrt with transmission. Im so lazy I didnt even make a startup script because it works stable for me.

    I didnt even read what you wrote right after the part where you say its a piece of shit and multiple F words.

    Really man go f yourself. Its a free peace of software and yes its not perfect but remember some ppl waste time making/trying it work and get your whining as credit.

    If you dont like it flash it back to ASUS firmware and kiss Download Master for me.

  8. #8
    Quote Originally Posted by Freelancer View Post
    Hi, there

    Here I am a couple of days later to continue the monologue.
    But hey maybe it will help somebody. :-)


    Well I installed on my PC the Windows Remote UI.
    From here:
    http://users.aber.ac.uk/anf6/projects/transmission/
    And that UI shows the trackers and I can sort them there.
    Visually I can keep track of them by the tracker.
    How ever there is no possibility of the comment which is still bad.
    An other thing, for me the Windows Remote UI did not worked and for this I needed to download the source and to correct it and recompile it.
    I rewrote the following function:
    Code:
    private void Form1_Resize(object sender, EventArgs e)
            {
                if (Program.form != null)
                {
                    if (Program.form.NotifyIcon.Visible && FormWindowState.Minimized == this.WindowState)
                    {
                        this.Hide();
                    }
                }
            }
    Could you post your recompiled version of the program?

  9. #9
    does someone have the transmission 1.22 ipkg files?

    i have been unable to find them on the internet =(

  10. #10
    Join Date
    Nov 2006
    Location
    Budapest
    Posts
    9

    Transmission 1.40 compilation problem

    Hi,

    I have tried to compile the newest transmission client (1.40) from source. The 'configure' command wants to find the file 'openssl.pc' which does not exists in the firmware. I thought that this was fixed in transmission 1.40 because I saw the closed tickets for this. I have both the openssl and openssl-dev packages installed.

    If anyone has an idea what am i missing, please let me know.

    [admin@wlgp transmission-1.40]$ ./configure -q && make -s
    appending configuration tag "CXX" to libtool
    appending configuration tag "F77" to libtool
    Package openssl was not found in the pkg-config search path.
    Perhaps you should add the directory containing `openssl.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'openssl' found
    configure: error: Cannot locate ssl

  11. #11
    Join Date
    Aug 2008
    Location
    Poland, Biała Podlaska
    Posts
    276
    Quote Originally Posted by gstadler View Post
    Hi,

    I have tried to compile the newest transmission client (1.40) from source. The 'configure' command wants to find the file 'openssl.pc' which does not exists in the firmware. I thought that this was fixed in transmission 1.40 because I saw the closed tickets for this. I have both the openssl and openssl-dev packages installed.

    If anyone has an idea what am i missing, please let me know.

    [admin@wlgp transmission-1.40]$ ./configure -q && make -s
    appending configuration tag "CXX" to libtool
    appending configuration tag "F77" to libtool
    Package openssl was not found in the pkg-config search path.
    Perhaps you should add the directory containing `openssl.pc'
    to the PKG_CONFIG_PATH environment variable
    No package 'openssl' found
    configure: error: Cannot locate ssl
    For me openssl-devel package not works too.
    I compiled it from sources and now it works.

  12. #12
    Join Date
    Nov 2006
    Location
    Budapest
    Posts
    9
    Did you mean the openssl-dev package works or compiling transmission 1.40 works as well for you?

  13. #13
    Join Date
    Aug 2008
    Location
    Poland, Biała Podlaska
    Posts
    276
    Quote Originally Posted by gstadler View Post
    Did you mean the openssl-dev package works or compiling transmission 1.40 works as well for you?
    Compile it: http://www.openssl.org/source/openssl-0.9.8i.tar.gz
    After that compile transmission.

  14. #14
    Join Date
    Aug 2008
    Location
    Poland, Biała Podlaska
    Posts
    276

    transmission 1.41b3

    hi,

    newest transmission from repository is not working for me.

    Code:
    [admin@LesiukNET root]$ transmission-daemon
    transmission-daemon: can't resolve symbol '__libc_pthread_init'
    Somebody know how to fix it?
    Transmission 1.40 works OK.

    edit: also __libc_* refers to a fullblown libc, not uClibc (afaik)
    is that package wrong compiled?

    best regards
    Damian Lesiuk
    Last edited by Lesiuk; 16-12-2008 at 19:51.

  15. #15
    Join Date
    Dec 2007
    Location
    The Netherlands - Eindhoven
    Posts
    1,767
    you probably need to do:
    ipkg install libpthread
    at least... that's what it's asking for I believe

Page 2 of 3 FirstFirst 123 LastLast

Similar Threads

  1. Segmentation fault ?
    By Needfoul in forum German Discussion - Deutsch (DE)
    Replies: 2
    Last Post: 04-03-2007, 18:24
  2. Segmentation Fault in Samba
    By Galleons in forum WL-500gP Q&A
    Replies: 2
    Last Post: 10-02-2007, 23:15

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •