[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#475435: marked as done (konqueror: crash going to Settings -> Configure Konqueror -> Enhanced Browsing, reproducible)

Your message dated Sat, 23 May 2009 22:40:43 +0200
with message-id <20090523204043.GA27902@ana.debian.net>
and subject line Re: Bug#475435: konqueror: crash going to Settings -> Configure Konqueror -> Enhanced Browsing, reproducible
has caused the Debian Bug report #475435,
regarding konqueror: crash going to Settings -> Configure Konqueror -> Enhanced Browsing, reproducible
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
475435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475435
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: konqueror
Version: 4:3.5.9.dfsg.1-2+b1
Severity: important

Same crash happens at least at the Proxies menu, too (which is the case
I'm describing below).

A KDE Control Module dialog says:

"
The module Proxies is not a valid configuration module.




The diagnostics is:
The desktop file Settings/Browsing/Web/proxy.desktop does not specify a library.
"

I assume that the crash happens directly after launching this
KDE Control Module dialog, most likely due to bad handling of this error case
(dunno what actually causes the error dialog above, but at least it certainly
shouldn't crash after displaying this error dialog).

Backtrace is:
(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 0xb68af8d0 (LWP 13584)]
(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)
[KCrash handler]
#5  0xb7c7b850 in KCModuleProxy::realModule () from /usr/lib/libkutils.so.1
#6  0xb7c7c412 in KCModuleProxy::buttons () from /usr/lib/libkutils.so.1
#7  0xb7c7c4b3 in KCMultiDialog::slotAboutToShow ()
   from /usr/lib/libkutils.so.1
#8  0xb7c7d1ab in KCMultiDialog::qt_invoke () from /usr/lib/libkutils.so.1
#9  0xb715cf6d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb7ac9591 in KDialogBase::aboutToShowPage () from /usr/lib/libkdeui.so.4
#11 0xb7ac9620 in KDialogBase::qt_emit () from /usr/lib/libkdeui.so.4
#12 0xb7c6564d in KCMultiDialog::qt_emit () from /usr/lib/libkutils.so.1
#13 0xb715cfb1 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0xb7ac946e in KJanusWidget::aboutToShowPage () from /usr/lib/libkdeui.so.4
#15 0xb7ac94cc in KJanusWidget::qt_emit () from /usr/lib/libkdeui.so.4
#16 0xb715cf29 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb74a7fb1 in QWidgetStack::aboutToShow () from /usr/lib/libqt-mt.so.3
#18 0xb7296634 in QWidgetStack::raiseWidget () from /usr/lib/libqt-mt.so.3
#19 0xb7b3da4c in KJanusWidget::showPage () from /usr/lib/libkdeui.so.4
#20 0xb7b3dc96 in KJanusWidget::showPage () from /usr/lib/libkdeui.so.4
#21 0xb7aac85b in KJanusWidget::slotShowPage () from /usr/lib/libkdeui.so.4
#22 0xb7b3a5c0 in KJanusWidget::qt_invoke () from /usr/lib/libkdeui.so.4
#23 0xb715cf6d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#24 0xb715daed in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#25 0xb749821c in QListBox::selectionChanged () from /usr/lib/libqt-mt.so.3
#26 0xb72316f4 in QListBox::setSelected () from /usr/lib/libqt-mt.so.3
#27 0xb722e023 in QListBox::mousePressEventEx () from /usr/lib/libqt-mt.so.3
#28 0xb722e434 in QListBox::mousePressEvent () from /usr/lib/libqt-mt.so.3
#29 0xb7195b06 in QWidget::event () from /usr/lib/libqt-mt.so.3
#30 0xb70ff18a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#31 0xb71000ba in QApplication::notify () from /usr/lib/libqt-mt.so.3
#32 0xb6e0cec2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#33 0xb709ea52 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#34 0xb709dafd in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#35 0xb70adfe6 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#36 0xb7115b80 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#37 0xb7115a16 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#38 0xb70fecff in QApplication::exec () from /usr/lib/libqt-mt.so.3
#39 0xb801fd44 in kdemain () from /usr/lib/libkdeinit_konqueror.so
#40 0x08048502 in ?? ()
#41 0x00000001 in ?? ()
#42 0xbfc851a4 in ?? ()
#43 0xbfc85118 in ?? ()
#44 0x08048539 in ?? ()
#45 0xb8079dc0 in ?? () from /lib/ld-linux.so.2
#46 0xbfc85120 in ?? ()
#47 0xbfc85178 in ?? ()
#48 0xb7d32450 in __libc_start_main () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC


konsole output (after an "konqueror &") is:
QInputContext: no input method context available
QInputContext: no input method context available
QObject::connect: Cannot connect (null)::changed( bool ) to KCModuleProxy::moduleChanged(bool)
QObject::connect: Cannot connect (null)::destroyed() to KCModuleProxy::moduleDestroyed()
QObject::connect: Cannot connect (null)::quickHelpChanged() to KCModuleProxy::quickHelpChanged()
KCrash: Application 'konqueror' crashing...


I can provide contents of both /usr/share/applications/kde/proxy.desktop
and /usr/share/applnk/Settings/Browsing/Web/proxy.desktop on request
(nothing too uncommon in there, it seems).



This fully reproducible crash happens with an entirely new system account even,
and with freshly started konqueror instances, with (at least) both German and
English KDE locale setup.
Gave it severity important since it's not funny if you have 30 tabs open
and you simply want to adjust settings and... BOOM, that's it.

It's certainly plausible that _something_ may be misconfigured somewhere,
all I'd ask for is that it tries to prevent such an aggressive crash
in such an error case, of course.

Athlon K7, Debian testing.

NOTE: system is "tainted" with an additional Chinese environment setup
(e.g. KDE sometimes was configured for Chinese language etc.),
that might explain me hitting this rather offensive crash,
just make sure to take this into account during analysis.
Oh, and this particular Debian is 12 years old on the 8th (or was it 9th?)
harddisk generation, so that kind of age might play a role, too ;)

Thanks a lot for an otherwise very enjoyable KDE environment,

Andreas Mohr

--- End Message ---
--- Begin Message --- 
On Tue, May 12, 2009 at 10:43:19PM +0200, Andreas Mohr wrote:
> Hi,
> 
> KDE 4.2.2 konqueror and related packages have hit testing;
> entering proxy setup in konqueror 4.2.2 (and doing some testing there)
> did not trigger the crash any more
> (either because the crash has been fixed for real, or because the
> configuration changes during upgrade circumvented the existing crash cause,
> who knows).
> 
> The bug report can thus be closed, methinks.
>

closing!

--- End Message ---
Reply to: