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 345557 - Error with BlueFish with QuickStart
Error with BlueFish with QuickStart
Status: RESOLVED DUPLICATE of bug 324836
Product: bluefish
Classification: Other
Component: application
unspecified
Other other
: High critical
: ---
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-06-21 15:24 UTC by steven
Modified: 2006-06-21 15:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description steven 2006-06-21 15:24:30 UTC 
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Click QuickStart with blank document open. Crash.

Distribution: Ubuntu 6.06 (dapper)
Package: bluefish
Severity: Normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Click QuickStart with blank document open. Crash.
Bugzilla-Product: bluefish
Bugzilla-Component: application
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:

BlueFish crashes after QuickStart button is pressed.

Steps to reproduce the crash:
1. Open BlueFish
2. Make sure document is 'new'
3. Click 'QuickStart' button

Expected Results:

Program crashes. Expected results should be simple. Program crashes.
How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226053248 (LWP 8323)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 68979

Thread 1 (Thread -1226053248 (LWP 8323))

  • #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 gtk_widget_set_sensitive
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 _gtk_tree_selection_emit_changed
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_tree_view_set_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 _IO_stdin_used
  • #16 ??
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-06-21 15:24 -------
Comment 1 Daniel Leidert 2006-06-21 15:49:34 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system as bug #324836, but please feel free to report any further bugs you find.

This bug has also been reported several times to the Ubuntu BTS https://launchpad.net/distros/ubuntu/+source/bluefish/+bug/40289/+index. Please also read the information there. The reason, why you observe this bug is a packaging bug in Ubuntu. Now _please_ ask your MOTUs to fix the mistake they made, so we don't get any further reports about this already fixed issue from Ubuntu users.


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