Bug 468511

Summary: [kfmclient/XAMPP] kfmclient crashes when is used by XAMPP to open a link to its web interface
Product: [Applications] konqueror Reporter: Nathanaël B. <nathanael.barentin>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED FIXED    
Severity: crash CC: nate, stefano.crocco
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: The .kcrash report file.

Description Nathanaël B. 2023-04-14 20:41:48 UTC 
Created attachment 158113 [details]
The .kcrash report file.

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Hi, I encounter a crash of kfmclient when trying to open a link through it with XAMPP.
I tried to use DrKonqi crash reports system, but when submitting the report, I get an error message like "Cannot submit a bug report : https://bugs.kde.org/rest/bug?token=<a token changing at every attempts>."

**STEPS TO REPRODUCE**
1. Install and open XAMPP,
2. Start its servers and click on "Go To Application" button,
3. Observe that kfmclient crashes.

**OBSERVED RESULT**
XAMPP seem to use kfmclient to open its web interface with the "Go To Application" button.
Every time I click this button, the Kde Crash Reports opens, saying kfmclient crashed, and proposing me to

**EXPECTED RESULT**
I expect a web page/web interface to be opened in my default browser (Firefox 112.0)

**SOFTWARE/OS VERSIONS**
Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.10-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i5-10400 CPU @ 2.90GHz
Memory: 15.4 Gio of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: Wortmann_AG
Product Name: EU1009628;2110193
System Version: B460M-A;2110193

ADDITIONAL INFORMATION
I’m attaching the .kcrash file generated by DrKonqi. I hope its content have all the needed debug symbols traces (It says there’s enough infos).
Comment 1 Stefano Crocco 2023-04-17 16:17:26 UTC 
The problem is that kfmclient can't connect to your DBus session, which is needed to find out whether an instance of Konqueror is already running or not. If you don't have an active DBus session, you need to start one. If you do, then for some reason the kfmclient program launched by XAMPP can't access it. I have no knowledge of XAMPP, but, given this problem and the fact that it doesn't attempt to launch your default browser, I'm wondering whether XAMPP is running as your current user or another one.
Comment 2 Nathanaël B. 2023-05-11 16:53:02 UTC 
(In reply to Stefano Crocco from comment #1)
> The problem is that kfmclient can't connect to your DBus session, which is
> needed to find out whether an instance of Konqueror is already running or
> not. If you don't have an active DBus session, you need to start one. If you
> do, then for some reason the kfmclient program launched by XAMPP can't
> access it. I have no knowledge of XAMPP, but, given this problem and the
> fact that it doesn't attempt to launch your default browser, I'm wondering
> whether XAMPP is running as your current user or another one.

Hi, thanks for your answer.
`ps -elf | grep dbus` tells I have a dbus session running.
`ps -elf | grep xampp` tells XAMPP is running as my current user.

However, since I created this crash report, it seems some XAMPP or Kde package update have solved the issue : kfmclient doesn’t crash anymore (except if I’m in a i3wm session, but that seems logical as some Kde/Plasma services may not be running), and the web interface opens in Konqueror (I hoped it would open in Firefox, but I think it’s the expected result).

I think this report can be mark as closed, then ? Sorry for that.