Summary: | plasma crashed and left a black screen (QGraphicsLayoutItemPrivate::effectiveSizeHints, Plasma::ExtenderItemPrivate::repositionToolbox, Plasma::ExtenderItemPrivate::resizeContent) (kde svn(old), qt 4.5 beta) | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | Giovanni Venturi <giovanni> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | andresbajotierra, aseigo, jmbarkei, mar444aberto |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Giovanni Venturi
2009-01-23 23:48:43 UTC
What KDE version (or SVN revision/branch) are you using? What QT version (qt-copy patches?) are you using ? What were you doing when Plasma crashed? Thanks kde svn from a week, qt 4.5 beta, I was not doing nothing of special I was closing a kde game... Mh, may be it's a Qt bug. (I can't find any other duplicate of this backtrace) I have this problem too, since this morning (19.02.09)), when I updated (as regularly) my KDE 4.2 version from the OpenSuse 11.1 repositories. crash is repeatedly initiated when either dolphin or konsole is started (on startup) and leaves a black screen, irritably with a movable mouse pointer on it ... (good to see there is still something at work ;-) but since nothing else works, there is no option except a system restart ... Thanks for a fast resolution this is a rather annoying bug! Jay Well ... seems there is no resolution or what??? bug has been growing even more annoying after todays update of KDE reps from OpenSuse-Servers. actually I get a black screen, with seemingly still runnign system under it, but no way to get back every now and then, when starting programs, opening dolphin, trying to open files, and so on. is there no one who would like to get help on this?? can't be that there is no resolution because it did not happen like that the three weeks before yesterday ...!! Jay I've been getting blank (with squares and rectangles) screens on first logins after reboot ever since the latest major update including kernel patch, requiring reboot (OpenSuse Yast's description of the update was "this is going to be the official version on the new SE version") just a few days ago. Worse yet, if I logout and re-login, the blank screen freezes, leaving only the power button logout/power-off/reboot menu as an option. I have a dv6840el HP laptop with NVIDIA driver, and all was fine until this last major update. Here follows the Plasma crash report: Application: Plasma Workspace (plasma), signal SIGSEGV [?1034h(no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb2b7db90 (LWP 6171)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb804378e in ?? () from /lib/ld-linux.so.2 #7 0xb804adab in ?? () from /lib/ld-linux.so.2 #8 0xb80469f6 in ?? () from /lib/ld-linux.so.2 #9 0xb804a66c in ?? () from /lib/ld-linux.so.2 #10 0xb5636c4f in ?? () from /lib/libdl.so.2 #11 0xb80469f6 in ?? () from /lib/ld-linux.so.2 #12 0xb563711c in ?? () from /lib/libdl.so.2 #13 0xb5636b81 in dlopen () from /lib/libdl.so.2 #14 0xb730c55f in ?? () from /usr/X11R6/lib/libGL.so.1 #15 0xb671b77c in ?? () from /usr/lib/libQtCore.so.4 #16 0xb671ba08 in ?? () from /usr/lib/libQtCore.so.4 #17 0xb6715613 in QPluginLoader::load() () from /usr/lib/libQtCore.so.4 #18 0xb6b0b708 in KPluginLoader::load() () from /usr/lib/libkdecore.so.5 #19 0xb6b0bd97 in KPluginLoader::KPluginLoader(KService const&, KComponentData const&, QObject*) () from /usr/lib/libkdecore.so.5 #20 0xb7ec27df in Plasma::Applet::load(QString const&, unsigned int, QList<QVariant> const&) () from /usr/lib/libplasma.so.2 #21 0xb7eee6f9 in ?? () from /usr/lib/libplasma.so.2 #22 0xb7eed0b9 in Plasma::Corona::loadLayout(QString const&) () from /usr/lib/libplasma.so.2 #23 0xb7eed971 in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib/libplasma.so.2 #24 0xb800c7b9 in ?? () from /usr/lib/libkdeinit4_plasma.so #25 0xb800e437 in ?? () from /usr/lib/libkdeinit4_plasma.so #26 0xb800e561 in ?? () from /usr/lib/libkdeinit4_plasma.so #27 0xb7fff81a in kdemain () from /usr/lib/libkdeinit4_plasma.so #28 0x08048852 in _start () Following up on the previous email above, the only way I can currently use KDE4 is to uninstall the NVIDIA driver and kernel patch, from IceWM. So I would suggest checking that latest kernel + NVIDIA patch update mentioned in the other email. Again, I use KDE4-only OpenSuse11.1 on an HP Pavilion dv6840el with NVIDIA card, and latest updates of the following repositories as of today: OSS, non-OSS, NVIDIA, Packman, Updates, Videolan. Installed software: nvidia-gfxG02-kmp-pae: v. 180.29_2.6.27.18_0.3-0.1 x11-video-nvidiaG02: v. 180.29-0.1 kde4-kdm: 4.1.3-10.1 kdebase4: 4.1.3-3.7 kdebase4-runtime: 4.1.3-4.1 kdelibs4: 4.1.3-4.9 qt3: 3.3.8b-87.11 libqt4: 4.4.3-4.8.2 I hope this can help you guys. An additional comment: - with NVIDIA driver installed, the first time you login after reboot you get a regular desktop environment. But if you log out and re-login, then you get the "blank" screen. @Mar: your crash seems to be different from the originally reported one. #14 0xb730c55f in ?? () from /usr/X11R6/lib/libGL.so.1 May be it's related to your graphics drivers OpenGL support. If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace in a NEW report? YOu may need to install the "kdelibs5-debuginfo", "kdebase4-workspace-debuginfo" and "libqt4-debuginfo" packages. Thanks :) -------- @Giovanni: have you experienced this crash again with an updated KDE and Qt4.5.0 final (already released) ? Thanks --- @Jay: your crash may be different. If you still experience it, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace in a NEW report? Thanks :) @ Darío Andrés (In reply to comment #9) > #14 0xb730c55f in ?? () from /usr/X11R6/lib/libGL.so.1 > May be it's related to your graphics drivers OpenGL support. The current version of NVIDIA driver at their repository was working perfectly until the latest kernel update, so I don't really know where to look for the problem in this case. > If you can reproduce the crash at will, may you read > http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports > and post a complete backtrace in a NEW report? > YOu may need to install the "kdelibs5-debuginfo", > "kdebase4-workspace-debuginfo" and "libqt4-debuginfo" packages. I've got another problem now: there is no crash anymore, only a dark screen after the second login after the installation of the driver. The only thing I can see is the mouse pointer that can move. It's not frozen, since I can hit the power button and logoff, and then log in to IceWM for another uninstallation of the driver. But without a crash, how can I get a crash report, even if I install the -debuginfo packages?? I've posted the bug report nr. 484573 at bugzilla.novell.com with attached x11 logs from before and after installation of nvidia driver. Would that be any helpful here? And, should I still create a new report here? Without crash reports, what sort of logs should I post? Thanks for the attention, appreciated! @Mar: on that "black screen", can you type Alt+F2 to launch KRunner and to try to start Konsole or starting Plasma directly ? Thanks original report does not include a version # or svn rev# and does not provide any information on how to duplicate it (though it looks like the crash-on-drag bug that was fixed) the rest of the comments are apparently driver issues. The original report reported the data of the update of the SVN. No information was needed at that time because it was the plasma crash dance. Plasma crashed on all action you did, so if you don't have the plasma crash dance wants to say that it's possible that the bug was fixed. |