Choqok too fast for kwallet

Hi,
Just a small problem that bothers me:
When my system (KDE) starts all programs that ran when I shut down the PC are started again. The problem is that choqok is too fast ;b
It says that there was no wallet and that everything is stored in plain text. A few second after this kwallet prompts for the password because choqok needs it. Anything I can do about it (except for turning off choqok every time I power off my machine)?
TIA

This is the prime reason I don't like benchmark programs. They talk @#$%. Memory will only run as fast as the bus it is plugged into (so long as it is capable of running at that speed or faster).

Similar Messages

Itunes can't burn this cd because the burn speed is too fast for your cd...

For the first time since upgrading to 10.3.9 I'm trying to burn a data disc from iTunes to backup some files. It fails every time and ruins the blank CD. This is getting expensive!
The CDs are Phillips CD-R 52x. (Yes, I've used blanks from this very box before the 10.3.9 upgrade and it never failed before.) iTunes was set to 24x burn then changed to "maximum possible" for the burn speed.
Most times it looks like it's burning the playlist but around the 5th file it spits it out and gives the error "itunes can't burn this cd because the burn speed is too fast for your cd burner or media". Sometims it just locks up itunes with "checking media" and I have to force quit iTunes. Then the disc is ruined. It won't even show up in Finder.
Ugh. Anyone know how to fix this?
edited p.s.
Here's what the Console log says for the last failed attempt.
Mac OS X Version 10.3.9 (Build 7W98)
2007-05-13 14:20:36 -0500
iTunes: Burn started, Sun May 13 14:21:47 2007
iTunes: Burning to CD-R media with SAO strategy in MATSHITA DVD-R UJ-816 DXJ3 via ATAPI.
iTunes: Requested CD burn speed was max, actual burn speed is 16x.
iTunes: Burn underrun protection is supported, and enabled.
iTunes: Write (10), block: 72864, count: 32 -> 3/0C/00 Medium Error, Write error
iTunes: Burn failed, Sun May 13 14:24:37 2007
iTunes: Burn sense: 3/0C/00 Medium Error, Write error
iTunes: Burn error: 0x80020060 The device drained its buffer without burn underrun protection.

I just tried setting the iTunes preferences to burn at 4x (since in theory the specs say my SuperDriver burns CDs at 8x) and got the following error.
The attempt to burn a disc failed. The device failed to respond properly, unable to recover or retry..
and looking in the console this is the error.
iTunes: Burn started, Sat May 19 21:46:14 2007
iTunes: Burning to CD-R media with SAO strategy in MATSHITA DVD-R UJ-816 DXJ3 via ATAPI.
iTunes: Requested CD burn speed was 4x, actual burn speed is 4x.
iTunes: Burn underrun protection is supported, and enabled.
iTunes: Write (10), block: -150, count: 32 -> 3/73/03 Medium Error, Power calibration area error
iTunes: Burn failed, Sat May 19 21:46:25 2007
iTunes: Burn sense: 3/73/03 Medium Error, Power calibration area error
iTunes: Burn error: 0x80020022 The device failed to respond properly, unable to recover or retry.
iTunes: Burn started, Sat May 19 21:52:27 2007
iTunes: Burning to CD-R media with SAO strategy in MATSHITA DVD-R UJ-816 DXJ3 via ATAPI.
iTunes: Requested CD burn speed was 4x, actual burn speed is 4x.
iTunes: Burn underrun protection is supported, and enabled.
iTunes: Write (10), block: -150, count: 32 -> 3/73/03 Medium Error, Power calibration area error
iTunes: Burn failed, Sat May 19 21:52:35 2007
iTunes: Burn sense: 3/73/03 Medium Error, Power calibration area error
iTunes: Burn error: 0x80020022 The device failed to respond properly, unable to recover or retry.

Am I too fast for Mail.app?

*Simplified version*: http://trials.sent.com/problem.jpg
*Detailed version:*
So here I am composing away in Mail.app. I suddenly decide that I need to select a prior portion of my typed text and replace it with another phrase.
So I select the text, and I start typing my replacement phrase without pressing delete. This used to work fine, and the portion that I wanted replaced would get replaced with the new intended phrase.
The problem? After I select a prior portion of the typed text, and press delete (or start typing with my replacement), I'm now seeing additional words (those that were present right after the deleted words) automatically selected by Mail.app.
This is bad, because if I'm typing away, I've already lost unintended words. Am I too fast for Mail.app? Should I slow down?
Is this just me? I've had this problem for over almost a year now (with my old macbook), and new macbook pro.

This exact problem has happened to me on my Late 2008 MBP a number of times.
After I select something, I delete it (cut it, type another letter, whatever) and the text is moved appropriately, but the selected area remains. So upon the next keystroke the next few words are also deleted.
It seems to be some sort of bug. I'm not sure if its related to the trackpad, or what. I haven't made much effort to isolate and fix the problem either. Perhaps we should both submit feedback to Apple about this. Your illustration depicts the problem perfectly. Would you mind if I link to it when I send in feedback?
One more thing: It's not limited to Mail.app on my machine. I get it in Pages and TextEdit as well, for sure. Perhaps it is limited to Cocoa applications; I'm not sure if I've ever got it in Word or Appleworks.
--Travis

How do I create a time delay so the signal from my throttle is not too fast for an ESC?

I am using Labview to control a ROV using a Playstation 3 controller. When I throttle too quickly the ESC cuts off and resets. I talked to the manufacturer of the ESC and they said the probable cause was the signal was changing to fast for the ESC to follow andthey recommended putting a delay in the program to allow time for the ESC to read the throttle increments. My question would be "How do I do this?" Thanks

I'm not exactly sure how to do what you are talking about. I have been doing this for about a month and have taken only an intro class in Labview at my university. Could you point me in the right direction to learn how to do it . I have attached the VI just in case you wanted a closer look at it. Thanks
Ivan
Attachments:
PS3Thruster.vi ‏210 KB

Instrument not recognized - computer too fast for AT-GPIB/TNT board

I have a problem with a potentiostat (PAR 283) connected to ISA AT-GPIB/TNT (not pnp) board. I recently upgraded to a motherboard with 1.8GHz AMD processor. Potentiostat is recognized by other software as "28PD", "28PE" or sometimes just some garbage characters, instead of "283". I'm using driver version 1.6 (1.7 could not recognize the board). In "Measurement&Automation" potentiostat doesn't respond to *IDN? query (error EAB0). FRA analyzer connected to the same board is recognized without a problem. None of the Windows programs can control potentiostat (it's not recognized as "283). One DOS program, however, is able to recognize and control the potentiostat. I tested the whole system with 166MHz compu
ter, and everything worked fine.
My operating system is Win98
Does anyone have idea what could solve the problem?
Thanks
Darko

I don't necessarily have an answer to your problem, but I want to assure you those usually these problems are with the instrument. The IEEE 488.1 standard defines a 3-wire interlocked handshake to prevent any problems due to computer/device speeds.
However, some devices violate this protocol. They rely on internal timing to determine when things should occur on the bus. For example, the talker asserts the DAV hardware line to indicate that data is valid on the bus. Following that, the listener is supposed to latch the data from the bus and then assert NDAC to indicate that it has taken the data from the bus. At the moment that NDAC has been asserted, the talker is allowed to modify the data lines since they have already been latched. However, some devices have noted in the past that their is usually X amount of time that passes from when NDAC is asserted until the data is removed from the wire. In order to improve peformance, they actually assert NDAC sometime before the data has been latched, assuming that the data will be there when they are actually ready to receive this data. In the case of moving to a faster computer, this data is actually staying on the bus for a shorter period of time than expected and the device receives garbage data.
A similar phenomenon can occur when the device is the talker where is violates the proper 3-wire handshake.
Note that not all failures are intential on the side of the device, it could be a legitimate bug.
Now that I have given a somewhat long-winded description of how problems like this can manifest, I can give you a few recommendations.
1) Obtain a GPIB bus analyzer and examine the handshake sequence to determine where the failure is.
2) Talk to the equipment manufacturer to see if they have any updates
3) Modify the bus timing in NI-488.2 from 500ns to 2ms. This is not likely to work since you are on the receiving end.
4) Try to procure a GPIB-PCII/IIA board. This is a slower board that overall responds to handshaking slower than the AT-GPIB/TNT board and may mask the problem.
5) Increase your cable length (including to "illegal" lengths such as 8m). This can add propegation delays that can mask this problem. I have seen work in teh past with troubled instruments.
Good luck.

Latency Timings too fast for my board?

A last question to you guys.
I expected with the buy of OCZ high Performance RAM Modules to run Latencies less then 3 Times, of course CAs2, RAS to CAS 2, TRAS 2.
So i startet and configured my settings to 2,5-2-2-6 at FSB 225 Mhz.
Result: Computer restartet after als false try to boot and set them back to Timings of 3!
Ok, i guess the RAM Modules aren´t the problem, so i expect that my damn Mainboard can´t handle timings faster then 3!
Is this the case or can anyone tell me, what a possible reason for this problem can be?
I can´t understand with a view on Abit, Epox and Asus, taht my MSI board can´t handle fast timings?!

if you´re running dual channel should be helpful to raise VDIMM up to max of 2,8 volts, but if you worry about warranty check ocz website if they can handle...
i have same mobo and i had to raise my VDIMM up to 2,7 volts to boot up system and to run stable...
but you could also post your full system specs if this wont help...

Studio 12 - too fast for me

o select debug executable
o click debug
o i have a stop in main - it stops
o click continue - program runs to completion
o my output starts showing in "Process I/O"
but, whew - before i can read it, the output is cleared
the i/o tab is still selected, but the panel is empty
actually this may be true for all the debug panels
any way to get my output back?

When the program exits the debugger session finishes.
When the debugger session finishes all it's windows get cleaned up.
Not a good ide for I/O ... it should linger.
Will address this in time.
Meanwhile you can stop your program before it goes away as
follows and then finish the session explicitly.
Choose Run->NewBreakpoint
Choose BreakpointType: Process
Choose Event: Last Rites
Or from the dbx command line issue
stop lastrites
This bpt will be permenent for all sessions.
LastRites is a "union" of exit/terminating-signal/killed from debugger etc.

Can't burn disc via iTunes. Burn speed too fast. AGAIN!

"iTunes can't burn this CD because the burn speed is too fast for your CD burner or media. Choose a lower speed in the burning pane of iTunes Preferences then try burning again".
I have been having on going problems burning CD’s in iTunes for YEARS, and I know I am not the only one. I get the error message above. Having checked the forum at the time, and posted for help, I am know there is no real solution except to change brand of disc.
Thing is, now I can’t get ANY brands to work. I’ve been through Verbatim, Maxell, JVC, Sony, but none work. The only brand that would work were TDK audios which I can no longer find anywhere.
I know its not the burner, as Toast works fine, and I know I am not alone. Anyone got any ideas?
Even after years Apple seem to be blanking this question. It’s very frustrating not being able to burn my purchased itunes downloads to disc.

To anyone who is interested I think I may have found a possible solution. When you put a blank disc in the drive, wait about 30-60 seconds or so for it to stop spinning before burning.
This seems to work. It's a bit sticky but eventually works. I tried both TDK & Maxwell discs and 9 out of 11 worked. Absolutely no reason why the other 2 didn't, but it's a lot better than none.

CD burner error: Burn Speed Too Fast

Whenever I try to burn a CD on my eMac an error message says
"iTunes can't burn this CD because the burn speed is too fast for your CD burner or media. Choose a lower speed in the burning pane of iTunes Preferences then try burning again".
It even says that when the burning speed is on x1. It says that on every speed. So does anyone know how I can fix this problem and make it be able to burn CDs? Is it because I have nearly 10,000 songs on my iTunes, so that is somehow making it slow down?
The blank disc I'm using is "High Quality Pure Silver CD-R 80 Tevion"
It has 700 megabytes (80 minutes) on it, and I want to burn a CD that is 60 minutes, exactly. So, help? Thanks.

Let me see if I can help you understand your delima.
Just because you buy a very expensive Media Brand, doesn't mean it is any good. There is such a wide range of quality in CD's and DVD's it is really hard to select what is considered to be the best.
A very good guide to use for Media in general for both CD, and DVD's is below.
http://www.digitalfaq.com/media/dvdmedia.htm
Next there are a couple of KEY points to remember when burning, these will help you.
Never have any other Applications open when burning.
I tend to use either CD-R or DVD-R Media, the reason is these 2 formats are the most widely used and recognized in all Players, and Computers alike.
Always choose the slowest speed to get a high quality burn.
This next suggestion is probably the most important.
Not all CD-R's and DVD-R's are the same
Read the packaging carefully
Many will explain that they will burn at all speeds from 1X upwards
This will help insure that your burner Software will choose the correct speed.
Don

ITunes CD Burn error (media too fast)??

I upgraded to the latest iTunes version and now Im getting errors when I try to burn a playlist. I havent burned a cd off this computer in a long time, so Im not sure if it's iTunes. However, the error, if I remember correctly,said iTunes is unable to burn the playlist because the requested speed is too fast for the burner or the media.
I tried slowing my burning speed to 8X, but it still gave me the error.
Any suggestions? Is it time for a new drive? If so, what are my options? I have the blue CRT (500mhz) iMac.
Thanks

Since my original post, I have been able to burn a cd, but still most of the time get the error. Why would it work sometimes, and not other times?
Im guessing the drive is going. Can it be replaced? Are there upgrades available for the CRT iMacs ?

Can you slow down a voicemail you are listening to? I can't understand what someone said to me because they spoke too fast. I just want to know how to slow down the voicemail so I can understand her if it's possible.

How can you slow down a voicemail you are listening to? Someone sent me a voicemail and they spoke way too fast for me to understand them. I want to know how to slow down the voicemail so I can understand them if that is possible.

   I have to say, this is so weird because it's actually become this way in the past week maybe, and I'm sure me saying this here will be disputed, ridiculed and belittled, and that's absolutely fair, but I've got to say it... up until a few days ago, my iTunes sync/backup area really would keep more than one backup for my one, single iPhone. They were all timed and dated with a drop-down menu (which appeared if I clicked the restore button) to choose which one I wanted to roll back to, for example. Sure, I'd read about the three backups thing etc. etc. and perhaps I got that wrong or misunderstood, but I can honestly say, I only ever had at the most two backups, that I could drop-down and choose to restore from. They were there. Same iPhone. Different dates.
   At the time, when this seemed to be the case, the backing-up process took quite a while. I would leave it to progress while I went and made a cup of tea, come back and it still wasn't finished running. So, not really AGES, but a little while.
   Now, when I perform a backup, the progress bar almost shoots across to a finish. I'll 'fess up... that worries me most of all. I can live without the luxury of a menu of backups... but if it does it once, I'd like to be sure it does it at all.
Much more importantly though, thank you for your replies so far.
Any further input, even if it's to belittle or shame is totally welcome. I'd like to understand this a bit more.
Thanks again.

A bug? Photoshop Action Playback is too fast after CS5-CS6 upgrade!! My action wont work

On a PC
I upgraded from CS5 to CS6 (cloud) over the long weekend and I'm now faced with a massive headache. The process actions I use intensively for my work are all foxed by the simple problem that the action playback is going too fast for scripting over two documents to keep up. I have tried everything I can think of but the only thing that allows the action to progress sensibly (as in previous versions of the software) is the step-by-step playback mode. This is too slow to use on an ongoing basis.
The problem is caused by the following sequence
Save as document (on desktop)
Open as document - open as Camera Raw - after settings open in Photoshop
Select All
Copy
Close - saving no
(PS automatically selects previous document)
++++ paste ++++ ERROR Paste command is not currently available
This is where Photoshop should select the previous/underlying document before applying the Paste command. Since the upgrade its been trying to paste the clipboard in the split second after closing and selecting the previous document, and reporting no document available at all. Slowing or pausing the playback with step by step or stop&continue works around the problem but causes workflow to slow down drastically.
Is there a way to script a pause during this one crucial moment? Or is there a preference setting I have overlooked that is casing the behaviour?

Save as - open as camera raw - select all- copy - close - paste. The dance is the ony way I can apply Camera Raw settings such as clarity, noise reduction etc to my retouch after the initial raw conversion. Its a well used technique that I've known about for years. Loads of people use this method in CS6, but for some reason I can'y get it to work after the upgrade.
The action is recorded in the regular record/play type action script. Its a big action and would take many hours to convert into javascript (even if I had the skills). I could possibly use the script recorder plugin but that rules out future tweaks without rewriting everything from scratch. app.refresh and $.sleep sound interesting though... is it possible to incorporate them into the basic action script?

Arrow keys work too fast on Polygon tool

My keyboard arrow keys change the amount of points/sides on the polygon tool too fast for me to control, and not one step at a time! How do I change this?

Illy is getting too highstrung. Give her a cold turkey instead of whatever she is on. If necessary, you may get her unstrung if you Ctrl+Alt+Shift/Cmd+Option+Shift while you wake her or Move the folder while she sleeps.
If that does not help, find out whether the arrow keys behave normally in other applications.

Time Capsule with ext HDD seems too slow for ethernet big file transfer

With new Snow Leopard on a Mac Mini, I have a wired Time Capsule with an external WD USB 2.0 HDD added. While moving files over 802.11N files seem to work fine, a full wired Ethernet connection seems to send the files too fast for the WD external drive to keep up. I get only the first 50Mb before the transfer gets corrupted. Isn't there a handshake that limits the file transmission to allow for the USB drive to stay ahead?
Has anyone else seen this? Is there a remedy?
Thanks
Bill H.

With new Snow Leopard on a Mac Mini, I have a wired Time Capsule with an external WD USB 2.0 HDD added. While moving files over 802.11N files seem to work fine, a full wired Ethernet connection seems to send the files too fast for the WD external drive to keep up. I get only the first 50Mb before the transfer gets corrupted. Isn't there a handshake that limits the file transmission to allow for the USB drive to stay ahead?
Has anyone else seen this? Is there a remedy?
Thanks
Bill H.

Slim "Id "x" respawning too fast: disabled for 5 minutes"

Hello Everyone,
Slim "Id "x" respawning too fast: disabled for 5 minutes"
This error drives my crazy I changed to slim after the recent change of gdm.
Since I changed, when I boot my PC this error always occurs. Only solution so far is either to wait for 5 minutes or to change to another TTY#, login and try init 3 and then init 5 (which only works sometimes but most of the time delivers the same error).
The error doesn't occur when I REboot the PC.
I start slim via inittab with "x:5:respawn:/usr/bin/slim >& /dev/null"
I already tried the German Arch-Forum but got no reply.
There is a topic http://bbs.archlinux.org/viewtopic.php?id=81159 with the "solution" to change inittab
"x:5:respawn:/usr/bin/slim >& /dev/null"
to
"x:5:once:/usr/bin/slim >& /dev/null"
but this doesn't work for me, slim then refuses completly to start.
I'd prefer to use the inittab method and not the daemon method...
Thank you in advance
cl10k
PS: Sry for bad English...
Last edited by cl10k (2009-11-24 21:54:18)

Hi,
"generally" X seems to work fine. I use Openbox without any problems. If I try /usr/bin/slim from init 3 it says: "Stale lockfile found, removing it" and then nothing happens - the console just stays on.
I haven't changed my Xorg for ages, I still use the same X configuration (besides updates) that I had years ago with kdm and then with gdm. Even when I switched from gdm to slim I just follwed to wiki and changed the Inittab line from gdm to slim.
Heres my Inittab and my Xorg.conf (to be honest I'm not really fit with Xorg configuration...)
To be sure, I just created a (very basic) new Xorg.conf with nvidia-xconfig.
# /etc/inittab
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
## Only one of the following two lines can be uncommented!
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
x:5:respawn:/usr/bin/slim >& /dev/null
# End of file
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder63) Tue Oct 20 21:01:12 PDT 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "LG F900B"
HorizSync 30.0 - 98.0
VertRefresh 50.0 - 160.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7600 GS"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT-0: 1280x1024_85 +1280+0, CRT-1: 1280x1024_85 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
EDIT: It seems to work now! Slim started without any errors. I will test that for some days to see if the problem is really gone now.
Just out of curiosity:
A lot seems to have changed in Xorg.conf since my old ~2years old config was made.
I had to turnoff boot logo manually and set Option "Composite" "Enable" but now everything seems to work by default?
Do you see any flaws in my xorg.conf? Any ideas for improvements (except metamodes)?
Last edited by cl10k (2009-11-25 10:47:02)

Choqok too fast for kwallet

Similar Messages

Maybe you are looking for