LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-06-2017, 08:15 AM   #1
michaelis
LQ Newbie
 
Registered: Dec 2017
Posts: 3

Rep: Reputation: Disabled
Segfault with konsole on -current


Hi,

I'm running Slackware64-current and after an upgrade-all yesterday, 2017-12-05, I cannot start Konsole or Dolphin after connecting to wifi network.
I get the error message (translated from swedish) "KDEInit cannot start '/usr/bin/konsole'." when trying to start Konsole.
Dolphin just will not start and once the screen saver is on I cannot return to desktop, everything stays black.
Dmesg shows me konsole[2319]: segfault at e0 ip 00007f967960c69a sp 00007ffe1ccf1400 error in libkdeui.so.5.14.38[7f96792a1000+43f000].

Any ideas?
 
Old 12-06-2017, 09:33 AM   #2
heyjann
Member
 
Registered: Dec 2015
Posts: 72

Rep: Reputation: Disabled
Quote:
Originally Posted by michaelis View Post
Hi,

I'm running Slackware64-current and after an upgrade-all yesterday, 2017-12-05, I cannot start Konsole or Dolphin after connecting to wifi network.
Do you mean that you are still able start to them before connecting to the network? That would be interesting, unusual.

This is standard Slackware, right, no plasma5 or other customisations?

How did you install Slackware64-current? That is, did you do a fresh install from a -current iso or did you upgrade from 14.2 using slackpkg or manually?
Are you, when upgrading, also using slackpkg install-new and slackpkg clean-system?
 
Old 12-06-2017, 11:04 AM   #3
michaelis
LQ Newbie
 
Registered: Dec 2017
Posts: 3

Original Poster
Rep: Reputation: Disabled
Hi,

I can start the applications before I connect to the wifi, and they run after I have connected. But I cannot start new instances of them.

It's a standard slackware as far as I know, I haven't done anything to customize KDE.

I upgraded the system manually, by changing the mirror to current and running all the appropriate commands, which I don't remember now since I have only done this once.

I'm not sure I understand your last question but when I upgrade-all I don't run slackpkg install-new and slackpkg clean-system. I think I did so when upgrading to current.
 
Old 12-06-2017, 12:04 PM   #4
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,544

Rep: Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494Reputation: 2494
Quote:
Originally Posted by michaelis View Post
I'm not sure I understand your last question but when I upgrade-all I don't run slackpkg install-new and slackpkg clean-system. I think I did so when upgrading to current.
If you want to be following -current, you need to be running install-new and clean-system. -current is Slackware's development branch. It can add and take things away and upgraded programs may rely on those new programs or need the old programs removed to prevent conflicts.

If this sounds like too much work, you would probably be better sticking with the latest stable release of Slackware, which is 14.2 right now. This will continue to have patches released as security issues get found and fixed.
 
Old 12-07-2017, 05:14 AM   #5
michaelis
LQ Newbie
 
Registered: Dec 2017
Posts: 3

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
If you want to be following -current, you need to be running install-new and clean-system. -current is Slackware's development branch. It can add and take things away and upgraded programs may rely on those new programs or need the old programs removed to prevent conflicts.

If this sounds like too much work, you would probably be better sticking with the latest stable release of Slackware, which is 14.2 right now. This will continue to have patches released as security issues get found and fixed.
You are absolutely right, and I thank you for your help. I read the manual for slackpkg and tried to do just that after your advice, but it still didn't solve the problem, so I'm switching back to non-current slackware, by reinstalling everything.
The reason I went to current was actually a mistake from my side, and I have no problems following the extra steps that are necessary to be in current. But I feel that I have not knowledge enough to be in current.
I'll leave that work for you experts.

Thanks again for all your answers.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware current - MPlayer + ffmpeg-3.3 segfault orbea Slackware 9 10-31-2017 09:51 AM
[SOLVED] Digikam segfault with current Bourdieu Slackware 17 07-25-2017 05:22 PM
Segfault with E17 on Slackware --Current frankbell Slackware 5 03-26-2013 08:19 PM
[SOLVED] Xorg segfault after latest upgrade -current yenn Slackware 14 05-14-2012 06:41 PM
Xterminal + current GTK = segfault crxssi Linux - Software 3 01-28-2006 07:58 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:24 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration