Bug 158251 - plasma crashes with composite
Summary: plasma crashes with composite
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-23 01:51 UTC by Alexander
Modified: 2008-06-01 06:46 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2008-02-23 01:51:03 UTC
Version:           0.0 (using 4.0.1 (KDE 4.0.x >=20080201) "release 12.6", compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.22.17-0.1-default

the kde4 is severous crashes in all aplications, conflict with composite enable
Comment 1 Aaron J. Seigo 2008-02-23 01:58:15 UTC
can you provide a backtrace? or does your X session simply not start if compositing features in kwin are turned on?
Comment 2 Aaron J. Seigo 2008-02-23 01:58:35 UTC
can you provide a backtrace? or does your X session simply not start if compositing features in kwin are turned on? if so, can you state what your graphics hardware and x.org driver are?

thanks.
Comment 3 Alexander 2008-02-23 04:05:27 UTC
Hello!
Before more nothing it would like to give the congratulations to the all of team KDE for the beautiful work that comes being done in kde4, using to advantage I I would like to suggest that it was incorporated plasma as window decoration or to incorporate kde4 looking very glass or compiz-fusion becoming the transparent windows particularly taste of this glass effect, good is this, congratulations to the all and success to kde.

Backtrace

[?1034h(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb57186f0 (LWP 8964)]
[New Thread 0xb3a89b90 (LWP 8966)]
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 8964)]

Thread 2 (Thread 0xb3a89b90 (LWP 8966)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb722b566 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb72819e8 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0xb3ed6037 in ?? () from /usr/lib/kde4/plasma_containment_desktop.so
#4  0x080edd14 in ?? ()
#5  0x080edd10 in ?? ()
#6  0xffffffff in ?? ()
#7  0xb3a89250 in ?? ()
#8  0xb3a8930c in ?? ()
#9  0xb7224170 in ?? () from /lib/libpthread.so.0
#10 0xb3ed950a in ?? () from /usr/lib/kde4/plasma_containment_desktop.so
#11 0xb7aad040 in ?? () from /usr/lib/libkdeui.so.5
#12 0xb3ed9511 in ?? () from /usr/lib/kde4/plasma_containment_desktop.so
#13 0xb7419788 in ?? ()
#14 0xb3a892dc in ?? ()
#15 0xb3a892c4 in ?? ()
#16 0x080edd10 in ?? ()
#17 0xb3a892b4 in ?? ()
#18 0xb3a89324 in ?? ()
#19 0xb3a89314 in ?? ()
#20 0xb64c2ff4 in ?? () from /usr/lib/libgthread-2.0.so.0
#21 0xb3a892e8 in ?? ()
#22 0xb3a891e8 in ?? ()
#23 0x3f800000 in ?? ()
#24 0x00000000 in ?? ()

Thread 1 (Thread 0xb57186f0 (LWP 8964)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb66a18d6 in nanosleep () from /lib/libc.so.6
#2  0xb66a16b7 in sleep () from /lib/libc.so.6
#3  0xb79b87b9 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()

----------------------------------------
[bugs.kde.org quoted mail]

_________________________________________________________________
Veja mapas e encontre as melhores rotas para fugir do tr
Comment 4 S. Burmeister 2008-02-23 09:39:02 UTC
> [?1034h(no debugging symbols found)
> Using host libthread_db library "/lib/libthread_db.so.1".
> (no debugging symbols found)
> (no debugging symbols found)


A backtrace with the above lines is useless, please install the debuginfo 
packages provided by your distro in order to provide useful backtraces 
including debugging symbols.
Comment 5 Jason Stubbs 2008-06-01 06:46:18 UTC
With 4.1 just around the corner, it's time to close off 4.0 bugs. If you get similar crashes with 4.1 please open a new bug with a full backtrace.