I am doing some project work and for that using the server at college with ssh connection. Every time I try to open emacs on the terminal after connecting, it opens emacs in the terminal itself i.e. not its own window. On my laptop on which ubuntu is installed, emacs always opens up in its own window an thats how I am used to it. There are several problems when it opens in the terminal like when I try to use commands such as M-V, actually terminal's view menu opens up, its very frustrating. Also I am pretty sure that the college server runs on red hat and has X installed on it. So what do I need to do to get my emacs window back.
I like emacs very much, and especially like using C-M-v and C-M-S-V to scroll other window up and down. It is cool, especially when I am coding and referring documents.The problem is, using C-M-v to scroll down is OK in both terminal and X,but using C-M-S-V to scroll up just works well in X, if I use it in terminal, it behaves scrolling down too.
I work with python and I use emacs as my IDE tool. I have been running Debian Squeeze (6.0.9) for some time now with emacs 23.2.1 and ecb 2.32. I am able to access my python methods in the ecb-methods window with no problems. However I recently upgraded my desktop to Debian Wheezy (7.5) running emacs 23.4.1 and ecb 2.40 but I have lost access to the methods in the ecb-methods window. The window is just empty while the others (directories, sources and history) are all populated. I have a second laptop which I decided to upgrade to Debian Jessie, however Jessie recommends emacs 23.4.1 which is running with ecb 2.40 also. The result is the same as on Wheezy.
I have used the ecb menus and googled for a solution or even just a mention that such a problem exists but have come up with nothing. Either I have a unique situation here or am doing something really dumb.
I would like to upgrade to Wheezy or Jessie but I need access to methods in the ecb methods window. How to keep my upgrade and see the methods in the methods window of the ecb system ....
My system boots, I login and am brought to my desktop. I click on the file system icon in the launcher to open a Nautilus window. The window opens, but is unresponsive (i.e., I can't move it, clicking on the icons does nothing, etc.). If I press the super key to get the dash and the press escape, the window becomes responsive again, just like normal.
If I open a folder in the window, the window becomes halfway unresponsive in that I can't move the window, but I can select more folders and toolbar icons. The top menu no longer appears at this point, and I can't access any of the system icons on the top right of the screen. Alt-F4 closes the window even if the close button doesn't work.As another example, suppose I open a Nautilus window and then a Chromium window. Both are immediately unresponsive. If I super-esc again, I can move the Chromium window around, and it seems to work normally. I can click on the Nautilus window, but it always stays greyed out. Even if I'm clicking on things in it, the Chromium window always has focus.
I had a similar experience to this with VLC and Chromium. After clicking around enough I eventually got it to the point where VLC apparently always had focus, but I couldn't access any of VLC's controls. Double clicking anywhere on the screen fullscreened the video, and that's all I could really do. Not even escape worked to bring it back.I can usually press super to get the dash and Alt-F2 to get a command prompt. Also Alt-Shift-T seems to usually work to bring up a working Terminal (at least one that accepts commands, even if I can't move the window).Does anyone have any ideas on what might be causing this? The behavior is highly unpredictable and extremely frustrating. I should note that key commands don't always work, even though they seem to in my examples. So I don't think it's just a mouse issue.
I know that uptime prints the time a machine has been up and running, but is there an easier (reliable) way to get the date of the start up than counting down from this output?I tried looking around /proc, but didn't find anything of relevance. There's also a line like this on my dmesg: [ 0.673492] rtc_cmos rtc_cmos: setting system clock to 2011-03-14 14:26:52 UTC (1300112812), but I'm wondering if this method is distribution and kernel version agnostic.
Just got this Dell M4400 with Redhat EL5 installed. After I setup the xorg.conf for dual monitor, the startup became extremely slow. Once I type in the user name and password, it just blacks out with the mouse curser still visible. This remains for about 3-4 minutes and then I'm in.
I thought it was my X file, so I overwrote the xorg.conf with my original file and restarted my X. Sadly, it still does that.
What could be causing it? Do I have to reinstall video driver or something?
I am trying to start Damn Small Linux from a USB stick on a HP t5000 thin client. When starting in Default mode the system just stops. When starting i failsafe mode, the text rolls on the console until the message "RAMDISK: Compressed image found on block 0" and then hangs..What does that mean? What could be wrong? Can I run the image without using a ramdisk?
I am setting up a thin client boot (over NFS) with x2go thinclient. So far everything works, the client boots over PXE, mounts the NFS dir on the server. But the x2go thinclient system does not install properly. I end up with a CLI prompt, to log in. It does not start X, not does it start the x2go client in a window managerless X session.
X2go is, in case you don't know it yet, a cool Linux X terminal session system, very much like Nomachines NXserver. I like it very much, since my experience, especially with freenx has not been good.
Now I am missing some Linux knowhow here: I know that after startup (the CLI part), the display manager is started (GDM or KDM), which starts the X server and shows the graphical login. Now since X2go does not properly setup and there is no documentation about the thinclient part, I will set it up myself.
I need the system to boot up, startx and then immediately start an X program (x2goclient), without having to log in before.
I found that putting a .xsession file in to the users home dir causes that script to be run when you invoke startx.But when I put startx in a script that runs as the last one in the runlevel (as in S05startx), it does not run at all.
What is the proper way to run X and a program on it directly, right at startup?
I have a ubuntu 11.04 system and a lappy with window 7 system on it.I have got samba set up on the ubuntu system so that file sharing is enable between them.However,when I put my files in my samba share and access it from the window 7 laptop.I got some errors as per attach files.
ubuntu 10.10/wubi/asus 1201ni have installed screenlets via synaptics and added two screenlets to my desktop.i added screenlets to the autostart menu, pointing it to a folder inside my documents folder, where the launching icon of this software is located.since then, after reboot a gedit window appears on my desktop and says the following :
Upon booting this morning, my Ubuntu 11.04 install no longer shows the login window at startup. The background is still there, as well as the on-screen keyboard I have set to appear at startup. tty1-6 all work just fine, although they they dont automatically connect to wifi so i have to go wired (or learn how to connect to wifi via tty1) if i need to use the internet for this. Before this issue popped up, I had tried out xmonad and upon switching back to compiz, I have to run "compiz --replace" every time I log in which may have something to do with this problem. I also installed and uninstalled gnome 3 before that, so I may have broken something with all that.
I have conky running a simple script on my Ubuntu 11.04 install. Running conky from using ALT-F2 is fine, but I have have conky added to the startup list, and when it runs from this, the conky window is different (ie not integrated with desktop layer). It has some shadowing around the edge and it seems to be on a layer other than the desktop. In addition to this, it stops running after a short while. I then run conky from ALT-F2 again and it's appears as I want, and stays there all day. I have included what I think is the relevant code below from my conkyrc. Has anyone had similar issues with a suitable way to resolve the problem?
I have installed a new Linux distro (just to test it) on my usb memory stick, and I'm trying to run it. I don't know if what I did is correct so far, anyways here's what I have:
Grub on sda (internal hard disk) sdb with no boot loader (memory stick)
In grub I've been doing: root (hd1,0) kernel /kernel-genkernel-x86_64-2.6.37-sabayon root=/dev/sdb1 vga=normal initrd /initramfs-genkernel-x86_64-2.6.37-sabayon boot
This seems to work (as opposed to when I forgot the root= parameter, which almost destroyed my linux on sda1 ), but during startup the system complains about no root bein found on /dev/sdb1. I also tried (hd1,0), but it didn't change much.
I'm sure I can boot an OS from usb on my computer, so doesn anyone know what I'm doing wrong?
I'm an old-school dinosaur, and I'd like to understand how drag and drop works on the X window system under Linux. Is it build into the X protocol? Is it a function of the window manager? Do applications have to be aware of drag and drop? Is it both the applications and the window manager?I'm looking for a general technical understanding. If I have specific questions about how to modify an app to support drag and drop, I'll ask them over on Stackoverflow.