Your message dated Tue, 28 Oct 2014 08:03:44 -0500 with message-id <[email protected]> and subject line Closing has caused the Debian Bug report #752734, regarding twidge: Segmentation Fault on setup to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 752734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752734 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: twidge Version: 1.1.2 Severity: grave Justification: renders package unusable Dear Maintainer, 'twidge setup' results in a segfault and nothing is written tot he config file. Twidge remains in an unusable state since it's not authentified to twitter. Debug output: $ twidge -d setup CP /home/bsp/.twidgerc exists? True Welcome to twidge. We will now configure twidge for your use with Twitter (or a similar service). This will be quick and easy! Please wait a moment while I query the server... Trying first signRq2 First signRq2 result: OAuthRequest {unpackRq = ReqHttp {version = HTTP/1.1, ssl = True, host = "api.twitter.com", port = 443, method = GET, reqHeaders = Authorization=OAuth%20oauth_signature%3D%22LforbyZZHk2YBsNLvX7d6YWANOM%253D%22%2Coauth_consumer_key%3D%22pzWekpM5IRh7HaKc9syEw%22%2Coauth_nonce%3D%22FKfnWVEpTJumxIJqIxLz%252BAzyaLYM94Y%252FefPdZdmd5ks%253D%22%2Coauth_timestamp%3D%221403741035%22%2Coauth_signature_method%3D%22HMAC-SHA1%22%2Coauth_version%3D%221.0%22%2Coauth_callback%3D%22oob%22, pathComps = ["","oauth","request_token"], qString = , reqPayload = "", multipartPayload = []}} OK, next I need you to authorize Twidge to access your account. Please cut and paste this URL and open it in a web browser: https://api.twitter.com/oauth/authorize?oauth_token=REDACTED Click Allow when prompted. You will be given a numeric key in your browser window. Copy and paste it here. (NOTE: some non-Twitter services supply no key; just leave this blank if you don't get one.) Authorization key: 2106649 Trying second signRq2 Second signRq2 result: OAuthRequest {unpackRq = ReqHttp {version = HTTP/1.1, ssl = True, host = "api.twitter.com", port = 443, method = GET, reqHeaders = Authorization=OAuth%20oauth_signature%3D%REDACTED%2Coauth_consumer_key%3D%REDACTED%22%2Coauth_nonce%3D%REDACTED%253D%22%2Coauth_timestamp%3D%221403741063%22%2Coauth_signature_method%3D%22HMAC-SHA1%22%2Coauth_version%3D%221.0%22%2Coauth_verifier%3D%REDACTED%22%2Coauth_token%3D%REDACTED, pathComps = ["","oauth","access_token"], qString = , reqPayload = "", multipartPayload = []}} Got token: AccessToken Application "REDACTED" "REDACTED" oob user_id=REDACTED&screen_name=myscreenname&oauth_verifier=2106649&oauth_token=REDACTED&oauth_token_secret=REDACTED&oauth_callback_confirmed=true Segmentation fault -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages twidge depends on: ii curl 7.37.0-1+b1 ii libc6 2.19-3 ii libcurl3-gnutls 7.37.0-1+b1 ii libffi6 3.1-2 ii libgmp10 2:6.0.0+dfsg-4 twidge recommends no packages. twidge suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Closing at request of submitter. Thanks!
--- End Message ---
