| Summary: | quanta QToolBar reports warnings at application startup | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Scott R. Godin <rhbugzilla> |
| Component: | quanta | Assignee: | Than Ngo <than> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-05-13 13:17:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
it's fixed in quanta-3.1-1 |
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830 Description of problem: When starting quanta from the command line of an xterm, the following warning is repeated several times QToolBar::QToolBar main window cannot be 0. Version-Release number of selected component (if applicable): quanta-3.0-1.pr1.5 How reproducible: Always Steps to Reproduce: 1.start quanta from the command line of an xterm Actual Results: 3:36pm {6} pcp02404936pcs:/home/webdragon>$ quanta _KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root DCOPServer up and running. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QToolBar::QToolBar main window cannot be 0. QGDict::hashKeyString: Invalid null key Expected Results: no warnings from QT Additional info: Additionally I have repeatedly seen this: _KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root and gone and manually changed the ownership of that file. I continue to see this warning, and do not know what is re-arranging this after I have reset it. It would also be particularly nice if these warnings reported line numbers so one could go in and mess with the code itself.