roster dop not keep its place after being minimized

[szym]

If you want to see what I mean do the fallowing. Change position of your roster window. Close roster windowa and message window. Click the tray icon. Roster pops up. Everything ok so far. Close roster and wait for a message from someone. After reciving message click tray icon until roster pops up. Your roster probobly is now in the same place it was before you moved it. Annoying isnt it?

[misc]

Isn't it a problem with the windows manager ? What do you use, so we can try to reproduce ?

[asterix]

here it works as it should

[anonymous]

I am also experiencing this bug. I'm using IceWM 1.2.28.

Whenever the roster is minimised and I receive an event, such as somebody coming online, and I unminimise the roster, it gets moved to the top left of the screen.

[asterix]

I can't reproduce. it's probably due to your WM. someone else with this WM to confirm ?

[anonymous]

If it was purely down to the WM then every program would be doing it. Why don't you install IceWM and test for yourself?

[junglecow]

Closed #2844 as a duplicate of this bug

[dentharg@…]

I experience this behaviour too. Using KDE 3.5.5 on Gentoo (#2844 was mine). So it doesn't depend on WM. If you need any trackbacks or any other debug data just tell what you need.

[dentharg@…]

I'm using Gajim 0.11.

[nk]

src/roster_window.py

after line 3288 add:

print self.window.window.get_root_origin()

I bet GTK reports wrong stuff for your cases

[anonymous]

Also seeing this on Xfce 4.4.

[asterix]

can you still repro with the new systray behaviour ? I can't with XFCE4.4

[anonymous]

I still see this problem with the latest Gajim from svn and IceWM 1.2.30.

If it's any use, while using a small Python program I wrote that updates the status message with the currently playing music track every couple of seconds, every time I minimized and restored the roster it would be moved. Without it, I see this bug much less frequently.

[anonymous]

I'm using GNOME 2.22.2 and the latest Gajim from SVN and am still seeing this problem.

[anonymous]

I'm pretty sure this problem is restricted to using the tray icon and not minimising/restoring in general.

[Jim++]

See also #4016.

[sgala@…]

I saw those warnings in the window where I ran "metacity --replace" after unselecting "disable_workarounds" in gconf-editor for metacity:

Window Manager Warning: Buggy client sent a _NET_ACTIVE_WINDOW
 message with a timestamp of 0 for 0x1000151 (gajim - Ga)
Window Manager Warning: meta_window_activate called by a
 pager with a 0 timestamp; the pager needs to be fixed.

[asterix]

see #4337

[drguildo]

#2012 looks like a duplicate of this bug.

[drguildo]

This bug is still in the latest nightly snapshot (15/11/2008).

[anonymous]

These are the steps I use to reproduce the bug:

1. Move the roster to somewhere beside the bottom right of the screen.
2. Right click on the tray icon and choose "Quit".
3. Start Gajim. Roster should appear in the location you moved it before closing Gajim.
4. Move the roster to the bottom right of the screen and minimise it by clicking on the tray icon.
5. Send youself a message from another client e.g. using gajim-remote send_chat_message jid@… "test".
6. Click on the tray icon to restore the roster, it should have moved to the location you moved it to in step 1.

[asterix]

everything you describe work fine for me ... Which gajim version? which window manager?

After you quit (step 2) look at ~/.gajim/config, what are the values for roster_width, roster_height, roster_x-position, roster_y-position?

[anonymous]

Gajim 0.12-beta1 and metacity 2.24.0 (i.e. GNOME). The values in ~/.gajim/config after step 2 are exactly the expected ones (otherwise it wouldn't start in the correct location in step 3, would it?).

As for reproducing the bug, not even I can do that anymore seeing as none of the messages I send using gajim-remote ever turn up. Awesome.

[anonymous]

Replying to anonymous:

Gajim 0.12-beta1 and metacity 2.24.0 (i.e. GNOME). The values in ~/.gajim/config after step 2 are exactly the expected ones (otherwise it wouldn't start in the correct location in step 3, would it?).

I understood that in step3 roster was not at the correct place (because of the should)

As for reproducing the bug, not even I can do that anymore seeing as none of the messages I send using gajim-remote ever turn up. Awesome.

If nobody can reroduce it's hard to understand what happens :/

[anonymous]

I guess it doesn't really matter anyway. I'm almost certain the bug is due to your use of libegg for the status icon. I remember talking to some people in the conf a while ago about another bug in the libegg tray icon code and why you should switch to the officially supported GNOME tray icon and being told that it wasn't going to happen. That and the fact that libegg tray icon support seems to have been abandoned over 2 years ago[1] means this is highly unlikely to get fixed.

[1] http://mail.gnome.org/archives/desktop-devel-list/2006-April/msg00418.html

[asterix]

unfortunatly this gtk.StatusIcon? don't support all features of libegg.

that said, I don't see any reason why it would be related to the position of roste window.