^ The WD USB enclosures were the only ones that failed that quickly (I have seen it happen to three different people), they had the most delicate USB ports I have ever seen.
They may be better now, I have not used a WD enclosure in years so I can't comment on the current quality.
I don't recommend them based on their poor reliability in the past for me and others.
Their drives are not bad (though they run hot in my experience) but I have found their enclosures to be fragile.
The "failed after 10 plugs/unplugs" actually happened to me after six months with a WD enclosure (I think a My Book).
I was a backup drive that was only moved if it had to be and was treated delicately.
I cracked the enclosure open (literally since it needed a special tool) and put the drive in a new enclosure and it still works six years later.
Other brands lasted longer but they did break eventually, I still use one of them because it is my only PATA enclosure and the Firewire ports work.
I always buy enclosures with more than one type of data port (USB/Firewire, USB/eSATA, etc.) now anyway so there is a backup if one fails.
^ Make sure you remove the cables from the ports if you take it anywhere, a friend of mine broke his by not doing that.
That time I could not blame the enclosure itself though since having the usb cable plugged in with the drive in your backpack is a great way to put too much stress on the usb port.
^^ After less than 2 years, though under 1 year is not uncommon in my experience.
These drives were not moved or unplugged more than 10 times so I think the problem is really just the poor quality of the usb ports or the way they are mounted in the enclosure that causes them to fail in normal use.
In my experience Western Digital enclosures are the most likely to have usb port problems.
In my house we have had three fail that way (only one mine) and several of my friends have had it happen as well over the years.
The cable (one of those cheap looking thin ones) itself failed (the head broke free of the cable and insulator) for one of my friends first and the port failed a couple of months later.
None of these drives had any problems once they were put in a new external enclosure.
I would recommend eSATA connections over USB for external drives, though you probably need a eSATA PCI card for that.
It is much faster than USB 2.0 and probably slower or the same speed as USB 3.0 depending on how your motherboard was designed.
I don't have any USB 3.0 devices so I have not done any real speed comparisons though.
The cables and ports are more durable as well so you are less likely to have an external enclosure fail for that reason.
That is why I don't use USB external drives anymore, the USB ports wear out to quickly.
You can get eSATA to SATA cables if your case is full but you have free SATA ports on your motherboard as well.
Most single drive eSATA enclosures have a USB port as well if you need to take the drive somewhere.
This is the enclosure I use myself for single drives.
It is not too expensive and has a built in fan to keep the drive cool.
A quick look at that mplayer2 post shows it uses cmake. Is that the same as regular make which our vaapi-mplayer uses?
No, cmake is an alternative to autotools for automated build configuration.
It can produce makefiles for multiple compilers (Linux, Windows, Mac ones for sure, possibly more) which is why it sees use on a lot of cross-platform programs like mplayer.
Some projects use it just because their developers prefer it though.
^ It is not that bad once you have done it a few times to learn how a few things work and what error messages are telling you.
I found where it was by using a "package contents" search for "XShm.h" here.
^ What I mean is you can color the background of the conky window with a semi-transparent color to make the window look like it is not a rectangle even though it is using a lua script.
I have done circle and donut shaped backgrounds that way before.
Making a four sided shape with corners that don't meet at 90 degree angles is not difficult.
From your image I thought you just wanted to draw everything at an angle not shrink it gradually as you get closer to one side of the screen.
I think you can do either of those with cairo transformations but I am not very familiar with that part of cairo.
Maybe one of the other people here who have more experience with that part of cairo can give you some advice on it.
Sorry about the long delays in posting but I am not around a lot at the moment, rather busy with other things.
Here is my autostart menu, I have done nothing to this at all.
## GNOME PolicyKit and Keyring (\ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 && \ /usr/bin/gnome-keyring-daemon --start --components=ssh && \ /usr/bin/gnome-keyring-daemon --start --components=secrets && \ /usr/bin/gnome-keyring-daemon --start --components=pkcs11 && \ /usr/bin/gnome-keyring-daemon --start --components=gpg \ ) &
This is wrong you can't call each component argument separately like that.
I think this was a error in a old version of #! when things were being tried to get rid of the "gnome-keyring" warning.
The correct command would be like this.
## GNOME PolicyKit and Keyring (\ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 && \ /usr/bin/gnome-keyring-daemon --start --components=ssh,secrets,pkcs11,gpg \ ) &
I don't know if you need the
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 && \
line or not in Openbox but I don't need it with Fluxbox.
All of this belongs in your .conkyrc not your Lua script, they are separate files.
background yes update_interval 1 cpu_avg_samples 2 net_avg_samples 2 temperature_unit celsius double_buffer yes no_buffers yes text_buffer_size 2048 gap_x 100 gap_y 100 minimum_size 260 700 -- maximum_width 190 own_window yes own_window_type override own_window_transparent yes own_window_hints undecorate,sticky,skip_taskbar,skip_pager,below border_inner_margin 0 border_outer_margin 0 alignment top left draw_shades no draw_outline no draw_borders no draw_graph_borders no override_utf8_locale yes use_xft yes xftfont Comic Sans MS:size=8 xftalpha 0.5 uppercase no default_color FFFFFF color1 888888 color2 AAAAAA color3 DDDDDD color4 CC3333 color5 F09000
You load the lua script with "lua_load" in your .conkyrc and run it with "lua_draw_hook_pre" or "lua_draw_hook_post" most of the time.
There are other commands to run a script with but they are for more specialized scripts than the one you are working on.
You can find the documentation on those settings here.
Thanks for the quick reply.
I have just opened openbox autostart and that line is already inserted, still not to worry as it causes no problems I'll just ignore it in future.
Post your whole "~/.config/openbox/autostart" file to see if there is anything that could cause it not to work in there.
Next question if I can tag it on Iget this
Conky: llua_load: /home/gordon/lua/GordonsScripts/hello:5: '=' expected near 'yes'
I have nothing in the script that has a yes near it what is that about please ?
I would need to see your script as it is now to help you with that.
I get the following
WARNING: gnome-keyring:: couldn't connect to: /home/gordon/.cache/keyring-f9X7tR/pkcs11: No such file or directory
Where do I find the keyring mentioned or do I just go to the .cashe and make it ?
This is only a warning message and won't cause any problems if you ignore it.
You have to run
/usr/bin/gnome-keyring-daemon --start --components=pkcs11
with your window managers "run command at login" function to get rid of that warning.
There are more options that may need to be added to the "--components=" section (as a comma separated list) if you use programs that need them but conky wants the "pkcs11" option.
I wanted to make sure this didn't get missed just because it was in mrpeachy's "HOW TO : using lua scripts in conky"Gordon wrote:
I am trying to follow your howto and have come across a problem that I have no idea how to fix it or what it is. this is what I get when I run conky in terminal
which is what I think you say is the minimum that you need. What have I got wrong please ?
Conky: missing text block in configuration; exiting
would be caused by not having a
after the settings at the top of your .conkyrc.
You have to have one even if it is empty when using Lua scripts.
The "Imlib2" error cannot be diagnosed with a broken .conkyrc and could be caused by it.
So Sector11 suggested a bash script that might point me in the right direction it used pgrep. This seemed perfect as it would present the pid of any conky I wanted, but in conky this doesn't seem to work right. In conky this command gives me the pid and another number that is counting up.
The command is:
pgrep -f ./conky/test2.conkyrc
I have used both exec and execp in conky trying to get just the pid only to no success, oh and the number that counts up doesn't go away like the pid does if the conky isn't running. That makes my if nil switch nonfunctional in lua
That pgrep command should be like this.
pgrep -f -x ".*/conky/test2.conkyrc"
In network manager the way you do it is to set the metric value for each connection.
To get to that setting go to the IPv4 Settings tab when editing the connection settings and click the "Routes" button.
This will open a new window where you can set routes for that connection.
If you need to add a entry here use the same values for "Address", "Netmask", and "Gateway" as are shown on the first edit Window.
Set a lower metric value here for the connection you want to give priority over the other.
If your local network has no connection to the Internet check the "Use this connection only for resources on its network" box in its routes Window.
If you use IPv6 you may need to repeat these steps on the IPv6 tab.
If both your networks connect to the Internet I don't know how well this will work since I have never had a setup like that.
I recently started building my own kernels with the Liquorix kernel as a base.
The main reason I do it is I need some non-standard build options to be able to set some of my wireless cards firmware options to get it to work correctly.
CONFIG_MAC80211_DEBUGFS=y CONFIG_ATH9K_DEBUGFS=y CONFIG_ATH_DEBUG=y
That lets me turn of "ANI (Adaptive Noise Immunity)" with
echo 1 > /sys/kernel/debug/ieee80211/phy0/ath9k/disable_ani
which stops my network speed from dropping to zero every 30 seconds.
I set some compile options to optimize for my processor (Intel specific settings with "-march=native") and turned off the GPU (Non Intel and Nvidia) and CPU modules (Non Intel) I will never use.
This helps some with load (~0.2 lower) on my old Core2 media server, much less so on my i7.
I also set
because I don't need 63 possible ttys.
I might go through and turn off all the other wireless card stuff I don't need some other time.
I don't turn anything else off since I don't want to have to recompile if I need to plug some random piece of hardware in.
toolbar: flat solid toolbar.color: #171717 toolbar.button: flat solid toolbar.button.color: #CC9900 toolbar.button.picColor: #171717 toolbar.label: flat solid toolbar.label.color: #171717 toolbar.label.textColor: #8B0000 toolbar.windowLabel: flat solid toolbar.windowLabel.color: #171717 toolbar.windowLabel.textColor: #8B0000 toolbar.clock: flat solid toolbar.clock.justify: Center toolbar.clock.color: #171717 toolbar.clock.textColor: #EE7600 toolbar.iconbar.focused: flat solid toolbar.iconbar.focused.color: #171717 toolbar.iconbar.focused.textColor: #EE7600 toolbar.iconbar.unfocused: flat solid toolbar.iconbar.unfocused.color: #171717 toolbar.iconbar.unfocused.textColor: #8B0000 toolbar.justify: right toolbar.font: liberationsans-9 menu.title: flat solid menu.title.color: #171717 menu.title.textColor: #8B0000 menu.title.font: liberationsans-10 menu.title.justify: center menu.frame: flat solid menu.frame.color: #171717 menu.frame.textColor: #EE7600 menu.frame.disableColor: #8B0000 menu.frame.font: liberationsans-10 menu.frame.justify: center menu.bullet.position: right menu.bullet: triangle menu.hilite: flat solid menu.hilite.color: #EE7600 menu.hilite.textColor: #171717 window.title.focus: flat solid window.title.focus.color: #CC9900 window.title.unfocus: flat solid window.title.unfocus.color: #8B0000 window.label.focus: flat solid window.label.focus.color: #171717 window.label.focus.textColor: #EE7600 window.label.unfocus: flat solid window.label.unfocus.color: #171717 window.label.unfocus.textColor: #8B0000 window.button.focus: flat solid window.button.focus.color: #CC9900 window.button.focus.picColor: #171717 window.button.unfocus: flat solid window.button.unfocus.color: #8B0000 window.button.unfocus.picColor: #171717 window.handle.focus: flat solid window.handle.focus.color: #CC9900 window.handle.unfocus: flat solid window.handle.unfocus.color: #8B0000 window.grip.focus: flat solid window.grip.focus.color: #8B0000 window.grip.unfocus: flat solid window.grip.unfocus.color: #CC9900 window.frame.focusColor: #CC9900 window.frame.unfocusColor: #8B0000 window.font: liberationsans-7.5 window.justify: right *button.pressed: flat solid *button.pressed.color: #8B0000 borderColor: #CC9900 bevelWidth: 1 borderWidth: 1 handleWidth: 1 *textColor: #EE7600 *Font: liberationsans-9 background: flat background.color: #171717
If I remember correctly it only affects a little one pixel strip between the resizing handles at the bottom of the window with my theme.
If I am wrong about that it may not be working but I never noticed it.
You can put it in the menu like this.
/bin/bash -c 'cd "/home/surfino/.wine/drive_c/Program Files/GOG.com/Fallout" && env WINEPREFIX="/home/surfino/.wine" wine "/home/surfino/.wine/drive_c/Program Files/GOG.com/Fallout/falloutw.exe"'
That will run the command with bash which I believe should work.