Sponsored Content
Full Discussion: Screen fading out and in.
Operating Systems Linux Ubuntu Screen fading out and in. Post 303003281 by kkeevv on Monday 11th of September 2017 03:45:56 PM
Old 09-11-2017
Quote:
Originally Posted by Corona688
I have experienced this hardware issue in CRTs before. It can happen when the flyback transformer loses voltage due to shorting or from its driving transistors overheating. It happens most often when the screen is left on for long periods of time.

Try swapping in an LCD to see if the problem goes away.
I have two CRT monitors, both work fine with WinXP. Both PC's are identical except one is set up for dual boot. The problem started when I installed Ubuntu and only occurs while running Ubuntu.

---------- Post updated at 02:45 PM ---------- Previous update was at 02:32 PM ----------

Quote:
Originally Posted by Peasant
I have a couple of questions if you be so kind to answer.
  1. Have you updated the boxes with firmware (I see 2011 and 2012 bios version) ?
  2. Can you confirm you are running both boxes on same ubuntu release (17.04) and the XP does not experience such problems ?
  3. After a blackout, is the pc functional or dead ? Can you perhaps use ssh to connect during blackout ?
  4. You might want to check out the logs during the incident if you can ssh in.

    If you cannot ssh, a more serious issue is at hand.
  5. What kind of GPU or GPUs are inside (stock, multiple ..), I suspect radeon ?
  6. Are you using stock out drivers or you installed them and if yes how ?
1. No I have not installed new BIOS. I don't see the need right now, that's not the problem. UPDATE: PC does have latest firmware version.
2. Yes both are running 17.04, and no the problem doesn't occur while logged on to XP.
3. It doesn't black out it just dims and becomes un responsive for several seconds.
4. I will try to locate log files. Didn't know ubuntu recorded such events.
5. integrated intel graphics media accelerator 3100
6. it's using what ever drivers ubuntu loaded when I did the install.

Last edited by kkeevv; 09-15-2017 at 07:45 PM..
 

10 More Discussions You Might Find Interesting

1. Programming

How to clear screen

I searched the post and someone said to clear the screen in C, use printf("\033[2J"); ?? However, this doesn't work...typo or no. What is an equivalent command to 'CLS' in DOS/'clear' in UNIX to clear the screen and go to top of screen?? Thank you. (2 Replies)
Discussion started by: giannicello
2 Replies

2. UNIX for Advanced & Expert Users

printing to the screen

HPUX 11.0.X / Korn Shell Hope this makes sense. I have a little function to place things on the screen using the column and row parameters. Question is, how can I be sure of where the current cursor postion is so that if I print something to the upper right hand corner of the screen, I can... (2 Replies)
Discussion started by: google
2 Replies

3. UNIX for Dummies Questions & Answers

reading from a screen

Hi There is a program running which displays output on the screen I have to grep a particular string from that screen how do i do this My problem is i'm running this program from a script which executes after every fifteen mins but sometimes it's happen that there is an error in the program... (4 Replies)
Discussion started by: satyanarayang
4 Replies

4. UNIX for Dummies Questions & Answers

no screen output

I'm a newbie. I'm having a problem at work with a script. What i'm trying to do is connect to a cisco switch from a sun station. After i run the script and telnet into the switch i don't get any output on the "xterm window" and all my commands from the script don't show up on the screen or on... (0 Replies)
Discussion started by: wisher115
0 Replies

5. UNIX for Dummies Questions & Answers

Double screen

Hi Guys, I'm using a double screen machine with linux Red Hat. The problem is that I see the same image in both screens... Can anybody tell me how to solve this problem? Thanks a lot, Pablo. (0 Replies)
Discussion started by: cordobapablo
0 Replies

6. UNIX for Dummies Questions & Answers

Help with screen

Hello everyone! I'm trying to figure out how to send commands from one screen to another. For example i wish to send a simple "ls -all" from screen #1 to screen #2, can it be done, and how? :confused: Thank you! (12 Replies)
Discussion started by: Gurth
12 Replies

7. OS X (Apple)

Virtual screen accessed by Screen Sharing

Hi, I'm trying to create a virtual screen, (maybe xvfb? or any other virtual screen buffer) and be able to use Screen Sharing to connect to it. The setup is that I have a Mac Mini connected to the TV. But when my girlfriend is using Front Row, I can't use Screen Sharing at the same time from... (0 Replies)
Discussion started by: linge
0 Replies

8. Red Hat

command line tool to disable screen lock and/or screen saver

Hi, I have a simple question : how to disable screen lock and/or sreen saver with command line with RHEL5.4 ? (1 Reply)
Discussion started by: albator1932
1 Replies

9. UNIX for Dummies Questions & Answers

Accidentally made a screen within a screen - how to move it up one level?

I made a screen within a screen. Is there a way to move the inner screen up one level so that it is at the same level as the first screen running from the shell? (2 Replies)
Discussion started by: phpchick
2 Replies

10. Shell Programming and Scripting

O/P same as on screen

#Random Scripts 4 #Desc: clear echo "1. To see all processes currently running on the system" echo "2. To kill any given process" echo "Choose between the two" read x case $x in "1")print `ps aux`;; "2") echo "Choose a process to be killed" read y check=`ps ax | grep... (1 Reply)
Discussion started by: targetshell
1 Replies
PBUILDER-DIST(1)					      General Commands Manual						  PBUILDER-DIST(1)

NAME
pbuilder-dist, cowbuilder-dist - multi-distribution pbuilder/cowbuilder wrapper SYNOPSIS
pbuilder-dist distribution [architecture] operation [options] [...] cowbuilder-dist distribution [architecture] operation [options] [...] DESCRIPTION
pbuilder-dist is a wrapper that makes it easy to use pbuilder with many different versions of Ubuntu and/or Debian. It is common to symlink this script in order to give it many names in the form of pbuilder-distribution or pbuilder-distribution-architec- ture, like for example pbuilder-feisty, pbuilder-sid, pbuilder-gutsy-i386, etc. The same applies to cowbuilder-dist, which uses cowbuilder. The main difference between both is that pbuilder compresses the created chroot as a a tarball, thus using less disc space but needing to uncompress (and possibly compress) its contents again on each run, and cowbuilder doesn't do this. USAGE
There are many arguments listed on the synopsis; each of them, if used, has to be used exactly in the same order as it appears there. In case you renamed the script to pbuilder-distribution, do not use the distribution parameter; same with i386 / amd64 if the name also con- tains -architecture. distribution Replace this with the codename of the version of Ubuntu or Debian you want to use. architecture This optional parameter will attempt to construct a chroot in a foreign architecture. For some architecture pairs (e.g. i386 on an amd64 install), the chroot will be created natively. For others (e.g. armel on an i386 install), qemu-user-static will be used. Note that some combinations (e.g. amd64 on an i386 install) require special separate kernel handling, and may break in unexpected ways. operation Replace this with the action you want pbuilder to do (create, update, build, clean, login or execute). If you don't specify any action, but the next argument is a .dsc file, it will assume that it should build. Check its manpage for more details. [...] Replace this with other parameters, if needed. For example, if build is the option, you will need to also specify a .dsc file. As a special feature, if you specify a .dsc file you can skip the build option and this script will automatically assume that building is the action you want to do. OPTIONS
--main-only (deprecated: mainonly) If you specify this option, only packages from the main (in Debian) or main and restricted (in Ubuntu) components will be used. By default, all official components are enabled. This only has effect when creating a new environment. --debug-echo The generated pbuilder/cowbuilder command will be printed to the standard output instead of being executed. This is useful for debugging. --buildresult DIRECTORY (pbuilder-dist only) If this option is specified, the resultant files of the pbuilder build are placed in DIRECTORY. --release-only Only use the release pocket. Default for development releases. --security-only Only use the release and security pockets. Suitable environment for preparing security updates. --updates-only Only use the release, security, and updates pocket. Not the proposed-updates pocket. EXAMPLES
pbuilder-dist gutsy create Creates a pbuilder environment for Ubuntu Gutsy, with all components enabled. pbuilder-sid --main-only create Creates a pbuilder environment for Debian Sid, with only the main component. pbuilder-feisty build ./sample_1.0-0ubuntu1.dsc Builds the specified package on an already existing Ubuntu Feisty environment. pbuilder-dist feisty withlog build ./sample_1.0-0ubuntu1.dsc Same as above, but stores pbuilder's output on a file. pbuilder-etch i386 update Updates an existing i386-architecture Debian Etch environment on an amd64 system. cowbuilder-experimental create Creates a cowbuilder environment for Debian Experimental. FILES AND ENVIRONMENT VARIABLES
By default, pbuilder-dist will store all the files it generates in ~/pbuilder/. This can be changed by setting the PBUILDFOLDER environment variable. If the directory doesn't exist, it will be created on the run. A file with the log of the last operation, called last_operation.log, will be saved in the results subdirectory of each build environment. The default authentication method is sudo. You can change this by setting the PBUILDAUTH variable. By default, pbuilder-dist use the master Debian and Ubuntu mirrors. The pbuilder MIRRORSITE and OTHERMIRROR variables are supported, as are the standard ubuntu-dev-tools variables: UBUNTUTOOLS_DEBIAN_MIRROR, PBUILDER_DIST_DEBIAN_MIRROR, UBUNTUTOOLS_DEBSEC_MIRROR, PBUILDER_DIST_DEBSEC_MIRROR, UBUNTUTOOLS_UBUNTU_MIRROR, PBUILDER_DIST_UBUNTU, UBUNTUTOOLS_UBUNTU_PORTS_MIRROR, and PBUILDER_DIST_UBUNTU_PORTS_MIRROR. See ubuntu-dev-tools (5) for details. You may also want to know that pbuilder-dist exports DIST and ARCH environment variables to the invoked process, containing the name of the distribution and the architecture targeted by the current build. You can make use of them, for example, in pbuilderrc. BUGS
If you experience any problem with this script contact me on rainct@ubuntu.com or file a bug at https://bugs.launch- pad.net/ubuntu/+source/ubuntu-dev-tools. Please ensure first that the problem is really this script and not an issue with pbuilder or cowbuilder themselves. SEE ALSO
pbuilder(1), pbuilderrc(5), cowbuilder(1), ubuntu-dev-tools(5). AUTHORS
pbuilder-dist and this manual page were written by Siegfried-A. Gevatter <rainct@ubuntu.com>, with contributions from Iain Lane <iain@orangesquash.org.uk>, Emmet Hikory <persia@ubuntu.com> and others. pbuilder-dist is released under the GNU General Public License, version 2 or later. ubuntu-dev-tools January 10, 2008 PBUILDER-DIST(1)
All times are GMT -4. The time now is 05:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy