Back to Netrunner | Back to Blue Systems

Segmentation Fault

I’ve been running Kubuntu for a while and have been on 13.10 since it was released with very few problems.

I wanted to try Netrunner 13.12 so i downloaded it yesterday, backed up my data and reformatted my drive and installed a 100% clean install of Netrunner. All I’ve done since then is apt-get update, apt-get upgrade and installed a new version of VirtualBox (4.3.6) and Chrome. I haven’t even restored my data yet.

Every single time I open a browser (Firefox or Chrome), or open almost any program (LibreOffice, FileZlilla, really anything), KDE crashes with a segmentation fault. It comes right back up, and no data is lost, and the program I was trying to run actually does work, but the crashes are driving me insane. Not sure what to do. I have a 2nd machine that is running Netrunner 13.06 with no issues but I’m hesitant to upgrade that one since it’s mission critical.

My machine is a Core i7-920 with 8GB RAM, an Nvidia 7800GTX (I know it’s old but it has been working fine in Kubuntu) and I’ve tried all the video drivers available for that card that I can find with no joy. I also tried to install a slightly newer 8600GT but it does the same thing.

Not sure what to do. Any help would be appreciated. I could reinstall from scratch again, but I’d rather not do that if the fix is easy, and I’m not even sure that would help.

[color=#000080][i]Try updating to KDE 4.12

Install the repository:[/i][/color]

[size=medium]sudo add-apt-repository ppa:kubuntu-ppa/backports[/size]

[color=#000080]Then you run:[/color]

[size=medium][b]sudo apt-get update

sudo apt-get dist-upgrade[/b][/size]

A full backtrace of that crash would help. So in Dr.Konqi (the little error window) install the debug tools to have a useful backtrace that can be posted here to identify the problem you have.

I’ve got the same problem but only with Chrome. :huh:

I tested chrome here on a freshly installed vm. Worked like a charm.
Did you updated to the latest expanding-icons-taskmanager just like noted here: http://www.netrunner-os.com/package-updates/ ?

Things have gone from bad to worse now.
Firefox is also crashing my desktop now.
Could it be a flash problem, there was a Flash update in the updates I installed this morning.
Everything was working fine after I installed Netrunner yesterday.

Will update expanding-icons-taskmanager now and see what happens.

Update did not solve problem.
[hr]
There are hunderds of stories on the internet about the KDE Desktop crashing but very few real answers.
Looks like this problem has been around since early last year.
I wonder why its has only cropped up here now…Buggy Updates…?

Netrunner 64bit or 32bit?
What KDE version are you running?
Firefox version? Flash version?
What is the exact package number of expanding-icons-taskmanager?

I’m using 64 bit.KDE 4.11.3 Firefox 12.0.1
I’m running Netrunner 13.12 and the programs that came with it, I have not made any changes except applying all the updates.
KSYSGUARD also crashes the desktop.
Thunderbird loads fine.
Flash version… the one that came with the latest updates, I don’t know where to see Flash version.
Chrome shows this Adobe Flash Player (2 files) - Version: 12.0.0.41
Shockwave Flash 12.0 r0

Something else I noticed was that after every desktop crash my memory usage was getting more.
Checked process table and there was six plasma, chrome and fire foxes running.

Upgrading KDE to 4.12 did not help. Every program I run crashes KDE. I cannot find even one that will run without a crash.

Here’s the backtrace:

Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library “/lib/x86_64-linux-gnu/libthread_db.so.1”.
[Current thread is 1 (Thread 0x7f0d3f8b87c0 (LWP 2121))]

Thread 4 (Thread 0x7f0d099d2700 (LWP 2345)):
#0 __GI___pthread_mutex_lock (mutex=0x7f0d04000a90) at pthread_mutex_lock.c:90
#1 0x00007f0d325433a1 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f0d3250368a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f0d325037ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f0d3bd6fa76 in QEventDispatcherGlib::processEvents (this=0x7f0d040008f0, flags=…) at kernel/qeventdispatcher_glib.cpp:426
#5 0x00007f0d3bd415ef in QEventLoop::processEvents (this=this@entry=0x7f0d099d1cb0, flags=…) at kernel/qeventloop.cpp:149
#6 0x00007f0d3bd418e5 in QEventLoop::exec (this=this@entry=0x7f0d099d1cb0, flags=…) at kernel/qeventloop.cpp:204
#7 0x00007f0d3bc4088f in QThread::exec (this=this@entry=0xade270) at thread/qthread.cpp:542
#8 0x00007f0d3bd22d13 in QInotifyFileSystemWatcherEngine::run (this=0xade270) at io/qfilesystemwatcher_inotify.cpp:265
#9 0x00007f0d3bc42f2f in QThreadPrivate::start (arg=0xade270) at thread/qthread_unix.cpp:338
#10 0x00007f0d2fc85764 in ?? () from /usr/lib/nvidia-304-updates/libGL.so.1
#11 0x00007f0d32c0df6e in start_thread (arg=0x7f0d099d2700) at pthread_create.c:311
#12 0x00007f0d3f1a29cd in clone () at …/sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7f0d091d1700 (LWP 2346)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at …/nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007f0d3855606b in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2 0x00007f0d385560a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3 0x00007f0d2fc85764 in ?? () from /usr/lib/nvidia-304-updates/libGL.so.1
#4 0x00007f0d32c0df6e in start_thread (arg=0x7f0d091d1700) at pthread_create.c:311
#5 0x00007f0d3f1a29cd in clone () at …/sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f0c7bfff700 (LWP 2349)):
#0 0x00007f0d3f195f7d in poll () at …/sysdeps/unix/syscall-template.S:81
#1 0x00007f0d325036a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f0d325037ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f0d3bd6fa76 in QEventDispatcherGlib::processEvents (this=0x7f0c740008f0, flags=…) at kernel/qeventdispatcher_glib.cpp:426
#4 0x00007f0d3bd415ef in QEventLoop::processEvents (this=this@entry=0x7f0c7bffecb0, flags=…) at kernel/qeventloop.cpp:149
#5 0x00007f0d3bd418e5 in QEventLoop::exec (this=this@entry=0x7f0c7bffecb0, flags=…) at kernel/qeventloop.cpp:204
#6 0x00007f0d3bc4088f in QThread::exec (this=this@entry=0x2f86d50) at thread/qthread.cpp:542
#7 0x00007f0d3bd22d13 in QInotifyFileSystemWatcherEngine::run (this=0x2f86d50) at io/qfilesystemwatcher_inotify.cpp:265
#8 0x00007f0d3bc42f2f in QThreadPrivate::start (arg=0x2f86d50) at thread/qthread_unix.cpp:338
#9 0x00007f0d2fc85764 in ?? () from /usr/lib/nvidia-304-updates/libGL.so.1
#10 0x00007f0d32c0df6e in start_thread (arg=0x7f0c7bfff700) at pthread_create.c:311
#11 0x00007f0d3f1a29cd in clone () at …/sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f0d3f8b87c0 (LWP 2121)):
[KCrash Handler]
#6 QHash<unsigned long, QHashDummyValue>::findNode (this=this@entry=0x38, ahp=ahp@entry=0x0, akey=) at /usr/include/qt4/QtCore/qhash.h:884
#7 0x00007f0d1c487180 in contains (akey=, this=0x38) at /usr/include/qt4/QtCore/qhash.h:874
#8 contains (value=, this=0x38) at /usr/include/qt4/QtCore/qset.h:91
#9 TaskManager::Startup::matchesWindow (this=, window=) at /build/buildd/expanding-icons-taskmanager-0.0+git20140116+r28~063a797+1~ubuntu13.10.1/libs/taskmanager/startup.cpp:114
#10 0x00007f0d1c47ccf3 in TaskManager::GroupManagerPrivate::addTask (this=0x23872c0, task=0x6cd5e60) at /build/buildd/expanding-icons-taskmanager-0.0+git20140116+r28~063a797+1~ubuntu13.10.1/libs/taskmanager/groupmanager.cpp:354
#11 0x00007f0d1c480f35 in TaskManager::GroupManager::qt_static_metacall (_o=0x38, _id=79691982, _a=0x0, _c=) at /build/buildd/expanding-icons-taskmanager-0.0+git20140116+r28~063a797+1~ubuntu13.10.1/obj-x86_64-linux-gnu/libs/taskmanager/groupmanager.moc:94
#12 0x00007f0d3bd56a58 in QMetaObject::activate (sender=sender@entry=0x2b77140, m=m@entry=0x7f0d1c6c14e0 TaskManager::TaskManager::staticMetaObject, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff93264320) at kernel/qobject.cpp:3539
#13 0x00007f0d1c49fe5f in TaskManager::TaskManager::taskAdded (this=this@entry=0x2b77140, _t1=_t1@entry=0x6cd5e60) at /build/buildd/expanding-icons-taskmanager-0.0+git20140116+r28~063a797+1~ubuntu13.10.1/obj-x86_64-linux-gnu/libs/taskmanager/taskmanager.moc:187
#14 0x00007f0d1c4a0b2f in TaskManager::TaskManager::windowAdded (this=0x2b77140, w=79691982) at /build/buildd/expanding-icons-taskmanager-0.0+git20140116+r28~063a797+1~ubuntu13.10.1/libs/taskmanager/taskmanager.cpp:297
#15 0x00007f0d1c4a229c in TaskManager::TaskManager::qt_static_metacall (_o=0x38, _id=79691982, _a=0x0, _c=) at /build/buildd/expanding-icons-taskmanager-0.0+git20140116+r28~063a797+1~ubuntu13.10.1/obj-x86_64-linux-gnu/libs/taskmanager/taskmanager.moc:103
#16 0x00007f0d3bd56a58 in QMetaObject::activate (sender=sender@entry=0xc29d60, m=m@entry=0x7f0d3ce212a0 KWindowSystem::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff93264540) at kernel/qobject.cpp:3539
#17 0x00007f0d3cb27592 in KWindowSystem::windowAdded (this=this@entry=0xc29d60, _t1=79691982) at ./kwindowsystem.moc:143
#18 0x00007f0d3cb28a7a in KWindowSystemPrivate::addClient (this=0xc45a80, w=79691982) at …/…/kdeui/windowmanagement/kwindowsystem_x11.cpp:287
#19 0x00007f0d3cb37553 in NETRootInfo::update (this=this@entry=0xc45aa8, dirty_props=dirty_props@entry=0x7fff93264700) at …/…/kdeui/windowmanagement/netwm.cpp:2227
#20 0x00007f0d3cb3896b in NETRootInfo::event (this=this@entry=0xc45aa8, event=event@entry=0x7fff93264870, properties=properties@entry=0x7fff93264780, properties_size=properties_size@entry=5) at …/…/kdeui/windowmanagement/netwm.cpp:2099
#21 0x00007f0d3cb2873b in KWindowSystemPrivate::x11Event (this=0xc45a80, ev=0x7fff93264870) at …/…/kdeui/windowmanagement/kwindowsystem_x11.cpp:190
#22 0x00007f0d3ca2ce98 in publicX11Event (e=0x7fff93264870, this=) at …/…/kdeui/kernel/ksystemeventfilter.cpp:43
#23 KSystemEventFilterPrivate::filterEvent (this=0xc64400, message=0x7fff93264870) at …/…/kdeui/kernel/ksystemeventfilter.cpp:102
#24 0x00007f0d3bd3485e in QAbstractEventDispatcher::filterEvent (this=0x38, message=0x4c000ce, message@entry=0x7fff93264870) at kernel/qabstracteventdispatcher.cpp:539
#25 0x00007f0d3b181850 in x11EventSourceDispatch (s=0xa7b0a0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:143
#26 0x00007f0d325033b6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f0d32503708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f0d325037ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f0d3bd6fa55 in QEventDispatcherGlib::processEvents (this=0x95ead0, flags=…) at kernel/qeventdispatcher_glib.cpp:424
#30 0x00007f0d3b1819d6 in QGuiEventDispatcherGlib::processEvents (this=, flags=…) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00007f0d3bd415ef in QEventLoop::processEvents (this=this@entry=0x7fff93264c50, flags=…) at kernel/qeventloop.cpp:149
#32 0x00007f0d3bd418e5 in QEventLoop::exec (this=this@entry=0x7fff93264c50, flags=…) at kernel/qeventloop.cpp:204
#33 0x00007f0d3bd46e5b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#34 0x00007f0d3b0de34c in QApplication::exec () at kernel/qapplication.cpp:3828
#35 0x00007f0d3f4ac28c in kdemain (argc=1, argv=0x7fff93264ea8) at …/…/…/…/plasma/desktop/shell/main.cpp:126
#36 0x00007f0d3f0c9de5 in __libc_start_main (main=0x4006e0 <main(int, char**)>, argc=1, ubp_av=0x7fff93264ea8, init=, fini=, rtld_fini=, stack_end=0x7fff93264e98) at libc-start.c:260
#37 0x000000000040070e in _start ()

I went back to my Windows troubleshooting ways and reinstalled from scratch.

That worked, and I’m good now.

I loathe the Windows mentality of rebuild from scratch when things don’t work right, but I didn’t have the time to deal with this any longer.

@drapsag Have you installed the updates and chrome…?

Yes, everything is still working properly after my complete reinstall, updating the OS and installing Chrome.

Not sure what broke the first time I installed, but I followed the same steps exactly the second time with no issues.

I had a second copy of Netrunner running on another harddrive which was running fine.
I installed updates and it still ran fine, then installed chrome and all was good till I rebooted.
The problem was back, Now I do not know if it was the updates or chrome that broke my system.
I will try a complete new install and then reboot after updates and then also reboot after installing chrome and see if I can
find out what is breaking my system. :cool:

I’m not sure where my first install went bad, but my second install is working just fine. Good luck in your troubleshooting.

This segmentation fault has made the OS completely unusable. I did a completely fresh install, set up my dual monitor panels, opened firefox, and then segmentation fault. Tried updating and upgrading, didn’t work. Tried reinstalling again, didn’t work. Tried googling errors and going to hundreds of different threads, but none have a working solution. There has to be something I’m doing wrong, because it doesn’t seem that most people are having this problem. My specs are:

i5 3470
16GB 1866mhz DDR3 RAM
Nvidia GTX 680

I have the same problem. I have installed Netrunner 64bit on two different machines with different hardware and on both of them, randomly, indipendently by what I’m doing, the desktop crashes (plasma-desktop segmentation fault) and restart. On both machines I have set a quite similar configuration with a second panel in the upper part of the desktop with several icons and Netrunner Desktops set to different directories. Automatically Firefox, Thunderbird, Clementine, Chokoq and Basket start up at login. Chromium browser is istalled but not running (rarely used).

Ciao
Massimiliano

Is your system up to date ?
Is Dr. Konqi the debug assistent starting for you on segmentation fault ?
If yes can you please install the debuging tool it offers and save the error log (you need the debuging tools installed otherwise the log would be not very useful [called ‘garbage’ in konqi]

Thank you for your reply.
Yes, the system is up to date.
The bug assistant always ask me to install the dubugging tools and send the error; I do it but then it says that the collected information are useless. I have never saved the error log; next time the error come up I will save it.

Ciao
Massimiliano

This evening the plasma-desktop segmentation fault error came up again. Attached the error log.

Thank you
Massimiliano

[attachment=162]

Hi,

I think to have understood what cause the problem; the segmentation fault is caused by the program Choqok. After Choqok uninstallation the error does not come up anymore.
Choqok cause the problem to Netrunner 14.06 too.

Regards
Massimiliano