LG 1780U (Flatron Slim)

I bought the mini-dvi to dvi adapter to use on my iMac (20" Intel) with my LG 1780U as a second monitor. For some reason the 1780U is recognized by the mac but it immediately goes into "digital power saving mode" and displays no image regardless of what I do (changing resolution/refresh rate, using different DVI cables, power-cycle machine/monitor).
Strange side note: my Mac Mini G4 does not work (using DVI) on this monitor either. If I switch the mini to use the DVI-VGA adapter then it works fine with VGA input to the monitor.
I tried using my old LG 1720P with the iMac and it works just fine with DVI. Even my cheap Westinghouse LCM-17w7 works perfectly with DVI.
Is there something I need to do to the 1780U to make it happy with the iMac or am I just out of luck?
iMac (intel) 20" OS X & WinXP (via Parallels) & Fedora Core 4 (via Parallels) Mac OS X (10.4.6)

navers wrote:
Sorry! It is an HP Pavilion 15 Notebook PC. I can give you the product number if you want? Running on Windows 8.1 64-bit
Thank you for the additional information.
Yes, the product number would be helpful. Please don't provide the Serial #, however.
I believe your problem may be that the monitor is not compatible with Win 8.1. The only updates that are available are for Win XP and Vista. You can find this information in the link that I provided under the section titled "Software Update".
I suggest contacting LG Customer Service to see if they can help you.
Please click the "Thumbs up + button" if I have helped you and click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

Similar Messages

Monitor Flashes on Startup

Hi,
I've got a Dual 2.7Ghz G5 with a Radeon 9650 video card in it. Recently it's been doing something odd on startup. When the computer first starts (or if the monitor's been off for a while) the screen flashes between dark and normal. It does this faster and faster, and then stops and the screen becomes perfectly normal. I'm hoping this isn't the sign of impending doom for wither the monitor or the video card. Any ideas as to what may be causing it?
I have a 19" LG LCD Flatron Slim monitor.

Am back from the store and have substituted the VGA cable and adaptor to simply a DVI cable. There's good news and there's bad news.
Good news: the display is much clearer.
Bad news: same flashing problem occurs at startup.
This time, like every time I've had to attach new components and ever since the first time I got this mini, getting it to power up from the start button can be hit and miss. This time, it took about two minutes of fiddling with the power cord at all three points - from back of mini to where it three-pronged plug goes into the power bar - before it finally lit up.
There's nothing wrong with the power bar as far as I can tell; nothing else connected to it is going kablooey.

SLiM only starts twice then exits to tty1

Hi... i've installed arch yesterday following this guide https://wiki.archlinux.org/index.php/Beginners'_Guide i
After that i started to set up a new desktop using openbox and slim.
Basically everything works fine... except that after exiting openbox 2 times slim won't start and i end at tty1.
systemctl status slim... after boot
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: active (running) since Di 2013-03-19 19:05:10 CET; 1min 10s ago
Main PID: 241 (slim)
CGroup: name=systemd:/system/slim.service
└─264 /usr/bin/X -nolisten tcp vt07 -auth /var/run/slim.auth
‣ 241 /usr/bin/slim -nodaemon
... after 1st "openbox logout"
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: active (running) since Di 2013-03-19 19:05:10 CET; 1min 50s ago
Main PID: 241 (slim)
CGroup: name=systemd:/system/slim.service
...after 2nt logout on tty1
slim.service - SLiM Simple Login Manager
Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
Active: failed (Result: exit-code) since Di 2013-03-19 19:07:04 CET; 23s ago
Process: 241 ExecStart=/usr/bin/slim -nodaemon (code=exited, status=1/FAILURE)
/var/log/slim.log
slim: waiting for X server to begin accepting connections.
slim: waiting for X server to shut down
slim: waiting for X server to begin accepting connections.
systemctl list-units
UNIT LOAD ACTIVE SUB DESCRIPTION
proc-sys...t_misc.automount loaded active running Arbitrary Executable File Formats File System Automount Point
sys-devi...-sda-sda1.device loaded active plugged IC25N080ATMR04-0
sys-devi...-sda-sda2.device loaded active plugged IC25N080ATMR04-0
sys-devi...-sda-sda3.device loaded active plugged IC25N080ATMR04-0
sys-devi...-sda-sda4.device loaded active plugged IC25N080ATMR04-0
sys-devi...block-sda.device loaded active plugged IC25N080ATMR04-0
sys-devi...block-sr0.device loaded active plugged _NEC_DVD+_-RW_ND-6500A
sys-devi...und-card0.device loaded active plugged /sys/devices/pci0000:00/0000:00:02.7/sound/card0
sys-devi...et-enp0s4.device loaded active plugged /sys/devices/pci0000:00/0000:00:04.0/net/enp0s4
sys-devi...et-wlp2s0.device loaded active plugged /sys/devices/pci0000:00/0000:00:09.0/0000:02:00.0/net/wlp2s0
sys-devi...tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
sys-devi...tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
sys-module-configfs.device loaded active plugged /sys/module/configfs
sys-subs...es-enp0s4.device loaded active plugged /sys/subsystem/net/devices/enp0s4
sys-subs...es-wlp2s0.device loaded active plugged /sys/subsystem/net/devices/wlp2s0
-.mount loaded active mounted /
boot.mount loaded active mounted /boot
dev-hugepages.mount loaded active mounted Huge Pages File System
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
home.mount loaded active mounted /home
proc-sys...infmt_misc.mount loaded active mounted Arbitrary Executable File Formats File System
sys-kernel-config.mount loaded active mounted Configuration File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted Temporary Directory
systemd-...ord-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
systemd-...ssword-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded active running Getty on tty1
net-auto-wireless.service loaded active running Provides automatic netcfg wireless connection
ntpd.service loaded active running Network Time Service
slim.service loaded failed failed SLiM Simple Login Manager
systemd-binfmt.service loaded active exited Set Up Additional Binary Formats
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-...es-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-...-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-...sessions.service loaded active exited Permit User Sessions
systemd-...le-setup.service loaded active exited Setup Virtual Console
dbus.socket loaded active running D-Bus System Message Bus Socket
dmeventd.socket loaded active listening Device-mapper event daemon FIFOs
lvmetad.socket loaded active listening LVM2 metadata daemon socket
systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
systemd-journald.socket loaded active running Journal Socket
systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
systemd-...d-control.socket loaded active listening udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
dev-sda2.swap loaded active active /dev/sda2
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded active active Network
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
systemd-...iles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
/etc/slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
# sessions xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
# default_user simone
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
# focus_password no
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login no
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/run/lock/slim.lock
# Log file
logfile /var/log/slim.log
When i run "systemctl start slim" on tty1 slim starts again and after exiting openbox twice i'm back on tty1.
...But when i run "slim" on tty1 slim starts and i can exit openbox as often as i want.
Any ideas ?
Edit:
Running /usr/bin/slim from tty1 gives me this logfile.
/var/log/slim.log
slim: waiting for X server to begin accepting connections.
slim: waiting for X server to shut down
slim: waiting for X server to begin accepting connections.
slim: waiting for X server to shut down
slim: waiting for X server to begin accepting connections.
Somehow the second "slim: waiting for X server to shut down" does not happen when running "systemctl start slim"
Last edited by Synth (2013-03-19 19:39:10)

Ok, I was able to workaround parts of the bug:
I changed slim.conf and and set daemon = true (so slim runs as a daemon). Furthermore changed the slim.service file for systemd:
[Service]
Type = forking
PIDFile = /var/lock/slim.lock
ExecStart=/usr/bin/slim
Now I can log in and out as often as I want. Seems to work. However, nm-applet only shows up in odd numbers of logins:
1st login --> nm-applet is shown
2nd login --> nm-applet is not shown (but running --> htop)
3rd login --> nm-applet is shown
4th login --> nm-applet is not shown (but running --> htop)
...and so on...
I search the web, it seems to be a problem with dbus and the order how the services get started. Don't know if that is true...any ideas from anyone?

[SOLVED] New slim, can't shutdown|reboot|suspend anymore

Hi!
I just upgraded slim, and i notice that i cannot suspend, shutdown and reboot anymore.
And to mount usb drive, i am asked for my password.
After the upgrade i changed /etc/slim.conf,pacnew to suit my needs and then sudo mv /etc/slim.conf.pacnew /etc/slim.conf .
My .xinitrc is the same, so, where is the problem?
here there are my slim.conf:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user federico
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password no
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login yes
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
and my .xinitrc:
#!/bin/bash
export BROWSER=chromium
export DE=xfce
exec ck-launch-session dbus-launch startxfce4
Thanks!
Last edited by nierro (2012-05-08 18:42:44)

From later in this thread:
Solution
Ok, do:
ck-list-sessions
There were two sessions for myself. So, the new slim is starting your exec line already with a console kit session. This is new behavior. It didn't before.
So, I modified my exec line to remove "ck-launch-session" in .xinitrc to:
exec dbus-launch --exit-with-session startxfce4
Reverted the changes I made to the shutdown/restart policy and rebooted. Shutdown, restart, mounting USB drive: they all work again now.
Edit: from even later on in this thread, just:
exec startxfce4
As your .xinitrc exec line should be sufficient for practically anyone. "startxfce4" does the dbus-launch itself.
Original post here:
Changed in my /etc/slim.conf:
default_path /bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin
Same issue, in Action buttons Shutdown and Restart grayed out.
in .xinitrc, launch line:
exec ck-launch-session startxfce4
Launch line was:
exec ck-launch-session dbus-launch --exit-with-session startxfce4
But, same issue with that launch line. Was googling and I found results saying dbus-launch is contained within startxfce4.
Last edited by headkase (2012-05-09 02:23:48)

How do I use an external hard drive to back up my laptop? I bought a G Drive Slim from Apple.

I have a G Drive Slim external hard drive that was purchased from an Apple store. I need to back up my laptop. I've forgotten the procedure. It's not as easy as "plug it in and follow the instructions." Can anyone help?

It should be plug and play and if it isn't it is probably because your new drive isn't formatted for the Mac. Plug in the drive and run Disk Utility - it is in the Utilities folder inside the Applications folder. You should see the drive in the DU window. Click on the drive and look at the bottom of the DU program. You'll see a Drive Description and other information. The last item in the second column is Partition Map Scheme. If it says GUID Partition Table you are good to go. If it doesn't the drive needs to be partitioned to be GUID.
Partition the drive:
Select the drive device in the list of devices. For each physical drive you'll see a drive device and then indented under that you'll see a drive name. For example looking at DU on my computer I see two devices: Macintosh HD at the top and indented beneath it "Yosemite" then 2TB OWC Elite and indented beneath it "TM". I'd select 2TB OWC Elite
Choose the "Partition" tab that appears.
Select "1 Partition" from the drop-down menu (or more, if you have specific need for more than one volume). When you select a new partition layout from the drop-down menu, each new partition will be formatted to Mac OS Extended (Journaled) by default, but be sure to double-check this by selecting each in the partition diagram and then choosing the format for it.
Click the Options button and ensure "GUID" is selected as the partition scheme.
Click Apply to save the changes.
Open Time Machine Preferences and click on Select Disk. Choose your newly partitioned and formatted drive. Make sure TM is turned on. That's it.

Venue 11 Pro - Slim Keyboard not behaving as expected or it should.

I recently received the slim keyboard from dell for my Venue 11 Pro - Baytrail tablet. Overall I like the quality and functionality, although I too like others have encountered the intermittent non-functional keyboard, but that's not the subject of this post.
I have noticed a couple items in its behavior that don't work as you would expect and I hope can be corrected via software.
1. When the keyboard is attached but folded back behind the tablet (ie the keyboard is not in use) the on screen keyboard will not appear. This makes it hard to use the device as a tablet as anytime data entry is required you need to unfold the keyboard and hold it somehow while you type then fold it back behind the screen to continue tablet use. When folding the keyboard behind the unit its just as important to make the on screen keyboard available as it is to stop the keyboard itself from functioning, right now the keyboard stops working as it should be no alternative input is available.
2. In much the same way as item #1. When the keyboard is attached but folded back behind the tablet orientation is locked so the screen will not rotate to portrait or landscape mode at need. So if you were carrying it with the cover / slim keyboard on and opened it up, folding the keyboard behind the screen the screen is stuck in landscape mode. The only method ive found to change its orientation is to go to desktop and run the intel graphics app to edit the orientation.
Combined this makes the slim keyboard worse than useless in several usage scenarios. I want the slim keyboard for the occasional need to input more data than is practical on the touch screen AND to protect the tablet.... but if your usage is more tablet than notebook you will find yourself constantly working around these limitations.
You have a great product here, but you really need to take a page from the surface playbook here. They kind of set the standard and expectations for how keyboard covers on tablets should work and while I really like the hardware the usage is awkward as it stands.

Just got our first Venue 11 into the office and was very disappointed to find this thread already active. Yes, this is a very simple use-case where someone will have the slim keyboard connected and then flip it back to use the onscreen keyboard for the modern UI. Auto screen rotation and pop-up onscreen keyboard really are a must when the keyboard is flipped back. Not sure how that very basic behavior could have been missed in testing. Hoping for a resolution soon...

Two Dell venue 11 pro + dell slim keyboard = one - work, one - not

Have two Dell Venue 11 Pro - i5 8gb ram 256gb and i5 4gb ram 128gb
And one dell slim keyboard.
It works fine just with one tablet! Second device don't see keyboard - like it dead
How can i connect it? what i need to do? or install some driver maybe?

which port do you mean?
there are two same tablets and one slim keyboard. it works with one tablet, but not working with other
i just unplugged it from one and plug-in to second tablet
here is video
cs_setInnerHtml('video_b26d630e-77c7-4a6d-b4bd-49606efd7cfd','');

[Solved] "slim: failed to execute login command" after awesomewm updat

Hi,
i updated some weeks ago via pacman -Syu, where also awesome wm was updated from 3.4.* to 3.5.* so I updated my rc.lua as it is told on their wiki, but i cant login with my rc.lua anymore i got the failed to execute login command error from slime. If i use the shipped efault rc.lua it works fine, can someone help me to figure out whats wrong with my rc.lua?
-- Standard awesome library
local gears = require("gears")
local awful = require("awful")
awful.rules = require("awful.rules")
require("awful.autofocus")
-- Widget and layout library
local wibox = require("wibox")
-- Theme handling library
local beautiful = require("beautiful")
-- Notification library
local naughty = require("naughty")
local menubar = require("menubar")
local vicious = require("vicious")
function fullscreens(c)
awful.client.floating.toggle(c)
if awful.client.floating.get(c) then
local clientX = screen[1].workarea.x
local clientY = screen[1].workarea.y
local clientWidth = 0
-- look at http://www.rpm.org/api/4.4.2.2/llimits_8h-source.html
local clientHeight = 2147483640
for s = 1, screen.count() do
clientHeight = math.min(clientHeight, screen[s].workarea.height)
clientWidth = clientWidth + screen[s].workarea.width
end
local t = c:geometry({x = clientX, y = clientY, width = clientWidth, height = clientHeight})
else
--apply the rules to this client so he can return to the right tag if there is a rule for that.
awful.rules.apply(c)
end
-- focus our client
client.focus = c
end
-- {{{ Error handling
-- Check if awesome encountered an error during startup and fell back to
-- another config (This code will only ever execute for the fallback config)
if awesome.startup_errors then
naughty.notify({ preset = naughty.config.presets.critical,
title = "Oops, there were errors during startup!",
text = awesome.startup_errors })
end
-- Handle runtime errors after startup
do
local in_error = false
awesome.connect_signal("debug::error", function (err)
-- Make sure we don't go into an endless error loop
if in_error then return end
in_error = true
naughty.notify({ preset = naughty.config.presets.critical,
title = "Oops, an error happened!",
text = err })
in_error = false
end)
end
-- {{{ Variable definitions
-- Themes define colours, icons, and wallpapers
-- beautiful.init("/home/kili/Repositories/awesome-themes/arch/theme.lua")
beautiful.init("/usr/share/awesome/themes/default/theme.lua")
-- This is used later as the default terminal and editor to run.
terminal = "urxvt"
editor = os.getenv("EDITOR") or "nano"
editor_cmd = terminal .. " -e " .. editor
-- Default modkey.
-- Usually, Mod4 is the key with a logo between Control and Alt.
-- If you do not like this or do not have such a key,
-- I suggest you to remap Mod4 to another key using xmodmap or other tools.
-- However, you can use another modifier like Mod1, but it may interact with others.
modkey = "Mod4"
-- Table of layouts to cover with awful.layout.inc, order matters.
layouts =
awful.layout.suit.tile,
awful.layout.suit.tile.left,
awful.layout.suit.tile.bottom,
awful.layout.suit.tile.top,
awful.layout.suit.floating,
awful.layout.suit.fair,
awful.layout.suit.fair.horizontal,
awful.layout.suit.spiral,
awful.layout.suit.spiral.dwindle,
awful.layout.suit.max,
awful.layout.suit.max.fullscreen,
awful.layout.suit.magnifier
-- {{{ Tags
-- Define a tag table which hold all screen tags.
tags = {}
for s = 1, screen.count() do
-- Each screen has its own tag table.
tags[s] = awful.tag({ 1, 2, 3, 4, 5}, s, layouts[1])
end
-- {{{ Menu
-- Create a laucher widget and a main menu
myawesomemenu = {
{ "manual", terminal .. " -e man awesome" },
{ "edit config", editor_cmd .. " " .. awesome.conffile },
{ "restart", awesome.restart },
{ "quit", awesome.quit }
mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
{ "open terminal", terminal }
mylauncher = awful.widget.launcher({ image = beautiful.awesome_icon, menu = mymainmenu })
-- {{{ Wibox
-- Create a textclock widget
batwidget = wibox.widget.textbox()
vicious.register(batwidget, vicious.widgets.bat,
function(widget,args)
local formatstring = " Bat: "..args[1]..args[2] .."%".. " "..args[3] .. " "
if args[2] <= 25 and args[1] == "-" then
return "".. formatstring .. ""
end
return formatstring
end, 60, "BAT0")
netwidgetETH = wibox.widget.textbox()
netwidgetWIFI = wibox.widget.textbox()
vicious.register(netwidgetETH, vicious.widgets.net, ' eth0:${eth0 down_kb} ${eth0 up_kb}', 3)
vicious.register(netwidgetWIFI, vicious.widgets.net,' wlan0:${wlan0 down_kb} ${wlan0 up_kb}', 3)
menubar.utils.terminal = terminal
mytextclock = awful.widget.textclock()--{ align = "right" })
-- Create a systray
mysystray = wibox.widget.systray()
-- Create a wibox for each screen and add it
mywibox = {}
mypromptbox = {}
mylayoutbox = {}
mytaglist = {}
mytaglist.buttons = awful.util.table.join(
awful.button({ }, 1, awful.tag.viewonly),
awful.button({ modkey }, 1, awful.client.movetotag),
awful.button({ }, 3, awful.tag.viewtoggle),
awful.button({ modkey }, 3, awful.client.toggletag),
awful.button({ }, 4, function(t) awful.tag.viewnext(aweful.tag.getscreen(t)) end),
awful.button({ }, 5, function(t) awful.tag.viewprev(aweful.tag.getscreen(t)) end)
mytasklist = {}
mytasklist.buttons = awful.util.table.join(
awful.button({ }, 1, function (c)
if c == client.focus then
c.minimized = true
else
c.minimized = false
if not c:isvisible() then
awful.tag.viewonly(c:tags()[1])
end
-- This will also un-minimize
-- the client, if needed
client.focus = c
c:raise()
end
end),
awful.button({ }, 3, function ()
if instance then
instance:hide()
instance = nil
else
instance = awful.menu.clients({ width=250 })
end
end),
awful.button({ }, 4, function ()
awful.client.focus.byidx(1)
if client.focus then client.focus:raise() end
end),
awful.button({ }, 5, function ()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end))
for s = 1, screen.count() do
-- Create a promptbox for each screen
mypromptbox[s] = awful.widget.prompt()--{ layout = awful.widget.layout.horizontal.leftright })
-- Create an imagebox widget which will contains an icon indicating which layout we're using.
-- We need one layoutbox per screen.
mylayoutbox[s] = awful.widget.layoutbox(s)
mylayoutbox[s]:buttons(awful.util.table.join(
awful.button({ }, 1, function () awful.layout.inc(layouts, 1) end),
awful.button({ }, 3, function () awful.layout.inc(layouts, -1) end),
awful.button({ }, 4, function () awful.layout.inc(layouts, 1) end),
awful.button({ }, 5, function () awful.layout.inc(layouts, -1) end)))
-- Create a taglist widget
mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.filter.all, mytaglist.buttons)
-- Create a tasklist widget
mytasklist[s] = awful.widget.tasklist(s, awful.widget.tasklist.filter.currenttags, mytasklist.buttons)
-- Create the wibox
mywibox[s] = awful.wibox({ position = "top", screen = s })
-- Widgets that are aligned to the left
local left_layout = wibox.layout.fixed.horizontal()
left_layout:add(mylauncher)
left_layout:add(mytaglist[s])
left_layout:add(mypromptbox[s])
-- Widgets that are aligned to the right
local right_layout = wibox.layout.fixed.horizontal()
if s == 1 then right_layout:add(wibox.widget.systray()) end
right_layout:add(netwidgetWIFI)
right_layout:add(netwidgetETH)
right_layout:add(batwidget)
right_layout:add(mytextclock)
right_layout:add(mylayoutbox[s])
-- Now bring it all together (with the tasklist in the middle)
local layout = wibox.layout.align.horizontal()
layout:set_left(left_layout)
layout:set_middle(mytasklist[s])
layout:set_right(right_layout)
mywibox[s]:set_widget(layout)
-- Add widgets to the wibox - order matters
--mywibox[s].widgets = {
-- mylauncher,
-- mytaglist[s],
-- mypromptbox[s],
--layout = awful.widget.layout.horizontal.leftright
-- mylayoutbox[s],
-- mytextclock,
-- batwidget,
-- netwidgetETH,
-- netwidgetWIFI,
-- s == 1 and mysystray or nil,
-- mytasklist[s],
-- layout = awful.widget.layout.horizontal.rightleft
end
-- {{{ Mouse bindings
root.buttons(awful.util.table.join(
awful.button({ }, 3, function () mymainmenu:toggle() end),
awful.button({ }, 4, awful.tag.viewnext),
awful.button({ }, 5, awful.tag.viewprev)
-- {{{ Key bindings
globalkeys = awful.util.table.join(
awful.key({ modkey, }, "Left", awful.tag.viewprev ),
awful.key({ modkey, }, "Right", awful.tag.viewnext ),
awful.key({ modkey, }, "Escape", awful.tag.history.restore),
awful.key({ modkey, }, "j",
function ()
awful.client.focus.byidx( 1)
if client.focus then client.focus:raise() end
end),
awful.key({ modkey, }, "k",
function ()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end),
awful.key({ modkey, }, "w", function () mymainmenu:show() end),
-- Layout manipulation
awful.key({ modkey, "Shift" }, "j", function () awful.client.swap.byidx( 1) end),
awful.key({ modkey, "Shift" }, "k", function () awful.client.swap.byidx( -1) end),
awful.key({ modkey, "Control" }, "j", function () awful.screen.focus_relative( 1) end),
awful.key({ modkey, "Control" }, "k", function () awful.screen.focus_relative(-1) end),
awful.key({ modkey, }, "u", awful.client.urgent.jumpto),
awful.key({ modkey, }, "Tab",
function ()
awful.client.focus.history.previous()
if client.focus then
client.focus:raise()
end
end),
-- Standard program
awful.key({ modkey, }, "Return", function () awful.util.spawn(terminal) end),
awful.key({ modkey, "Control" }, "r", awesome.restart),
awful.key({ modkey, "Shift" }, "q", awesome.quit),
awful.key({ modkey, }, "l", function () awful.tag.incmwfact( 0.05) end),
awful.key({ modkey, }, "h", function () awful.tag.incmwfact(-0.05) end),
awful.key({ modkey, "Shift" }, "h", function () awful.tag.incnmaster( 1) end),
awful.key({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end),
awful.key({ modkey, "Control" }, "h", function () awful.tag.incncol( 1) end),
awful.key({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end),
awful.key({ modkey, }, "space", function () awful.layout.inc(layouts, 1) end),
awful.key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
awful.key({ modkey, "Control" }, "n", awful.client.restore),
-- Prompt
awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end),
awful.key({ modkey }, "x",
function ()
awful.prompt.run({ prompt = "Run Lua code: " },
mypromptbox[mouse.screen].widget,
awful.util.eval, nil,
awful.util.getdir("cache") .. "/history_eval")
end),
-- Multimedia
awful.key({ }, "XF86AudioLowerVolume", function () awful.util.spawn("amixer -q sset Master 2dB-") end),
awful.key({ }, "XF86AudioRaiseVolume", function () awful.util.spawn("amixer -q sset Master 2dB+") end),
awful.key({ }, "XF86AudioNext",function () awful.util.spawn( "mocp -f" ) end),
awful.key({ }, "XF86AudioPrev",function () awful.util.spawn( "mocp -r" ) end),
awful.key({ }, "XF86AudioPlay",function () awful.util.spawn( "mocp -G" ) end),
awful.key({ }, "Print", function () awful.util.spawn("ksnapshot") end),
awful.key({ }, "", function () awful.util.spawn("slimlock") end)
clientkeys = awful.util.table.join(
awful.key({ modkey, }, "f", function (c) c.fullscreen = not c.fullscreen end),
awful.key({ modkey, "Shift" }, "c", function (c) c:kill() end),
awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle ),
awful.key({ modkey, "Control" }, "Return", function (c) c:swap(awful.client.getmaster()) end),
awful.key({ modkey, }, "o", awful.client.movetoscreen ),
-- awful.key({ modkey, "Shift" }, "r", function (c) c:redraw() end),
awful.key({ modkey, }, "t", function (c) c.ontop = not c.ontop end),
awful.key({ modkey, }, "n",
function (c)
-- The client currently has the input focus, so it cannot be
-- minimized, since minimized clients can't have the focus.
c.minimized = true
end),
awful.key({ modkey, }, "m",
function (c)
c.maximized_horizontal = not c.maximized_horizontal
c.maximized_vertical = not c.maximized_vertical
end),
awful.key({ modkey, "Shift" }, "f", fullscreens)
-- Compute the maximum number of digit we need, limited to 9
keynumber = 0
for s = 1, screen.count() do
keynumber = math.min(9, math.max(#tags[s], keynumber))
end
-- Bind all key numbers to tags.
-- Be careful: we use keycodes to make it works on any keyboard layout.
-- This should map on the top row of your keyboard, usually 1 to 9.
for i = 1, keynumber do
globalkeys = awful.util.table.join(globalkeys,
awful.key({ modkey }, "#" .. i + 9,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewonly(tags[screen][i])
end
end),
awful.key({ modkey, "Control" }, "#" .. i + 9,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewtoggle(tags[screen][i])
end
end),
awful.key({ modkey, "Shift" }, "#" .. i + 9,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.movetotag(tags[client.focus.screen][i])
end
end),
awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.toggletag(tags[client.focus.screen][i])
end
end))
end
clientbuttons = awful.util.table.join(
awful.button({ }, 1, function (c) client.focus = c; c:raise() end),
awful.button({ modkey }, 1, awful.mouse.client.move),
awful.button({ modkey }, 3, awful.mouse.client.resize))
-- Set keys
root.keys(globalkeys)
-- Set Firefox to always map on tags number 2 of screen 1.
-- { rule = { class = "Firefox" },
-- properties = { tag = tags[1][2] } },
-- {{{ Rules
if screen.count() > 1 then
awful.rules.rules = {
-- All clients will match this rule.
{ rule = { },
properties = { border_width = beautiful.border_width,
-- border_color = beautiful.border_normal,
focus = true,
keys = clientkeys,
buttons = clientbuttons } },
{ rule = { class = "MPlayer" },
properties = { floating = true } },
{ rule = { class = "gimp" },
properties = { floating = true } },
{ rule = { class = "Xdialog" },
properties = { floating = true } },
{ rule = { class = "Firefox" },
properties = { tag = tags[1][1] } },
{ rule = { name = "Thunderbird" },
properties = { tag = tags[1][2] } },
{ rule = { instance = "plugin-container" },
properties = { floating = true } },
{ rule = { class = "Luakit" },
properties = { floating = true } }
else
awful.rules.rules = {
-- All clients will match this rule.
{ rule = { },
properties = { border_width = beautiful.border_width,
-- border_color = beautiful.border_normal,
focus = true,
keys = clientkeys,
buttons = clientbuttons } },
{ rule = { class = "MPlayer" },
properties = { floating = true } },
{ rule = { class = "gimp" },
properties = { floating = true } },
{ rule = { class = "Firefox" },
properties = { tag = tags[1][2] } },
{ rule = { name = "Thunderbird" },
properties = { tag = tags[1][3] } },
{ rule = { instance = "plugin-container" },
properties = { floating = true, fullscreen = true } },
{ rule = { class = "Dolphin" },
properties = { floating = false, fullscreen = false, tag = tags[1][4] } },
{ rule = { class = "Luakit" },
properties = { floating = true } },
{ rule = { class = "Pidgin" },
properties = { tag = tags[1][5] } }
end
-- {{{ Signals
-- Signal function to execute when a new client appears.
client.connect_signal("manage", function (c, startup)
-- Add a titlebar
-- awful.titlebar.add(c, { modkey = modkey })
-- Enable sloppy focus
c:connect_signal("mouse::enter", function(c)
if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
and awful.client.focus.filter(c) then
client.focus = c
end
end)
if not startup then
-- Set the windows at the slave,
-- i.e. put it at the end of others instead of setting it master.
-- awful.client.setslave(c)
-- Put windows in a smart way, only if they does not set an initial position.
if not c.size_hints.user_position and not c.size_hints.program_position then
awful.placement.no_overlap(c)
awful.placement.no_offscreen(c)
end
end
local titlebars_enabled = false
if titlebars_enabled and (c.type == "normal" or c.type == "dialog") then
-- Widgets that are aligned to the left
local left_layout = wibox.layout.fixed.horizontal()
left_layout:add(awful.titlebar.widget.iconwidget(c))
-- Widgets that are aligned to the right
local right_layout = wibox.layout.fixed.horizontal()
right_layout:add(awful.titlebar.widget.floatingbutton(c))
right_layout:add(awful.titlebar.widget.maximizedbutton(c))
right_layout:add(awful.titlebar.widget.stickybutton(c))
right_layout:add(awful.titlebar.widget.ontopbutton(c))
right_layout:add(awful.titlebar.widget.closebutton(c))
-- The title goes in the middle
local title = awful.titlebar.widget.titlewidget(c)
title:buttons(awful.util.table.join(
awful.button({ }, 1, function()
client.focus = c
c:raise()
awful.mouse.client.move(c)
end),
awful.button({ }, 3, function()
client.focus = c
c:raise()
awful.mouse.client.resize(c)
end)
-- Now bring it all together
local layout = wibox.layout.align.horizontal()
layout:set_left(left_layout)
layout:set_right(right_layout)
layout:set_middle(title)
awful.titlebar(c):set_widget(layout)
end
end)
client.connect_signal("focus", function(c) c.border_color = beautiful.border_focus end)
client.connect_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
Here is also my slime config and my initrc
ls -lisa .xinitrc
3276814 4 -rwxr-xr-x ...
#!/bin/sh
xrdb -merge ~/.Xresources
wicd-client --tray &
exec awesome #>> ~/.cache/awesome/stdout 2>> ~/.cache/awesome/stderr
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions awesome,xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user kili
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
focus_password yes
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login no
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme archlinux-simplyblack
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
Thanks in advance!
Edit:
Besides a lot of other errors the problem was the systray. It was created 2 times, now login works again. I figured that out via enabling logging for awesome in the xinitrc again.
Last edited by stubb (2013-01-08 23:20:05)

Hi,
I have the same kind of issue after updated slim from v1.3.4-4 to v1.3.5-1.
see my topic here :
https://bbs.archlinux.org/viewtopic.php?id=156792
Last edited by cedricl (2013-01-24 17:16:42)

Trying to connect my macbook pro to an LG FLATRON W2052TQ monitor

Trying to connect my macbook pro to an LG FLATRON W2052TQ but monitor but it does not work

Ya it is exactly same problem the Macbook see the monitor but but monitor does not show anything

Shockwave Player updates, gives 2 options, full or slim - nothing explains the difference How do I know what to use

McAfee program searches for programs that are susceptible to malware and automatically searched for updates and installs them. For some Reason, when it comes to Adobe products it requires myself to have to perform a manual update.
When I followed the link McAfee provides to the Adobe website and follow the steps to install the update....at one point it give you and option of an update that as the word "Full" in the middle of the Update Choice, and the 2nd option is exactly the same except instead of the word "Full", it has the word "Slim".
Nowhere (FAQs, etc) can I find the difference between the two, so how do I know which I need?
I have a Dell Laptop with Windows 8.1 operating system.
8GB Ram and I think its one of those Quad Drive things
1 TB Memory
I use Firefox as my internet operating system.
I started with Internet Explorer, but a problem existed that had something to do with that program not being loaded properly initially,
I tried to Get Microsoft Help but they wanted $149 to fix it, So I abandoned use of Internet Explorer and loaded Fire Fox.
I will note, I don't know if its germane or note, Since switching to Fire Fox,   my system stalls quite frequently and I get a popup that says something about a Flash Program (maybe shockwave flash) and it states it is not responding. It gives me the option to continue or cancel and a check box to not ask me again.   Though I select that check box I do get asked often.
When this Popup occurs, I can't use any of the internet windows I have open or any of the internet window Tabs I have open. It also seems to affect the one game I play (Spider) and it stalls that game also. I sense it has something to do with anything that has pictures on it possibly. After several minutes 3 to 5 plus it seems to recover
I'm sorry I am not real computer literate
Thank you for any help you can provide
Keith
PS All I am trying to do is get hold of Adobe to ask about their program, why I have to do all this registering and go into a Forum or Community (whatever those are) is confusing to me.

The Full version includes all xtras and the Slim version just the bare essentials. I would recommend using the full version as your experience of using the plugin will be more seamless (no pausing while required xtras are downloaded on demand)

1-new slim imac, 1-new vista machine, 1-new airport extreme

so I've been searching around the threads here and it seems like everyone's problems deal with like not seeing a wireless connection or not being able to print or not being able to file share and you would think that my situation was pretty common; if there is another thread about this please direct me and I apologize if I'm repeating a recent topic.
ok, so i'm setting up a small little network for my aunt, she has a brand new 20" imac slim, two vista machines and one xp laptop. i advised her of getting an airport extreme to share internet. the imac sees and connects to the airpot fine but with vista it does not. vista can clearly see the basestation but won't let me connect to it. i've used a simple WEP key to connect to the base station and basically used defaults for my setting, yes, i am using an "Equivalent Key" for the vista machines but vista just keeps telling me it is unable to connect due to an unknown error.
I've also tried to connect to the basestation with my little cousin's nintendo ds lites and it tells me that it "does not support this type of network security". i mean i just have WEP turned on, are there other settings on the basestation that i need to change? i'm new to the basestation i usually work with the airport express, the setting and stuff are different.
any ideas?
any and every post is much appreciated.

i reset the basestation and and installed the airport utility on the vista machine and through the vista machine set up the basestation. i still can not connect to the basestation if any sort of encryption is turned on but if the basestation is open then the vista pc connects fine. since it looks like wireless encryption isn't an option; is there a way that i can just keep the connection open and just use a MAC filter?
if they had cable internet it wouldn't be a bandwidth problem, but my aunt and uncle live in a somewhat rural area and they have to have satellite internet which means their download cap is around 17GB per month. if their neighbor knows and steals their bandwidth they'll hit 17GB in no time.
the basestation has the latest firmware and both imac and vista machines have airport utility installed but i still don't understand why i can't turn on wireless security and still have the vista machine connect.
i've tried using every encryption type possible and nothing will let the vista machine jump online; even the airport utility (on the vista machine) won't see the basestation when i turn on any sort wireless security.
thanks cloth542000 for your reply, does anyone have any ideas on what i should do?

Slim doesn't works but LXDE is ok

Hello (and sorry for my english )
I installed today arch linux on my laptop. At the beginning, everything was ok, slim worked fine. After playing with the policykit issue (see "I won the struggle against hal and policykit": http://bbs.archlinux.org/viewtopic.php?id=65070 )and installing the networkmanager (both are working now), slim doesn't works any more - I get a black screen with no mouse and nothing. I think that the problem is slim itself, because if I tipe "startx" from the commandline as normal user (after having killed X as root) lxde starts and everything works. I tried to reinstall slim but it doesn't works.
I don't know which files to post, so here are two of them
[swisstux@inspiron ~]$ cat .xinitrc
exec ck-launch-session startlxde
[swisstux@inspiron ~]$ cat /etc/rc.conf
DAEMONS=(syslog-ng polkitparser hal @cpufreq @laptop-mode @networkmanager @crond @alsa @slim)

it says only this:
slim: Stale lockfile found, removing it
it is a bit slow (too slow, on another PC it is 10 times faster), but it works if I start it from the command line. just on boot it doesn't works.
edit: here is the log of slim starting at boot and at the end the log of slim starting from the shell: http://pastebin.com/m4b6fad81
second edit: I removed every "@" from the daemon's list in rc.conf and now it works. but it is still really slow
Last edited by swisstux (2009-04-16 17:53:25)

Bash script: Rotate your wallpaper and SLiM theme at the same time

EDIT;
I've decided I should really thank Cerebral for his help with writing this script; this thank you should have been here from the get go.
After writing:
#!/usr/bin
echo "Hello World!"
I wrote a script to rotate my fluxbox background and SLiM theme at the same time, so I could have a contiuously changing background and still have a smooth transition from SLiM to fluxbox. (It just looks so much cooler when both have matching backgrounds). By the time you finish reading it, and configuring your box so it will work, you will probably have decided you could have writtin your own, better script to do the same thing. But, on the off chance anybody finds use for it, here it is:
(this should be obvious, but: don't run this script without at least reading the comments)
#!/bin/bash
#this is a script to rotate a number of backgrounds
#to be shared by the fluxbox desktop and SLiM login manager.
#it is the first meaningful script I've written. It may be
#freely distributed and used with the understanding that you are
#using it at your own risk.
#Before running this script you need to check that your SLiM
#themes are installed to the path /usr/share/slim/themes, which
#is the defulat path for installation in Arch. Here are some
#other things you need to set up:
#1. create (if you don't have it) the directory /usr/share/wallpapers
#2. create a wallpaper in /usr/share/wallpapers called 'dummy' by copying
#you current wallpaper to that filename
#3. set your window manager to display the wallpaper 'dummy', this works fine
#using a style overlay in fluxbox, I haven't tested it with any other window
#manager, but I don't see why this would cause a problem.
#4. create a directory /usr/share/slim/themes/current, you can copy one of
#your slim themes into that directory if you want. (this will prevent you
#from seeing some error messages the first time you run the script)
#5. define the names of the themes you want to rotate, in order for this
#script to work, you must name them "themeNUMBER", where NUMBER is replaced
#by an integer. Your themes must be numbered consecutively, start with 1
# that is:
#theme1 , theme2, theme3, etc. , theme305
#If you don't number consecutively, this script will not run properly. You
#must also define the total number of themes as "rotate_number"
#6. Check if the script runs, if it does, you should change /etc/slim.conf to
#use the theme "current"
#7. This theme will now rotate your SLiM theme and wallpaper in such a way as
#to make them match each other. Note that SLiM will not let you change themes
#"on the fly", (as of July 6, 2008), so changes will not be apparent unless you
#restart SLiM. I run the script before I run slim in my etc/rc.local local
#script, so each time I reboot I get different wallpaper / login background.
#Fred Drueck 2008
#Define here all themes to be rotated and the total number of
#themes to rotate:
rotate_number=9
theme1=/usr/share/slim/themes/default
theme2=/usr/share/slim/themes/lake
theme3=/usr/share/slim/themes/lunar
theme4=/usr/share/slim/themes/flower2
theme5=/usr/share/slim/themes/the-light
theme6=/usr/share/slim/themes/mindlock
theme7=/usr/share/slim/themes/parallel-dimensions
theme8=/usr/share/slim/themes/wave
theme9=/usr/share/slim/themes/fingerprint
#check you are running this script as super-user:
if [ $(id -u) != "0" ]; then
echo "You must be the superuser to run this script" >&2
exit 1
fi
echo "rotating themes"
#figure out which theme is currently set, then name it as the variable
#"last theme number", otherwise set last theme number as 0
if [ -f /usr/share/slim/themes/current/current_theme_number ]
then
echo "checking current theme"
cd /usr/share/slim/themes/current/
eval last_theme_number=$(cat /usr/share/slim/themes/current/current_theme_number)
echo $last_theme_number
else
echo "no theme is currently set, using theme 1"
last_theme_number=0
echo $1 > /usr/share/slim/themes/current/current_theme_number
fi
#set the new theme number
eval new_theme_number=$(($(($last_theme_number % $rotate_number))+1))
#select the new theme
placeholder=theme
eval new_theme=\$$placeholder$new_theme_number
echo $new_theme
#now clean out the "current" theme where I keep the current
#theme for slim
rm /usr/share/slim/themes/current/background*
rm /usr/share/slim/themes/current/panel*
rm /usr/share/slim/themes/current/slim.theme
#the wildcards are there since the themes use jpg and png files
cp $new_theme/background* /usr/share/slim/themes/current
cp $new_theme/panel* /usr/share/slim/themes/current
cp $new_theme/slim.theme /usr/share/slim/themes/current
#increase the theme number, but first clear the old file
rm /usr/share/slim/themes/current/current_theme_number
echo $new_theme_number > /usr/share/slim/themes/current/current_theme_number
#copy over the dummy wallpaper in "/usr/share/wallpapers" (with the theme
#background file
cp $new_theme/background* /usr/share/wallpapers/dummy
exit 0
Last edited by pseudonomous (2008-07-07 21:59:42)

oh i forgot to mention... its rotating while moving. i.e. is doesn't have to stop rotate and then continue back to origin.

How can I slim down the aperture library?

Hi,
My aperture library grew a lot. Is there any way to slimmed it down, without erasing content? I am talking about recreating previews with less quality or smaller size, deleting old thumbnails (I read that even if you delete a picture from the library, Aperture won't delete the thumbnail).
Does anybody knows any tricks about how to do that?
Thank you very much for your answers!
Gus

Easy. Switch to Referenced-Masters Library with Masters on external drives.
More complete explanation:
First make a Vault to an external drive as backup.
Then from within Aperture:
File Menu--> Relocate Masters. Choose external hard drive(s) and direct Aperture to move the Masters to those drives. Give it plenty of time depending on how many Masters are being moved. The Library remains on an internal drive, only the Masters get moved.
Next back up the drive that the Masters were relocated to, because now you have a Referenced Masters Library so Masters are backed up (once) separately from the Library Vault backups.
In the future back up originals (once) on external drives prior to import into Aperture or any other images app. I cannot overstate how important that is, and various manuals, texts, etc. present workflows that skip that critical step. Also back up the Aperture Library using Aperture's Vaults, which are designed for that purpose.
A complete Referenced-Masters workflow follows. Note that for image security reasons Aperture is not involved until the end of the process:
• Create a folder ("abc") for the incoming images. Easiest is to create the folder on the external hard drive where the Masters will permanently live, but Referenced Masters can be temporarily on the laptop's internal drive, then moved later as described above. I initially put Masters referenced on my MBP internal drive, then after backup and editing I use File Menu--> Relocate Masters to move the Masters to a permanent external drive location.
• Connect a card reader with the camera card in it. The camera card should show on the desktop. If it does not show, restart the Mac with the reader and card still plugged in. You can of course use the camera directly in this step, but I do not recommend it. Obviously cameras like the iPad2 do require direct camera-to-computer uploading.
• Drag the contents of the card's image folder(s) to the abc folder that you previously created on the hard drive.
• Review the abc folder contents to be sure they all copied properly.
• Software-eject the camera card.
• Physically disconnect the camera card reader from the Mac. This step is important to help avoid all-too-common human error.
• Again review the abc folder contents to be sure they are indeed all there (because stuff happens sometimes...).
• Back up the abc folder contents on to another drive.
• Review the files on the backup to be sure they all copied properly.
• At any time after but not before the previous step you can reformat the camera card in-camera. Do not delete images on the card using the computer.
• Start Aperture.
• Import the images from folder abc into Aperture, selecting "Store Files: In their current location" on the right-hand side of the import window (important!). Note that the Library remains on an internal drive, only the Masters are on externals.
HTH
-Allen Wicks

Display Problem with my Mac Pro and LG Flatron Wide Monitor in Mountain Lion

After upgrading to Mountain Lion, my Mac Pro has display problems with my LG Flatron display. The image is displayed with a black bar on the right and on the bottom. And the left side of the content is not visible. I tried every resolution available in the Display System Preferences, they are different in terms of how big the black bars are, and what part is not visible, but none of them are correct. I held down the option key to try to detect displays or switch to resolutions that are not normally available. When I restart the image is lined up with the display, but if the display ever goes to sleep or gets turned off, the image reverts to being off center, and the only way I can get it back is to restart... The interesting thing is that this monitor works fine with the same machine if I reboot using BootCamp into Windows 7. The Monitor also works fine, connecting the same connector to a Mac Mini, although that mac mini is running 10.6 and not Mountain Lion. I've reset the SMC and restarted countless times, I don't see any other levers to pull or things to try...

That card is for a PC it may not give you Startup and Option-Boot screens.
The 7950 "Mac Edition" card has a very distinctive look:
http://www.sapphiretech.com/presentation/product/product_index.aspx?cid=1&gid=3& sgid=1157&pid=1777&psn=&leg=0&lid=1

LG 1780U (Flatron Slim)

Similar Messages

Maybe you are looking for