Bug 288091 - evince doesn't destroy tooltips belonging to a closed document
Summary: evince doesn't destroy tooltips belonging to a closed document
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 7
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Kristian Høgsberg
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-12 18:02 UTC by Ignacio Vazquez-Abrams
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-22 03:49:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Sample PDF (84.63 KB, application/x-pdf)
2007-09-15 23:15 UTC, Ignacio Vazquez-Abrams
no flags Details

Description Ignacio Vazquez-Abrams 2007-09-12 18:02:48 UTC
Description of problem:
evince doesn't destroy tooltips belonging to a document if you close the
document window.

Version-Release number of selected component (if applicable):
evince-0.8.2-1.fc7

How reproducible:
Every time

Steps to Reproduce:
1. Open any document in evince
2. Open another document in evince that has/uses tooltips
3. While the tooltip is showing, close the document, leaving the initial one open
  
Actual results:
Tooltips remain on the screen until all evince documents are closed

Expected results:
Tooltips should be destroyed as the generating document is closed

Additional info:
I saw this with PDFs, but there's no reason I can think of that other document
types would result in this.

Comment 1 Matthias Clasen 2007-09-14 23:30:06 UTC
It would be helpful if you could attach a document that shows this problem (ie
uses tooltips)

Comment 2 Ignacio Vazquez-Abrams 2007-09-15 23:15:08 UTC
Created attachment 196601 [details]
Sample PDF

Comment 3 Matthias Clasen 2007-09-17 02:59:48 UTC
Doesn't happen here. It is possible that tooltip fixes in GTK+ make a difference;
can you try with GTK+ 2.12.0 ?

Comment 4 Ignacio Vazquez-Abrams 2007-09-20 00:21:32 UTC
GTK+ 2.11.6 doesn't exhibit this problem.


Note You need to log in before you can comment on or make changes to this bug.