Bug 263371 - Errores de Dolphin al cerrar
Summary: Errores de Dolphin al cerrar
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-16 23:28 UTC by josuenodre
Modified: 2011-01-17 15:34 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 josuenodre 2011-01-16 23:28:09 UTC
Application: dolphin (1.6)
KDE Platform Version: 4.5.95 (4.6 RC2)
Qt Version: 4.7.1
Operating System: Linux 2.6.34.7-0.7-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
Dolphin da error al cerrar y al terminar de copiar un archivo impidiendo que se copie correctamente

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Aborted
[KCrash Handler]
#7  0xffffe430 in __kernel_vsyscall ()
#8  0xb5fad7ff in raise () from /lib/libc.so.6
#9  0xb5faf140 in abort () from /lib/libc.so.6
#10 0xb5fe9fd7 in __libc_message () from /lib/libc.so.6
#11 0xb5fefffb in malloc_printerr () from /lib/libc.so.6
#12 0xb5ff4b49 in free () from /lib/libc.so.6
#13 0xb619f98f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0xb618005b 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 0xb618010a in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/libstdc++.so.6
#16 0xb5fb07cf in __run_exit_handlers () from /lib/libc.so.6
#17 0xb5fb082d in exit () from /lib/libc.so.6
#18 0x0804e529 in _start ()

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

Reported using DrKonqi
Comment 1 Frank Reininghaus 2011-01-17 15:34:46 UTC
Thanks for the bug report! This issue has been reported already.

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