I'm using Ubuntu 13.04 with XFCE 4.10 from Ubuntu's sources, installed manually (i.e. not xubuntu-desktop) on my laptop that has an external screen attached. The big external monitor also has a vertical panel. My external screen is on the right side of my laptop.

When I maximize windows on my external monitor, the panel overlaps those. However, when I maximize windows on my smaller laptop monitor, there seems to be the panel's width reserved in space (which is just empty)

How can I make it reserve space on the right monitor?

My setup looks like this (generated with arandr and modified (right-of and primary are by me, trying to solve the problem):

#!/bin/sh
xrandr --output HDMI1 --primary --right-of LVDS1 --mode 1920x1080 --pos 1440x0 --rotate normal \
--output LVDS1 --mode 1440x900 --pos 0x368 --rotate normal \
--output TV1 --off --output VGA1 --off

I'm using xfce with arch linux on an Asus Zenbook Prime (UX21A) and noticed that by upgrading from xfce4-power-manager-1.2.0-3-x86_64 to
xfce4-power-manager-1.2.0-4-x86_64 a faulty setting is introduced: whenever the screen returns from a blankd out state the program xfpm-power-backlight-helper sets screen backlight to max; here is the journalctl output:

archlinux pkexec[1939]:: Executing command [USER=root] [TTY=unknown] [CWD=/] [COMMAND=/usr/bin/xfpm-power-backlight-helper --set-brightness 10]

This is annoying because you have to readjust backlight every time manually.

Can anyone shed some light on this? Where can I configure these settings?

Thanks.

Antis

However, enabling this option when using full screened windows produces an odd looking shadow behind my top panel (I'm running dual panels, gnome2 style. top panel is semitransparent.).

I'd like a way to customize the shadow behavior so it acts like "hide frame of windows when maximized" in the accessibility tab in the window manager tweaks panel, where I could "hide shadows of windows when maximized".

If this isn't configurable via xconf or similar, should I add an enhancement request?

Thanks for the help!

I don't know whether the behavior you are experiencing has to do with an incorrect setting (if it does, it is not one that appears in (my version of) the Window Buttons preferences), a component that your installation is missing, a misconfiguration somewhere else that is affecting this, or if it is because you have an older version of Xfce. I just looked at the Xfce page of the Debian Wiki and it looks like Wheezy and Sid both use the older 4.8 version of Xfce and only Experimental uses 4.10, which is more or less the current one. I confess that I do not know the reasons for keeping what has always been, for me, a rock-solid version of Xfce in the "Experimental" version of Debian, but as I do not use that distro, I lack knowledge that others may have. (I use computers that at and approaching ten years old, and have installed a distro with Xfce 4.10 on friends' brand-new computers - none have shown issues - so I don't see how it can be that they are doing it because of compatibility concerns with old - or the newest - computers. Maybe it is a case of keeping older versions of desktop environments to guarantee compatibility with... all the other things that they only have old versions of, lol? IDK, honestly, but if "Experimental" only has "current," where does a Debian user go when he/she truly wishes to experiment? Are there things like the PPAs that users of Ubuntu and Ubuntu-derived distros can add, such as the Xfce 4.12 PPA (which has also been solid and stable, with only one very minor bug which was fixed a day or so later in an update) that I added to Mint 14 Xfce?

I am afraid that I do not know an easy way to find exactly which version of the Window Buttons applet that I have installed. If someone is nice enough to post a way, I will check. Perhaps that would help you troubleshoot your system (by reading release notes for the versions after yours and up to mine, to see if this behavior was mentioned as a fixed bug?).

Best of luck,
MDM

I wanted to share the solution that works for me. When I have two keyboard layouts installed (LT and RU) then keyboard shortcuts like CTRL+Letter and ALT+Letter stop working in KDE applications only (Krusader, Kate, etc.). Keyboard shortcuts like CTRL+. or CTRL+F1 or ALT+F4 are working fine. When I remove RU keyboard layout then all shortcuts work in KDE applications just fine.

By the way only KDE applications are affected. Gnome and XFCE applications are working fine all the time.

My solution was to remove RU keyboard layout.

Is this a bug/feature?
Does one have some suggestions on howto get it right?

I had/have the same problem here.
I use:

own_window yes
own_window_transparent yes
own_window_type override

The feh tricks works for me, but it also fixes if I open the dektop parameter window (right click on the desktop) ...

By the way,  if you want to put the "feh trick" in your conky startup script, you might want to query which image is used for your background (not to change your script each time you change your background), then use this:
xfconf-query -c xfce4-desktop -p /backdrop/screen0/monitor0/image-path

for example: feh --bg-center `xfconf-query -c xfce4-desktop -p /backdrop/screen0/monitor0/image-path`

After a lot of try, your trick make my day  !
I think it's the only way to use conky with xfce 4.8 & wheezy
Thank you much

I just needed to adapt a little to make it work perfectly on my config

feh --bg-fill `xfconf-query -c xfce4-desktop -p /backdrop/screen0/monitor0/image-path`

http://git.xfce.org/xfce/xfce4-session/ … 30356b41f9.

There is a patch which fixed it for me:

http://git.xfce.org/xfce/xfce4-session/ … 30356b41f9.

Suspend and hibernate are still not working from action button item on my xfce panel. I also tried to run the command `pmi action suspend` and received the following:

Sorry, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/command-not-found/+filebug
Please include the following information with the report:

command-not-found version: 0.3
Python version: 3.3.1 final 0
Distributor ID:    Ubuntu
Description:    Ubuntu Saucy Salamander (development branch)
Release:    13.10
Codename:    saucy
Exception information:

unsupported locale setting
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/CommandNotFound/util.py", line 24, in crash_guard
callback()
File "/usr/lib/command-not-found", line 69, in main
enable_i18n()
File "/usr/lib/command-not-found", line 40, in enable_i18n
locale.setlocale(locale.LC_ALL, '')
File "/usr/lib/python3.3/locale.py", line 541, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting