[solved] maximizing window results in white screen

hi, using xfce4 and gdm with nvidia driver (from Arch), 64 bit, using compiz
while in the GUI if i maximize a window, say Thunderbird, the app only shows a white screen. the window decorations are still there and i can restore it down and everything is fine, but when i maximize, white screen
not to post two problems in one thread, but im using emerald via compiz, but i would like to use gtk-window-decorator but if i change it, it does not stick. after a log out/log in it is changed back to emerald
i have tried different emerald themes and i still get the white screen. i think it only happens when the window is opened small to begin with. if it opens full screen i dont have that problem
Last edited by dodgefan (2011-07-19 03:57:39)

i think i figured this out, i was using the latest nvidia driver when i should have been using the 173xx series

Similar Messages

Updates from Apple result in white screen, have to reinstall thru time machine, 4hrs.

I have a Mac 21.5, OS X Yosemite 10.10.2
Processor: 3.06 GHz; intel Core i3
Memory 4 GB 1333MHz DDR3
If I do an update from Apple I end up with the White Screen of Death. I restore thru Time Machine and this takes about 4hrs. I have to turn off, unplug everything then plug everything back in, power up while holding "shift" "command" "r" and "p", keeping my finger on power button till I get an option screen with 4 choices. I've found, restore with Time Machine the best choice. It takes two people to hold the keys and power up. I don't know why this happens, hoping for some ideas. There has to be an easier and faster way to restore. I currently have an update pending, 10.10.3, I just did 10.10.2 Saturday (04-11-15) and had to go through all of the above to get update and eliminate "white screen" to restore.

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of it have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. Here's a general summary of what you need to do, if you choose to proceed:
☞ Copy a particular line of text to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.
5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is sometimes, but not always, slow, run the test during a slowdown.
You may have started up in "safe" mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
6. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
7. Load this linked web page (on the website "Pastebin.") The title of the page is "Diagnostic Test." Below the title is a text box headed by three small icons. The one on the right represents a clipboard. Click that icon to select the text, then copy it to the Clipboard on your computer by pressing the key combination command-C.
If the text doesn't highlight when you click the icon, select it by triple-clicking anywhere inside the box. Don't select the whole page, just the text in the box.
8. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:
[Process started]
        Part 1 of 8 done at … sec
        Part 8 of 8 done at … sec
        The test results are on the Clipboard.
        Please close this window.
[Process completed]
The intervals between parts won't be exactly equal, but they give a rough indication of progress. The total number of parts may be different from what's shown here.
Wait for the final message "Process completed" to appear. If you don't see it within about ten minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it and go to the next step. You'll have incomplete results, but still something.
12. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.
Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the referenced "Diagnostic Test"), I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Mac Mini Server Boot Camp Windows 8.1 White Screen Issue

Hello Apple Peeps!
I have a Mac Mini Server 2012 which I have had for around 6 months. I use it quite a lot mainly for Music Production on the OS X side and Graphic Design on the Windows side.
I recently decided to factory restore it as I wanted to spring clean it and reorganise the way some of my apps were installed. The way I had it set up was it was running OS X on one SSD and Windows 8.1 (installed using Boot Camp) on the other SSD. The way I went about the factory restore was I first used disk utility to erase/format the Windows SSD to Mac OS Extended (Journaled) and then went about the factory restore of OS X onto the other SSD as normal (following instructions from the Apple website).
The issue I am having now is that my newly installed Windows 8.1 (used solely on a single SSD) is hanging on a white screen for quite a long time before the Windows splash screen shows up, where before when I would boot or restart into Windows there was no white screen and it would go straight into the Windows splash screen and load to the desktop very quickly.
So my question is...
Why do I get this prolonged white screen before the Windows 8.1 splash screen appears? How can I get rid of it? It was certainly not present on my previous installation. Can anyone advise me what the computer is doing during this time so that I can do some further research into a solution.
What I have tried already....
1) PRAM & SMC reset.
2) Setting the startup disk to Boot Camp in both OS X and Windows 8.1.
3) Reinstalling Windows 8.1 through Boot Camp.
MAC MINI SERVER (LATE 2012), 2.6GHZ QUAD CORE I7, 16GB RAM, 2 x 256GB SSD, OS X 10.10.2, Windows 8.1 (Retail), Boot Camp Assistant (5.1.3), Covered By AppleCare.
I would really appreciate some help with this ;-)

I have right clicked on each SSD in Device Manager and selected the option 'Properties' from the drop down menu, which brings me to this window...
I'm not sure where I can find Device Attributes, I have clicked on each of the tabs in the window above, as far as I can see none of them mention AHCI enabled or anything similar. Thanks for all of your responses by the way...much appreciated!

Fixed iphone glass screen, resulted in white screen after assembling it back together?

i've had a cracked screen on my iphone 3Gs for a fairly long time now and i decided to replace it. It's been working perfectly with the cracked screen and after i had replaced the glass screen and assembling it back all together, i have a white screen on the front, doesn't seem to go away and i've searched online for all types of solutions such as holding down the home and power button for 10secs etc but none seem to work, i came to an conclusion thinking its hardware? can anyone help me please, would be much appreciated. thanks
note: i intend to take it to the apple store as my last option
Kind Regards

"note: i intend to take it to the apple store as my last option"
That should have been the first thnig that you should have done. If you had done so, Apple could have done an out-of-warranty exchange for you. Now that you've tried to fix it, and failed, Apple won't extend the exchange to you. I think that you might be able to sell your iPhone "as is" to a techno-tweek, or you can use it as a door stop.

[SOLVED] awesome & urxvt results in some screen flickering

Hi,
i've been using awesome since a few weeks and i noticed a flickering problem when starting urxvt (via mod4+enter).
urxvt starts, disappears, comes back again, disappears and so on.
starting up urxvt (time until i get a usable promt) takes about 1-2 seconds.
However, i don't know how to track the problem down. Maybe it is urxvt's (i think it is), maybe it is awesome's or even ati's fault (using 2.6.32 with open source ati driver).
when i switch between multiple windows (using mod4+n) only urxvt windows are flickering. Switching between gui-apps (ff, dolphin, …) works as expected.
maybe someone has an idea about this …
Here are the configs:
.Xdefaults:
!URxvt settings
!--[Title]--!
URxvt*title: urxvtc
URxvt*termName: rxvt-unicode
URxvt*cursorBlink: true
URxvt*urgentOnBell: true
!--[Url's /launching/marking/yanking]--!
URxvt.perl-ext: default,matcher
URxvt.urlLauncher: /usr/bin/firefox
URxvt.matcher.button: 1
!--[Fonts]--!
URxvt*font: xft:Bitstream Vera Sans Mono:pixelsize=14:antialias=false
URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true:antialias=false
URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true:antialias=false
URxvt.underlineColor: yellow
URxvt.scrollBar: false
!--[Urxvt Options]--!
URxvt.boldMode: false
URxvt.imLocale: de_AT.UTF-8
URxvt.loginShell: true
URxvt.saveLines: 512
URxvt.inheritPixmap: true
URxvt.borderless: true
URxvt.jumpScroll: true
URxvt.tintColor: white
URxvt.internalBorder: 0
URxvt.cursorBlink: false
URxvt.cursorColor: #dd9900
URxvt.cursorColor2: #000000
URxvt.background: #222222
URxvt.foreground: #ddccbb
URxvt.colorBD: #ffffff
URxvt.colorIT: #bbbbbb
URxvt.colorUL: #999999
URxvt.underlineColor: #999999
URxvt*saveLines: 512
!URxvt*depth: 32
!URxvt*background: rgba:02f0/04f0/04f0/cccc
URxvt*transparent: true
URxvt*shading: 10
!--[Colours]--!
!Theme One from
!http://phraktured.net/terminal-colors/terminal%20theme.tags.html
*background: rgb:00/00/00
*foreground: rgb:a8/a8/a8
*color0: rgb:00/00/00
*color1: rgb:a8/00/00
*color2: rgb:00/a8/00
*color3: rgb:a8/54/00
*color4: rgb:00/00/a8
*color5: rgb:a8/00/a8
*color6: rgb:00/a8/a8
*color7: rgb:a8/a8/a8
*color8: rgb:54/50/54
*color9: rgb:f8/54/50
*color10: rgb:50/fc/50
*color11: rgb:f8/fc/50
*color12: rgb:50/54/f8
*color13: rgb:f8/54/f8
*color14: rgb:50/fc/f8
*color15: rgb:f8/fc/f8
http://github.com/nblock/config/blob/master/.Xdefaults
rc.lua:
-- {{{ Load libraries
-- Standard awesome library
require("awful")
require("awful.autofocus")
require("awful.rules")
-- Theme handling library
require("beautiful")
-- Notification library
require("naughty")
require("vicious")
-- {{{ Variable definitions
-- Themes define colours, icons, and wallpapers
beautiful.init("/usr/share/awesome/themes/zenburn/theme.lua")
-- This is used later as the default terminal and editor to run.
terminal = "urxvtc"
editor = "vim"
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, --1
awful.layout.suit.tile.left, --2
awful.layout.suit.tile.bottom, --3
awful.layout.suit.tile.top, --4
awful.layout.suit.fair, --5
awful.layout.suit.fair.horizontal, --6
awful.layout.suit.spiral, --7
awful.layout.suit.spiral.dwindle, --8
awful.layout.suit.max, --9
awful.layout.suit.max.fullscreen, --10
awful.layout.suit.magnifier, --11
awful.layout.suit.floating --12
-- some commands
local commands = {}
commands.suspend = "sudo pm-suspend"
commands.help = "touch ~/seppal"
commands.lock = "xscreensaver-command --lock"
commands.screenshot = "scrot -e 'mv $f ~/bilder/screenshots'"
--audio stuff
commands.raisevol = "amixer set PCM 2%+"
commands.lowervol = "amixer set PCM 2%-"
commands.mute = "amixer sset PCM toggle"
commands.cmusnext = "cmus-remote --next"
commands.cmusprev = "cmus-remote --prev"
commands.cmuspause = "cmus-remote --pause"
commands.cmusplay = "cmus-remote --play"
commands.calc = "krunner"
--todo
commands.fileman = "pcmanfm"
commands.calc = "xcalc"
commands.browser = "firefox"
-- {{{ 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 download", "2 mail", "3 chat",
"4 music", "5 news", "6 fm",
7, 8, 9 }, s,
{layouts[3], layouts[1], layouts[1], -- Tags: 1, 2, 3
layouts[1], layouts[1], layouts[1], -- 4, 5 ,6
layouts[1], layouts[1], layouts[1] -- 7, 8, 9
end
-- {{{ Menu
-- Create a laucher widget and a main menu
myawesomemenu = {
{ "manual", terminal .. " -e man awesome" },
{ "edit config", editor_cmd .. " " .. awful.util.getdir("config") .. "/rc.lua" },
{ "restart", awesome.restart },
{ "quit", awesome.quit }
mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
{ "open terminal", terminal }
mylauncher = awful.widget.launcher({ image = image(beautiful.awesome_icon),
menu = mymainmenu })
-- {{{ Wibox
-- {{{ Widgets configuration
-- {{{ Reusable separators
local spacer = widget({ type = "textbox", name = "spacer" })
local separator = widget({ type = "textbox", name = "separator" })
spacer.text = " "
separator.text = " • "
-- {{{ CPU load
local cpuwidget = widget({ type = "textbox" })
vicious.register(cpuwidget, vicious.widgets.cpu, "load: $2% - $3%")
-- {{{ CPU temperature
local thermalwidget = widget({ type = "textbox" })
vicious.register(thermalwidget, vicious.widgets.thermal, "temp: $1°C", 20, "thermal_zone1")
-- {{{ Battery state
-- Widget icon
-- baticon = widget({ type = "imagebox", name = "baticon" })
-- baticon.image = image(beautiful.widget_bat)
local batwidget = widget({ type = "textbox" })
vicious.register(batwidget, vicious.widgets.bat, "bat: $1$2%", 60, "C1C5")
-- {{{ Date and time
local datewidget = widget({ type = "textbox" })
vicious.register(datewidget, vicious.widgets.date, "%a, %d.%m.%y - %H:%M", 5)
-- {{{ Volume widget
local volwidget = widget({ type = "textbox" })
vicious.register(volwidget, vicious.widgets.volume, "vol: $1%", 1, 'PCM')
-- {{{ System tray
systray = widget({ type = "systray" })
-- {{{ Wibox initialisation
local wibox = {}
local promptbox = {}
local layoutbox = {}
local taglist = {}
taglist.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, awful.tag.viewnext),
awful.button({ }, 5, awful.tag.viewprev))
for s = 1, screen.count() do
-- Create a promptbox
promptbox[s] = awful.widget.prompt({ layout = awful.widget.layout.horizontal.leftright })
-- Create a layoutbox
layoutbox[s] = awful.widget.layoutbox(s)
layoutbox[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
taglist[s] = awful.widget.taglist(s, awful.widget.taglist.label.all, taglist.buttons)
-- Create the wibox
wibox[s] = awful.wibox({
position = "top", screen = s,
fg = beautiful.fg_normal, bg = beautiful.bg_normal
-- Add widgets to the wibox
wibox[s].widgets = {{
launcher, taglist[s], layoutbox[s], promptbox[s],
layout = awful.widget.layout.horizontal.leftright
s == screen.count() and systray or nil,
spacer, datewidget,
separator, volwidget,
separator, batwidget,
separator, cpuwidget,
separator, thermalwidget,
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(
--user defined
awful.key({}, "XF86PowerOff", function() awful.util.spawn_with_shell(commands.suspend) end ),
awful.key({}, "Help", function() awful.util.spawn_with_shell(commands.help) end ),
awful.key({ modkey, }, "F12", function () awful.util.spawn_with_shell(commands.lock) end),
--audio stuff
awful.key({}, "XF86AudioMute", function() awful.util.spawn_with_shell(commands.mute) end ),
awful.key({}, "XF86AudioRaiseVolume", function() awful.util.spawn_with_shell(commands.raisevol) end ),
awful.key({}, "XF86AudioLowerVolume", function() awful.util.spawn_with_shell(commands.lowervol) end ),
awful.key({}, "XF86AudioNext", function() awful.util.spawn_with_shell(commands.cmusnext) end ),
awful.key({}, "XF86AudioPrev", function() awful.util.spawn_with_shell(commands.cmusprev) end ),
awful.key({}, "XF86AudioPlay", function() awful.util.spawn_with_shell(commands.cmuspause) end ),
awful.key({}, "XF86Tools", function() awful.util.spawn_with_shell(commands.cmusplay) end ),
awful.key({}, "XF86Calculator", function() awful.util.spawn_with_shell(commands.calc) end ),
awful.key({}, "Print", function() awful.util.spawn_with_shell(commands.screenshot) end ),
-- awful.key({}, "XF86MyComputer", function() awful.util.spawn_with_shell(commands.fileman) end ),
-- awful.key({}, "XF86Mail", function() awful.util.spawn_with_shell(commands.mail) end ),
-- awful.key({}, "XF86HomePage", function() awful.util.spawn_with_shell(commands.browser) end ),
-- awful.key({}, "XF86Sleep", function() awful.util.spawn_with_shell(commands.lock) end ),
-- awful.key({"Control", "Mod1"}, "l", function() awful.util.spawn_with_shell(commands.lock) end ),
--default bindings
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, }, "n",
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(true) end),
-- Layout manipulation
awful.key({ modkey, "Shift" }, "n", function () awful.client.swap.byidx( 1) end),
awful.key({ modkey, "Shift" }, "k", function () awful.client.swap.byidx( -1) end),
awful.key({ modkey, "Control" }, "n", 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),
-- Prompt
awful.key({ modkey }, "r", function () promptbox[mouse.screen]:run() end),
-- Run stuff in a Terminal
awful.key({ modkey }, "x", function ()
awful.prompt.run({ prompt = "Run in Terminal: " }, promptbox[mouse.screen].widget,
function (prog)
awful.util.spawn_with_shell(terminal .. " -name " .. prog .. " -e /bin/bash -c " .. prog)
end)
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, }, "j", function (c) c.minimized = not c.minimized end),
awful.key({ modkey, }, "m",
function (c)
c.maximized_horizontal = not c.maximized_horizontal
c.maximized_vertical = not c.maximized_vertical
end)
-- 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)
-- {{{ Rules
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 } },
--floating apps
{ rule = { class = "pinentry-qt4" },
properties = { floating = true } },
{ rule = { class = "Gimp" },
properties = { floating = true } },
--apptags
--downloading stuff
{ rule = { class = "JDownloader" },
properties = { tag = tags[1][1],switchtotag = true } },
{ rule = { instance = "rtorrent" },
properties = { tag = tags[1][1],switchtotag = false } },
-- mail
{ rule = { class = "Kmail" },
properties = { tag = tags[1][2],switchtotag = true } },
--chat and stuff like that
{ rule = { class = "Choqok" },
properties = { tag = tags[1][3],switchtotag = false } },
{ rule = { class = "Kopete" },
properties = { tag = tags[1][3],switchtotag = false } },
-- cmus
{ rule = { instance = "cmus" },
properties = { tag = tags[1][4],switchtotag = true } },
-- news
{ rule = { instance = "newsbeuter" },
properties = { tag = tags[1][5],switchtotag = true } },
--file manager
{ rule = { class = "Dolphin" },
properties = { tag = tags[1][6],switchtotag = true } },
--misc stuff
{ rule = { class = "Konqueror" },
properties = { tag = tags[1][9],switchtotag = true } },
-- {{{ Signals
-- Signal function to execute when a new client appears.
client.add_signal("manage", function (c, startup)
-- Add a titlebar
-- awful.titlebar.add(c, { modkey = modkey })
-- remove gaps
c.size_hints_honor = false
-- Enable sloppy focus
c:add_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
end)
client.add_signal("focus", function(c) c.border_color = beautiful.border_focus end)
client.add_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
-- {{{ Autostart
os.execute("krandrtray &")
-- vim: fdm=marker fdl=0 sts=4 ai
http://github.com/nblock/config/blob/ma … ome/rc.lua
Thanks.
Last edited by nblock (2010-01-02 09:59:24)

Try this .Xdefaults which works with awesome/urxvt.
*utf8: 1
*faceSize: 10
*jumpScroll: true
*multiScroll: true
*boldMode: false
*scrollBar: false
*cutNewline: false
*scrollTtyOutput: false
*scrollKey: true
*cursorBlink: true
*dynamicColors: true
*saveLines: 5000
*geometry: 125x45
! URxvt
URxvt*termName: xterm
URxvt.font: xft:Bitstream Vera Sans Mono:antialias=true:pixelsize=12
!urxvt.font: xft:Bitstream Vera Sans Mono-12:antialias=true
URxvt*transparent: false
URxvt*tintColor: #666666
URxvt*shading: 50
URxvt*scrollBar: false
URxvt*internalBorder: 5
URxvt*urgentOnBell: true
URxvt*scrollTtyKeypress: true
URxvt*underlineColor: yellow
URxvt*perl-ext-common: default,matcher
URxvt*urlLauncher: firefox
URxvt*matcher.button: 1
URxvt*matcher.pattern.1: \\bwww\\.[\\w-]\\.[\\w./?&@#-]*[\\w/-]
! Colours
*background: #303030
*foreground: #f2f2f2
*cursorColor: #999
*highlightColor: #333
*color0: #101010
*color1: #f13a21
*color2: #93f91d
*color3: #ffd00a
*color4: #404f9e
*color5: #ec0048
*color6: #2aa7e7
*color7: #f2f2f2
*color8: #1d202f
*color9: #ff361e
*color10: #ffc005
*color11: #93ff00
*color12: #3071ff
*color13: #ef0051
*color14: #4bb8fd
*color15: #a020f0
Last edited by r6 (2010-01-02 05:05:11)

[Solved] Tiling window managers and on-screen keyboards

I've got a small, old tablet pc with a 10" touchscreen, and was hoping to use a tiling window manager so that I could have an on-screen keyboard (onboard, cellwriter etc) stuck to the bottom third of the screen, and other applications 'fullscreened' in the rest of it, preferably in tabs.
I've tried a few tabbed tiling wm's (i3, xmonad, wmii, ion3) and while I can get the layout I want, I'm unable to use the onscreen keyboard due to focus switching - clicking on the 'keys' of the keyboard (or in fact, moving the cursor into it's frame/window/whatever) moves the focus to the keyboard, so it sends the typed text to itself.
Since tiling wm's are usually targeted at keyboard users, I'm having trouble finding which wm's listen to the onscreen keyboard's 'nofocus' properties. Does anyone know of any tiling wm's that respect that property and work with onscreen keyboards? Or even if there are simple config changes I can do to stop the keyboard from getting focus?
Failing that, any other window managers I could try? fwiw, I really liked twindy (http://www.niallmoody.com/twindy/about.htm) but it suffered from the same problem (and wasted a fair amount of space with its sidebar).
Thanks!
Last edited by mjc506 (2010-12-10 00:41:01)

Ah, thanks, that got me looking for and finding an xmonad patch that should make it not focus on onboard and cellwriter, amongst others: http://code.google.com/p/xmonad/issues/detail?id=177 Its a shame that the patch still isn't in the darcs repo, but I guess a working open office is more important that the few people using onscreen keyboards!
...time to compile from source... ugh - only got a single core running at 900kHz...

13" MBP: Maximized Windows Not Utilizing Whole Screen

I have a 2011 13" Macbook Pro. If I maximize the window of any application (whether by using the green button or by dragging the lower right corner) I'm not able to use the last few pixels at the bottom of the screen.
The Desktop image goes to the bottom of the screen, but windows can not use the last 5-10 (?) pixels of the screen.
Anyone experienced this or know what's going on?
Thanks.

I see what you are saying. It looks like about 3 pixels on my 15"
I use RightZoom.app for better control and still see the pixels (desktop) at the bottom. Never really noticed this before, but rarely do I pull a window all the way to the bottom.
In Firefox shift-command-F it will capture the entire screen however.

White screen on Canvas window

I am using Final Cut and have created a small problem.
When viewing playback from the timeline in the canvas window, everything is fine. However, when I pause the playback the canvas window shows a white screen and when I try to move my text around etc, I can see the wireframe moving but I get a little black cross in the top right of the canvas.
Any ideas?

http://discussions.apple.com/message.jspa?messageID=10600003#10600003

White screen, safe mode won't boot up

My iMac won't boot up in safe mode (shift key) and when I try to run Recovery HD (option key) I still get the white screen freeze up.
Order of events:
computer was freezing with vertical lines, sometimes on boot up too.
Tried installing avast. Now vertical lines every attemp to boot up.
Reset PRAM. now white screen freeze up on boot up
Safe mode (shift) results in white screen
Recovery HD results in white screen
So nothing appears to be loading, except the single user mode.
Is there anthing I can do in the single user mode to revive the beast?
Thanks!

Hi there
I am having the exact same problem - may I know how was this solved?
Did you have to replace your logic board etc?
Thanks!!!!

Opening maximized window from embedded flash movie

Hi!
I need your help!
I have a html file with a flash movie-menu embedded into it. I'd like one of the buttons to open an external html page strictly in a new maximized window. It does not matter if the new window has toolbar or not. I want it to open a new maximized window (not the full screen thing) onclick.
How can I achieve this?
thank you!

use the javascript window.open method to open your popup and set the page dimensions.
you can use getURL or navigateToURL() to execute a javascript function or better use the externalinterface class to call a javascript function in your embedding html file.

Internet PDFs produce white screen with AR 9.3.4

This may be similar to "BUG? Links in Adobe Reader 9.3.4 don't work" and if so my apologies.
My problem is when opening PDF links within a secure website (banks, etc.). When I click on the link, IE opens a window and "Start downloading..." and "Done" appear at the bottom; however, nothing ever appears on the window except a white screen. Would this have something to do with the Security settings in AR? If so, what might those be as I have looked at the selection options and nothing really sounds like my issue.
Any help appreciated.

Thanks. I did submit a report at the site. I hope somebody reads it as this is a big problem for us.
Thanks again.

Creative Cloud stays on white screen, not loading to show apps

everytime I open my creative cloud, it opens up to the window with a white screen. It was working a while ago but i can't seem to find out why it is doing this. Just wondering if anyone has either had the same problem and fixed it or knows how to fix it.
Thanks

BLANK Cloud Screen http://forums.adobe.com/message/5484303 may help
-and step by step http://forums.adobe.com/thread/1440508?tstart=0
-and http://helpx.adobe.com/creative-cloud/kb/blank-white-screen-ccp.html

When I bring up my Mozillafirefox, all I get is a window with a blank white screen. (I 'reinstalled' Firefox 3.66 about a month and a half ago, (and lost all my bookmarks as a result therein), and hope I can get my firefox back this time without having t

When I bring up my Mozillafirefox, all I get is a window with a blank white screen, (and the firefox logo). (After using Firefox very happily for over a year, I had to 'reinstall' Firefox 3.66 about a month and a half ago, (and lost all my bookmarks as a result therein), and hope I can get my firefox back this time without having to reinstall. Mozilla Firefox is still listed as one of my active programs). HELP! Is there a way to get my firefox back without reinstalling? Many thanks!
== This happened ==
Every time Firefox opened
== June 30, 2010 ==
== User Agent ==
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727)

same problem. wtf. just happened one day when i went to use it. nothing out of the ordinary installed either....

[Solved] White screen after KDE 4.11.1 upgrade

Hi!
I updated the system going from KDE 4.11.0 to KDE 4.11.1. On reboot I got the correct loading of KDM, but upon arrival on the desktop the latter is presented fully white with big red button with an "X" in them. Thinking it was the configuration of kde, I deleted .kde4 with the effect that the next time I always white screen (that is only the red buttons have disappeared).
I try to remove completely kde with:
pacman -Rsnc kde
and seeing that reinstalling I get the same result, I also tried to clean up the cache pacman packages listed by the command:
ls kde*4.11.1*
so I redownload and reinstalled with:
pacman -Syu kde
without solution. I also tried to do what is recommended in the wiki, that is in addition to eliminating .kde4, I run:
$ rm ~/.config/Trolltech.conf
$ kbuildsycoca4 --noincremental
without solution.
Thinking then it might be the partition / almost full, I checked with:
df
but the partition is not filled even for half of the 30gb that is available.
I checked some logs and these are the outputs:
.xsession-errors
> http://pastebin.com/GESX81PV
boot.log
[[32m OK [0m] Started Load Kernel Modules.
Mounting Configuration File System...
[[32m OK [0m] Mounted Configuration File System.
[[32m OK [0m] Found device SAMSUNG_SSD_830_Series.
Mounting /Windows...
Mounting FUSE Control File System...
[[32m OK [0m] Mounted FUSE Control File System.
[[32m OK [0m] Mounted /Windows.
[[32m OK [0m] Found device WDC_WD10EALX-009BA0.
Mounting /Dati...
[[32m OK [0m] Mounted /Dati.
[[32m OK [0m] Reached target Local File Systems.
Starting Trigger Flushing of Journal to Persistent Storage...
Starting Recreate Volatile Files and Directories...
Starting Tell Plymouth To Write Out Runtime Data...
[[32m OK [0m] Reached target Bluetooth.
[[32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage.
[[32m OK [0m] Started Recreate Volatile Files and Directories.
Starting Update UTMP about System Reboot/Shutdown...
[[32m OK [0m] Started Update UTMP about System Reboot/Shutdown.
[[32m OK [0m] Started Show Plymouth Boot Screen.
[[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data.
[[32m OK [0m] Reached target System Initialization.
[[32m OK [0m] Listening on CUPS Printing Service Sockets.
[[32m OK [0m] Reached target Paths.
[[32m OK [0m] Listening on D-Bus System Message Bus Socket.
[[32m OK [0m] Reached target Sockets.
[[32m OK [0m] Reached target Timers.
Starting Restore Sound Card State...
[[32m OK [0m] Reached target Basic System.
Starting Network Manager...
Starting CUPS Printing Service...
[[32m OK [0m] Started CUPS Printing Service.
Starting Catalyst's fglrx kernel' module builder...
Starting Login Service...
Starting D-Bus System Message Bus...
[[32m OK [0m] Started D-Bus System Message Bus.
Starting Permit User Sessions...
[[32m OK [0m] Started Permit User Sessions.
Starting Wait for Plymouth Boot Screen to Quit...
Starting K Display Manager...
[[32m OK [0m] Started K Display Manager.
[[32m OK [0m] Started Catalyst's fglrx kernel' module builder.
[[32m OK [0m] Reached target Sound Card.
[[32m OK [0m] Started Restore Sound Card State.
[[32m OK [0m] Started Login Service.
Starting Manage, Install and Generate Color Profiles...
Starting Authorization Manager...
[[32m OK [0m] Started Manage, Install and Generate Color Profiles.
[[32m OK [0m] Started Authorization Manager.
[[32m OK [0m] Started Network Manager.
[[32m OK [0m] Reached target Network.
Starting Network Time Service...
[[32m OK [0m] Started Network Time Service.
[[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[[1;31m*[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[[31m*[1;31m*[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[ [31m*[1;31m*[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[ [31m*[1;31m*[0m[31m* [0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K Starting Daemon for power management...
[[32m OK [0m] Started Daemon for power management.
Starting Disk Manager...
[[32m OK [0m] Started Disk Manager.
[ [31m*[1;31m*[0m[31m*[0m] A start job is running for Wait for Plymouth Boot Screen to Quit
[K[[1;31mFAILED[0m] Failed to start Wait for Plymouth Boot Screen to Quit.
See 'systemctl status plymouth-quit-wait.service' for details.
Starting Getty on tty1...
[[32m OK [0m] Started Getty on tty1.
[[32m OK [0m] Reached target Login Prompts.
[[32m OK [0m] Reached target Multi-User System.
[[32m OK [0m] Reached target Graphical Interface.
[[32m OK [0m] Stopped target Sound Card.
[[32m OK [0m] Stopped target Bluetooth.
Stopping Disk Manager...
Stopping Daemon for power management...
Stopping Authorization Manager...
Stopping Manage, Install and Generate Color Profiles...
Stopping CUPS Printing Service...
[[32m OK [0m] Stopped target Graphical Interface.
[[32m OK [0m] Stopped target Multi-User System.
Stopping Network Time Service...
Stopping Catalyst's fglrx kernel' module builder...
Stopping Login Service...
Stopping D-Bus System Message Bus...
[[32m OK [0m] Stopped target Login Prompts.
Stopping Getty on tty1...
Stopping K Display Manager...
[[32m OK [0m] Stopped K Display Manager.
[[32m OK [0m] Stopped Daemon for power management.
[[32m OK [0m] Stopped Getty on tty1.
[[32m OK [0m] Stopped D-Bus System Message Bus.
[[32m OK [0m] Stopped Disk Manager.
Stopping Permit User Sessions...
[[32m OK [0m] Stopped Authorization Manager.
[[32m OK [0m] Stopped Network Time Service.
[[32m OK [0m] Stopped target Network.
Stopping Network Manager...
[[32m OK [0m] Stopped Manage, Install and Generate Color Profiles.
[[32m OK [0m] Stopped Catalyst's fglrx kernel' module builder.
[[32m OK [0m] Stopped Login Service.
[[32m OK [0m] Stopped Network Manager.
[[32m OK [0m] Stopped CUPS Printing Service.
[[32m OK [0m] Stopped Permit User Sessions.
[[32m OK [0m] Stopped target Basic System.
[[32m OK [0m] Stopped target Paths.
[[32m OK [0m] Stopped target Timers.
[[32m OK [0m] Stopped target Sockets.
[[32m OK [0m] Closed CUPS Printing Service Sockets.
[[32m OK [0m] Closed LVM2 metadata daemon socket.
[[32m OK [0m] Closed /dev/initctl Compatibility Named Pipe.
[[32m OK [0m] Closed Delayed Shutdown Socket.
[[32m OK [0m] Closed Device-mapper event daemon FIFOs.
[[32m OK [0m] Closed udev Control Socket.
[[32m OK [0m] Closed D-Bus System Message Bus Socket.
[[32m OK [0m] Stopped target System Initialization.
Unmounting Debug File System...
Unmounting FUSE Control File System...
Stopping Update UTMP about System Reboot/Shutdown...
Unmounting POSIX Message Queue File System...
Unmounting Huge Pages File System...
Stopping Setup Virtual Console...
[[32m OK [0m] Stopped Setup Virtual Console.
[[32m OK [0m] Unset automount Arbitrary Executable File Formats File System Automount Point.
Stopping Apply Kernel Variables...
[[32m OK [0m] Stopped Apply Kernel Variables.
Unmounting Configuration File System...
[[32m OK [0m] Stopped target Encrypted Volumes.
[[32m OK [0m] Stopped target Swap.
[[32m OK [0m] Stopped target Local File Systems.
Unmounting /Windows...
Unmounting /Dati...
Unmounting Temporary Directory...
Stopping Journal Service...
[[32m OK [0m] Stopped target Remote File Systems.
[[32m OK [0m] Stopped Update UTMP about System Reboot/Shutdown.
[[32m OK [0m] Unmounted Temporary Directory.
[[32m OK [0m] Unmounted POSIX Message Queue File System.
[[32m OK [0m] Unmounted FUSE Control File System.
[[32m OK [0m] Unmounted Huge Pages File System.
[[32m OK [0m] Unmounted Configuration File System.
Stopping Load Kernel Modules...
[[32m OK [0m] Stopped Load Kernel Modules.
[[32m OK [0m] Unmounted Debug File System.
[[32m OK [0m] Unmounted /Windows.
[[32m OK [0m] Unmounted /Dati.
[[32m OK [0m] Reached target Unmount All Filesystems.
[[32m OK [0m] Stopped target Local File Systems (Pre).
Stopping Remount Root and Kernel File Systems...
[[32m OK [0m] Stopped Remount Root and Kernel File Systems.
[[32m OK [0m] Stopped Journal Service.
[[32m OK [0m] Closed Journal Socket.
Starting Show Plymouth Reboot Screen...
Starting Store Sound Card State...
Unmounting /...
[[32m OK [0m] Started Store Sound Card State.
[[32m OK [0m] Reached target Shutdown.
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Hardware watchdog 'iTCO_wdt', version 0
Unmounting file systems.
All filesystems unmounted.
Deactivating swaps.
All swaps deactivated.
Detaching loop devices.
All loop devices detached.
Detaching DM devices.
All DM devices detached.
Storage is finalized.
dmesg
> http://pastebin.com/fbgh2ayu
journalctl -p 3 --since=today
-- Logs begin at mar 2013-07-30 13:16:10 CEST, end at lun 2013-09-16 08:52:14 CEST. --
set 16 08:43:14 arch dhcpcd[346]: eno1: ipv6rs_sendprobe: sendmsg: Cannot assign requested address
set 16 08:43:14 arch ntpd_intres[338]: host name not found: 0.pool.ntp.org
set 16 08:43:14 arch ntpd_intres[338]: host name not found: 1.pool.ntp.org
set 16 08:43:14 arch ntpd_intres[338]: host name not found: 2.pool.ntp.org
set 16 08:43:14 arch ntpd_intres[338]: host name not found: 3.pool.ntp.org
set 16 08:43:18 arch ntpd_intres[338]: host name not found: 0.pool.ntp.org
set 16 08:43:18 arch ntpd_intres[338]: host name not found: 1.pool.ntp.org
set 16 08:43:18 arch ntpd_intres[338]: host name not found: 2.pool.ntp.org
set 16 08:43:18 arch ntpd_intres[338]: host name not found: 3.pool.ntp.org
set 16 08:45:03 arch login[308]: pam_systemd(login:session): Failed to connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
set 16 08:45:04 arch kdm[351]: :0[351]: pam_systemd(kde:session): Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
set 16 08:45:04 arch kdm[351]: :0[351]: pam_close_session() failed: Cannot make/remove an entry for the specified session
set 16 08:45:04 arch systemd-coredump[1103]: Process 309 (X) dumped core.
[1;39m-- Reboot --[0m
set 16 08:46:11 arch dhcpcd[346]: eno1: ipv6rs_sendprobe: sendmsg: Cannot assign requested address
set 16 08:46:12 arch ntpd_intres[337]: host name not found: 0.pool.ntp.org
set 16 08:46:12 arch ntpd_intres[337]: host name not found: 1.pool.ntp.org
set 16 08:46:12 arch ntpd_intres[337]: host name not found: 2.pool.ntp.org
set 16 08:46:12 arch ntpd_intres[337]: host name not found: 3.pool.ntp.org
set 16 08:46:16 arch ntpd_intres[337]: host name not found: 0.pool.ntp.org
set 16 08:46:16 arch ntpd_intres[337]: host name not found: 1.pool.ntp.org
set 16 08:46:16 arch ntpd_intres[337]: host name not found: 2.pool.ntp.org
set 16 08:46:16 arch ntpd_intres[337]: host name not found: 3.pool.ntp.org
set 16 08:48:02 arch login[305]: pam_tally(login:auth): pam_get_uid; no such user
kdm.log
> http://pastebin.com/zmgj4AGq
Xorg.0.log has no errors.
How can I resolve it?
Thanks
Last edited by Fregtux (2013-09-20 08:35:13)

Fregtux wrote:
Thanks Thaodan! I deleted /var/tmp/kdecache-$USER and I solve the problem! I also restore .kde4_backup and at the moment have no issue.
Small question: I noticed that there are also kdecache-kdm and kdecache-root. I should remove it or doesn't matter?
Thanks for the help!
THANKS, my White Screen was caused by a combination of issues but this solution worked for me.
My Problem -
I am not sure exactly what caused my white screen, I was playing around with /etc/profile & /etc/sudoers
What I changed -
sudoers - I added my user group to sudoers and allowed sudo to execute applications using xauth in home dir
profile - changed umask to 133 ( I hate execute bit ) and default text editor to nano
What Happened -
Tried to reload via source but no changes where taking effect so I rebooted.
Upon reboot I could not login to KDE, it would keep looping back to the KDM after I entered by password for my user, however it would let me login as root ( after I enabled root login ).
I figured this was a permission issue so I changed umask back to 022 in /etc/profile, I was then greeted with the White Screen after login. I read numerous posts about how to fix this, most said to reinstall kde and delete /tmp, none of this worked.
I deleted /var/tmp/kdecache-$USER and now I am back in business ( I had to re set the widgets, i.e. panel ).
I was so excited that I had to write a post about it!
Thanks again!

Adobe Windows Fireworks CS5 opens to white screen

I had Adobe Creative Suite 5 Design Premium installed and working fine for over a year. All of a sudden today when I click the icon to open Fireworks it opens to a blank screen "white".
I can see my icons for Windows 7 at the bottom but nothing but a white screen. It appears Dreamweaver is doing the same. I tried uninstalling FW and re-install and the problem
continues. Help

I checked the above article and it wasn't relevant to the problem stated at the beginning of this article, first off that person was using an iPad (there is no blue icon on the right side of the browser window on a computer) and 2nd, what is needed is preventing small images opening in full screen mode instead of the image loading in screen the same size as the image. The above article shows how to get in and out of full screen mode but that doesn't address the issue in the original post because the image is still placed on a too large screen. When the image is only 3x2 inches you don't need the page opening as large as a full size screen on a 27" monitor. When that happens you have to click on the tiny, miniscule, hardly attainable 1 pixel spot at the lower right corner of the screen and resize the page manually so it doesn't take up the whole screen so you can see the other documents. when you are opening multiple images this is very annoying.
I have trouble believing that Adobe techs haven't found a solution to this issue since Sept 2011 when the first post on this issue was posted above.

[solved] maximizing window results in white screen

Similar Messages

Maybe you are looking for