I'v just installed wicd. I can't get it to sart, I get errors saying that wicd couldn't connect to it's dbus interface and the wicd deamon has shut down. Then there's a report from SELinux saying that it's preventing /usr/bin/python "write" access on /etc/dhcp/manager-settings.conf and that access is denied to wicd. I can get wicd to start if I su to root, but I'd like to not have to do that every time I boot. Is there a fix?
My university has a secure wireless network that has the following specs: WPA2, 1st Authentication TTLS, 2nd Authentication PAP, Encryption CCMP or AES, Thawte_Premium_Server_CA certificate and username and password.
I have never gotten this to work with wicd. First of all, wicd does not have a default template for this configuration. This led me in the past to quickly install Network-Manager (on top of XFCE...). While this has worked for me just fine. Recently I found out that this functionality is possible in wicd by creating your own template. So I did and here it is!
name = WPA2 Enterprise TTLS author = Andres Cimmarusti version = 1
I did everything outlined here: [URL] (that is I saved the file as wpa2-ttls and then added this entry to the active file in /etc/wicd/encryption/templates/).
Sadly wicd's gui does not load my template!, the logs show no errors!...it simply refuses to take it. I cannot see any mistake in the above... do you?Is this some debian bug perhaps?This is the most important issue for me, before accepting to use wicd instead of NM.
I have wicd 1.6.1 (bzr-r426) and it is working very good with my root user but with all those which have not the root rights wicd asks for superuser password to connect. I want to avoid this pop-up window to be shown, how can I proceed? I first thought about the sid and gid but it seems that there is no improvements using chmod 4755 and 2755 on the different files involved in.
how to get a shortcut for opening a terminal as root? I mean something I could put in my gnome panel and then just click and get a dialog asking for the root password. Or maybe just open the terminal and automatically do "su -" (maybe this is easier actually). In Debian/Ubuntu this can be achieved doing "gksu gnome-terminal". In F10 I got it done using beesu, but it doesn't work anymore in F11:
I'm running 18.104.22.168-95.fc14.i686 on Gnome 2.32.0. I've been trying to assign a keyboard shortcut to Suspend the system when activated, but it doesn't work because to suspend the system you need to be root. The command I've been using for the shortcut is terminal "pm-suspend".I don't wanna set up the working user as root. Is there any way to get around the root authentication while suspend to make the shortcut work?
I have been using Fedora 11 for some time and I ran into a major problem today. I had installed some packages by yum (especially bacula-related) and erased them. Now I can't use gnome-terminal as root. Quote:
[webman@localhost ~]$ su - Password: su: incorrect password
The password is correct, but it is not accepted as such.
Every time I invoke gedit from the root terminal I get:-
[AnOther@FSLServer ~]$ su Password: [root@FSLServer AnOther]# gedit
(gedit:6447): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
followed by 33 occurrences of:-
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See [URL]. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)gedit opens fine but it seems really odd. My exposure to linux is not vast but this has never happened before Fedora12 It doesn't happen if I just use the terminal as an ordinary user.It also has nothing to do with the Bad & Ugly Gstreamer plugins as this happened from the moment the system was installed from the DVD and before the plugins were loaded even after removing them and rebooting I still get the ream of GConf errors if I start Gedit after su,
Everyone is wondering why we can't run gEdit and other tools from a terminal by logging in as root(e.g"su-"), I understand that by making changes they are trying to force us as users of Linux to learn better habits that are more secure, but the issues are driving people nuts!
I for one really like being able to log as root and open gEdit to make drive changes without having to login as root, I would normally still have access to all my things like email etc. So changing Linux to force everyone to not use tools like gEdit as root is becoming more of an inconvenience than they realize, there must be a safe way to do this!
I was using the latest stable release of Debian, dual-booted alongside Windows Vista, with the GNOME desktop, installed via netinst, trying to build and install a library that I knew and trusted, when suddenly I couldn't open the Root Terminal. I clicked the link (in Applications->Accessories (I think, whatever the top one is)->Root Terminal), and in the taskbar I saw an item that said "Starting Root Terminal". A few seconds later, that went away, but the terminal still wasn't open. I tried the regular user terminal, to see the same thing happen. Unsure of what was happening, I tried restarting my computer, since that's always the first step you should take in computer problems.
When I restarted, GNOME wouldn't start. The screen would flash a bit for a few seconds, then a dialog box would appear over a background of static that said "The greeter application is crashing. Attempting another one...".t would then go back to the DOS-style kernel, wait a second, and then the same thing would happen. After several of that, I would get a blue screen which said something to the effect of "It has been detected that the desktop environment has crashed six times in the past 30 seconds.
Waiting two minutes before trying again." When it did that, I tried logging in as root to assess the problem. I gave it the correct password, but it said that it was an incorrect login. After several tries (to ensure I didn't mistype the password), I logged in as myself. Same problem. I tried the su command, with the correct password, and it said it couldn't authorise it.
After a lengthy conversation with a friend of mine who was very good with computers, he basically summarised that he had no clue, but that his best guess would be a virus. Upon running the Linux installer, I found the Repair option. Not being particularly familiar with Linux, I used it simply to backup my important files onto a flash drive. I then tried running the Install option, in an attempt to simply write over my existing Linux and make it new again. The installer, however, consistently froze up when trying to start the partitioner, on the "Checking disks..." stage. I figured it was a problem with my partition. In my naivete, I simply used the Windows tools to clear that partition... It destroyed GRUB too, so I couldn't run any OS. I figured my computer was pretty well screwed, and at that point just decided to bring it into the shop and have them completely wipe it.
my computer was backed up onto an external hard driven I brought it back, I reinstalled Windows. Upon restart, it said that it was still looking for GRUB, which made no sense to me. After messing around with it a bit, I decided to just reinstall Linux too. To my lack of surprise, that fixed the problem. Both OS' now ran just fine. The first thing I did on Debian was to install the Clam Anti-Virus, which I understood to be one of the best Linux anti-viruses. However, within about 10 hours, got the same problem as originally. I wasn't doing any of the same things, and between the lack of consistency in activities and the fact that I had an anti-virus running,figured it wasn't a virus. Not knowing what to do, I just left it and have been using Windows since.
If I type "halt" from root terminal , the system tries to shut down , its closing all apps and services , unmounting disks , shutting down network etc, but finally I can see a message "System Halted"...But it doesnt turn off the monitor though..is this a bug? I have tried many times , however "poweroff" works properly..I was thinking since these are similar commands , bith should give the same result ...I usually use "halt" as it has fewer char to type!
I was tinkering around with my /etc/grub.d/10_linux file to try and alter the way my OS's were displayed on startup and somehow I filtered out my Ubuntu option, now I have no way off accessing the terminal, I tried the command gnome-terminal, but had no success, does anybody know how to access my /etc/grub.d/10_linux file through the grub2 command line?
After upgrading from 10.10 to 11.04, my machine was freezing as the desktop was loading. The mouse pointer would move and some of the basic shortcut keys would work, but nothing on the screen was responsive.
I've got the NVIDIA 7300 LE video card, so i thought it was a conflict between that and UNITY (which I have ZERO interest in running), so I move over to a terminal login and this is what it looks like: [url] (click for pic - apparently, not everybody uses a 55" LCD as a monitor)
I can type like a regular terminal window, but obviously I can't read anything. I ran 'sudo apt-get remove unity' (and then 'sudo apt-get install gnome' when that didn't work) but the desktop still doesn't load and the terminal login tabs are still completely illegible.
After experimenting with wicd I've gone back to network manager. All is well on the networking front however I am having trouble stopping wicd completely.I've stopped it starting up the daemonchkconfig --list | grep wicdreturns emptybut when my kde windows starts up the wicd try icon start up.
My computer won't load the login. How do I load the root of the computer to bypass this freeze? How do I force it to give me the login screen? It only displays the computer's name and ubuntu's version 10.10. There are no links at the bottom to follow.
I had Fedora 7 and Windows Vista dual booting on my computer. I just installed Fedora 10. When the live CD asked me where to install it, I chose "Remove all Linux Partitions and create default layout" The installation went perfectly, but now when reboot my computer, it boots directly into Fedora; GRUB does not load to ask me which OS I want to load. I know I did not overwrite Vista because I can still view my Vista files through Fedora. Here is my grub.conf file:
What do I need to do to make GRUB load again upon booting?
I have found that APACHE or 'httpd' is installed in my machine. But the problem is I can start or stop the httpd but whenever I load the url http://localhost in Mozilla it shows a page load error.I have done this ,
$ /etc/init.d/httpd start then this $ /etc/init.d/httpd graceful
in xfce desktop >> when i try and run "disk management" >> it gives me a "not allowed" message >> How can I use su (root) with "disk management" (in the gui) without the "command prompt-terminal" window?
On a ancient server Proliant 3000 (works perfect) with Smart Array 3200 and raid 5, and a CD-ROM IDE drive, I have installed Debian Squeeze or Lenny more five times without success. Before run install the OS on this server is neccesary to execute Smart Start CD, which create (block 1 of the hard disk) the Compaq Diagnostic partition (aprox 39 MB).After that proceeding, I ran the installation CD (Debian Squeeze, or Lenny, both with same results) wich ended well. The bootloader was sets on MBR or primary sector.On restart, the OS remains long time trying to load root, and later it warns something as this:"Gave up waiting for root device:" etc etc and "ALERT! /dev/disk/by-uuid/c53f0423 does not exist. Droping to a shell!"
I summarized the screen text because lines that I pasted above are clear about matter.I tried to change GRUB 2 from bootloader screen ("e" keypress) the /dev/hda or hd0 or like this, but not resolved the problem...I went to other console (Alt-F2) and I typed "fdisk -l" and "df -h" and I saw that CD drive appears like "/dev/hda"... It not's something strange?
I have a problem on Ubuntu Karmic Koala. I can't log in as 'root' on the terminal or on 'root terminal'. And i just update the Karmic Koala, but still... i can't enter as 'root'...? Frankly speaking.... it's easy to use 'root' on Ubuntu 8.10.....