I am unable to reproduce this bug on a Kubuntu Natty i386 system with qtcreator 2.1.0-0ubuntu2, libkdepim4 4:4.4.10-0ubuntu4, and Qt packages sourced by https://launchpad.net/ubuntu/+source/qt4-x11/4:4.7.2-0ubuntu6.2. My Kubuntu system is affected by bug 752713, so I cannot enter deisgn mode to attempt to produce the crash. But Tools > Options does not cause a crash on my system.
Are either of you still experiencing this bug, on a fully updated Kubuntu 11.04 system? If not, this can be marked Invalid. If so, then more information (specifically, a stack trace) will be required, in order for it to be likely that a developer could begin work on the bug. The best way to do this is (for either of you) to: (1) Install the necessary debug symbol packages. Since there is very little technical information provided so far about the crash, it is hard for me to know exactly which debug symbols are needed, but I recommend installing kdelibs5-dbg, libc6-dbg, libexpat1-dbgsym, libfontconfig1-dbg, libfreetype6-dbgsym, libgcc1-dbg, libglib2.0-0-dbg, libice6-dbg, libjpeg62-dbg, libpcre3-dbg or libpcre3-dbgsym, libpng12-0-dbgsym, libqt4-dbg, libsm6-dbg, libstdc++6-4.5-dbg, libtiff4-dbgsym, libxau6-dbg, libx11-6-dbg, libxcb1-dbg, libxext6-dbg, libxi6-dbg, libxrender1-dbg, libxt6-dbg, qtcreator-dbgsym, qt4-demos-dbg (if qt4-demos is installed), and zlib1g-dbg. If libkdepim4 is installed, then I recommend also installing kdelibs5-dbg, kdepimlibs-dbg, kdepim- dbg, kdepim-runtime-dbg, and libakonadiprotocolinternals1-dbgsym. Since some of these packages end in -dbgsym, you will have to add the ddebs software source (by following steps 1-4 at https://wiki.kubuntu.org/DebuggingProgramCrash#Debug_Symbol_Packages) in order to install them. (2) Enable Apport (https://wiki.kubuntu.org/Apport). (3) Produce the crash and let Apport initiate a new bug report (see https://help.ubuntu.com/community/ReportingBugs and https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting for more information about reporting crashes with Apport). Apport will automatically attach a stack trace and other important technical information about the crash. (4) Fill out the new bug report (in the automatically opened web browser window) and make sure it contains all the available information about this bug. Submit the bug report. (5) Change the new bug report's visibility from private to public. (You may want to read https://wiki.kubuntu.org/Bugs/HowToTriage first so you know the potential information disclosure risks of this and can take any necessary steps to mitigate them.) Please note that CoreDump.gz should *remain* attached so that the stack trace and thread stack trace can be further processed if necessary. (6) Mark this bug report as a duplicate of the new bug report (which is not the same as marking the new report a duplicate of this report). It seems likely that the symbol lookup error, reported when you run the application, is related to the crash--it may even be directly triggering program termination. Or it may be handled by the application, but lead to a crash later. (Or it may be unrelated to the crash, but that seems unlikely.) When an Apport-initiated report is submitted, that should be determinable. ** Changed in: qtcreator (Ubuntu) Status: New => Incomplete ** Tags added: amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790949 Title: qtcreator crashes when opening the designer or options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/790949/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
