[Bug 1322013] Re: libsoup2.4 2.46.0-2ubuntu1 may have regressed soup_message_set_request
soup_message_set_request() had incorrect annotations before; you shouldn't have to explicitly specify the length of the data from python. The annotations are fixed now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322013 Title: libsoup2.4 2.46.0-2ubuntu1 may have regressed soup_message_set_request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1322013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011473] Re: Please update to latest libsoup 2.39.2
webkit uses an unstable API in libsoup, which changed slightly in 2.39. you can't use stable webkit with unstable libsoup. the current unstable webkit release will work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011473 Title: Please update to latest libsoup 2.39.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1011473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930630] Re: 2.37.5.1 : soup_uri_set_path: runtime check failed: (path != NULL)
it still warns, but everything should still work fine anyway. (At this point the bug is in midori; it's calling soup_uri_set_path(uri, NULL), when it should be using instead.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930630 Title: 2.37.5.1 : soup_uri_set_path: runtime check failed: (path != NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/930630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929133] Re: After upgrading soup, can no longer connect to daap share via libdmapsharing: 'libsoup-CRITICAL **: soup_uri_new_with_base: assertion `base == NULL || SOUP_URI_IS_VALID (base)' failed
*** This bug is a duplicate of bug 928820 *** https://bugs.launchpad.net/bugs/928820 ** This bug has been marked a duplicate of bug 928820 libsoup-CRITICAL **: soup_uri_set_path: assertion `path != NULL' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929133 Title: After upgrading soup, can no longer connect to daap share via libdmapsharing: 'libsoup-CRITICAL **: soup_uri_new_with_base: assertion `base == NULL || SOUP_URI_IS_VALID (base)' failed' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/929133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928820] Re: libsoup-CRITICAL **: soup_uri_set_path: assertion `path != NULL' failed
can someone try building a new package with this patch, and see if it fixes things? (there will still be warnings, but the code should work despite the warnings now) ** Patch added: 0001-soup-uri-revert-some-of-the-previously-added-return-.patch https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/928820/+attachment/2726727/+files/0001-soup-uri-revert-some-of-the-previously-added-return-.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/928820 Title: libsoup-CRITICAL **: soup_uri_set_path: assertion `path != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/928820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928820] Re: libsoup-CRITICAL **: soup_uri_set_path: assertion `path != NULL' failed
what app are the warnings coming from? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/928820 Title: libsoup-CRITICAL **: soup_uri_set_path: assertion `path != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/928820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864384] Re: in python, Soup.Server handlers always get a null query. Same code works in vala.
this is a pygobject bug, not libsoup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864384 Title: in python, Soup.Server handlers always get a null query. Same code works in vala. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/864384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 823325] Re: 400 Bad Request on Launchpad subdomains
This is fixed with glib-networking master (and the next release, which I think will be 2.29.17). The patch should apply easily to earlier glib- networking releases as well. (http://git.gnome.org/browse/glib- networking/commit/?id=4175fd4718bfd247420fe20af492c944edf9b598) FWIW, it seems to me that this is a bug in the server-side TLS implementation; the SNI should not be included as part of the saved session (since it's presented as part of the ClientHello, not in one of the messages that gets skipped when resuming), and even if it is saved, the server ought to refuse to resume the session if the SNI saved in the session doesn't match the SNI requested in the ClientHello. But I don't know exactly what bit of software would be responsible for that on the server side of launchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/823325 Title: 400 Bad Request on Launchpad subdomains To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/823325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551308] Re: clock-applet crashed with SIGSEGV in g_main_context_dispatch()
the retraced stack trace is garbage. neither the sequence of calls nor the alleged arguments to those calls make any sense. did it use the wrong debuginfo? -- clock-applet crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/551308 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355547] Re: libsoup-CRITICAL: soup_message_queue_destroy: assertion
hrmph. This is http://bugzilla.gnome.org/show_bug.cgi?id=568375 but I was hoping it would go away in 2.26. ** Bug watch added: GNOME Bug Tracker #568375 http://bugzilla.gnome.org/show_bug.cgi?id=568375 -- libsoup-CRITICAL: soup_message_queue_destroy: assertion https://bugs.launchpad.net/bugs/355547 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286906] Re: Unable to use libmozjs.so in an application, because of library path problem.
This currently breaks gnome-shell as well, because gjs uses spidermonkey. bgo bug is http://bugzilla.gnome.org/show_bug.cgi?id=573413. (I was going to link that to this bug, but the Also affects project link only talks about *upstream* bugs, and this is downstream.) -- Unable to use libmozjs.so in an application, because of library path problem. https://bugs.launchpad.net/bugs/286906 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326099] Re: gnome-panel segfaulting every few seconds
ok. i think given that 2.25.91 is now only a week away, i'm not going to bother putting out another tarball before then. -- gnome-panel segfaulting every few seconds https://bugs.launchpad.net/bugs/326099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326099] Re: gnome-panel segfaulting every few seconds
I am pondering this. There is currently no good workaround. (The bad workaround is to remove all configured locations from you clock applet.) -- gnome-panel segfaulting every few seconds https://bugs.launchpad.net/bugs/326099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326099] Re: gnome-panel segfaulting every few seconds
I've committed this fix to libsoup svn... if possible, it would be cool to know for sure that this really does fix the problem before I release it as 2.25.5.1 ** Attachment added: probably fix http://launchpadlibrarian.net/22050072/326099.diff -- gnome-panel segfaulting every few seconds https://bugs.launchpad.net/bugs/326099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326099] Re: gnome-panel segfaulting every few seconds
The crash should only happen if the proxy requests authentication, so if that didn't happen for some reason when you used it from your home network, then you wouldn't see the crash. -- gnome-panel segfaulting every few seconds https://bugs.launchpad.net/bugs/326099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198562] Re: seahorse crashed with SIGSEGV in g_value_peek_pointer()
FYI, the crash appears to happen when seahorse tries to connect to a keyserver that isn't running. And the fact that there are many dups of the bug under ubuntu and none under other distros suggests that the non- responding server is probably keyserver.ubuntu.com. So if it's easy to make that server a little more reliable, that would keep people from hitting the bug. (The bug itself should probably be fixed by GNOME 2.24.1, next month.) -- seahorse crashed with SIGSEGV in g_value_peek_pointer() https://bugs.launchpad.net/bugs/198562 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95758] Re: Blam Theme Images not Displayed
Seen in my http logs: GET /~danw/blog/2007/03/blam-box-top-left.png HTTP/1.1 404 361 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) GET /~danw/blog/2007/03/blam-box-pad.png HTTP/1.1 404 356 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) GET /~danw/blog/2007/03/blam-box-top-right.png HTTP/1.1 404 362 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) GET /~danw/blog/2007/03/blam-box-bottom-left.png HTTP/1.1 404 364 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) GET /~danw/blog/2007/03/blam-box-bottom-right.png HTTP/1.1 404 365 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) at various times from various IP addresses, but always with the same Ubuntu-feisty User-Agent string. Blam in feisty is apparently trying to find its theme images on the blog server rather than on local disk. -- Blam Theme Images not Displayed https://launchpad.net/bugs/95758 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70368] Re: bug-buddy can block 'x-session-manager', preventing new X processes
** Changed in: bug-buddy (upstream) Importance: Undecided = Unknown Bugwatch: None = GNOME Bug Tracker #406009 Status: Unconfirmed = Unknown -- bug-buddy can block 'x-session-manager', preventing new X processes https://launchpad.net/bugs/70368 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
