Bug 179247 - Executing Actions on Plasmoids causes whole KDE4 Workspace Crash only with Desktop Effects Enabled.
Summary: Executing Actions on Plasmoids causes whole KDE4 Workspace Crash only with De...
Status: RESOLVED UPSTREAM
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-01 01:06 UTC by Cameron Seader
Modified: 2009-01-02 21:20 UTC (History)
3 users (show)

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


Attachments
.xsession-errors received (39.03 KB, application/octet-stream)
2009-01-02 20:17 UTC, Cameron Seader
Details
Xorg.0.log output (30.14 KB, text/x-log)
2009-01-02 20:25 UTC, Cameron Seader
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cameron Seader 2009-01-01 01:06:42 UTC
Version:           4.1.86 (using Devel)
OS:                Linux
Installed from:    Compiled sources

This only occurs when Desktop Effects are enabled.
Here are two scenarios that can most certainly cause a crash..

Desktop Folder Plasmoid:
If i right click in the Plasmoid and select Create > New Text File Plasma Crashes

Picture Frame Plasmoid:
If i right Click and go to Picture Frame Settings > Select a Picture then Plasma Crashes

What do you need to debug this... Where can i get the backtraces?
Comment 1 Dario Andres 2009-01-01 01:51:19 UTC
You can read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and then post a complete backtrace here. Thanks :)
Comment 2 Cameron Seader 2009-01-02 18:31:09 UTC
OK... I have read the information from Comment #1 but i still don't see where i can gain a backtrace when the whole Desktop environment crashes. Do i need to start kde from within gdb or valgrind? We are not talking a specific application.. the whole Desktop Environment crashes and it takes me back to a login screen. I just installed the version 4.1.87 and its crashing on this as well. Please let me know how to proceed. Is there a way to tell KDE to spit out a crash dump or something. maybe i need to set ulimit -c unlimited so i can get a core file.
Comment 3 Cameron Seader 2009-01-02 18:45:31 UTC
I get this kernel message whenever it crashes with the initial comments Scenario's 

Jan  2 10:21:34 seaderx kernel: nepomukservices[9577] general protection ip:7fe0cda4a37e sp:7fffd60357d0 error:0 in libQtCore.so.4.4.3[7fe0cd9ee000+223000]

I also get this message as well...

kdm[2597]: X server for display :0 terminated unexpectedly

so is nepomukservices giving a general protection fault when i execute those scenario's?? or is it with libQtCore

Comment 4 Michael Leupold 2009-01-02 19:57:33 UTC
When you're taken back to kdm, please try checking $HOME/.xsession-errors which might have some useful information. Apart from that it sounds like either ksmserver or your display driver (X11) are crashing. Please also check your xorg logfile, eg. /var/log/Xorg.0.log.
Comment 5 Cameron Seader 2009-01-02 20:17:44 UTC
Created attachment 29837 [details]
.xsession-errors received
Comment 6 Cameron Seader 2009-01-02 20:18:44 UTC
I am not sure about the xsession-errors received.. I looked at my /var/log/Xorg.0.log and its clean.. Also attached. 
Comment 7 Aaron J. Seigo 2009-01-02 20:22:14 UTC
this is a bug in x.org and/or the driver. the only reason you crash out to the
log in is if there is a bug in the x server or the driver. an application
should never be able to crash the xserver, and given that it happens only when
desktop effects are enabled says it's almost certainly the x.org driver.
Comment 8 Cameron Seader 2009-01-02 20:25:12 UTC
Created attachment 29838 [details]
Xorg.0.log output
Comment 9 Cameron Seader 2009-01-02 21:20:30 UTC
I figured it out... It Certainly Xorg.. I have an Intel Video.. and i enabled XAA as the Accel method for intel driver.. because its smoother.. but XAA is what is causing this problem to occur.. as soon as i go back to EXA which is the default Accel Method for intel driver then this problem does not occur any more.