Bug 658313 - KXML GUI Client error upon closing Okular
Summary: KXML GUI Client error upon closing Okular
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: okular
Version: 19
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 804614 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-29 23:43 UTC by James sparenberg
Modified: 2015-02-17 13:31 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:31:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 261538 0 None None None Never

Description James sparenberg 2010-11-29 23:43:52 UTC
Description of problem:
Upon closing okular (when opened from the command line) the following error is sent to standard out.

$ okular somedang.pdf 
okular(6866)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory! 
okular(6866)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x8dc1650 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. 


Version-Release number of selected component (if applicable):

kdegraphics-4.5.80-2.fc14.i686

How reproducible:

Open pdf from command line and then close it.  


Steps to Reproduce:
1. okular somedang.pdf
2. close okular
  
Actual results:

Above error message.

Expected results:
No error message.

Additional info:

Does not affect usability however the error message is one that could lead to user panic once it reaches production.

Comment 1 Kevin Kofler 2012-03-19 18:55:47 UTC
*** Bug 804614 has been marked as a duplicate of this bug. ***

Comment 2 Fedora End Of Life 2013-04-03 19:07:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 3 Fedora End Of Life 2015-01-09 16:28:00 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 13:31:06 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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