[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 #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 #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 #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 #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.
[ktouch] [Bug 424080] New: KTouch doesn't start when called from Krunner or launcher, but starts from terminal
https://bugs.kde.org/show_bug.cgi?id=424080
Bug ID: 424080
Summary: KTouch doesn't start when called from Krunner or
launcher, but starts from terminal
Product: ktouch
Version: 20.04
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: general
Assignee: sebastian.gottfr...@posteo.de
Reporter: marava...@yahoo.fr
Target Milestone: ---
SUMMARY
Ktouch doesn't start when called from Krunner or launcher, but starts from
terminal (whithout loading any saved database).
STEPS TO REPRODUCE
1. Try to launch Ktouch by means other than terminal
2. Nothing apparently happens
deleting user config files and reinstalling did not solve the problem.
OBSERVED RESULT
journalctl output hereafter.
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
ADDITIONAL INFORMATION - journalctl -r
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname plasmashell[4104]:
file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { >
Jul 10 23:30:35 hostname systemd[3940]: flatpak-org.kde.ktouch-22442.scope:
Succeeded.
Jul 10 23:30:35 hostname kwin_x11[4037]: qt.qpa.xcb: QXcbConnection: XCB error:
3 (BadWindow), sequence: 18501, resource id: 44040264, major code: 18
(ChangeProperty), minor code: 0
Jul 10 23:30:34 hostname xdg-desktop-portal-kde[15748]: xdp-kde-settings:
key: "smallestReadableFont"
Jul 10 23:30:34 hostname xdg-desktop-portal-kde[15748]: xdp-kde-settings:
group: "org.kde.kdeglobals.General"
Jul 10 23:30:34 hostname xdg-desktop-portal-kde[15748]: xdp-kde-settings: Read
called with parameters:
Jul 10 23:30:34 hostname xdg-desktop-portal-kde[15748]: xdp-kde-settings:
key: "toolBarFont"
Jul 10 23:30:34 hostname xdg-desktop-portal-kde[15748]: xdp-kde-settings:
group:
[systemsettings] [Bug 423289] Settings Module Crash on opening "Configure Window Manager" in window context menu
https://bugs.kde.org/show_bug.cgi?id=423289 Pierre Maraval changed: What|Removed |Added CC||marava...@yahoo.fr -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423289] New: Settings Module Crash on opening "Configure Window Manager" in window context menu
https://bugs.kde.org/show_bug.cgi?id=423289 Bug ID: 423289 Summary: Settings Module Crash on opening "Configure Window Manager" in window context menu Product: systemsettings Version: 5.19.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcmshell Assignee: plasma-b...@kde.org Reporter: marava...@yahoo.fr Target Milestone: --- Application: kcmshell5 (5.19.0) Qt Version: 5.15.0 Frameworks Version: 5.71.0 Operating System: Linux 5.7.1-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: 1) Open Application (tried with several) 2) Access WIndow menu with Alt+F3 or by right clicking on the titlebar 3) Select "More Actions" 4) Select "Configure Window Manager" > Crash notification appears instead of desired configuration window. Other context menu options (Special Windows Settings etc) work fine. The same settings window behaves fine when accessed through the KDE settings or by accessing "Window Rules" from KRunner. The crash can be reproduced every time. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault [KCrash Handler] #4 0x7f9aa5a4ab97 in std::__atomic_base::load (__m=std::memory_order_acquire, this=0x38) at /usr/include/c++/10/bits/atomic_base.h:741 #5 std::atomic::load (__m=std::memory_order_acquire, this=0x38) at /usr/include/c++/10/atomic:523 #6 QAtomicOps::loadAcquire (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:251 #7 QBasicAtomicPointer::loadAcquire (this=0x38) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:255 #8 QBasicAtomicPointer::operator QThreadData* (this=0x38) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:251 #9 QObjectPrivate::setParent_helper (this=0x55efca8f8670, o=0x55efca8f84d0) at kernel/qobject.cpp:2157 #10 0x7f9a933514ff in KWinOptionsSettings::KWinOptionsSettings (this=, parent=, this=, parent=) at /usr/src/debug/kwin5-5.19.0-1.1.x86_64/build/kcmkwin/kwinoptions/kwinoptions_settings.cpp:9 #11 0x7f9a9334ed94 in KFocusConfigStandalone::KFocusConfigStandalone (parent=0x55efca803990, this=0x55efca8f84d0) at /usr/src/debug/kwin5-5.19.0-1.1.x86_64/kcmkwin/kwinoptions/main.cpp:44 #12 KPluginFactory::createInstance (parentWidget=, parent=, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:520 #13 0x7f9aa6bf9c52 in KPluginFactory::create (this=this@entry=0x55efca8d46e0, iface=0x7f9aa52bb298 "KCModule", parentWidget=parentWidget@entry=0x0, parent=parent@entry=0x55efca803990, args=..., keyword=...) at /usr/src/debug/kcoreaddons-5.71.0-1.1.x86_64/src/lib/plugin/kpluginfactory.cpp:133 #14 0x7f9aa6f185dd in KPluginFactory::create (parentWidget=0x0, args=..., keyword=..., parent=0x55efca803990, this=0x55efca8d46e0) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:567 #15 KService::createInstance (parentWidget=0x0, error=0x7ffd8d50e788, args=..., parent=0x55efca803990, this=0x55efca274450) at /usr/include/KF5/KService/kservice.h:557 #16 KService::createInstance (error=0x7ffd8d50e788, args=..., parent=0x55efca803990, this=0x55efca274450) at /usr/include/KF5/KService/kservice.h:532 #17 KCModuleLoader::loadModule (mod=..., report=report@entry=KCModuleLoader::Inline, parent=0x55efca803990, args=...) at /usr/src/debug/kcmutils-5.71.0-1.1.x86_64/src/kcmoduleloader.cpp:120 #18 0x7f9aa6f18fa4 in KCModuleProxyPrivate::loadModule (this=this@entry=0x55efca8133b0) at /usr/src/debug/kcmutils-5.71.0-1.1.x86_64/src/kcmoduleproxy.cpp:94 #19 0x7f9aa6f19638 in KCModuleProxy::realModule (this=this@entry=0x55efca803990) at /usr/src/debug/kcmutils-5.71.0-1.1.x86_64/src/kcmoduleproxy.cpp:67 #20 0x7f9aa6f19ac2 in KCMultiDialog::addModule (this=0x7f9a940086a0, moduleInfo=..., parentItem=0x0, args=...) at /usr/src/debug/kcmutils-5.71.0-1.1.x86_64/src/kcmultidialog.cpp:496 #21 0x55efc8e73ee0 in main (_argc=, _argv=) at /usr/include/qt5/QtCore/qbasicatomic.h:118 [Inferior 1 (process 24696) detached] -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 418707] New: Kontact crashes on first startup
https://bugs.kde.org/show_bug.cgi?id=418707 Bug ID: 418707 Summary: Kontact crashes on first startup Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: marava...@yahoo.fr Target Milestone: --- Application: kontact (5.13.2 (19.12.2)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.7-1-default x86_64 Windowing system: X11 Distribution: openSUSE Tumbleweed -- Information about the crash: Kontact crashes on first run after OpenSUSE VM (VirtualBox) installation. The Account Assistant starts nonetheless. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7b47635a80 (LWP 2436))] Thread 24 (Thread 0x7f7aef325700 (LWP 2537)): #0 0x7f7b53c82795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7b4de54ddc in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in ?? () Thread 23 (Thread 0x7f7aefb26700 (LWP 2536)): #0 0x7f7b5620c9c7 in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f7b561f4b2e in buffered_vfprintf () from /lib64/libc.so.6 #2 0x7f7b561f1a44 in __vfprintf_internal () from /lib64/libc.so.6 #3 0x7f7b562945cf in __fprintf_chk () from /lib64/libc.so.6 #4 0x7f7b49ff8f2e in event_logv_ () from /usr/lib64/libevent-2.1.so.7 #5 0x7f7b49ffbb15 in event_warn () from /usr/lib64/libevent-2.1.so.7 #6 0x7f7b49ffd678 in ?? () from /usr/lib64/libevent-2.1.so.7 #7 0x7f7b4a00e086 in event_base_loop () from /usr/lib64/libevent-2.1.so.7 #8 0x7f7b4de5cad6 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x00010077007c in ?? () #10 0x7f7aefb25990 in ?? () #11 0x7f7aefb25988 in ?? () #12 0x in ?? () Thread 22 (Thread 0x7f7af0327700 (LWP 2508)): #0 0x7f7b5627bacf in poll () from /lib64/libc.so.6 #1 0x7f7b531932fe in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7b5319341f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7b54eabc6b in QEventDispatcherGlib::processEvents (this=0x7f7b2df0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7b54e53bfb in QEventLoop::exec (this=this@entry=0x7f7af0326b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f7b54c7e62e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f7b54c7f6f8 in QThreadPrivate::start (arg=0x558cb330bc60) at thread/qthread_unix.cpp:342 #7 0x7f7b53c7befa in start_thread () from /lib64/libpthread.so.0 #8 0x7f7b562863bf in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f7af1538700 (LWP 2505)): #0 0x7f7b562774fc in read () from /lib64/libc.so.6 #1 0x7f7b531da20f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7b53192e57 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7b531932a2 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f7b5319341f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f7b54eabc6b in QEventDispatcherGlib::processEvents (this=0x7f7b24039870, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f7b54e53bfb in QEventLoop::exec (this=this@entry=0x7f7af1537b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7f7b54c7e62e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7f7b54c7f6f8 in QThreadPrivate::start (arg=0x558cb32e0d90) at thread/qthread_unix.cpp:342 #9 0x7f7b53c7befa in start_thread () from /lib64/libpthread.so.0 #10 0x7f7b562863bf in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f7af1d46700 (LWP 2502)): #0 0x7f7b53192df4 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #1 0x7f7b531932a2 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f7b5319341f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7b54eabc6b in QEventDispatcherGlib::processEvents (this=0x7f7b180020e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7b54e53bfb in QEventLoop::exec (this=this@entry=0x7f7af1d45b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f7b54c7e62e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f7b54c7f6f8 in QThreadPrivate::start (arg=0x558cb329efc0) at thread/qthread_unix.cpp:342 #7 0x7f7b53c7befa in start_thread () from /lib64/libpthread.so.0 #8 0x7f7b562863bf in clone () from /lib64/libc.so.6 Thread 19 (Thread
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 Pierre Maraval changed: What|Removed |Added CC||marava...@yahoo.fr -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 390206] Kontact crash on Kmail message search
https://bugs.kde.org/show_bug.cgi?id=390206 --- Comment #2 from Pierre Maraval <marava...@yahoo.fr> --- The "Filter by status" function and the Tag selector both work flawlessly. Only the search typing field causes the crash. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 390206] Kontact crash on Kmail message search
https://bugs.kde.org/show_bug.cgi?id=390206 --- Comment #1 from Pierre Maraval <marava...@yahoo.fr> --- The "Filter by status" function and the Tag selector both work flawlessly. Only the search typing field causes the crash. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 390206] New: Kontact crash on Kmail message search
https://bugs.kde.org/show_bug.cgi?id=390206 Bug ID: 390206 Summary: Kontact crash on Kmail message search Product: kontact Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: marava...@yahoo.fr Target Milestone: --- Application: kontact (5.5.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.104-39-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Reading mails on Kmail on OpenSUSE Leap 42.3 - Unusual behavior I noticed: Typing into the search field in the message list (of IMAP accounts) and pressing Enter or waiting a little makes Kontact crash. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5882988780 (LWP 26806))] Thread 24 (Thread 0x7f571b7fe700 (LWP 2148)): #0 0x7f587b389478 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5872b889b2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5872b963f6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5872b965e6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5872b9031e in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f574d628700 (LWP 26875)): #0 0x7f587a76bf25 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #1 0x7f587a74637c in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #2 0x7f587a7471d5 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f587a74742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f587fefd1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f587feaabfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f587fceaa29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #9 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f574f769700 (LWP 26870)): #0 0x7f587b3890cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5872b925d9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5872b92d9d in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5872b935c0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5872b9031e in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f5766cdb700 (LWP 26838)): #0 0x7f587f3db37d in poll () at /lib64/libc.so.6 #1 0x7f587a747314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f587a74742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f587fefd1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f587feaabfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f587fceaa29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f57674dc700 (LWP 26837)): #0 0x7f587f3db37d in poll () at /lib64/libc.so.6 #1 0x7f587a747314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f587a74742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f587fefd1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f587feaabfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f587fce5f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f587fceaa29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f587b384724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f587f3e3c1d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f576835f700 (LWP 26836)): #0 0x7f587f3d73fd in read () at /lib64/libc.so.6 #1 0x7f587a787750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f587a746e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f587a7472a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f587a74742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f587fefd1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f587feaabfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7
[korganizer] [Bug 375080] Crash when trying tu use every to-do action and New-Event or New-Journal
https://bugs.kde.org/show_bug.cgi?id=375080 --- Comment #4 from Pierre Maraval <marava...@yahoo.fr> --- Workaround found for Kubuntu 17.04: Update to PIM 16.12.3 (Kontact 5.4.3) by using the backports as described here: http://kubuntu.org/news/kde-pim-update-now-available-for-zesty-zapus-17-04/ Downside: Sorry no backtrace :\ -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 375080] Crash when trying tu use every to-do action and New-Event or New-Journal
https://bugs.kde.org/show_bug.cgi?id=375080 Pierre Maraval <marava...@yahoo.fr> changed: What|Removed |Added CC||marava...@yahoo.fr --- Comment #3 from Pierre Maraval <marava...@yahoo.fr> --- Kubuntu 17.04 Kontact 5.2.3 Steps to reproduce: 1. Open Kontact 2. Go to Calendar 3. Add New Event to remote or local calendar (Crash) 4. Open Kontact again 5. Go to Calendar (Crash) Using Akonadi-console or Kontact Settings one can delete the bugging resource to stop Steps 4 and 5 to lead to a crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358009] Task Manager has problems with rendering its items when placed on a panel in different screen adges
https://bugs.kde.org/show_bug.cgi?id=358009 Pierre Maraval <marava...@yahoo.fr> changed: What|Removed |Added CC||marava...@yahoo.fr --- Comment #3 from Pierre Maraval <marava...@yahoo.fr> --- Created attachment 96693 --> https://bugs.kde.org/attachment.cgi?id=96693=edit Scee -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358009] Task Manager has problems with rendering its items when placed on a panel in different screen adges
https://bugs.kde.org/show_bug.cgi?id=358009 --- Comment #4 from Pierre Maraval <marava...@yahoo.fr> --- Screenshot. Related problem. The windows on the taskbar are not rendered correctly. -- You are receiving this mail because: You are watching all bug changes.
