GNOME Bugzilla – Bug 154442
gnome-terminal crashes when mouse hovers over link
Last modified: 2005-07-22 16:30:23 UTC
Distribution: Debian 3.1 Package: gnome-terminal Severity: normal Version: GNOME2.8.0 2.7.3 Gnome-Distributor: Debian Synopsis: gnome-terminal crashes when mouse hovers over link Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.7.3 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: gnome-terminal crashes whenever I move my mouse over an hyperlink (such as ftp://debian.org). Steps to reproduce the crash: 1. Echo a hyperlink 2. Move the mouse over the hyperlink 3. Expected Results: Underline the hyperlink How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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)...[Thread debugging using libthread_db enabled] [New Thread 1089526272 (LWP 6980)] [New Thread 1104931760 (LWP 6983)] [Thread debugging using libthread_db enabled] [New Thread 1089526272 (LWP 6980)] [New Thread 1104931760 (LWP 6983)] [Thread debugging using libthread_db enabled] [New Thread 1089526272 (LWP 6980)] [New Thread 1104931760 (LWP 6983)] (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)...0x40c55431 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 50741
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-04 05:58 ------- Unknown version 2.7.3 in product gnome-terminal. Setting version to "1.9.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was troplosti@orcaweb.cjb.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
This crashed happened deep inside of your regexp lib and/or libc. Maybe you have a broken package? Do you see this?
I can't narrow it down. My libc version is currently 2.3.2.ds1-18. I don't think it's broken (unstable version). I thought I'd wait a while to see if the problem would go away when I some libs got updated, but nothing changed. I'm not having crashes when I hover over hyperlinks btw. When I do something like 'echo http://www.google.nl' and hover over it, everythings okay. But when I do 'apt-get upgrade' and the question to proceede appears and I then move my mouse over some text this crash occurs.... it's very annoying, also because it now crashes on one of my own applications while I'm trying to develop it...
You say “I then move my mouse over some text this crash occurs” What text do you mean? Does the crash happen when you have the pointer on a URL?
Any text. It doesn't matter what kind of text it is. My current gnome-terminal version is btw 2.8.0-2.
Ok. Then I have never seen anything like this. Since the stack trace does not even mention any thing related to gnome-terminal, I can't but wait for a duplicate which might give more information. The stack is probably corrupt, though. You should try to get a gnome-terminal debian package which includes debugging information, and try to get a stack trace with that.
I'm trying to build gnome-terminal with debug information but I can't get it to work, I'm working on it though...
I get: Previous frame inner to this frame (corrupt stack?) I'm not sure what else I can do...
Hi Jesse, are you still able to reproduce this? If you are able to reproduce this, it'd be really great if you could provide some stack traces with debugging symbols. If you experience any problems feel free to drop me a line and I'll try to help you out a bit.
I can't reproduce this any more. I thought it had something to do with utf-8 (and there was another bug report opened about this, it affected not only gnome-terminal but a lot of other applications as well). I guess it has been fixed so this can be closed.
All right, I'll close this as INCOMPLETE for now (since we can't pin-point a specific change that fixed it). If you reexperience it feel free to reopen it. Thanks a lot for following up.