tulip crashes on startup

I am also getting this error.

Running from the command line the only output I get is:

$ tulip
Segmentation fault

Before the segmentation fault I see the splash screen the progress bar goes all the way across, the window opens then crashes.

Version: tulip 3.0.0~B6-2

I'm experiencing this bug in hardy 32 bit.

I'm also getting this on hardy 32 bit. I'm no good at reading strace, but it makes a lot of references to "Resource temporarily unavailable" right before crashing...

mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb57fa000
read(15, "Xcur\20\0\0\0\0\0\1\0\3\0\0\0\2\0\375\377\30\0\0\0004\0"..., 4096) = 4096
_llseek(15, 0, [0], SEEK_SET) = 0
read(15, "Xcur\20\0\0\0\0\0\1\0\3\0\0\0\2\0\375\377\30\0\0\0004\0"..., 4096) = 4096
close(15) = 0
munmap(0xb57fa000, 4096) = 0
select(8, [7], [7], NULL, NULL) = 2 (in [7], out [7])
read(7, "\23\0009C\206\0\240\4\206\0\240\4\0i\301\t\330(\361\277"..., 4096) = 160
writev(7, [{"\236\24+\0\231\0\240\4\1\0\0\0004\0\0\0\v\0\f\0\0\0\f\0"..., 3364}], 1) = 3364
read(7, 0x82feb44, 4096) = -1 EAGAIN (Resource temporarily unavailable)
....
select(8, [7], [7], NULL, NULL) = 1 (out [7])
writev(7, [{"\2\t\4\0\217\0\240\4\0@\0\0\\\0\240\4", 16}], 1) = 16
read(7, 0x82feb44, 4096) = -1 EAGAIN (Resource temporarily unavailable)
select(8, [7], [7], NULL, NULL) = 1 (out [7])
writev(7, [{"\2\t\4\0\215\0\240\4\0@\0\0\\\0\240\4", 16}], 1) = 16
read(7, 0x82feb44, 4096) = -1 EAGAIN (Resource temporarily unavailable)
select(8, [7], [7], NULL, NULL) = 1 (out [7])
writev(7, [{"\22\0\30\0V\0\240\4(\0\0\0)\0\0\0 \0\0\0\22\0\0\0\37\2"..., 280}], 1) = 280
read(7, "\34\257\275CV\0\240\4(\0\0\0007|!$\0\31\t\10\20c \10\220"..., 4096) = 64
read(7, 0x82feb44, 4096) = -1 EAGAIN (Resource temporarily unavailable)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Process 7008 detached

I have the same problem over hardy amd64.
I have a segmentation fault

Following the instructions on https://wiki.ubuntu.com/DebuggingProgramCrash, I got a backtrace:

gdb tulip
...
(gdb) r
Starting program: /usr/bin/tulip
[Thread debugging using libthread_db enabled]
[New Thread 0xb587b740 (LWP 21683)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb587b740 (LWP 21683)]
0xb6de6e5a in ?? () from /usr/lib/libQtGui.so.4
(gdb) bt
#0 0xb6de6e5a in ?? () from /usr/lib/libQtGui.so.4
#1 0xb6de7f76 in QBoxLayout::minimumSize () from /usr/lib/libQtGui.so.4
#2 0xb6e07791 in QLayout::totalMinimumSize () from /usr/lib/libQtGui.so.4
#3 0xb6e07b20 in QLayout::activate () from /usr/lib/libQtGui.so.4
#4 0xb6e30761 in QWidget::setVisible () from /usr/lib/libQtGui.so.4
#5 0xb772e413 in Q3ToolBar::checkForExtension () from /usr/lib/libQt3Support.so.4
#6 0xb772e4fb in Q3ToolBar::resizeEvent () from /usr/lib/libQt3Support.so.4
#7 0xb6e32562 in QWidget::event () from /usr/lib/libQtGui.so.4
#8 0xb7167063 in QFrame::event () from /usr/lib/libQtGui.so.4
#9 0xb770b6b7 in Q3DockWindow::event () from /usr/lib/libQt3Support.so.4
#10 0xb772e73c in Q3ToolBar::event () from /usr/lib/libQt3Support.so.4
#11 0xb6ddac0c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#12 0xb6ddf898 in QApplication::notify () from /usr/lib/libQtGui.so.4
#13 0xb7a106a9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#14 0xb6e6595e in QWidgetPrivate::setGeometry_sys () from /usr/lib/libQtGui.so.4
#15 0xb6e2b58f in QWidget::setGeometry () from /usr/lib/libQtGui.so.4
#16 0xb7702619 in ?? () from /usr/lib/libQt3Support.so.4
#17 0xb77029e7 in ?? () from /usr/lib/libQt3Support.so.4
#18 0xb770418f in Q3DockAreaLayout::layoutItems () from /usr/lib/libQt3Support.so.4
#19 0xb7704824 in Q3DockAreaLayout::sizeHint () from /usr/lib/libQt3Support.so.4
#20 0xb6e075af in QLayout::totalSizeHint () from /usr/lib/libQtGui.so.4
#21 0xb6e20456 in QWidget::sizeHint () from /usr/lib/libQtGui.so.4
#22 0xb6e0b7a6 in QWidgetItemV2::updateCacheIfNecessary () from /usr/lib/libQtGui.so.4
#23 0xb6e0bc26 in QWidgetItemV2::maximumSize () from /usr/lib/libQtGui.so.4
#24 0xb6de6e37 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb6de7f76 in QBoxLayout::minimumSize () from /usr/lib/libQtGui.so.4
#26 0xb6e07791 in QLayout::totalMinimumSize () from /usr/lib/libQtGui.so.4
#27 0xb6e07b20 in QLayout::activate () from /usr/lib/libQtGui.so.4
#28 0xb6e07d3e in QLayout::widgetEvent () from /usr/lib/libQtGui.so.4
#29 0xb6ddabcd in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#30 0xb6ddf898 in QApplication::notify () from /usr/lib/libQtGui.so.4
#31 0xb7a106a9 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#32 0xb7a11a59 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#33 0xb7a11c7d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#34 0xb7a3bbcf in ?? () from /usr/lib/libQtCore.so.4
#35 0xb6693bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#36 0xb6696e5e in ?? () from /usr/lib/libglib-2.0.so.0
#37 0xb66973ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#38 0xb7a3bf98 in QEventDispatcherGlib::processEvents () from...

tulip still crashes with segmentation rocks version 3.0.0~B6-2.1.

How was this released? If a program is unusable, it should not be in the repositories at release. If people want it, put it in backports when it's stable.

I confirm this bug on Intrepid amd64:

$ uname -a
Linux 2.6.27-9-generic #1 SMP Thu Nov 20 22:15:32 UTC 2008 x86_64 GNU/Linux

$tulip
Segmentation fault

(package tulip_3.0.0~B6-2.1_amd64.deb)

Suspecting a problem related to the 64 architecture, I tested on a 32 bit intel machine.
tulip also crashed, although after dispaying the splash screen and (very) briefly an application window.

$ uname -a
Linux 2.6.27-11-generic #1 SMP Wed Jan 28 00:02:01 UTC 2009 i686 GNU/Linux

$ tulip
Segmentation fault

I'm also experiencing this bug with the following error message.

$ tulip
get fences failed: -1
param: 6, val: 0
Segmentation fault
$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
$ LANG=C apt-cache policy tulip
tulip:
  Installed: 3.0.0~B6-2.1
  Candidate: 3.0.0~B6-2.1
  Version table:
 *** 3.0.0~B6-2.1 0
        500 http://archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status
$

I upload the (tar gzipped) strace result of my environment by following the instruction in
https://wiki.ubuntu.com/Strace .

I also upload my backtrace result by following https://wiki.ubuntu.com/Backtrace .

This was autosynced from Debian which doesn't seem to have this problem. I suspect this is an issue with different versions of dependent libraries.

Karmic has the later version but that has failed to build. (Bug #379986).

Is everyone running this under Ubuntu, or Kubuntu? If Ubuntu, does it work okay if run under Kubuntu?

I'm wondering if this bug is Debian bug 479327 ?

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479327

It's fixed in the karmic version, but that doesn't build. Get the karmic version building, test then backport?

Thank you for your comment, Caroline ! Sorry for this late reply.

The environment I got the backtrace was on Ubuntu.
As you kindly pointed out, my backtrace was without some dbgsym packages.
After installing some *-dbgsym packages lacking, I get the backtrace again.
The result is attached in this comment.
I cannot find the appropriate dbgsym for uncovering ?? of "libQt3support.so.4."
If you know it and let me know it, I will get the backtrace once again.

After this, I'm going to run and check tulip on Kubuntu and Debian unstable environments.

Thank you again !

I algo get the backtrace on Kubuntu. The result is attached in this comment.

I checked the difference between them.
It seemed there was little difference except register numbers.
Maybe, this bug is common on some ubuntu distributions.

I see the segfault on startup on Trusty