GNOME Bugzilla – Bug 462840
crash if marking text behind left display border
Last modified: 2007-08-02 16:39:46 UTC
Distribution: Red Hat Linux release 3 Package: gedit Severity: Normal Version: GNOME2.14.3 2.14.4 Gnome-Distributor: Ubuntu Synopsis: crash while maring text behind left display border Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.14.4 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: When you mark text with mouse behind left border of the display and relase left click there, then marked text follow mouse even if mouse click is released. When you click to stop it, it crash. Steps to reproduce the crash: 1. write at least 1/2 page of text 2. mark text with mouse (hold left click) and move on the screen. Go behind left window corner (out of display if gedit window is not maximalized) 3. if you release the click when out of display(left side) with the mouse and continue moving the mouse, marked text will follow you. If it follows you and you right click on the text to stop it, it crash. If it doesn't start to follow you, then play litle bit like this and it will come. Expected Results: How often does this happen? every time, if done as described Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912587743664 (LWP 6932)] [New Thread 1074006368 (LWP 6933)] (no debugging symbols found) 0x00002aaaaf6f20ca in waitpid () from /lib/libpthread.so.0
+ Trace 152356
Thread 1 (Thread 46912587743664 (LWP 6932))
------- Bug created by bug-buddy at 2007-08-02 16:13 ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this. Unknown version 2.14.4 in product gedit. Setting version to "2.14.x".
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 344826 ***