Bug 159365 - Pressing Ctrl-Tab crashes konqueror (kde4)
Summary: Pressing Ctrl-Tab crashes konqueror (kde4)
Status: RESOLVED DUPLICATE of bug 163778
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-15 19:02 UTC by Federico Asara
Modified: 2008-06-11 13:07 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 Federico Asara 2008-03-15 19:02:16 UTC
Version:           4.0.2 (KDE 4.0.2) (using 4.0.2 (KDE 4.0.2), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-12-generic

If you press Ctrl-Tab konqueror crashes. Tested on KDE4 from Kubuntu Hardy. 
I couldn't find debugging symbols packages anywhere, thus I don't have an useful backtrace.
It will crash, regardless of what you were doing.
Comment 1 Daniel Costalis 2008-03-27 22:36:52 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 ()
Comment 2 Eduardo Robles Elvira 2008-06-05 17:23:05 UTC
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?
Comment 3 Christophe Marin 2008-06-11 13:07:04 UTC
closing as dup of 163778 (which has an useful backtrace)

*** This bug has been marked as a duplicate of 163778 ***