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 131365 - DataSourceSelector crashes if data source doesn't exist
DataSourceSelector crashes if data source doesn't exist
Status: RESOLVED FIXED
Product: libgnomedb
Classification: Deprecated
Component: widgets
1.0.x
Other Linux
: High critical
: ---
Assigned To: Rodrigo Moya
gnome-db Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-13 20:16 UTC by Jon Willeke
Modified: 2005-08-15 01:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jon Willeke 2004-01-13 20:16:27 UTC 
I'm using libgda 1.0.2, libgnomedb 1.0.2, Python 2.3.3, and PyGTK 2.0.0 on
SuSE Linux 8.2.

If the name parameter doesn't correspond to an existing data source,
gnome_db_data_source_selector_new() causes a segmentation fault.  You can
reproduce this directly with DataSourceSelector or indirectly with Login. 
Here's the relevant portion of a backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 43191

Thread 16384 (LWP 13391)

  • #0 gnome_db_option_menu_set_selection
    at gnome-db-util.c line 579
  • #1 show_data_sources
    at gnome-db-data-source-selector.c line 73
  • #2 gnome_db_data_source_selector_new
    at gnome-db-data-source-selector.c line 182
  • #3 gnome_db_login_construct
    at gnome-db-login.c line 258
  • #4 gnome_db_login_new
    at gnome-db-login.c line 301
  • #5 _wrap_gnome_db_login_new
    at db.c line 2020 






Comment 1


alexander.winston





          2004-01-14 02:33:35 UTC
        



Bumping severity to critical and priority to high because this is a
crasher.






Comment 2


Laurent Sansonetti





          2004-02-16 18:01:58 UTC
        



Fixed in CVS (both HEAD and 1.0 branch).