GNOME Bugzilla – Bug 679355
gedit crashes and locks up the system when dragging tab bar
Last modified: 2014-04-14 01:40:15 UTC
I'm using Gedit_3.4.1 on Ubuntu 12.04 64bit. I'm reporting a bug that is also experienced by someone using Gedit 3.3.0 on Fedora 16. Because of this, I hope it's safe to presume this is an upstream bug. fedora bug link https://bugzilla.redhat.com/show_bug.cgi?id=808789 Description of problem: Gedit crashes and freezes system when dragging a file from one Gedit window to another. Reproducible: 100% Steps to Reproduce: 1. Open Gedit from the menu, and open a file in that Gedit. 2. Use nautilus (or any file manager) to open another file with Gedit. (It will open in a new Gedit window) 3. Try to combine the files onto a single Gedit window by dragging the files tab. Results: XWindows gets locked up with a dragging mouse cursor. System must be hard rebooted, or Gedit killed from TTY1 for the system to continue.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Hi Mr Klapper. I will try to get a stack trace. In the meantime, if I may ask, are you able to produce this bug on your system? The steps are very simple. If I were to guess, I would imagine the problem is stemming from the fact that there should not even be 2 gedit instances running.
While trying to get the strace, I see that gedit actually running in two instances. It has only created a second window from the same instance. Why would it do that, who knows?
Created attachment 218326 [details] gdb output
I had to run gdb as root (sudo) because it wouldn't let me attach to the process. I was running as the same user, so I don't know why it wouldn't attach. After I got gdb attached, I dragged the tab from window to window, then my mouse locked up. I went to TTY1 and ran: killall gedit killall -9 gedit I ran the rest of the commands I was instructed to run for gdb, but they didn't all seem want to run well. Hopefully you can get what you need from the output that I was able to produce.
The above should say "gedit actually is Not running in two instances" > While trying to get the strace, I see that gedit actually running in two instances. It has only created a second window from the same instance. Why would it do that, who knows?
Another person is having a similar result in Firefox. Unfortunately, they are unable to reproduce this error, nor their own error. Here is the link: http://askubuntu.com/questions/162164/how-to-pinpoint-source-of-firefox-window-behavior/162207 "One of my favorite Unity features is the ability to pin windows to one side of the screen or the other. My tendency to do this a lot has made me notice a bug where when I'm moving a Firefox window I get the clenched fist and even after letting go of the window the pointer never returns to normal. After this I'm unable to use the mouse normally until I do a killall firefox from the terminal." The main reason I'm reporting this is because their description of their system locking up is nearly identical. -The mouse pointer turns into a clenched (dragging) icon. -The mouse can still be moved around the screen, but has no more capability to function. -Pressing Alt+F2 still brings up the Run dialog. -In the Run dialog, I can still type in keys on the keyboard, but Space and Enter (and perhaps all whitespace?) are not being received. Hopefully this further description will help with diagnosis. For whatever it's worth, it is my hunch that this bug is in a gtk library.
Stephen, is it still crashing with the latest version? I'm trying the 32-bit Gedit 3.10.3 and it's not happening right here. The Fedora Bug was closed with WONTFIX due to end of support of F16, and I think that bug was against the 32-bit version.
Yes, it is still crashing. My system is Ubuntu 64bit.
My system is still on Ubuntu 12.04, but I will probably upgrade to 14.04 in the next two months.
This looks to me like a bug in gtk+ that was fixed some time ago already. I tried reproducing the bug in 3.10 and couldn't. I'm closing this bug assuming it has been fixed, but please feel free to reopen it if you still manage to reproduce it.
Very good. I just tested gedit v3.10 on a machine running Ubuntu 14.04, and the bug cannot be reproduced there. I suppose now I should bring this bug to the attention of downstream (Ubuntu 12.04), so they can perhaps resolve it somehow. Thank you.