On Tue, Aug 28, 2007 at 07:42:40PM +0200, Alban Browaeys wrote:
> Package: menu-xdg
> Version: 0.2.3
> Followup-For: Bug #439427
> 
> 
> A previous run created incorrect files in /var/lib/menu-xdg instead of the 
> directory 
> (see attached archive). This leads to this error while running 
> dpkg-reconfigure menu or menu-xdg.
> 
> Execution of /usr/share/menu/cdd-menu generated no output or returned an 
> error.
> Unknown error, message=Could not create directory(menu-xdg): File exists
> install-menu: /etc/menu-methods/xdg-desktop-entry-spec-dirs: aborting
> update-menus[7314]: Script /etc/menu-methods/xdg-desktop-entry-spec-dirs 
> returned error status 1.
> Unknown error, message=Could not create directory(menu-xdg): File exists
> install-menu: /etc/menu-methods/xdg-desktop-entry-spec-apps: aborting
> update-menus[7314]: Script /etc/menu-methods/xdg-desktop-entry-spec-apps 
> returned error status 1.
> Unknown error, message=Could not create directory(xsessions/): File exists
> install-menu: /etc/menu-methods/xdg-desktop-entry-spec-sessions: aborting
> update-menus[7314]: Script /etc/menu-methods/xdg-desktop-entry-spec-sessions 
> returned error status 1.
> 
> 
> This produces unusable debian menus .
> It looks like 
> http://www.yepthatsme.com/2005/10/12/if-your-debian-menu-in-gnome-ever-disappears/
>  .
> I fixed it via rm -Rf /var/lib/menu-xdg/* plus dpkg-reconfigure menu-xdg.
> 
> I wonder if it is a problem that can be fixed in the package or menu-method 
> (by checking if those 
> are files instead of directories and deleting them if so).

This is possible to do, but I would be very much interested to know
how /var/lib/menu-xdg/xsessions ended being a file instead of a
directory. I checked carefully and update-menus cannot do that.
Especially the content of /var/lib/menu-xdg/xsessions is strange.
What filesystem are you using ?

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to