Bug 263492 - K3B crash on close
Summary: K3B crash on close
Status: RESOLVED DUPLICATE of bug 257944
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Michał Małek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-18 00:17 UTC by mrdocs
Modified: 2011-01-18 02:49 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 mrdocs 2011-01-18 00:17:27 UTC
Application: k3b (2.0.2)
KDE Platform Version: 4.5.95 (4.6 RC2)
Qt Version: 4.7.1
Operating System: Linux 2.6.34.7-0.5-desktop i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:

Burned 2 DVD data discs sucessfully then burned an audio CD which had errors, then on closing the crash

-- Backtrace:
Application: K3b (k3b), signal: Aborted
[KCrash Handler]
#7  0xffffe424 in __kernel_vsyscall ()
#8  0xb41707ff in raise () from /lib/libc.so.6
#9  0xb4172140 in abort () from /lib/libc.so.6
#10 0xb41acfd7 in __libc_message () from /lib/libc.so.6
#11 0xb41b2ffb in malloc_printerr () from /lib/libc.so.6
#12 0xb41b7b49 in free () from /lib/libc.so.6
#13 0xb438098f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0xb436105b 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 0xb436110a in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/libstdc++.so.6
#16 0xb41737cf in __run_exit_handlers () from /lib/libc.so.6
#17 0xb417382d in exit () from /lib/libc.so.6
#18 0xb415bc16 in __libc_start_main () from /lib/libc.so.6
#19 0x08080691 in _start ()

Possible duplicates by query: bug 263477, bug 263361, bug 263325, bug 263203, bug 262977.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-01-18 02:49:47 UTC

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