Bug 481506 - [X11, qt 6.7 beta 3 ] Open Terminal Here in Dolphin crashes konsole
Summary: [X11, qt 6.7 beta 3 ] Open Terminal Here in Dolphin crashes konsole
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 24.02.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-18 11:20 UTC by pmargeti34
Modified: 2024-03-17 16:03 UTC (History)
6 users (show)

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


Attachments
pertinent journal segment when Open Terminal Here is selected (4.27 KB, text/plain)
2024-02-18 11:20 UTC, pmargeti34
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pmargeti34 2024-02-18 11:20:26 UTC
Created attachment 165923 [details]
pertinent journal segment when Open Terminal Here is selected

SUMMARY
***
Konsole doesn't open when invoked via Dolphin's Open Terminal Here option under X11. See attached journal file for more details.
***


STEPS TO REPRODUCE
1.  Open Dolphin
2.  Right click
3. Select Open Terminal Here

OBSERVED RESULT

Mouse cursor indicates konsole is launching. Nothing happens.

EXPECTED RESULT

Konsole opens in the working directory

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Linux 6.7.5 / Plasma 6 RC2
(available in About System)
KDE Plasma Version: Plasma 6 RC2
KDE Frameworks Version: 5.115
Qt Version: 6.7 beta 3

ADDITIONAL INFORMATION
It worked on qt 6.7 beta 2 so this is likely a regression introduced in beta 3.
Comment 1 Antonio Rojas 2024-02-18 11:59:51 UTC
Please post the output when running with the QT_DEBUG_PLUGINS=1 env variable set
Comment 2 pmargeti34 2024-02-19 12:04:53 UTC
~ ▶ export QT_DEBUG_PLUGINS=1
~ ▶ dolphin
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland.
Comment 3 Nelson 2024-03-06 19:31:15 UTC
(In reply to pmargeti34 from comment #2)
> ~ ▶ export QT_DEBUG_PLUGINS=1
> ~ ▶ dolphin
> Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not
> UTF-8.
> Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
> If this causes problems, reconfigure your locale. See the locale(1) manual
> for more information.
> qt.qpa.xcb: could not connect to display 
> qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load
> the Qt xcb platform plugin.
> qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though
> it was found.
> This application failed to start because no Qt platform plugin could be
> initialized. Reinstalling the application may fix this problem.
> 
> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
> offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland.

Got the same problem with the same output. KDE Neon 6.0.0. X11.

I use a button on the Dolphin panel to open terminals in the current directory.
Found the bug when that button no longer did anything.
I assume it's the exact same as using the context menu.
Comment 4 Victor Ryzhykh 2024-03-07 21:10:20 UTC
The same problem in session x11 on Fedora and Rosa.
This is only in x11, there is no such problem in the Wayland session.
Comment 5 Bernhard Rosenkränzer 2024-03-13 00:53:10 UTC
This is caused by KTerminalLauncherJob launching konsole with an empty environment (causing the DISPLAY variable to go missing, causing the connection to the X server to fail).
It has already been fixed in git (and in OpenMandriva packages). https://invent.kde.org/frameworks/kio/-/commit/6e7775d315f389df0a440ed62b842ce83dc9a27e
Comment 6 Nelson 2024-03-13 01:08:52 UTC
(In reply to Bernhard Rosenkränzer from comment #5)
> This is caused by KTerminalLauncherJob launching konsole with an empty
> environment (causing the DISPLAY variable to go missing, causing the
> connection to the X server to fail).
> It has already been fixed in git (and in OpenMandriva packages).
> https://invent.kde.org/frameworks/kio/-/commit/
> 6e7775d315f389df0a440ed62b842ce83dc9a27e

That's good. But excuse me, I'm not a technical user: what does it mean it's fixed in git? I hear there's a KDE 6.0.1 out already with some fixes, but on Neon, the distro I use, it's not yet available, for example. Can we know when the fixes will be released on any given distro?
Comment 7 Victor Ryzhykh 2024-03-13 10:17:10 UTC
(In reply to Bernhard Rosenkränzer from comment #5)
> This is caused by KTerminalLauncherJob launching konsole with an empty
> environment (causing the DISPLAY variable to go missing, causing the
> connection to the X server to fail).
> It has already been fixed in git (and in OpenMandriva packages).
> https://invent.kde.org/frameworks/kio/-/commit/
> 6e7775d315f389df0a440ed62b842ce83dc9a27e

Thank you. I'll fix it with a patch for now.