** Changed in: notify-osd (Ubuntu)
Status: Incomplete = Invalid
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This seems to be extremely transient, unfortunately. Some kind of race
condition. I am marking it as incomplete, please reopen it if you manage
to reliably reproduce this, or of this crash occurs at an alarming rate.
** Changed in: notify-osd (Ubuntu)
Status: Confirmed = Incomplete
--
IE is my locale and the font is sans or sans bold.
I havent got the same error that I originally got when I reported the bug.
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs,
shane, is this something you still experience with the current notify-
osd package?
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: notify-osd (Ubuntu)
Assignee: David Barth (dbarth) = Eitan Isaacson (eeejay)
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
what application do you use which displays the bubble to get this issue?
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
rhythmbox.
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
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
what locale and font do you use?
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
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
Confirm this bug after a failure to resume and following kernel oops.
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Thanks the log has good informations now
==5005== Invalid read of size 8
==5005==at 0x6FA67CF: g_type_check_instance_is_a (in
/usr/lib/libgobject-2.0.so.0.2000.0)
==5005==by 0x40EADC: glow_cb (bubble.c:2346)
==5005==by 0x6F8C27C: g_closure_invoke (in
it seems that bubble is freed before having glow_cb() checking it, could
be a race somewhere I will let the notify-osd guys comment
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
I still couldnt recreate the crash as it happened the first. Originally
the whole desktop froze for about a minute but the errors that I got
while memcheck was on were more freezes with notify-osd only.
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in:
What command should I run? I installed valgrind but I dont know what
command to use.
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I got it started how much should I log?
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
did you read the wiki page indicated? or do you mean what binary?
/usr/lib/notify-osd/notify-osd is the one to run, you should stop the
running instance before starting the valgrind one though
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You
Yes I got it working. But when should I stop?
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
until you get the crash or an error in the log (invalid read or write
usually)
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Ok I got a few errors in the log but I couldnt make it crash like it did when I
reported this bug.
Ill attach the log.
** Attachment added: valgrind.log
http://launchpadlibrarian.net/24367553/valgrind.log
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
the log has clearly errors but you don't have debug symbols, can you
install notify-osd-dbgsym and get a new log?
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is
notify-osd-dbgsym isnt in the archive. Where do I get it?
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
http://wiki.ubuntu.com/DebuggingProgramCrash has details
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I got the log with the debug symbols. I also get a segmentation fault
with valgrind. Reported that bug also.
** Attachment added: memcheck with debug symbols
http://launchpadlibrarian.net/24380597/valgrind.log
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
StacktraceTop:IA__g_slice_alloc (mem_size=72)
pango_fc_font_map_load_fontset (fontmap=0x129a930,
pango_fc_font_map_load_font (fontmap=0x129a930,
_pango_cairo_font_private_get_hex_box_info (
_pango_cairo_font_private_get_glyph_extents (
** Attachment removed: CoreDump.gz
I confirm this bug on same configuration.
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: notify-osd (Ubuntu)
Status: New = Confirmed
--
notify-osd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/346596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/24200505/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24200506/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/24200507/Disassembly.txt
** Attachment
27 matches
Mail list logo
