Awn

KWin4.2: dock hint not honored when autohide enabled

Bug #359986 reported by chepioq
2
Affects Status Importance Assigned to Milestone
Awn
Fix Released
Medium
Unassigned

Bug Description

I use fedora10, kde 4.2.2 with desktop effect enable and avant-window-navigator.
When I use awn with no auto hide option, awn is on my four desktop,
But when I enable auto hide option in setting of awn, I have just awn on my first desktop, and not on the three other.
I feel this on the bugzilla of kde, but the respond is:
"avant-window-navigator is not a KDE application.
Please report the problem to its developers."

Do you think it is an awn bug?

Tags: autohide kde
Revision history for this message
Mark Lee (malept) wrote :

IMO, I don't think this is an Awn bug. But just in case, which version of Awn is this? I presume that KWin (and not compiz) is the window manager?

summary: - awn is not on all desktop when autohide
+ KWin4.2: dock hint not honored when autohide enabled
Changed in awn:
status: New → Incomplete
tags: added: autohide kde
Revision history for this message
chepioq (chepioq) wrote :

Thank Mark Lee for your answer.
My version of awn is "avant-window-navigator-0.3.2-5.fc10" and my windows manager is KWin.
You say that it is not an awn bug, and I post this bug on kde bugzilla, ( https://bugs.kde.org/show_bug.cgi?id=189434 )
ant they say the same thing: it is not an kde bug...
Where is the problem?...
I think you should discuss this problem with kde developers.

Revision history for this message
moonbeam (rcryderman) wrote :

chepioq,

What are the settings selected/unselected in the first tab visible when opening awn-manager? Most interested in the 4 checkboxes. When you check these values please try testing awn with both possible settings for keep-below.

I've reviewed the relevant code in awn trunk and can confirm that it is quite pigheaded about maintaining its status as sticky.

Thanks,

Revision history for this message
chepioq (chepioq) wrote :

hi moonbeam
I am a french man and my awn is also in french, but my english is bad.
I send you a snapshot of the first tab: http://pix.toile-libre.org/upload/original/1239682734.png
I tested the different setting for same results.
I observed one thing:
-when I check "Garder sous les fenêtres maximisées si le dock est inutilisé", auto hide don't work.
-when I unchecked "Garder sous les fenêtres maximisées si le dock est inutilisé", then "Masquer automatiquement la barre lorsqu'elle n'est pas utilisée" is automatically unchecked.

Revision history for this message
moonbeam (rcryderman) wrote :

I've set up a VM with Kubuntu Jaunty prelease to test what is happening.

Qt: 4.5.0
KDE: 4.2.2 (KDE 4.2.2)
KWin: 4.2.2 (KDE 4.2.2)

What I am seeing is that the sticky hint is set and it is being honoured by kwin. However, for whatever reason unhide is _not_ triggered when moving the mouse to the bottom on the screen on anything other than the first workspace.

chepioq, could you please try the following: make sure that awn is visible then _quickly_ change workspaces before awn autohides. I expect you will see awn on the the other workspace.

If this is confirmed to be the Fedora behaviour also, then I'm inclined to target a fix for this for 0.4 given the horribly, inherently broken, nature of awn autohide in the 0.3.x and lower releases. If it turns out to be some issue with the sticky hint then it probably should be pursued sooner.

Revision history for this message
chepioq (chepioq) wrote : Re: [Bug 359986] Re: KWin4.2: dock hint not honored when autohide enabled

Hi moonbean,
I have already test that you want I test:
When I quickly change my desktop before awn is hidden, I have awn on my all
desktop but when I pass my mouse on awn, it is hidden but don't re-appear,
except on first desktop.
For test I install cairo dock (but I prefer awn...), and when cairo-dock is
auto-hide, it is visible on all desktop...
I don't know if that help you...
Amicalement
Dominique

2009/4/18 moonbeam <email address hidden>

> I've set up a VM with Kubuntu Jaunty prelease to test what is happening.
>
> Qt: 4.5.0
> KDE: 4.2.2 (KDE 4.2.2)
> KWin: 4.2.2 (KDE 4.2.2)
>
> What I am seeing is that the sticky hint is set and it is being honoured
> by kwin. However, for whatever reason unhide is _not_ triggered when
> moving the mouse to the bottom on the screen on anything other than the
> first workspace.
>
> chepioq, could you please try the following: make sure that awn is
> visible then _quickly_ change workspaces before awn autohides. I expect
> you will see awn on the the other workspace.
>
> If this is confirmed to be the Fedora behaviour also, then I'm inclined
> to target a fix for this for 0.4 given the horribly, inherently broken,
> nature of awn autohide in the 0.3.x and lower releases. If it turns out
> to be some issue with the sticky hint then it probably should be pursued
> sooner.
>

Revision history for this message
chepioq (chepioq) wrote :

I have already test that you want I test:
When I quickly change my desktop before awn is hidden, I have awn on my all desktop but when I pass my mouse on awn, it is hidden but don't re-appear, except on first desktop.
For test I install cairo dock (but I prefer awn...), and when cairo-dock is auto-hide, it is visible on all desktop...
I don't know if that help you...
Amicalement
Dominique

Revision history for this message
moonbeam (rcryderman) wrote :

I'm expecting this should be resolved with the 0.4 release. I'll verify rewrite has resolved the issue on KDE when I have an opportunity.

Changed in awn:
importance: Undecided → Medium
milestone: none → 0.4.0
status: Incomplete → Confirmed
Revision history for this message
chepioq (chepioq) wrote :

Hi
Where can-I download the 0.4 version? (source or rpm)
If I can I install it and test for you.

Revision history for this message
chepioq (chepioq) wrote :

A little up...
I would like tested awn 0.4, but I don't know where I can get the source...
I search with google but I don't find.
Where I can download it?

Revision history for this message
moonbeam (rcryderman) wrote :

https://code.launchpad.net/~awn-core/awn/trunk-rewrite-and-random-breakage

and extras is

https://code.launchpad.net/~awn-extras/awn-extras/extras-trunk-rewrite-and-random-breakage

You will also need to install libdesktop-agnostic in addition to a lot of the standard awn dev packages.

https://code.launchpad.net/~malept/awn/0.4-libdesktop-agnostic

This is not for the faint of heart. If you have any build related questions I'd suggest posting them on http://awn.planetblur.org/ or drop by #awn on freenode.

Revision history for this message
chepioq (chepioq) wrote :

Thank for the link, but I can't download the 0.4-libdesktop-agnostic, I have these error message:

[dominique@Dominique ~]$ bzr branch lp:~malept/awn/0.4-libdesktop-agnostic
You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data. See "bzr help launchpad-login".
bzr: ERROR: Unknown branch format: 'Bazaar-NG Loom branch format 7\n'
[dominique@Dominique ~]$

Revision history for this message
moonbeam (rcryderman) wrote :

from the libdesktop-agnostic link.

Repository format: Packs 6 (uses btree indexes, requires bzr 1.9)

I'm guessing you probably have an earlier version.

Revision history for this message
moonbeam (rcryderman) wrote :

correction for libdesktop agnostic you need to

bzr branch lp:libdesktop-agnostic

lp:libdesktop-agnostic is an awn/lda integration branch that you should not try to install.

Revision history for this message
moonbeam (rcryderman) wrote :

correction again. for some reason I cannot copy and paste today.

lp:~malept/awn/0.4-libdesktop-agnostic is an awn/lda integration branch that you should not try to install.

Sorry for the spam

Revision history for this message
chepioq (chepioq) wrote :

OK...
The ./configure don't work with trunk-rewrite-and-random-breakage and extras-trunk-rewrite-and-random-breakage.the error message is:

[dominique@Dominique trunk-rewrite-and-random-breakage]$ ./configurebash: ./configure: Aucun fichier ou dossier de ce type
[dominique@Dominique trunk-rewrite-and-random-breakage]$

I have already compiled another source for other programs...
I think I'll wait for the official release of awn 0.4

Revision history for this message
Michal Hruby (mhr3) wrote :

Could you test this with our latest Awn-testing packages, please?
http://wiki.awn-project.org/DistributionGuides#Testing_Package_Archive

Revision history for this message
chepioq (chepioq) wrote :

I don't understand what I do with your link...
I am not with ubuntu, but with fedora (F11)...
Please give a link with the source of your revision, and I can compile it.

Revision history for this message
Michal Hruby (mhr3) wrote :

You can find the sources in lp:awn/0.4

Revision history for this message
chepioq (chepioq) wrote :

Ok...
I download the source, but that don't work for me...
When I try ./configure, I have this error message:
No package 'desktop-agnostic' found

I get the source of 'desktop-agnostic' but when I lauch ./configure for this I have this error:
No package 'libwnck-1.0' found

With Fedora the version of libwnck is libwnck-2.26....

Revision history for this message
Michal Hruby (mhr3) wrote :

You need the -devel package...

Changed in awn:
status: Confirmed → Incomplete
Revision history for this message
chepioq (chepioq) wrote :

Ok, I install the -devel package and ./configure for 'desktop-agnostic' work.
But I have errors with "make":

awn-vfs.c -fPIC -DPIC -o .libs/awn-vfs.o
Dans le fichier inclus à partir de awn-vfs.c:39:
/usr/include/gnome-vfs-module-2.0/libgnomevfs/gnome-vfs-module-shared.h:30:2: erreur: #error configuration macros set inconsistently, gnome_vfs_stat_to_file_info will malfunction
make[4]: *** [awn-vfs.lo] Erreur 1
make[4]: quittant le répertoire « /home/dominique/0.4/desktop-agnostic/libawn »
make[3]: *** [all-recursive] Erreur 1
make[3]: quittant le répertoire « /home/dominique/0.4/desktop-agnostic/libawn »
make[2]: *** [all] Erreur 2
make[2]: quittant le répertoire « /home/dominique/0.4/desktop-agnostic/libawn »
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le répertoire « /home/dominique/0.4/desktop-agnostic »
make: *** [all] Erreur 2
[dominique@33 desktop-agnostic]$

Revision history for this message
Michal Hruby (mhr3) wrote :

There is no awn-vfs.c in 0.4 branch, what are you compiling exactly?

Revision history for this message
chepioq (chepioq) wrote :

I compile the branch I have downloded by this command:

bzr branch lp:awn/0.4

And for "desktop agnostic:

bzr branch lp:~malept/awn/desktop-agnostic

Revision history for this message
Michal Hruby (mhr3) wrote :

Libdesktop-agnostic is at lp:libdesktop-agnostic

Revision history for this message
chepioq (chepioq) wrote :

Ok....
I try compiling libdesktop-agnostic, and after more test (I have not all dependencies), I configure with (I see that in install.rst) :

./waf configure --config-backends=[cfg] --vfs-backends=[vfs] --desktop-entry-backends=[de]

That work, but after I must do ./waf and I have this error message:

dominique@33 libdesktop-agnostic]$ ./waf
Waf: Entering directory `/home/dominique/libdesktop-agnostic/build'
Waf: Leaving directory `/home/dominique/libdesktop-agnostic/build'
source not found: 'config-impl-[cfg].vala' in 'dir:///home/dominique/libdesktop-agnostic/libdesktop-agnostic'

I stop my tests here, and I think that I'll wait for a future Fedora package...
Sorry for the inconvenience.

Revision history for this message
Mark Lee (malept) wrote :

in docs/install.rst of libdesktop-agnostic:

> The placeholders (specified by the ``[bracketed]`` identifiers) should be
> replaced by a comma-separated list of backends. A list of valid backends
> follows:

[there is a list here which I chose not to copy/paste]

Revision history for this message
chepioq (chepioq) wrote :

I don't understand what you say (my English is so bad....)
Where I do replaced this list of backends ?

Revision history for this message
Michal Hruby (mhr3) wrote :

You need to replace the [values] with specific backends you want. For example I use `./waf configure --config-backends=gconf --vfs-backends=gio --desktop-entry-backends=glib`

Revision history for this message
Michal Hruby (mhr3) wrote :

This should be fixed in Awn 0.4, if you still experience the issue, please reopen by setting status to "New".

Changed in awn:
status: Incomplete → Fix Committed
Mark Lee (malept)
Changed in awn:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.