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

List:       konq-bugs
Subject:    [Bug 284830] konqueror file manager crash on tab refresh
From:       Wayne E. Nail <altbinspam () yahoo ! com>
Date:       2011-10-26 17:17:47
Message-ID: E1RJ76p-0001of-8Y () bugs ! kde ! org
[Download RAW message or body]

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





--- Comment #1 from Wayne E. Nail <altbinspam yahoo com>  2011-10-26 17:17:46 ---
Created an attachment (id=64899)
 --> (http://bugs.kde.org/attachment.cgi?id=64899)
New crash information added by DrKonqi

konqueror (4.6.5 (4.6.5)) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.4

- What I was doing when the application crashed:

This crash persists and has no special relationship with refreshing tabs, and
is multiply repeatable. Normally I have three konqueror filemanager instances
open on my desktop in the same workspace, two as my user, and one as root
(kdesu, and please don't start with how this is a bad idea because I've yet to
screw anything up in years and years of using it this way). 

If I leave any of these instances open but 'untended' for some period of time
yet to be discovered -- more than a few minutes but less than five hours -- 
once I refocus upon any of those instances and attempt to perform any action,
the instance simply vanishes. Poof. Gone.

This bug may be related to 284841 ... and it may be that the plasma crash is
the defining time factor that will cause konqueror instances to vanish on next
visit. That is, after the plasma crash and automatic plasma reload, the next
time I visit one of the konqueror instances, that instance will disappear.
However, it may be the case that the plasma crash does not need to happen first
for the konqueror instance to disappear.

Both the plasma crash (284841) bug and this konqueror bug began after the same
yum update on 22 October 2011.

- Unusual behavior I noticed:

Each konqueror instance remains on the desktop unless and until I transfer
focus to it (I use 'focus follows mouse'). Once focused, I must then perform
some action -- click on a tab, folder, filename, etc -- to cause that instance
to disappear.

Sometimes, but not always, one of the three konqueror instances disappearing
will take another instance with it. The odd part about this is that at least
once, the root instance of konqueror took one of the user instances of
konqueror with it, leaving the remaining user instance of konqueror onscreen.
However, once that remaining instance of konqueror is focused upon and an
action is performed in that window, that instance also disappears.

-- Backtrace (Reduced):
#10 0x009ae487 in g_logv (log_domain=0xa0eca6 "GLib", log_level=<value
optimized out>, format=0xa148c4 "Cannot create pipe main loop wake-up: %s\n",
args1=0xb53d617c "\364+\222") at gmessages.c:557
#11 0x009ae4c3 in g_log (log_domain=0xa0eca6 "GLib",
log_level=G_LOG_LEVEL_ERROR, format=0xa148c4 "Cannot create pipe main loop
wake-up: %s\n") at gmessages.c:577
#12 0x009a1dbc in g_main_context_init_pipe (context=0xb4a004e8) at gmain.c:520
#13 0x009a21c5 in g_main_context_new () at gmain.c:615
#14 0x07b369b6 in QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate
(this=0xb4a00478, context=0x0) at kernel/qeventdispatcher_glib.cpp:310

-- 
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@kde.org
https://mail.kde.org/mailman/listinfo/konq-bugs
[prev in list] [next in list] [prev in thread] [next in thread]