Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
Summary: New libgxim breaks emacs under heavy scrolling
https://bugzilla.redhat.com/show_bug.cgi?id=489121
Summary: New libgxim breaks emacs under heavy scrolling Product: Fedora Version: 10 Platform: All OS/Version: Linux Status: NEW Severity: high Priority: low Component: libgxim AssignedTo: tagoh@redhat.com ReportedBy: alfredo.ferrari@cern.ch QAContact: extras-qa@fedoraproject.org CC: tagoh@redhat.com, fedora-i18n-bugs@redhat.com Estimated Hours: 0.0 Classification: Fedora
Created an attachment (id=334416) --> (https://bugzilla.redhat.com/attachment.cgi?id=334416) echo of "strace emacs xxxx"
Description of problem: When editing remotely a file using emacs (eg in a vnc window) and scrolling it fast (eg with the down arrow kept pressed) emacs crashes all the times
Version-Release number of selected component (if applicable): libgxim-0.3.2-4.fc10.x86_64 libgxim-0.3.2-4.fc10.i386
How reproducible: Always
Steps to Reproduce: 1. Open a vnc connection. Edit a file using emacs 2. Scroll the file keeping the down arrow (or equivalent) pressed 3. Observe emacs crashing
Actual results: emacs crashes
Expected results: there should be no problem
Additional info: reverting to libgxim-0.3.1-1 fixes the problem. The problem has been verified on both i386 and x86_64. It does not depend on the network speed, even opening a vnc session on the same machine results in emacs crashing. The only error message visible on the screen is Connection lost to X server `:1.0'
I am sorry to report a further problem with the new libgxim, but it appears to be definitively not ready for prime time, breaking to many critical applications in unpredictable ways
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=489121
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flag| |needinfo?(alfredo.ferrari@c | |ern.ch)
--- Comment #1 from Akira TAGOH tagoh@redhat.com 2009-03-09 06:29:41 EDT --- When emacs crashed, is imsettings-applet still running?
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=489121
Alfredo Ferrari alfredo.ferrari@cern.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Flag|needinfo?(alfredo.ferrari@c | |ern.ch) |
--- Comment #2 from Alfredo Ferrari alfredo.ferrari@cern.ch 2009-03-09 07:13:39 EDT --- Yes, imsettings-applet is still running, at least it shows up in "ps ax" ....
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=489121
--- Comment #3 from Akira TAGOH tagoh@redhat.com 2009-03-09 07:40:50 EDT --- Hmm, I've tried keep pressing a Down or PageDown key on emacs to reproduce, after changing the keyboard settings on gnome-keyboard-properties to get a KeyPress event too fast and too much. however I've never seen emacs crashes yet.
Can you give me more info please?
1. head -20 $HOME/.xsession-errors 2. a backtrace at the place where X connection is lost. you might get something with setting a breakpoint at x_error_handler on gdb. 3. any other logs in .xsession-errors that might relates to imsettings-applet. or run LIBGXIM_DEBUG=all imsettings-applet manually after killing the existing one and try again.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=489121
--- Comment #4 from Akira TAGOH tagoh@redhat.com 2009-03-09 08:04:32 EDT --- Okay, finally I can reproduce this here too
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=489121
--- Comment #5 from Alfredo Ferrari alfredo.ferrari@cern.ch 2009-03-09 09:07:17 EDT --- Ok!! I am happy I am not alone... let me know if you need further infos.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=489121
--- Comment #6 from Akira TAGOH tagoh@redhat.com 2009-03-09 09:22:43 EDT --- Just for updates. maybe losing X connection is a side-effect. the root cause would be the key events is somehow getting stuck and didn't send back appropriate responses to the client. I'm investigating that now.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=489121
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |DUPLICATE
--- Comment #7 from Akira TAGOH tagoh@redhat.com 2009-03-10 09:11:27 EDT --- Closing as DUPLICATE so that the root cause is the same with it and as I mentioned at comment #6, crash with X connection lost is a side-effect. that would be just timed out to wait for a response.
*** This bug has been marked as a duplicate of 488976 ***
i18n-bugs@lists.fedoraproject.org