The title pretty much describes the issue. The timespan is sometimes some minutes instead of some seconds. I've tried unplugging every peripherials and disabling the touchpad, killing every non-critical processes, disabling and enabling Compiz, but nothing has helped so far.
I'm running Karmic on an Acer Aspire 8935G-874G100BN laptop with a Radeon graphics chipset.
The following script should make screen blanking work without disabling gnome-power-manager code...
This script can also be called from a panel launcher (with ./<scriptname> if it is in $HOME). It will not disable the power manager even though the process disappears from the system monitor. The "if" condition is necessary because SIGHUP will return an error if the process doesn't exist.
If you want a bash command, add this to $HOME/.bashrc:
# The following cannot be implemented as an alias
# and it cannot be called from a launcher, more's the pity
dark () code...
I tried to log on to a remote computer using ssh, but I got an error:
xset: unable to open display
I have installed Ubuntu 11.04, 64 bit and now I am trying to install/configure MFC-7420 scanner part (printer works fine)I tried to follow the steps listed at http://ubuntuforums.org/archive/index.php/t-590793.html, but I don't have etc / udev / rules.d/45-libsane.rules file to edit and can not continue with the remaining steps of the guide.
I also tried to follow the steps provided by the Brother Solution Center http:[url].... I have downloaded brscan2 64 bit and installed without error but when I tried to install the brscan-skey-0.2.1-3.amd64.deb using >sudo dpkg -i --force-all brscan-skey-0.2.1-3.amd64.deb I get the following error:
************************************************** **************************************************
sudo dpkg -i --force-all brscan-skey-0.2.1-3.amd64.deb
[sudo] password for aUser:
dpkg: warning: overriding problem because --force enabled:[code].....
Which dependencies am I missing? or What am I doing wrong?
I installed Ubuntu on a Toshiba Satellite about a month ago. It worked for about three hours. I installed Wine, and it still worked but the display would sometimes go black for a few seconds. Later that day I rebooted and that was it, no more Ubuntu. It goes through all of the process of booting but then the screen just goes black before I even get to the purple Ubuntu screen. I'm running this on a drive in an enclosure so I simply plugged the drive into another machine ( actually two other machines ), and it works perfectly. I have an old Vista drive that I put in the Toshiba and that works just fine, so it's not a pure hardware issue. Just to be sure I wiped the Ubuntu drive and re-installed, this time without installing wine. No Toshiba love. Just the black screen. I even made a flash drive with the loader and iso from the Ubuntu site. Same deal. It starts to boot from the flash and then just goes black where you would normally expect the purple Ubuntu screen. This thing is driving me nuts and I am at a point where I really need this machine working and will be faced with simply wiping the Ubuntu drive and installing Windows.
View 9 Replies View RelatedHow do I force grub2 to display the menu on a single boot installation of Ubuntu 10.04?
View 3 Replies View RelatedI have been messing about with my themes lately and was wondering if it was possible to force the title of a window to display on the right side and have the buttons on the right. I'm already aware of using gconf-edit to change the order and position of the buttons but I can't seem to figure out how to move the title.
View 8 Replies View RelatedI had my system running fine on Debian for about a month and a half. Then tonight the display suddenly went black. The system was still running, but my screen was black (though the monitor didn't indicate that it had lost signal). I restarted the computer; it booted through the BIOS and showed me my GRUB menu, but then the display went black again. Shorting the jumper pins to clear CMOS data didn't help; in fact, that made the display go black even sooner. Now, I see my motherboard's BIOS splash screen for a couple of seconds, and the display goes black. I know the system is still booting okay, because I hear the usually noises from the internal speaker. But I now have no visual output.
Could this be an issue with the motherboard or the video card? The board doesn't have onboard video, or else I'd try that. And I don't have any spare boards, video cards, or monitors available to me here. I did try using a D-sub cable instead of DVI-D (my monitor and video card support both), but that was no better. What can I do to try to fix this problem?
Motherboard: MSI 870A-G54
CPU: AMD Athlon II X2 250 (at 3.0 GHz, not overclocked)
Video card: Sapphire 100252HDMI Radeon HD 4550
Monitor: Asus VW195T
Is there a way to display the seconds on the clock of the GNOME status bar?
View 3 Replies View RelatedIs there a way for the time at the top of the screen to display seconds as well as the date ?
My clock seems to be about :40 seconds off... before i upgraded from f-13 i had my time controlled by ntp(how to verify ntp is enabled) ? even with network time = yes, it seems to lag a little.
I figured out the network time. it is under a whole separate menu for some reason.
Is there a way to get weather/ temperature like in classic gnome ?
Rite now my clock reads: tue 3:50 pm...Is there a way i can make it read: tue, aug 20, 2011 3:50:45 pm
I am running FC12 x86_64 with KDE 4.3.3 using an NVidia GeForce 9600 graphics card. I installed the drivers followings leigh's procedure and everything works fine -- apart from the fact that clicking the the "f" button to bring up the K menu takes between 8 and 10 seconds. Same thing happens if I select anything from the K desktop pop-up menu, like the Konsole or the run command for example. I disabled desktop effects but this had no impact.
View 1 Replies View RelatedSame problem with 11.4 x64 DVD version (gnome default). System ends with text before showing logon screen allso in failsafe
[code]...
I just installed Ubuntu 10.04.1 32-bit on a Dell Optiplex GX280 with Intel P4 3.4GHz, 1GB ram, 40GB hard drive, it's connected to a 17" CRT monitor which was detected automatically. Anyways, I set screensaver to come on after 15 minutes, monitor to shut off after 30 minutes and computer to go to sleep after an hour idle. The screensaver came on and monitor shut off as desired but the computer wouldn't go to sleep. So I manually put it to sleep (clicked "Suspend") and it went down and came back up just fine.I then did a few other things like installed java, flash, vlc player and I noticed that the screensaver won't even come on now. What is going on???Running:
Code:sudo lshwshows under display: Intel 82915G/GV/910GL Integrated Graphics Controller. Again the screensaver and DPMS WERE working, but they aren't now. I don't understand why Ubuntu isn't doing what I asked it to do in Preferences. it's very frustrating
A friend of mine recently broke his laptop's screen. He knew I wanted to setup a small personal server so he gave it to me. I used an old monitor and wiped the HDD and installed Ubuntu. At the end I chose to upgrade the freshly installed OS. When I rebooted the computer after upgrading I couldn't get any images on the monitor. I tried to unplug/plug it several times but it doesn't work. I keep getting the "No signal" message on the screen.
Is there a way for me to somehow force the computer to use the secondary display? And if not is it possible to install and configure all the packages to run a VNC server on it without seeing anything?
After upgrading to Mythbuntu 10.10 from 9.10 (clean install) on my combined front/backend I cannot get monitor (Dell 3007) to switch off from remote, I have been using simple script to DPMS force off for years with no problems, it still works, but some random time later the backlight comes back on. I have tryed the more complex scripts that stop and start the frontend and all of the acpi_osi options. Disabling screensaver has no effect. what causes this, or how to fix? Sysem is Abit IP35e (I suspect this board is the problem)
[Code]...
I have 2 remote frontends both upgraded OK. I have tryed installing 10.10 on a 'scrap' P4 machine, DPMS off works fine on it. I would try another install and/or another MoBo but its the only TV system in the house now.
I use 'xset r 133' to set autorepeat for the 'Windows key'.
But somehow after a while autorepeat does not work any longer and I have to redo the 'xset r 133'. I don't log out or so.
Ubuntu 10.04, gnome, compiz
There's a short version at the bottom.
I just installed jessie with gdm3 and use xfce.
I like my monitor to turn off when I'm not at the computer for more than 10 or 20 minutes or so and it wasn't doing that. I haven't used Linux for years and was used to xorg.conf/x11.conf and xinitrc and such.
So I rediscovered xset is responsible for DPMS settings. xset -q revealed DPMS was off. So I used it and put it in ~/.xinitrc. It didn't work. After some canoodling around I found out about xfce's Session and Startup gui thing. I was using that to run ~/.xinitrc.
When I got to my desktop and did a check with xfce4-terminal by running xset -q it would show DPMS enabled but the values were wrong. 600, 0, 900 to be exact.
After some searching I came across the information that xscreensaver will override DPMS settings as it manages DPMS too. So after more canoodling I found out about xfce's Screensaver preferences dialogue and used that to set my values. The values would immediately be set but the problem is that they are not persistent. If I reboot or log out the values will revert to 600, 0, 900. They will only reset to what I want them to be by running xfce's Screensaver preferences dialogue manually.
man gdm3, info gdm3, grep -r DPMS in /etc/gdm3, grep -r dpms in /etc/gdm3 reveal nothing related to DPMS. I've done some searching and nothing useful.
there is an /etc/X11/app-defaults/XScreenSaver-nogl which has some DPMS settings but the times are too large (2 hours); the only thing that matches is the off setting which is specified there.
xscreensaver -no-splash is present in the output of ps so it is xscreensaver and not gnome-screensaver.
The weird thing is that I re-enabled my ~/.xinitrc in xfce's Session and Startup gui thing and it is being run, but the numbers are getting set wrong after it is run. (I put an echo command after xset dpms 900 1200 1500, and the file is appearing in ~)
Where does 600, 0, 900 come from? Mystified on how to proceed from here. I don't remember enough on how to see what's doing what. Is there some sys thing or proc thing I can monitor to find out what's setting these values?
Short version: my xset dpms values are getting reset to 600, 0, 900 every time I logout or reboot. They revert to 600, 0, 900 every time I get to my desktop. I use gdm3 and xfce. Where are these coming from?
I'm using Debian Jessie on amd64. I have this video card:
Code: Select all01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [NVS 310] (rev a1)
I'm using the stock nouveau driver that ships with Jessie, and loads by default. I installed this card during my botched attempt to upgrade from Wheezy. This is a fresh install, and DPMS isn't working right.
I can run "xset dpms force off", and the screens will blank. I even see the "HDMI signal lost" screen of both (identical) monitors. However, before the power LEDs of either monitor go orange (instead of blue) the screens come back on as if I had made mouse or keyboard input. If I've locked the screen with xscreensaver, the screens are blank (I use only the blank hack). I've forgone the use of xscreensaver for now, believing it to be contributing to the problem. If I run "xset dpms force off" now, the screens blank, but the "HDMI signal lost" screen doesn't show, and the screens immediately unblank.
Here's the output of "xset q":
Code: Select allxset q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000000
XKB indicators:
00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
[Code] ...
It's like something is preventing the screen from going blank, but I don't know what it could be.
I installed the proprietary nvidia driver. Sadly, it does the same thing, so that's one thing I can cross off as the likely culprit.
Ran this command:
Code: Select allxset dpms 0 0 0
So when "xset dpms force off" is called, it powers down the monitor immediately. I will be reverting back to nouveau, and will report whether the problem resurfaces.
I have an embedded board with a small UPS. When AC power goes down, I need to turn off all power hungry devices in order to have a clean shutdown. First thing I do, is set DPMS to force powerdown, then go through the usual SIGTERM/SIGKILL/umount sequence. I have an Intel i915 Display adapter connected to an LVDS LCD panel.
Unfortunately, when Xorg dies, Xserver or the VT code turn the LCD panel back on.
I even tried working around it by directly poking the panel enable register in the Display chip, so that X doesn't know about it, but the panel goes back on when the VT comes back.
Is there any "legal" way of keeping the display off?
I have 2 Fedora 12 installs with this problem. Before installing FC 12, xset led 3 worked fine.
The command:
SHOULD turn on the scroll lock LED.
With FC 12, it doesn't.
In Xorg.log, I see: (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(I believe before FC12, I was using driver "kbd".) The man page for kbd shows the options needed for program control of the LEDs.
The new driver appears to be "evdev". I've read some of the HAL documentation and I think this driver uses the file: /usr/share/hal/fdi/policy/10osvendor/10-leds.fdi
I see nothing about program control in this file.
Anyway, anyone have any idea why xset led stopped working and how to go about fixing it?
Debian Lenny on a Toshiba Portege 350000:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1 (rev 82)kernel version 2.6.26-2-686On my system, "xset dpms force off" blanks the screen, but does not turn off the backlight. This means that the automated screen off in X does not actually save any power when it blanks the screen.I can turn off the backlight manually using the BIOS tool "vbetool dpms off" (but then I have to turn it back on again manually too).Question 1: is this a problem with the graphics driver interface, or with X, or with the power management driver interface?Question 2: as a workaround, is there any way for me to hook into the dpms off/on that X is doing, and run a script to call vbetool? The best workaround hack I have come across so far is to have a screensaver that calls vbetool, but I was hoping to find something that doesn't require me to run a daemon all the time.
View 4 Replies View RelatedWith keyboard : Illuminant model SK-020EL See next post for a workaround.
ETA : Code now works for my keyboard.
I recently did a clean install of Fedora 11 (from Fedora 10). In Fedora 9 and 10 I used a remote font server so that I could launch HP OpenView over a VPN tunnel. The procedure would go something like this:
*connect to VPN
*xset +fp tcp/<hp_ux_server>:7000
*ssh -X user@hp_ux_server
*launch OpenView
OpenView requires the fonts that are installed on the HP-UX server, hence the need for the xset command. Now since the installation of Fedora 11, I cannot get the xset command to work.
xset fp+ tcp/<hp_ux_server>:7000
xset: bad font path element (#23), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
I have turned off the firewall to make sure it wasn't blocking the request. But to no avail. I have also had two other people with Fedora 11 machines try this, they get the same error. Were there major changes in the X server from Fedora 10 to 11+?
Title is self-explanatory. I turn on swap, restart, and it's off again. Ubuntu 10.10 64-bit. I tri-boot with Win7 (32-bit) and LMDE (32-bit) if it matters.
View 9 Replies View RelatedI set up Plymouth and now it disables the GUI. I can only use the command line. It looks ugly and then it goes to TTY1.
View 2 Replies View Relatedso i've tried doing the whole /tmp as tmpfs thingy and it works!
View 4 Replies View RelatedI installed Ubuntu 10.10 on my Windows machine a couple of days ago via wubi (with no partition), and it seems to be working. However, I have a problem: When I press any of the 'special' keys on the keyboard (Vol up, down, mute, and various others), the left-click on my mouse disables. I'm using a Microsoft Digital Media Keyboard 3000, which has a lot of special keys (and the f keys are special by default), so I've been having trouble not disabling my mouse. Anyone know what the problem is, how to resolve it? And on top of that, how do I make the special keys work?
View 9 Replies View RelatedI have a Dell Inspiron 1520 with nVidia 8600M graphics card. I'm running 10.10 Maverick, and I've set up CompizConfig settings manager. Everything works just dandy, but it will sometimes disable all settings. Restarting X fixes everything, but I can't figure out why it disables in the first place. When disabled, all the visual effects are disabled (wiggly windows, transparency, desktop cube, etc.) The settings in System>Preferences>appearance>Visual Effects is set to Extra, and all my CompizConfig settings are the same. I haven't figured out any way to get it working again except by restarting X.
So far, the only times it has disabled like that are when I've set the computer to "suspend" or "hibernate", and a couple times when it has gone to screensaver while running on battery. It never does it while plugged in (but plugging it in will not restore the graphic effects) I have no idea how to keep the graphic effects working. Perhaps it's related to me unplugging my computer and running on battery? If so, is there any way to turn off this setting?
Making wifi work with ndiswrapper disabled usb automount. This happened on several ubuntu versions, including 10.10.
After following the directions given in this post [URL] usb automounting stopped working.
I fixed it this way:
Code:
sudo gedit /etc/modules
Added these lines to the file:
Code:
usb_storage
usbhid
Save and exit, worked after reboot or restarting network.
usb automount troubles could also be related to legacy floppy settings in BIOS, see
[URL]
I recently upgraded to 10.04 Lucid. Before I had the command "xset led 3" mapped to my scroll lock button. This turned on the SunbeamTech Illuminated Keyboard. Now it does nothing even when typing it into the terminal. Has anyone had this problem after upgrading?
View 2 Replies View Related