[Bug 167522] New: Konqueror process doesn't stop after close (keeps running iddle)

[Eduardo Robles Elvira]

El Domingo 27 Julio 2008, Eduardo Robles Elvira escribió:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=167522
>            Summary: Konqueror process doesn't stop after close (keeps
>                     running iddle)
>            Product: konqueror
>            Version: unspecified
>           Platform: Compiled Sources
>         OS/Version: Linux
>             Status: NEW
>           Severity: normal
>           Priority: NOR
>          Component: general
>         AssignedTo: konq-bugs kde org
>         ReportedBy: edulix gmail com
>
>
> Version:            (using Devel)
> Installed from:    Compiled sources
>
> The problem is that when closing the last konqueror window, the window gets
> closed, but the konqueror process keeps running and doesn't stop unless I
> kill it. I'm using revision 838176 (trunk ~4.2) and yes, I have konqueror
> preloading disable (and anyway I'm launching it from a tty andd thus I get
> the message "Running from tty, not keeping for preloading" which is quite
> descriptive :-).
>
> Note that the problem is happening to me also in kwrite and kate for
> example, but in other programs like kfind or kmail the process finish
> correctly.
>
> This is the gdb backtrace when konqueror keeps running after having closed
> it:
>
> konqueror(19880) KonqMainWindow::checkPreloadResourceUsage: Running from
> tty, not keeping for preloading
>
> Program received signal SIGINT, Interrupt.
> [Switching to Thread 0x7f7b00d9a780 (LWP 19880)]
> 0x00007f7af9d9ec3f in poll () from /lib/libc.so.6
> (gdb) bt
> #0  0x00007f7af9d9ec3f in poll () from /lib/libc.so.6
> #1  0x00007f7af8d61542 in ?? () from /usr/lib/libglib-2.0.so.0
> #2  0x00007f7af8d61bcb in g_main_context_iteration () from
> /usr/lib/libglib-2.0.so.0 #3  0x00007f7afe54b3cf in
> QEventDispatcherGlib::processEvents (this=0x61ea90, flags=<value optimized
> out>) at kernel/qeventdispatcher_glib.cpp:325 #4  0x00007f7afb83c68f in
> QGuiEventDispatcherGlib::processEvents (this=0x886130, flags=<value
> optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #5 
> 0x00007f7afe5263d5 in QEventLoop::processEvents (this=<value optimized
> out>, flags= 0x7fff08dd42a0) at kernel/qeventloop.cpp:149 #6 
> 0x00007f7afe526547 in QEventLoop::exec (this=0x7fff08dd42e0, flags=
> 0x7fff08dd42f0) at kernel/qeventloop.cpp:196 #7  0x00007f7afe528551 in
> QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #8 
> 0x00007f7b00972224 in kdemain (argc=1, argv=0x7fff08dd4db8) at
> /home/edulix/proyectos/kde4/kdesvn/kdebase/apps/konqueror/src/konqmain.cpp:
>227 #9  0x0000000000400943 in main (argc=1, argv=0x7fff08dd4db8) at
> /home/edulix/proyectos/kde4/kdesvn/build/kdebase/apps/konqueror/src/konquer
>or_dummy.cpp:3 _______________________________________________
> Konq-bugs mailing list
> Konq-bugs at mail.kde.org
> https://mail.kde.org/mailman/listinfo/konq-bugs


I must say this bug is driving me crazy since last night when it first 
happened to me (or I first noticed, I don't know). Any ideas? I've tried using 
a new ~/.kde4 directory to see if it was bad configuration but it didn't 
help.

Cheers,
      Eduardo Robles Elvira.
-- 
"The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all progress
depends on the unreasonable man." (George Bernard Shaw)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20080727/125111ee/attachment.sig>