search for: trippy

OS: Linux (Linux ares 2.6.22-3-686 #1 SMP) Dist: Debian (testing) UPS: Tripp Lite Omni1000 LCD After updating from 2.2.0 to 2.2.1, the following command seems to go into loop and becomes unresponsive except for a "kill -9": /lib/nut/usbhid-ups -u root -DDD -a trippy It seem that the previous version would pause the output at some polling interval, but with the new version prints to the screen at a very high rate. I thought i remember someone else having this same issue, but I was unable to find a relevant posting. -- John

...'d check. OH so wait... What you're saying then is that the buffers always have to be filled with 32-bit-SIZED-FIELDS, inside of which exists a low-aligned integer sample value? So the VALUES aren't 32-bit integer, but the SPACE FOR THE SAMPLE VALUE is 32-bit. Wow, that's very trippy. Honestly, I *never* would have guessed that from the documentation. That would explain the silence, too. Ev Technical Knowledge Officer Head Programmer/Designer Audiofile Engineering http://www.audiofile-engineering.com/ -------------- next part -------------- An HTML attachment was scrub...

Hello I am having a very trippy time trying to get the [homes] share to work on my samba 3.0.3pre2-SuSE (SuSE 9.0) server working. Users home folders have been copied from an old sbs server to /data1/fileroot/PersonalFiles. Here is the [homes] section of my smb.conf: [homes] path = /data1/fileroot/PersonalFiles/%S vali...

https://bugs.freedesktop.org/show_bug.cgi?id=65310 --- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> --- Please provide repro steps. I'm inclined to believe this is a problem in the environment, and not a core gcc bug. But those are some trippy optimization flags, so who knows. Be sure to specify the platform you're building for (given the sse2 flag, x86 or x86_64... but which one... I guess x86 since x86_64 implies sse2). If you can reproduce this by just running a single gcc command (like the one you pasted, but figure out the actu...

...Previously it didn't, although (as noted above) that > same command when specifying the device did (i.e., "aplay > /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently > installing and/or running audacity fixed something, but not everything. > > Another trippy discovery: I used rpm to verify all the files installed > with all the alsa* packages and there were absolutely no changes to any of > them... they're all exactly as they were when first installed. Since sound > worked exquisitely when I first installed 7.2 on this box and no alsa fi...

I wrote a while back about the inability to kill the following command with anything but "kill -9" and the apparent high speed polling rate. # /lib/nut/usbhid-ups -u root -DDD -a trippy The setup I have worked on a previous version of nut, but I have forgotten at what point it stopped working. (I believe it was around Nov, 2007 that I noticed things were not working correctly.) I track Debian testing and am currently using 2.6.24 kernel and nut_2.2.1-2_i386. Trying to start...

On 03/29/2017 06:43 AM, ken wrote: > On 03/28/2017 08:53 PM, ken wrote: >> The www has failed me with this, so I'm trying you guys. Sound worked >> great out of the box when I installed 7.2... Yay! I could watch all >> kinds of videos, like on facebook and youtube. And I could listen to >> most podcasts too. But then something happened. It was either a >>

...> it didn't, although (as noted above) that same command when > specifying the device did (i.e., "aplay > /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently > installing and/or running audacity fixed something, but not > everything. > > Another trippy discovery: I used rpm to verify all the files > installed with all the alsa* packages and there were absolutely no > changes to any of them... they're all exactly as they were when > first installed. Since sound worked exquisitely when I first > installed 7.2 on this box and no al...

Does the following error message have a specific meaning: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -75 I get two of these messages every time I run the following: /lib/nut/usbhid-ups -u root -DDD -a trippy The following is the output from the above command: debug level is '3' Checking device (0000/0000) (004/001) - VendorID: 0000 - ProductID: 0000 - Manufacturer: Linux 2.6.22-3-686 ehci_hcd - Product: EHCI Host Controller - Serial Number: 0000:00:03.3 - Bus: 004 Trying to match device Dev...

...; and that worked. Previously it didn't, although (as noted above) that same command when specifying the device did (i.e., "aplay /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently installing and/or running audacity fixed something, but not everything. Another trippy discovery: I used rpm to verify all the files installed with all the alsa* packages and there were absolutely no changes to any of them... they're all exactly as they were when first installed. Since sound worked exquisitely when I first installed 7.2 on this box and no alsa files have be...

Hello, I have a problem with the timing of effects. I do have a tag (with id: post1). When the link is clicked, the block "post1" must BlindUp. Then the block is updated with the new content and then the effect BlindDown is executed. Below is the source code of the link_to_remote I am using. <%= link_to_remote("Ajax Edit", :update =>