After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 520469 - Available audio codec table should not be visible in gok when it's not showing.
Available audio codec table should not be visible in gok when it's not showing.
Status: RESOLVED INCOMPLETE
Product: ekiga
Classification: Applications
Component: Accessibility
2.0.x
Other opensolaris
: Normal normal
: ---
Assigned To: Jan Schampera
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-05 07:55 UTC by Tim Miao
Modified: 2017-07-17 18:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Tim Miao 2008-03-05 07:55:17 UTC 
Steps to reproduce:
1. Launch ekiga and gok.
2. Go to ekiga menu Edit->Preferences to open the ekiga preferences tab.
3. Go to any entry of left menu tree, e.g. "Personal Data" under "General".
4. Select GOK UI Grab to grab available widgets in this tab.

Expected result:
GOK should grab widgets which are contained in current tab.

Actual result:
GOK grabs the Audio codec table in "Audio Codecs" tab when this tab is not visible.
Comment 1 Damien Sandras 2008-04-02 20:44:01 UTC 
Is it really an Ekiga problem ?
Comment 2 Damien Sandras 2008-09-14 18:55:39 UTC 
Ping...
Comment 3 Tim Miao 2008-09-16 03:23:34 UTC 
Li, would you please help to look at this bug? Thanks.
Comment 4 Matthias Schneider 2008-10-14 06:24:00 UTC 
Does this still apply to Ekgia 3.0.0?
Comment 5 Eugen Dedu 2009-05-22 20:07:05 UTC 
Any news?
Comment 6 Tim Miao 2009-05-25 02:29:06 UTC 
According to #583313, this problem might be a regression of GOK. Wait for the patch in #583313 integration and verify this bug later.
Comment 7 Eugen Dedu 2013-01-28 17:44:14 UTC 
Ping...
Comment 8 Alexandre Franke 2017-07-17 18:25:08 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!