Bug 358045 - Kdialog display nothing with --progressbar
Summary: Kdialog display nothing with --progressbar
Status: RESOLVED FIXED
Alias: None
Product: kdialog
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Brad Hards
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-16 00:42 UTC by Aristide
Modified: 2017-03-26 02:22 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Attempted fix; does not work (1.58 KB, patch)
2016-12-30 17:37 UTC, Christoph Feck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aristide 2016-01-16 00:42:50 UTC
When I type : 

kdialog --progressbar "Whatever" 

Nothing dialog appear. I get only DBus reference in output from terminal. but access to this reference with qdbusviewer crash Qdbusviewer. 

I have see this bug on several distros. 

kdialog --version
Qt: 5.5.1
KDE Frameworks: 5.19.0
KDialog: 1.0
Comment 1 dutchkind 2016-12-22 17:32:18 UTC
I can confirm this bug in Opensuse Tumbleweed and would appreciate a fix
Comment 2 Christoph Feck 2016-12-30 17:37:37 UTC
Created attachment 103095 [details]
Attempted fix; does not work

I tried adding KDBusService(Multiple) before printing the connection name, but it did work. tests/progressdemo says

Path 'org.kde.kdialog.ProgressDialog' is not a valid path name.

Needs someone with understanding QDBus to fix it.
Comment 3 José JORGE 2017-01-08 15:31:47 UTC
I can confirm this is a recent bug, as for Plasma 5.8.0 it did work.
I observe it with Mageia Cauldron for at most one month.
Comment 4 Vishal Rao 2017-02-12 14:21:52 UTC
Using KDE Neon dev unstable edition here and kdialog progressbar does not seem to be visible to qdbus. I tried to look and fix the code but can't get it even visible to qdbus.
Comment 5 Vishal Rao 2017-02-13 10:02:56 UTC
OK it looks like the fork() call is causing dbus to not work. If I comment out the fork portion and also add KDBusService as attempted by Christoph the dialog becomes visible and is operable by qdbus commands. But it does not hide or go into background of course, so some other approach is needed than fork.

I also came across another project bug which might imply fork() is not safe with QDBus code: https://github.com/mumble-voip/mumble/issues/2820
Comment 6 Christoph Feck 2017-03-26 02:22:34 UTC
Fixed by David Faure.

https://commits.kde.org/kdialog/d72ab46df8879024cda620beec9da71a674873dc