Version: 0.11.23-3 (using KDE KDE 3.5.0) Installed from: Fedora RPMs Compiler: Fedora Core 4 OS: Linux Startup application via menubar or commandline and the splash screen comes up. Splash screen disappears and "K3b- The KDE Crash Handler" comes up with the following general info and backtrace info. General info="caused signal 11 (SIGSEGV)" Backtrace= (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209054368 (LWP 3118)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #4 0x00967483 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 #5 0x03ebdc65 in Arts::readTypeSeq<Arts::InterfaceDef> () from /usr/lib/libmcop.so.1 #6 0x03eb2c28 in Arts::ModuleDef::readType () from /usr/lib/libmcop.so.1 #7 0x03eb30aa in Arts::ModuleDef::ModuleDef () from /usr/lib/libmcop.so.1 #8 0x03ede36f in Arts::IDLFileReg::startup () from /usr/lib/libmcop.so.1 #9 0x03ee65f2 in Arts::StartupManager::startup () from /usr/lib/libmcop.so.1 #10 0x03ec71d5 in Arts::Dispatcher::Dispatcher () from /usr/lib/libmcop.so.1 #11 0x03fdc209 in KArtsDispatcher::KArtsDispatcher () from /usr/lib/libartskde.so.1 #12 0x0808a5c0 in KFileTreeView::slotSetNextUrlToSelect () #13 0x0809b86e in QValueList<int>::detachInternal () #14 0x0809f228 in QValueList<int>::detachInternal () #15 0x0808194b in QValueListPrivate<QString>::QValueListPrivate () #16 0x080a003f in QPtrList<K3bPluginFactory>::~QPtrList () #17 0x00aedd5f in __libc_start_main () from /lib/libc.so.6 #18 0x0807e0f1 in ?? ()
Distribution bug. File upstream and tell them to stop being stubborn. *** This bug has been marked as a duplicate of 111115 ***
That's all well and good but..... 1. I don't have an acinclude.m4.in file 2. I do have /usr/share/libtool/libltdl/acinclude.m4 but there is no fvisibility option in that file. Does this mean it's a separate bug? On 18 Dec 2005 23:15:27 -0000, Thiago Macieira <thiago@kde.org> wrote: [bugs.kde.org quoted mail] -- 'You can get more with a kind word and a two-by-four than you can with just a kind word' - Marcus, B5 That's all well and good but.....<br> <br> 1. I don't have an <a href="http://acinclude.m4.in">acinclude.m4.in</a> file<br> 2. I do have /usr/share/libtool/libltdl/acinclude.m4<br> but there is no fvisibility option in that file.<br> <br> Does this mean it's a separate bug?<br><br><div><span class="gmail_quote">On 18 Dec 2005 23:15:27 -0000, <b class="gmail_sendername">Thiago Macieira</b> <<a href="mailto:thiago@kde.org">thiago@kde.org</a>> wrote:</span> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter. <br><br><a href="http://bugs.kde.org/show_bug.cgi?id=118607">http://bugs.kde.org/show_bug.cgi?id=118607</a><br>thiago kde org changed:<br><br> What |Removed |Added<br>----------------------------------------------------------------------------<br> Status|UNCONFIRMED |RESOLVED<br> Product|k3b |arts<br> Resolution| |DUPLICATE<br><br><br><br>------- Additional Comments From thiago kde org 2005-12-19 00:15 -------<br>Distribution bug. File upstream and tell them to stop being stubborn.<br><br>*** This bug has been marked as a duplicate of 111115 *** <br></blockquote></div><br><br clear="all"><br>-- <br>'You can get more with a kind word and a two-by-four than you can with just a kind word' - Marcus, B5
I could have agreed if I hadn't just seen another Fedora issue exactly alike, but in another program. The pool allocator in g++ is broken. Distributions turning it on are, therefore, broken.
Reopening. Three very similar bugs have been reported. Maybe it warrants special attention, though I still think it's the pool allocator's fault.
*** Bug 118631 has been marked as a duplicate of this bug. ***
*** Bug 118613 has been marked as a duplicate of this bug. ***
Maks, what do you think?
*** Bug 118663 has been marked as a duplicate of this bug. ***
My experiences, for what it's worth.... I'm running fedora core 4 on AMD64. Starting 2005-12-16 I noticed some problems on my system. KDE panel (kicker) was the first to crash when I logged-out. Today I also had the problem with k3b. These issues clearly have something to do with the latest updates I received during some nightly yum updates. I tried the previous kernel but it didn't solve the problem. For the time being I switched to Gnome and it doesn't crash when I log-out. :) The following packages were installed/updated since 2005-12-16: Package Installed: kernel.x86_64 2.6.14-1.1653_FC4 Package Updated: perl.x86_64 3:5.8.6-22 cups-libs.x86_64 1:1.1.23-15.2 xterm.x86_64 207-1.FC4 kbd.x86_64 1.12-10.fc4.1 dhclient.x86_64 10:3.0.2-26.FC4 cups.x86_64 1:1.1.23-15.2 kdenetwork.x86_64 7:3.5.0-0.1.fc4 kdeutils.x86_64 6:3.5.0-0.1.fc4 kdelibs.x86_64 6:3.5.0-0.1.fc4 kdepim.x86_64 6:3.5.0-0.2.fc4 kdebase.x86_64 6:3.5.0-0.1.fc4 kdemultimedia.x86_64 6:3.5.0-0.1.fc4 kdegraphics.x86_64 7:3.5.0-0.1.fc4 arts.x86_64 8:1.5.0-0.1.fc4 kdeaddons.x86_64 3.5.0-0.1.fc4 kdeartwork.x86_64 3.5.0-0.1.fc4 I hope this information is usefull to you and helps you to isolate the cause of the problems.
*** Bug 118750 has been marked as a duplicate of this bug. ***
Can someone who experienced this problem report this to Fedora and paste the link to the bug report here?
There is a fedora bugzilla report at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176126 Mike
*** Bug 118851 has been marked as a duplicate of this bug. ***
According to the comments on the Red Hat Bugzilla, this has been fixed by rebuilding the package. This is, therefore, not a KDE bug. Everyone, please just upgrade your k3b installations.
*** Bug 118897 has been marked as a duplicate of this bug. ***
The fedora updates issued a new rpm which has gone to the mirror sites, so anyone running a yum update in the past day or so will now have the updated version of k3b (k3b-0.12.10-0.fc4.1) which works without problems in Fedora Core 4 under KDE 3.5 Mike