[prev in list] [next in list] [prev in thread] [next in thread] 

List:       konq-bugs
Subject:    [Bug 255758] New: Konqueror crashed when maximizing after freeze
From:       Achim Herwig <achim.herwig () wodca ! de>
Date:       2010-10-31 18:27:56
Message-ID: bug-255758-5021 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=255758

           Summary: Konqueror crashed when maximizing after freeze
           Product: konqueror
           Version: unspecified
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: konq-bugs@kde.org
        ReportedBy: achim.herwig@wodca.de


Application: konqueror (4.5.2 (KDE 4.5.2))
KDE Platform Version: 4.5.2 (KDE 4.5.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.31.14-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

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

I use Konqueror for file managemant as well as browsing. I had clicked on a
symlink to a directory and konqueror was hanging for some seconds (it does that
often), so I minimized the window and maximized it again in order to directly
see when it would recover (it usually does on this case). However, instead it
crashed with that attached backtrace.

As I see in the proposed Duplicates the question of Nepomuk raised quite often:
I have it disabled.

-- Backtrace:
Application: Konqueror (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  _dbus_connection_lock (connection=0x0) at dbus-connection.c:355
#7  0x00007fb9acd6bbfd in _dbus_pending_call_get_connection_and_lock
(pending=0xfe4b00) at dbus-pending-call.c:307
#8  0x00007fb9acd5dd3e in reply_handler_timeout (data=0x0) at
dbus-connection.c:3158
#9  0x00007fb9afde05a7 in q_dbus_timeout_handle (timeout=<value optimized out>)
at qdbus_symbols_p.h:174
#10 QDBusConnectionPrivate::timerEvent (timeout=<value optimized out>) at
qdbusintegrator.cpp:1050
#11 0x00007fb9b2a300b9 in QObject::event (this=0x6f53e0, e=0x718930) at
kernel/qobject.cpp:1175
#12 0x00007fb9b1b8413c in QApplicationPrivate::notify_helper (this=0x687900,
receiver=0x6f53e0, e=0x7fff3f44e1e0) at kernel/qapplication.cpp:4396
#13 0x00007fb9b1b8c82d in QApplication::notify (this=0x7fff3f44e6f0,
receiver=0x6f53e0, e=0x7fff3f44e1e0) at kernel/qapplication.cpp:4277
#14 0x00007fb9b371c606 in KApplication::notify (this=0x7fff3f44e6f0,
receiver=0x6f53e0, event=0x7fff3f44e1e0) at
/usr/src/debug/kdelibs-4.5.2/kdeui/kernel/kapplication.cpp:310
#15 0x00007fb9b2a1df7c in QCoreApplication::notifyInternal
(this=0x7fff3f44e6f0, receiver=0x6f53e0, event=0x7fff3f44e1e0) at
kernel/qcoreapplication.cpp:732
#16 0x00007fb9b2a4d850 in sendEvent (event=<value optimized out>,
receiver=<value optimized out>) at kernel/qcoreapplication.h:215
#17 QTimerInfoList::activateTimers (event=<value optimized out>,
receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:617
#18 0x00007fb9b2a4a3b8 in timerSourceDispatch (source=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:184
#19 idleTimerSourceDispatch (source=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:231
#20 0x00007fb9ae536dee in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#21 0x00007fb9ae53a7b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fb9ae53a8e0 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#23 0x00007fb9b2a4a083 in QEventDispatcherGlib::processEvents (this=0x616cf0,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#24 0x00007fb9b1c3594e in QGuiEventDispatcherGlib::processEvents (this=0x0,
flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007fb9b2a1cca2 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#26 0x00007fb9b2a1d08c in QEventLoop::exec (this=0x7fff3f44e540, flags=) at
kernel/qeventloop.cpp:201
#27 0x00007fb9b2a21ff9 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1009
#28 0x00007fb9a34905e4 in kdemain () from /usr/lib64/libkdeinit4_konqueror.so
#29 0x0000000000407fe7 in launch (argc=4, _name=<value optimized out>,
args=<value optimized out>, cwd=<value optimized out>, envc=32, envs=<value
optimized out>, reset_env=true, tty=0x0, 
    avoid_loops=false, startup_id_str=0x66e618
"juma;1288549271;109394;3712_TIME2170786") at
/usr/src/debug/kdelibs-4.5.2/kinit/kinit.cpp:723
#30 0x0000000000408d30 in handle_launcher_request (sock=12, who=<value
optimized out>) at /usr/src/debug/kdelibs-4.5.2/kinit/kinit.cpp:1215
#31 0x0000000000409198 in handle_requests (waitForPid=0) at
/usr/src/debug/kdelibs-4.5.2/kinit/kinit.cpp:1399
#32 0x0000000000409eb2 in main (argc=4, argv=<value optimized out>, envp=<value
optimized out>) at /usr/src/debug/kdelibs-4.5.2/kinit/kinit.cpp:1892

Possible duplicates by query: bug 255619, bug 255005, bug 254880, bug 254515,
bug 254074.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Konq-bugs mailing list
Konq-bugs@mail.kde.org
https://mail.kde.org/mailman/listinfo/konq-bugs
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic