GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — Add more details to error on ldd failure by jlskuz · Pull Request #342 · linuxdeploy/linuxdeploy

Conversation

jlskuz commented Oct 31, 2026

Copy link

Copy Markdown

Mention the file it failed on
Show stderr and stdout off ldd

This should make it easier to debug issues like linuxdeploy/linuxdeploy-plugin-qt#203 and linuxdeploy/linuxdeploy-plugin-qt#111

I faced a smiliar failure onSuch the CD of Kdenlive. Unfortunately it is very hard to debug, because it is not reproducible outside of CD. Better error messages would help a lot.

-- Running input plugin: qt -- 
[qt/stdout] Using user specified qmake: /builds/multimedia/kdenlive/linux-64-gcc/bin/qmake 
[qt/stdout] Using qmake: /builds/multimedia/kdenlive/linux-64-gcc/bin/qmake 
[qt/stderr] linuxdeploy-plugin-qt version 1-alpha (git commit ID ce5291e), GitHub actions build 211 built on 2025-02-13 21:36:34 UTC
[qt/stdout] 
[qt/stdout] Using Qt version:  6.12.0  ( 6 ) 
[qt/stderr] terminate called after throwing an instance of 'std::runtime_error'
[qt/stderr]   what():  Failed to run ldd: exited with code 1
ERROR: Failed to run plugin: qt (exit code: 6) 
Command ['/builds/multimedia/kdenlive/linux-64-gcc/dev-utils/bin/linuxdeploy-x86_64.AppImage', '--appdir', '/builds/multimedia/kdenlive/linux-64-gcc/build/kde/kdemultimedia/kdenlive/archive', '--desktop-file', '/builds/multimedia/kdenlive/linux-64-gcc/build/kde/kdemultimedia/kdenlive/archive/usr/share/applications/org.kde.kdenlive.desktop', '--output=appimage', '--plugin=qt', '-v0'] failed with exit code 1

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions


          Add more details to error on ldd failure

16297c3

- Mention the file it failed on
- Show stderr and stdout off ldd

This should make it easier to debug issues like linuxdeploy/linuxdeploy-plugin-qt#203 and linuxdeploy/linuxdeploy-plugin-qt#111

TheAssassin commented Oct 31, 2026

Copy link

Copy Markdown

Member

Thank you for your contribution. I am not sure whether I like the approach, though. Dumping the entire stdout/stderr into the exception message might cause more issues downstream and overloads its meaning. I would instead log messages to the debug log (maybe even by default, although that can also be cumbersome). What do you think?

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.