Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1661848 - ODBCManageDataSourcesQ4 segfaults
Summary: ODBCManageDataSourcesQ4 segfaults
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: unixODBC-gui-qt
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Jan Staněk
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-24 02:57 UTC by Roy A. Gilmore
Modified: 2019-11-27 20:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 20:42:13 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Roy A. Gilmore 2018-12-24 02:57:08 UTC 
Description of problem:
Trying to run ODBCManageDataSourcesQ4 causes a segfault

Version-Release number of selected component (if applicable):
unixODBC-gui-qt-0-0.18.20120105svn98.fc29.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Open a terminal window
2. type /usr/bin/ODBCManageDataSourcesQ4
3. press "enter"

Actual results:
[rag@thor ~]$ /usr/bin/ODBCManageDataSourcesQ4
Segmentation fault (core dumped)

Expected results:
To actually do something useful, like manage my ODBC datasources.

Additional info:
Comment 1 Jan Staněk 2019-01-04 14:22:43 UTC 
The reported segmentation faults manifests even on the latest (currently r132) SVN checkout when using Qt4 libraries. However, the Qt5 version seems to work correctly.

If available, is using Qt5 version an option? Note that the executable names will change the Q4 suffic to Q5:
- `ODBCCreateDataSourcesQ4` → `ODBCCreateDataSourcesQ5`
- `ODBCManageDataSourcesQ4` → `ODBCManageDataSourcesQ5`
Comment 2 Fedora Update System 2019-01-15 15:04:50 UTC 
unixODBC-gui-qt-0-0.19.20190111svn132.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-376e81570f
Comment 3 Fedora Update System 2019-01-16 03:31:11 UTC 
unixODBC-gui-qt-0-0.19.20190111svn132.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-376e81570f
Comment 4 Ben Cotton 2019-10-31 20:10:10 UTC 
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

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 29 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 5 Ben Cotton 2019-11-27 20:42:13 UTC 
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.