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.
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.
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.
*** 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
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
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
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
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
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
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
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
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
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
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
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
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
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;
** 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
18 matches
Mail list logo
