Summary: | crash selecting desktop settings | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | wet <mstrerotic> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | andresbajotierra, aseigo, kwin-bugs-null |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
wet
2010-01-28 23:07:29 UTC
This could be related to the glibc bug : bug 196207. Check this: - Start Konsole - Type "kquitapp plasma-desktop" + Enter - Wait 10 seconds - Type "killall plasma-desktop" + Enter - Type "export QT_NO_GLIB=1" + Enter - Type "export MALLOC_CHECK_=" + Enter - Type "plasma-desktop" + Enter - Repeat the situation and check if it crashes or not If it doesn't crash, then it is likely to be bug 196207. Thanks Thanks... I tried that and got this output from konsole... Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection That message is another bug which you should ignore in the test... try the whole set of steps again. Regards ok ran it again and the crash still happens... Can you install the "kdelibs5-dbg" and "kdebase-workspace-dbg" packages and post a complete backtrace here? (you can get more information at http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting ) Thanks ok did that and this is what I get now... Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #6 0x00e76422 in __kernel_vsyscall () #7 0x00c194d1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0x00c1c932 in *__GI_abort () at abort.c:92 #9 0x00c12648 in *__GI___assert_fail (assertion=0x6164b94 "dpy->xcb->reply_data != ((void *)0)", file=0x6164b29 "../../src/xcb_io.c", line=542, function=0x6164c91 "_XRead") at assert.c:81 #10 0x060f491d in _XRead () from /usr/lib/libX11.so.6 #11 0x04dde25d in ?? () from /usr/lib/libGL.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) and yes that is from the developer information tab... That is a different crash (as it is another application crashing). It seems to be related to your graphics drivers. May be the KWin developers can help you more than me. Regards so where do I go with this then...??? > Qt Version: 4.6.0
i'd start by using a Qt version that isn't known to have easily triggered crashes :) 4.6.1 at a minimum is recommended.
@wet: I added the KWin devs to the CC list of this mail, so they should be aware of this. Please wait for their advice. Regards (Offtopic: usually it is better to not mixup different crashes in the same report, but it is ok for this time as they could be related.) the entire reason I went to the "bleeding edge" version of kde is because initially kwin crashed completely at login every time... by doing a dist-upgrade it at least runs and completely except for the system settings = desktop part of it... the version of qt I have installed is the latest available from distribution... any advice on how to get version 4.6.1 or higher...??? as far as mixing up different crashes goes I only posted the results following your recommendations... I was completely unaware that this was more than one crash until you said so... I'm not normally your "bleeding edge" user so any help you can give is greatly appreciated... ^__^ No problem :) I don't know if Qt4.6.1 is available on Kubuntu, but it should appear in the "karmic-backports" repository. Regards Closing for lack of feedback. |