xfce4-panel doesn't check desktop files

I assume you mean that it uses the .desktop files to list the available plugins. As soon as you install a new one, and open the "Add Item" window, you should see it in the list. I just tested this on the same version without problems.
1. Run "sudo apt-get install xfce4-genmon-plugin"
2. Right-click on the panel, select "Add Item".
3. "Generic monitor" is listed.

Can you test this? And if it doesn't work, can you check with a new user account to see if the problem is your configuration?

On 3/22/06, Andrew Conkling <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35857
>
> Task: ubuntu xfce4-panel
> Severity: Critical => Normal
> Status: Unconfirmed => Needs Info
>
> Comment:
> I assume you mean that it uses the .desktop files to list the available plugins. As soon as you install a new one, and open the "Add Item" window, you should see it in the list. I just tested this on the same version without problems.
> 1. Run "sudo apt-get install xfce4-genmon-plugin"
> 2. Right-click on the panel, select "Add Item".
> 3. "Generic monitor" is listed.
>
> Can you test this? And if it doesn't work, can you check with a new user account to see if the problem is your configuration?
>

i found what was the problem, i had a swp file in the plugin folder
... the panel while loading and reading desktop files doesn't check
the extension, and it stops to scan if there is a corrupted file.

I guess this should be fixed by xfce4 devels

OK, good. How did the swp file get there? Was it installed by a rogue package, or maybe a plugin that you compiled yourself?

On 3/22/06, Andrew Conkling <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35857
>
> Comment:
> OK, good. How did the swp file get there? Was it installed by a rogue
> package, or maybe a plugin that you compiled yourself?
>
plugins can go even in $HOME/.local, that's where i have the desktop
file of a plugin i'm coding. So mainly this is an issue that you can
see just if you edit those files ... not common ... but i guess it
should be fixed anyway.

This is fixed (i.e. committed) upstream. Now what do we do to get this package fixed in Ubuntu? Do we need a UVF exception? A new bug?

This was confirmed and fixed upstream. Now we just need to release a later version of xfce4-panel in Ubuntu.

I don't want to spam with too frequent package updates so this will
wait until more fixes accumulate upstream, since this is not at all critical :)

On 3/23/06, Jani Monoses <email address hidden> wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/35857
>
> Comment:
> I don't want to spam with too frequent package updates so this will
> wait until more fixes accumulate upstream, since this is not at all critical :)
>

well .. that's true it 's not at all critical .. i'm sorry if i set it
so at the beginning but it was a strange coincidence with an upgrade
:)

It was not a hint at prio being set to critical (I did not even notice that) I only stated the general rule which is applied to most xfce svn stuff. So once at least a few bugs accumulate or something resembling a feature that needs testing is added upstream I upload but not earlier.

uploaded new svn snapshot