https://bugzilla.novell.com/show_bug.cgi?id=281249 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kde-maintainers@suse.de |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=281249 ------- Comment #2 from markus.kossmann@gmx.de 2007-06-06 09:37 MST ------- (In reply to comment #1)

What are the steps to reproduce?

This crash was produced by starting konqueror from a konsole window ( without any arguments). But before that two instances of konqueror saved in the KDE desktop were already crashed at startup of KDE ( runlevel 5, kdm ). Now, after a reboot, I've catched a slighly different looking crash with the crashmanager from the instance at KDE startup. Überprüfung der Systemkonfiguration beim Start deaktiviert. Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47555487469632 (LWP 6696)] [KCrash handler] #5 0x00002b405b97b3c0 in strncpy () from /lib64/libc.so.6 #6 0x00002b405a3be994 in trim () from /opt/kde3/lib64/libkdecore.so.4 #7 0x00002b405a3bf542 in lt_dlopen () from /opt/kde3/lib64/libkdecore.so.4 #8 0x00002b405a34f753 in KLibLoader::library () from /opt/kde3/lib64/libkdecore.so.4 #9 0x00002b4059dca6e5 in KURIFilter::loadPlugins () from /opt/kde3/lib64/libkio.so.4 #10 0x00002b4059dca835 in KURIFilter::self () from /opt/kde3/lib64/libkio.so.4 #11 0x00002b406060ba42 in KonqMisc::konqFilteredURL () from /opt/kde3/lib64/libkdeinit_konqueror.so #12 0x00002b40606445ae in kdemain () from /opt/kde3/lib64/libkdeinit_konqueror.so #13 0x00000000004074a1 in launch () #14 0x0000000000407dd4 in handle_launcher_request () #15 0x00000000004082ac in handle_requests () #16 0x00000000004091ea in main () If I start konqueror from the Konsole commandline after that crash I can reproduce the first crashlog. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=281249 markus.kossmann@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #4 from markus.kossmann@gmx.de 2007-06-09 09:33 MST ------- The update to kdebase3-3.5.7-23.2. reintroduces the bug :-( It seems that only running konqueror as webbrowser triggers the bug A gdb session shows : mk@PC1:~> gdb /opt/kde3/bin/konqueror GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-suse-linux"...Using host libthread_db library "/lib64/libthread_db.so.1". (gdb) run Starting program: /opt/kde3/bin/konqueror [Thread debugging using libthread_db enabled] [New Thread 47777363063904 (LWP 21204)] konqueror: WARNING: KGenericFactory: instance requested but no instance name or about data passed to the constructor! Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47777363063904 (LWP 21204)] 0x00002b7401dd03c0 in strncpy () from /lib64/libc.so.6 (gdb) bt #0 0x00002b7401dd03c0 in strncpy () from /lib64/libc.so.6 #1 0x00002b740380e994 in trim () from /opt/kde3/lib64/libkdecore.so.4 #2 0x00002b740380f542 in lt_dlopen () from /opt/kde3/lib64/libkdecore.so.4 #3 0x00002b740379f753 in KLibLoader::library () from /opt/kde3/lib64/libkdecore.so.4 #4 0x00002b7402584853 in KParts::Plugin::loadPlugin () from /opt/kde3/lib64/libkparts.so.2 #5 0x00002b740258f558 in KParts::Plugin::loadPlugins () from /opt/kde3/lib64/libkparts.so.2 #6 0x00002b74025904c9 in KParts::PartBase::setInstance () from /opt/kde3/lib64/libkparts.so.2 #7 0x00002b740ab6848b in KHTMLPart::KHTMLPart () from /opt/kde3/lib64/libkhtml.so.4 #8 0x00002b740cf24f76 in KonqAboutPage::KonqAboutPage () from /opt/kde3/lib64/kde3/konq_aboutpage.so #9 0x00002b740cf2510a in KonqAboutPageFactory::createPartObject () from /opt/kde3/lib64/kde3/konq_aboutpage.so ---Type <return> to continue, or q <return> to quit--- #10 0x00002b740257d3d4 in KParts::Factory::createPart () from /opt/kde3/lib64/libkparts.so.2 #11 0x00002b7401ab3d07 in KonqViewFactory::create () from /opt/kde3/lib64/libkdeinit_konqueror.so #12 0x00002b7401ab4177 in KonqFrame::attach () from /opt/kde3/lib64/libkdeinit_konqueror.so #13 0x00002b7401ab42ab in KonqView::switchView () from /opt/kde3/lib64/libkdeinit_konqueror.so #14 0x00002b7401ab4b9e in KonqView::changeViewMode () from /opt/kde3/lib64/libkdeinit_konqueror.so #15 0x00002b7401ab8305 in KonqMainWindow::openView () from /opt/kde3/lib64/libkdeinit_konqueror.so #16 0x00002b7401ac13dd in KonqViewManager::loadItem () from /opt/kde3/lib64/libkdeinit_konqueror.so #17 0x00002b7401ac3617 in KonqViewManager::loadViewProfile () from /opt/kde3/lib64/libkdeinit_konqueror.so #18 0x00002b7401ac4cf1 in KonqMisc::createBrowserWindowFromProfile () from /opt/kde3/lib64/libkdeinit_konqueror.so ---Type <return> to continue, or q <return> to quit--- #19 0x00002b7401ac8f1d in kdemain () from /opt/kde3/lib64/libkdeinit_konqueror.so #20 0x00002b7401d79ae4 in __libc_start_main () from /lib64/libc.so.6 #21 0x0000000000400599 in _start () -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=281249 ------- Comment #6 from markus.kossmann@gmx.de 2007-06-13 20:37 MST ------- Since I was running a KOTD when installing the kde update and it went away when reinstalling the kde rpms when running a good kernel, I think now that it's triggered by filesystem corruption caused by bug #284002. However I think that shouldn't happen, even with damaged files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=281249#c8 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|schwab@novell.com |bnc-team-screening@forge.provo.novell.com --- Comment #8 from Andreas Schwab 2007-08-13 08:59:36 MST --- This is definitely wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=281249#c10 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|schwab@novell.com | --- Comment #10 from Andreas Schwab 2007-08-13 09:51:55 MST --- The patch. There is no bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=281249#c11 Dirk Mueller changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |schwab@novell.com --- Comment #11 from Dirk Mueller 2007-08-13 15:04:59 MST --- well, in the presense of NUL bytes, strlen() is definitely wrong. the issue is that fgets() succeeds, but that broken while loop believes it didn't find a end-of-line, and reallocates memory until the machine crashes. I'm fine with you ignoring the patch, given that its fixed for KDE already, but there is a bug otherwise it wouldn't have been reproted in the first place. it is also very easy to reproduce (I can give you a sample .la) file and it is an easy to fix issue, given that I even included a patch. In case you say that a .la file should not contain NUL bytes and that crashing is valid behaviour: well, then close the bug. My part is done, stop reassigning it. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.