Re: Problems with window placement on suse and fluxbox 0.9.12 and higher

Hi,

Is it still broken with a blank config?
mv .fluxbox .fluxbox.temp
(test running fluxbox)
mv .fluxbox .fluxbox.old &&
mv .fluxbox.temp .fluxbox &&
rm -rf .fluxbox.old

If it is NOT still broken, then please send your init and apps files, as 
I'd like to find out why.

If it is still broken... well, I've got no idea how that would happen in a 
normal X server.

Cheers,

  - Simon

On Sun, 18 Jun 2006, Thomas Bauer wrote:

> Hi all,
>
> I successfully run fluxbox 1.0rc on fedora FC4 and FC5 at home without
> problems.
> At work, however, we use suse. Until fluxbox 0.9.11, I had no problems,
> too. But I can't update to a higher version, because the window
> placement is somehow broken. Windows, e.g. an xterm, which I open with a
> keyboard shortcut, are all opened in the upper left corner of the screen
> (x=0, y=0), even if there is already a window there and plenty of free
> space e.g. in the upper right corner.
> I didn't report this so far because I thought it's because the suse
> version (9.1) is obsolete. But recently we had an update to 10.0, and
> window placement still doesn't work, even with fluxbox 1.0rc.
> I use self-compiled fluxbox binaries. I even once tried to configure it
> with the debug option, but could not get some useful information from
> the debug output why the window placement fails. Below is the output
> after opening a second new window (0.9.15).
> Any ideas what changed between 0.9.11 and 0.9.12 and can cause this
> problem? Any confirmations?
>
> Regards,
>
> Thomas
>
>
> Log File: /home/bauer/.fluxlog
> Fluxbox version: 0.9.15.1
> Compiled: May 18 2006 09:00:00
> Compiler: GCC
> Compiler version: 4.0.2 20050901 (prerelease) (SUSE Linux)
>
> Defaults:
>    menu: /home/bauer/nobackup/usr/share/fluxbox/menu
>   style: /home/bauer/nobackup/usr/share/fluxbox/styles/Clean
>    keys: /home/bauer/nobackup/usr/share/fluxbox/keys
>    init: /home/bauer/nobackup/usr/share/fluxbox/init
>
> Compiled options (- => disabled):.
> DEBUG
> SLIT
> TOOLBAR
> XPM
> -IMLIB2
> GNOME
> KDE
> EWMH
> REMEMBER
> SHAPE
> XFT
> XMB
> -XINERAMA
> RENDER
>
> ..
>
> MapRequest for 0x1c00020
> Window.cc: FluxboxWindow::init(this=0x8224ba8, client=1c00020, frame =
> c00574)
> updateTransientInfo: m_win = 0x8224ba8
> updateTransientInfo: window() = 0x1c00020Failed to read transient for hint.
> FluxboxWindow(bash)::setFocusFlag(0)
> FluxboxWindow(bash)::moveToLayer(8)
> 0x8224ba8 notify layer signal
> FluxboxWindow::init(bash) transientFor: 0
> IconbarTool::addWindow(0x0x8224ba8 title = bash)
> FluxboxWindow(bash)::setFocusFlag(0)
> Workspace.cc(290): Checking grouping. (bash)
> FluxboxWindow(bash)::raise()[layer=8]
> FluxboxWindow::mapNotifyEvent: ne.override_redirect = 0 isVisible() = 1
> FluxboxWindow::mapNotify: not override redirect ans visible!
> FluxboxWindow::setCurrentClient: labelbutton[client] = 0x821fd68
> FluxboxWindow::setInputFocus isModal() = 0
> FluxboxWindow::setInputFocus transient size = 0
> Window.cc(mapNotifyEvent) TODO check grouping here
> PropertyNotify(bash), property = _NET_WM_DESKTOP
> PropertyNotify(bash), property = _BLACKBOX_ATTRIBUTES
> PropertyNotify(bash), property = WM_STATE
> PropertyNotify(bash), property = _BLACKBOX_ATTRIBUTES
> PropertyNotify(bash), property = WM_STATE
> PropertyNotify(bash), property = _BLACKBOX_ATTRIBUTES
> ------------------
> Setting Focused window = 0
> Current Focused window = 0x8170af0
> ------------------
> FluxboxWindow(bauer)::setFocusFlag(0)
> ------------------
> Setting Focused window = 0x8223a08
> title: bash
> Current Focused window = 0
> ------------------
> FluxboxWindow::setCurrentClient: labelbutton[client] = 0x821fd68
> FluxboxWindow(bash)::setFocusFlag(1)
> PropertyNotify(bash), property = WM_ICON_NAME
> PropertyNotify(bauer), property = WM_NAME
>