Gedit crashes after certain mouse clicks

Bug #83128 reported by Shushan Wen
4
Affects Status Importance Assigned to Milestone
gedit
Fix Released
Unknown
gedit (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

1) start gedit
2) put your mouse in the middle of the empty screen
3) don't move your mouse while doing the following steps:
4) push left mouse button & hold
5) push right mouse button, release
6) release left mouse button
7) click left mouse button

Revision history for this message
Shushan Wen (shushanwen) wrote :

This bug was reported in Bug # 344826 by another user in gedit v2.14.3 and was marked as fixed. But it is still there in a fully patched Ubuntu dapper drake with gedit v2.14.4. I tried it in ubuntu dapper desktop i386 and amd64. Both have the same problem. It seems the bug is fixed by upstream. Please include the fix into dapper. Thanks.

Áron Sisak (asisak)
Changed in gedit:
importance: Undecided → Medium
Revision history for this message
Áron Sisak (asisak) wrote :

Thanks for your report and upstream bug tracker link.
Fix has been released for this: dapper-updates contains gedit 2.14.4.

Changed in gedit:
status: Unconfirmed → Fix Released
Changed in gedit:
assignee: nobody → desktop-bugs
Revision history for this message
Áron Sisak (asisak) wrote :

Sorry, I read again your report, Shushan. So I tried to reproduce it on up-to-date Dapper, with Gedit 2.14.4 and failed. However if I am right, for you the bug is still present on your system.

Changed in gedit:
assignee: desktop-bugs → asisak
status: Fix Released → Needs Info
Revision history for this message
Shushan Wen (shushanwen) wrote :
Download full text (7.8 KiB)

Yes. Both of my Dapper systems are up-to-date, too. If gedit does not crash at the first time, just repeat steps from 4 to 7. Thank you, Aron. The backtrace is as follows:

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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912587768240 (LWP 6018)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00002aaaaf6f8094 in waitpid () from /lib/libpthrea...

Read more...

Revision history for this message
Áron Sisak (asisak) wrote :

Thanks for your answer. Please try to obtain a backtrace with the debugging package: <http://wiki.ubuntu.com/DebuggingProgramCrash>.
This will greatly help us in tracking down your problem.

Revision history for this message
Shushan Wen (shushanwen) wrote :

Attached is the gdb backtrace info. If gdb is running, gedit will be deadlocked rather than crash. Thanks.

Changed in gedit:
status: Unknown → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gedit:
assignee: asisak → desktop-bugs
status: Needs Info → Rejected
Changed in gedit:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.