Bug 33155

Summary: Konqueror does not work any more on Cauldron; at least for x86.
Product: Mageia Reporter: Ben McMonagle <westel>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: konqueror-24.02.2-1.mga10.src.rpm CVE:
Status comment:

Description Ben McMonagle 2024-04-29 11:57:48 CEST
Description of problem: These four .desktop files: kfmclient, kfmclient_
dir, kfmclient_htkl & kfmclient_war do not invoke konqueror browser when double clicked. 
running the Exec command via CLI does not work either, e.g.:

$ kfmclient openURL %u
org.kde.kfmclient: Error starting konqueror

Konqueror does invoke from both CLI or menu launcher.

comparing the (properties) application tab between Mga9 & 10 does not show any differences (to my untrained eye)
when comparing the contents of the files with a text editor, the mga9 and mga10 files appear identical.

This is a regression from Mga9. 

They are likely to be included with the Mga10 release isos, so should be functional. (were included in Mga8 & Mga9)

Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. attempt to invoke the kfmclient.desktop files via mouse click or their Exec commands  
2.
3.
Comment 1 sturmvogel 2024-04-29 18:01:39 CEST
This seems not the right way to use it:
https://techbase.kde.org/Development/Tools/Using_kfmclient
Comment 2 Ben McMonagle 2024-04-29 22:08:25 CEST
(In reply to sturmvogel from comment #1)
> This seems not the right way to use it:
> https://techbase.kde.org/Development/Tools/Using_kfmclient

created the shell script as per the link.

$ ./here.sh 
org.kde.kfmclient: Error starting konqueror
Ben McMonagle 2024-04-29 22:36:47 CEST

Source RPM: (none) => konqueror-24.02.2-1.mga10.src.rpm

Comment 3 Lewis Smith 2024-04-30 21:44:29 CEST
These are all konqueror thingies. They may have .desktop entries, but do they appear in any menu? I do not think they are meant to be invoked directly.
/usr/share/applications/kfmclient.desktop
/usr/share/applications/kfmclient_dir.desktop
/usr/share/applications/kfmclient_html.desktop
/usr/share/applications/kfmclient_war.desktop

Mageia 9:
From a terminal (none of them have a man page):
 $ LANG=C kfmclient
Syntax:
  kfmclient openURL 'url' ['mimetype']
            # Opens a window showing 'url'.
            #  'url' may be a relative path
            #   or file name, such as . or subdir/
            #   If 'url' is omitted, $HOME is used instead.

            # If 'mimetype' is specified, it will be used to determine the
            #   component that Konqueror should use. For instance, set it to
            #   text/html for a web page, to make it appear faster

  kfmclient newTab 'url' ['mimetype']
            # Same as above but opens a new tab with 'url' in an existing Konqueror
            #   window on the current active desktop if possible.

 $ kfmclient_dir
bash: kfmclient_dir: command not found
 $ kfmclient_html
bash: kfmclient_html: command not found
 $ kfmclient_war
bash: kfmclient_war: command not found

In a file manager, double-clicking:
kfmclient.desktop
 opens a konqueror FM window.
kfmclient_dir
 opens a web page (duckduckgo, Directory).
kfmclient_html
 opens a web page (duckduckgo, HTML).
kfmclient_war.desktop
 opens a web page (duckduckgo,Webarchive).

All this is spurious, and it should not matter that the same does not happen elsewhere. I think you have discovered a curiosity rather than something that matters. What might matter is that *Konquerer's* functionality is adversely affected; but this application is being rather sidelined against Dolphin & Falkon.

CC: (none) => lewyssmith

Comment 4 Ben McMonagle 2024-06-05 09:10:39 CEST
for i586,

this issue has been resolved
Comment 5 Ben McMonagle 2024-06-06 01:08:54 CEST
valid for x86_64

changing "Hardware" to x86_64

Hardware: All => x86_64

Comment 6 Lewis Smith 2024-06-09 21:36:01 CEST
I still think this is a curiosity rather than a real problem. These 'hidden' .desktop files, unless represented in a menu, are clearly not meant to be invoked directly by the user.

(In reply to Ben McMonagle from comment #4)
> for i586,
> this issue has been resolved
So please say what does happen when you double-click the .desktop filenames.
Comment 7 Ben McMonagle 2024-06-10 08:49:28 CEST
i586:

double click brings up a dialogue box (open /execute / cancel)
choosing "execute" invokes  konqueror.

sadly, Konqueror does not display any of the expected web pages (just a blank page).

since the above does not open a web page,
I tried invoking konqueror from the application launcher menu.

same result, no webpages open.

using Konqueror to open a local .txt file displays contents of local text file, local file browser functions -ok 

will try x86_64 tomorrow.
Comment 8 Ben McMonagle 2024-06-10 22:55:17 CEST
x86_64:

double click brings up a dialogue box (open /execute / cancel)
choosing "execute" does not invoke konqueror.

attempting to invoke konqueror from application launcher menu also fails.

attempting to invoke konqueror from CLI results in:

$ konqueror 
kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/webenginepart.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/dragonpart.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/fsviewpart.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/konq_sidebar.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/dolphinpart.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/uachangerplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/khtmlsettingsplugin.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/webarchiverplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/akregatorkonqfeedicon.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/autorefresh.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/babelfishplugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/konqueror_kget_browser_integration.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/webenginepart.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/dragonpart.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/fsviewpart.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/konq_sidebar.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed
kf.coreaddons: The plugin "/usr/lib64/qt6/plugins/kf6/parts/dolphinpart.so" explicitly states an 'Id' in the embedded metadata. This value should be removed, the resulting pluginId will not be affected by it
WARNING: radv is not a conformant Vulkan implementation, testing use only.
konqueror: symbol lookup error: /lib64/libQt6WebEngineCore.so.6: undefined symbol: _ZN3re23RE210FullMatchNEN4absl12mga_2023080211string_viewERKS0_PKPKNS0_3ArgEi


this is a regression, as konqueror used to work in x86_64
Comment 9 Lewis Smith 2024-06-11 21:46:23 CEST
This looks more solid: konqueror no longer works on Cauldron.

Unsure why you expect it to open a web page when launched; unless you define a specific one in its settings.

Assigning to KDE.

CC: lewyssmith => (none)
Summary: the 4 kfmclient .desktop files do not launch (kfmclient, _dir, _html, & _war) => Konqueror does not work any more on Cauldron; at least for x86.

Lewis Smith 2024-06-11 21:48:00 CEST

Assignee: bugsquad => kde