Bug 1779442 - system-config-bind --> GUI: nothing happens; TUI: "ImportError: No module named ui" error message
Summary: system-config-bind --> GUI: nothing happens; TUI: "ImportError: No module nam...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-bind
Version: 31
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-04 01:16 UTC by Gustavo Marchetti
Modified: 2020-11-24 16:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 16:08:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gustavo Marchetti 2019-12-04 01:16:52 UTC
Description of problem: When I try to run system-config-bind (system-config-bind-4.0.15-16.fc29.noarch) under a GUI environment, like KDE Plasma 5.16.5, Qt 5.12.5, "nothing happens". 
When I try to run it from a TUI shell, like bash (bash-5.0.7-3.fc31.x86_64), it shows me:

[root@server ~]# system-config-bind
Traceback (most recent call last):
  File "/usr/sbin/system-config-bind", line 43, in <module>
    import gnome.ui
ImportError: No module named ui

[root@server ~]# uname -r
5.3.13-300.fc31.x86_64

[root@server ~]# rpm -q system-config-bind
system-config-bind-4.0.15-16.fc29.noarch

[root@server ~]# dnf update system-config-bind
Last metadata expiration check: 3:02:25 ago on Tue 03 Dec 2019 07:06:42 PM -03.
Dependencies resolved.
Nothing to do.
Complete!

[root@server ~]# rpm -q bash
bash-5.0.7-3.fc31.x86_64

[root@server ~]# dnf repolist
repo id                                                                                           repo name
fedora                                                                                            Fedora 31 - x86_64
fedora-modular                                                                                    Fedora Modular 31 - x86_64
google-chrome                                                                                     google-chrome
rpmfusion-free                                                                                    RPM Fusion for Fedora 31 - Free
rpmfusion-free-updates                                                                            RPM Fusion for Fedora 31 - Free - Updates
rpmfusion-nonfree                                                                                 RPM Fusion for Fedora 31 - Nonfree
rpmfusion-nonfree-updates                                                                         RPM Fusion for Fedora 31 - Nonfree - Updates
updates                                                                                           Fedora 31 - x86_64 - Updates
updates-modular                                                                                   Fedora Modular 31 - x86_64 - Updates
virtio-win-stable                                                                                 virtio-win builds roughly matching what was shipped in latest RHEL
[root@server ~]#





Version-Release number of selected component (if applicable):
system-config-bind-4.0.15-16.fc29.noarch


How reproducible:
Described above.

Steps to Reproduce:
1. Described above.
2.
3.

Actual results:
I can't edit my DNS server configurations on GUI environment.

Expected results:
It works fine.

Additional info:

Comment 1 Gustavo Marchetti 2019-12-04 01:20:16 UTC
On last three releases of Fedora (29, 30 and 31) this kind of bug happened...

Comment 2 Jaroslav Reznik 2019-12-04 08:06:15 UTC
System-config-bind is unmaintained upstream, so I believe the best way how to handle this in Fedora is to remove the package altogether.

Comment 3 Fedora Admin user for bugzilla script actions 2020-05-27 15:27:09 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 4 Ben Cotton 2020-11-03 16:48:17 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 2020-11-24 16:08:35 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.