You are not logged in.
Hello, first of all, I want to excuse me for my English, as I live in Argentina. Secondly, I want you to know that my linux knowledge is very limited, so excuse me if I seem ignorant
.
Well, i'm having a problem: when I turn on the pc, an error message appears saying "Could not connect to wicd's D-Bus interface. Check the wicd log for error mesages", and when I close it, another one appears saying "The wicd daemon has shut down. The UI will not function properly until it is restarted". And that happens everytime I want to start wicd, not only in the startup. This is a new install.
I checked the logs, but as I am a newbie I cannot fully understand if there's anything wrong, because the errors about wired connections are because I have just a wifi connection. Here are them: http://pastebin.com/F5Xc2L1B
I'm using xfce and SLiM.
My /etc/rc.conf file is as follows:
DAEMONS=(slim syslog-ng dbus wicd ntpd @bumblebeed !hwclock netfs crond)
MODULES=(fuse)
But I dont think there's a problem there either
I looked for this on the internet and did what poeple recommended (this seems to be common), but nothing happens, it's the same.
What can I do?
Thank you in advance
Last edited by TMalthus (2013-01-20 04:51:50)
Offline
Welcome to the boards.
People here will need more information in order to help you; see https://wiki.archlinux.org/index.php/Fo … ow_to_Post
If the error message says to check the logs, then post (or pastebin depending on size) the output here. Include some details about your
setup, so we understand how you are starting wicd, what setup steps you followed; whether this is a new install, or it has worked in the
past, version number etc...
In general, please see How To Ask Questions The Smart Way.
Offline
Welcome to the boards.
People here will need more information in order to help you; see https://wiki.archlinux.org/index.php/Fo … ow_to_Post
If the error message says to check the logs, then post (or pastebin depending on size) the output here. Include some details about your
setup, so we understand how you are starting wicd, what setup steps you followed; whether this is a new install, or it has worked in the
past, version number etc...In general, please see How To Ask Questions The Smart Way.
Thank you very much. I edited the post, if something else (a log, a file) is needed in order to help me, please name it.
Offline
This is a new install.
My /etc/rc.conf file is as follows
Why you have rc.conf if you are using a new install? You installed it using the latest iso? are you using an old iso? or are you using archbang or similar?
"open source is about choice"
No.
Open source is about opening the source code complying with this conditions, period. The ability to choose among several packages is just a nice side effect.
Offline
Why you have rc.conf if you are using a new install? You installed it using the latest iso? are you using an old iso? or are you using archbang or similar?
Im using rc.conf because I used various tutorials when configuring the xfce and slim, and as I said before, I'm not very knowledgeable in linux, I didn't know rc.conf is no longer in use, as you suggest. And yes, I used the lastest iso, and no, I'm using plain Arch.
(Distro: Arch Linux, Kernel: 3.6.11-1-ARCH, Window Manager: Xfwm, Desktop Environment: Xfce)
Offline
https://www.archlinux.org/news/end-of-i … s-support/
Also, make sure you ahve the correct interfaces set in wicd's preferences: it is trying to connect but cannot find a valid profile.
Offline
Im using rc.conf because I used various tutorials when configuring the xfce and slim, and as I said before, I'm not very knowledgeable in linux, I didn't know rc.conf is no longer in use, as you suggest.
Oh I'm sorry, But, since an installation using the latest iso has systemd-sysvcompat installed by default, which makes rc.conf file to be ignored AND you are starting slim from rc.conf, that would mean you installed initscripts manually or that you are using some other distro.
Well, remove initscripts, and upgrade to systemd. And... follow the arch wiki instead other (probably outdated) tutorials. ![]()
"open source is about choice"
No.
Open source is about opening the source code complying with this conditions, period. The ability to choose among several packages is just a nice side effect.
Offline
https://www.archlinux.org/news/end-of-i … s-support/
Also, make sure you ahve the correct interfaces set in wicd's preferences: it is trying to connect but cannot find a valid profile.
So I have to add the things that are in rc.conf like this?:
/etc/modules-load.d/virtio-net.conf
# Load virtio-net.ko at boot
virtio-net
I'm not understanding, sorry. I'm damn new in this.
Offline
So I have to add the things that are in rc.conf like this?:
/etc/modules-load.d/virtio-net.conf
# Load virtio-net.ko at boot
virtio-net
You have to add to /etc/modules-load.d/ only your modules, not all the things. On the rc.conf you posted, that would be fuse
Read the wiki: Kernel modules
Last edited by chris_l (2013-01-20 01:02:56)
"open source is about choice"
No.
Open source is about opening the source code complying with this conditions, period. The ability to choose among several packages is just a nice side effect.
Offline
You are probably best to start from scratch. Install Arch using up-to-date media and following the official documentation, not some random
tutorials that are clearly well out of date. Then, follow the respective wiki pages (in the case of this thread it would be wireless and wicd)
and methodically build up your system piece-by-piece.
Trying to do it in one go will mean that you may end up with an Arch install, but you will certainly not understand it.
Offline
You have to add to /etc/modules-load.d/ only your modules, not all the things. On the rc.conf you posted, that would be fuse
Read the wiki: Kernel modules
Thank you, I'll do so.
Offline
You have to add to /etc/modules-load.d/ only your modules, not all the things. On the rc.conf you posted, that would be fuse
Read the wiki: Kernel modules
So, apart from that, I'll have to add each of the thing I had in the rc.conf like this:
/etc/modprobe.d/NAMEOFTHEPROGRAM.conf
options NAMEOFTHEPROGRAM parameters
For example:
/etc/modprobe.d/slim.conf
options slim
Am I wrong?
Offline
You are probably best to start from scratch. Install Arch using up-to-date media and following the official documentation, not some random
tutorials that are clearly well out of date. Then, follow the respective wiki pages (in the case of this thread it would be wireless and wicd)
and methodically build up your system piece-by-piece.Trying to do it in one go will mean that you may end up with an Arch install, but you will certainly not understand it.
Yes, I did follow the Begginers guide, but somethings after the installation were too hard to understand for a linux newbie and a non-native in English. So I looked for them in Spanish. I know the best think would be to start from scratch, but I put a lot of effort in this, and I don't think there's no come back. Thank you anyway.
Offline
All of the key pages, including the wireless and wicd pages, are in Spanish.
If you are determined to proceed, you have a lot of reading in front of you. Good luck.
Offline
All of the key pages, including the wireless and wicd pages, are in Spanish.
If you are determined to proceed, you have a lot of reading in front of you. Good luck.
Thank you. I know new guys must be a pain in the ass here. I'm planning to do lots of reading on gnu/linux, but first I wanted to have a more or less usable pc.
Offline
I solved it, and emptying the rc.conf also solved other minimal problems I had. Thank you VERY much.
Offline
So, apart from that, I'll have to add each of the thing I had in the rc.conf like this:
/etc/modprobe.d/NAMEOFTHEPROGRAM.conf
options NAMEOFTHEPROGRAM parametersFor example:
/etc/modprobe.d/slim.conf
options slimAm I wrong?
I know you said you solved it, but just for the record: No, those ones are started by Systemd. But, at this moment, you probably already know that.
I know new guys must be a pain in the ass here.
Oh no, not at all. But its sometimes is problematic when they follow blogs or youtube videos instead of the official installation guide, (or the beginners' guide), mostly because they tend to be outdated (Arch changes a lot and changes fast for being rolling release). or when they use archbang, manjaro, etc, and ask here instead of their respective forums.
Putting that aside, I don't think anyone here is against newbies (we have a newbie section after all) ![]()
Edit your first post to add "[SOLVED]" to it.
good luck ![]()
"open source is about choice"
No.
Open source is about opening the source code complying with this conditions, period. The ability to choose among several packages is just a nice side effect.
Offline