Not a glib bug
** Changed in: glib2.0 (Ubuntu)
Status: New => Invalid
** Summary changed:
- [gutsy] glib2.0 applications crash with signal 5 in g_logv()
+ [gutsy] firefox crash on a _XError
--
[gutsy] firefox crash on a _XError
https://bugs.launchpad.net/bugs/122858
You received this bu
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Mozilla Bugs
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Tags added: mt-eval
--
[gutsy] glib2.0 a
Those bugs are not due to glib, the backtrace just starts on g_logv now
when a gdk_x_error or g_assert is triggered
--
[gutsy] glib2.0 applications crash with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122858
You received this bug notification because you are a member of Ubuntu
Desktop
something weird is happening with those, bug #122916 title is mentioning
g_logv, the error in an assert though
--
[gutsy] glib2.0 applications crash with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122858
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Well it may not be due to glib, but the segfault still happens in glib's
g_logv() :)
I'm using an Intel i915, with the i810 driver.
--
[gutsy] glib2.0 applications crash with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122858
You received this bug notification because you are a member o
what videocard and driver do you use? bug #122875 is a bug, it doesn't
show it's due to glib, a way to trigger it and a valgrind would be nice
to work on it
--
[gutsy] glib2.0 applications crash with signal 5 in g_logv()
https://bugs.launchpad.net/bugs/122858
You received this bug notification be
So far, I have seen no link in the crashes except the point at which the
crash happens, and as a result I haven't found a trigger. However, bug
122875 confirms this in evolution, and probably as a result other
applications as well.
--
[gutsy] glib2.0 applications crash with signal 5 in g_logv()
h
Do you have a way to trigger the crash? Looks rather an xorg driver bug
than a glib one
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
--
[gutsy] glib2.0 applications crash with signal 5 in g_logv()
https://bugs.launchpad.net
StacktraceTop:IA__g_logv (log_domain=,
log_level=G_LOG_LEVEL_ERROR, format=0xb79ab5a0 "%s", args1=0xbfc2acdc
"x\206\b\b\003")
IA__g_log (log_domain=0xb798f0a3 "Gdk", log_level=G_LOG_LEVEL_ERROR,
format=0xb79ab5a0 "%s") at /build/buildd/glib2.0-2.13.5/glib/gmessages.c:517
gdk_x_error (display=0x
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/8226335/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/8226336/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/8226337/Disassembly.txt
** Attachment
10 matches
Mail list logo
