[Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
Same issue, 21,10 using Unity, and the apparmor workaround fixes it for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130682] Re: pasv_min_port, pasv_max_port does not work if client uses PASV
** Changed in: vsftpd (Ubuntu) Status: Invalid = New -- pasv_min_port,pasv_max_port does not work if client uses PASV https://bugs.launchpad.net/bugs/130682 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 130682] Re: pasv_min_port, pasv_max_port does not work if client uses PASV
Same problem on Ubuntu 10.04 server with vsftpd. I'm using a Cisco 1811 router with ports 20 and 21 statically NATed and a NAT pool for the PASV ports. This works fine in standard FTP mode, but when I switch to PASV mode in FTPES, it uses a port outside the range specified by the min/max port settings. The router is NOT doing any firewall functions or interfering with packets in any way. I am a network engineer by trade, so I am confident of this. I have observed this same behavior connecting to the server from a host inside the router on the same subnet, and of course, the connection works fine because the port is accessible from the inside, but the port requested is still outside the range specified in vsftpd.conf when in FTPS mode. I will post here if I find any more info. Setting status to NEW -- pasv_min_port,pasv_max_port does not work if client uses PASV https://bugs.launchpad.net/bugs/130682 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 563973] Re: vsftpd fails to start on boot when using pasv_addr_resolve
Not a big deal for me, since I reboot the server rarely and have added this to /etc/rc.local, but FWIW, I have encountered this strange behavior as well. Using 10.04 Server and vsftpd. Can provide more detailed info if needed. -- vsftpd fails to start on boot when using pasv_addr_resolve https://bugs.launchpad.net/bugs/563973 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 130682] Re: pasv_min_port, pasv_max_port does not work if client uses PASV
Whoops. Found a flaw in my .conf file. I had copied the pasv_min_port to a different spot while troubleshooting another issue, and had two values for min, with no value for max. Works fine now in both modes. Setting status back the way I found it. ** Changed in: vsftpd (Ubuntu) Status: New = Invalid -- pasv_min_port,pasv_max_port does not work if client uses PASV https://bugs.launchpad.net/bugs/130682 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 130682] Re: pasv_min_port, pasv_max_port does not work if client uses PASV
** Changed in: vsftpd (Ubuntu) Status: Invalid = New -- pasv_min_port,pasv_max_port does not work if client uses PASV https://bugs.launchpad.net/bugs/130682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130682] Re: pasv_min_port, pasv_max_port does not work if client uses PASV
Same problem on Ubuntu 10.04 server with vsftpd. I'm using a Cisco 1811 router with ports 20 and 21 statically NATed and a NAT pool for the PASV ports. This works fine in standard FTP mode, but when I switch to PASV mode in FTPES, it uses a port outside the range specified by the min/max port settings. The router is NOT doing any firewall functions or interfering with packets in any way. I am a network engineer by trade, so I am confident of this. I have observed this same behavior connecting to the server from a host inside the router on the same subnet, and of course, the connection works fine because the port is accessible from the inside, but the port requested is still outside the range specified in vsftpd.conf when in FTPS mode. I will post here if I find any more info. Setting status to NEW -- pasv_min_port,pasv_max_port does not work if client uses PASV https://bugs.launchpad.net/bugs/130682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563973] Re: vsftpd fails to start on boot when using pasv_addr_resolve
Not a big deal for me, since I reboot the server rarely and have added this to /etc/rc.local, but FWIW, I have encountered this strange behavior as well. Using 10.04 Server and vsftpd. Can provide more detailed info if needed. -- vsftpd fails to start on boot when using pasv_addr_resolve https://bugs.launchpad.net/bugs/563973 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130682] Re: pasv_min_port, pasv_max_port does not work if client uses PASV
Whoops. Found a flaw in my .conf file. I had copied the pasv_min_port to a different spot while troubleshooting another issue, and had two values for min, with no value for max. Works fine now in both modes. Setting status back the way I found it. ** Changed in: vsftpd (Ubuntu) Status: New = Invalid -- pasv_min_port,pasv_max_port does not work if client uses PASV https://bugs.launchpad.net/bugs/130682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: HPA ( Host Protected Area ) interferes with dmraid
NeCod, do be careful not to let the mobo re-write that HPA. From my (very bad) experience with that Gigabyte board, a reset of the CMOS, a BIOS flash, a bad stick of RAM, or just playing around with the BIOS backup tools in the wrong way can cause it to do this without warning you. (the driver CD that came with my board was bootable and would do this.) If you have an option in BIOS to disable the backup BIOS to HDD feature, (I didn't, but have seen later boards that did) definitely disable it before using HDAT2, so that you won't have to go through this twice. If that testdisk util doesn't work, look up R-studio. It's commercial software (and expensive,) but might be able to recover the data on your array if you're really hurting for it. You should still have an external storage device to which to dump the data, but this might save you a lot of reinstalls. Either way, watch for UUIDs to change when you rebuild. Check /etc/fstab and replace disk-by-uuid references to the array before trying to boot to a recovered drive. Also, HDAT2 is now included on the Ultimate Boot CD, which is an extremely useful resource in its own right, and may contain other utilities to help you recover your array once HDAT2 is run. http://www.ultimatebootcd.com/ -- HPA ( Host Protected Area ) interferes with dmraid https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 307891] Re: Can not add photos to Facebook
This same message is appearing to me in 10.04 with Firefox. My first attempt to go ahead with running the app has resulted in Firefox going to a gray busy lockup condition, and it is still in that state on that machine. More specific data was available, and I will post everything in a few minutes once I kill and restart Firefox. It looks like one problem is an invalid certificate from Thawte, though the details of the certificate seem to show that it has not yet expired. It also said that the it would have to run without certain java security features. ** Changed in: firefox-3.0 (Ubuntu) Status: Invalid = New -- Can not add photos to Facebook https://bugs.launchpad.net/bugs/307891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 307891] Re: Can not add photos to Facebook
I had to kill Firefox to unlock it. Ubuntu 10.04 x64 Firefox version 3.6.3 Mozilla Firefox for Ubuntu canonical 1.0 Plugins highlights: IcedTea NPR Web Browser Plugin (IcedTea6 1.8 (6b18-1.8-0ubuntu1)) Shockwave Flash 10.0 r45 Silverlight Plug-In 3.0.40818.0 (I had to do some research on M$ website for a class) Extensions highlights: NoScript 1.9.9.81 (confirmed not blocking any scripts on this page) Ubuntu Firefox Modifications 0.9rc2 AniWeather 0.7.4 Flagfox 4.0.5 Novell Moonlight 2.2 (goes with the Silverlight plugin) Personas 1.5.3 Some others in there that I don't think are relevant. I will provide the complete list if needed. This error appears for me on Facebook when I try to upload photos. I click on upload photos from the home screen, then on +upload photos button at the top of the center frame that loads. This brings me to an add new photos page and a chance to create a new album. After entering the info for the new album, I click on the create album button and it takes me to the page that loads the app that creates this error. The error is formatted differently than a typical non-recognized certificate error in Firefox, which is what set off alarm bells for me. It also has extra info that shows there's more to it than a typical expired or unrecognized certificate. Here is the error: Warning - Security The application's digital signature cannot be verified. Do you want to run the application? Name: Applet Publisher: Temporary Aurigma Inc. From: upload.facebook.com (checkbox) always trust content from this publisher (run button) (cancel button) The digital signature could not be verified by a trusted source. Only run if you trust the origin of the application. (more information button. Clicking on the more information button displays the following: More information This application will be run without the security restrictions normally provided by java. The digital signature has expired. Resources contain entries whose signer certificate will expire within six months. The digital signature was generated with an untrusted certificate. (certificate details button) (close button) I was most concerned about the first in that list. I clicked on the certificate details button and copied/pasted the info into the text file that is attached. You will note that neither of the two certificates has expired. I did a search for this problem on another computer before proceeding, thinking it was a facebook problem, or possibly a java problem, since I don't have the sun java plugin on the affected machine. This was the first hit I got and as you can see, it matches my problem exactly. Since Nick tried hitting run without immediate problems, I did too, and instead of the gray box just staying there, it turned the whole Firefox window gray, as in not responding gray, and stayed that way for about 5 minutes until I force quit Firefox. I will try some troubleshooting on this issue: 1. I will install the sun-java6-plugin and the official sun jre 6 on this machine to see what it does (I hadn't had any java problems before this point, however.) 2. I will try it on the machine I'm currently using, which has Ubuntu 9.10 and Firefox 3.5.9 and Sun-java6-jre installed, but uses the IcedTea plugin. (I won't upgrade this one until there's a workaround for the shutdown/logout countdown design flaw in 10.04) Will post results later. ** Attachment added: Certificate details from facebook error. http://launchpadlibrarian.net/49791467/Facebook_error_info.txt -- Can not add photos to Facebook https://bugs.launchpad.net/bugs/307891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 307891] Re: Can not add photos to Facebook
1. I tried it first on the Ubuntu 9.10 machine with sun-java6-jre installed but not with sun-java6-plugin. The same error message appeared. I will not repeat the details. When I hit run, the applet loaded, and it appears to be functioning normally. 2. I installed both sun-java6-jre and sun-java6-plugin on the first machine. (the one with 10.04) Same behavior as the 9.10 machine. Same error message, then the app appears to work fine after you hit run. So, I conjecture that the problem is that the app needs to run in the sun-java6-jre instead of in the plugin, where it should run. It is an applet for uploading pictures, and allows you to browse files on your own machine and upload them, so there's a fairly obvious possibility for a large security hole here. I'm not qualified to evaluate whether this particular app is allowing remote systems access to local info, but the error message seems to indicate that there is some sort of security problem here. The most serious error seems to be with the design of the app, and not with Ubuntu or Firefox. Also, it is still throwing an error on the certificate, which, to my untrained eye, appears valid and current. Thawte may do business with some shady characters, but facebook is a big player, so perhaps this certificate should not be rejected automatically. Leaving status at new for now, since this second issue might be valid. Reporting the issue to facebook as well. -- Can not add photos to Facebook https://bugs.launchpad.net/bugs/307891 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] apport-collect data
Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe2396 F pulseaudio /dev/snd/pcmC0D0c: joe2396 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xeb20 irq 22' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100103' Controls : 38 Simple ctrls : 21 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: alsa-base 1.0.20+dfsg-1ubuntu5 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-20.58-generic Uname: Linux 2.6.31-20-generic x86_64 UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev pulse pulse-access sambashare scanner tape vboxusers video -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] AlsaDevices.txt
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/42242381/AlsaDevices.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] AplayDevices.txt
** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/42242382/AplayDevices.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] BootDmesg.txt
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/42242443/BootDmesg.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] ArecordDevices.txt
** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/42242383/ArecordDevices.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] Card0.Amixer.values.txt
** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/42242452/Card0.Amixer.values.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] Card0.Codecs.codec.2.txt
** Attachment added: Card0.Codecs.codec.2.txt http://launchpadlibrarian.net/42242456/Card0.Codecs.codec.2.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] CurrentDmesg.txt
** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/42242463/CurrentDmesg.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] Dependencies.txt
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42242465/Dependencies.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] PciMultimedia.txt
** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/42242466/PciMultimedia.txt -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] Re: Volume control headphone switch works, but causes loud pops in speakers
Since the time I posted this issue, I have upgraded this machine to 64 bit 9.10. Under this release, with all updates installed as of today, the problem is different. Now the machine no longer detects when the headphones are plugged into the front jack, and treats them the same as the main analog output. This means that when the headphones are plugged in, the speakers are not muted, and the audio just goes to the headphones as well. Also, under sound preferences-output, I have two options for connector: analog output and analog headphones. When I switch it to analog headphones, I get no sound out of either connector, and with analog output, I get sound out of both. I have run apport-collect. I will test with the development release and upstream kernel in the next day or so. and update. -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] XsessionErrors.txt
** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/42242467/XsessionErrors.txt ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = New ** Tags added: apport-collected -- Volume control headphone switch works, but causes loud pops in speakers https://bugs.launchpad.net/bugs/318642 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 423532] Re: [i965gm] lcd backlight never stays off
*** This bug is a duplicate of bug 413168 *** https://bugs.launchpad.net/bugs/413168 This is happening on my HP HDX16 with Nvidia 9600M graphics. xset dpms force off shuts off the light for 30-60 seconds, then the backlight comes back on. This appears to be different from the earlier bug, because this function worked fine under 9.04 -- [i965gm] lcd backlight never stays off https://bugs.launchpad.net/bugs/423532 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314777] Re: Error:file is encrypted or is not a database
I've tried both methods (Mick's and Aaron's) and both result in gnome- rdp becoming unresponsive when it is restarted. I had encountered this same problem when going from 7.04 to 8.10 and solved it in a similar way, by re-importing the database in a different version (I'll edit in the reference if I can find it.) Now I get the same thing after upgrading to 9.04 (I wish they'd just pick one database version and stick with it. Is it possible that the fix is not working for me because of the earlier fix? If so, is there anything I can do to get this working? My database has more than 300 entries, so re-entering these from scratch is not really an option. -- Error:file is encrypted or is not a database https://bugs.launchpad.net/bugs/314777 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314777] Re: Error:file is encrypted or is not a database
Scratch that last post: Mick's script worked on the second try after a reboot. I was using several different backups of the original .gnome- rdp.db to try the different methods and probably used one that had been partially processed already as the seed for the script. Aaron's method still did not work for me with the correct backup, and I'm pretty sure I had it right when I tried pasting in Mick's commands (i.e. not using the script) so there may still be a typo in those. I should add that I'm using the release version of 9.04, not the alpha. Thanks for the awesome script, Mick. You saved me a *lot* of trouble. -- Error:file is encrypted or is not a database https://bugs.launchpad.net/bugs/314777 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318642] [NEW] Volume control headphone switch works, but causes loud pops in speakers
Public bug reported: I have a strange problem in 64 bit 8.10 Intrepid Ibex, which I have not been able to find reported anywhere else in spite of extensive searching. Whenever the headphones are plugged in, the main speakers automatically mute, as they should, but if any sound is played across the headphones in this mode, the speakers emit a loud pop every two to five seconds, until the sound playback is stopped or the hedphone plug is removed. During this time, the sound plays perfectly with no distortion on the headphones themselves. This seems to happen regardless of the audio source (Audacious, Ubuntu system sounds, Virtualbox with either PulseAudio or Alsa output.) The pops seem to be at a louder volume level than the headphone audio or the main audio would suggest, and it is loud enough and regular enough to make using the headphones unfeasible. When I unplug the headphones, it switches back to the speakers again automatically, and the speakers sound just fine. Intrepid seems to have detected my audio properly, with a Realtek ALC889A codec, and the card shows as HDA Intel (I have a Gigabyte GA- X48T-DQ6 motherboard, with the HDA front sound header connected.) When I open up the volume control applet from Gnome, I have the switches tab available, and a check-box there for headphones, all of which came up properly after install and required no special tricks to get working like I've seen others had to use. The speakers are connected to the main output jack on the motherboard, while the headphones are plugged/unplugged from the front headphone jack. This feature does work fine without the pop if I boot into windows, but I really prefer not to do that. I have not found any threads out there that describe a similar issue. Most people seem to have problems even getting to the point that I started at, and don't complain once they get the headphone switch to work. Please Help! The pop is too loud to ignore and makes the headphones pretty well useless! Here is some info that might prove useful: The device that shows first in Volume Control is HDA Intel (Alsa mixer) and in System - Preference - Sound, I have set all outputs to use that device, though it does the same thing when set to auto. I have both Front Mic and Line-in muted. Nothing is connected to those jacks, anyway. j...@cosmos:~$ cat /proc/asound/modules 0 snd_hda_intel j...@cosmos:~$ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: ALC883 Digital [ALC883 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 j...@cosmos:~$ head -n 1 /proc/asound/card0/codec* Codec: Realtek ALC889A ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa audio control hda intel mixer switch volume ** Description changed: I have a strange problem in 64 bit 8.10 Intrepid Ibex, which I have not been able to find reported anywhere else in spite of extensive searching. Whenever the headphones are plugged in, the main speakers automatically mute, as they should, but if any sound is played across the headphones in this mode, the speakers emit a loud pop every two to five seconds, until the sound playback is stopped or the hedphone plug is removed. + During this time, the sound plays perfectly with no distortion on the + headphones themselves. This seems to happen regardless of the audio source (Audacious, Ubuntu system sounds, Virtualbox with either PulseAudio or Alsa output.) The pops seem to be at a louder volume level than the headphone audio or the main audio would suggest, and it is loud enough and regular enough to make using the headphones unfeasible. When I unplug the headphones, it switches back to the speakers again automatically, and the speakers sound just fine. Intrepid seems to have detected my audio properly, with a Realtek ALC889A codec, and the card shows as HDA Intel (I have a Gigabyte GA- X48T-DQ6 motherboard, with the HDA front sound header connected.) When I open up the volume control applet from Gnome, I have the switches tab available, and a check-box there for headphones, all of which came up properly after install and required no special tricks to get working like I've seen others had to use. The speakers are connected to the main output jack on the motherboard, while the headphones are plugged/unplugged from the front headphone jack. This feature does work fine without the pop if I boot into windows, but I really prefer not to do that. I have not found any threads out there that describe a similar issue. Most people seem to have problems even getting to the point that I started at, and don't complain once they get the headphone switch to work. Please Help! The pop is too loud to ignore and makes the headphones pretty well useless! Here is some
[Bug 219393] Re: HPA ( Host Protected Area ) interferes with dmraid
I have found a utility that will avoid you having to use the workaround for HPA. This utility will allow you to remove the HPA from your hard drive permanently in most cases. You have to have the hard drive on a SATA port that is in AHCI mode, not in RAID mode when you run this bootdisk and utility. My RAID was one with redundancy, and my motherboard has an extra separate SATA controller to add two more ports, so what I did was move the drive with the HPA over to that extra port and put that in AHCI mode, then used the utility to remove the HPA. After that, I put the drive back, and let the RAID rebuild, without any loss of data. This would also work if you put the drive on a separate computer with an AHCI controller. I don't know what would happen if you changed your RAID controller to AHCI mode, but I suspect it would break the array permanently, so make a backup if you have to do this. Here is the utility: http://www.hdat2.com/ This solved all my problems with Linux and unmodified Live CDs, too. Now it all just works. Anyone else with a Gigabyte board that has Xpress Recovery like mine should be careful never to turn that on again, or you'll have the HPA back. I have read that there are some Dell computers out there that also have code in their boot sector to make them re-create the HPA even if you delete it. If you have one of those, you will have to do more work to make this permanent. -- HPA ( Host Protected Area ) interferes with dmraid https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: HPA ( Host Protected Area ) interferes with dmraid
I didn't have the file, either. All you have to do is create the empty (and writable) file libata-options in /etc/modprobe.d/ and then open it with your favorite text editor and add options libata ignore_hpa=0. That's the only line that needs to be in there. Once you've done that, the sudo update-initramfs -u command is also required to make this work. -- HPA ( Host Protected Area ) interferes with dmraid https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Thanks Phillip! That worked for me as well! I can now sudo mount /dev/dm-1 /media/RAID and read and write to it without breaking the array. The issue where the RAID is shown as broken after a soft reboot is resolved as well. Some of the research that I did on this issue since my last post indicates that this HPA could have been created by the Xpress recovery feature of this motherboard. This is supposed to create a system restore partition at the end of a hard disk, much like is found on some laptops, and some sources on forums indicate that these partitions are commonly hidden by the BIOS using HPA. I was trying to find a way to use the feature to change which drive it uses to apply HPA. The funny thing is that this board does not support the feature at all when the RAID controller is turned on, so I could not even load the configuration utility to see if it had such an option. Other people with similar features on their motherboards might need to use this same workaround. Thanks again, Phillip, for your excellent detective work and problem solution. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
The kernel parameter does not appear to have had the intended effect. I added this entry to menu.lst in /boot/grub and cold-booted to it: title Ubuntu 8.04, kernel 2.6.24-16-generic (RAID fix) root(hd0,4) kernel /boot/vmlinuz-2.6.24-16-generic root=UUID=ec648d6c-188d-4513-b3d5-0a534bd5e377 ro splash ata_ignore_hpa=0 initrd /boot/initrd.img-2.6.24-16-generic Just appended ata_ignore_hpa=0 to then end of the kernel line. It looks like the command was taken. From dmesg: [0.00] Kernel command line: root=UUID=ec648d6c- 188d-4513-b3d5-0a534bd5e377 ro splash ata_ignore_hpa=0 but when it got to my second disk (which is the only one it was doing hpa unlocking on before): [ 47.817330] ata3.00: HPA unlocked: 976771055 - 976773168, native 976773168 I have included a partial dmesg from this attempt. Only one of the drives seems to get the hpa on it. I also tried several other ways to add the parameter, but none have prevented the line above from appearing. Also, Sebounet, I'd like to try your method. I'm not booting to a live cd, but I'm a bit new to ubuntu, so from a hard disk install, how and where would one add the modprobe libata ignore_hpa=0 line? /etc/modprobe.d has many files in it, and I don't just want to throw it in anywhere. ** Attachment added: dmesg.txt http://launchpadlibrarian.net/14651729/dmesg.txt -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I'll have to inform Gigabyte of the problem, then. The BIOS I have is F4, which is the release version, but also the most recent version available for this board. With such a new product, I guess that's the danger. In the meantime, I'd like to see this work at least once, just so we can confirm that this is the only issue. I seem to recall that there was a procedure for specifying the position of the signature to dmraid. Is that true, and if so, how would one do it? -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Thanks, I didn't see your last message before I posted, there. I'll give that kernel parameter a try this evening. I still think Gigabyte needs to act on this, especially if they've got an old version of the RAID BIOS. I think I will send them to this thread directly. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I tried breaking the array, reformatting both drives with mkfs (ext2) and then rebuilding the array. This time dmraid would only see one drive of the mirror, and not the other one. I'm including my info dump in a text file. Perhaps this version of the Intel driver only needs to mark one drive? Seems like it wouldn't work if one drive failed in that case. Other possibility is that it's putting the mark in a different spot on the second drive, but that also seems unlikely. It really looks to me like there is a bug preventing dmraid from finding the correct marker on the second drive. I should mention that I booted ubuntu immediately after the array build in this case, but after I did all of the stuff you seen in the text dump, I cold booted to windows and the array came up as healthy and happy. I then initialized it for windows and formatted it ntfs, then rebooted and tried ubuntu again, but there was no change, except that the ext2 filesystem that had been visible on each individual drive is now inaccessible, and only one 500 gig device shows, instead of both, but it is also unmountable. Also, watchwolf, I am using the rc14 version of dmraid, so it looks like that is not the fix for my problem: [EMAIL PROTECTED]:~$ dmraid -V dmraid version: 1.0.0.rc14 (2006.11.08) dmraid library version: 1.0.0.rc14 (2006.11.08) device-mapper version: unknown ** Attachment added: DMRAID.txt http://launchpadlibrarian.net/14626442/DMRAID.txt -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I have a gentoo live CD lying around somewhere, so I'll give that a try tonight. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I will try this procedure this evening and post the results. Do you want me to run this procedure on sda as well? In my current configuration, sda is not a RAID member, and it serves as my boot disk. sdb and sdc are the members of the RAID. One correction, dmraid does not work correctly after a cold boot. Unfortunately, I've never been able to get dmraid to work on this machine. The cold boot has to do with getting the bios and the windows drivers to work correctly. If I boot Ubuntu, whether I try to use dmraid or not, then restart from Ubuntu (warm boot,) the bios shows both disks of the array as offline members and windows does not see them properly either. It is only when I cold boot and go directly to windows that the RAID works. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Phillip, I have attached the results of your suggested procedure. I took the chance to look at them, and found that while the sig data does exist on both drives, it is also located in very different spots on each. This seems very strange to me, but also suggests an easy workaround and fix. For now, I'm going to try moving both signatures to the same place. Hopefully, there is a way to make dmraid search for this data on both drives so that future users don't have to deal with this. I hope that the position is not supposed to be determined by the disk serial or something equally cryptic. I will post the results. ** Attachment added: Files generated http://launchpadlibrarian.net/14631998/RAID_info.tar.bz2 -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I moved the signature data on sdb to the same offset as that on sdc (and zeroed out its old position.) (I moved the data from sdb to sdb, even though it looked like the sigs on the two drives were identical.) This resulted in the BIOS seeing the RAID as degraded, with one member disk, and one non-member, but healthy disk. I booted without letting the BIOS make any changes, and dmraid also did not like the new set. I have attached that info in a text file. I did not boot windows at any time during all of this, and all boots were cold ones. From the results of dmraid -n it looks like there is some data for the RAID stored in other parts of the disk. I don't know enough to mess with it further, so I'll put it back the way it was and wait to hear back. p.s. thanks for all your help, Phillip. ** Attachment added: DMRAID-3.txt http://launchpadlibrarian.net/14632757/DMRAID-3.txt -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
Masa, what you are seeing seems to agree with my most recent test. I once again deleted the array in BIOS and re-created it, only this time, I named it NewRAID1 When I ran dmraid -n it showed the first disk as being a part of NewRAID1 and the second as being a part of RAID1, which was the name of the old array. When I get home, I will try breaking the array, completely reformatting both, and then rebuilding it to see what happens. Sorry for the slow response, I have been on the road for the last couple of weeks. Intel's bug report process is a joke, for those of you who are interested. As far as I can tell, there is no way to report a driver or BIOS bug aside from going through the motherboard manufacturer. Glad I didn't get an Intel-made board. My guess is that this is really a bug in the driver/BIOS, as others have suggested. I will take it up with Gigabyte when time permits and post the results here (if any.) -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I tried that the first time I saw this happen, because the offline member message when I rebooted made me think the raid had been broken by dmraid. On a later attempt, (when I actually had some data on that array to test) I tried a cold boot, and both Windows and the bios recognized the array as being healthy, with all data intact. (This array is on a new build, and it had always been built from scratch using this same board/bios) I'm willing to rebuild again to help figure this out, but only if there's a different method to try, as right now it would involve moving around a lot of data. For some reason, what dmraid sees as broken, Intel's windows driver thinks is just fine, with both disks participating in the mirror and healthy. This is what makes me think that either Intel has changed the way it marks these RAIDs, or perhaps the chipset driver is slightly off, so that it reads these incorrectly. I *have* rebuilt this array more than once, so it *could* be reading one of those sets of info from an earlier attempt, but it threw up the same error after the very first build, and these were brand new drives at that point. There was another bug with the ethernet controller on this board that caused Windows to turn the controller off on shutdown, and the ubuntu driver did not know how to turn it back on, so you needed to enable wake on lan in Windows or do a cold boot to turn ethernet back on. The first part of this bug seems almost like that in reverse, with the disks being offline after a warm boot from ubuntu. -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219393] Re: ich9R raid array not detected
I have the same problem, won't recognize he RAID 1 array on my ICH9R, (Intel X48, Gigabyte X48T-DQ6) warm reboot gives member offline for both member disks, but a cold reboot restores them to normal operational status. Using 8.04 Live CD. This RAID works fine under Windows. A similar problem is discussed in this thread: http://osdir.com/ml/linux.ataraid/2007-09/msg00019.html Here's my info, let me know if anything else would be useful: [EMAIL PROTECTED]:~$ sudo dmraid -ay ERROR: isw device for volume RAID broken on /dev/sdc in RAID set isw_bfhebdcdbd_RAID ERROR: isw: wrong # of devices in RAID set isw_bfhebdcdbd_RAID [1/2] on /dev/sdc ERROR: isw device for volume RAID broken on /dev/sdb in RAID set isw_cajggdbbad_RAID ERROR: isw: wrong # of devices in RAID set isw_cajggdbbad_RAID [1/2] on /dev/sdb ERROR: no mapping possible for RAID set isw_bfhebdcdbd_RAID ERROR: no mapping possible for RAID set isw_cajggdbbad_RAID [EMAIL PROTECTED]:~$ sudo dmraid -b /dev/sdc:976773168 total, 9QM0KAPS /dev/sdb:976773168 total, 9QM0K9QQ /dev/sda:488397168 total, 9SF03FRH # sda is my boot disk, and is not a member of the RAID [EMAIL PROTECTED]:~$ sudo dmraid -n /dev/sdc (isw): 0x000 sig: Intel Raid ISM Cfg Sig. 1.1.00 0x020 check_sum: 1693590363 0x024 mpb_size: 480 0x028 family_num: 1574132313 0x02c generation_num: 4466 0x030 reserved[0]: 4080 0x034 reserved[1]: 2147483648 0x038 num_disks: 2 0x039 num_raid_devs: 1 0x03a fill[0]: 2 0x03b fill[1]: 0 0x040 filler[1]: 1574132313 0x0d8 disk[0].serial: 9QM0K9QQ 0x0e8 disk[0].totalBlocks: 976771055 0x0ec disk[0].scsiId: 0x2 0x0f0 disk[0].status: 0x53a 0x108 disk[1].serial: 9QM0KAPS 0x118 disk[1].totalBlocks: 976773168 0x11c disk[1].scsiId: 0x3 0x120 disk[1].status: 0x53a 0x138 isw_dev[0].volume: RAID 0x14c isw_dev[0].SizeHigh: 0 0x148 isw_dev[0].SizeLow: 976764928 0x150 isw_dev[0].status: 0xc 0x154 isw_dev[0].reserved_blocks: 0 0x158 isw_dev[0].filler[0]: 1900544 0x190 isw_dev[0].vol.migr_state: 0 0x191 isw_dev[0].vol.migr_type: 0 0x192 isw_dev[0].vol.dirty: 0 0x193 isw_dev[0].vol.fill[0]: 255 0x1a8 isw_dev[0].vol.map.pba_of_lba0: 0 0x1ac isw_dev[0].vol.map.blocks_per_member: 976765192 0x1b0 isw_dev[0].vol.map.num_data_stripes: 3815488 0x1b4 isw_dev[0].vol.map.blocks_per_strip: 128 0x1b6 isw_dev[0].vol.map.map_state: 0 0x1b7 isw_dev[0].vol.map.raid_level: 1 0x1b8 isw_dev[0].vol.map.num_members: 2 0x1b9 isw_dev[0].vol.map.reserved[0]: 2 0x1ba isw_dev[0].vol.map.reserved[1]: 255 0x1bb isw_dev[0].vol.map.reserved[2]: 1 0x1d8 isw_dev[0].vol.map.disk_ord_tbl[0]: 0x0 0x1dc isw_dev[0].vol.map.disk_ord_tbl[1]: 0x1 /dev/sdb (isw): 0x000 sig: Intel Raid ISM Cfg Sig. 1.1.00 0x020 check_sum: 2738587652 0x024 mpb_size: 480 0x028 family_num: 2096631103 0x02c generation_num: 6 0x030 reserved[0]: 4080 0x034 reserved[1]: 2147483648 0x038 num_disks: 2 0x039 num_raid_devs: 1 0x03a fill[0]: 2 0x03b fill[1]: 0 0x040 filler[1]: 2096631103 0x0d8 disk[0].serial: 9QM0K9QQ 0x0e8 disk[0].totalBlocks: 976773168 0x0ec disk[0].scsiId: 0x2 0x0f0 disk[0].status: 0x13a 0x108 disk[1].serial: 9QM0KAPS 0x118 disk[1].totalBlocks: 976773168 0x11c disk[1].scsiId: 0x3 0x120 disk[1].status: 0x13a 0x138 isw_dev[0].volume: RAID 0x14c isw_dev[0].SizeHigh: 0 0x148 isw_dev[0].SizeLow: 976766976 0x150 isw_dev[0].status: 0xc 0x154 isw_dev[0].reserved_blocks: 0 0x158 isw_dev[0].filler[0]: 1900544 0x190 isw_dev[0].vol.migr_state: 0 0x191 isw_dev[0].vol.migr_type: 0 0x192 isw_dev[0].vol.dirty: 0 0x193 isw_dev[0].vol.fill[0]: 255 0x1a8 isw_dev[0].vol.map.pba_of_lba0: 0 0x1ac isw_dev[0].vol.map.blocks_per_member: 976767240 0x1b0 isw_dev[0].vol.map.num_data_stripes: 3815496 0x1b4 isw_dev[0].vol.map.blocks_per_strip: 128 0x1b6 isw_dev[0].vol.map.map_state: 0 0x1b7 isw_dev[0].vol.map.raid_level: 1 0x1b8 isw_dev[0].vol.map.num_members: 2 0x1b9 isw_dev[0].vol.map.reserved[0]: 2 0x1ba isw_dev[0].vol.map.reserved[1]: 255 0x1bb isw_dev[0].vol.map.reserved[2]: 1 0x1d8 isw_dev[0].vol.map.disk_ord_tbl[0]: 0x0 0x1dc isw_dev[0].vol.map.disk_ord_tbl[1]: 0x1 [EMAIL PROTECTED]:~$ -- ich9R raid array not detected https://bugs.launchpad.net/bugs/219393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
