Author Topic: Do kbuildsycoca4 messages mean we're doing something wrong?  (Read 1667 times)

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3985
Do kbuildsycoca4 messages mean we're doing something wrong?
« on: January 14, 2012, 12:44:02 PM »
When using dbus-launch to start an application from a terminal I see output like this:

Code: [Select]

kbuildsycoca4 running...
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Actions in "ServiceMenus/sram_e.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Actions in "ServiceMenus/sram_o.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Actions in "ServiceMenus/sram_r.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Actions in "ServiceMenus/sram_d.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Actions in "ServiceMenus/open_as_root.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/dillo.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/pclinuxos-pdfedit.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/gkrellm.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/NX/share/applnk/x-nxclient/nxclient.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/ImageMagick.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/audacity.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry MimeType in "/usr/share/applications/opera.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/apt-sources-update.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/xterm.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/keytouch-editor.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/lxinput.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/lxrandr.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/lxautostart.desktop" is not compliant with XDG standard (missing trailing semicolon).
kbuildsycoca4(29945) KConfigGroup::readXdgListEntry: List entry Categories in "/usr/share/applications/bleachbit-root.desktop" is not compliant with XDG standard (missing trailing semicolon).

As most .desktop files are generated from the .spec file, I wonder whether this indicates we're not doing it properly. Is it something to watch on the next build or is it a false result?
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline rubentje1991

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2110
  • Rubenus Parvus MCMXCI
Re: Do kbuildsycoca4 messages mean we're doing something wrong?
« Reply #1 on: January 16, 2012, 06:57:22 AM »
Just took the gkrellm SRPM (version 2.3.5.1 - is that the version you've installed?)...
SPEC file:
Quote
cat >  %{buildroot}%{_datadir}/applications/%{name}.desktop << EOF
[Desktop Entry]
Name=%{title}
Comment=%{longtitle}
Exec=%{_bindir}/%{name}
Icon=%{name}
Terminal=false
Type=Application
StartupNotify=true
Categories=GTK;System;Monitor;X-MandrivaLinux-System-Monitoring
EOF
=> does this mean that in categories, the list has to end with a semicolon?

Maybe someone with a bit of time at hands, can test this out (compiling an adjusted SRPM with the semicolon), installing it on a testing system and compare the output of kdbuildsycoca4 to the output without the change?

EDIT: or some expert which can say at once what's correct/incorrect?

Offline Archie

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8589
  • Aurum nostrum non est aurum vulgi.
Re: Do kbuildsycoca4 messages mean we're doing something wrong?
« Reply #2 on: January 16, 2012, 07:04:11 AM »
@Ruben, I believe it must end with a semi-colon.

Oi ... and don't you call me an expert. ;)

But has that got to do with kjpetrie's issues?
« Last Edit: January 16, 2012, 07:06:04 AM by Archie »
Since 2006 | LiCo 401868 | Bare Metal | What is necessary is never unwise. --Sarek, 2258.42


Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3985
Re: Do kbuildsycoca4 messages mean we're doing something wrong?
« Reply #3 on: January 16, 2012, 10:40:18 AM »
Yes, that's exactly the point. It looks as if we've got into the habit of leaving the semicolon off (or perhaps we never realised it was needed) and that might not cause any obvious problems in normal use, but it does cause a huge list of complaints to standard error which I suspect delays the opening of the application until the complaints are sent/written/logged.

There is just the possibility that Texstar has chosen for some reason that it be like this, but unless that is the case it looks like something we need to watch in future.
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline pinoc

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2842
    • other projects...
Re: Do kbuildsycoca4 messages mean we're doing something wrong?
« Reply #4 on: January 16, 2012, 11:02:00 AM »
if you have more than 1 entry for a given line in a .desktop file then each entry must be followed by a semicolon, in this example for the Categories, there must be a semicolon at the end of the line. If not I get an error. Some more info is available here