Bug 289963 - Plasma Active Won't Start
Summary: Plasma Active Won't Start
Status: RESOLVED FIXED
Alias: None
Product: Active
Classification: Plasma
Component: General (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: unscheduled
Assignee: active
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-27 23:06 UTC by Peter Mui
Modified: 2012-04-11 08:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Mui 2011-12-27 23:06:08 UTC
Application: plasma-device (1.0)
KDE Platform Version: 4.7.2 (4.7.2) "release 5"
Qt Version: 4.7.4
Operating System: Linux 3.1.0-1.2-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

-- Information about the crash:
I've tried several clean installs on two different EXOPCs and I keep getting the same result.

I install OpenSUSE 12.1 and apply all the updates.  Then I follow the instructions to install Plasma Active, but when I reboot I get the error:

We are sorry, Plasma Workspace closed unexpectedly.

Executable plasma-device PID: 17xx Signal: Segmentation Fault (11)

The the touch capability and on-screen keyboard seem to work.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Workspace (plasma-device), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f649c70a760 (LWP 1713))]

Thread 2 (Thread 0x7f6484f29700 (LWP 1714)):
#0  0x00007f6492efce6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f6496436852 in ?? () from /usr/lib64/libQtScript.so.4
#2  0x00007f6496436889 in ?? () from /usr/lib64/libQtScript.so.4
#3  0x00007f6492ef8f05 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f649c02a53d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f649c70a760 (LWP 1713)):
[KCrash Handler]
#6  QObject::property (this=0x0, name=0x7f6482dcfa67 "childrenPositions") at kernel/qobject.cpp:3459
#7  0x00007f6482dcd3ff in WindowStrip::updateFrame (this=0x982bc0) at /usr/src/debug/plasma-mobile/applets/windowstrip/windowstrip.cpp:143
#8  0x00007f6482dce325 in WindowStrip::scrollChanged (this=0x982bc0) at /usr/src/debug/plasma-mobile/applets/windowstrip/windowstrip.cpp:114
#9  0x00007f6482dce5af in WindowStrip::WindowStrip (this=0x982bc0, parent=<optimized out>) at /usr/src/debug/plasma-mobile/applets/windowstrip/windowstrip.cpp:71
#10 0x00007f6482dcf351 in WindowStripApplet::graphicsWidget (this=0x993480) at /usr/src/debug/plasma-mobile/applets/windowstrip/applet.cpp:60
#11 0x00007f649bb543aa in ?? () from /usr/lib64/libplasma.so.3
#12 0x00007f649bb54cb2 in Plasma::Corona::importLayout(KConfigGroup const&) () from /usr/lib64/libplasma.so.3
#13 0x00007f649c3042a5 in MobCorona::loadDefaultLayout (this=0x7df100) at /usr/src/debug/plasma-mobile/shell/mobcorona.cpp:153
#14 0x00007f649bb54f5c in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib64/libplasma.so.3
#15 0x00007f649c309392 in PlasmaApp::corona (this=0x62a8b0) at /usr/src/debug/plasma-mobile/shell/plasmaapp.cpp:335
#16 0x00007f649c309b8a in PlasmaApp::PlasmaApp (this=0x62a8b0) at /usr/src/debug/plasma-mobile/shell/plasmaapp.cpp:163
#17 0x00007f649c309f85 in PlasmaApp::self () at /usr/src/debug/plasma-mobile/shell/plasmaapp.cpp:76
#18 0x00007f649c3033f7 in kdemain (argc=1, argv=0x7fff3f4aba18) at /usr/src/debug/plasma-mobile/shell/main.cpp:59
#19 0x00007f649bf7223d in __libc_start_main () from /lib64/libc.so.6
#20 0x0000000000400691 in _start () at ../sysdeps/x86_64/elf/start.S:113

Reported using DrKonqi
Comment 1 Carl Symons 2011-12-27 23:41:51 UTC
My ExoPC Slate has a 32 bit CPU (i686), not x86_64.
Comment 2 Peter Mui 2011-12-28 00:22:32 UTC
Hi Carl:

Thanks for looking at my bug. If I understand your email correctly, you suspect that the problem is that I'm using the 64-bit version of OpenSUSE 12.1?  That may be the issue, but my understanding is that the Intel Atom N450 in the EXOPC has 64-bit support.  Also: I had another EXOPC running OpenSUSE 12.1 64-bit / Plasma Active One and upgraded them to Plasma Active Two without issue.  I started running into trouble when I tried clean installs in the last couple of days on these two other EXOPCs.

Happy Holidays, -Peter


On Dec 27, 2011, at 3:41 PM, Carl Symons wrote:

> https://bugs.kde.org/show_bug.cgi?id=289963
> 
> 
> 
> 
> 
> --- Comment #1 from Carl Symons <carlsymons gmail com>  2011-12-27 23:41:51 ---
> My ExoPC Slate has a 32 bit CPU (i686), not x86_64.
> 
> -- 
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
Comment 3 Carl Symons 2011-12-28 02:41:13 UTC
Hi Peter,

I'm delighted that you're experimenting with Plasma Active on the ExoPC.

I'm not the swiftest cheetah in the race on this stuff. 

All I know is that I saw x86_64 and knew that I had installed 32 bit. My uname -m shows i686. Yet /proc/cpuinfo on the ExoPC, shows the lm flag, so you're probably right about the CPU.

http://www.exopc.com/devices/ for ExoPC Slate...installed OS is Microsoft Windows 7 Home Premium, 32-bit Edition. Hmmm.

Mine is working fine with 32 bit Balsam 12.1 iso image. One of the lead Plasma Active developers is associated with open-slx and works to make sure that their ISOs work right.

The instructions at community.kde.org/Plasma/Active/Installation say to 
install openSUSE 12.1 Live KDE via USB stick from the [link: openSUSE download page]. That kinda leaves it up to the user to decide the format--64 or 32 bit. 

However, I had good luck with the live Balsam ISO from open-slx. Link [download.open-slx.com/iso] on community.kde.org/Plasma/Active/Installation>>Install Plasma Active on x86 Systems>>Live Images>>Balsam Professional
Comment 4 Marco Martin 2012-04-11 08:50:27 UTC
this crash was in the windowstrip applet.
this applet is not used/doesn't exist anymore.