ClamTK: Unknown error. Desktop file appears to be are valid.

Bug #1885623 reported by michael on 2020-06-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
clamtk (Ubuntu)
Undecided
Unassigned

Bug Description

Unknown error. Desktop file appears to be are valid.

michael@michael-Inspiron-531:~$ lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04

michael@michael-Inspiron-531:~$ apt-cache policy clamtk
clamtk:
  Installed: 6.02-1
  Candidate: 6.02-1
  Version table:
 *** 6.02-1 500
        500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu focal/universe i386 Packages
        100 /var/lib/dpkg/status

I expect ClamTK to tell me, what the error is.

It says, Unknown error. Desktop file appears to be are valid.

Answer from Launchpad.
For several other messages showing "Unknown error. Desktop file appears to be are valid.":
The error message is incomprehensible. I assume that it comes from clamtk and might be reported as bug against clamtk. The message does not tell what clamtk deems wrong, so I cannot judge what okular should change to make the error disappear.

Overall I do not see any severe problem or malware or trojans.

michael (yellupcm-gmail) wrote :
michael (yellupcm-gmail) wrote :

This bug was found when bug #1884815 came up.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1885623/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Paul White (paulw2u) on 2020-06-29
affects: ubuntu → clamtk (Ubuntu)
tags: added: focal
Dave M (dave-nerd) wrote :

Hi,

Can you give some more information on this? Maybe this is my lack of experience with Ubuntu, but I don't understand what the error is or how it comes about. Does clamtk run?

Thanks,

michael (yellupcm-gmail) wrote :

I ask question about parsing error, in Launchpad question #691449. Answer was to file a bug. bug #1884815

Will show dialogue, between Launchpad and me.

michael (yellupcm-gmail) said on 2020-06-23: #8

Manfred
I was looking through Applications. I saw an icon I didn't know what it did. Menu Editor, clicked on it, this is what came up.

https://postimg.cc/87jXr09B

Clicked on details. Got this.

https://postimg.cc/nsLcZzSr

Clicked middle icon on right side. I got a page, that had many different sentences, in different languages. Using Google Translate, most said to do virus scan. Did two scans, first had three Trojans. I deleted them. The second scan is what you see. Later, I clicked Menu Editor again, this is what I got.

https://postimg.cc/pyBGPrZF

Manfred Hampl (m-hampl) said on 2020-06-24: #9

My interpretation of what you see:

The "Menu Editor" starts clamtk to check the *.dektop files for wrong entries, and clamtk complains about some configuration settings in these files that it deems not correct.

When you click the middle icon on the right side in the first line (.../clamtk-kde.desktop), you see the contents of that desktop file. It starts with

[Desktop Entry]
Name=clamtk
Exec=clamtk %F
Type=Service
ServiceTypes=KonqPopupMenu/Plugin
MimeType=inode/directory;application/octet-stream;
X-KDE-StartupNotify=true;
Actions=openScanner;

[Desktop Action openScanner]
Icon=clamtk
Exec=clamtk %F
Name=Scan for threats...
Name[af]=Skandeer vir virusse...
Name[ar]=إمسح للكشف عن الفيروسات
Name[ast]=Buscar amenaces...
Name[az]=Təhlükə mövcudluğuna yoxla...
...

Yes, of course you see the text "Scan for viruses" in different languages, because that is the purpose of a *.desktop file - giving a description for an executable program in whatever language you have selected as your desktop language.

According to https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html the clamkt scanner is right, when it complains about "Type=Service", because the value 'Service' is not valid. This is something that comes from Debian and should probably be reported as bug there.

For several other messages showing "Unknown error. Desktop file appears to be are valid.":
The error message is incomprehensible. I assume that it comes from clamtk and might be reported as bug against clamtk. The message does not tell what clamtk deems wrong, so I cannot judge what okular should change to make the error disappear.

Overall I do not see any severe problem or malware or trojans.

michael (yellupcm-gmail) said on 2020-06-26: #10

Manfred
Thank you for the explanation. Will mark as solved. Will file bug reports.

Dave M (dave-nerd) wrote :

Hi,

Thank you! I see now. You're talking about this:

"This specification defines 3 types of desktop entries: Application (type 1), Link (type 2) and Directory (type 3). To allow the addition of new types in the future, implementations should ignore desktop entries with an unknown type."

Right? Also, this issue is actually with clamtk-kde, according to your screenshot.

That's an easy fix, if I understand correctly. I'll get a new version out (hopefully) this week.

Thanks,
Dave M

Dave M (dave-nerd) wrote :

Hi

I just realized why I never changed it to Application - because the context menu won't show up. This would defeat its purpose of scanning files/directories on right-click.

Does anyone know of a way to make this happen if changed to Application?

Thanks,
Dave M

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers