[drkonqi] [Bug 379684] New: drkonqi crashed while reporting a crash of Discover on Kubuntu 17.04
https://bugs.kde.org/show_bug.cgi?id=379684 Bug ID: 379684 Summary: drkonqi crashed while reporting a crash of Discover on Kubuntu 17.04 Product: drkonqi Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: arossi.g...@gmail.com Target Milestone: --- drkonqi has crashed while I was reporting a crash of Discover. I'm on a fresh Kubuntu 17.04 installation. Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb4213c98c0 (LWP 3833))] Thread 3 (Thread 0x7fb405bb3700 (LWP 3835)): #0 0x7fb41cceb18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb418d78576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb418d7868c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb41d60ef2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb41d5b888a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb41d3e5fe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb41e9b25c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fb41d3eac98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb41aca06da in start_thread (arg=0x7fb405bb3700) at pthread_create.c:456 #9 0x7fb41ccf717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fb40ecea700 (LWP 3834)): #0 0x7fb41cceb18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb4184e8c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fb4184ea8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fb411241ed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fb41d3eac98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb41aca06da in start_thread (arg=0x7fb40ecea700) at pthread_create.c:456 #6 0x7fb41ccf717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fb4213c98c0 (LWP 3833)): [KCrash Handler] #6 0x55e9d9bec802 in ?? () #7 0x7fb41dc53b28 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7fb41dc53d56 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7fb41d5e64a9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb41de6104a in QTextDocument::contentsChange(int, int, int) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7fb41dc11fcd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fb41e45935e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fb41e436b59 in QTextEdit::append(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x55e9d9bda99d in ?? () #15 0x7fb41d5e681e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x55e9d9c276e5 in ?? () #17 0x55e9d9bdec02 in ?? () #18 0x7fb41d5e681e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fb41d4f41d8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fb41d4f4630 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb41d5e64a9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fb41d66046e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fb41d5f2a62 in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fb41e29235c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7fb41e299b11 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fb41d5ba8a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fb41d60f3bd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fb418d78377 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7fb418d785e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7fb418d7868c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fb41d60ef0f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fb41d5b888a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fb41d5c0ffc
[Discover] [Bug 370906] Discover crash immediately after system update
https://bugs.kde.org/show_bug.cgi?id=370906 Red changed: What|Removed |Added CC||arossi.g...@gmail.com --- Comment #5 from Red --- I confirm this bug on a fresh installation of Kubuntu 17.04. I can't attach a log because drkonqi crashed too while I was reporting the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478364] New: Plasma crashed after inserting a USB memory stick/flash drive
https://bugs.kde.org/show_bug.cgi?id=478364 Bug ID: 478364 Summary: Plasma crashed after inserting a USB memory stick/flash drive Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: redwirel...@hotmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-13-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Whole Plasma env went dark/came back within 2-5 seconds The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #9 0x7fc04e0d1a2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #11 0x7fc04faaf841 in QQmlTypeLoader::load(QQmlDataBlob*, QQmlTypeLoader::Mode) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fc04fab0180 in QQmlTypeLoader::getType(QUrl const&, QQmlTypeLoader::Mode) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7fc04fa88b34 in QQmlComponentPrivate::loadUrl(QUrl const&, QQmlComponent::CompilationMode) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 [...] #15 0x7fc050930c77 in PlasmaQuick::AppletQuickItem::init() () from /lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478364] Plasma crashed after inserting a USB memory stick/flash drive
https://bugs.kde.org/show_bug.cgi?id=478364 --- Comment #1 from red --- Created attachment 164076 --> https://bugs.kde.org/attachment.cgi?id=164076&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478364] Plasma crashed after inserting a USB memory stick/flash drive
https://bugs.kde.org/show_bug.cgi?id=478364 --- Comment #3 from red --- I tried to send the backtrace, but after almost an hour of 'sending', I shutdown the PC. /red Sent via my Samsung Galaxy S9+ 4G LTE smartphone - follow us on Mastodon+ at @redwirel...@mstdn.plus Original message From: Arjen Hiemstra Date: 12/11/23 9:12 AM (GMT-05:00) To: redwirel...@hotmail.com Subject: [plasmashell] [Bug 478364] Plasma crashed after inserting a USB memory stick/flash drive https://bugs.kde.org/show_bug.cgi?id=478364 Arjen Hiemstra changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||ahiems...@heimr.nl --- Comment #2 from Arjen Hiemstra --- This crash is deep within Qt. Unfortunately without a more clear backtrace and steps to reproduce we cannot really do anything with this. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487594] KWrite automatic encoding detection error
https://bugs.kde.org/show_bug.cgi?id=487594 Red changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Red --- (In reply to Christoph Cullmann from comment #2) > Hmm, can't get that to happen with Kate or KWrite and Frameworks 6.3. > Opens with proper encoding, if fallback is correct, else for me opens as > latin15, which is not correct but correctly shown in the status bar. I can still reproduce this issue on Frameworks 6.3, even though it shows GBK in the bottom right corner, KWrite will fallback to the Fallback encoding option. In Kubuntu, it will switch to the detected text encoding. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 484121] New: CJK Bold font is difficult to read
https://bugs.kde.org/show_bug.cgi?id=484121 Bug ID: 484121 Summary: CJK Bold font is difficult to read Classification: Applications Product: Haruna Version: 1.0.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: wingv5...@protonmail.com Target Milestone: --- Created attachment 167537 --> https://bugs.kde.org/attachment.cgi?id=167537&action=edit CJK bold font STEPS TO REPRODUCE 1. Open a video containing a CJK string name 2. Move the mouse to the left to display the playlist OBSERVED RESULT CJK bold font weight is incorrect and the displayed font is difficult to read. EXPECTED RESULT Display CJK bold font correctly SOFTWARE/OS VERSIONS KDE Plasma Version: 6.02 KDE Frameworks Version: 6 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Red changed: What|Removed |Added CC||wingv5...@protonmail.com --- Comment #38 from Red --- (In reply to terranova from comment #37) > I have opened a merge request: > https://invent.kde.org/plasma/kwin/-/merge_requests/5730 This has been fixed by upstream: https://chromium-review.googlesource.com/c/chromium/src/+/5539621 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487594] New: KWrite automatic encoding detection error
https://bugs.kde.org/show_bug.cgi?id=487594 Bug ID: 487594 Summary: KWrite automatic encoding detection error Classification: Applications Product: kate Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: encoding Assignee: kwrite-bugs-n...@kde.org Reporter: wingv5...@protonmail.com Target Milestone: --- Created attachment 169853 --> https://bugs.kde.org/attachment.cgi?id=169853&action=edit Incorrect display of GBK encoding SUMMARY KWrite successfully identified the text as being encoded in GBK, but it did not actually use the GBK encoding. I have to manually select GBK from the menu in order to display the text correctly. It shows GBK in the bottom right corner, but falls back to a different character encoding. STEPS TO REPRODUCE 1.Create a file encoded in GBK or Shift_JIS 2.Open the file EXPECTED RESULT Display GBK text correctly. I cannot reproduce this issue on Kubuntu with Plasma 5. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2 Qt Version: 6.7 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487594] KWrite automatic encoding detection error
https://bugs.kde.org/show_bug.cgi?id=487594 --- Comment #1 from Red --- Created attachment 169856 --> https://bugs.kde.org/attachment.cgi?id=169856&action=edit Test File -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 379684] New: drkonqi crashed while reporting a crash of Discover on Kubuntu 17.04
https://bugs.kde.org/show_bug.cgi?id=379684 Bug ID: 379684 Summary: drkonqi crashed while reporting a crash of Discover on Kubuntu 17.04 Product: drkonqi Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: arossi.g...@gmail.com Target Milestone: --- drkonqi has crashed while I was reporting a crash of Discover. I'm on a fresh Kubuntu 17.04 installation. Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb4213c98c0 (LWP 3833))] Thread 3 (Thread 0x7fb405bb3700 (LWP 3835)): #0 0x7fb41cceb18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb418d78576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb418d7868c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb41d60ef2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb41d5b888a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb41d3e5fe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb41e9b25c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fb41d3eac98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb41aca06da in start_thread (arg=0x7fb405bb3700) at pthread_create.c:456 #9 0x7fb41ccf717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fb40ecea700 (LWP 3834)): #0 0x7fb41cceb18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb4184e8c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fb4184ea8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fb411241ed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fb41d3eac98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb41aca06da in start_thread (arg=0x7fb40ecea700) at pthread_create.c:456 #6 0x7fb41ccf717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fb4213c98c0 (LWP 3833)): [KCrash Handler] #6 0x55e9d9bec802 in ?? () #7 0x7fb41dc53b28 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7fb41dc53d56 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7fb41d5e64a9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb41de6104a in QTextDocument::contentsChange(int, int, int) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7fb41dc11fcd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fb41e45935e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fb41e436b59 in QTextEdit::append(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x55e9d9bda99d in ?? () #15 0x7fb41d5e681e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x55e9d9c276e5 in ?? () #17 0x55e9d9bdec02 in ?? () #18 0x7fb41d5e681e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fb41d4f41d8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fb41d4f4630 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb41d5e64a9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fb41d66046e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fb41d5f2a62 in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fb41e29235c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7fb41e299b11 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fb41d5ba8a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fb41d60f3bd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fb418d78377 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7fb418d785e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7fb418d7868c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fb41d60ef0f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fb41d5b888a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fb41d5c0ffc
[Discover] [Bug 370906] Discover crash immediately after system update
https://bugs.kde.org/show_bug.cgi?id=370906 Red changed: What|Removed |Added CC||arossi.g...@gmail.com --- Comment #5 from Red --- I confirm this bug on a fresh installation of Kubuntu 17.04. I can't attach a log because drkonqi crashed too while I was reporting the bug. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 378272] New: Commandline feature request
https://bugs.kde.org/show_bug.cgi?id=378272 Bug ID: 378272 Summary: Commandline feature request Product: dragonplayer Version: 2.0 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: sit...@kde.org Reporter: intns...@golgotha.net CC: myr...@kde.org Target Milestone: --- While Dragon Player is great, it could be "more great" simply by adding a couple of simple commandline switches. Commandline switches to be able to run DragonPlayer in fullscreen modeo, to turn on the fullscreen volume meter, and to fully exit/terminate when a video is finished would allow DragonPlayer to be easily integrated into KDE as a fullscreen video player. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395014] New: Downloaded videos do not show
https://bugs.kde.org/show_bug.cgi?id=395014 Bug ID: 395014 Summary: Downloaded videos do not show Product: kdenlive Version: 18.04.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: redhedge.ha...@gmail.com Target Milestone: --- When trying to import downloaded videos for a collab, it does not show up. Instead it just show video recordings. I am using a Windows version Beta of your Editor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446916] KCMs flicker and reload when the cursor passes over their QQuickWidget
https://bugs.kde.org/show_bug.cgi?id=446916 Red Valsen changed: What|Removed |Added CC||o.ozturk...@gmail.com --- Comment #4 from Red Valsen --- This bug affects me too. My laptop screen is 1920x1080 and i don't use scaling factor. This cannot be a distro-specific issue because i use arch based distro. Operating System: EndeavourOS KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-10300H CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446916] QML KCMs and Overview effect thumbnails flicker when cursor passes over them
https://bugs.kde.org/show_bug.cgi?id=446916 --- Comment #14 from Red Valsen --- I have another older laptop ( i5-6300HQ CPU + Intel HD Graphics 530 ) arch based distro with kde and systemsettings works as expected no flickering at all. I think just new Intel graphic cards are effected. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395014] New: Downloaded videos do not show
https://bugs.kde.org/show_bug.cgi?id=395014 Bug ID: 395014 Summary: Downloaded videos do not show Product: kdenlive Version: 18.04.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: redhedge.ha...@gmail.com Target Milestone: --- When trying to import downloaded videos for a collab, it does not show up. Instead it just show video recordings. I am using a Windows version Beta of your Editor -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 378272] New: Commandline feature request
https://bugs.kde.org/show_bug.cgi?id=378272 Bug ID: 378272 Summary: Commandline feature request Product: dragonplayer Version: 2.0 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: sit...@kde.org Reporter: intns...@golgotha.net CC: myr...@kde.org Target Milestone: --- While Dragon Player is great, it could be "more great" simply by adding a couple of simple commandline switches. Commandline switches to be able to run DragonPlayer in fullscreen modeo, to turn on the fullscreen volume meter, and to fully exit/terminate when a video is finished would allow DragonPlayer to be easily integrated into KDE as a fullscreen video player. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 359691] New: "Warn about files modified by foreign processes" no longer working
https://bugs.kde.org/show_bug.cgi?id=359691 Bug ID: 359691 Summary: "Warn about files modified by foreign processes" no longer working Product: kate Version: 3.14.2 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: kdebts8...@iceteks.com Using latest kate version from Mint 17.1 KDE (3.14.2) and noticed that recently, there is no longer a warning when a file has been modified by another process. Reproducible: Always Steps to Reproduce: 1. Open a file in Kate 2. Modify that file using another program, such as vim 3. Switch back to Kate Window and click on the opened file - you should be prompted with a warning asking if you want to reload the file because it changed Actual Results: Nothing. It is now possible to hit save and overwrite any changes that were made in the other program. (ex: coding remotely then coming back home to continue coding) Expected Results: There should be a prompt saying that the file changed, asking what to do with it All files are stored via NFS. It's worked before. On a side note, the "Disable swap files syncing" option also does not work and can make using KATE with NFS files unbearable if there is a backup job or other latency on the file server. I am wondering if there is a bigger issue here, perhaps none of the options are actually registering. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 359691] "Warn about files modified by foreign processes" no longer working
https://bugs.kde.org/show_bug.cgi?id=359691 Red Squirrel changed: What|Removed |Added CC||kdebts8...@iceteks.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 359691] "Warn about files modified by foreign processes" no longer working
https://bugs.kde.org/show_bug.cgi?id=359691 Red Squirrel changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Red Squirrel --- I believed it was only doing it with NFS but I just tested again to confirm and it seems to be working now. It's possible it was fixed since the time I submitted the report. I'll close the report. The disable swap file syncing issue still exists though, but I will open a new bug report for that. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 367941] New: Each keystroke generates a disk write
https://bugs.kde.org/show_bug.cgi?id=367941 Bug ID: 367941 Summary: Each keystroke generates a disk write Product: kate Version: 3.14.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kdebts8...@iceteks.com As title, each keystroke generates disk I/O, it writes to a .*.kate-swp file where * is the file name. This causes typing in Kate to be very slow if the file is located on a network and if the network is experiencing any kind of latency (ex: VPN over internet or backup jobs happening). There is an option under "Configure Kate, Open/Save, advanced" called "Disable swap file syncing" which I presume is to disable this feature, but whether the option is on or not, it still does it. I read previous bug reports and they were closed as this being by design. If that's the case, can you please add another option to disable this completely and force the data to be in memory and only save when the save button is set? Optionally add an option to just have the swap file somewhere else, such as a local directory. (this would kill SSDs though... maybe a local ram disk?) This issue makes Kate unusable over a network. It is nice to store files over a SMB or NFS volume and work on them directly while they are on a central file server that uses raid, has backups etc while not having to worry about doing any of that at the client level. How to reproduce: open a file that is stored on a NFS server, create a high load on that server, such as a dd operation on the same raid array. Hold down a key. It will be extremely choppy. Optionally a packet sniffer can be used to confirm many NFS writes while the key is being held down. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 367941] Each keystroke generates a disk write
https://bugs.kde.org/show_bug.cgi?id=367941 --- Comment #2 from Red Squirrel --- That's great to know. I'm on Mint 17.1, is there an easy way to do that update without having to do a clean install or mess with 3rd party repos? Worse case scenario I have been thinking of updating to latest Mint version so I presume it will be included. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 359691] New: "Warn about files modified by foreign processes" no longer working
https://bugs.kde.org/show_bug.cgi?id=359691 Bug ID: 359691 Summary: "Warn about files modified by foreign processes" no longer working Product: kate Version: 3.14.2 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: kdebts8...@iceteks.com Using latest kate version from Mint 17.1 KDE (3.14.2) and noticed that recently, there is no longer a warning when a file has been modified by another process. Reproducible: Always Steps to Reproduce: 1. Open a file in Kate 2. Modify that file using another program, such as vim 3. Switch back to Kate Window and click on the opened file - you should be prompted with a warning asking if you want to reload the file because it changed Actual Results: Nothing. It is now possible to hit save and overwrite any changes that were made in the other program. (ex: coding remotely then coming back home to continue coding) Expected Results: There should be a prompt saying that the file changed, asking what to do with it All files are stored via NFS. It's worked before. On a side note, the "Disable swap files syncing" option also does not work and can make using KATE with NFS files unbearable if there is a backup job or other latency on the file server. I am wondering if there is a bigger issue here, perhaps none of the options are actually registering. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 359691] "Warn about files modified by foreign processes" no longer working
https://bugs.kde.org/show_bug.cgi?id=359691 Red Squirrel changed: What|Removed |Added CC||kdebts8...@iceteks.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 359691] "Warn about files modified by foreign processes" no longer working
https://bugs.kde.org/show_bug.cgi?id=359691 Red Squirrel changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Red Squirrel --- I believed it was only doing it with NFS but I just tested again to confirm and it seems to be working now. It's possible it was fixed since the time I submitted the report. I'll close the report. The disable swap file syncing issue still exists though, but I will open a new bug report for that. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 367941] New: Each keystroke generates a disk write
https://bugs.kde.org/show_bug.cgi?id=367941 Bug ID: 367941 Summary: Each keystroke generates a disk write Product: kate Version: 3.14.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kdebts8...@iceteks.com As title, each keystroke generates disk I/O, it writes to a .*.kate-swp file where * is the file name. This causes typing in Kate to be very slow if the file is located on a network and if the network is experiencing any kind of latency (ex: VPN over internet or backup jobs happening). There is an option under "Configure Kate, Open/Save, advanced" called "Disable swap file syncing" which I presume is to disable this feature, but whether the option is on or not, it still does it. I read previous bug reports and they were closed as this being by design. If that's the case, can you please add another option to disable this completely and force the data to be in memory and only save when the save button is set? Optionally add an option to just have the swap file somewhere else, such as a local directory. (this would kill SSDs though... maybe a local ram disk?) This issue makes Kate unusable over a network. It is nice to store files over a SMB or NFS volume and work on them directly while they are on a central file server that uses raid, has backups etc while not having to worry about doing any of that at the client level. How to reproduce: open a file that is stored on a NFS server, create a high load on that server, such as a dd operation on the same raid array. Hold down a key. It will be extremely choppy. Optionally a packet sniffer can be used to confirm many NFS writes while the key is being held down. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 367941] Each keystroke generates a disk write
https://bugs.kde.org/show_bug.cgi?id=367941 --- Comment #2 from Red Squirrel --- That's great to know. I'm on Mint 17.1, is there an easy way to do that update without having to do a clean install or mess with 3rd party repos? Worse case scenario I have been thinking of updating to latest Mint version so I presume it will be included. -- You are receiving this mail because: You are watching all bug changes.
