Quanta Goes Haywire after switching MDI modes

Bug #230078 reported by aidave
2
Affects Status Importance Assigned to Milestone
kdewebdev (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Trying to switch MDI modes in Quanta causes all sorts of craziness. After switching to "top" mode it simply refuses to run anymore. This happens from console:

$ quanta
kbuildsycoca running...
QObject::connect: Cannot connect (null)::initiateDrag(QWidget *) to QuantaApp::slotTabDragged(QWidget*)
KCrash: Application 'quanta' crashing...
Could not find 'drkonqi' executable.
KCrash cannot reach kdeinit, launching directly.

Using Hardy+Gnome

Revision history for this message
aidave (aidave) wrote :

Now, even after using apt-get to remove Quanta and reinstalling it, it still refuses to run.

Revision history for this message
aidave (aidave) wrote :

Both Toplevel mode and Childframe MDI modes cause a crash.

Running "quanta --resetlayout" will restore it.

However those two MDI modes remain buggy!

Revision history for this message
aidave (aidave) wrote :
Revision history for this message
Michel (degreef-michel) wrote :

I have the same problem running Ubuntu 8.10 + KDE

Running "quanta --resetlayout" restores it.

Revision history for this message
gersoid (gerson-riddy) wrote :

I have the same problem on 8.10 + Gnome, could not start Quanta after entering MDI Childframe mode (pity)

cured also by quanta --resetlayout from the command line.

but on this first (re)run, I could not resize the Quanta window (which had opened in and had locked to the size of the parent winow in MDI mode). Exit cleanly from Quanta and restart from the menu fixed this.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Hi there!

 Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

 Thanks!

Changed in kdewebdev (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
JonathanEllis (jonnybal-gmail) wrote :

Has this bug actually been reported on https://bugs.kde.org as suggested by Harald?
Can someone post the link to that bug here, please?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.