Debian :: Pavucontrol Resets Every Time During Reboot
May 16, 2015
if I have to reset my system for any reason or even logging out my pavucontrol resets to my built in audio instead of sticking to my HDMI like I want it to.I can manually configure a file I will, I just need to know where to start.I will provide hardware info when asked for it, just need a feeler here.I am running Debian Jessie KDE 64bit
I've just installed Debian 8 XFCE and I can't get the sound working properly after a reboot. I mean I can but it keeps resetting to default audio output (analog-stereo) after reboot.
I set it to Digital Stereo in Pavucontrol settings, reboot and here comes analog-stereo again.
I've tried setting digital stereo as default using pactl in the terminal but same problem. When I change settings then relog in my session, sound is working, but when I reboot it reverts back to default output. Strange.
I'm using Gnome and OpenSUSE 11.2, and my keyboard layout changes USA from Finland every time I reboot my pc. I have to delete USA-layout from keyboard preferences every time after reboot.
I have a Geforce GTX 460 GPU and I recently switched from Ubuntu to Suse 11 and I have installed the latest Nvidia drivers (the same as I had on Ubuntu) In Ubuntu I had configured the xserver to display my desktop on my LCD monitor and my LED TV as clones and everything worked fine When I change the settings in Suse everything works fine until I restart the Xserver. All my settings disappear and everything is back to the standard settings again. It doesn't seem to make any difference whether I have root privileges or not, and I have tried saving to etc/X11/xorg.conf., etc/X11/xorg.conf.install, etc/X11/xorg.conf.backup but each time I reboot everything is back to the default settings again. In Ubuntu I just saved the new settings to etc/X11/xorg.conf. and restarted the Xserver and all was fine.
Here is a copy of what I saved to the X config file:
# nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 270.41.06 (buildmeister@swio-display-x86-rhel47-07.nvidia.com) Mon Apr 18 15:15:00 PDT 2011 Section "ServerLayout"
[code].....
ERROR: Invalid display device DFP-2 specified on line 56 of configuration file '/root/.nvidia-settings-rc'(the currently enabled display devices are DFP-0 on linux-c0rf:0.0). and all the settings are defaulted
I have installed wally on my Dell inspiron 1420 with Ubuntu 10 10 . I have pointed wally to my personal picture folder in an external drive in folder settings. But whenever i reboot folder settings gets reset and i have to set the picture folder path again. Is there a way by which what ever path i set will stay after the reboot of the system.
I currently have the proprietary drivers for nvidia installed for my gtx 460, nvidia drivers are ver 270.41.06. Ever since I reformatted my computer and got the new nvidia drivers, every time I reboot my resolution goes to something horrible(1024x76 on a monitor capable of 1920x1080. While I can simply change it every boot, it gets quite tedious so I have a script to run on boot:
Code: xrandr -s 1920x1080 To set my monitor to its proper resolution, the issue is I still have to reset gnome panels etc every time after the resolution has changed the config. My xorg.conf is as follows: Code:# nvidia-settings: X configuration file generated by nvidia-settings
[Code]...
I have also tried changing the default resolution in the server settings manager and saving the xorg.conf file, but nothing seems to work. Is there any way to change this/has anybody else had the issue? I'm considering going back to an older version of the drivers if that would solve it,
I just install a GT240 video card on my desktop. The monitor that I've been using is a 50PH9UK plasma TV. The TV is connected to the desktop through VGA output. It appears that Fedora sets the screen size at 1360x860 by default. However, I prefer to set the screen size at 1020x768. The problem is that everytime I reboot the desktop, Fedora automatically resizes the screen to the default resolution (1360x860). I tried to look for the xcon.fig file in /etc/X11/ but it's not there. It appears that the xcon.fig is missing. Do you know how I can correct the automatic screen reset issue? By the way, I'm using the Fedora 14 KDE version.
The volume keyboard shortcuts on my Asus Eee 1008p resets on reboot.(going back to no shortcut at all). It works for the session, if i set it, but after reboot i have to set it again.
I've read some people having the same problem, but I can't manage to fix it. I got a 1440x900 screen. Every time I reboot my system starts up with 1400x1050 , I have to go to System settings to fix it, options don't get saved as one would expect.
Well, I think my problem is cause of nvidia drivers, so I go to nvidia settings to get this fixed. But, these settings are all fine, it says 1440x900. When I try pressing Save to X (to make sure it gets saved), i get a failed to parse message (Failed to parse existing X config file '/etc/X11/xorg.conf'!). I've got driver version 256.53
Oh well, screw this, I'll do it manually, so I go to the xorg.conf file. But over here everything says 1440x900. How come my resolution keeps changing each time I reboot?
I have Ubuntu 10.04 32bit installed on my desktop. My video card is an nVidia 7800 GT. My Monitor is a Sceptre X24WG. I am able to use the NVIDIA X Server Settings utility to change my resolution to 1920x1080 as well as 1920x1200,and 3d opengl accelerated games work. When i reboot, the x server comes up with 1280x1024 as the resolution. I want it to remember the resolution i selected instead of defaulting to a different resolution.
I was running Kubuntu 8.10 previously and had some difficulty setting up the graphics initially, but i don't recall what steps i had taken to get it to work. When i recently reformatted to install Ubuntu 10.04, it wouldn't go directly to 10.04. The screen would go to a garbled display and would load the install window, so i installed 9.04 and then upgraded to 9.10 and then 10.04, without trouble.
I'm using the nVidia hardware driver version 195.36.15, which in the hardware drivers utility is listed as the current and recommended version. It originally wouldn't install until after i had rebooted into the 2.6.31-21 kernel. I have tried the option to save to x configuration file. When i save to x configuration file, the xorg.conf in /etc/X11/ looks like this:
Code: # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 1.0 (buildd@palmer) Fri Apr 9 10:35:18 UTC 2010 # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 (buildmeister@builder75) Fri Mar 12 01:42:27 PST 2010 # xorg.conf (X.Org X Window System server configuration file)
I done searches for "clock" and found similar threads, but no real fix that is working for me. My clock resets when I boot into linux. It does not happen in windows or bios even on cold boots. The battery is replaced and good** the old battery was by all measures dead (0.6v), but still seemed to have enough power for the clock, since windows tested fine with it.
I have tryed setting it to local time, UTC.. etc... My timezone is GMT (london). "sudo /sbin/hwclock --systohc" Although I have windows, I do not use it except the few times to test this, so no conflict.
I have recently installed ubuntu as my main operating system, everything has been working great except every time I re-boot the resolution resets back to a default. How can I get it to default to 1440x900?
I'm on 10.10 Everytime I start my iMac, the volume in alsamixer is reset to zero. It takes 8 seconds to fix, but I'd rather not have to do this every time I boot up. Anyone know how to fix this?
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
I've read from some Web-page that GNU/Linux resets it's uptime every 497 (498) days... So even if GNU system works 1000 days, uptime never will be more then 497 (498) days. Is it true?
When I logout out of gnome, the brightness reaches maximum level. I've tried adding a script to adjust the directory "/sys/class/backlight/intel_ backlight/ brightness" to the rc.local file. I'm not sure if it has to do with my video card but it certainly could be the case since I'm using an experimental package for the Intel graphics card.
I have a custom .Xmodmap file to change the keyboard layout. The problem is that sometimes the keyboard layout changes back to the default. I have seen the lights on the keyboard blink at times, so I tried unplugging and reconnecting the keyboard and yes - that reset the layout. I can see keyboard removed/detected entries in the logs as well, so I guess my keyboard reconnects sometimes, I don't know why. However the solution from the post earlier (to rename the xmodmap file to ~/.Xmodmap) did not work. So is there another default filename I should use? Or do I have to enable xmodmap to run when a keyboard is plugged in somehow?
The only thing I can think of right now is to monitor /var/log/Xorg.0.log for "Adding input device USB Keyboard" and running xmodmap when that happens... but I'm really hoping for a better solution.If I can't fix the xmodmap problem, maybe I can fix the usb disconnects.I read something about power saving settings for usb. After some digging, I found that those settings are in /sys/bus/usb/devices/.../power/. However, disabling autosuspend for the hub did not seem to work (it was already disabled for the keyboard).
But I found something else in kern.log. Perhaps the keyboard disconnects has something to do with static electricity?
Code: Select all[ 7078.175830] usb 1-10-port3: disabled by hub (EMI?), re-enabling... [ 7078.175888] usb 1-10.3: USB disconnect, device number 4 [ 7078.624349] usb 1-10.3: new full-speed USB device number 6 using xhci_hcd [ 7078.729012] usb 1-10.3: New USB device found, idVendor=04d9, idProduct=0125 [ 7078.729014] usb 1-10.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 7078.729016] usb 1-10.3: Product: USB Keyboard
when I was entering a sed command, with a back-reference to the scnd set of parenthesis. 2 reset X, or so I though ... I did some experimenting, and lo and behold, I could reproduce the behaviour even on the xdm login screen, when I typed in my sed expression as the name. Not every time, not accurately, but maybe 3 out of 10 times I can reset X by pressing 2 on the numeric row in a quick succession with other keys, and the I at first thought was required to trigger the behavior is not necessary at all. Nothing in the X-log, nothing in ~/.xsession-errors.
I'm annoyed, and as X is quite sizable and spawns a truckload of processes I'm highly reluctant to try and reproduce the behaviour under the control of strace (mind you, since it seems to be "speed" related it maybe wouldn't even occur under strace ;}). I'm running Slack64 13.0 on a Thinkpad R500 with an Intel GMA 4500MHD graphics chipset, can't think of anything else that might be special with this hardware in regards to X.
1. Use yum to install pavucontrol Go to tab "configuration", choose "off"
2. remove alsa-plugins-pulseaudio, if you installed it before
3. Go to "System->Preference->Startup Applications", deselect the "Volume Control" application from "gnome-media" package, which only uses pulseaudio interface
4. Use yum to install python-alsaaudio pygtk2 gnome-python2-libegg gst-mixer Then add the attached python script to "Startup Applications", which mimics the behavior of volume control but using alsa interface. This is a modified version from its origin: http://david.chalkskeletons.com/files/volume-tray.py which adds a feature of changing icon according to the value of volume.
I added an ext4dev filesystem to my hard drive as /dev/sda3 and mounted at /share with the goal of putting all of my multimedia files on it and sharing it through NFS. I followed this guide: [url]
Of course, this was from lenny (hence the -dev). The partition was fine, and I mounted it numerous times. I also performed a dist-upgrade to squeeze. I shutdown that computer with the usual 'shutdown -h now' and disconnected the AC power cord from it, because I wasn't planning on using that machine for awhile. As far as I could determine, everything was fine before I unplugged it.
Every time that computer is powered off, the clock resets to 1999 because the battery is bad. So I am used to getting the "last mount time is in the future" error.
Three weeks after halting, I powered the computer back on. It was unplugged until this point. I got an error message when it attempted to mount /dev/sda3
I then removed its line from /etc/fstab, rebooted. and tried to check it, but I just keep getting the same error-- even with the '-b 8193' option.
The machine is still using the 2.6.26 kernel from lenny. I am building a new one right now (2.6.30), hoping that the problem is caused by the ext4dev/ext4 module. Otherwise I don't know what to do.
I had installed pavucontrol in Ubuntu 10.04 to record the sounds being played on the system, by changing the "Record stream for" value to "Monitor of Internal Audio Analog Stereo". I installed pavucontrol in Maverick as well, but here it doesn't capture and show the sounds being played at all, not even in playback (No sound meter bar activity below each entry). The sound can still be decreased/increased and it shows all the devices playing back or recordong. Also if I change the hardware to "Digital duplex" from Analog stereo Duplex" it starts capturing and showing the streams, but then I can't hear anything from the speakers. I even compiled the newest pavucontrol, but still the same.
So, I've to machines running Ubuntu 10.10. One of them (a htpc) shares its local pulseaudio sinks, and I want the other (a laptop) to direct its audio to it.
So, on the htpc, I've ticked "Enable network access to local sound devices" in paprefs. On the laptop, I've ticked "Make discoverable PulseAudio network sound devices available locally".
The result is that, in padevchooser and pabrowser, the laptop sees the remote sinks. However in pavucontrol they are not visible. If I set one of the remote sinks as default in padevchooser, local applications (tried totem, vlc and spotify) cannot play audio.
Every time I reboot my computer the system time always comes up exactly 10 hours behind where it should be. So if I reboot it at 16:00 it comes up as 06:00.
This has only been happening since I got back from a trip to Australia, where I naturally changed the computer's timezone to match the local one. I'm now back in Central European Time which is 10 hours behind Australia's. This is on opensuse 11.3.
I've used the YAST date and time tool to set the timezone correctly, and /etc/localtime is set correctly:
I am using Ubuntu 9.10. Every time I try to reboot my system it hangs. Shutdowns work properly. I've done multiple re-installations. Nothing I've tried fixes the problem. Does anyone have any suggestions?
I was wondering if any one came across that issue before. Everytime I reboot my PC something (I assume GNOME) reset my system clock to an hour behind what is was the last time. So if a reboot twice in a row that'll be two hours behind and so on. It used to work fine until I had to change my system time backward temporally to overcome and issue with GPG. Since I put it back I get that phenomena. It's like it's adjusting it for the Day light saving everytime a boot. Problem is Japan does not have any day light saving. I run OpenSuse 11.2 with Gnome 2.28.2 as my interface. I'm currently located in Japan GMT+9 not DST. /etc/localtime -> /usr/share/zoneinfo/Asia/Tokyo
I suspect a bug in Gnome or Yast. It's not user specific because the time is already altered even before I log it.
Every time I reboot my computer the system time always comes up exactly 10 hours behind where it should be. So if I reboot it at 16:00 it comes up as 06:00.
This has only been happening since I got back from a trip to Australia, where I naturally changed the computer's timezone to match the local one. I'm now back in Central European Time which is 10 hours behind Australia's. This is on opensuse 11.3.
I've used the YAST date and time tool to set the timezone correctly, and /etc/localtime is set correctly:
I'm running a CentOS 5.2 vm on a W2K8 hyper-v core server. The problem I have is that when I reboot, the system time always resets itself to 6:00 am in the morning. I tried the /sbin/hwclock --systohc command but it hasn't taken hold.
I change the audio channels to 6 in alsamixer by choosing my sound card and change the channels to '6ch'. But this setting is not preserved. I see that after a reboot the channels are again going back to 2ch. I have to manually change everytime to 6ch after each reboot. Is there a way to save the setting in alsamixer so that I will get 6ch everytime after reboot? I am not sure I have explained my problem in a way so that you can understand.
Dual boot system. Boot Linux Fedora 13 and the hardware clock is set to GMT. Boot Windows 7, time is wrong, as it expects the hardware clock to be set to the local time. reset the hardware clock each time I reboot in to the other O/S.