LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Multiple post-installation problems (https://www.linuxquestions.org/questions/slackware-14/multiple-post-installation-problems-4175525061/)

victorvscn 11-11-2014 06:20 AM

Multiple post-installation problems
 
Hello, guys,
I'm new to the linux scene and, after some frustrating experiences with Ubuntu 14.10, decided to find the most stable linux distro. Every answer led me here. Anyway, after struggling a bit with the installation, I could finally install Slackware (latest version) using a USB flash drive. Installed Elilo, since I'm dual booting with Windows. I have two hard drives. First hard drive has Windows 8.1 installed. Second used to have Windows, but now it holds a) Windows's recovery (and EFI boot) partitions b) a general NTFS storage partition c) Slackware itself on /dev/sdb9 d) a swap partition on /dev/sdb8.

I had some errors post-installation:
Code:

VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6. Please append a correct "root=" boot option: here are the available partition ...
There errors, however, were resolved upon reinstalling. I leave them here merely as context. Anyway, after booting up, adding my user, I loaded the login GUI. As soon as I logged in, I got the following error message:

Code:

cannot open consolekit session unable to open session failed to connect to socket /var/run/dbus/system_bus_socket: no such file or directory
Indeed, I do not have a system_bus_socket file/folder on /var/run/dbus. These are the contents of my /var/run/dbus folder: image 1


I'm not familiar with the default KDE environment, but everything looked out of place. For example, I could not find a Wifi toggle (seems pretty standard on OSes these days). In fact, there were no bars at all, except a bottom bar to add widgets. Thought to myself it could be normal behavior on KDE, and directed myself to system settings. Figured I'd try to update and everything would be corrected, but I had no internet connection. Trying to open the network settings, it force-closed on me. Other settings force closed as well.
I thought it could be related to the root account, so I logged out and logged in again with my default user. Same error. Same general dysfunctional desktop environment, except that sudo doesn't work and upon editing sudoers I get syntax errors (all I did was add "username ALL=(ALL) ALL"). I have found some troubleshooting ideas for other distros, but they all referred to files I could not find on Slackware.

Any ideas?
Thanks in advance!

EDIT: I've seen this response for Arch Linux numerous times: https://bbs.archlinux.org/viewtopic.php?id=132802, but it refers to a /etc/rd.conf I cannot seem to find. Another user suggests the deletion of a ~/.kde folder, which I've done, to no avail.

PS: Sorry for taking so long to explain my problem, this is all new to me and I'm not sure which details are important.

moisespedro 11-11-2014 06:45 AM

1 - You don't need elilo, I have Windows 8.1 installed too and LILO works fine.
2 - I am not able to help you :-( but I know we will need you to provide more information.

victorvscn 11-11-2014 07:04 AM

Quote:

Originally Posted by moisespedro (Post 5268138)
1 - You don't need elilo, I have Windows 8.1 installed too and LILO works fine.
2 - I am not able to help you :-( but I know we will need you to provide more information.

1 - I see. Well, Slackware setup recommended me to skip lilo and install elilo, so that's what I did.
2 - What kind of information? Tell me the logs to run and I'll do it, I just don't know what to run by myself.

moisespedro 11-11-2014 07:33 AM

Maybe dmesg and Xorg.0.log?

Alien Bob 11-11-2014 07:42 AM

Quote:

Originally Posted by victorvscn (Post 5268125)
As soon as I logged in, I got the following error message:
Code:

cannot open consolekit session unable to open session failed to connect to socket /var/run/dbus/system_bus_socket: no such file or directory
Indeed, I do not have a system_bus_socket file/folder on /var/run/dbus.

It looks as if DBus is not running. Without DBus, KDE will be pretty dysfunctional. What are the properties of the file "/etc/rc.d/rc.messagebus" ? Slackware installs that file executable by default (mode 755) - it is this rc script which starts DBus.

Quote:

I'm not familiar with the default KDE environment, but everything looked out of place. For example, I could not find a Wifi toggle (seems pretty standard on OSes these days).
In Slackware you need to add that widget yourself.
During installation, as part of networking configuration, you should have seen the question whether you want to use NetworkManager yes/no. If you chose "yes" then in KDE you can add a networkmanagement widget by clicking on the bottom-right corner icon and searching for "network". If you answered "no" to NetworkManager support, then you need to configure your network manually using an ascii editor, in the configuration file "/etc/rc.d/rc.inet1.conf".

Quote:

In fact, there were no bars at all, except a bottom bar to add widgets. Thought to myself it could be normal behavior on KDE, and directed myself to system settings. Figured I'd try to update and everything would be corrected, but I had no internet connection. Trying to open the network settings, it force-closed on me. Other settings force closed as well.
Those systemsettings applets should not crash in case you do not have Internet. But you are right, the KDE in Slackware is a barebones configuration, you can add widgets all you want but there is of course the Application launcher menu in the lower left which holds all functionality.

Quote:

I thought it could be related to the root account, so I logged out and logged in again with my default user. Same error. Same general dysfunctional desktop environment
Graphical environments in Slackware should not be run as root. We make no arrangements for the root account and KDE is quite unforgiving of running as root.

Quote:

except that sudo doesn't work and upon editing sudoers I get syntax errors (all I did was add "username ALL=(ALL) ALL")
Sudo is not configured out of the box. That syntax you show us looks correct, but if you get a syntax error for it, something else is wrong in that file. By the way, what you are attempting to do is very Ubuntu-ish, and should not be used like that in Slackware. Very insecure.

Eric

victorvscn 11-11-2014 08:18 AM

Thank you for your answers. If the barebones is the default KDE configuration, then *that* is fine. I rather like it. I was just worried it could be a bug. Anyway, back to business.

Contents of rc.messagebus:
Code:

#!/bin/sh
#
# messagebus:  The D-BUS systemwide message bus
#
# description:  This is a daemon which broadcasts notifications of system events \
#              and other messages. See http://www.freedesktop.org/software/dbus/
#
# processname: dbus-daemon
# pidfile: /var/run/dbus/pid

# This is a modified version of the rc.messagebus script distributed with the
# dbus sources.  Thanks to Don Tanner of the GWare <http://gware.org> Project
# for most of the work involved      --Robby Workman <rworkman@slackware.com>


PIDFILE=/var/run/dbus/dbus.pid

start() {
  mkdir -p $(dirname $PIDFILE)
  if ! ps -u messagebus -c | grep -wq dbus-daemon; then
    rm -f $(dirname $PIDFILE)/*
    if [ -x /usr/bin/dbus-uuidgen -a -x /usr/bin/dbus-daemon ] ; then
      echo "Starting system message bus:  /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system"
      /usr/bin/dbus-uuidgen --ensure
      /usr/bin/dbus-daemon --system 1> /dev/null
    fi
  fi
}

stop() {
  if [ -e "$PIDFILE" ]; then
    echo "Stopping system message bus..."
    pid=$(cat $PIDFILE)
    kill $pid 1> /dev/null 2> /dev/null
    # Just in case:
    killall dbus-daemon 1> /dev/null 2> /dev/null
    rm -f $PIDFILE
  fi
}

reload() {
  echo "Reloading system message bus configuration..."
  if [ -e "$PIDFILE" ]; then
    pid=$(cat $PIDFILE)
    kill -HUP $pid
  else
    killall -HUP dbus-daemon
  fi
}

status() {
  if ps -u messagebus -c | grep -wq dbus-daemon; then
    echo "System dbus-daemon is running."
  else
    echo "System dbus-daemon is stopped."
  fi
}

# See how we were called.
case "$1" in
  start)
    start
    ;;
  stop)
    stop
    ;;
  restart)
    stop
    start
    echo "You may need to restart your Window Manager to reconnect to the system dbus."
    ;;
  reload)
    reload
    ;;
  status)
    status
    ;;
  *)
    echo $"Usage: $0 {start|stop|restart|reload|status}"
    ;;
esac

Screenshot of its permissions:
http://i.imgur.com/WuIAFqR.png

I did a "su/chmod 755 /etc/rc.d/rc.messagebus", not sure if that will help.

victorvscn 11-11-2014 08:29 AM

Additional logs:
Xorg: http://textuploader.com/ovtt
dmesg (err looks important): http://textuploader.com/ovt0
system settings debug: http://textuploader.com/ovtk

Alien Bob 11-11-2014 09:06 AM

The error at the start of the "dmesg" log about "couldn't mount because of unsupported optional features (240)" is in fact just a warning. See http://www.linuxquestions.org/questi...-240-a-843675/ for the explanation.

The segfault of systemsettings happens in libQtDBus.so, so this seems related to the DBus errors you see at login. The content of rc.messagebus which you posted earlier is irrelevant, this is a Slackware script which is never modified. It is worth running it again before you start X:
Code:

/etc/rc.d/rc.messagebus restart
and see if that shows relevant errors.

Eric

victorvscn 11-11-2014 09:21 AM

Quote:

Originally Posted by Alien Bob (Post 5268197)
The error at the start of the "dmesg" log about "couldn't mount because of unsupported optional features (240)" is in fact just a warning. See http://www.linuxquestions.org/questi...-240-a-843675/ for the explanation.

The segfault of systemsettings happens in libQtDBus.so, so this seems related to the DBus errors you see at login. The content of rc.messagebus which you posted earlier is irrelevant, this is a Slackware script which is never modified. It is worth running it again before you start X:
Code:

/etc/rc.d/rc.messagebus restart
and see if that shows relevant errors.

Eric

Actually, I restarted and everything worked after the chmod. Except for my network interface. Any ideas on that? It's a Qualcomm Atheros AR5BWB222 Wireless Network Adapter.

Edit: Apparently, that's not automatic either. I'm going through http://docs.slackware.com/slackbook:network.
Edit 2: Ok, I've been able to configure them by myself. Thanks everybody!


All times are GMT -5. The time now is 06:10 AM.