By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2989 - ark-trinity could not start from trinity desktop menu.
Summary: ark-trinity could not start from trinity desktop menu.
Status: NEEDINFO
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeutils (show other bugs)
Version: R14.1.x [Trinity]
Hardware: amd64 Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2018-12-01 21:59 CST by Andy
Modified: 2018-12-03 09:39 CST (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
抓图1.png (814.38 KB, image/png)
2018-12-01 21:59 CST, Andy 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andy 2018-12-01 21:59:12 CST 
Created attachment 2909 [details]
抓图1.png

I am using Trinity Desktop R14.1.0 on Debian Sid amd64.But,when I try to start 
ark-trinity from trinity desktop menu,it shows me an error dialog:

FATAL:libark could not found.Aborting.

See "抓图1.png" for details.
But I can start ark-trinity from konsole-trinity by using command "ark" without any arguments.
Comment 1 Michele Calgaro 2018-12-01 22:35:33 CST 
Hi Andy,
running debian testing + R14.1.0-dev here, no issues.

1) if you press Alt+F2, then type "ark" in the launcher box, does ark starts? Or same error?
2) can you check your menu config and post the command used for the Ark entry?
Comment 2 Slávek Banko 2018-12-03 08:29:18 CST 
The problem is probably related to bug 2961 and a series of patches associated with it - see https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/7

Are you using Preliminary Testing Builds repository? Updated packages for tdeutils should already be available in repository. Please try to update and if everything is fine, you can close the bug.