Bug 375206 - Kdenlive-16.12.1-2-x86_64.AppImage aborts with 'failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id"'
Summary: Kdenlive-16.12.1-2-x86_64.AppImage aborts with 'failed to read machine uuid: ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: Installation (show other bugs)
Version: Appimage - Refactoring
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2017-01-17 23:51 UTC by Lutz Vieweg
Modified: 2018-09-19 14:37 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Lutz Vieweg 2017-01-17 23:51:06 UTC 
When I start to run Kdenlive-16.12.1-2-x86_64.AppImage, it quickly aborts with the following message:

process 14977: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
  D-Bus not built with -rdynamic so unable to print a backtrace
/tmp/.mount_Dk8eCB/AppRun: line 55: 14977 Aborted                 kdenlive --config kdenlive-appimagerc $@

This problem did not occur with Kdenlive-16.12.0-x86_64.AppImage, so something new must have introduced the hunt for the non-existing machine-id file.

(My operating system here is the latest and greatest CentOS 7.3.1611, and yes, there is no "/var/lib/dbus/machine-id" file - never missed it ;-) )
Comment 1 Lutz Vieweg 2017-01-18 00:05:35 UTC 
Seems that one can either do

 ln -s /var/lib/dbus/machine-id /etc/machine-id

or just create a new /var/lib/dbus/machine-id file and write some random 32-hex-digits number to it.

Then, Kdenlive-16.12.1-2-x86_64.AppImage does start on my system.

Would of course be better if the AppImage provided that file readily.
Comment 2 Vincent PINON 2017-10-20 19:14:57 UTC 
Hello,
Is the bug fixed with the recent 17.08 images?
Comment 3 Lutz Vieweg 2017-10-31 16:30:23 UTC 
(In reply to Vincent PINON from comment #2)
> Is the bug fixed with the recent 17.08 images?

No, the symptom still occurs with kdenlive-17.08.2-x86_64.AppImage - and the same work-around I mentioned above (which is only possible to create as "root") is still possible.
Comment 4 Andrew Crouthamel 2018-09-19 14:37:59 UTC 
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.