Application: krdc (4.4.1 (KDE 4.4.1) "release 227") KDE Platform Version: 4.4.1 (KDE 4.4.1) "release 227" Qt Version: 4.6.2 Operating System: Linux 2.6.31.12-0.1-desktop i686 Distribution: "openSUSE 11.2 (i586)" -- Information about the crash: I was working on a windows terminal server. After a network disconnect the session hang and I tried to open the new connection tab. -- Backtrace: Application: KRDC (krdc), signal: Segmentation fault [KCrash Handler] #6 0xb65656d3 in QLayout::addChildWidget (this=0x8173f70, w=0x82676c0) at kernel/qlayout.cpp:1014 #7 0xb6573845 in QStackedLayout::insertWidget (this=0x8173f70, index=-1, widget=0x82676c0) at kernel/qstackedlayout.cpp:211 #8 0xb6a061d4 in QStackedWidget::insertWidget (this=0x8175770, index=-1, widget=0x82676c0) at widgets/qstackedwidget.cpp:185 #9 0xb6a150fc in QTabWidget::insertTab (this=0x817f310, index=-1, w=0x82676c0, icon=..., label=...) at widgets/qtabwidget.cpp:455 #10 0xb6a151ae in QTabWidget::insertTab (this=0x817f310, index=-1, w=0x82676c0, label=...) at widgets/qtabwidget.cpp:435 #11 0xb6a15213 in QTabWidget::addTab (this=0x817f310, child=0x82676c0, label=...) at widgets/qtabwidget.cpp:381 #12 0x08062844 in _start () Reported using DrKonqi
Can you reproduce this crash?
Sorry, so far not.
*** Bug 242696 has been marked as a duplicate of this bug. ***
See #242696 for a better stack trace. Tony, this bug might be introduces with your "recent" changes? Haven't you changed something with stacked layouts?
*** Bug 243290 has been marked as a duplicate of this bug. ***
*** Bug 243468 has been marked as a duplicate of this bug. ***
Urs, I can't see how this is crashing, unless there is a bug in Qt 4.6.2. All we are doing is calling KTabWidget::addTab(page, label). KRDC 4.4 does not use QStackedLayouts, just KTabWidget. The underlying implementation in Qt for QTabWidget uses them of course.
Can you reproduce this crash with KRDC from KDE SC 4.5?
*** Bug 248895 has been marked as a duplicate of this bug. ***
Better traces in: #243468 and #243290
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
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!
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!