[neon] [Bug 480179] KDE Connect Daemon crashes
https://bugs.kde.org/show_bug.cgi?id=480179 --- Comment #13 from Jacques Roux --- The update release works. Thanks On Tue, 23 Jan 2024 at 14:24, Jonathan Riddell wrote: > https://bugs.kde.org/show_bug.cgi?id=480179 > > --- Comment #10 from Jonathan Riddell --- > update release that should fix it > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480183] New: KDE Connect always crashes when phone tries to connect after frameworks update
https://bugs.kde.org/show_bug.cgi?id=480183 Bug ID: 480183 Summary: KDE Connect always crashes when phone tries to connect after frameworks update Classification: Applications Product: kdeconnect Version: 23.08.4 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: rouxjacque...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.4) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-14-generic x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Was working before frameworks update. It stopped working after the update. Uninstalled and reinstalled both in KDE Neon and on the phone. Still crashes The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7fd4a27b787e in Device::reloadPlugins() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #5 0x7fd4a27b8591 in Device::addLink(DeviceLink*) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #6 0x7fd4a27b33a1 in Daemon::onNewDeviceLink(DeviceLink*) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #7 0x7fd4a10f4db4 in QtPrivate::QSlotObjectBase::call (a=0x7ffc777b9df0, r=0x7ffc777bb780, this=0x557de44a0910) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x557de410d770, signal_index=3, argv=0x7ffc777b9df0) at kernel/qobject.cpp:3925 #9 0x7fd4a2792903 in LinkProvider::onConnectionReceived(DeviceLink*) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #10 0x7fd4a279d7c4 in LanLinkProvider::addLink(QSslSocket*, DeviceInfo const&) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #11 0x7fd4a279e3cf in LanLinkProvider::encrypted() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #12 0x7fd4a10f4db4 in QtPrivate::QSlotObjectBase::call (a=0x7ffc777ba0f0, r=0x557de410d770, this=0x557de44b7250) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x557de40b7c10, signal_index=16, argv=0x7ffc777ba0f0) at kernel/qobject.cpp:3925 #14 0x7fd4a10ede87 in QMetaObject::activate (sender=sender@entry=0x557de40b7c10, m=m@entry=0x7fd4a0dfa0e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3985 #15 0x7fd4a0d646e4 in QSslSocket::encrypted (this=this@entry=0x557de40b7c10) at .moc/moc_qsslsocket.cpp:317 #16 0x7fd4a0d848b3 in QSslSocketBackendPrivate::continueHandshake (this=0x557de41919f0) at ssl/qsslsocket_openssl.cpp:2045 #17 0x7fd4a0d8b21b in QSslSocketBackendPrivate::startHandshake (this=this@entry=0x557de41919f0) at ssl/qsslsocket_openssl.cpp:1480 #18 0x7fd4a0d8b9e3 in QSslSocketBackendPrivate::transmit (this=0x557de41919f0) at ssl/qsslsocket_openssl.cpp:1136 #19 0x7fd4a10f4de8 in doActivate (sender=0x557de448c1f0, signal_index=3, argv=0x7ffc777bb350) at kernel/qobject.cpp:3937 #20 0x7fd4a10ede87 in QMetaObject::activate (sender=sender@entry=0x557de448c1f0, m=m@entry=0x7fd4a135b960 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3985 #21 0x7fd4a0fe77c4 in QIODevice::readyRead (this=this@entry=0x557de448c1f0) at .moc/moc_qiodevice.cpp:190 #22 0x7fd4a0d3a2ff in QAbstractSocketPrivate::emitReadyRead (channel=0, this=0x557de406f880) at socket/qabstractsocket.cpp:1323 #23 QAbstractSocketPrivate::canReadNotification (this=0x557de406f880) at socket/qabstractsocket.cpp:748 #24 0x7fd4a0d4d439 in QReadNotifier::event (this=, e=) at socket/qnativesocketengine.cpp:1274 #25 0x7fd4a1d6c783 in QApplicationPrivate::notify_helper (this=, receiver=0x557de44b2490, e=0x7ffc777bb490) at kernel/qapplication.cpp:3640 #26 0x7fd4a10bd30a in QCoreApplication::notifyInternal2 (receiver=0x557de44b2490, event=0x7ffc777bb490) at kernel/qcoreapplication.cpp:1064 #27 0x7fd4a1117405 in socketNotifierSourceDispatch (source=0x557de3f747c0) at kernel/qeventdispatcher_glib.cpp:107 #28 0x7fd49fb20d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7fd49fb76258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7fd49fb1e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fd4a111686e in QEventDispatcherGlib::processEvents (this=0x557de3f769b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #32 0x7fd4a10bbc2b in QEventLoop::exec (this=this@entry=0x7ffc777bb6a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #33 0x7fd4a10c41d4 in QCoreApplication::exec () at
[digikam] [Bug 467448] Digikam Crash when closing the app
https://bugs.kde.org/show_bug.cgi?id=467448 --- Comment #8 from Jacques VALLOIS --- Created attachment 159993 --> https://bugs.kde.org/attachment.cgi?id=159993=edit New crash information added by DrKonqi digikam (8.0.0-beta1) using Qt 5.15.8 This app crashes each times I quit. -- Backtrace (Reduced): #4 0x7f14e94f093e in QObject::removeEventFilter(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f14e736c29a in Sonnet::SpellCheckDecorator::~SpellCheckDecorator() () from /lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 #6 0x7f14e736c2cd in Sonnet::SpellCheckDecorator::~SpellCheckDecorator() () from /lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 #7 0x7f14e94e58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f14ea1aa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467448] Digikam Crash when closing the app
https://bugs.kde.org/show_bug.cgi?id=467448 Jacques VALLOIS changed: What|Removed |Added CC||p...@vallois.nom.fr -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 462704] New: Files not opening in new tab when opening via Explorer.
https://bugs.kde.org/show_bug.cgi?id=462704 Bug ID: 462704 Summary: Files not opening in new tab when opening via Explorer. Classification: Applications Product: okular Version: 22.08.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jacques.doub...@lexisnexis.co.za Target Milestone: --- 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 *** STEPS TO REPRODUCE 1. Change settings to open new documents in a tab. 2. double click a pdf file in explorer, then another. OBSERVED RESULT Each file is opened in a new window EXPECTED RESULT Files should be opened in a new tab in the existing open window. It works when doing it via file, open, but not via double clicking on an associated file in Explorer. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 453264] Could not connect to search (Could not connect to host www.googleapis.com: SSL negotiation failed.)
https://bugs.kde.org/show_bug.cgi?id=453264 --- Comment #4 from Jacques Le Bourlot --- (In reply to Robby Stephenson from comment #3) > (In reply to Jacques Le Bourlot from comment #2) > > (In reply to Robby Stephenson from comment #1) > > > What data source are you trying to search? Has it cleared up? > > > > Still the same. > > > > I am trying to reach "Google Book Search". As soon as I click on search I > > get the message: "Could not connect to host www.googleapis.com: SSL > > negotiation failed." > > > > I updated tellico yesterday (included in a " brew update / brew upgrade" > > routine), and it is still the same. > > Everything I've tested is working as expected. This may be something in the > home brew network stack perhaps? I'm just guessing. The error about the SSL > negotiation makes it sound like something in the network or KIO library. > Sorry I can't help more. If any of the other data sources show similar > errors, you'd know for sure it's not Tellico since most of them also use > https I just tested the "Library of Congress" and "Open Library" databases, which are working fine. So it seems to be something specific with google. Thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 453264] Could not connect to search (Could not connect to host www.googleapis.com: SSL negotiation failed.)
https://bugs.kde.org/show_bug.cgi?id=453264 --- Comment #2 from Jacques Le Bourlot --- (In reply to Robby Stephenson from comment #1) > What data source are you trying to search? Has it cleared up? Still the same. I am trying to reach "Google Book Search". As soon as I click on search I get the message: "Could not connect to host www.googleapis.com: SSL negotiation failed." I updated tellico yesterday (included in a " brew update / brew upgrade" routine), and it is still the same. (base) ~ % brew info tellico kde-mac/kde/tellico: stable 3.4.4, HEAD KDE collections manager https://tellico-project.org /opt/homebrew/Cellar/tellico/3.4.4 (402 files, 15.3MB) * Built from source on 2022-05-09 at 10:04:41 (base) ~ % brew config HOMEBREW_VERSION: 3.4.10 ORIGIN: https://github.com/Homebrew/brew HEAD: 3088bbf1a696961cd4202d9ef85ac5f95b977e7c Last commit: 9 days ago Core tap ORIGIN: https://github.com/Homebrew/homebrew-core Core tap HEAD: 9b8051554e2a27e12c5866e108795cc78ef78241 Core tap last commit: 16 hours ago Core tap branch: master HOMEBREW_PREFIX: /opt/homebrew HOMEBREW_CASK_OPTS: [] HOMEBREW_CORE_GIT_REMOTE: https://github.com/Homebrew/homebrew-core HOMEBREW_MAKE_JOBS: 10 Homebrew Ruby: 2.6.8 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby CPU: 10-core 64-bit arm_firestorm_icestorm Clang: 13.1.6 build 1316 Git: 2.32.0 => /Applications/Xcode.app/Contents/Developer/usr/bin/git Curl: 7.79.1 => /usr/bin/curl macOS: 12.3.1-arm64 CLT: 13.3.1.0.1.1648687083 Xcode: 13.3.1 Rosetta 2: false (base) ~ % brew tap homebrew/cask homebrew/core homebrew/services kde-mac/kde -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 453264] New: Could not connect to search (Could not connect to host www.googleapis.com: SSL negotiation failed.)
https://bugs.kde.org/show_bug.cgi?id=453264 Bug ID: 453264 Summary: Could not connect to search (Could not connect to host www.googleapis.com: SSL negotiation failed.) Product: tellico Version: 3.4.4 Platform: Homebrew (macOS) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: jacques.lebour...@obspm.fr Target Milestone: --- I just installe tellico through HomeBrew on a brand new Mac (OS 12.3.1), and could not use the search engine. I receive this error message: Could not connect to host www.googleapis.com: SSL negotiation failed. I have no idea what to do (sorry). STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 446233] New: KDE Partition Manager crash
https://bugs.kde.org/show_bug.cgi?id=446233 Bug ID: 446233 Summary: KDE Partition Manager crash Product: partitionmanager Version: 4.1.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: tux34...@gmail.com Target Milestone: --- Application: partitionmanager (4.1.0) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.11.0-40-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: i tried to partition a usb key, the key was previously partition with W10 and had a corrupted partition table: (cf size +800Gb !!) KDE partition manager crashed Note: the same key is partionned/formatted OK with Gparted $ sudo fdisk -l Disk /dev/sdb: 3.66 GiB, 3911188480 bytes, 7639040 sectors Disk model: Transcend 4GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0a0dff65 Device Boot StartEndSectors Size Id Type /dev/sdb1 1869881445 3571221465 1701340021 811.3G 7a unknown /dev/sdb2 1634566756 3553817813 1919251058 915.2G 72 unknown /dev/sdb30 0 0 0B 0 Empty /dev/sdb4 28049408 28049849442 221K 0 Empty Partition table entries are not in disk order. The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Floating point exception Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f974a9f5800 (LWP 17413))] Thread 6 (Thread 0x7f972700 (LWP 17421)): #0 __GI___libc_read (nbytes=16, buf=0x7f972fffecd0, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=18, buf=0x7f972fffecd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f974caaeb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f974ca65ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f974ca66312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f974ca666f3 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f974057bf8a in ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x7f974ca8fad1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f974d2ad609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f974dda0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f9734ffe700 (LWP 17420)): #0 0x7f974dd93aff in __GI___poll (fds=0x56177a6e04a0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f974ca6636e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f974ca664a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f974ca664f1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f974ca8fad1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f974d2ad609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f974dda0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f97357ff700 (LWP 17419)): #0 0x7f974e33249f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f974ca658ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f974ca6629b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f974ca664a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f974e332583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f974e2d94db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f974fafc05f in ?? () from /lib/x86_64-linux-gnu/libkpmcore.so.9 #7 0x7f974e1129d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f974d2ad609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f974dda0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f9743fff700 (LWP 17417)): #0 __GI___libc_read (nbytes=16, buf=0x7f9743ffeb60, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7f9743ffeb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f974caaeb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f974ca65ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f974ca66312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f974ca664a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f974e332583 in
[kdenlive] [Bug 431505] Kdenlive crashes instantly on Wayland due to EGL format mismatch
https://bugs.kde.org/show_bug.cgi?id=431505 --- Comment #9 from Jacques Noé --- Hello, Thank you for the support. There is a typo in the workaround, it is "QT_QPA_PLATFORM=xcb kdenlive". kdenlive works well now. Best regards, Jacques Noé Le jeu. 17 juin 2021 à 21:04, Kyrylo Bohdanenko a écrit : > https://bugs.kde.org/show_bug.cgi?id=431505 > > --- Comment #8 from Kyrylo Bohdanenko --- > There is a workaround (that defeats the purpose of running. Kdenlive on > Wayland) > > QT_QPA_PLATFORM=xkb kdenlive > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438746] New: Unable to start kdenlive (linux + kde+ wayland)
https://bugs.kde.org/show_bug.cgi?id=438746
Bug ID: 438746
Summary: Unable to start kdenlive (linux + kde+ wayland)
Product: kdenlive
Version: 21.04.1
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: jacques.noe@gmail.com
Target Milestone: ---
SUMMARY:
Each time I start kdenlive, it stops immediately.
Each time there is a colourful window with, in the lower right corner, "version
21.04.1
Then there is a very brief window with kdenlive interface (time-line, ...)
Then kdenlive stops.
Here is the bug report:
--
Application: kdenlive (21.04.1)
Qt Version: 5.15.2
Frameworks Version: 5.82.0
Operating System: Linux 5.12.10-300.fc34.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.5
Distribution: Fedora 34 (KDE Plasma)
-- Information about the crash:
The crash can be reproduced every time.
-- Backtrace:
A useful backtrace could not be generated
---
This happens all the time, including after a freshly booted system without any
prior application.
I have started kdenlive from a terminal and here is the output of the command:
$ kdenlive
No LADSPA plugins were found!
Check your LADSPA_PATH environment variable.
Invalid metadata for "telecide"
Failed to parse "telecide"
Invalid metadata for "avcolour_space"
Failed to parse "avcolour_space"
Invalid metadata for "avcolor_space"
Failed to parse "avcolor_space"
Invalid metadata for "avdeinterlace"
Failed to parse "avdeinterlace"
Invalid metadata for "swscale"
Failed to parse "swscale"
Invalid metadata for "swresample"
Failed to parse "swresample"
Invalid metadata for "glsl.manager"
Failed to parse "glsl.manager"
Invalid metadata for "movit.convert"
Failed to parse "movit.convert"
Invalid metadata for "movit.crop"
Failed to parse "movit.crop"
Invalid metadata for "movit.resample"
Failed to parse "movit.resample"
Invalid metadata for "movit.resize"
Failed to parse "movit.resize"
Invalid metadata for "jack"
Failed to parse "jack"
Invalid metadata for "audiochannels"
Failed to parse "audiochannels"
Invalid metadata for "audioconvert"
Failed to parse "audioconvert"
Invalid metadata for "data_feed"
Failed to parse "data_feed"
Invalid metadata for "imageconvert"
Failed to parse "imageconvert"
Invalid title/identifier for "crop_detect"
Failed to parse "crop_detect"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QObject::disconnect: Unexpected nullptr parameter
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qrc:/qml/timeline.qml:1868:5: QML Connections: Implicitly defined onFoo
properties in Connections are deprecated. Use this syntax instead: function
onFoo() { ... }
QWaylandGLContext::makeCurrent: eglError: 3009, this: 0x557a2d7391e0
QWaylandGLContext::makeCurrent: eglError: 3009, this: 0x557a2fc82b30
QWaylandGLContext::makeCurrent: eglError: 3009, this: 0x7fd8c0007b50
QOpenGLFunctions created with non-current context
The Wayland connection experienced a fatal error: Mauvais descripteur de
fichier
$
--
You are receiving this mail because:
You are watching all bug changes.
[kscreenlocker] [Bug 413087] lockscreen broken when mediacontrols active
https://bugs.kde.org/show_bug.cgi?id=413087 --- Comment #7 from Jacques W --- (In reply to Jacques W from comment #6) > (In reply to sasori.nami from comment #5) > > PS: I've been working since 2019-10-19 with the line commented and can > > confirm that I didn't have the problem once in that time. > > I got the exact same problem. Best way to reproduce is just use > /usr/lib/kscreenlocker_greet --testing command to test. With the line > commented out screen locking works again :-) I use: Mellowplayer Linux 5.3.8-3 Plasma 5.17.2 KDE Frameworks 5.63.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413087] lockscreen broken when mediacontrols active
https://bugs.kde.org/show_bug.cgi?id=413087 Jacques W changed: What|Removed |Added CC||nuclearjo...@gmail.com --- Comment #6 from Jacques W --- (In reply to sasori.nami from comment #5) > PS: I've been working since 2019-10-19 with the line commented and can > confirm that I didn't have the problem once in that time. I got the exact same problem. Best way to reproduce is just use /usr/lib/kscreenlocker_greet --testing command to test. With the line commented out screen locking works again :-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 Jacques changed: What|Removed |Added CC||jacq...@stry.co.za -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 60900] Setting a local raw printer using CUPS does not work
https://bugs.kde.org/show_bug.cgi?id=60900 Dominic Jacques changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Dominic Jacques --- I've entered the bug 15 years ago... Please close it, it is probably no more relevant. Regards, Dominic -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 392053] New: kdenlive keeps on crashing
https://bugs.kde.org/show_bug.cgi?id=392053 Bug ID: 392053 Summary: kdenlive keeps on crashing Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: jacq...@steyn.pro Target Milestone: --- Yesterday I installed kdenlive and it worked perfectly, and really OK. Today it keeps on crashing - working on exactly the same file as yesterday. I searched for solutions, but could not find any. With crashing I mean it stops working, but stays in the GUI. After a short time it greays out. And hangs there for up to 10 minutes. So I have to kill it, and start afresh. It particularly does this when deleting clips imported onto the timeline. BTW - the entire video I am working on is less than a minute. Please advise Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369068] Add tiling to KWin
https://bugs.kde.org/show_bug.cgi?id=369068 Jacques <oelof...@gmail.com> changed: What|Removed |Added CC||oelof...@gmail.com --- Comment #8 from Jacques <oelof...@gmail.com> --- +1 Agreed i had tried i3. Cant live without kwin + tiling. If it would get better upstream support imho would best solution. i3 is too ridged. -- You are receiving this mail because: You are watching all bug changes.
