ktoon crashes on start (empty window with title Fatal error)

[Konstantinos Kostarellis]

Binary package hint: ktoon

starting ktoon lucid on terminal results in following output

-------
ktoon
[Initializing DApplication]
[Initializing DConfig]
[Initializing DConfigDocument]
*********Init configuration file : "/home/USERNAME/.ktoon/ktoon.cfg"
ktoon(2488)/ KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-USERNAME/ksycoca4"
ktoon is crashing with signal 11 :(
-------

replaced my user with USERNAME

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: ktoon 0.8.1-4.1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Thu Jun 10 13:21:42 2010
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:de:en_GB:en
SourcePackage: ktoon

[Daniel Hahler (blueyed)]

Is there a crash file from apport that you could attach? Look in /var/crash.

You may have to enable apport first (see /etc/default/apport IIRC).

[Ute Hauth (listen-miradlo)]

It's the same for me :

starting ktoon lucid on terminal results in following output
...$ [Initializing DApplication]
[Initializing DConfig]
[Initializing DConfigDocument]
*********Init configuration file : "/home/ute/.ktoon/ktoon.cfg"
ktoon(4394)/ KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-ute/ksycoca4"
ktoon is crashing with signal 11 :(

[1]+ Exit 128 ktoon
#####
2.6.32-24-generic #39-Ubuntu

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: ktoon 0.8.1-4.1 (amd64)
Uname: Linux 2.6.32-24-generic #39-Ubuntu
ProcEnviron:
 LANG=de_DE.UTF-8
 ###
I enabled /etc/default/apport but I didn't get any results in /var/crash

[Tony Brown (bonybrown-gmail)]

The problem can be worked around by placing the attached config file into ~/.ktoon/ktoon.cfg
It would seem then that KToon is not writing a valid or complete initial config file when it's first started.

[Eckhart Wörner (eckhart)]

Version: unspecified (using KDE 4.4.5)
OS: Linux

This bug has been copied over from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603480

----

In qguiplatformplugin_kde.cpp:fileDialogSetVisible it has
        if (!kdefd && visible) {

           if(qfd->options() & QFileDialog::DontUseNativeDialog)
                return false;

            kdefd = new KFileDialogBridge(KUrl::fromPath(qfd->directory().canonicalPath()),
                                          qt2KdeFilter(qfd->nameFilters().join(";;")), qfd);

            qfd->setProperty("_k_bridge", QVariant::fromValue(kdefd));
        }

i.e. if you are making this visible and kdefd hasn't been created then create it now.
Most of the contents of the function are guarded by an if (visible) however on line 249 we have
        kdefd->setVisible(visible);

and if you make the object hidden before it's ever been made visible then kdefd will be NULL
and it seg's on line 249.

This is the underlying cause of [Debian] bug 599303 in ktoon which is marked RC.
It makes ktoon unusable for KDE users (although it works for Gnome users!)

I suggest guarding this line with an if (kdefd) but I don't know the structure to know if that is all that is needed.

Reproducible: Didn't try

[Cfeck (cfeck)]

Proposed patch:

Index: qguiplatformplugin_kde.cpp
===================================================================
--- qguiplatformplugin_kde.cpp (revision 1197348)
+++ qguiplatformplugin_kde.cpp (working copy)
@@ -214,7 +214,7 @@
     virtual bool fileDialogSetVisible(QFileDialog *qfd, bool visible)
     {
         K_FD(qfd);
- if (!kdefd && visible) {
+ if (!kdefd) {
             if(qfd->options() & QFileDialog::DontUseNativeDialog)
                 return false;

[Eckhart Wörner (eckhart)]

(In reply to comment #1)
> Proposed patch:

Doesn't that make fileDialogSetVisible(false) unnecessarily expensive? What are the reasons against the original submitter's proposal of guarding the kdefd->setVisible(visible) call?

[Launchpad Janitor (janitor)]

[Expired for ktoon (Ubuntu) because there has been no activity for 60 days.]

[Daniel Hahler (blueyed)]

I confirm this still being the case in Maverick (version 0.8.1-4.1ubuntu1) when using an empty config dir ~/.ktoon.

[Daniel Hahler (blueyed)]

We should check if the current release (0.9a-git04) still has this issue.

There's a deb available for it, but currently berlios.de (the site hosting the downloads) appears to be down; see http://www.ktoon.net/portal/download_counter

[Daniel Hahler (blueyed)]

The crash appears to be with KDE, see the second Debian bug I've just linked; http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603480

[Daniel Hahler (blueyed)]

This is fixed as of 0.8.1-4.1ubuntu2 (Ubuntu 11.04 / Natty).

[klearvue (thorovsky-gmail)]

The bug re-appeared in Oneiric.

Ktoon version - 0.8.1-4.2ubuntu1
KDE version - 4:4.7.2-0ubuntu1~ppa2

Launching Ktoon gives this:

  $ ktoon
  [Initializing DApplication]
  [Initializing DConfig]
  [Initializing DConfigDocument]
  *********Init configuration file : "/home/<USERNAME>/.ktoon/ktoon.cfg"
  ktoon is crashing with signal 11 :(

Ktoon creates configuration directory in ~/.ktoon but does NOT create ktoon.cgf file there.

[Daniel Hahler (blueyed)]

It's likely that the fix has been dropped in KDE:

   [ Didier Raboud ]
   * Fix a segfault in qguiplatformplugin_kde, thanks to David Alan Gilbert
     (patch 33_qguiplatformplugin_kde_NULL_check.diff). (Closes: #603480)

[Daniel Hahler (blueyed)]

I am opening a task for KDE.

Please verify that the fix from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603480 is included still in Ubuntu.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Harald Sitter (apachelogger)]

We do not introduce patches that were not approved and applied upstream.

[Justin Zobel (justin-zobel)]

Thank you for the report, Eckhart.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.

[Bug-janitor (bug-janitor)]

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

[Bug-janitor (bug-janitor)]

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!