3038 – KDialog doesn't show in Chrome and Vivaldi browser

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 3038 - KDialog doesn't show in Chrome and Vivaldi browser

Summary: KDialog doesn't show in Chrome and Vivaldi browser

Status:	NEW

Alias:	None

Product:	TDE
Classification:	Unclassified
Component:	other (any) (show other bugs)
Version:	R14.0.x [Trinity]
Hardware:	Other Linux

Importance:	P5 normal
Assignee:	Timothy Pearson

URL:

Depends on:
Blocks:

Reported:	2019-09-05 06:40 CDT by Heimen Stoffels
Modified:	2019-09-06 15:22 CDT (History)
CC List:	3 users (show)

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

Attachments
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 Heimen Stoffels 2019-09-05 06:40:34 CDT

I have no idea why, as it works fine in other TDE apps, and even KDE apps like Falkon. I don't know where to start as the terminal doesn't show any errors related to it when I launch e.g. Vivaldi. But it's gotta be a bug somehow.

To clarify: with "KDialog doesn't show" I mean that it just doesn't pop up in Chrome and Vivaldi when it's supposed to show a "Open file" (i.e. for uploading files to a website) or "Save file" (i.e. when saving an image) dialog.

Can anybody help me debug this so that we can find the cause of this bug?

Comment 1 Roman 2019-09-05 11:33:39 CDT

Maybe I did not understand what.
Why should KDialog work in Chrome?
Google Chrome uses the gtk+3 dialog, it belongs to the gtk+3 library.
Maybe this error only appears in TDE?

Comment 2 Heimen Stoffels 2019-09-05 12:01:46 CDT

In Plasma 5, Vivaldi uses the KDE dialog, so why would it use the GTK one on TDE if KDialog is also available on TDE? But even if so: Vivaldi doesn't show any dialog under TDE, so there's still a bug somewhere.

Comment 3 Roman 2019-09-05 14:24:19 CDT

Perhaps a bug. 
If the same thing is repeated, for example, in openbox, then, most likely, the point is in the settings. I cannot repeat this bug on my Gentoo. 
Perhaps after launching Plasma 5, some settings were added. According to personal observations, TDE is poorly compatible with Plasma.
I was just wondering.

Comment 4 Heimen Stoffels 2019-09-05 14:30:12 CDT

I installed Plasma 5 before I installed TDE. But even so: I see no reason why dialogs don't work in Vivaldi and Chrome on TDE but they work in all other apps on TDE. Is there no way to debug this?

Comment 5 Roman 2019-09-05 15:54:45 CDT

What is your OS?
I myself can not get kdialog to work with Vivaldi.
pid received by the command:
sleep 2s; xdotool getwindowpid $ (xdotool getwindowfocus)
shows that the dialogue belongs to Vivaldi.
This means that the GTK dialog is used.
I cannot repeat this even with installed plasma.

Comment 6 Heimen Stoffels 2019-09-05 16:16:44 CDT

I don't know what to tell you: Vivaldi uses the KDE dialogs on Plasma for me. But I don't care what kind of dialogs it's supposed to use on TDE, I just want working dialogs in Vivaldi on TDE, that's all.

My OS is Arch Linux. Sorry, should've included that in the OP.

Comment 7 Heimen Stoffels 2019-09-05 16:21:37 CDT

In fact, Manjaro even says that Vivaldi is supposed to use KDialog on Plasma by installing kdialog (which I did):

"By default, Vivaldi will use the GTK file dialogs. If you are using plasma and would prefer native dialogs, you can install the package kdialog using your favorite package manager or with the command:

pamac install kdialog"
Source: https://wiki.manjaro.org/index.php?title=Vivaldi_Browser#Using_the_Native_File_Dialogs_on_KDE.2Fplasma

And Arch suggests the same: https://wiki.archlinux.org/index.php/Vivaldi

So I really don't understand why you think Vivaldi doesn't use KDialog on Plasma.

Comment 8 Roman 2019-09-06 11:16:18 CDT

I managed to reproduce this bug.
What does this command output?
$ env|grep -i XDG

Comment 9 Heimen Stoffels 2019-09-06 12:57:09 CDT

This is the output:

vistaus@ThinkArch ~> env|grep -i XDG
XDG_CONFIG_DIRS=/opt/trinity/etc/xdg:/etc/xdg
XDG_CURRENT_DESKTOP=KDE
XDG_DATA_DIRS=/opt/trinity/share:/usr/local/share:/usr/share
XDG_RUNTIME_DIR=/run/user/1001
XDG_SEAT=seat0
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=
XDG_SESSION_ID=15
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session14
XDG_SESSION_TYPE=x11
XDG_VTNR=1
vistaus@ThinkArch ~>

Comment 10 Roman 2019-09-06 13:48:18 CDT

The reason is in the variable XDG_CURRENT_DESKTOP. As far as I understand, this variable does not belong to TDE. Maybe it’s the display manager.
Try adding a line to the ~/.xprofile file:

unset XDG_CURRENT_DESKTOP

If this file is missing, you must create it.
The gtk dialog in vivaldi will open.
That should work.

Comment 11 Heimen Stoffels 2019-09-06 14:19:17 CDT

Thanks! That worked! But it still doesn't use TDE's KDialog while it does use KDialog on Plasma, so this bug is still relevant.

Comment 12 Roman 2019-09-06 14:40:20 CDT

There is not option in TDE Kdedialog:
--attach=$winid
Therefore, using it is not realistic in vivaldi.

Comment 13 Heimen Stoffels 2019-09-06 14:52:23 CDT

What do you mean?

Comment 14 Roman 2019-09-06 15:06:43 CDT

I mean, kdialog in TDE and kdialog in Plasma use different parameters. Because of this, Kdialog from TDE fails and does not start in Vivaldi.

Comment 15 Heimen Stoffels 2019-09-06 15:09:47 CDT

Okay, understood. But there ought to be a way to make it work. If not, then this bug should at least remain open so that this can be implemented some time.

Comment 16 Roman 2019-09-06 15:22:44 CDT

I'm not against.
But I'm not a TDE developer.
Good luck!