The valgrind log has no error. Could you open a new bug rather than
comment on a closed one? The issue might be not the same one and the
submitter might be not interested in the mails about yours
--
[apport] gnome-terminal crashed with SIGSEGV
https://bugs.launchpad.net/bugs/98813
You received
I have been seeing the same symptoms. I was at first unable to
reproduce it reliably, but I found that button-mashing (like repeating
the home keys: asdf;lkj) while in unicode-input mode (scim) would
crash it quickly. Actually, it doesn't crash, it just locks up. I have
to then kill it manually
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/7051348/CoreDump.gz
--
[apport] gnome-terminal crashed with SIGSEGV
https://bugs.launchpad.net/bugs/98813
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
As described in the previous comments, your report lacks the information
we need to investigate the problem further. We'll close this report for
now - please reopen it if you can give us the missing information.
** Changed in: gnome-terminal (Ubuntu)
Status: Needs Info = Rejected
--
The log has no error, could you try to get a new one?
--
[apport] gnome-terminal crashed with SIGSEGV
https://bugs.launchpad.net/bugs/98813
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
yes!the term is dead,so i kill it!i must upload a log again?
2007/3/31, Sebastien Bacher [EMAIL PROTECTED]:
did you get the crash during that run? The log has no clear error
--
[apport] gnome-terminal crashed with SIGSEGV
https://launchpad.net/bugs/98813
--
闲云孤鹤 - 清冷香中抱膝吟
--
[apport]
did you get the crash during that run? The log has no clear error
--
[apport] gnome-terminal crashed with SIGSEGV
https://launchpad.net/bugs/98813
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
ok ,i'll install the valgrind to get the debug log
2007/3/30, Daniel Holbach [EMAIL PROTECTED]:
Can you run gnome-terminal under valgrind and attach the log here?
http://wiki.ubuntu.com/Valgrind might help with that.
** Changed in: gnome-terminal (Ubuntu)
Status: Unconfirmed = Needs
the debug log with the command:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log gnome-
terminal
in the new gnome-termail window,i login a suse linux 8(GB2312
code),input some chinese word by scim to reproduce the
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7051348/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7051349/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7051350/Disassembly.txt
** Attachment
Thanks for your bug report.
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs
** Tags added: need-i386-retrace
--
[apport] gnome-terminal crashed with SIGSEGV
https://launchpad.net/bugs/98813
--
desktop-bugs mailing
StacktraceTop:malloc_consolidate () from /lib/tls/i686/cmov/libc.so.6
_int_malloc () from /lib/tls/i686/cmov/libc.so.6
malloc () from /lib/tls/i686/cmov/libc.so.6
?? () from /usr/lib/libfreetype.so.6
?? ()
** Tags removed: need-i386-retrace
** Attachment added: Stacktrace.txt (retraced)
Can you run gnome-terminal under valgrind and attach the log here?
http://wiki.ubuntu.com/Valgrind might help with that.
** Changed in: gnome-terminal (Ubuntu)
Status: Unconfirmed = Needs Info
--
[apport] gnome-terminal crashed with SIGSEGV
https://launchpad.net/bugs/98813
--
13 matches
Mail list logo
