Bug 281020 - plasma tablet crashes on startup
Summary: plasma tablet crashes on startup
Status: RESOLVED FIXED
Alias: None
Product: Active
Classification: Unmaintained
Component: Plasma mobile shell (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: unscheduled
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-29 21:10 UTC by Kenny D
Modified: 2011-09-12 11:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kenny D 2011-08-29 21:10:39 UTC 
Application: plasma-mobile (0.1)
KDE Platform Version: 4.7.1 (4.7.1) "release 9"
Qt Version: 4.7.3
Operating System: Linux 3.0.3-43-desktop i686
Distribution: "openSUSE 11.4 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:

during kde starting plasma crashes. this started after updating suse at the weekend

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Workspace (plasma-mobile), signal: Segmentation fault
[Current thread is 1 (Thread 0xb2673710 (LWP 2332))]

Thread 2 (Thread 0xb157eb70 (LWP 2333)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb384e105 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb77e5aec in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xb41f7f27 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0xb430e1a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#4  0xb41f7f6f in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0xb430e1a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#5  0xb3849b05 in start_thread () from /lib/libpthread.so.0
#6  0xb77d7d5e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb2673710 (LWP 2332)):
[KCrash Handler]
#7  0xb6d6fb77 in d_func (this=0x0) at ../../src/declarative/graphicsitems/qdeclarativeitem.h:194
#8  QDeclarativeItem::height (this=0x0) at graphicsitems/qdeclarativeitem.cpp:3073
#9  0xb7892c03 in PlasmaApp::setupHomeScreen (this=0x806a6d0) at /usr/src/debug/plasma-mobile/shell/plasmaapp.cpp:271
#10 0xb78935dd in PlasmaApp::corona (this=0x806a6d0) at /usr/src/debug/plasma-mobile/shell/plasmaapp.cpp:341
#11 0xb789485a in PlasmaApp::PlasmaApp (this=0x806a6d0) at /usr/src/debug/plasma-mobile/shell/plasmaapp.cpp:154
#12 0xb7894e5e in PlasmaApp::self () at /usr/src/debug/plasma-mobile/shell/plasmaapp.cpp:72
#13 0xb788bf53 in kdemain (argc=1, argv=0xbfb41874) at /usr/src/debug/plasma-mobile/shell/main.cpp:59
#14 0x0804861b in main (argc=1, argv=0xbfb41874) at /usr/src/debug/plasma-mobile/builddir/shell/plasma-mobile_dummy.cpp:3

Reported using DrKonqi
Comment 1 Marco Martin 2011-09-12 11:43:44 UTC 
since plasma-tablet is gone now (is plasma-device, with different homescreen etc), i think this is not valid anymore, it can be closed and eventually opened a new one if in a future image plasma-device will again crash at startup

from the backtrace seemed due to a parse error in the home screen (would need the console out put to be really sure)
in that case is fixed for sure now