compiz.real crashed with SIGSEGV

[Ton]

Intrepid 8.10

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/compiz.real
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.7.8-0ubuntu4
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --loose-binding core ccp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: compiz
Stacktrace: #0 0xb7be0f7b in ?? () from /usr/lib/libGL.so.1
StacktraceTop: ?? () from /usr/lib/libGL.so.1
ThreadStacktrace:
 .
 Thread 1 (process 6442):
 #0 0xb7be0f7b in ?? () from /usr/lib/libGL.so.1
Title: compiz.real crashed with SIGSEGV
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Marlon Cisternas Milla (mcisternas-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[Ton (ton-groenestein)]

On za, 2008-10-18 at 15:04 +0000, Luke Faraone wrote:
> ** Changed in: compiz (Ubuntu)
> Sourcepackagename: None => compiz
> Dear Luke: I do not know what you mean. I am just a beginner in Intrepid

[Ton (ton-groenestein)]

On za, 2008-10-18 at 15:14 +0000, Marlon Cisternas Milla wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we can't fix it because your description
> didn't include enough information. You may find it helpful to read "How
> to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem.
>
> We have instructions on debugging some types of problems at
> http://wiki.ubuntu.com/DebuggingProcedures
>
> At a minimum, we need:
> 1. the specific steps or actions you took that caused you to encounter the problem,
> 2. the behavior you expected, and
> 3. the behavior you actually encountered (in as much detail as possible).
> Thanks!
>
> ** Changed in: compiz (Ubuntu)
> Status: New => Incomplete
>
Sorry I cannot help you at this time because I am not known with all the
commands etc . I am a newly on Ubuntu 8.10. I just followed some
commands form the Ubuntu Intrepid page, which was toled to be very
interesting and the bug report screen showed up. I filled it in and sent
the report. Although I have had this problem on more occasions the last
couple of weeks and I did not know what to do with it. I closed all the
screen and went on. I have no recollection of it. I think i must be more
carefull with what Iam installing because it is all so new.
What is compiz really doing.

[Ton (ton-groenestein)]

Sorry I cannot help you at this time because I am not known with all the
commands etc . I am a newly on Ubuntu 8.10. I just followed some
commands form the Ubuntu Intrepid page, which was toled to be very
interesting and the bug report screen showed up. I filled it in and sent
the report. Although I have had this problem on more occasions the last
couple of weeks and I did not know what to do with it. I closed all the
screen and went on. I have no recollection of it. I think i must be more
carefull with what Iam installing because it is all so new.
What is compiz really doing.

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/libGL.so.1

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!