| Summary: | Pressing Ctrl-Tab crashes konqueror (kde4) | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Federico Asara <ze4lot> |
| Component: | general | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Federico Asara
2008-03-15 19:02:16 UTC
Crashed from Ubuntu Hardy output: 0xb7fc6410 in __kernel_vsyscall () [Current thread is 0 (process 7873)] Thread 1 (Thread 0xb64d8720 (LWP 7873)): #0 0xb7fc6410 in __kernel_vsyscall () #1 0xb7e32ba6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7e329b7 in sleep () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7928000 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5 #4 0x00000001 in ?? () #5 0x00000000 in ?? () #0 0xb7fc6410 in __kernel_vsyscall () This report is not very useful. You should give more information for reproducing the crash. Moreover the backtrace should be done with the debug packages. http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How_to_create_useful_crash_reports Does it still happen to you in any recent version of KDE 4? |