Debian :: Slight Delay In Root Terminal (inside X)
Jan 26, 2011
When I'm in OpenBox, I often have a termianl (lxterminal) open in the background. The terminals responds quickly when logged in as my standard user. If I, however, use su to switch to root, there's about a 2 or 3 second delay on the output for any command I type. This delay goes away if I type another character or tap the spacebar. That input is read as normal -- I've accidentally answered 'y' to prompts before.
My machine is an ASUS Eee PC 1001P (1GB of RAM, Atom 450) with an 40GB Intel SSD.
Switching to and from insert mode in Vim is no longer instantaneous since I use tmux. After pressing Esc in insert mode, it takes a noticeable amount of time to actually get out of insert mode. After pressing Esc and any other key afterwards the switch is immediate, and the command for the key pressed after Esc is executed. Any idea what might cause this?The Vim configuration is not the problem as the delay does not occur when I run Vim outside tmux, so this is probably related to tmux somehow. I use gnome-terminal btw.
Also worth noting, it seems I can not define key bindings in tmux for Esc, my plan was to bind Esc to:bind Escape send-keys.Alas, it seems binding anything to Esc for tmux does not work. The same problem occurs in screen as well.
I upgraded from Slackware 64 13.1 to Slackware 64 13.37 a week or so ago. I am now having a perceptible delay of a few seconds when launching commands from the command line, say for example: screen -R.
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.
After reboot I can start it, no problem here. But if I close root terminal and trying to open it again - it won't open.
If to open it from user terminal, it gives me:
Code: Select allgksu /usr/bin/x-terminal-emulator Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 1
The only thing comes to my mind is that right after installation I opened root terminal and:
- kept a tick on "remember password" - put a tick on "save in the keyring".
I guess the last tick is the problem. I installed debian 8.4 in virtualbox and specifically kept the tick where it should be and I can start root terminal many times w/o any problem. How I can fix that?
I do realize that I can get root privileges in terminal. I guess it's more about convenience.
I tried to google it, but no luck. Just to name few:
I am running Lenny with LXDE. Fresh install of the single CD. The regular terminal fails to open when I click on the icon or when I use the Accessories menu title. However, the root terminal will open. Any way to fix this? I don't want to always be using root for routine work.
I installed openbox and obmenu with everything seeming to run smooth , but I managed to mess something up. When right clicking my screen I get an error stating that I am missing root-menu. I cannot open terminal while inside openbox. So while out I used apt-get purge on both applications , and reinstalled. The problem is still there and cannot right click or super+t for terminal. I've found other problems same as mine , but with being able to access the terminal while in.
I'm configuring some security and i'd like to run arpon to a specific device everytime wicd connects.So, if Wicd connects to a wireless, i'd launch gksu arpon -d -i eth2 (for example.) But this doesn't work, because it seems that gksu only works for X apps.I found that if i do: gnome-terminal -e 'sudo arpon -d -i eth2' It works, but it leaves me with a terminal window open, and i'd like to be asked for a password gksu style.I've also tried this: gksu -- arpon -d -i eth2which also works, but the program quits right after it's started.Am i missing something here?
Running Gnome on Jessie. Have had Gnome hang a few times over the past few months. The hangs seem to be related to having open and / or closing a root terminal. It has happened on a Gateway AMD Phenom II tower and on my Gateway NV59 lappy with Pentium P6200.
I'm brand new to Linux and perhaps foolishly jumped right into Debian (Jessie). I've managed to get Dropbox downloaded/installed/whatever the proper parlance is, but in order to access it I have to input Code: Select all~/.dropbox-dist/dropboxd. When I close the root terminal, Dropbox disappears.There's no icons in the menu. Likewise with GUFW. It might be superfluous since UFW seems to be active whenever I check it through the root terminal. Is there any way to configure Dropbox to start automatically and maintain its status even if the root terminal is closed? I've looked around these forums and the internet in general and not found any similar problems. Also, I installed Spotify but whenever I click the icon nothing happens.
I am running a shell script using a non root user. Somewhere down in the script, I'll have to call some script to be executed as su (or a user with more privileges than the one running the original script). So if i put a line in the script as:
su - root -c /root/roleScripts/assignRoles.sh
Then when running the command, it will prompt me for root password(because the current user has lower privileges than the user requested. Suppose I want to pass this password as an argument to the original script, so that it doesn't prompt me for password later on, what is the way? Can I switch user passing the password and run a command?
I just installed Ubuntu 10.04 for some development. I was trying to set some environment variables are noticed that when I hit 'set' inside a terminal (to dump environment vars) I get the usual first few variables but then I see a whole lot of script code ....
I've installed a lot of tools (NetBeans, Ruby, Java, build-essentials etc) but essentially I installed Ubuntu today - so it shouldn't have rotted out this quickly. is this hijacking of environment vars to embed script code intentional with Ubuntu 10.04?
After GRUB 2 comes up (I'm running Ubuntu 10.10) and I choose the OS to boot, there is about a 5 second delay where nothing appears to happen after I make the selection -- no disk activity. It happens consistently every time I boot. Again, this is after I choose the OS to boot, so it shouldn't have anything to do with the standard delay to allow me to choose the appropriate OS.Is there a good way to troubleshoot this and determine what is causing the delay?
I searched the forum but could not get the desired result.PROBLEM- I am using ubuntu 10.10 installed inside Windows Vista. Now with every start up ubuntu gives a low space warning. I alloted 10 GB inside windows while installing ubuntu using wubi. Now it says only 34 MB space is free. Is it possible to increase the root size inside windows. My both OS are on C drive and it has about 15 GB free. I would like to allocate & GB to ubuntu.
I have a small internal network with about 8 or so servers or workstations. My mail server is getting spammed from all over to the root and other administrative accounts. I also get valid email sent to the root and administrative accounts from within my local network. Is there a way to block all email coming from outside my local network while still receiving it inside the local network to these specific accounts?
Before upgrading to Lenny there was no noticeable delay between entering a username & the prompt for a password when logging in via ssh. Now there is about a 5-second delay which is rather annoying. There is no delay when logging in through the Gnome UI. Anyone know why the delay is there? Is it something about ssh under Lenny? Is there a setting that can be changed?
I want to run a command on startup (Via startup applications) that has to wait for another program to run first.I don't seem to be able to use sleep to delay the command as it is stored in a .desktop file.How do I make it run later, preferably without having to create a script just for this one command.Also, how do I make the system start with compiz? Change "/desktop/gnome/session/required_components/windowmanager" ? Or do it the clean way by (Somehow) configuring gnome to use compiz?
I have moved from a raspberry pi to an olimex LIME A20. I have managed to get everything working correctly except mediatomb. I have a USB drive attached, I believe that mediatomb is trying to read the drive before it's mounted leaving me with an empty database.
After boot I can create the mediatomb database which works until I reboot the computer. What can I try to delay the mediatomb services start?
I have debian lenny, when I run an application is slow to load (example: iceweacel open and it takes, I can hold him iceweacel work normally), I tried to change from gnome to another and the same thing, went down some services (samba, squid) and nothing. I open a terminal and it takes, I want to duplicate it and do it fast. From a terminal without X (tty1) with root run mc and moves quickly, also run as root "sudo mc" and takes to boot.Any action done with sudo it takes to run.Can not be what it takes to make starting the applications, not the PC because it is new, and from one moment to another I began to pass this
I have Linux debian 7.7.0 i386-amd64 under VBox 4.3.20 and here is the problem:::
When I open the menu from Linux's top-right corner and click SHUT DOWN..., it shows the dialog with choices, and that Linux guest will automatically shutdown after 60 seconds and I need to change that delay value to 3 seconds. Of course I could just re-click Shut Down -button again, but I don't want to do it. Period.
By Googling I found these "instructions" for UBUNTU:
None of this worked on my 13.04 system. In the end I re-compiled gnome-session.
In gsm_shell.c and gsm_logout_dialog.c change #define AUTOMATIC_ACTION_TIMEOUT from 60 to 5
I'm having some difficulty starting a service from an init.d script. It relies on the availability of a network filesystem (glusterfs) which is mounted from fstab. The service starts before the filesystem is up, and crashes.I've tried adding "# Required-Start: remote_fs" to the service init.d script, and delaying it by changing the ordering with "update-rc.d service defaults 90", but neither seems to work. If I add a "sleep 10" to the script, that works, but it feels wrong.Is there some way to get the ordering right? To delay starting the service until after everything in fstab is ready to g
I have the slight, high-pitched hissing frequency when ever I play back audio.I know other people have experienced this as well, but the threads were in a development section of the forum and are no longer open. Has anyone has the same issue yet found a solution?