krunner_lock crashed with SIGSEGV

[Roosje]

Binary package hint: kdebase-workspace

after update to alpha 6 of I.I. ALso Nvidia driver was not working, had to revert back to nv driver.

ProblemType: Crash
Architecture: i386
Disassembly: 0x0:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/kde4/libexec/krunner_lock
Package: kdebase-workspace-bin 4:4.1.1-0ubuntu9
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/kde4/libexec/krunner_lock
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LANGUAGE=en_US
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace:
 #0 0x00000000 in ?? ()
 #1 0xb80bfbe4 in ?? () from /lib/ld-linux.so.2
 #2 0xb80b282f in ?? () from /lib/ld-linux.so.2
StacktraceTop:
 ?? ()
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/ld-linux.so.2
ThreadStacktrace:
 .
 Thread 1 (process 21543):
 #0 0x00000000 in ?? ()
 #1 0xb80bfbe4 in ?? () from /lib/ld-linux.so.2
 #2 0xb80b282f in ?? () from /lib/ld-linux.so.2
Title: krunner_lock crashed with SIGSEGV
Uname: Linux 2.6.27-4-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
_dl_init_internal () from /lib/ld-linux.so.2
_dl_start_user () from /lib/ld-linux.so.2

[Jonathan Thomas (echidnaman)]

So what exactly was happening when this crash occurred?
If it's reproducible, could you install kdebase-workspace-dbg and try to get it to crash again so we can get a better backtrace? It seems apport didn't want to retrace.

[Roosje (wilco-roos)]

I will try, back in a sec (i hope ;-) )

On Fri, Sep 26, 2008 at 2:33 PM, Jonathan Thomas <email address hidden>wrote:

> So what exactly was happening when this crash occurred?
> If it's reproducible, could you install kdebase-workspace-dbg and try to
> get it to crash again so we can get a better backtrace? It seems apport
> didn't want to retrace.
>
> ** Changed in: kdebase-workspace (Ubuntu)
> Status: New => Incomplete
>
> --
> krunner_lock crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/274705
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Jonathan Thomas (echidnaman)]

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!