Bug 328278 – Crash on click the "Pops up the navigation window" button on the bottom right corner

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 328278 - Crash on click the "Pops up the navigation window" button on the bottom right corner


Summary:	Crash on click the "Pops up the navigation window" button on the bottom right...


Status:	RESOLVED DUPLICATE of bug 151696

Product:	dia
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Dia maintainers
QA Contact:	Dia maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-01-23 10:04 UTC by mancina
Modified:	2006-01-23 19:59 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description mancina 2006-01-23 10:04:44 UTC

Distribution: Ubuntu 5.10 (breezy)
Package: dia
Severity: blocker
Version: GNOME2.12.1 0.94
Gnome-Distributor: Ubuntu
Synopsis: Crash on click the "Pops up the navigation window" button on 
the bottom right corner
Bugzilla-Product: dia
Bugzilla-Component: general
Bugzilla-Version: 0.94
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
Dia informs the user about an unexpected program exit after clicking
some times the button in the right down corner.
At each button press, a window tries to open up, but immediately closes
with no usability.

Steps to reproduce the crash:
1. Start Dia
2. Try to click the mentioned button ore or more times.
3.

Expected Results:
Program exit

How often does this happen?
Always

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/dia-gnome'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223661888 (LWP 9138)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 65512

Thread 1 (Thread -1223661888 (LWP 9138))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 _gdk_cursor_destroy
from /usr/lib/libgdk-x11-2.0.so.0
#5 gdk_cursor_unref
from /usr/lib/libgdk-x11-2.0.so.0
#6 navigation_popup_new
#7 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#13 _gtk_button_paint
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __kernel_vsyscall




-- 
Antonio Mancina




------- Bug created by bug-buddy at 2006-01-23 10:04 -------

Comment 1 Hans Breuer 2006-01-23 19:59:01 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 151696 ***