When I open a pdf file (e.g., beamer file) using xpdf, there's an annoying window on the left displaying section headings. Presumably it's possible to close it, ideally toggle it closed and open with a key binding, but I can't find out how to do this.
I have configured my system to suspend whenever I close the lid, by using the Power Management applet provided by my desktop manager (see my later comment). However, sometimes, when I reopen the lid, I see that the laptop is switched on but it won't resume, while the CPU heats up. I must shutdown forcefully. What could be causing this?
I have found this thread [URL] .... in regard to OpenSUSE. Is it relevant for Debian as well?
System info: - Debian GNU/Linux: 8.1 - Linux Kernel 3.16.0-4-amd64 - MATE desktop 1.8.1 - GNOME Shell 3.14.4
Clarified that the suspend is a user-level setting.
Gnome (or XORG, I'm not sure which name to give it) freezes up not always, but about once every 24 hours after I close the laptop's cover/lid. I know this happens when I close the lid rather than open it judging by the time the clock is locked at. The cursor will move around on the screen, but noting will react to it in any way. Other services such as FTP and Samba still work just fine when the computer is "locked down". Without more details to why the problem is occurring, I have no idea what to search for or where to get started solving the problem. I have attached the XORG logs (found in var/log) in case they are of any use.
I am using CentOS5.2 and gnome 2.16, sometimes (not very often) when I open something and close it by clicking the CROSS on the top-right corner. The application crash and I lose all control (no keyboard anymore), I have to reboot the system by reset the machine. What's going on?
Yesterday, when I logon as root and run service setup, after I uncheck a sevice in the list and then start it, I click the CROSS on the top-right corner of the window, it popup a window (in the background) to ask me to save it or not, but then I total lose the control, no mouse, no keyboard. I try to reset the machine many times, but everytime when I repeat the same operation, it crash again. Seems that if I don't close it, everything would be fine!!!!
I just bought my new lenovo T460 notebook and have a problem with the lid closing/suspend handling which is very puzzling for me.
If the device is on the AC, closing the lid causes the notebook to suspend. This works perfectly - in other words: The notebook wakes up after opening the lid and is usable. If the notebook is on battery, closing the lid causes the notebook to freeze. In other words: If I open the lid again, everything is frozen. Not only the UI but I'm also not able to change to TTY1, 2, ...
What I did to find out more:
Manually suspending the notebook when on battery is working. If I do a systemctl suspend it works as expected. I tried to use the KDE settings to deactivate suspending when closing the lid when on battery. But even then, the system is freezing when closing the lid. I found this link [URL] .... laptop-lid which suggests to change the HandleLidSwitch setting in /etc/systemd/logind.conf to ignore. But this does not change the behavior.
I'm using debian stretch/testing
Details about my experience with the T460 under debian gnu linux can be found here: [URL] ....
I've been running Ubuntu on my laptop for a couple months now and I've been using compiz settings manager. For some reason I can't seem to get the window effects for minimizing, closing, etc. to work. I have followed a few tutorials and nothing seems to make any difference. As far as I can tell, that is the only thing in compiz that is not working. I am running Ubuntu 10.10
I have a bash script and I'm dropping a file on script launcher shortcut. Everything seems fine, only that after executing the script console window closes, so I can't see if some messages were produced during execution.
As I just recently switched from Windows, this kind of problem is solved there by adding 'pause' command in batch script, on which user has to press key and script will then continue (finish) or by launching through 'cmd /k' which makes console window persistent.
Googling I found about 'sleep' command and more appropriate for me 'read' command, so I did this:
Unfortunately, I can't see any effect of 'read' command as console windows again terminates after execution. Execution is successful BTW. So what's the catch?
KDE tends to freeze momentarily after performing some tasks, like closing a window, pressing a button that should result in an option pane being popped, or simply trying to drag a window around the desktop. It doesn't happen every single time, but it's very persistently. I first noticed that the mouse would freeze sometimes when I do something like close a window and it takes 3~4 seconds for me to get control back, and for the task that I requested (close a window for instance) to be carried out.
During this time, I notice that all of KDE freezes up because my binary clock widget freezes as well. Is this a known problem with KDE? Can somebody give me some advice as to what might be causing this behaviour? I recall having similar problems back when I first tried 11.0, but back then it was so bad that I ended up going with Gnome. Now KDE has me hooked again, except for this one niggling issue. If I can get this resolved, then I think I will finally have an absolutely stable linux desktop.
So I have these three bars that I suppose are some kind of left over fragment of windows I had up the last time I rebooted. Anyhow, whenever I boot now, these three bars show on my desktop, and I cant get rid of them, they dont have the minimize, maximize or close buttons. Yet when I click the, "show desktop" buttom, they then minimize. HOwever, they don't show up on my window list. I've tried restarting my xsession and that didnt work, I've restarted nautilus that didn't work, I cant right click on them, I already tried xkill and force quite and that doesnt work. They're just always there.
I just installed Ubuntu 10.10 x64 and already am really annoyed by Firefox, which freezes my mouse after changing a tab (with ctrl+tab, alt+#) or closing it (ctrl+w). After about one second, i can continue working as usual. Changing Tabs by just clicking on one does not freeze anything...Maybe some of you would think now if I am crazy because of complaining about such a little thing, but it is really annoying if you are used to work fluently with ff.Edit:I today noticed, that not only shortcuts in firefox, but all Hotkeys freeze my mouse for a second. For examle ctrl+c, ctrl+v, super+e or anything else.Do you have any Idea what causes this behaviour? Reinstalling ubuntu didn't change anything
When in Home Folder or working Inkscape, the window I'm working in goes grey and the programs freeze.Only that program or folder or if I have two folders open then when the home folder freezes so will the other folders, but not programs.
I'm using: ubuntu 10.04 64 bit proprietary fglrx drivers for ati 4890.
When shaking the mouse to bring up the computer, the screensaver will freeze and not display the dialog box to log back into my profile. However, even though I can't see it, if I blindly and correctly type in my password it will work.
[update] I posted this question while at work where I do not use Ubuntu...sadly. Anyway, when I got home, I locked the screen, the gl fish screensaver came up. bam, no login dialog box. ok, tried the gl matrix screensaver, bam, no dialog box. Finally, I tried a non-gl screensaver, and what do you know, there's my login dialog box. Something is up with the gl screensavers.
Just to reiterate, when I activate the mouse or keyboard during a gl screensaver I do not see the login dialog box.
Several times now my PC with Ubuntu 10.04 LTS installed wont close down. I click on all the appropriate buttons but the system doesn't shut down. I have to press the on / off button on the computer to end my session.
I have been using Ubuntu 10.04 LTS for several months and recently the system has stopped closing down cleanly. It starts okay and runs just fine, but when I come to closing down it doesn't do anything after I've clicked on the shut down button. The same happens with the restart button. I have been closing the system by pressing the power button on the front of my tower. I have no idea as to why it won't close ... I haven't installed any extra software, so I guess it's a system problem. Closing down by pressing the power button cannot be doing the OS any good, so I could do with a fix ASAP on this one.
I recently purchased a dedicated server and have been having trouble with putty. I have been using the server to try and host the game called minecraft. Hosting the server is not a problem however. What is the problem is being able to exit putty without stopping the server. I looked this up, and it sayed to create a screen. I did that after installing screen. I then created a screen, ran the server, then tried to disconnect using the ctr-a-d.However only two things happen when i push the buttons. The majority of the time the window just closes, along with my server stopping. The other thing that happens is putty just stops. I cant type in anything, but I am still notified when I try to close putty.
I want to close an open port which is in listening mode between my client and server application. Is there any manual command line option in Linux to close a port ??NOTE: I came to know that "only the application which owns the connected socket should close it, which will happen when the application terminates."I dont understand why it is only possible by the application which opens it ... But still eager to know if there is any another way to do it ??
I'm wondering if there is any way to execute a program, run some command or anything else when closing the laptop's lid. My question aims to be generic, both for Windows and Linux. Something useful should be locking the laptop when closing the lid (Win + L in windows), or running expensive processes such as antivirus analysis etc. without doing it manually before closing the lid.
I am using putty to interact with Linux server. I have started a process using putty. The process is running and will take 5-6 hours. I want that process to keep running after I close the putty session. How can I keep that process alive after closing the putty session? I do not want to keep the computer ON all the time. Is there any way to do this?.
I run the ping command using system() in C. It start pinging the desired destination but when I close my application it continues to ping. Is there any solution that as soon as I close my application it also stops pinging. Any change required in my C code?