*** This bug is a duplicate of bug 85776 ***
https://bugs.launchpad.net/bugs/85776
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/6652915/CoreDump.gz
--
[apport] gnome-panel crashed with SIGSEGV in _int_malloc()
https://bugs.launchpad.net/bugs/90383
You received this
*** This bug is a duplicate of bug 85776 ***
** This bug has been marked a duplicate of bug 85776
[apport] gnome-panel crashed with SIGSEGV on package installation, valgrind
log required
--
[apport] gnome-panel crashed with SIGSEGV in _int_malloc()
https://launchpad.net/bugs/90383
--
Something else that has just happened; I believe there were some Gnome
updates in the last couple days; after a reboot earlier this evening,
nothing 'docks' in the system tray anymore. I can look in the system
monitor and it's in there that 'it' is loaded up, but nothing in the
system tray.
Thank you for your work, those valgrind logs have no error though
--
[apport] gnome-panel crashed with SIGSEGV in _int_malloc()
https://launchpad.net/bugs/90383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ok... I didn't know if maybe you could see something that was not
right. I have valgrind running and will let it run until something
'breaks'. I assume that the errors in there are normal...
Bill
Sebastien Bacher wrote:
Thank you for your work, those valgrind logs have no error though
I am also getting Nautilus crashes, but it doesn't come up in the Bug
Reporting proggy... Below is what comes up in a box:
Nautilus can't be used now, due to an unexpected error.
Nautilus can't be used now, due to an unexpected error from Bonobo when
attempting to locate the factory.Killing
thank you for the work on that. the valgrind log is not useful. You can
use gnome-session-remove gnome-panel then run valgrind
--
[apport] gnome-panel crashed with SIGSEGV in _int_malloc()
https://launchpad.net/bugs/90383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
OK... this is what I get when I first start valgrind... I see errors
but not sure if it's what you need. I assume you want me to leave it
running for a while and see what all happens when the panel crashes...
It's already at when I click on the 'frame' of the 'windows' to move a
window to a
I will be more then happy to, however I'm not sure exactly how to go
about it... I assume I will need to 'kill' gnome-panel, which I can do
in the system monitor and then restart it with Valgrind? Won't killing
the gnome-panel make that hard to do? I'd like to know exactly how to
go about it,
Not sure if this helps or not... but there are errors.
[EMAIL PROTECTED]:~$ valgrind gnome-panel
==29963== Memcheck, a memory error detector.
==29963== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==29963== Using LibVEX rev 1658, a library for dynamic binary translation.
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6652915/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/6652916/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/6652917/Disassembly.txt
** Attachment
Thanks for your bug report. The crash looks like a memory corruption.
Could you try to get a valgrind log for it? (you can follow the
instructions from https://wiki.ubuntu.com/Valgrind for that)
** Changed in: gnome-panel (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) =
12 matches
Mail list logo
