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 339015 - Blue fish crashes when you click on Quick start
Blue fish crashes when you click on Quick start
Status: RESOLVED DUPLICATE of bug 324836
Product: bluefish
Classification: Other
Component: application
1.0.4
Other other
: High critical
: ---
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-04-19 12:31 UTC by davmor2
Modified: 2006-04-30 13:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description davmor2 2006-04-19 12:31:14 UTC
Distribution: Ubuntu 6.06 (dapper)
Package: bluefish
Severity: major
Version: GNOME2.14.1 1.0.4
Gnome-Distributor: Ubuntu
Synopsis: Blue fish crashes when you click on Quick start
Bugzilla-Product: bluefish
Bugzilla-Component: application
Bugzilla-Version: 1.0.4
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
After bluefish starts up I click on quick start to get the basic
framework laid out.  When clicking on Quick Start however it crashes and
brings up close/restart/inform developers.  after click on restart and
close and the bug still prevailing I am reporting it.  This is in
Ubuntu Dapper Beta.

Steps to reproduce the crash:
1. I open bluefish click on Quick start and it crashes.
2.
3.

Expected Results:
It just crashes

How often does this happen?
Everytime I click on Quick start

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/bluefish'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912586485856 (LWP 5412)]
(no debugging symbols found)
0x00002aaaae21b094 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 46912586485856 (LWP 5412))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_set_sensitive
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #8 gtk_tree_view_set_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 ??
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #22 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #26 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
  • #31 __libc_start_main
    from /lib/libc.so.6
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #0 waitpid
    from /lib/libpthread.so.0

--
Seek That Thy Might Know




------- Bug created by bug-buddy at 2006-04-19 12:31 -------

Comment 1 Daniel Leidert 2006-04-19 23:12:05 UTC
Sounds like http://bugzilla.gnome.org/show_bug.cgi?id=324836. Do you still observe this issue with out latest stable version (do you need a package for the dapper release?)
Comment 2 Alastair Porter 2006-04-20 08:41:24 UTC
I can confirm this issue, and that 1.0.5 works fine.

I've also filed a bug in Ubuntu's bug tracker to see if they can push 1.0.5 into Dapper as well.
Comment 3 Daniel Leidert 2006-04-20 16:35:18 UTC
Then I guess, this is a duplicate of bug #324836. Please feel free to report any further bugs you find.

> I've also filed a bug in Ubuntu's bug tracker to see if they can push 1.0.5
> into Dapper as well.

There is already an open UVF exception report for bluefish:
http://www.mail-archive.com/ubuntu-motu@lists.ubuntu.com/msg00333.html




*** This bug has been marked as a duplicate of 324836 ***
Comment 4 Alastair Porter 2006-04-20 20:52:37 UTC
(In reply to comment #3)
> There is already an open UVF exception report for bluefish:
Great, thanks
Comment 5 Daniel Leidert 2006-04-25 18:22:19 UTC
Hmm. Looking again into this, it could be another bug than I thought. The bluefish version in dapper should already contain the fix for the quickstart dialog (applied as part of the patch debian/patches/01_quickstart_fix.dpatch). Alastair, can you verify this bug with the dapper-version of bluefish (1.0.4-1ubuntu2)? If yes, there must be another bug and I was wrong thinking, that this is a duplicate of #324836.
Comment 6 Alastair Porter 2006-04-27 07:54:05 UTC
Hi Daniel,

There's something weird going on here,
after reinstalling bluefish (apt-get install --reinstall) I couldn't crash it. However, I got console spam:
(bluefish:8997): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed

Trying my 1.0.5 install (./configure --prefix=/opt/bluefish) didn't segfault / no spam,

Then trying the 1.0.4 install again, it crashed fine. Even after reinstalling.

I'll have a closer look in the next few days when I have some more time

Alastair
Comment 7 Alastair Porter 2006-04-30 05:36:04 UTC
Hi,

On closer inspection it looks like the patch is not being applied - there is no patch target in the debian/rules file.  Is this something to be reported upstream, or shall we wait for feedback on getting 1.0.5 into Dapper?
Comment 8 Daniel Leidert 2006-04-30 13:27:43 UTC
Right. Stephan added the include line for dpatch.make but forgot the patch and unpatch targets. This is not an upstream issue. It's a problem with the Ubuntu package and should be filed as bug against the Ubuntu package. Maybe you should try to directly contact Daniel Holbach or Stephan Hermann to get this issue solved. About the UVF-exception report and version 1.0.5: I'm not an Ubuntu user nor an Ubuntu maintainer. I just do the work for Debian and my packages are only used by Ubuntu. Please contact Daniel Holbach or Stephan Hermann about the open UVF excepton report to get 1.0.5 into dapper. IMHO there is also a place in Launchpade to mention the UVF exception report (the place is described somewhere in the Ubuntu-Wiki - just search the Wiki for 'UVF').

So this bug should be really a duplicate of #324836.