I moved from a Linux environment from one company to another and one annoying difference came out:When I used to run an application in a terminal (no GUI), the transcript lines were presented one the window - when the window was full then the scrolling of the lines would continue only if one hit the space bar to proceed (of course waiting to user input did not stop the run).
In the new environment the behavior is different - transcript lines keep going on and on so I need to scroll up - and moreover each page-up command is cancelled by the new lines appearing.perhaps this is also reproduce with other Linux commands , say "find" or "ls".
I have a headset microphone plugged into the built-in audio input. The output is plugged into an amplifier > speakers.
Pulseaudio is "helpfully" routing the microphone input signal to the speaker output. I do not want this. I go to pavucontrol and disable the "monitor of the internal audio analog stereo" -- and what I say into the microphone is still coming out of the speakers.
Google gives a lot of information about how to live-stream mic input over the Internet. And, I found this here (that's for karmic, I'm running lucid):
[URL]
... but that's about how to ENABLE loopback. It says loopback should not be enabled by default, but I very clearly hear that something is doing the same thing as loopback.
(Of course, I need to hear sound from applications that are playing, and when I'm dictating text into NaturallySpeaking running under virtual box, I need sound input to go there -- so turning the mic all the way down to zero is not the solution.)
I'm fairly sure I remember hearing this behavior ever since installing Ubuntu, and I didn't do anything to turn it on. I can't imagine most users would prefer this behavior -- if it's the default behavior, why? It makes absolutely no sense to me. (Sorry. It's one of those piddly little configuration things that costs a couple of hours of web searching time, and after a while I just have to give up, but not before becoming much more frustrated than I should have to.)
So, to be clear, here's what I want:
- Applications playing audio should send sound to the main output.
- Applications receiving audio input should hear the microphone.
- Microphone sound should not EVER go to the main output unless I have explicitly launched an application making the connection. (The signal goes input -> output even when NO application is open - hence my consternation.)
I've recently noticed that my IEC958 digital audio output has stopped working. The short version of why I didn't notice this immediately is that I have two simultaneous audio outputs from my system to my speakers and I hadn't realized the IEC958 output wasn't in use.After messing around with a few settings to no avail, I remembered that I'd recently run update manager (this had to be within the last two weeks) and thought this might be the cause.I have just booted to a 10.10 install disc and verified the IEC958 output works fine there.
Unfortunately I'm not sure which of the recent updates could have caused this problem. Before I submit a bug report on launchpad I was hoping anyone here might have a suggestion as to where to look to figure this out.I'd recently seen this thread and this thread which lead me to believe it may have been a recent kernel update.What's my best course of action to determine the problematic update?[edit]In case anyone needs the info, I'm running Ubuntu 10.10 64 bit on a system with an Intel DH57JG motherboard. Using the HDMI output to a TV, with a separate optical audio cable to my speakers.Also, I've attempted using all of the available digital audio output options in the sound preferences panel and I've also installed gnome-alsamixer and tried enabling/disabling every digital output listed there as well. None of these got the optical output working again.
I installed a fresh Debian Desktop without the LAN cable connected. After that I got message when I put the cable in:
Code: Select allNetwork Interface Connection New Wired Connection failed
I have tried to re-install everything once again with the cable in, but during the Debian installation there was no network detected.
However, I proceeded and re-installed Debian. But the problem persists. It continues to re-connect and than disconnect. There is a symbol showing re-connection. The network eth0 is visible to the machine.
I booted Mint Live disc and the same happens there.
I'm trying to setup VNC on our debian server so the boss can remotely do admin stuff from anywhere in the world. the first step is getting it working from anywhere in the room, though. And I can't even seem to get that far.
So far I have a VNC server setup, although not without problems. I downloaded and installed vnc from the vnc site, that wouldn't work because trying to start a vnc server gave this error: "error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory"
There are lots of results on google for this error, and the solution everywhere seems to be the same. to install the package: libstdc++2.10-glibc2.2
However, trying to install this package in debian fails. both using apt-get and trying to manually download it from packages.debian.org it just doesn't seem to exist.
I've tried tightvnc from the official repositories and it gives the same error, too.
The way I got around that eventually, thanks to another tutorial, was to install the package vnc4server. then run vnc4passwd to create a password. and after that vncserver works fine, or seems to. Creates display 1.
Now, when I'm trying to connect to hostname:1 from another computer in the LAN. It gives error 10061, connection refused. I installed the debian and I don't recall setting it up to refuse connections on port 1. Is there anything I should check or change to allow the connection, or any log file in debian to check and see what's going wrong?
I'm also trying connecting internally via client on the debian machine, but I can't runvncviewer. I get the same missing shared library error as before. I guess I just worked around, not solved it.
I also can't access it with the java viewer. Trying to connect on port 5801 either from the server itself, or from another one on the lan, tells me it's refusing the connection.
To be clear, I'm certain that the vnc server is started. We have working DNS, and trying to connect directly to the internal IP:1 doesn't work either.
I updated my Jessie system today. Nothing crucial in the apt-get list as far as I can see, perhaps it's unrelated. Anyway, now I cannot open the terminal any longer. Launching `gnome-terminal` shows the app name in the menu bar, a spinning wheel, and then after a few seconds nothing. It doesn't appear in the list of processes, either. I can still log into the text shell via ctrl-alt-F1.
I also added `LC_TIME="en_GB.UTF-8"` to `/etc/environment` to get rid of the American date format. Could it be the cause? I just tried to launch the terminal from the JVM. I get this output:
Code: Select all(process:2629): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. 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 8
I will delete the environment variable again and reboot, but I wonder if I can still have the British date format?
How to get compiz to auto-start. What seems to be the generally accepted method (from what a few google searches and the debian wiki tell me) of using gconf-editor and changing the window manager from 'gnome-wm' to 'compiz' in desktop > gnome > session > required_components doesn't change anything. The only method I found that did not involve using a terminal and running 'compiz --replace' every time I boot the computer was to add compiz and fusion-icon to the gnome startup apps, but this causes unwanted flickering (it starts metacity and then replaces it with compiz, ie it's simply automating what I would do with the terminal). Autostarting the fusion-icon alone does not start compiz, although it allows me to start it from it's menu if I right click the icon. Note that I sometimes use fluxbox as well, so starting it on boot isn't really an option either.
Perhaps this can be useful : compiz: Installed: 0.8.4-4 Candidate: 0.8.4-4 gnome-session: Installed: 2.30.2-3 Candidate: 2.30.2-3
I am not referring to the bash history file. I am referring to the system log file. All of my console activity (letter for letter) is being stored in the system log. It's my understanding that version 4.1 of bash is where this behavior first started but was originally optional. I don't like it and I want to stop it. I am using a current version of jessie with bash 4.3 and I can find no way of turning it off
Monitoring the activities of users may be necessary .for admins in a business environment but this is a home computer and I consider this kind of tracking intrusive and unwanted.
I first noticed this with the journal system log and mistakenly though it had to do with journal so I removed the journal system and installed dsyslog which has the same behavior.
Perhaps debian should offer two versions of bash. It's my understanding that this is configured in a header before compiling.
I can't spin down my internal windows SATA disk with sdparm anymore. It worked well in Lenny, but not in squeeze. The disk I'm trying to stop is not mounted or anything. Is this something udev related?
I'm running Debian 8.4 on a Lenovo W500 laptop and I recently upgraded from kernel version 3.2.0-4 to 3.16.0-4. Since then I encounter issues with lightdm (I suppose) which manifest themselves in two different scenarios:
1) scenario 1: lightdm fails to start.Instead of showing the graphical login screen, the system boots into terminal. Lightdm seems to be running, but I can't enter the X-Session (Alt+Ctrl+F7 doesn't work), nor can I restart the lightdm via
Code: Select all# service lightdm stop # service lightdm start
dmesg shows the following (I've only pasted the end of dmesg): Code: Select all[ 240.100071] INFO: task kworker/0:2:39 blocked for more than 120 seconds. [ 240.106512] Not tainted 3.16.0-4-amd64 #1 [ 240.112956] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.119494] kworker/0:2 D ffff880155155a48 0 39 2 0x00000000
[code].....
and /var/log/lightdm/lightdm.log shows errors of type Code: Select allGtk-CRITICAL: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
when I then try to shutdown via Code: Select all# shutdown -h now
the OS gets stuck on a message of the form Code: Select allirq 17: nobody cared
and eventually I have to force a shutdown by holding the poweroff button.scenario 2: lightdm starts, but can't be stopped/In this case I can login and use the system as usual, but when I try to shutdown either via # shutdown -h now, or via the GUI or the power button, the system gets stuck and I have to force a shutdown by holding the poweroff button.It seems that people had similar issues on other distros (see e.g.: URL... but there doesn't seem to be a good fix so far. I can for now solve the issue by downgrading the kernel to 3.2.0-4, but I was wondering if there is a permanent fix.
I'd like to know if there's a way, an option or something that will allow me to keep my .desktop files in /usr/share/applications untouched when I upgrade their programs.For example, I only want Chromium to appear in XFCE (for all usersdded the OnlyShowIn=XFCE" option to its .desktop file. The problem is that aptitude upgraded Chromium and reverted its desktop file back to its original configuration. Of course, I went ahead and added the same option again, but I'd like to know if there's a way to changs behavior of aptitude. I don't want to imagine the work I'll have to do again when they release a new version of KDE in the repos and I have to edit all of those files again. searched the forums for ".desktop files" and also for "/usr/share/applications" and got no significant results in the first 10 pages. The same with google. I'd appreciate it if someone could point me in the right direction. Would it be a possible approach to add a directory to /etc/ to keep my settings fixed, the way there's an /etc/menu?
Well it turns out my system has logged out more then once on its own. I had the system updated and upgraded from 7-3-11 and it did this about once a week. On 7-18-11 I did a full update and upgrade and it logged out a few times in a couple of hours. It does it while I am away and the system is in screen saver mode. I used my partition clone and restored the system back to 7-3-11. Has any one else ever had such an issue?
I am trying to make a web server with debian 6 and i want a xfce dsektop when i need to open files,extract,navigate but to be able to turn it off when i dont need it (to save ressources).I already installed it with aptitude install xorg and aptitude install xfce.
I'm running a SuperMicro GPU server with nvidia GFX 750 card. Debian Sid with last update this morning. The server is far away from the screen. So i'm using 5m active USB 2.0 cable with one Belkin powered hub. All USB device work always correctly.
But sometimes, my keyboard (a logitech illuminated) doesn't work anymore. I need to disconnect and reconnect it. Backlight keep on but no key work. I can't change the numlock or caps lock too.
Apparently, this appear mainly (only?) when i use the keyboard (for shortcut or typing text in vim).
I've tried with and without autosuspend (setting manually or from GRUB).
I have just install debian squeeze in my old laptop (HP nx6120). Everything works fine except for the fan. When it boots up, the fan is really silent but after a few of minutes it starts working and doesn't stop at all. The CPU usage is low (1%) with 53MB/512MB of used RAM.This is how I install Debian:_ During the installation, I chose to install the "laptop" and "base system" categories (the last 2 categories of package)._ I use FluxBox as my graphical environment and Slim as login manager.I have Ubuntu installed before and it didn't happen so I think this is a configuration problem
I have a Debian Etch machine that was given to me but when it boots up it executes a program that is located on my desktop.
I don't want to move or rename the program but would like to prevent it from starting when the machine starts. Anyone have any idea as to what file I need to edit in order to achieve this?
I tried to install Debian-Squeeze 64-bit from CD [URL] as I thought mistakenly my cpu has 64 bit support. Ofcurse proccess stoped as the kernel wasn't compatible, but only when I removed the 'quiet' parameter I could see the error, when the 'quiet' parameter was passed, process gave no visible error,just stop in the start screen of debian-installer.
I've bought a new notebook. The hard drive won't stop spinning down and then spinning up again during load. I don't want HD power saving, so I disabled it within
Is there a way to instruct mencoder to stop streaming/recording after a specified period associated with a loss of signal?I use mencoder to record over-the-air television recordings. Most of the time there are no problems.Occasionally a station's transmission signal disappears, caused by quirky atmospheric conditions, usually at night.Noticing these signal outages is easy by the mencoder error message:dvb_streaming_read, attempt N. %x failed with errno %y when reading %z bytes"Lengthy outages are unbearable because mencoder silently waits forever rather than quit.The significant problem with lengthy signal outages is mencoder continues recording for the time specified by the -endpos parameter. Thus, for example, if the recording is scheduled for 2 hours and there is a 20 minute loss of signal, the recording does not end until 2 hours and 20 minutes after starting.
Generally, when the interruption is lengthy the recording is ruined and I don't care to watch. I would like to programmatically tell mencoder to stop waiting and quit.Is there a way to do this? Say, after ten minutes of no signal, just terminate.I do not notice any parameters that might offer that option, but I could be overlooking something obvious. I tried the -skiplimit parameter with no success.I am aware of the MPlayer/MEncoder Tips and Tricks thread.
Im totally newbie is *nix OS (including debian) but more than pro in Win, so treat me with understanding,
TECH SPEC: Debian 6 Gnome 2.30.2
PROBLEM DESCRIPTION: Mouse still working well during random period of time (it may be less then one minute and more then few hour's from boot up) then instantly stop moving (cursor are freeze) but it still active. Obviously it is not associated with any program, coz it happens even on log-on screen.
One thing make this case unusual - im using Logitech Wireless Desktop MK710 keyboard + mice set. It mean there is only one receiver for both devices. You guessed it, keyboard continues to operate normally after mouse fail! Absolutely normally! Even more, if i connect new wired usb mouse at this time, it will be work well, but not for log... after random period of time it goes freeze too =/ KEYBOARD STILL WORKING
Running Debian lenny.I want Debian to stop from loading certain kernel module at startup. For now I tried adding "blacklist my_module" line in /etc/modprobe.d/blacklist file with no luck. Also I tried to add line above into some new file in /etc/modprobe.d directory - not working.How do I blacklist kernel module in Debian lenny ?
I have debian/sid on my new hp/Compaq Presario CQ62 laptop. I installed usplash and started getting booting issues every fourth or 5th boot. The system stops responding till I power off the system by pressing the power switch. I checked the syslog and noticed that it also stopped without logging the cause.
By the way, except the above issue, every thing works great on my laptop with debian/sid including the wireless using the native linux driver which I obtained from hp website.