[opensuse] Dolphin in KDE 4.3.1 crashing?
Guys, My install of KDE 4.3.1 has dolphin segfaulting all the time. I installed lots of updates and rebooted the Machine a couple days ago. Per yast, it was built: Sun 04 Oct 2009 04:30:03 PM EDT, so it is very new. Since then Dolphin has been totally unreliable. It may relate to browsing samba servers, since that is about 80% of what I do from this machine. Are others seeing this? Thanks Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer Preservation and Forensic processing of Exchange Repositories White Paper - <http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html> The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 14 October 2009 17:24:20 Greg Freemyer wrote:
Guys,
My install of KDE 4.3.1 has dolphin segfaulting all the time.
I installed lots of updates and rebooted the Machine a couple days ago.
Per yast, it was built: Sun 04 Oct 2009 04:30:03 PM EDT, so it is very new.
Since then Dolphin has been totally unreliable. It may relate to browsing samba servers, since that is about 80% of what I do from this machine.
Are others seeing this?
Thanks Greg
I've seen recently a similar behavior. It's not extremely annoying, but it happens from time to time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 14 October 2009 16:26:51 Bogdan Cristea wrote:
On Wednesday 14 October 2009 17:24:20 Greg Freemyer wrote:
Guys,
My install of KDE 4.3.1 has dolphin segfaulting all the time.
I installed lots of updates and rebooted the Machine a couple days ago.
Per yast, it was built: Sun 04 Oct 2009 04:30:03 PM EDT, so it is very new.
Since then Dolphin has been totally unreliable. It may relate to browsing samba servers, since that is about 80% of what I do from this machine.
Are others seeing this?
Thanks Greg
I've seen recently a similar behavior. It's not extremely annoying, but it happens from time to time.
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere. Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 15 October 2009 12:06:17 Will Stephenson wrote:
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere.
please be more specific what steps should I follow in order to provide the backtrace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 15 October 2009 11:19:39 Bogdan Cristea wrote:
On Thursday 15 October 2009 12:06:17 Will Stephenson wrote:
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere.
please be more specific what steps should I follow in order to provide the backtrace
Install those packages, make it crash, open the 'Developer information' tab of the crash dialog ('Dr Konqi'), check that it has 2 or 3 stars there (this indicates whether the backtrace is useful for diagnosis) and copy the backtrace into a mail. Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Will Stephenson wrote:
On Thursday 15 October 2009 11:19:39 Bogdan Cristea wrote:
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere.
On Thursday 15 October 2009 12:06:17 Will Stephenson wrote: please be more specific what steps should I follow in order to provide the backtrace
Install those packages, make it crash, open the 'Developer information' tab of the crash dialog ('Dr Konqi'), check that it has 2 or 3 stars there (this indicates whether the backtrace is useful for diagnosis) and copy the backtrace into a mail.
Will
Until final release of Opensuse, why aren't those packages installed by default? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Oct 15, 2009 at 2:06 PM, John Andersen <jsamyth@gmail.com> wrote:
Will Stephenson wrote:
On Thursday 15 October 2009 11:19:39 Bogdan Cristea wrote:
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere.
On Thursday 15 October 2009 12:06:17 Will Stephenson wrote: please be more specific what steps should I follow in order to provide the backtrace
Install those packages, make it crash, open the 'Developer information' tab of the crash dialog ('Dr Konqi'), check that it has 2 or 3 stars there (this indicates whether the backtrace is useful for diagnosis) and copy the backtrace into a mail.
Will
Until final release of Opensuse, why aren't those packages installed by default?
I don't know the official answer, but they are huge. So doing a KDE only upgrade on the machine I have them installed on takes much longer than if I did not have them installed. I imagine many users would be pretty unhappy having to download them everytime KDE was updated. Also, I'm having the problem with OS 11.1, but with the kde 4.3.1 repo. That is semi-released I guess. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer Preservation and Forensic processing of Exchange Repositories White Paper - <http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html> The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 15 October 2009 20:14:29 Greg Freemyer wrote:
On Thu, Oct 15, 2009 at 2:06 PM, John Andersen <jsamyth@gmail.com> wrote:
Will Stephenson wrote:
On Thursday 15 October 2009 11:19:39 Bogdan Cristea wrote:
On Thursday 15 October 2009 12:06:17 Will Stephenson wrote:
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere.
please be more specific what steps should I follow in order to provide the backtrace
Install those packages, make it crash, open the 'Developer information' tab of the crash dialog ('Dr Konqi'), check that it has 2 or 3 stars there (this indicates whether the backtrace is useful for diagnosis) and copy the backtrace into a mail.
Will
Until final release of Opensuse, why aren't those packages installed by default?
I don't know the official answer, but they are huge. So doing a KDE only upgrade on the machine I have them installed on takes much longer than if I did not have them installed. I imagine many users would be pretty unhappy having to download them everytime KDE was updated.
That's right - think of all the other packages besides KDE that might crash - installs would be enormous, the load on the mirrors would be huge, and testing openSUSE would be much more onerous. There's a plan to let Dr Konqi prompt you to install the packages as needed, but that won't happen for 11.2. Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 15/10/09 15:06, John Andersen wrote:
Until final release of Opensuse, why aren't those packages installed by default?
Simple, you do not need them unless something particular crashes.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Cristian Rodríguez wrote:
On 15/10/09 15:06, John Andersen wrote:
Until final release of Opensuse, why aren't those packages installed by default?
Simple, you do not need them unless something particular crashes..
And we all know, that NEVER happens. Isn't this what beta is for? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Oct 15, 2009 at 5:06 AM, Will Stephenson <wstephenson@suse.de> wrote:
On Wednesday 14 October 2009 16:26:51 Bogdan Cristea wrote:
On Wednesday 14 October 2009 17:24:20 Greg Freemyer wrote:
Guys,
My install of KDE 4.3.1 has dolphin segfaulting all the time.
I installed lots of updates and rebooted the Machine a couple days ago.
Per yast, it was built: Sun 04 Oct 2009 04:30:03 PM EDT, so it is very new.
Since then Dolphin has been totally unreliable. It may relate to browsing samba servers, since that is about 80% of what I do from this machine.
Are others seeing this?
Thanks Greg
I've seen recently a similar behavior. It's not extremely annoying, but it happens from time to time.
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere.
Will, I have the debuginfo packages installed. Next time it happens I'll use the automated submission tool to submit a bug to kde. There is at least one there, but when I checked it yesterday, it did not have the full symbolic trace. ie. No debuginfo packages in use by the submitter. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer Preservation and Forensic processing of Exchange Repositories White Paper - <http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html> The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Oct 15, 2009 at 5:06 AM, Will Stephenson <wstephenson@suse.de> wrote:
On Wednesday 14 October 2009 16:26:51 Bogdan Cristea wrote:
On Wednesday 14 October 2009 17:24:20 Greg Freemyer wrote:
Guys,
My install of KDE 4.3.1 has dolphin segfaulting all the time.
I installed lots of updates and rebooted the Machine a couple days ago.
Per yast, it was built: Sun 04 Oct 2009 04:30:03 PM EDT, so it is very new.
Since then Dolphin has been totally unreliable. It may relate to browsing samba servers, since that is about 80% of what I do from this machine.
Are others seeing this?
Thanks Greg
I've seen recently a similar behavior. It's not extremely annoying, but it happens from time to time.
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere.
Will
Will, It finally crashed again. I have the debuginfo's installed that you mention, but they must not be enough. the Dr. Kongi is only giving me one star. Here's the trace as it stands: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #5 0x00007f445ecbbeb4 in ?? () from /lib64/libdbus-1.so.3 #6 0x00007f445eccd51d in ?? () from /lib64/libdbus-1.so.3 #7 0x00007f445ecc054f in ?? () from /lib64/libdbus-1.so.3 #8 0x00007f446517f446 in QDBusConnectionPrivate::timerEvent (this=0x6a3290, e=0x7fff5214b260) at ./qdbus_symbols_p.h:172 #9 0x00007f44642c8533 in QObject::event (this=0x6a3290, e=0x17) at kernel/qobject.cpp:1075 #10 0x00007f446474cb0d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #11 0x00007f4464754d9a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #12 0x00007f4465cafa8b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #13 0x00007f44642b894c in QCoreApplication::notifyInternal (this=0x7fff5214b650, receiver=0x6a3290, event=0x7fff5214b260) at kernel/qcoreapplication.cpp:610 #14 0x00007f44642e5b60 in QTimerInfoList::activateTimers (this=0x6b2080) at kernel/qcoreapplication.h:213 #15 0x00007f44642e1ddd in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #16 0x00007f44606540fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #17 0x00007f44606578cd in ?? () from /usr/lib64/libglib-2.0.so.0 #18 0x00007f4460657a8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #19 0x00007f44642e1d3f in QEventDispatcherGlib::processEvents (this=0x689730, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #20 0x00007f44647e3fef in ?? () from /usr/lib64/libQtGui.so.4 #21 0x00007f44642b71d2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1377088896}) at kernel/qeventloop.cpp:149 #22 0x00007f44642b75a4 in QEventLoop::exec (this=0x7fff5214b5c0, flags={i = 1377088976}) at kernel/qeventloop.cpp:201 #23 0x00007f44642b9894 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #24 0x000000000043980d in main (argc=5, argv=0x7fff5214bb38) at /usr/src/debug/kdebase-4.3.1/apps/dolphin/src/main.cpp:94 Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Greg Freemyer wrote:
On Thu, Oct 15, 2009 at 5:06 AM, Will Stephenson <wstephenson@suse.de> wrote:
On Wednesday 14 October 2009 16:26:51 Bogdan Cristea wrote:
On Wednesday 14 October 2009 17:24:20 Greg Freemyer wrote:
Guys,
My install of KDE 4.3.1 has dolphin segfaulting all the time. ...
I've only had two or so crashes of dolphin in the three or four weeks I've been on 4.3.1, but I have seen it. In both cases, it immediately opened the directory or file it had crashed on and had no further trouble; in both cases, the crash dialog said the crash information was not useful. Is it worthwhile for me to find and install a debug-enabled version? John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John E. Perry wrote:
Greg Freemyer wrote:
On Thu, Oct 15, 2009 at 5:06 AM, Will Stephenson <wstephenson@suse.de> wrote:
On Wednesday 14 October 2009 16:26:51 Bogdan Cristea wrote:
On Wednesday 14 October 2009 17:24:20 Greg Freemyer wrote:
Guys,
My install of KDE 4.3.1 has dolphin segfaulting all the time. ...
I've only had two or so crashes of dolphin in the three or four weeks I've been on 4.3.1, but I have seen it.
I suppose I ought to be more diligent about reporting the problems I see. Disclaimer: I've updated all packages since the last occurrence of any of these problems, so, ... To clarify my comment above, I've seen these crashes of Dolphin, then been able to restart Dolphin on the same file I was trying to open when it crashed. I see no pattern in the file type, size, or anything else. I'm using the ext3 filesystem. There has never been a repeat within several days of the previous crash. This last happened Friday, as I recall. Also, I've had Firefox (now 3.0.14) freeze my display and keyboard several times. It doesn't happen on any particular web page, or at any particular time, or after any stretch of time that I can identify. When it happens, the mouse pointer works fine, but the buttons have no effect, and the keyboard doesn't respond at all. The last was early this afternoon. Since I have no power button (known hardware failure), my only recourse is to remove the battery and disconnect power (yes, I've tried waiting for hours). After putting the battery back in and applying power again, it boots up and works normally for days -- even on the web pages I was on when it froze. Since I habitually keep half a dozen instances of Firefox, Konqueror, and Dolphin open, several instances of OpenOffice, many instances of Konsole, and always have Thunderbird open, I suppose my machine is pretty heavily loaded as far as my 2G of memory and 2G of swap are concerned. But I've never seen any other program crash like Dolphin, or X freeze as it does when I'm using Firefox. Finally, recently, whenever I have to restart the system or kde, my wifi won't work until I kill both NetworkManager and knetworkmanager and restart them. Once it's up, it will stay until I have to reboot or restart the session again. Info: hp dv6000CTO OS: Linux 2.6.27.29-0.1-pae i686 System: openSUSE 11.1 (i586) KDE: 4.3.1 (KDE 4.3.1) "release 163" Dolphin Version 1.3 Display: Tungsten Graphics, Inc Model: Mesa DRI Intel(R) 945GM 20080716 x86/MMX/SSE2 Driver: 1.4 Mesa 7.2 Firefox: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.14) Gecko/2009090900 SUSE/3.0.14-0.1.2 Firefox/3.0.14 Wireless: pci.product = 'PRO/Wireless 3945ABG [Golan] Network Connection' info.linux.driver = 'iwl3945' Hope this is helpful to someone (including me :-) John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Will, ping, Greg On Fri, Oct 16, 2009 at 5:14 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Thu, Oct 15, 2009 at 5:06 AM, Will Stephenson <wstephenson@suse.de> wrote:
On Wednesday 14 October 2009 16:26:51 Bogdan Cristea wrote:
On Wednesday 14 October 2009 17:24:20 Greg Freemyer wrote:
Guys,
My install of KDE 4.3.1 has dolphin segfaulting all the time.
I installed lots of updates and rebooted the Machine a couple days ago.
Per yast, it was built: Sun 04 Oct 2009 04:30:03 PM EDT, so it is very new.
Since then Dolphin has been totally unreliable. It may relate to browsing samba servers, since that is about 80% of what I do from this machine.
Are others seeing this?
Thanks Greg
I've seen recently a similar behavior. It's not extremely annoying, but it happens from time to time.
What's the backtrace (with kdelibs4-debuginfo and kdebase4-debuginfo installed)? Otherwise this thread won't go anywhere.
Will
Will,
It finally crashed again. I have the debuginfo's installed that you mention, but they must not be enough. the Dr. Kongi is only giving me one star.
Here's the trace as it stands:
Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #5 0x00007f445ecbbeb4 in ?? () from /lib64/libdbus-1.so.3 #6 0x00007f445eccd51d in ?? () from /lib64/libdbus-1.so.3 #7 0x00007f445ecc054f in ?? () from /lib64/libdbus-1.so.3 #8 0x00007f446517f446 in QDBusConnectionPrivate::timerEvent (this=0x6a3290, e=0x7fff5214b260) at ./qdbus_symbols_p.h:172 #9 0x00007f44642c8533 in QObject::event (this=0x6a3290, e=0x17) at kernel/qobject.cpp:1075 #10 0x00007f446474cb0d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #11 0x00007f4464754d9a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #12 0x00007f4465cafa8b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #13 0x00007f44642b894c in QCoreApplication::notifyInternal (this=0x7fff5214b650, receiver=0x6a3290, event=0x7fff5214b260) at kernel/qcoreapplication.cpp:610 #14 0x00007f44642e5b60 in QTimerInfoList::activateTimers (this=0x6b2080) at kernel/qcoreapplication.h:213 #15 0x00007f44642e1ddd in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #16 0x00007f44606540fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #17 0x00007f44606578cd in ?? () from /usr/lib64/libglib-2.0.so.0 #18 0x00007f4460657a8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #19 0x00007f44642e1d3f in QEventDispatcherGlib::processEvents (this=0x689730, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #20 0x00007f44647e3fef in ?? () from /usr/lib64/libQtGui.so.4 #21 0x00007f44642b71d2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1377088896}) at kernel/qeventloop.cpp:149 #22 0x00007f44642b75a4 in QEventLoop::exec (this=0x7fff5214b5c0, flags={i = 1377088976}) at kernel/qeventloop.cpp:201 #23 0x00007f44642b9894 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #24 0x000000000043980d in main (argc=5, argv=0x7fff5214bb38) at /usr/src/debug/kdebase-4.3.1/apps/dolphin/src/main.cpp:94
Greg
-- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer Preservation and Forensic processing of Exchange Repositories White Paper - <http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html> The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Bogdan Cristea -
Cristian Rodríguez -
Greg Freemyer -
John Andersen -
John E. Perry -
Will Stephenson