[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #16 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #15 from Pierre Maraval --- (In reply to Christoph Feck from comment #13 and comment #13) I'm not sure how I ended up with 2 versions. Yes, using the other one worked. Anyway after the August OpenSUSE and KDE updates everything is back to normal. Thank you for the time. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #14 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #13 from Christoph Feck --- If you can provide the information requested in comment 12, please add it. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #12 from Christoph Feck --- Pierre, could you confirm that removing the flatpak version of KTouch and only keeping the version from your package repositories resolve this issue? -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #11 from Alexander Lohnau --- Oh sorry, forget about the reassigning I said, since it was assigned to ktouch in the first place. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #10 from Alexander Lohnau --- It seems like you have installed ktouch with both your package manager and also flatpak. Reassigning this to ktouch, because this is nothing KRunner specific. Maybe just removing the flatpak install fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #9 from Pierre Maraval --- (In reply to Alexander Lohnau from comment #8) > But does it work if you execute the > >/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=ktouch > >org.kde.ktouch > command in a terminal? No, the terminal prints the following /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=ktouch org.kde.ktouch Warning: QT_DEVICE_PIXEL_RATIO is deprecated. Instead use: QT_AUTO_SCREEN_SCALE_FACTOR to enable platform plugin controlled per-screen factors. QT_SCREEN_SCALE_FACTORS to set per-screen DPI. QT_SCALE_FACTOR to set the application global scale factor. Qt: Session management error: Could not open network socket Icon theme "Qogir-dark" not found. qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Could not initialize GLX -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #8 from Alexander Lohnau --- But does it work if you execute the >/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=ktouch >org.kde.ktouch command in a terminal? -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #7 from Pierre Maraval --- (In reply to Pierre Maraval from comment #6) > (In reply to Alexander Lohnau from comment #5) > > Created attachment 130046 [details] > > Different launch options in KRunner > > > > Can you please check for each of the three ways to launch the app if they > > work? > > Thank you for your help. > > - KRunner applications launcher : doesn't work. Nothing visible happens. > - "Normal" icon launcher : nothing visible happens. > - Launching as a shell command from Krunner : works! > > I also found out that the console and shell command launch uses a profiles > database in ~/.local/share/ktouch/ whereas my normal launch used the one in > ~/.var/app/org.kde.ktouch/data/ktouch/. Executing manually /usr/bin/ktouch also runs Ktouch normally with the file in ~/.local/share/ktouch/. The command in my KDE menu is /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=ktouch org.kde.ktouch The only special option in the menu is "Enable Launch Feedback" I installed Ktouch through zypper (or maybe initially through Discover). -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #6 from Pierre Maraval --- (In reply to Alexander Lohnau from comment #5) > Created attachment 130046 [details] > Different launch options in KRunner > > Can you please check for each of the three ways to launch the app if they > work? Thank you for your help. - KRunner applications launcher : doesn't work. Nothing visible happens. - "Normal" icon launcher : nothing visible happens. - Launching as a shell command from Krunner : works! I alsofound out that the console and shell command launch uses a profiles database in ~/.local/share/ktouch/ whereas my normal launch used the one in ~/.var/app/org.kde.ktouch/data/ktouch/. Thank you very much, one Ctrl+C-Ctrl+V later I can use again my painfully formatted customs lessons. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #5 from Alexander Lohnau --- Created attachment 130046 --> https://bugs.kde.org/attachment.cgi?id=130046=edit Different launch options in KRunner Can you please check for each of the three ways to launch the app if they work? -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #4 from Pierre Maraval --- (In reply to Alexander Lohnau from comment #2) > I can't reproduce this on KDE Neon unstable. > > Does this issue persist after a reboot? Yes it does. I run OpenSUSE Tumbleweed (Kernel 5.7.7.1). This problem doesn't appear on Manjaro (I run a 5.6 Kernel though, so maybe it's some update's fault somewhere). (In reply to Alexander Lohnau from comment #3) > Also does it work when starting ktouch as a shell command in > KRunner/Launcher? What do you mean ? Typing Ktouch and pressing Enter results in nothing. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 --- Comment #3 from Alexander Lohnau --- Also does it work when starting ktouch as a shell command in KRunner/Launcher? -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080 Alexander Lohnau changed: What|Removed |Added CC||alexander.loh...@gmx.de --- Comment #2 from Alexander Lohnau --- I can't reproduce this on KDE Neon unstable. Does this issue persist after a reboot? -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 424080] KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080
--- Comment #1 from Pierre Maraval ---
Terminal output when starting from Konsole :
Warning: QT_DEVICE_PIXEL_RATIO is deprecated. Instead use:
QT_AUTO_SCREEN_SCALE_FACTOR to enable platform plugin controlled per-screen
factors.
QT_SCREEN_SCALE_FACTORS to set per-screen DPI.
QT_SCALE_FACTOR to set the application global scale factor.
qCoreApp Application(0x7fffb71ce1e0)
Fetched layout groups from X server:layouts: ("fr", "gb", "ru", "us")
variants: ("", "", "phonetic_fr", "")
Fetched layout groups from X server:layouts: ("fr", "gb", "ru", "us")
variants: ("", "", "phonetic_fr", "")
qrc:/ktouch/qml/main.qml:129:9: QML HomeScreen: Binding loop detected for
property "activeKeyboardLayoutName"
Fetched layout groups from X server:layouts: ("fr", "gb", "ru", "us")
variants: ("", "", "phonetic_fr", "")
qrc:/ktouch/qml/trainingscreen/TrainingScreenToolbar.qml:53:5: QML Connections:
Implicitly defined onFoo properties in Connections are deprecated. Use this
syntax instead: function onFoo() { ... }
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
qrc:/ktouch/qml/homescreen/HomeScreen.qml:33:5: QML Connections: Implicitly
defined onFoo properties in Connections are deprecated. Use this syntax
instead: function onFoo() { ... }
qrc:/ktouch/qml/common/TextArea.qml:41:17: QML Rectangle: Possible anchor loop
detected on fill.
qrc:/ktouch/qml/common/TextArea.qml:41:17: QML Rectangle: Possible anchor loop
detected on fill.
Fetched layout groups from X server:layouts: ("fr", "gb", "ru", "us")
variants: ("", "", "phonetic_fr", "")
qrc:/ktouch/qml/homescreen/KeyboardLayoutMismatchMessage.qml:36:9: QML
GridLayout: Possible anchor loop detected on centerIn.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
qrc:/ktouch/qml/homescreen/KeyboardLayoutMismatchMessage.qml:36:9: QML
GridLayout: Possible anchor loop detected on centerIn.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
--
You are receiving this mail because:
You are watching all bug changes.
