Bug 428181 - Audacious music player "Open Folder" option no longer working after Plasma 5.20 update
Summary: Audacious music player "Open Folder" option no longer working after Plasma 5....
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Open/save dialogs (show other bugs)
Version: git master
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2020-10-24 13:56 UTC by Sanras
Modified: 2022-12-21 11:52 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sanras 2020-10-24 13:56:42 UTC
SUMMARY
The "Open Folder" option in Audacious does not work anymore after an update to Plasma 5.20. While the folder selector pops up, selecting a folder and clicking the "open" button does nothing.

STEPS TO REPRODUCE
1. Open Audacious (Using the "Winamp Classic Interface"), and select "Open Folder"
2. Navigate into a folder that contains audio files.
3. Click "Open" button

OBSERVED RESULT
The "open" button does not do anything, and the folder select window stays open. No songs are loaded into Audacious.

EXPECTED RESULT
The window closes, and the songs in the selected folder are loaded into the current playlist in Audacious.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux, kernel 5.9.1-arch1-1
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
Audacious Version: 4.0.5
Comment 1 guschtlswife 2020-10-26 04:35:21 UTC
Same issue over here:

https://github.com/borgbase/vorta/issues/693

Same OS, same KDE/Plasma/Qt versions.
Used to work back in Plasma 5.19.x
Thanks!
Comment 2 Jazz 2020-11-08 13:34:45 UTC
I ran into the same problem with Audacious after the recent Plasma update on Manjaro KDE. Interface of the app is irrelevant, since I use the default one.

File > Open Folder... > [select a dir] > Open

Whilst clicking "Open", nothing happens. It used to work fine previously.
Comment 3 farzad 2020-12-30 00:17:24 UTC
Same issue using vorta on KDE Plasma.
https://github.com/borgbase/vorta/issues/693

Linux 5.4.80-2-MANJARO x86_64 GNU/Linux
plasmashell 5.20.4
QT 5.15.2
vorta 0.7.1-3
Comment 4 sdfagvbasdfgasdfgasdf 2021-01-06 00:56:42 UTC
I created a code example, requires PyQt5. Expected behaviour is clicking the open button prints the path.

from PyQt5 import QtCore
from PyQt5.QtWidgets import QFileDialog, QApplication, QWidget
import os
import sys

class App(QWidget):
    def __init__(self):
        def receive():
            dirs = dialog.selectedFiles()
            print(dirs)
        super().__init__()
        dialog = choose_file_dialog(self, "asdf", want_folder=True)
        dialog.open(receive)  # Open and cancel buttons don't do anything on KDE, breaks here.
        dialog.exec()
        sys.exit()


def choose_file_dialog(parent, title, want_folder=True):
    options = QFileDialog.Options()
    if want_folder:
        options |= QFileDialog.ShowDirsOnly
    dialog = QFileDialog(parent, title, os.path.expanduser('~'), options=options)
    dialog.setFileMode(QFileDialog.Directory if want_folder else QFileDialog.ExistingFiles)
    dialog.setParent(parent, QtCore.Qt.Sheet)
    return dialog

if __name__ == '__main__':
    app = QApplication(sys.argv)
    ex = App()
    sys.exit(app.exec_())
Comment 5 Patrick Silva 2021-04-03 11:53:47 UTC

*** This bug has been marked as a duplicate of bug 419874 ***
Comment 6 Jazz 2021-09-02 01:48:42 UTC
I still have the same issue like reported here. I patiently waited after multiple updates for months. Currently on KDE Plasma v5.22.4. After I run the above code by @samuel-w, I can still replicate the original bug - I couldn't select any subdirectory. The button "Open" behaves like it's disabled, but it's actually not disabled. When I run the code, this is the output:

$ python test.py 
QApplication: invalid style override 'gtk' passed, ignoring it.
        Available styles: Breeze, kvantum-dark, kvantum, qt5ct-style, Windows, Fusion
qt.svg: link #path2410 is undefined!
kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/desktop.so" "Failed to extract plugin meta data from '/usr/lib/qt/plugins/kf5/kio/desktop.so'"
kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data from '/usr/lib/qt/plugins/kf5/kio/applications.so'"
kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/desktop.so" "Failed to extract plugin meta data from '/usr/lib/qt/plugins/kf5/kio/desktop.so'"
kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data from '/usr/lib/qt/plugins/kf5/kio/applications.so'"
Comment 7 Sanras 2021-09-02 02:19:55 UTC
@Jazz(In reply to Jazz from comment #6)
> I still have the same issue like reported here. I patiently waited after
> multiple updates for months. Currently on KDE Plasma v5.22.4. After I run
> the above code by @samuel-w, I can still replicate the original bug - I
> couldn't select any subdirectory. The button "Open" behaves like it's
> disabled, but it's actually not disabled. When I run the code, this is the
> output:
> 
> $ python test.py 
> QApplication: invalid style override 'gtk' passed, ignoring it.
>         Available styles: Breeze, kvantum-dark, kvantum, qt5ct-style,
> Windows, Fusion
> qt.svg: link #path2410 is undefined!
> kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/desktop.so"
> "Failed to extract plugin meta data from
> '/usr/lib/qt/plugins/kf5/kio/desktop.so'"
> kf.coreaddons: no metadata found in
> "/usr/lib/qt/plugins/kf5/kio/applications.so" "Failed to extract plugin meta
> data from '/usr/lib/qt/plugins/kf5/kio/applications.so'"
> kf.coreaddons: no metadata found in "/usr/lib/qt/plugins/kf5/kio/desktop.so"
> "Failed to extract plugin meta data from
> '/usr/lib/qt/plugins/kf5/kio/desktop.so'"
> kf.coreaddons: no metadata found in
> "/usr/lib/qt/plugins/kf5/kio/applications.so" "Failed to extract plugin meta
> data from '/usr/lib/qt/plugins/kf5/kio/applications.so'"

I can confirm that this issue is still present for me as well. Should've reopened this issue myself.
Comment 8 Jazz 2021-09-05 22:39:16 UTC
I've noticed something interesting. I.g. if we have the following dir path:

~/A/B/C/D

In case you open D dir (from the "Open Folder" dialogue) and try to click at "Open" - it won't work.

But in case you open dir C and JUST SELECT dir D (without opening it), then clicking "Open" works as expected!

I could replicate the above behavior whilst running the above Python code as well.

Is this the expected behavior? Not very intuitive/user friendly imo. It should work in both cases.
Comment 9 bitchefbird 2022-03-07 17:08:48 UTC
Hi,

I am experiencing the same phenomenon with audacious 4.1 on Gentoo.

Actions performed:

Start audacious in a terminal.
Then from the GUI select:
File > Open Folder .. > (choose a folder) click "Open" button
or
File > Add Folder .. > (choose a folder) click "Add" button

Expected:

All music files in the designated folder are added to the playlist.

Observed:

In both cases the dialog box stays open, no file is added to the playlist, and I get the following message in my terminal
Qt: Session management error: networkIdsList argument is NULL

I noticed that this phenomenon disappears when audacious is launched from another window manager (e.g i3)  and uses the generic Qt file chooser (as John Lindgren from audacious so graciously helped me determine https://redmine.audacious-media-player.org/issues/1089#note-7).

It is suspected that the KDE File chooser is interfering with audacious' default behaviour.  I hope this will help in identifying the root cause of the problem.
I am willing to perform further tests if necessary.

Thanks for your help.


Installed version:

media-plugins/audacious-plugins 4.1
media-sound/audacious 4.1

dev-qt/qtcore 5.15.2-r14
kde-frameworks/plasma 5.90.0-r1
kde-plasma/plasma-desktop 5.23.5-r1
x11-base/xorg-server 21.1.3

Environment:

Portage 3.0.30 (python 3.9.9-final-0, default/linux/amd64/17.1/desktop/plasma/systemd, gcc-11.2.0, glibc-2.33-r7, 5.15.23-gentoo x86_64) =================================================================

Timestamp of repository gentoo: Sun, 06 Mar 2022 06:30:01 +0000
Head commit of repository gentoo: 595d57be87fef04ee62ecdd9ed3dd2c7f444ee2c
sh bash 5.1_p16
ld GNU ld (Gentoo 2.37_p1 p2) 2.37
app-shells/bash: 5.1_p16::gentoo
dev-lang/perl: 5.34.0-r6::gentoo
dev-lang/python: 3.7.12_p1::gentoo, 3.8.12_p1-r1::gentoo, 3.9.9-r1::gentoo, 3.10.0_p1-r1::gentoo
dev-util/cmake: 3.22.2::gentoo
dev-util/meson: 0.60.3::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.71-r1::gentoo
sys-devel/automake: 1.13.4-r2::gentoo, 1.14.1-r2::gentoo, 1.16.4::gentoo
sys-devel/binutils: 2.37_p1-r2::gentoo
sys-devel/binutils-config: 5.4::gentoo
sys-devel/clang: 13.0.0::gentoo
sys-devel/gcc: 11.2.0::gentoo
sys-devel/gcc-config: 2.5-r1::gentoo
sys-devel/libtool: 2.4.6-r6::gentoo
sys-devel/llvm: 13.0.0::gentoo
sys-devel/make: 4.3::gentoo
sys-kernel/linux-headers: 5.15-r3::gentoo (virtual/os-headers)
sys-libs/glibc: 2.33-r7::gentoo
Comment 10 Fushan Wen 2022-03-14 15:44:03 UTC
Can reproduce.
Comment 11 Fushan Wen 2022-03-14 16:51:53 UTC
Hangs at nativeDialogInUse = platformFileDialogHelper() != nullptr;
Comment 12 Fushan Wen 2022-12-21 11:52:46 UTC
Should be fixed now