CRITICAL **: egg_desktop_entries (ERRORS) [FIXED]

[Adam D]

Robert Wallace wrote:
> I was able to fix this problem by running doing the following commands:
> 
> cd /usr/share/applications
> sudo update-desktop-database -v
> 
> the last command should generate errors and the desktop entry with the
> problem will be the one after the error, edit the desktop file and you
> will have some duplicate entries like "[Desktop Entry]" and/or
> Encoding.
> 
> After fixing the files you should be able to run the
> update-desktop-database command again and all should be fine.
> 
> Hope this helps.
> 

That worked perfectly!!!!  Thanks.. 



> On 6/2/06, Adam D <emlists at gmail.com> wrote:
>> Adam D wrote:
>> > I have been receiving these errors
>> >
>> > ** (process:4337): CRITICAL **: egg_desktop_entries_add_group:
>> assertion `egg_desktop_entries_lookup_group (entries, group_name) ==
>> NULL' failed
>> >
>> > ** (process:4337): CRITICAL **: egg_desktop_entries_add_group:
>> assertion `egg_desktop_entries_lookup_group (entries, group_name) ==
>> NULL' failed
>> >
>> > ** (process:4337): CRITICAL **: egg_desktop_entries_add_group:
>> assertion `egg_desktop_entries_lookup_group (entries, group_name) ==
>> NULL' failed
>> >
>> >
>> > They started on my PPC G4 powerbook and they are displayed every
>> time I upgrade or install using apt and now it shows up when I am
>> trying to install from source VMware on my AMD64 box and running apt
>> on the AMD64 too.  This just started when I installed a bunch of KDE,
>> gtk and other misc software today and then it just started.  I have
>> noticed others on line have had this issue but there has not been any
>> postings for eradicating the CRITICAL egg_desktop error.  I  have
>> noticed that is only happens in Dapper and my Breezy partitions are
>> just find and never show this CRITICAL error.
>> >
>> > I am wondering if it is tied to 'desktop' but I have not installed
>> anything labeled as 'desktop' when looking at the logs.  Is it a
>> 'desktop' related error or is this tied to something else?
>> >
>> > -Adam
>> >
>>
>> Is there a way to track this for trouble shooting.  The hardest part
>> is I have no idea where to begin.  It has been plaguing me for months
>> on Ubuntu PPC and now since it is starting on my AMD 64, I know it is
>> not a platform issue but something to do with a package in dapper.  I
>> can track it down and then file a bug report but I just don't have any
>> idea how to decipher the bug error and track it for a bug report.
>>
>> The events that lead to this demise yesterday.
>>
>> I was getting some make xconfig (kconfig) errors so I thought to
>> install more qt packages.. which actually led me to install KDE which
>> I really do not use but several of its apps.  I then wanted to see if
>> make gconfig produced the same errors and then had to install gtk(+)
>> dev files.  (Now installing the gtk+ dev files proved the errors I 
>> was receiving with the kconfig are only with xconfig (kconfig).. it
>> ruled that out.)
>>
>> Then there were some xserver updates and some misc files.  Looking at
>> my aptitude log file I could not find what could have caused any
>> abnormality.  I also used synaptic to select the KDE packages to install.
>>
>> I know this is a package issue since it only started after I did a
>> large package install in Dapper and is happening now to 2 boxes.
>>
>> If someone who has gone through this and has fixed it.. could please
>> let the list know .. at lease where to begin which is the one place I
>> just can't seam to find and post it to the list so the others may also
>> see for future times?  Very much in thanks...
>>
>> -Adam
>>
>> -- 
>> ubuntu-users mailing list
>> ubuntu-users at lists.ubuntu.com
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>
>