Bug 263432 - Dolphin crash onn closing
Summary: Dolphin crash onn closing
Status: RESOLVED DUPLICATE of bug 257944
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-17 16:22 UTC by dan
Modified: 2011-01-17 19:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dan 2011-01-17 16:22:00 UTC
Application: dolphin (1.6)
KDE Platform Version: 4.5.95 (4.6 RC2)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-default i686
Distribution: "openSUSE 11.4 Milestone 5 of 6 (i586)"

-- Information about the crash:
- What I was doing when the application crashed: closing program and i always get this error message Idont think this is normal

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Aborted
[KCrash Handler]
#7  0xffffe430 in __kernel_vsyscall ()
#8  0xb5ff38bf in raise () from /lib/libc.so.6
#9  0xb5ff5200 in abort () from /lib/libc.so.6
#10 0xb602fdb7 in __libc_message () from /lib/libc.so.6
#11 0xb6035ddb in malloc_printerr () from /lib/libc.so.6
#12 0xb603a929 in free () from /lib/libc.so.6
#13 0xb61e5b1f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0xb61c673b in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep::_M_destroy(std::allocator<char> const&) () from /usr/lib/libstdc++.so.6
#15 0xb61c67ea in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/libstdc++.so.6
#16 0xb5ff68bf in __run_exit_handlers () from /lib/libc.so.6
#17 0xb5ff691d in exit () from /lib/libc.so.6
#18 0x0804e539 in _start ()

Possible duplicates by query: bug 263371, bug 263367, bug 263361, bug 263325, bug 263258.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2011-01-17 19:24:18 UTC
Thanks for the bug report! This crash has been reported already.

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