[frameworks-kwindowsystem] [Bug 384760] absence of proper (current) titles in Task Manager where, for example, many windows are opened in rapid succession by Firefox or SeaMonkey
https://bugs.kde.org/show_bug.cgi?id=384760 --- Comment #4 from Martin Flöser --- I asked for the complete xprop output. Please don't remove anything, I need the complete output. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384784] New: kmail crash when selecting enable system tray icon
https://bugs.kde.org/show_bug.cgi?id=384784 Bug ID: 384784 Summary: kmail crash when selecting enable system tray icon Product: kmail2 Version: 5.4.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: bugz...@free.fr Target Milestone: --- Application: kmail (5.4.3) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.43-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: The kmail icon in system tray had disapeared while it was enable in Settings>Configure kmail>system tray and mail was not read in kmail. So I selected it and pressed apply and had a crash -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2d5e55b840 (LWP 14268))] Thread 28 (Thread 0x7f2c2ea29700 (LWP 16727)): #0 0x7f2d800ecc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2d7b3d8c23 in JSC::GCThread::gcThreadMain() () from /lib64/libQt5WebKit.so.5 #2 0x7f2d7b6f8141 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQt5WebKit.so.5 #3 0x7f2d800e766d in start_thread () from /lib64/libpthread.so.0 #4 0x7f2d89952e4d in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f2d23fff700 (LWP 16726)): #0 0x7f2d800ecc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2d7b3d7bf4 in JSC::BlockAllocator::blockFreeingThreadMain() () from /lib64/libQt5WebKit.so.5 #2 0x7f2d7b6f8141 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQt5WebKit.so.5 #3 0x7f2d800e766d in start_thread () from /lib64/libpthread.so.0 #4 0x7f2d89952e4d in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f2d3d7fa700 (LWP 16725)): #0 0x7f2d800ecc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2d7b6c929b in WTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5WebKit.so.5 #2 0x7f2d7b6c92d9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5WebKit.so.5 #3 0x7f2d800e766d in start_thread () from /lib64/libpthread.so.0 #4 0x7f2d89952e4d in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f2c73c14700 (LWP 15297)): #0 0x7f2d800ecc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2d76b426ef in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f2d76b42e10 in base::SequencedWorkerPool::Worker::Run() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f2d76b42fe0 in base::SimpleThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f2d76b3fb6d in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f2d800e766d in start_thread () from /lib64/libpthread.so.0 #6 0x7f2d89952e4d in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f2cf51bc700 (LWP 15289)): #0 0x7f2d800ecc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2d71f88234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f2d71f88279 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f2d800e766d in start_thread () from /lib64/libpthread.so.0 #4 0x7f2d89952e4d in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f2cf663d700 (LWP 15271)): #0 0x7ffed359fb1b in clock_gettime () #1 0x7f2d89960a06 in clock_gettime () from /lib64/libc.so.6 #2 0x7f2d8a2f8166 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7f2d8a464aa9 in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7f2d8a464ff5 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7f2d8a46635e in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #6 0x7f2d7f8c422d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #7 0x7f2d7f8c4bc3 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #8 0x7f2d7f8c4d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #9 0x7f2d8a466e2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #10 0x7f2d8a41249a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #11 0x7f2d8a24c3bc in QThread::exec() () from /lib64/libQt5Core.so.5 #12 0x7f2d8a250ff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #13 0x7f2d800e766d in start_thread () from /lib64/libpthread.so.0 #14 0x7f2d89952e4d in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f2cfaffd700 (LWP 14632)): #0 0x7f2d800ecc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2d76a58830 in mojo:
[kaddressbook] [Bug 384736] Version 5.6.1 : contact modification not recorded
https://bugs.kde.org/show_bug.cgi?id=384736 --- Comment #2 from Alex6 --- Le dimanche 17 septembre 2017 08:39:14 CEST, vous avez écrit : > https://bugs.kde.org/show_bug.cgi?id=384736 > > Laurent Montel changed: > >What|Removed |Added > > CC||mon...@kde.org > > --- Comment #1 from Laurent Montel --- > Did you click on "add address" button ? > > No, only trying to edit a contact to modify location. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 Antonio Rojas changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- CC||aro...@archlinux.org Status|RESOLVED|REOPENED --- Comment #30 from Antonio Rojas --- Still reproducible after commit d0a5f4159cddcca656ca8bbcbd6e551e3499c166 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 382208] Automatical adjustment for the icons in places panel
https://bugs.kde.org/show_bug.cgi?id=382208 --- Comment #8 from Matthias --- In an up to date KaOS installation, it works still. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 354330] Renaming a file does not scroll to the selected file
https://bugs.kde.org/show_bug.cgi?id=354330 --- Comment #7 from Elvis Angelaccio --- Git commit 478f404b8abf924a0e3e21bbf1dd49aefbe47672 by Elvis Angelaccio, on behalf of Emirald Mateli. Committed on 17/09/2017 at 09:12. Pushed by elvisangelaccio into branch 'Applications/17.08'. Keep renamed file(s) in view When renaming a file, if its new name causes it to scroll out of view, Dolphin will not scroll to the location of the new file. This patch aims to address that. This affects all view modes. Test Plan: 1. Have many files in a directory (or several files, just zoom in a lot) 2. Rename a file so that it will move out of view Differential Revision: https://phabricator.kde.org/D6312 M +19 -3src/views/dolphinview.cpp M +9-0src/views/dolphinview.h M +9-0src/views/renamedialog.cpp M +4-0src/views/renamedialog.h https://commits.kde.org/dolphin/478f404b8abf924a0e3e21bbf1dd49aefbe47672 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384075] korganizer crashes when selecting a calendar to be shown in agenda/day/week/month view (regression 17.08.*)
https://bugs.kde.org/show_bug.cgi?id=384075 --- Comment #6 from Achim Bohnet --- I've exported the problemetic caldav Calendar folder with Thunderbird and imported it with korganizer 5.6.1 into a new Calendar. => Loading the ics calendar worked without problem and I could move in the aganda view forward and backfard in time. Bug: after I exited korganizer and tried to start it again -> Crash. WORDAROUND: I've removed the viewing of the imported calendar in korganizerrc GlobalCollationSelection and korganizer start again. Bug: selecting the newly created imported-calendar -> Crash. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 354330] Renaming a file does not scroll to the selected file
https://bugs.kde.org/show_bug.cgi?id=354330 --- Comment #8 from Elvis Angelaccio --- I'm leaving this bug open because there is still a corner case not fixed by the above patch: 1. rename something so that it goes out of the view 2. dolphin scrolls the view 3. press CTRL+Z 4. dolphin should scroll the view back to the original place but it doesn't. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384785] New: Properties windows shrink when you move it, instead of having scroll bars
https://bugs.kde.org/show_bug.cgi?id=384785 Bug ID: 384785 Summary: Properties windows shrink when you move it, instead of having scroll bars Product: kdenlive Version: git-master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: paj...@gmail.com Target Milestone: --- Created attachment 107887 --> https://bugs.kde.org/attachment.cgi?id=107887&action=edit properties window shrink Tittle and attachment -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 384201] SMB3 is broken in Dolphin
https://bugs.kde.org/show_bug.cgi?id=384201 Christopher Rüprich changed: What|Removed |Added CC||i...@con-data.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384786] New: Kwin crashed when saving multiple pictures in Canon DPP (Wine)
https://bugs.kde.org/show_bug.cgi?id=384786 Bug ID: 384786 Summary: Kwin crashed when saving multiple pictures in Canon DPP (Wine) Product: kwin Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: ld_second...@outlook.com Target Milestone: --- And now I lost the ‘Close’ button. Also when right-clicking the title bar, the ‘close’ option is grayed out. Plasma version 4.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384787] New: Cant add speed to clips
https://bugs.kde.org/show_bug.cgi?id=384787 Bug ID: 384787 Summary: Cant add speed to clips Product: kdenlive Version: git-master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: paj...@gmail.com Target Milestone: --- Im sorry, i feel im opening bugs every single day... Its just that im using it every single day :) steps to reproduce: new video, add clip, select clip, click effect, search speed, double click speed, nothing happens. Drag speed into clip in project bin, nothing happens If you try with any other effect, it works I was trying to reverse a clip by giving it -100% speed. It works if you do it on the timeline, but Its a very short clip and I wanted the effect to apply to the clip instead of the timeline Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 384788] New: KInfoCentre crash on switching between display servers tree items
https://bugs.kde.org/show_bug.cgi?id=384788 Bug ID: 384788 Summary: KInfoCentre crash on switching between display servers tree items Product: kinfocenter Version: 5.8.7 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: dcko...@gmail.com Target Milestone: --- Application: kinfocenter (5.8.7) Qt Version: 5.7.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-33-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: I was switching back and forth in the infocenter between wayland, x-server and opengl. The crash can be reproduced sometimes. -- Backtrace: Application: Info Center (kinfocenter), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe6103f48c0 (LWP 2528))] Thread 4 (Thread 0x7fe5ebfff700 (LWP 2533)): #0 0x7fe60d64070d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe608d7438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe608d7449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe60df6075b in QEventDispatcherGlib::processEvents (this=0x7fe5e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe60df0b0ba in QEventLoop::exec (this=this@entry=0x7fe5ebffece0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe60dd3af64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fe60ce1cbf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fe60dd3fb48 in QThreadPrivate::start (arg=0x1cde6c0) at thread/qthread_unix.cpp:368 #8 0x7fe60ad166ba in start_thread (arg=0x7fe5ebfff700) at pthread_create.c:333 #9 0x7fe60d64c3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fe5faa55700 (LWP 2531)): #0 0x7fe60d64070d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe608d7438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe608d7449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe60df6075b in QEventDispatcherGlib::processEvents (this=0x7fe5ec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe60df0b0ba in QEventLoop::exec (this=this@entry=0x7fe5faa54cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe60dd3af64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fe610537735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fe60dd3fb48 in QThreadPrivate::start (arg=0x7fe6105abd60) at thread/qthread_unix.cpp:368 #8 0x7fe60ad166ba in start_thread (arg=0x7fe5faa55700) at pthread_create.c:333 #9 0x7fe60d64c3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fe5ff002700 (LWP 2530)): #0 0x7fe60d64070d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fe6078bbc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fe6078bd8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fe601559d79 in QXcbEventReader::run (this=0x1a34f60) at qxcbconnection.cpp:1343 #4 0x7fe60dd3fb48 in QThreadPrivate::start (arg=0x1a34f60) at thread/qthread_unix.cpp:368 #5 0x7fe60ad166ba in start_thread (arg=0x7fe5ff002700) at pthread_create.c:333 #6 0x7fe60d64c3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fe6103f48c0 (LWP 2528)): [KCrash Handler] #6 0x7fe6078bc82d in xcb_send_request64 () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #7 0x7fe6078bc969 in xcb_send_request () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #8 0x7fe6078c1723 in xcb_get_geometry () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #9 0x7fa5e2415e2b in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #10 0x7fa5e24151be in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #11 0x7fa5e2415327 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #12 0x7fa5e240086c in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #13 0x7fa5e28a7acc in get_gl_info_egl (scrnum=0, after=0x3d00ae0, l1=0x22f1aa0, dpy=0x2b81ee0) at /workspace/build/Modules/opengl/opengl.cpp:820 #14 GetInfo_OpenGL (treeWidget=0x2af9ed0) at /workspace/build/Modules/opengl/opengl.cpp:937 #15 0x7fa5e28a8bea in KCMOpenGL::KCMOpenGL (this=0x27ef580, parent=) at /workspace/build/Modules/opengl/opengl.cpp:79 #16 0x7fa5e28a9beb in KPluginFactory::createInstance (parentWidget=, parent=, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:479 #17 0x7fe60f082a6f in KPluginFactory::create(char const*, QWidget*, QObject*, QList co
[plasmashell] [Bug 384789] New: UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 Bug ID: 384789 Summary: UI elements on wayland are huge Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: fab...@ritter-vogt.de Target Milestone: 1.0 It looks like the scaling computations on wayland went wrong: https://openqa.opensuse.org/tests/487014#step/start_wayland_plasma5/27 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 384483] libexiv2 from Neon repo crashes Gwenview, fixed upstream
https://bugs.kde.org/show_bug.cgi?id=384483 Mahendra Tallur changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Mahendra Tallur --- Issue fixed ! Thank you Jonathan for applying this patch. It'll be in the next libexiv2 version. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 --- Comment #7 from David Edmundson --- Note that there are two code paths for X and wayland, all your comments are about the X one. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 --- Comment #6 from David Edmundson --- You can't be selecting 1.2... Either you're not running master or you're not runing wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384769] Kwin: Mouse pointer inaccurate when closing/resizing windows due to scaling factor
https://bugs.kde.org/show_bug.cgi?id=384769 --- Comment #4 from David Edmundson --- So the bug is in the DRM hardware cursor rendering, we're not scaling it, but we are implicitly scaling the hotpost. Leading to everything being ever so slighlty off, particularly when you change cursors. The obvious fix is that I should scale the cursor, but then I hit this damn issue again of the user needing different settings depending on whether they're on Wayland or not. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 384790] New: "Places" in Dolphin disappear
https://bugs.kde.org/show_bug.cgi?id=384790 Bug ID: 384790 Summary: "Places" in Dolphin disappear Product: kdeconnect Version: 1.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: r...@activeservice.co.uk Target Milestone: --- Whenever a kdeconnect device attaches or detaches, all the default places in Dolphin's panel disappear. This includes Home, Root, etc, all under Recently Saved and Search For, but not other Devices. The items that disappear are everything that's listed only in ~/.kde/share/apps/kfileplaces/bookmarks.xml, what remains is what's listed in ~/.local/share/user-places.xbel. At the instant it happens, ~/.local/share/user-places.xbel gets updated. I've looked at other bugs related to Dolphin Places, but they don't describe what I'm seeing. It doesn't happen when other devices (USB drives etc.) attach or detach, only kdeconnect. I'm running Kubuntu 16.04 LTS with KDE5. kdelibs is version 4:4.14.22. Let me know if you need any other info. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384786] Kwin crashed when saving multiple pictures in Canon DPP (Wine)
https://bugs.kde.org/show_bug.cgi?id=384786 Martin Flöser changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- I'm sorry, but we don't support version 4.x any more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384769] Kwin: Mouse pointer inaccurate when closing/resizing windows due to scaling factor
https://bugs.kde.org/show_bug.cgi?id=384769 --- Comment #5 from Martin Flöser --- @David: as the cursor is just a wl_surface: maybe we do get the information of whether it should be scaled as well. If the applications send us a scale on the cursor we could incorporate that in the DRM platform. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384791] New: Option for unbuffered output
https://bugs.kde.org/show_bug.cgi?id=384791 Bug ID: 384791 Summary: Option for unbuffered output Product: kdevelop Version: 5.1.2 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Output Views Assignee: kdevelop-bugs-n...@kde.org Reporter: s...@lynxlynx.info Target Milestone: --- The Run and Debug output windows seem to do some internal buffering, in effect delaying display of the output until the buffer threshold is reached. I'd like to be able to disable this behaviour. Or force a flush. I have a program that logs a lot of debug info to stdout and it's annoying to not be able to read it when I need it. So much, that I have to do such debugging outside of kdevelop. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 378987] Yakuake window Freezes when running command and exiting
https://bugs.kde.org/show_bug.cgi?id=378987 --- Comment #4 from Mustaqim --- (In reply to Alexander Mentyu from comment #3) > (In reply to Mustaqim from comment #2) > > I am on archlinux, It occurs with any command. If it's a single session, and > > I run exit it will occur. It happened this morning, I ran `sudo pacman -Syu` > > and after updating, I exited `exit`, and it froze for 2 seconds and then > > retracted. > > > > It does not happen if I have a second session running. Then it exits > > normally with no freeze. > > Try to quit Yakuake, rename it's conf file ~/.config/yakuakerc, and launch > Yakuake with default configuration. Is it still freezes? Sorry for the late reply, it still occurs all default settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Can you tell me if Qt_force_font_dpi is set? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #2 from Fabian Vogt --- (In reply to David Edmundson from comment #1) > Can you tell me if Qt_force_font_dpi is set? The previous test module sets that up, so yes: https://openqa.opensuse.org/tests/487014#step/plasma5_force_96dpi/4 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 384792] New: Unwanted row height changes
https://bugs.kde.org/show_bug.cgi?id=384792 Bug ID: 384792 Summary: Unwanted row height changes Product: ksysguard Version: 5.10.5 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: bertyf...@gmail.com Target Milestone: --- Created attachment 107888 --> https://bugs.kde.org/attachment.cgi?id=107888&action=edit a firefox process on top of the list Firefox processes are launched with a bunch of garbage in their arguments. I have the Command column enabled and when one of such firefox processes is on top of the list the height of all rows in the table changes in response to, I presume, line breaks in the command string, even if they are not displayed. Another possible reason is that some of the characters in that string are rendered with a font that has different line height. But no matter what the real reason is I think such behavior is unwanted and should be considered as a bug, i.e. the row height shouldn't change to fit in the invisible text. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 384792] Unwanted row height changes
https://bugs.kde.org/show_bug.cgi?id=384792 --- Comment #1 from Eugene --- Created attachment 107889 --> https://bugs.kde.org/attachment.cgi?id=107889&action=edit the same process, but not the first row -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 317325] Severe problem with "File > Send File"
https://bugs.kde.org/show_bug.cgi?id=317325 Andrei A. Lomov changed: What|Removed |Added Platform|Debian stable |Debian testing --- Comment #2 from Andrei A. Lomov --- Still actual in Buster: konqueror 4.14.25, kmail 5.2.3 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 384616] buffer used by "Copy Link URL" entry in a link context menu
https://bugs.kde.org/show_bug.cgi?id=384616 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #3 from David Edmundson --- One thing that's changed very recently is I have different font DPI config vars for Wayland and x. That link seemed to show X? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384793] New: kdenlive does not preserve normalization gain on save/load or render
https://bugs.kde.org/show_bug.cgi?id=384793 Bug ID: 384793 Summary: kdenlive does not preserve normalization gain on save/load or render Product: kdenlive Version: 17.04.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: mag...@minimum.se Target Milestone: --- Steps to reproduce: - Start kdenlive - Add clip "music.mp3" and "video.mp4" to your project. (You can download these exact files from https://utby.minimum.se/index.php/s/7cBpBNob6xaDXdA .. although I suspect this bug has nothing to do with these files) - Put music.mp3 on track "Audio #1" - Put video.mp4 on track "Video #1" - Apply effect "Audio correction" -> "Normalize" to video track - Note that the normalization works, and is by default set to 100% gain. - Sound of ocean waves are amplified as expected. - Save project to a new file, quit kdenlive. - Start kdenlive, load project. - Observe that the audio of video track is now "muted" when you play the project. This is because kdenlive adjusts the gain to 0% when it loads the project, even though it was saved as 100% gain. The same thing happens if you render your project. E.g, apply an Audio Normalize effect, render movie and the output have muted video audio, even if the audio is there when you play it through kdenlive preview. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384793] kdenlive does not preserve normalization gain on save/load or render
https://bugs.kde.org/show_bug.cgi?id=384793 --- Comment #1 from Magnus --- Summary of bug: kdenlive does not preserve the gain parameter to audio normalization when it saves (or loads) projects. This results in a behaviour where a saved project is not the same project when you load it later. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 384616] buffer used by "Copy Link URL" entry in a link context menu
https://bugs.kde.org/show_bug.cgi?id=384616 Rex Dieter changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Rex Dieter --- I'll have to test how other browsers treat this. My suspicions are that most will behave like khtml. If so, then I'd have to strongly recommend that webengine part ought to follow suit. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 366561] Baloo file daemon starts with non-KDE Desktop environments
https://bugs.kde.org/show_bug.cgi?id=366561 --- Comment #3 from Christoph Feck --- The baloo daemon tracks files deletions and moves, so it should run regardless of the desktop you use. Additionally, you can run KDE applications even if you did not start the Plasma desktop. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 384039] KConfig::groupList() returns deleted group
https://bugs.kde.org/show_bug.cgi?id=384039 --- Comment #3 from Christoph Feck --- To upload patches, use https://phabricator.kde.org/differential/diff/create/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 347564] Crash in KPluginMetadata on kded5 startup
https://bugs.kde.org/show_bug.cgi?id=347564 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Christoph Feck --- To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 347564] Crash in KPluginMetadata on kded5 startup
https://bugs.kde.org/show_bug.cgi?id=347564 Kai Uwe Broulik changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Kai Uwe Broulik --- I think this fixed itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 361426] Crash in KIconLoaderPrivate::findCachedPixmapWithPath and KSharedDataCache
https://bugs.kde.org/show_bug.cgi?id=361426 --- Comment #18 from Christoph Feck --- Maybe bleachbit was not updated to the new KF5 location ~/.cache/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 384037] DesktopFileParser::convert: incorrect service file name?
https://bugs.kde.org/show_bug.cgi?id=384037 --- Comment #4 from Christoph Feck --- Michael, does comment #3 provide the requested information? Please set the bug status. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384066] Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066 Christoph Feck changed: What|Removed |Added Assignee|fa...@kde.org |se...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 382419] Krusader (sometimes) crashes when moving file from ext4 partition to fat32 partition
https://bugs.kde.org/show_bug.cgi?id=382419 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #7 from Christoph Feck --- No response, changing status. If you have new information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 384149] Dolphin Action Menu entries appear in random order
https://bugs.kde.org/show_bug.cgi?id=384149 --- Comment #2 from Christoph Feck --- If you can provide the information requested in comment #1, please add it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #4 from Fabian Vogt --- (In reply to David Edmundson from comment #3) > One thing that's changed very recently is I have different font DPI config > vars for Wayland and x. > > That link seemed to show X? Yes, it sets the checkbox on X so that the scale after switching to wayland is already correct. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379956] Can't open a file with a shell script from digiKam
https://bugs.kde.org/show_bug.cgi?id=379956 --- Comment #6 from Andrius --- Maik, I played a bit more with opening files from digikam with my scripts on a non KDE machine and here is what I found so far: - for background scripts (scripts that do not need a terminal window): right click - open with - /path/to/script.sh works just fine - if you want to open a script in a terminal: right click - open with - xterm -e /path/to/script.sh works just fine (make sure xterm is installed in your system) - weird thing that the same command but with mate-terminal or gnome-terminal does not work. No arguments (%F) being passed to the script. Not sure if it is digikam related or the terminal related issue. Same command from Caja(Nautilus) works just fine. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 383950] Just some graphical errors
https://bugs.kde.org/show_bug.cgi?id=383950 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 364766 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 Christoph Feck changed: What|Removed |Added CC||andr...@schoeppach.de --- Comment #7 from Christoph Feck --- *** Bug 383950 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384794] New: instable behavior; lost recents open files list
https://bugs.kde.org/show_bug.cgi?id=384794 Bug ID: 384794 Summary: instable behavior; lost recents open files list Product: kate Version: 16.04 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: r...@vivointernetdiscada.com.br Target Milestone: --- * Kate especific version: 16.04.3 (Mint 18.2 KDE). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384795] New: Krita expands beyond window when image in use (GL Open ticked only).
https://bugs.kde.org/show_bug.cgi?id=384795 Bug ID: 384795 Summary: Krita expands beyond window when image in use (GL Open ticked only). Product: krita Version: 3.2.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: mrs.elizabeth@gmail.com Target Milestone: --- Forum post about issue (Includes images): https://forum.kde.org/viewtopic.php?f=305&t=141813&p=381269#p381269 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384795] Krita expands beyond window when image in use (GL Open ticked only).
https://bugs.kde.org/show_bug.cgi?id=384795 wolthera changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Hey, this is a bug in the intel drivers that we're fixing for 3.3. Because it is intel sepcific, it actually counts as a dupkicate of the intel bug, so I'll mark it as that. *** This bug has been marked as a duplicate of bug 360601 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360601] [INTEL] Various issues caused by buggy Intel drivers.
https://bugs.kde.org/show_bug.cgi?id=360601 wolthera changed: What|Removed |Added CC||mrs.elizabeth@gmail.com --- Comment #65 from wolthera --- *** Bug 384795 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 354183] Sonnet uses the wrong path for configuration files...
https://bugs.kde.org/show_bug.cgi?id=354183 Christoph Feck changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- Sonnet uses QSettings instead of KConfig, to be able to work in pure Qt applications. The QSettings class mandates an 'organization' name. You can see it with many other Qt applications, such as Trojita, Minitube, etc. Some applications simply use the applications name as the organization name, e.g. sqlitebrowser, smplayer etc. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 356974] Support for syntax highlighted fenced code blocks in Markdown
https://bugs.kde.org/show_bug.cgi?id=356974 --- Comment #3 from Christoph Feck --- Please upload patches to https://phabricator.kde.org/differential/diff/create/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #5 from David Edmundson --- I now have that option on X, it affects X If you set that option on wayland, it affects wayland Reasons for that in the commit; it's not something I want to undo unless we have a reason. But since ages it would default to 96dpi if this value wasn't set (so that users don't need to do this stage). The other possibility is that we're hitting wayland scaling. Easy way to tell is open xterm and see if that's also massive. It doesn't make sense as I put the requirements as being dpi > ~150 and screen vertical size >= 1440pixels it's possible the virtual screen has messed up physical size, but the mode is clearly 768px... If you can run kscreen-console outputs that would tell us. -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 384796] New: Rekonq crashes every time opening a page
https://bugs.kde.org/show_bug.cgi?id=384796 Bug ID: 384796 Summary: Rekonq crashes every time opening a page Product: rekonq Version: 2.4.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: adj...@gmail.com Reporter: momo7...@googlemail.com Target Milestone: --- Application: rekonq (2.4.2) KDE Platform Version: 4.14.35 Qt Version: 4.8.6 Operating System: Linux 4.13.1-3.g0d725b5-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: tried to open ftp://ftp.avm.de asked for reopening old session, then crashed it too. The crash can be reproduced every time. -- Backtrace: Application: Rekonq (rekonq), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43164a88c0 (LWP 8379))] Thread 8 (Thread 0x7f429dfa6700 (LWP 8413)): #0 0x7f4315ce628d in read () at /lib64/libc.so.6 #1 0x7f430d673750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f430d632e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f430d6332a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f430d63364a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #5 0x7f42a2453386 in () at /usr/lib64/libgio-2.0.so.0 #6 0x7f430d657a85 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f430cb8e744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f4315cf2aad in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f42bd2ce700 (LWP 8412)): #0 0x7f4315cea20d in poll () at /lib64/libc.so.6 #1 0x7f430d633314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f430d63342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f430d633469 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f430d657a85 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f430cb8e744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f4315cf2aad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f42b5513700 (LWP 8390)): #0 0x7f4315cea20d in poll () at /lib64/libc.so.6 #1 0x7f430d633314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f430d63342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f431030cfce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f43102ded3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f43102df035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f43101dc49f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f43102c0643 in () at /usr/lib64/libQtCore.so.4 #8 0x7f43101deb7f in () at /usr/lib64/libQtCore.so.4 #9 0x7f430cb8e744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f4315cf2aad in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f42b6fe1700 (LWP 8387)): #0 0x7f430d6748b4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f430d632950 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f430d633230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f430d63342c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f431030cfce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f43102ded3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f43102df035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f43101dc49f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #8 0x7f43101deb7f in () at /usr/lib64/libQtCore.so.4 #9 0x7f430cb8e744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f4315cf2aad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f42b7901700 (LWP 8386)): #0 0x7f430cb930bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f43146450ab in WebCore::IconDatabase::syncThreadMainLoop() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f4314645294 in WebCore::IconDatabase::iconDatabaseSyncThread() () at /usr/lib64/libQtWebKit.so.4 #3 0x7f4315149806 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #4 0x7f430cb8e744 in start_thread () at /lib64/libpthread.so.0 #5 0x7f4315cf2aad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f42bcacd700 (LWP 8385)): #0 0x7f430cb930bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4314e9495d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f4315149806 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f430cb8e744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4315cf2aad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f42fe57f700 (LWP 8382)): #0 0x7f430cb930bf in pthread_cond_wait@@GLIBC
[kaddressbook] [Bug 375296] unable to use kdeconnect-cli to send an sms
https://bugs.kde.org/show_bug.cgi?id=375296 --- Comment #11 from Christoph Feck --- This looks like a memory corruption. If possible, try to get a valgrind log. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383087] recover unsaved files after crash
https://bugs.kde.org/show_bug.cgi?id=383087 --- Comment #2 from Christoph Feck --- Did comment #1 help? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382758] Freeze effect doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=382758 --- Comment #5 from tszym --- Hi, Are you sure this has been fixed? I am still experiencing the same issue with 17.08.1 french or english. I am trying to use the freeze effect as showed in the following video: https://youtu.be/fwfSWAz9ewA?t=2m Still no freeze on the project monitor or rendering results. I am using Archlinux and have tried using i3 window manager & KDE plasma. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377392] Select Folder on Going up (Feature Request)
https://bugs.kde.org/show_bug.cgi?id=377392 --- Comment #4 from Tsu Jan --- If only KDE was developed on GtiHub... Sorry, but the current situation doesn't encourage any contribution. Believe me, KDE needs a lot of contribution. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 383991] Akonadi 17.08.0 / 5.6.0 with MariaDB 10.2.8 - Plugin pvio_socket could not be loaded: not initialized
https://bugs.kde.org/show_bug.cgi?id=383991 --- Comment #4 from Heinz Wiesinger --- Git commit b145f47f000978b9d39edc1882849ec7f6b3ef79 by Heinz Wiesinger. Committed on 17/09/2017 at 15:21. Pushed by wiesinger into branch 'Applications/17.08'. Only remove init connections to the database on server shutdown. Summary: With MariaDB 10.2 libmysqlclient was replaced with libmariadb that changed how establishing database connections behaves. The MySQL QSQL driver calls mysql_server_end() on QSqlDatabase::removeDatabase() if the overall connection count dropped to 0 (which it does when the init connection is removed). A future QSqlDatabase:addDatabase() would call mysql_server_init() again, but this no longer works with libmariadb as that one only allows calling mysql_server_init() once. Future calls are simply ignored. In order to prevent this from happening we have to keep the init connection open until the server shuts down, so the connection count only drops to 0 at shutdown and mysql_server_end() isn't called before. This is a workaround for QTBUG-63108 Reviewers: dvratil, mlaurent Reviewed By: dvratil Subscribers: #kde_pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D7858 M +2-1src/server/akonadi.cpp M +3-1src/server/storage/dbconfigmysql.cpp https://commits.kde.org/akonadi/b145f47f000978b9d39edc1882849ec7f6b3ef79 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383963] Kate is not opening current folder when it's remote (KIO, sftp)
https://bugs.kde.org/show_bug.cgi?id=383963 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 374913 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 374913] Open does use directory for currently open file with sftp://
https://bugs.kde.org/show_bug.cgi?id=374913 Christoph Feck changed: What|Removed |Added CC||charles.vej...@yale.edu --- Comment #15 from Christoph Feck --- *** Bug 383963 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 383069] Corrputed mp3 files when sent through KDE Connect
https://bugs.kde.org/show_bug.cgi?id=383069 --- Comment #19 from Michał Dybczak --- You're right. When using Dolphin and dragging a file between panels/locations, it shows "cannot write /path1 to /path2". When I used a small text file, everything went ok. So I guess, we're still waiting for sshfs 3.2.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384787] Cant add speed to clips
https://bugs.kde.org/show_bug.cgi?id=384787 --- Comment #1 from alberto --- Okay, I guess adding effects to clips is bugged in general. Ive seen many things not working now. I can make a list if needed. Just ask and I will add a comprehensive list but I suspect this is not supposed to be used yet :) The last thing was transform. Modifiying scale in the clip doesnt show up once you move the clip into the timeline -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
https://bugs.kde.org/show_bug.cgi?id=345979 silentz0r changed: What|Removed |Added CC||d.misdani...@gmail.com --- Comment #3 from silentz0r --- (In reply to Denis Kurz from comment #2) > This bug has never been confirmed for a KDE PIM version that is based on KDE > Frameworks (5.x). Those versions differ significantly from the old 4.x > series. Therefore, I plan to close it in around two or three months. In the > meantime, it is set to WAITINGFORINFO to give reporters the oportunity to > check if it is still valid. As soon as someone confirms it for a recent > version (at least 5.1, ideally even more recent), I'll gladly reopen it. > > Please understand that we lack the manpower to triage bugs reported for > versions almost two years beyond their end of life. This bug stills exists. I'm on whatever version is currently on Arch Linux's upstream repositories which is fairly up-to-date. This does not even happen for such large collections, I've had this happen on my work mail which is less than 400MB (0.33 GB (2%) of 15 GB used, per gmail's quota). This is not an old migrated setup either, the PC was wiped clean less than 6 months ago and everything was reinstalled. I've noticed that one specific folder which contains over 1,000 emails is the one that gets stuck when syncing. After restarting akonadi manually (akonadictl restart) and hitting the sync button, Kmail starts syncing my folders one by one and eventually gets to the large folder, which only goes up to 84% IIRC. Maybe this helps track down some resource which would crash on anything above 800-900 emails (84% of 1100) or maybe it's just an unrelated visual while akonadi crashes. This seems like akonadi hangs when any task gets stuck, which is pretty bad. It has also been confirmed by a KDE dev on the forums: https://forum.kde.org/viewtopic.php?f=215&t=139394#p375588 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 384093] Kaffeine crashes randomly when watching DVB-T
https://bugs.kde.org/show_bug.cgi?id=384093 Christoph Feck changed: What|Removed |Added Resolution|--- |BACKTRACE Severity|normal |crash Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Christoph Feck --- If this is reproducible, please add the backtrace for all threads. The command is: thread apply all bt -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 305492] Wrong (real) .. location (auto-suggestions) shown in copy/move windows, while in a directory symlink; wrong drag-and-drop moving to .. from dir symlink
https://bugs.kde.org/show_bug.cgi?id=305492 Alex Bikadorov changed: What|Removed |Added Severity|major |normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #6 from Fabian Vogt --- (In reply to David Edmundson from comment #5) > I now have that option on X, it affects X > If you set that option on wayland, it affects wayland That sounds like bad design, at the very least it should tell the user in the UI. Everyone setting that option expects it to behave exactly the same on wayland. > Reasons for that in the commit; it's not something I want to undo unless we > have a reason. But since ages it would default to 96dpi if this value wasn't > set (so that users don't need to do this stage). Not true, without it set X and wayland looked slightly different, just enough for openQA to reject. > The other possibility is that we're hitting wayland scaling. Easy way to > tell is open xterm and see if that's also massive. It doesn't make sense as > I put the requirements as being dpi > ~150 and screen vertical size >= > 1440pixels > > it's possible the virtual screen has messed up physical size, but the mode > is clearly 768px... > > If you can run kscreen-console outputs that would tell us. Ok, I'll do all that and report back. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 375296] unable to use kdeconnect-cli to send an sms
https://bugs.kde.org/show_bug.cgi?id=375296 Philippe ROUBACH changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #12 from Philippe ROUBACH --- no problem with another opensuse leap 42.2. on another disk and fresh installation. there is still many "QFSFileEngine::open: No file name specified" without any problem. i close this bug report. thanks -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 384467] Crash on KDE5.37.0
https://bugs.kde.org/show_bug.cgi?id=384467 Christoph Feck changed: What|Removed |Added Resolution|FIXED |INVALID -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 384242] apps in task bar bouncing
https://bugs.kde.org/show_bug.cgi?id=384242 Christoph Feck changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Christoph Feck --- Could you please add exact steps to reproduce the issue? Maybe also record a video of the bug, because I am unsure what bug you see. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 384301] appmenu button (placed on window title bar) for Oxygen "Window decorations" looks the same like button "Menu"
https://bugs.kde.org/show_bug.cgi?id=384301 Christoph Feck changed: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384797] New: UI Freezes 100% CPU usage of 1 core while clicking on clip with spacer tool in large project
https://bugs.kde.org/show_bug.cgi?id=384797 Bug ID: 384797 Summary: UI Freezes 100% CPU usage of 1 core while clicking on clip with spacer tool in large project Product: kdenlive Version: 17.08.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: b...@stefantriller.de Target Milestone: --- In the current 17.08.1 version of Kdenlive I have a very large video project lasting around 3 hours. Now I want to insert some clips to the front of it. If I click on the spacer tool and then select a clip which is in the first couple of minutes of the project with around >200 clips behind, the UI freezes and uses 100% CPU of one core of my system. After a few _minutes_ the clip and all the following clips are selected. Dragging the clip with all its followers also takes minutes while the UI is frozen and 100% CPU of one core is used. I do not know what kdenlive is doing (calculating) that lasts this long, but there is definitely a bug in it because it shouldn't last that long. I do not know how I can add some clips between others in my project now because it always freezes kdenlive once I select a clip with many followers in the timeline. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 384093] Kaffeine crashes randomly when watching DVB-T
https://bugs.kde.org/show_bug.cgi?id=384093 --- Comment #2 from voncl...@gmail.com --- Running Kaffeine at the moment - if it crashes I will post the information ASAP -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383825] Ctrl colour picking tool shows inverted image instead of the colour being picked
https://bugs.kde.org/show_bug.cgi?id=383825 Alvin Wong changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/b6e9d537070af23b211eaf8e ||f5ff1faa2f36d83f Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/b6e9d537070af23b211eaf8e |ta/b1f67e34fce0b6ada0e9c06d |f5ff1faa2f36d83f|9feab8c765891677 --- Comment #1 from Alvin Wong --- Git commit b6e9d537070af23b211eaf8ef5ff1faa2f36d83f by Alvin Wong. Committed on 17/09/2017 at 16:09. Pushed by alvinwong into branch 'krita/3.3'. Fix paint tool colour picker display witn QPainter canvas M +2-0libs/ui/tool/kis_tool.cc https://commits.kde.org/krita/b6e9d537070af23b211eaf8ef5ff1faa2f36d83f --- Comment #2 from Alvin Wong --- Git commit b1f67e34fce0b6ada0e9c06d9feab8c765891677 by Alvin Wong. Committed on 17/09/2017 at 16:10. Pushed by alvinwong into branch 'master'. Fix paint tool colour picker display witn QPainter canvas M +2-0libs/ui/tool/kis_tool.cc https://commits.kde.org/krita/b1f67e34fce0b6ada0e9c06d9feab8c765891677 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383825] Ctrl colour picking tool shows inverted image instead of the colour being picked
https://bugs.kde.org/show_bug.cgi?id=383825 Alvin Wong changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/b6e9d537070af23b211eaf8e |ta/b1f67e34fce0b6ada0e9c06d |f5ff1faa2f36d83f|9feab8c765891677 --- Comment #2 from Alvin Wong --- Git commit b1f67e34fce0b6ada0e9c06d9feab8c765891677 by Alvin Wong. Committed on 17/09/2017 at 16:10. Pushed by alvinwong into branch 'master'. Fix paint tool colour picker display witn QPainter canvas M +2-0libs/ui/tool/kis_tool.cc https://commits.kde.org/krita/b1f67e34fce0b6ada0e9c06d9feab8c765891677 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383825] Ctrl colour picking tool shows inverted image instead of the colour being picked
https://bugs.kde.org/show_bug.cgi?id=383825 Alvin Wong changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/b6e9d537070af23b211eaf8e ||f5ff1faa2f36d83f Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Alvin Wong --- Git commit b6e9d537070af23b211eaf8ef5ff1faa2f36d83f by Alvin Wong. Committed on 17/09/2017 at 16:09. Pushed by alvinwong into branch 'krita/3.3'. Fix paint tool colour picker display witn QPainter canvas M +2-0libs/ui/tool/kis_tool.cc https://commits.kde.org/krita/b6e9d537070af23b211eaf8ef5ff1faa2f36d83f -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377512] Feature request: autosaving
https://bugs.kde.org/show_bug.cgi?id=377512 Christoph Feck changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #11 from Christoph Feck --- No response, assuming it is working. If you still see a bug, please add a comment or a new ticket. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 384093] Kaffeine crashes randomly when watching DVB-T
https://bugs.kde.org/show_bug.cgi?id=384093 --- Comment #3 from voncl...@gmail.com --- Blanked screen application did not close out: Results posted here: https://pastebin.com/cEwXPMWD -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #7 from Fabian Vogt --- (In reply to David Edmundson from comment #5) > I now have that option on X, it affects X > If you set that option on wayland, it affects wayland > > Reasons for that in the commit; it's not something I want to undo unless we > have a reason. But since ages it would default to 96dpi if this value wasn't > set (so that users don't need to do this stage). > > The other possibility is that we're hitting wayland scaling. Easy way to > tell is open xterm and see if that's also massive. It doesn't make sense as > I put the requirements as being dpi > ~150 and screen vertical size >= > 1440pixels xterm is massive as well. > it's possible the virtual screen has messed up physical size, but the mode > is clearly 768px... > > If you can run kscreen-console outputs that would tell us. kscreen-console says: > Pos: QSize(0,0) > MMSize: QSize(0,0) > Scale: 2 > Mode: "1" > Perferred modes: () > Modes: > ... > "1": "4096x2160@60" QSize(4096,2160) 6 So it looks like it thinks the tiny 1024x768 display is actually 4k@60Hz. Note that this hits all wayland runs in a VM (nothing unique to openQA), so it should be relatively easy to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384732] posix_spawn with glibc 2.25 causes an assertion
https://bugs.kde.org/show_bug.cgi?id=384732 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #7 from Philippe Waroquiers --- (In reply to Mark Wielaard from comment #6) > (In reply to Tom Hughes from comment #5) > > We already detect CLONE_VFORK|CLONE_VM as a special case and deliberately > > drop CLONE_VM because I imagine anything else would be a disaster as > > valgrind's shadow memory etc would be shared. > > Sharing shadow memory should be fine since we do share the actual memory. > But sharing the thread state is probably a problem. > > And indeed just not dropping VM_CLONE when we see VM_VFORK doesn't work. > It does successfully create the child and execs the new process, but > returning to the parent seg faults fairly soon. Yes, that looks expected. For example, if the scheduler in the child process has to regain control e.g. to translate a block in what follows the clone syscall, then the parent host stack will be thrashed by the code executed by the host child. In other words, i highly suspect that the constraints of vfork syscall apply for VM_CLONE+VM_VFORK (i.e. no function call, no return, ...). What is tricky is that such constraints have to be respected both for the guest and the host parts of the child; > > > The comments in the source explicitly mention preserving CLONE_VFORK to > > preserve the wait-for-exec semantics and that does indeed seem to work. > > Earlier we did drop both CLONE_VFORK and CLONE_VM. > And I can definitely see why CLONE_VM is bad without CLONE_VFORK. > > I am probable missing some bad sharing which messes things up. > But I still wonder if we could handle CLONE_VFORK | CLONE_VM specially as if > it was a simple thread creation (do_clone vs do_fork_clone) up till the > actual exec/exit call (at which point we might have to do some magic to do > the actual fork). Maybe too much bad voodoo though... To fully respect the vfork semantic, all the threads have to be suspended while the new thread has not yet done the exec, and nothing can happen in these threds (e.g. signal handling or whatever). It does look like a nice challenge to achieve. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382977] "Play" action only plays current clip instead of project in timeline
https://bugs.kde.org/show_bug.cgi?id=382977 Christoph Feck changed: What|Removed |Added Summary|radio buttons do not work. |"Play" action only plays ||current clip instead of ||project in timeline --- Comment #8 from Christoph Feck --- It looks like you are using an old version of kdenlive. On the current versions (17.04 or 17.08) the Monitor has a tabbar to switch between "Project Monitor" and "Clip Monitor". Then, hitting Play affects either the current clip or the complete project (which the timeline shows). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #8 from Fabian Vogt --- I just tried to force the font dpi to 96 on wayland as well, no difference at all. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 383097] Problem with titles not workig properly
https://bugs.kde.org/show_bug.cgi?id=383097 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 383868] Closing Kdenlive with "X" button leave tasks opened.
https://bugs.kde.org/show_bug.cgi?id=383868 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 380854 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380854] Kdenlive exit does not close all processes
https://bugs.kde.org/show_bug.cgi?id=380854 Christoph Feck changed: What|Removed |Added CC||bartol...@outlook.com --- Comment #4 from Christoph Feck --- *** Bug 383868 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384148] rendering window reports "mkv" as unsupported
https://bugs.kde.org/show_bug.cgi?id=384148 --- Comment #3 from Christoph Feck --- Does comment #2 provide the requested information? Please set the bug status or add a comment. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 384301] appmenu button (placed on window title bar) for Oxygen "Window decorations" looks the same like button "Menu"
https://bugs.kde.org/show_bug.cgi?id=384301 --- Comment #3 from Hugo Pereira Da Costa --- Hello, Thanks for reporting. Most likely an oxygen bug, (choosing the same visual appearance for the menu and appmenu button). Will investigate asap. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 384301] appmenu button (placed on window title bar) for Oxygen "Window decorations" looks the same like button "Menu"
https://bugs.kde.org/show_bug.cgi?id=384301 Hugo Pereira Da Costa changed: What|Removed |Added Component|top menubar |win deco Assignee|plasma-b...@kde.org |hugo.pereira.da.costa@gmail ||.com Product|kded-appmenu|Oxygen -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 297217] picker window always opens with the left pane so narrow that most entries are indistinguishable from others
https://bugs.kde.org/show_bug.cgi?id=297217 --- Comment #13 from Christoph Feck --- Felix, the bug has already been investigated, see comment #7, so there is no reason to continue nagging. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #9 from David Edmundson --- Font DPI was a red herring. (though I'm 95% convinced you can remove your setting it from X) >Scale 2 is the important line. Normally, if we are on a 4k screen we do want to double everything; that's my automatic scaling detection working perfectly as intended. The part that's wrong is that we're clearly not on a 4k scene; that's our bug not the scaling. It comes from a few different parts of the stack What VM tech are you using? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 341514] Dolphin fails to mount CIFS 3 share
https://bugs.kde.org/show_bug.cgi?id=341514 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Christoph Feck --- Indeed, thanks! *** This bug has been marked as a duplicate of bug 339752 *** -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 339752] enable max protocol SMB3
https://bugs.kde.org/show_bug.cgi?id=339752 Christoph Feck changed: What|Removed |Added CC||shm...@mykolab.com --- Comment #5 from Christoph Feck --- *** Bug 341514 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384789] UI elements on wayland are huge
https://bugs.kde.org/show_bug.cgi?id=384789 --- Comment #10 from Fabian Vogt --- (In reply to David Edmundson from comment #9) > Font DPI was a red herring. > (though I'm 95% convinced you can remove your setting it from X) Not on Plasma 5.10 yet, AFAICT the default is not 96 there. > >Scale 2 > > is the important line. > > Normally, if we are on a 4k screen we do want to double everything; that's > my automatic scaling detection working perfectly as intended. > > The part that's wrong is that we're clearly not on a 4k scene; that's our > bug not the scaling. It comes from a few different parts of the stack > > What VM tech are you using? QEMU 2.9.0 (with KVM) and virtio as VGA. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 281270] Show progress actually transferred to disk instead of to caches
https://bugs.kde.org/show_bug.cgi?id=281270 Christoph Feck changed: What|Removed |Added CC||sse...@gmail.com --- Comment #12 from Christoph Feck --- *** Bug 383995 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 383995] KDE notificator is giving wrong copying time.
https://bugs.kde.org/show_bug.cgi?id=383995 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 281270 *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 384240] Dolphin doesn't read samba shares when V1 smb protocol is disabled
https://bugs.kde.org/show_bug.cgi?id=384240 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 339752 *** -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 339752] enable max protocol SMB3
https://bugs.kde.org/show_bug.cgi?id=339752 Christoph Feck changed: What|Removed |Added CC||ene...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 384240 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 382128] wayland: kinfocenter still crashing when clicking on "Graphical information -> OpenGL"
https://bugs.kde.org/show_bug.cgi?id=382128 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 380373 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 380373] Open OpenGL info page in KDE Info Center Crash in Plasma-Wayland
https://bugs.kde.org/show_bug.cgi?id=380373 Christoph Feck changed: What|Removed |Added CC||m4n...@gmx.de --- Comment #4 from Christoph Feck --- *** Bug 382128 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
