| Summary: | Crash after Login in KDE [QX11PixmapData::toImage, QPixmap::toImage, KPixmapCache::Private::writeData] | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | x545 <x545> |
| Component: | kdeui | Assignee: | kdelibs bugs <kdelibs-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | eragca, falk |
| Priority: | NOR | ||
| Version: | 4.3.1 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.5 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
- crashes 3 times after login - doesn't matter if I press restart or ok button Mh, it could be a Qt or kdelibs issue. - Did you got this google resource by debian packages or you manually compiled/installed it ? Thanks It is the official debian package: Package: akonadi-kde-resource-googledata Status: install ok installed Priority: extra Section: net Installed-Size: 500 Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Architecture: amd64 Source: akonadi-googledata Version: 1.0.1-1 Depends: kdebase-runtime (>= 4:4.3.0), kdelibs5 (>= 4:4.3.0), kdepimlibs5 (>= 4:4.3.0), libc6 (>= 2.2.5), libgcal0, libgcc1 (>= 1:4.1.1), libqt4-dbus (>= 4:4.5.2), libqt4-svg (>= 4:4.5.2), libqtcore4 (>= 4:4.5.2), libqtgui4 (>= 4:4.5.2), libstdc++6 (>= 4.1.1) Description: Google calendar and contacts resource for Akonadi It provides an easy access to Google calendars events and contacts. . This package contains the Google calendar and contacts resource for Akonadi, a Personal Information Management (PIM) storage service. Homepage: http://code.google.com/p/libgcal/ Sandro *** Bug 220801 has been marked as a duplicate of this bug. *** *** Bug 222155 has been marked as a duplicate of this bug. *** *** Bug 218998 has been marked as a duplicate of this bug. *** Created attachment 41691 [details]
New crash information added by DrKonqi
Akonadi uses both CPUs at 100% for 30sec, then crashes
Created attachment 41730 [details]
New crash information added by DrKonqi
Crash on session startup.
Special circumstances were delayed initialization of encrypted home volume, no network connectivity.
From bug 231943: (ksmserver crashed) -- Information about the crash: run automatic updates update yum without errors wait 30mins (i was reading :)) to reboot reboot fine and freezed/crashed after login *** Bug 231943 has been marked as a duplicate of this bug. *** From bug 231912: -- Information about the crash: I logued out after upgrading some KDE packages (Fedora 12) and it crashed right after I logued back in. The login splash screen froze for a while and then the Crash Reporting Assistant appeared. *** Bug 231912 has been marked as a duplicate of this bug. *** *** Bug 232019 has been marked as a duplicate of this bug. *** From bug 232354: -- Information about the crash: I did an update, restarted, and when logging in the desktop never showed up and I got this crash message. *** Bug 232322 has been marked as a duplicate of this bug. *** *** Bug 232354 has been marked as a duplicate of this bug. *** As a possible workaround, you may want to try to cleanup your "/var/tmp/kdecache-USERNAME/kpc/" directory. *** Bug 232742 has been marked as a duplicate of this bug. *** *** Bug 233003 has been marked as a duplicate of this bug. *** *** Bug 212795 has been marked as a duplicate of this bug. *** *** Bug 233388 has been marked as a duplicate of this bug. *** *** Bug 233296 has been marked as a duplicate of this bug. *** *** Bug 233701 has been marked as a duplicate of this bug. *** *** Bug 234130 has been marked as a duplicate of this bug. *** *** Bug 234075 has been marked as a duplicate of this bug. *** *** Bug 234246 has been marked as a duplicate of this bug. *** *** Bug 234561 has been marked as a duplicate of this bug. *** *** Bug 234576 has been marked as a duplicate of this bug. *** *** Bug 234867 has been marked as a duplicate of this bug. *** *** Bug 236091 has been marked as a duplicate of this bug. *** *** Bug 236578 has been marked as a duplicate of this bug. *** *** Bug 236894 has been marked as a duplicate of this bug. *** *** Bug 236969 has been marked as a duplicate of this bug. *** *** Bug 239883 has been marked as a duplicate of this bug. *** *** Bug 240373 has been marked as a duplicate of this bug. *** *** Bug 240565 has been marked as a duplicate of this bug. *** *** Bug 240605 has been marked as a duplicate of this bug. *** *** This bug has been confirmed by popular vote. *** *** Bug 242004 has been marked as a duplicate of this bug. *** *** Bug 242840 has been marked as a duplicate of this bug. *** *** Bug 234954 has been marked as a duplicate of this bug. *** *** Bug 236782 has been marked as a duplicate of this bug. *** *** Bug 237456 has been marked as a duplicate of this bug. *** *** Bug 234333 has been marked as a duplicate of this bug. *** *** Bug 237576 has been marked as a duplicate of this bug. *** *** Bug 235822 has been marked as a duplicate of this bug. *** *** Bug 241082 has been marked as a duplicate of this bug. *** SVN commit 1143110 by cfeck: Make sure QClipboard is created before setting the window icon The window icon will usually be a KIcon. Not really sure at which stage in KApplication initialization we are ready to access icons, but looking at how late we trigger KGlobalSettings, we should not set the global window icon before creating the clipboard. BUG: 209263 M +4 -0 kapplication.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1143110 *** Bug 244963 has been marked as a duplicate of this bug. *** *** Bug 244888 has been marked as a duplicate of this bug. *** *** Bug 243339 has been marked as a duplicate of this bug. *** *** Bug 244710 has been marked as a duplicate of this bug. *** *** Bug 244963 has been marked as a duplicate of this bug. *** *** Bug 246277 has been marked as a duplicate of this bug. *** *** Bug 245551 has been marked as a duplicate of this bug. *** *** Bug 246616 has been marked as a duplicate of this bug. *** *** Bug 246676 has been marked as a duplicate of this bug. *** *** Bug 246764 has been marked as a duplicate of this bug. *** *** Bug 247579 has been marked as a duplicate of this bug. *** *** Bug 247655 has been marked as a duplicate of this bug. *** Created attachment 50672 [details]
New crash information added by DrKonqi
When logon starts, the called program crashes.
@Juan Carlos Rivera Espinoza: please, don't attach bactkraces but paste directly in the comment. --- backtrace from comment #61 --- Application: klipper (v0.9.7) KDE Platform Version: 4.4.5 (KDE 4.4.5) (Compiled from sources) Qt Version: 4.6.3 Operating System: Linux 2.6.33.6-147.2.4.fc13.i686 i686 Distribution: "Fedora release 13 (Goddard)" -- Information about the crash: When logon starts, the called program crashes. -- Backtrace: Application: Klipper (klipper), signal: Aborted [KCrash Handler] #6 0x0053b416 in __kernel_vsyscall () #7 0x00b30d11 in raise () from /lib/libc.so.6 #8 0x00b325ea in abort () from /lib/libc.so.6 #9 0x003f0397 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #10 0x003ee226 in ?? () from /usr/lib/libstdc++.so.6 #11 0x003ee263 in std::terminate() () from /usr/lib/libstdc++.so.6 #12 0x003ee3a2 in __cxa_throw () from /usr/lib/libstdc++.so.6 #13 0x04bf4816 in qBadAlloc() () from /usr/lib/libQtCore.so.4 #14 0x04bffe5d in qUncompress(unsigned char const*, int) () from /usr/lib/libQtCore.so.4 #15 0x03d84bce in KPixmapCache::Private::loadData(int, QPixmap&) () from /usr/lib/libkdeui.so.5 #16 0x03d86872 in KPixmapCache::find(QString const&, QPixmap&) () from /usr/lib/libkdeui.so.5 #17 0x03cd1e2c in KIconCache::find(QString const&, QPixmap&) () from /usr/lib/libkdeui.so.5 #18 0x03cd2b51 in KIconCache::find(QString const&, QPixmap&, QString*) () from /usr/lib/libkdeui.so.5 #19 0x03cc7c87 in KIconLoader::loadIcon(QString const&, KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () from /usr/lib/libkdeui.so.5 #20 0x03d35245 in KSystemTrayIcon::loadIcon(QString const&, KComponentData const&) () from /usr/lib/libkdeui.so.5 #21 0x03d35853 in KSystemTrayIcon::KSystemTrayIcon(QString const&, QWidget*) () from /usr/lib/libkdeui.so.5 #22 0x009aae58 in ?? () from /usr/lib/libkdeinit4_klipper.so #23 0x009aa8ad in kdemain () from /usr/lib/libkdeinit4_klipper.so #24 0x080486dc in _start () Possible duplicates by query: bug 237576, bug 236969, bug 236091, bug 234987, bug 234867. Reported using DrKonqi *** Bug 249504 has been marked as a duplicate of this bug. *** *** Bug 249692 has been marked as a duplicate of this bug. *** *** Bug 250148 has been marked as a duplicate of this bug. *** *** Bug 250565 has been marked as a duplicate of this bug. *** *** Bug 251106 has been marked as a duplicate of this bug. *** *** Bug 251358 has been marked as a duplicate of this bug. *** *** Bug 250244 has been marked as a duplicate of this bug. *** *** Bug 250301 has been marked as a duplicate of this bug. *** *** Bug 250954 has been marked as a duplicate of this bug. *** *** Bug 251232 has been marked as a duplicate of this bug. *** *** Bug 246837 has been marked as a duplicate of this bug. *** *** Bug 251952 has been marked as a duplicate of this bug. *** *** Bug 252183 has been marked as a duplicate of this bug. *** *** Bug 252662 has been marked as a duplicate of this bug. *** (In reply to comment #17) > As a possible workaround, you may want to try to cleanup your > "/var/tmp/kdecache-USERNAME/kpc/" directory. Thanks a lot for the hint, worked for me. *** Bug 253471 has been marked as a duplicate of this bug. *** *** Bug 253605 has been marked as a duplicate of this bug. *** *** Bug 255225 has been marked as a duplicate of this bug. *** *** Bug 256697 has been marked as a duplicate of this bug. *** *** Bug 254903 has been marked as a duplicate of this bug. *** *** Bug 257270 has been marked as a duplicate of this bug. *** *** Bug 257876 has been marked as a duplicate of this bug. *** *** Bug 258783 has been marked as a duplicate of this bug. *** Created attachment 54489 [details]
New crash information added by DrKonqi
nepomukservicestub (0.2) on KDE Platform 4.5.4 (KDE 4.5.4) using Qt 4.7.1
- What I was doing when the application crashed:
Browsing the web. So likely unrelated.
- Unusual behavior I noticed:
Computer was quite slow and unresponsive. After crash it seemed to get better.
-- Backtrace (Reduced):
#10 0x002fdc45 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#11 0x002fbb16 in __cxxabiv1::__terminate (handler=0x2fdaf0 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:39
#12 0x002fbb53 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:49
#13 0x002fbcd2 in __cxxabiv1::__cxa_throw (obj=0xb47d3970, tinfo=0x33080c, dest=0x29f830 <std::length_error::~length_error()>) at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:83
#14 0x0029fdb0 in std::__throw_length_error (__s=0x308b63 "basic_string::_S_create") at ../../../../libstdc++-v3/src/functexcept.cc:74
Note that the last comment (comment 86) is a Strigi (file indexer) bug unrelated to this report which was fixed in KDE SC 4.5. Please report that error to the Strigi bugtracker if you can reproduce: http://sourceforge.net/tracker/?group_id=171000&atid=856302 Thanks *** Bug 260609 has been marked as a duplicate of this bug. *** *** Bug 260684 has been marked as a duplicate of this bug. *** *** Bug 260984 has been marked as a duplicate of this bug. *** *** Bug 260945 has been marked as a duplicate of this bug. *** *** Bug 262505 has been marked as a duplicate of this bug. *** Created attachment 56612 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.1
- What I was doing when the application crashed: unfortunately there's a case we can crash it.
This is how to reproduce it even wth 4.6.0
I've to explain my setup :
/ioda/data can have to state, serve as mountpoint when I'm connected to my main nfs server, otherwise it's a symlink to my local synchronised (by unison) data pointing to /home/ioda_data
Some of my pim data, and also nepomuk indexed folders are on this place.
So this time I've start kde with the nfs mounted. and launch the syncronizing process. No trouble.
At this end of the process, I unmount the nfs share and replace it by it's symlink.
(the umount process goes well, so we can affirm at this time no files where open)
I've only konversation open at that time + konsole
Once the symlink has been in place virtuoso-t start running at 100% cpu during 4-5minutes. In the mean times, I loose plasma control (can't change desktop by clicking on icon in systray bar. but able to change with ctrl+F# )
60 to 80 minutes after virtuoso-t running at 100% plasma-desktop start using 100% cpu too. Then crash (this backtrace) and restart properly.
After plasma-desktop restart everything works as expected.
It's pretty easy to me to reproduce it, so if dev's give me the how to get a good valgrind trace (which process must be analized) I can give that one.
-- Backtrace (Reduced):
#8 0x00007f0e95228b3d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#9 0x00007f0e95226d56 in __cxxabiv1::__terminate (handler=<value optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:39
#10 0x00007f0e95226d83 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:49
#11 0x00007f0e95226ed6 in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x00007f0e9648d373 in QEventLoop::exec (this=0x7fff9c9cc780, flags=...) at kernel/qeventloop.cpp:214
[Comment from a bug triager] @Bruno: you will need to create another bug report as yours is different to the original one here (that one was fixed on KDE SC 4.5); also, your backtrace is not the same, even when the crash handler said so (that's a limitation of the crash handle) Good enough, you provided lot of information, so I guess developers can check it. - Can you create a new bug report against plasma-desktop, please ? To other people: please do not add more KDE SC 4.5.0 or later reports; as this specific crash (with the backtrace including "KPixmapCache" as the title says) is fixed for KDE SC 4.5.0 THANKS @Dario : new bug 264738 is open now with the full details reported Sorry, I've been wrongly drive by drkonqi here. [Comment from a bug triager] Thank you very much! *** Bug 265865 has been marked as a duplicate of this bug. *** *** Bug 266279 has been marked as a duplicate of this bug. *** *** Bug 262774 has been marked as a duplicate of this bug. *** Christophe, Sunday I installed the latest security update for Java from Debian Squeeze and the Akonadi crash when launching Kmail has not shown up since. *** Bug 267068 has been marked as a duplicate of this bug. *** *** Bug 265784 has been marked as a duplicate of this bug. *** *** Bug 269142 has been marked as a duplicate of this bug. *** *** Bug 258745 has been marked as a duplicate of this bug. *** *** Bug 269249 has been marked as a duplicate of this bug. *** *** Bug 269746 has been marked as a duplicate of this bug. *** *** Bug 268820 has been marked as a duplicate of this bug. *** *** Bug 277629 has been marked as a duplicate of this bug. *** *** Bug 276946 has been marked as a duplicate of this bug. *** *** Bug 279934 has been marked as a duplicate of this bug. *** *** Bug 284058 has been marked as a duplicate of this bug. *** Clearing the CC list. There's no need to spam everyone for a bug fixed more than one year ago. Christophe Je n'ai pas eu le bug depuis les dernières mises à jour. *** Bug 285027 has been marked as a duplicate of this bug. *** |
Application that crashed: akonadi_googledata_resource Version of the application: 0.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.31.1 x86_64 Distribution: Debian GNU/Linux 5.0.3 (lenny) -- Backtrace: Application: Akonadi Resource (akonadi_googledata_resource), signal: Segmentation fault [KCrash Handler] #5 QX11PixmapData::toImage (this=<value optimized out>) at image/qpixmap_x11.cpp:1552 #6 0x0000003ec069895d in QPixmap::toImage (this=<value optimized out>) at image/qpixmap.cpp:447 #7 0x0000003ec489e251 in KPixmapCache::Private::writeData (this=<value optimized out>, key=<value optimized out>, pix=<value optimized out>) at ../../kdeui/util/kpixmapcache.cpp:1434 #8 0x0000003ec489ee34 in KPixmapCache::insert (this=<value optimized out>, key=<value optimized out>, pix=<value optimized out>) at ../../kdeui/util/kpixmapcache.cpp:1400 #9 0x0000003ec47f4f3d in KIconLoader::loadIcon (this=<value optimized out>, _name=<value optimized out>, group=<value optimized out>, size=<value optimized out>, state=<value optimized out>, overlays=) at ../../kdeui/icons/kiconloader.cpp:1052 #10 0x0000003ec47f5567 in KIconLoader::loadIcon (this=<value optimized out>, _name=<value optimized out>, group=<value optimized out>, size=<value optimized out>, state=<value optimized out>, overlays=) at ../../kdeui/icons/kiconloader.cpp:1177 #11 0x0000003ec47eb683 in KIconEngine::pixmap (this=<value optimized out>, size=<value optimized out>, mode=<value optimized out>, state=<value optimized out>) at ../../kdeui/icons/kiconengine.cpp:119 #12 0x0000003ec0670b35 in QIcon::pixmap (this=<value optimized out>, size=<value optimized out>, mode=<value optimized out>, state=<value optimized out>) at image/qicon.cpp:713 #13 0x0000003ec065fc45 in QWidgetPrivate::setWindowIcon_sys (this=<value optimized out>, forceReset=<value optimized out>) at kernel/qwidget_x11.cpp:1347 #14 0x0000003ec0629c10 in QWidget::create (this=<value optimized out>, window=<value optimized out>, initializeWindow=<value optimized out>, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1283 #15 0x0000003ec064ccf9 in setupOwner () at kernel/qclipboard_x11.cpp:130 #16 0x0000003ec064ece9 in QClipboard (this=<value optimized out>, parent=<value optimized out>) at kernel/qclipboard_x11.cpp:452 #17 0x0000003ec05d79f4 in QApplication::clipboard () at kernel/qapplication.cpp:3045 #18 0x0000003ec482a58f in KClipboardSynchronizer::Private::setupSignals (this=<value optimized out>) at ../../kdeui/kernel/kclipboard.cpp:94 #19 0x0000003ec482a953 in KClipboardSynchronizer (this=<value optimized out>, parent=<value optimized out>) at ../../kdeui/kernel/kclipboard.cpp:84 #20 0x0000003ec482ab04 in operator-> () at ../../kdeui/kernel/kclipboard.cpp:73 #21 operator KClipboardSynchronizer* () at ../../kdeui/kernel/kclipboard.cpp:73 #22 KClipboardSynchronizer::self () at ../../kdeui/kernel/kclipboard.cpp:74 #23 0x0000003ec4826400 in KApplicationPrivate::init (this=<value optimized out>, GUIenabled=<value optimized out>) at ../../kdeui/kernel/kapplication.cpp:463 #24 0x0000003ec482788f in KApplication (this=<value optimized out>, GUIenabled=<value optimized out>) at ../../kdeui/kernel/kapplication.cpp:343 #25 0x0000000000409b47 in _start () Reported using DrKonqi