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 72691 - gnome-db crashes clicking Apply in DSN Create Wizard
gnome-db crashes clicking Apply in DSN Create Wizard
Status: RESOLVED DUPLICATE of bug 72509
Product: gnome-db
Classification: Deprecated
Component: Configuration
unspecified
Other other
: Normal critical
: GNOME-DB-1-0
Assigned To: Rodrigo Moya
Rodrigo Moya
Depends on:
Blocks:
 
 
Reported: 2002-02-26 16:07 UTC by danmorg
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description danmorg 2002-02-26 16:08:13 UTC 
Package: gnome-db
Severity: normal
Version: 0.8.104
Synopsis: gnome-db crashes clicking Apply in DSN Create Wizard
Bugzilla-Product: gnome-db
Bugzilla-Component: builder
BugBuddy-GnomeVersion: 2.0 (1.112.0)

Description:
Description of Problem:
gnome-db crashes once you click the button Apply in the Data Set Name
create wizard.
It appears that the crash  takes place in gnome-db-components.
gnome-db also crashes a second time after it crashes the first time -
probably because it is exiting.

Steps to reproduce the problem:
1. run gnome-db
2. click Manager button
3. click Create DSN toolbar button
4. when the Wizard pops up, click the title bar (this maybe a GNOME
problem having to click the title bar to make the DSN Wizard the Active
focused window, but that's another bug)
5. enter your DSN info: Name: dsn12, select provider: PostgreSQL, click
Forward, enter Host: localhost Database: test
6. click Apply

These steps will crash gnome-db everytime.

Actual Results:
It has a 'segmentation fault' twice in a row.  I think the first maybe
gnome-db-components and which causes gnome-db to exit which crashes
itself with a segmentation fault.

Expected Results:
gnome-db not to crash, the wizard to close, the dsn to show up in the
list of DSNs when I try to connect to database.

How often does this happen?
Everytime.

Additional Information:
Could it be something with Gnome, Bonobo, GtkSocket, or GConf?



Debugging Information:

[New Thread 1024 (LWP 30151)]
0x40c52669 in __wait4 () from /lib/i686/libc.so.6

+ Trace 18332

Thread 1 (Thread 1024 (LWP 30151))

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 598
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 gtk_socket_end_embedding
    at gtksocket.c line 375
  • #7 gtk_socket_filter_func
    at gtksocket.c line 1346
  • #8 gdk_event_apply_filters
    at gdkevents-x11.c line 267
  • #9 gdk_event_translate
    at gdkevents-x11.c line 531
  • #10 _gdk_events_queue
    at gdkevents-x11.c line 1691
  • #11 gdk_event_dispatch
    at gdkevents-x11.c line 1747
  • #12 g_main_dispatch
    at gmain.c line 1616
  • #13 g_main_context_dispatch
    at gmain.c line 2160
  • #14 g_main_context_iterate
    at gmain.c line 2241
  • #15 g_main_loop_run
    at gmain.c line 2461
  • #16 gtk_main
    at gtkmain.c line 882
  • #17 bonobo_ui_main
    at bonobo-ui-main.c line 135
  • #18 gnome_db_main_run
    at gnome-db-init.c line 94
  • #19 main
    at main.c line 58
  • #20 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 598
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 gtk_socket_end_embedding
    at gtksocket.c line 375
  • #7 gtk_socket_filter_func
    at gtksocket.c line 1346 



------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-02-26 11:08 -------

Reassigning to the default owner of the component, rodrigo@gnome-db.org.
Comment 1 Rodrigo Moya 2002-02-26 16:20:27 UTC 
This is a crash of the manager component, which then seems to make the
frontend crash itself.
Comment 2 danmorg 2002-02-26 16:41:21 UTC 
According to Rodrigo, the problem is with GConf.

See this email from Havoc (the GConv maintainer) to Rodrio concerning
a    problem with GConfClient not being reentrant.  He has a
workaround.  See message at:

http://mail.gnome.org/archives/gconf-list/2002-February/msg00017.html

A workaround will be made for this.  May need to look in
libgda/libgda/gda-config.c
Comment 3 Luis Villa 2002-02-27 21:50:14 UTC 
Rodrigo: could you look at bug 72509? It appears that maybe this was a
gtk bug that has been fixed in CVS.
Comment 4 Gediminas Paulauskas 2002-03-02 22:48:53 UTC 
*** This bug has been marked as a duplicate of 72509 ***