** Changed in: glib
Importance: Unknown = Medium
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
glib2.0 (2.13.7-1ubuntu1) gutsy; urgency=low
* Sync with Debian and new upstream version:
- The memory corruption warning from the slice allocator that
occurred when threads were initialized after the slice allocator
has been removed, as the slice allocator now works fine
I'm have no doubt that it will be fixed prior to the final release
thankyou.
I would have thought that obvious as have read through the various
milestones schedule up to the first beta.
Not to mention that I'm well aware of the unstable nature of alpha
releases. Gosh, such 'warnings' pop up all
Hi, having browsed through the Gutsy milestones the first entry entry
that I found is for Ubuntu 7.10 Beta scheduled for release on the 27th
of September. Just over two months away.
I'm curious as to why this is the case as,
a) an upstream fix has been released,
b) the bug has been rated as high
Well it will certainly be fixed by the developers long before Gutsy is
released as stable, currently it's an Alpha release and should not be
used for anything other than testing and bug-hunting.
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You
** Changed in: glib (upstream)
Status: Confirmed = Fix Released
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
I would just like to add that I recently compiled the latest stable
release of glib, 2.13.2 at the time, under feisty and installed it.
Suddenly I started getting this error everywhere. Therefore, it IS glib
related. Whether this has always been the case, but the error was not
previously printed
Yea, this command happens with lots of commands on Gutsy.
Just to add to the list :gftp
gFTP Warning: Skipping line 229 in config file: entropy_source
gFTP Warning: Skipping line 232 in config file: entropy_len
gFTP Warning: Skipping line 235 in config file: verify_ssl_peer
***MEMORY-WARNING***:
You can add comments if they have new informations, complains about
software not working correctly or printing warning on gutsy are of no
use. If an application is displaying an error you can open a bug against
it or a task on this one
--
[gutsy] GSlice: g_thread_init() Warning messages
Erm, just to add my $0,02, this warning has been displayed in all the glib
development releases for a while and is hidden in stable release, hence the
fact that one doesn't ever see it usually.
And for the record, it affects all pyGTK apps, and it's definitely not a
problem most often, but a
I realize there is a bit of dispute over whether or not this is a bug in
GLib or the applications that are using GLib, but regardless, it seems
to have an effect on a handful of programs. Could this be a case of an
older bug in GLib that was fixed but possibly now breaks existing apps
that
I understand that Gutsy is not stable yet. :)
I am just trying to help by validating this bug's importance for
resolution.
Handling the error better is a good starting point, but ideally someone who
knows the inner workings of GLib or one of the libraries that calls to it
can isolate the bug and
there is a workaround described in the bug. The glib2.0 upstream task
state they want to make it handle the error better, that will likely
happen before for gutsy, you are using an unstable distribution and such
bugs happen there
--
[gutsy] GSlice: g_thread_init() Warning messages
or clearly state what libraries/apps are doing wrong now
the warning is clear no, g_thread_init() must be called before all
other GLib functions?
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a
In the upstream bug linked to this one is stated that these errors
occurr if g_thread_init() is not the first glib function called and you
use gslice functions.
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because
Indeed. thanks for the clarification.
I will begin digging through some 3rd party library code to see if I can
remedy my problems.
I guess I am most surprised that the same libraries worked (as far as I
could tell) with older versions of GLib. I am glad that the errors are now
being caught and
I'm getting these too. I don't seem to see any pattern to them. It seems
completely random because I'm getting them by just installing the
updates.
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a
The bug is a mono bug, it should NOT depend on glib!!
It is already fixed in the upstream mono SVN and in debian unstable repository
as in
http://bugzilla.ximian.com/show_bug.cgi?id=8186
http://packages.debian.org/changelogs/pool/main/m/mono/mono_1.2.4-4/changelog
I'm attaching a patch which
Wrong link for ximian bugzilla, sorry
http://bugzilla.ximian.com/show_bug.cgi?id=81862
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
?! This patch is already in the gutsy packages since weeks... also mono
must depend on glib as it uses many glib functions to not reinvent the
wheel.
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a
Sorry, i just saw you committed the patch on 12/06, the bug report is dated
30/05, so i guess it is solved now, at least for mono...
I did not say mono must not depend on glib, i was saying this is not a glib bug
as stated, but a mono bug.
I think this should be closed...
--
[gutsy] GSlice:
Well, it's arguable whether this is a glib or $random_application bug...
see the upstream bugreport linked to this one here.
And this can't be closed because it still affects n+1 different
applications ;)
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
Same warnings are in bug 120344
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I am getting this same bug when I try to run a Java OpenGL (JOGL/SWT)
application (avoCADo CAD) that worked cleanly before I installed
[gutsy].Have there been any updates or decisions since the last post
about 12 days ago? I realize that [gutsy] is still in the debug
process and just want to
After all it seems that the GSlice: g_thread_init() bug was not due to
libglib, but to wxwidget 2.6 and 2.8. So it affected most programs
dependent from those libraries. With new versions of those libraries
released between yesterday and today it seems that the issue is gonna
be resolved. I still
** Changed in: glib (upstream)
Status: Unknown = Confirmed
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Changed in: glib2.0 (Ubuntu)
Importance: Low = High
Target: None = ubuntu-7.10-beta
--
[gutsy] GSlice: g_thread_init() Warning messages
https://bugs.launchpad.net/bugs/116870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Gramps (the genealogy program) and Audacity do not load at all. This may be due
to this bug or something else, if I am reading the comments properly, and I
should amend or file bugs for both of these.
Audacity has previously reported stability problems:
bug 106930
So I added my traceback report
28 matches
Mail list logo
