Bug 266222 - KMail window is drawn with all widgets one on top of another
Summary: KMail window is drawn with all widgets one on top of another
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: GUI (show other bugs)
Version: 1.13.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-13 19:34 UTC by Davor Cubranic
Modified: 2018-09-04 18:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of the blank window (15.26 KB, image/png)
2011-02-13 19:34 UTC, Davor Cubranic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Davor Cubranic 2011-02-13 19:34:44 UTC
Created attachment 57220 [details]
Screenshot of the blank window

Version:           1.13.5 (using KDE 4.5.1) 
OS:                Linux

After startup, KMail's window was almost entirely blank except for a rectangle in the top left (see attached screenshot). That appears to be all the widgets placed one on top of another, because when I right-click in that area, I see context menus for the folder view or the scrollbars. Menu shortcuts do not work, and closing the window with Alt-F4 crashed KMail and produced the following trace:


Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7716780 (LWP 1868))]

Thread 2 (Thread 0xb263ab70 (LWP 1979)):
#0  0x01eefe36 in clock_gettime (clock_id=32456692, tp=0xb2639f20) at ../sysdeps/unix/clock_gettime.c:100
#1  0x0090e50b in ?? () from /usr/lib/libQtCore.so.4
#2  0x009e56e5 in ?? () from /usr/lib/libQtCore.so.4
#3  0x009e572a in ?? () from /usr/lib/libQtCore.so.4
#4  0x009e37a8 in ?? () from /usr/lib/libQtCore.so.4
#5  0x009e383d in ?? () from /usr/lib/libQtCore.so.4
#6  0x01e38e6a in g_main_context_prepare () from /lib/libglib-2.0.so.0
#7  0x01e39279 in ?? () from /lib/libglib-2.0.so.0
#8  0x01e39848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#9  0x009e359f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#10 0x009b3609 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#11 0x009b3a8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x008afb7e in QThread::exec() () from /usr/lib/libQtCore.so.4
#13 0x0099235b in ?? () from /usr/lib/libQtCore.so.4
#14 0x008b2df9 in ?? () from /usr/lib/libQtCore.so.4
#15 0x00b45cc9 in start_thread (arg=0xb263ab70) at pthread_create.c:304
#16 0x05f1d69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7716780 (LWP 1868)):
[KCrash Handler]
#7  0x048ed874 in QTreeWidget::setItemExpanded(QTreeWidgetItem const*, bool) () from /usr/lib/libQtGui.so.4
#8  0x010d4d05 in KMail::FolderView::slotFolderExpanded(QTreeWidgetItem*) () from /usr/lib/libkmailprivate.so.4
#9  0x010e0577 in KMail::FolderView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4
#10 0x010e589a in ?? () from /usr/lib/libkmailprivate.so.4
#11 0x009ba8ca in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#12 0x009cd6ad in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#13 0x048e6383 in QTreeWidget::itemExpanded(QTreeWidgetItem*) () from /usr/lib/libQtGui.so.4
#14 0x048e7e36 in ?? () from /usr/lib/libQtGui.so.4
#15 0x048ee3c1 in QTreeWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtGui.so.4
#16 0x081f7cba in KPIM::TreeWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdepim.so.4
#17 0x08280fba in KPIM::FolderTreeWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdepim.so.4
#18 0x010e051a in KMail::FolderView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4
#19 0x010e589a in ?? () from /usr/lib/libkmailprivate.so.4
#20 0x009ba8ca in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#21 0x009cd6ad in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#22 0x048a4943 in QTreeView::expanded(QModelIndex const&) () from /usr/lib/libQtGui.so.4
#23 0x048b6642 in QTreeView::expand(QModelIndex const&) () from /usr/lib/libQtGui.so.4
#24 0x048b716c in QTreeView::setExpanded(QModelIndex const&, bool) () from /usr/lib/libQtGui.so.4
#25 0x048ed8f2 in QTreeWidget::setItemExpanded(QTreeWidgetItem const*, bool) () from /usr/lib/libQtGui.so.4
#26 0x010d9073 in KMail::FolderView::restoreItemStates() () from /usr/lib/libkmailprivate.so.4
#27 0x010e023d in KMail::FolderView::reload(bool) () from /usr/lib/libkmailprivate.so.4
#28 0x01358e8b in KMMainWidget::readConfig() () from /usr/lib/libkmailprivate.so.4
#29 0x0136c4e1 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, KSharedPtr<KSharedConfig>) () from /usr/lib/libkmailprivate.so.4
#30 0x0105da1a in ?? () from /usr/lib/libkmailprivate.so.4
#31 0x01270701 in KMKernel::openReader(bool) () from /usr/lib/libkmailprivate.so.4
#32 0x01277bbb in KMKernel::action(bool, bool, QString const&, QString const&, QString const&, QString const&, QString const&, KUrl const&, KUrl::List const&, QStringList const&) () from /usr/lib/libkmailprivate.so.4
#33 0x0127a435 in KMKernel::handleCommandLine(bool) () from /usr/lib/libkmailprivate.so.4
#34 0x08049dd9 in _start ()


Reproducible: Didn't try
Comment 1 Davor Cubranic 2011-02-14 07:13:07 UTC
I think the underlying cause of this bug might be bug 266228: a problem with kwallet. While my wallet was borked, KMail would either open with the window as described here, or exit immediately, which I reported as bug 266216. I'll let the dev team decide whether this and 266216 is the same bug,  or if it really is two different ones triggered by the same condition, and which one manifests itself depends on random timing. (Visually at least, the two look very different, as #266216 exits without opening the window.)
Comment 2 Christophe Marin 2011-02-14 12:41:06 UTC
If This issue is reproducible, please install the debug packages for KMail and Qt and paste a better backtrace.
Comment 3 Andrew Crouthamel 2018-09-04 18:17:30 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!