logjam causes critical error in libsoup

Bug #125769 reported by Benjamin Collar
2
Affects Status Importance Assigned to Milestone
logjam (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I want logjam to use a proxy. When I set the proxy information, logjam dispIays "unknown error" and standard output has (logjam:1475): libsoup-CRITICAL **: soup_socket_client_new_sync: assertion `hostname != NULL' failed

Steps to Reproduce:

Open the menu Logjam/Preferences/System
Check "Use Proxy Server"
Type '192.168.0.1:3129' in the proxy text field.
Close the dialog
Try to submit a new entry

Revision history for this message
Jeff Anderson (jander99) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in logjam (Ubuntu):
status: New → Incomplete
Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for logjam (Ubuntu) because there has been no activity for 60 days.]

Changed in logjam (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.