[kontact] [Bug 384693] New: Kontact crash when add contact from mail to existing
https://bugs.kde.org/show_bug.cgi?id=384693 Bug ID: 384693 Summary: Kontact crash when add contact from mail to existing Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ad...@different-perspectives.com Target Milestone: --- Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.79-18.26-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Viewing email in list -> add email address from email to existing contact -> crash -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f53557ab7c0 (LWP 4217))] Thread 44 (Thread 0x7f522adb3700 (LWP 11259)): #0 0x7f53521e628d in read () at /lib64/libc.so.6 #1 0x7f534d52a670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f534d4e9e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f534d4ea2a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f534d4ea42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f5352d0e33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f5352cbbfeb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f5352af6f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f5352afb9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f534e127744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f53521f2aad in clone () at /lib64/libc.so.6 Thread 43 (Thread 0x7f522b5b4700 (LWP 11257)): #0 0x7f534d4e9da4 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #1 0x7f534d4ea2a8 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f534d4ea42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5352d0e33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f5352cbbfeb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5352af6f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f5352afb9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f534e127744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f53521f2aad in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7f522bdb5700 (LWP 11160)): #0 0x7f53521e628d in read () at /lib64/libc.so.6 #1 0x7f534d52a670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f534d4e9e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f534d4ea2a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f534d4ea42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f5352d0e33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f5352cbbfeb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f5352af6f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f5352afb9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f534e127744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f53521f2aad in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7f522c5b6700 (LWP 11159)): #0 0x7f53521ea20d in poll () at /lib64/libc.so.6 #1 0x7f534d4ea314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f534d4ea42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5352d0e33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f5352cbbfeb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5352af6f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f5352afb9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f534e127744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f53521f2aad in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7f522d2dd700 (LWP 11157)): #0 0x7f534d4ea418 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #1 0x7f5352d0e33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #2 0x7f5352cbbfeb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f5352af6f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #4 0x7f5352afb9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f534e127744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f53521f2aad in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7f522f95b700 (LWP 11155)): #0 0x7f534d4f87f0 in g_poll () at /usr/lib64/libglib-2.0.so.0 #1 0x7f534d4ea314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f534d4ea42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5352d0e33b
[plasmashell] [Bug 384692] New: Crash on resizing pannel (wayland)
https://bugs.kde.org/show_bug.cgi?id=384692 Bug ID: 384692 Summary: Crash on resizing pannel (wayland) Product: plasmashell Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: silvio.fris...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.12.0-13-generic x86_64 Distribution: Ubuntu Artful Aardvark (development branch) -- Information about the crash: - What I was doing when the application crashed: closing the pannel settings after changing the width of the pannel - Custom settings of the application: Pannel is on the left side of the screen. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f3513d2cf80 (LWP 5714))] Thread 27 (Thread 0x7f33d33fe700 (LWP 6645)): [KCrash Handler] #6 0x7f350c2b2b30 in wl_proxy_create_wrapper () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #7 0x7f34ee7838a1 in () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #8 0x7f34ee770d17 in () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #9 0x7f34ee9a9f4d in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so #10 0x7f34ee9a84c5 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so #11 0x7f350e4d5266 in QOpenGLContext::makeCurrent(QSurface*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7f35117e1004 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f35117e88eb in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f35117e7b77 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f35117e7f4a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f350da7329d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f350cc2474a in start_thread (arg=0x7f33d33fe700) at pthread_create.c:456 #18 0x7f350d384caf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 26 (Thread 0x7f33d3fff700 (LWP 6644)): #0 0x7f350cc2a520 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f350da746cb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f35117e7ae8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7f35117e7f4a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f350da7329d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f350cc2474a in start_thread (arg=0x7f33d3fff700) at pthread_create.c:456 #6 0x7f350d384caf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 25 (Thread 0x7f33ed72e700 (LWP 6643)): #0 0x7f350803f569 in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3507ffa020 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3507ffa22c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f350dca941b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f350dc4edba in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f350da6e3ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3510bd1f45 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f350da7329d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f350cc2474a in start_thread (arg=0x7f33ed72e700) at pthread_create.c:456 #9 0x7f350d384caf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 24 (Thread 0x7f33eeffd700 (LWP 6624)): #0 0x7f350cc2a520 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f350da746cb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3455471995 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x7f3455475a18 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f3455470b5d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f3455475a72 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f3455470b5d in ThreadWeaver::Weaver::applyForWork(ThreadWeave
[kmail2] [Bug 383279] Kmail unnecessarily prompts for passwords
https://bugs.kde.org/show_bug.cgi?id=383279 abyss.and...@gmail.com changed: What|Removed |Added CC||abyss.and...@gmail.com --- Comment #1 from abyss.and...@gmail.com --- I can confirm this problem in general. Kmail asks for a password at startup or once I click some folder (not synchronized before) for IMAP account with GSSAPI auth. Asking for password every 5-10 minutes was fixed in https://bugs.kde.org/show_bug.cgi?id=311456 KDE neon 5.10 KDE Plasma 5.10.5 KDE Frameworks 5.38.0 KDE Applications 17.08.1 Qt 5.9.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379316] Notification sounds don't play
https://bugs.kde.org/show_bug.cgi?id=379316 David Rosca changed: What|Removed |Added Version Fixed In||5.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379316] Notification sounds don't play
https://bugs.kde.org/show_bug.cgi?id=379316 David Rosca changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #6 from David Rosca --- Another fix comes in Plasma 5.11. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384603] Camera Creation Date not set from EXIF data
https://bugs.kde.org/show_bug.cgi?id=384603 Simon changed: What|Removed |Added CC||freisi...@gmail.com --- Comment #14 from Simon --- Thanks for the thorough investigation. In my opinion not re-reading metadata off of files that haven't changed when doing it for entire albums or by maintenance, but agree there should be an option to override it for cases like this where something is fd up and probably also not care about it when doing the operation directly on items. I haven't looked at the code yet whether this is easily feasible, as I am working on something else right now (and if Maik does, he will be like 10x faster anyway). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend
https://bugs.kde.org/show_bug.cgi?id=360058 --- Comment #23 from Sergio --- Bug still present as of framework 5.37 QT 5.7.1 plasma 5.10.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384691] New: mouse sticks to window decoration with touchscreen
https://bugs.kde.org/show_bug.cgi?id=384691 Bug ID: 384691 Summary: mouse sticks to window decoration with touchscreen Product: kwin Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: silvio.fris...@gmail.com Target Milestone: --- If I use a touch screen to drag a window, the mouse is never released from the window decoration. It just keeps dragging the window around and nothing else can be clicked. Tested on ubuntu 16.10/17.04/17.10Beta. With Lenovo Yoga 510. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384690] New: display is glitching
https://bugs.kde.org/show_bug.cgi?id=384690 Bug ID: 384690 Summary: display is glitching Product: krita Version: 3.2.1 Platform: Windows CE OS: unspecified Status: UNCONFIRMED Severity: major Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: bethany...@gmail.com Target Milestone: --- Created attachment 107846 --> https://bugs.kde.org/attachment.cgi?id=107846&action=edit picture of where i can and can;t draw on the page i have my tablet connnected to my laptop. When i go over a certain area ( the bottom and right side) the cursor jumps from the middle of the page to off the page to the toolbox. Everything still functions but i cant access (draw on) the bottom right of my page unless i drag one line from the top to the bottom. if i move the image to the top left corner then i can acess(draw on) the bottom right corner again. It is like a part of the workspace is blocked. I have had Krita on another laptop but it doesn't work well with this one. i have a dell xps. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 384682] disk usage pop up says kdiskfree not installed also it is
https://bugs.kde.org/show_bug.cgi?id=384682 Rog131 changed: What|Removed |Added CC||samrog...@hotmail.com --- Comment #1 from Rog131 --- This bug is at frameworks-knewstuff. The kdf is installing org.kde.kdf.desktop. The knewstuff frameworks is looking kdf.desktop -> https://lxr.kde.org/source/frameworks/knewstuff/data/kmoretools-desktopfiles/ A workaround is to symlink the org.kde.kdf.desktop to kdf.desktop. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384689] Customize digiKam and Showfoto splash-screens at startup
https://bugs.kde.org/show_bug.cgi?id=384689 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Setup-Misc Version|unspecified |5.7.0 Summary|costomize appimage splash |Customize digiKam and |screen |Showfoto splash-screens at ||startup -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384689] New: costomize appimage splash screen
https://bugs.kde.org/show_bug.cgi?id=384689 Bug ID: 384689 Summary: costomize appimage splash screen Product: digikam Version: unspecified Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: w...@culturanuova.net Target Milestone: --- I'd like customize digikam appimage splash screen (maybe with command-line --config? or adding something to digikamrc?). Thank you -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 384597] Shift+alt+[arrow keys] and Shift+Meta+[arrow keys] shortcuts broken in 5.38.0
https://bugs.kde.org/show_bug.cgi?id=384597 --- Comment #13 from Martin Flöser --- (In reply to Nate Graham from comment #12) > Is anyone able to reproduce this on Wayland, or just X11? Wayland should not be affected. The change you mention only affects X11. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383219] Bug in ubiquity-frontend-kde: Can't create LUKS encrypted volumes during manual disk setup in KDE Neon and Kubuntu 17.10 (does not affect Ubuntu, Ubuntu MATE, or Ubuntu Budgie)
https://bugs.kde.org/show_bug.cgi?id=383219 --- Comment #8 from GizmoChicken --- I've posted various places, but no one from Kubuntu every acknowledges that their installer introduces a bug relative to the GTK installer used by vanilla Ubuntu. Anyway, with regard to KDE Neon, as I see it, the "bug" is that KDE Neon uses the “ubiquity-frontend-kde” package in the first place. Rather, KDE Neon should use the text-based installer used by Ubuntu Server. Or, at the very least, an ISO including the text-based installer should be offered as an option. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 261945] black borders around some thumbnails
https://bugs.kde.org/show_bug.cgi?id=261945 --- Comment #5 from Nate Graham --- Excellent! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378275] Kate doesn't do smooth pixel-by-pixel scrolling
https://bugs.kde.org/show_bug.cgi?id=378275 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Nate Graham --- I've spoken to Kate developers and they don't object. It's just a matter of doing it. I've taken a look but my C++ skills are probably not advanced enough yet. At some point, if nobody else does first, I'll return to tackle this. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 182089] Places sidebar in Open/Save dialog doesn't allow fixed icon sizes
https://bugs.kde.org/show_bug.cgi?id=182089 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383206] Open and Save dialogs sidebars are different
https://bugs.kde.org/show_bug.cgi?id=383206 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- 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 #5 from Nate Graham --- This is weird. In this bug, someone asks to implement automatic panel icon resizing. But in https://bugs.kde.org/show_bug.cgi?id=182089, people complain about it! So which is it? Is this feature implemented or not? FWIW in an up-to-date Neon VM, my save and open dialogs both use small, un-resizable icons and don't ever seem to get bigger no matter how I resize the dialogs. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378275] Kate doesn't do smooth pixel-by-pixel scrolling
https://bugs.kde.org/show_bug.cgi?id=378275 atomnuker changed: What|Removed |Added CC||rasty...@abv.bg --- Comment #1 from atomnuker --- Hi, I too would very much appreciate for both kate and konsole to do pixel-by-pixel scrolling. Kate has been the best editor I've used and whilst it has much more features than Gedit its more uncomfortable to use with large files where you need to quickly and accurately scroll between lines. There's no reason to be stuck in the 90's. If not by default, make it an option, like with most KDE programs. Thanks -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 --- Comment #4 from Leslie Zhai --- Git commit c84ad1e966697622b8e96557fbe6061fd5a7 by Leslie Zhai. Committed on 14/09/2017 at 02:25. Pushed by lesliezhai into branch 'master'. Hi Mayeul, Please test it for me what will happen if cue title is larger than 80 bytes, thanks! M +2-1libk3b/projects/k3bcuefileparser.cpp https://commits.kde.org/k3b/c84ad1e966697622b8e96557fbe6061fd5a7 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 384597] Shift+alt+[arrow keys] and Shift+Meta+[arrow keys] shortcuts broken in 5.38.0
https://bugs.kde.org/show_bug.cgi?id=384597 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #12 from Nate Graham --- Is anyone able to reproduce this on Wayland, or just X11? KGlobalAccel has only gotten one consequential many commit since 5.37: https://cgit.kde.org/kglobalaccel.git/commit/?id=2c20ddff034e4958bf0536ca91ae9e444955305d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 384597] Shift+alt+[arrow keys] and Shift+Meta+[arrow keys] shortcuts broken in 5.38.0
https://bugs.kde.org/show_bug.cgi?id=384597 --- Comment #11 from deonix --- I'm having the same issue on Arch. The shortcut I'm using is ctrl + shift + spacebar. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 384597] Shift+alt+[arrow keys] and Shift+Meta+[arrow keys] shortcuts broken in 5.38.0
https://bugs.kde.org/show_bug.cgi?id=384597 deonix changed: What|Removed |Added CC||deonix+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384688] New: brush unresponsive
https://bugs.kde.org/show_bug.cgi?id=384688 Bug ID: 384688 Summary: brush unresponsive Product: krita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: 1spag00...@gmail.com Target Milestone: --- when I make brush strokes, the strokes do not appear. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384687] New: overview docker unresponsive
https://bugs.kde.org/show_bug.cgi?id=384687 Bug ID: 384687 Summary: overview docker unresponsive Product: krita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: 1spag00...@gmail.com Target Milestone: --- When I tap the overview docker, the "red square" does not seem to move sometimes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384686] New: entire program "cropped"
https://bugs.kde.org/show_bug.cgi?id=384686 Bug ID: 384686 Summary: entire program "cropped" Product: krita Version: unspecified Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: 1spag00...@gmail.com Target Milestone: --- When I open Krita, everything is fine. But when I load a file, I don't know how to explain it properly, but it seems to be "cropped" to the side, which means the drop-down menu is gone and i cannot access some of the tools. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384033] Overview docker is very blurry
https://bugs.kde.org/show_bug.cgi?id=384033 1spag00...@gmail.com changed: What|Removed |Added CC||1spag00...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384685] New: drop-down menus are gone, overview docker stops responding
https://bugs.kde.org/show_bug.cgi?id=384685 Bug ID: 384685 Summary: drop-down menus are gone, overview docker stops responding Product: krita Version: unspecified Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: 1spag00...@gmail.com Target Milestone: --- W -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 380459] read out loud
https://bugs.kde.org/show_bug.cgi?id=380459 --- Comment #3 from Nate Graham --- Thanks Albert. I can confirm that Okular has a text-to-speech feature when compiled with Qt5TextToSpeech. It doesn't in Kubuntu 17.04. I'll file a bug on that: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1717131 That said, when I compile git master with libqt5texttospeech5-dev and launch Okular with a PDF, the feature is available, but neither "Speak Whole Document" nor "Speak Current Page" result in any sound. Console prints "No text-to-speech plug-ins were found." What else is missing? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384684] New: Window changes after opening document
https://bugs.kde.org/show_bug.cgi?id=384684 Bug ID: 384684 Summary: Window changes after opening document Product: krita Version: 3.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: ali.capron.art...@gmail.com Target Milestone: --- Created attachment 107845 --> https://bugs.kde.org/attachment.cgi?id=107845&action=edit Window expanding off screen, buttons distorted When opening a document in Krita, the program's window expands past the screen and the typical buttons are misplaced. Never had this problem before, not sure what changed. I included a picture of what I'm experiencing. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384473] Missing icon sizes
https://bugs.kde.org/show_bug.cgi?id=384473 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from Nate Graham --- You did great! Are you planning to make additional changes to your patch? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379316] Notification sounds don't play
https://bugs.kde.org/show_bug.cgi?id=379316 Nate Graham changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|INVALID |--- --- Comment #5 from Nate Graham --- Re-opening. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 384404] Kate and KWrite both crash when editing a Javascript or CSS file
https://bugs.kde.org/show_bug.cgi?id=384404 --- Comment #4 from Omar Plummer --- It crashes here regardless of what I have the indentation mode set to, even "None". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384683] New: The main menu "grows a little"; resulting in uncalibrated cursor and hidden Menubars.
https://bugs.kde.org/show_bug.cgi?id=384683 Bug ID: 384683 Summary: The main menu "grows a little"; resulting in uncalibrated cursor and hidden Menubars. Product: krita Version: 3.2.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: ernestotrejo2...@yahoo.com Target Milestone: --- Created attachment 107844 --> https://bugs.kde.org/attachment.cgi?id=107844&action=edit [Possibly] the glitched file. -OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.15063 Pretty Productname: Windows 10 Product Type: windows Product Version: 10 OpenGL Info Vendor: Intel Renderer: Intel(R) HD Graphics 620 Version: 3.0.0 - Build 21.20.16.4639 Shading language: 1.30 - Build 21.20.16.4639 Version: 3.0 Supports deprecated functions: true - Because I am awful at explanation, the .mp4 link I shown can explain the problem. https://www.dropbox.com/s/grwjjwq5b2kpyt3/Krita%20Error.mp4?dl=0 Also, at some point when trying to mess around, the system crashes, but it happen sometimes when messing with the TAB key. Also, looking at "resetting Krita" i feel this KritaRC has the setup. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 384682] disk usage pop up says kdiskfree not installed also it is
https://bugs.kde.org/show_bug.cgi?id=384682 Christoph Feck changed: What|Removed |Added Version|17.08.0 |unspecified Product|dolphin |frameworks-knewstuff Component|bars: status|general Assignee|dolphin-bugs-n...@kde.org |jpwhit...@kde.org CC||kdelibs-b...@kde.org See Also||https://bugs.kde.org/show_b ||ug.cgi?id=369646 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 369646] The 'free' menu in Dolphin's status bar incorrectly lists KDE Partition Manager as not installed
https://bugs.kde.org/show_bug.cgi?id=369646 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=384682 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384636] Kmail crash on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=384636 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 381630 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381630] Crash in wl_proxy_create_wrapper in QtWayland after window destruction
https://bugs.kde.org/show_bug.cgi?id=381630 Christoph Feck changed: What|Removed |Added CC||m...@rainer-finke.de --- Comment #18 from Christoph Feck --- *** Bug 384636 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381630] Crash in wl_proxy_create_wrapper in QtWayland after window destruction
https://bugs.kde.org/show_bug.cgi?id=381630 Christoph Feck changed: What|Removed |Added CC||kde...@gmail.com --- Comment #17 from Christoph Feck --- *** Bug 384680 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 384680] Segmentation fault under wayland when clicking on configure
https://bugs.kde.org/show_bug.cgi?id=384680 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 381630 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384682] New: disk usage pop up says kdiskfree not installed also it is
https://bugs.kde.org/show_bug.cgi?id=384682 Bug ID: 384682 Summary: disk usage pop up says kdiskfree not installed also it is Product: dolphin Version: 17.08.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bars: status Assignee: dolphin-bugs-n...@kde.org Reporter: tuxfus...@gmail.com Target Milestone: --- Created attachment 107843 --> https://bugs.kde.org/attachment.cgi?id=107843&action=edit kdiskfree_not_found_by_dolhpin when clicking on dolphin disk usage bar, the following pop up shows filelight but explains kdiskusage is not installed. It offers me to visit the website. kdiskusage is installed as you can see from the screenshot. the binary is started with "kdf". The version of dolphin and kdiskfree is 17.08.1 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384679] Crash when applying a partition move operation on LVM2 partition
https://bugs.kde.org/show_bug.cgi?id=384679 --- Comment #7 from Andrius Štikonas --- Well, you shouldn't be able to move it when luks is opened. Automount should also be disabled as soon as you click apply. I can't reproduce it on my system here but I'm downloading Neon LTS. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384679] Crash when applying a partition move operation on LVM2 partition
https://bugs.kde.org/show_bug.cgi?id=384679 --- Comment #6 from Revolt media --- (In reply to Andrius Štikonas from comment #5) > By the way, you are moving deactivated LUKS partition, aren't you? So LVM > stuff is not seen anyway? Well I haven't luksOpened the drive yet... OR touched it other than trying to use kde partition manager to move it. Since this is a live USB it isn't set up to auto mount that I know of. I installed partitionmanager-dbgsym but partitionmanager-dbg wasn't found in the main repo. Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa2ec33a940 (LWP 3086))] Thread 2 (Thread 0x7fa2d9aca700 (LWP 3088)): #0 0x7fa2e856270d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa2e3b9038c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa2e3b9049c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa2e8e8275b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa2e8e2d0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa2e8c5cf64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa2ec49c735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fa2e8c61b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa2e55e06ba in start_thread (arg=0x7fa2d9aca700) at pthread_create.c:333 #9 0x7fa2e856e3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa2ec33a940 (LWP 3086)): [KCrash Handler] #4 0x7fa2ebe541bf in Partition::sectorsUsed() const () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.5 #5 0x7fa2ebe954cc in PartWidget::paintEvent(QPaintEvent*) () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.5 #6 0x7fa2e9754f38 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fa2e970decc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fa2e97158c6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7fa2e8e2f0c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fa2e974dd7a in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fa2e974e3c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fa2e974f08c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fa2e974ef79 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fa2e974df31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fa2e974f08c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fa2e974df31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fa2e974f08c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fa2e974df31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fa2e971e002 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fa2e971e1dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fa2e973cebf in QWidgetPrivate::syncBackingStore() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fa2e9755008 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fa2e9852e3b in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fa2eb625217 in KMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #25 0x7fa2eb66a495 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #26 0x7fa2e970decc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib
[partitionmanager] [Bug 384679] Crash when applying a partition move operation on LVM2 partition
https://bugs.kde.org/show_bug.cgi?id=384679 --- Comment #5 from Andrius Štikonas --- By the way, you are moving deactivated LUKS partition, aren't you? So LVM stuff is not seen anyway? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383997] Yakuake/Konsole crashed when selecting long scrollback
https://bugs.kde.org/show_bug.cgi?id=383997 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 338997 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 338997] Konsole crashed while I was selecting text, causing the window to scroll up
https://bugs.kde.org/show_bug.cgi?id=338997 Christoph Feck changed: What|Removed |Added CC||nico.kru...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 383997 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383523] Support merging tabs aka undo split
https://bugs.kde.org/show_bug.cgi?id=383523 --- Comment #4 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-kxmlgui] [Bug 356489] Black field
https://bugs.kde.org/show_bug.cgi?id=356489 --- Comment #18 from Ronald Buckman --- I'm now seeing the black game field if qt5ct is used outside of Plasma to set the Appearance --> Style to either Breeze or Oxygen. I am using Applications 17.08.1, Frameworks 5.38.0, Plasma 5.10.5, Alien's unofficial KDE Slackware packages on Slackware 14.2. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 356489] Black field
https://bugs.kde.org/show_bug.cgi?id=356489 Ronald Buckman changed: What|Removed |Added CC||ron...@yahoo.com --- Comment #17 from Ronald Buckman --- I'm now seeing the black game field if qt5ct is used outside of Plasma to set the Appearance --> Style to either Breeze or Oxygen. I am using Applications 17.08.1, Frameworks 5.38.0, Plasma 5.10.5, Alien's unofficial KDE Slackware packages on Slackware 14.2. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383219] Bug in ubiquity-frontend-kde: Can't create LUKS encrypted volumes during manual disk setup in KDE Neon and Kubuntu 17.10 (does not affect Ubuntu, Ubuntu MATE, or Ubuntu Budgie)
https://bugs.kde.org/show_bug.cgi?id=383219 --- Comment #7 from Christoph Feck --- If those two packages are maintained by different people, please ask in a forum of your distribution how to find the maintainers of the -kde frontend. It is possible that Kubuntu maintainers are totally unaware of the fact that "their" bugs land unreviewed into the inbox of ubiquity developers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379316] Notification sounds don't play
https://bugs.kde.org/show_bug.cgi?id=379316 Paul Sommer changed: What|Removed |Added CC||n...@paul-sommer.de --- Comment #4 from Paul Sommer --- Don't know if this will be read by anyone, because this bug is now marked as "resolved invalid" which is not true. Since years I am not able to set the volume of the notification sound at all. It always sticks at 0%. When I move the slider to higher volumes it immediately moves back to 0%. But in spite of that setting notification sounds are played with full volume, always kicking me out of my chair. Only now, after installing pavucontrol and setting the volume there I also can change the volume in the "standard" plasma mixer too. Furthermore, the notification sound doesn't respect the main volume setting (it's the same volume all the time). That's especially annoying at night. Distro: Debian Stretch and Kubuntu 16.04 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384681] New: PUT(pc, ) should specialize to help debugging
https://bugs.kde.org/show_bug.cgi?id=384681 Bug ID: 384681 Summary: PUT(pc, ) should specialize to help debugging Product: valgrind Version: 3.13 SVN Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: jrei...@bitwagon.com Target Milestone: --- The VEX code for PUT(pc, ) should specialize these cases in order to help debugging: 1) return from subroutine 2) multi-way branch inside a subroutine (C-language 'switch') 3) subroutine call indirect through a pointer-to-function 4) any other write to pc of a non-constant value. [There is no change for PUT(pc, ).] Just allocate 4 more pseudo-registers in the thread state, and assign the **current** pc (not the destination) to the appropriate slot. And check that the value is sane: not zero in any case, and if extra debugging is requested then the destination should be mapped and executable, etc. The emulator doesn't have to be as dumb as the hardware. Instead, the emulator can tell you exactly where the problem was triggered. Here's an example of how this is helpful. = stomp.S for ARM(32-bit) _start: .globl _start // execution starts here mov r0,#0 // value to overwrite return address bl sub // call subroutine mov r7,#248 // NR_exit svc #0 sub: // IN: r0: value to clobber pc stmdb sp!,{lr} // save return address str r0,[sp] // clobber the return address ldmia sp!,{pc} // try to return = $ gcc -o stomp -nostartfiles -nostdlib stomp.S $ valgrind ./stomp ==19579== Memcheck, a memory error detector ==19579== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==19579== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==19579== Command: ./stomp ==19579== ==19579== Jump to the invalid address stated on the next line ==19579==at 0x0: ??? ==19579== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==19579== SB 1 (evchecks 1) [tid 1] 0x0 UNKNOWN_FUNCTION UNKNOWN_OBJECT+0x0 ==19579== ==19579== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==19579== Bad permissions for mapped region at address 0x0 ==19579==at 0x0: ??? ==19579== ==19579== HEAP SUMMARY: ==19579== in use at exit: 0 bytes in 0 blocks ==19579== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==19579== ==19579== All heap blocks were freed -- no leaks are possible ==19579== ==19579== For counts of detected and suppressed errors, rerun with: -v ==19579== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Segmentation fault (core dumped) $ = All that output, but no useful information: no hint of the pc just before it became 0. Instead, VEX should recognize "ldmia sp!,{pc}" as return-from-subroutine, and save the address of the ldmia in the new pseduo-register for "address of most recent RETURN". Then when extra debugging is requested a helper can check the new value of pc; and in any case the error diagnostic for "bad pc" can print the most recent locations that wrote a variable value into pc. This can save hours of debugging time. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384679] Crash when applying a partition move operation on LVM2 partition
https://bugs.kde.org/show_bug.cgi?id=384679 --- Comment #4 from Andrius Štikonas --- Hmm, I don't think debug symbols worked. Can we try one more time. Make sure you have both partitionmanager-dbgsym and partitionmanager-dbg. If it still doesn't work, I'll download neon lts... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384473] Missing icon sizes
https://bugs.kde.org/show_bug.cgi?id=384473 --- Comment #4 from mandian --- Hi, I did my best to submit the patch at phabricator. I do not find it so easy, at least at first time so I hope I did it fine. The link is: https://phabricator.kde.org/D7810 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384679] Crash when applying a partition move operation on LVM2 partition
https://bugs.kde.org/show_bug.cgi?id=384679 --- Comment #3 from Revolt media --- Also, I updated to kde partition manager 3.1.2 Still crashes. Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fda3dc2d940 (LWP 11194))] Thread 3 (Thread 0x7fda27310700 (LWP 11196)): #0 0x7fda39e5470d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fda3548238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fda3548249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fda3a77475b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fda3a71f0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fda3a54ef64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fda3dd8f735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda3a553b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fda36ed26ba in start_thread (arg=0x7fda27310700) at pthread_create.c:333 #9 0x7fda39e603dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fda2d0fb700 (LWP 11195)): #0 0x7fda39e5470d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fda34dcbc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fda34dcd8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fda2f44dd79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fda3a553b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fda36ed26ba in start_thread (arg=0x7fda2d0fb700) at pthread_create.c:333 #6 0x7fda39e603dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fda3dc2d940 (LWP 11194)): [KCrash Handler] #6 0x in ?? () #7 0x7fda3d787ac2 in PartWidget::paintEvent(QPaintEvent*) () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.5 #8 0x7fda3b046f38 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7fda3afffecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fda3b0078c6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fda3a7210c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fda3b03fd7a in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fda3b0403c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fda3b04108c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fda3b040f79 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fda3b03ff31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fda3b04108c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fda3b03ff31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fda3b04108c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fda3b03ff31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fda3b010002 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fda3b0101dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fda3b02eebf in QWidgetPrivate::syncBackingStore() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fda3b047008 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7fda3b144e3b in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fda3cf17217 in KMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #27 0x7fda3cf5c495 in KXml
[systemsettings] [Bug 384680] New: Segmentation fault under wayland when clicking on configure
https://bugs.kde.org/show_bug.cgi?id=384680 Bug ID: 384680 Summary: Segmentation fault under wayland when clicking on configure Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: kde...@gmail.com Target Milestone: --- How to reproduce: 1.Open system settings 2.Click on configure 3.Segmentation fault == Version === KWin version: 5.10.90 Qt Version: 5.9.1 Qt compile version: 5.9.1 XCB compile version: 1.11.1 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11903000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 1, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: LP156WD1-TLB LVDS-1-unknown Geometry: 0,0,1600x900 Refresh Rate: 59.99 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile OpenGL version string: 3.0 Mesa 17.0.7 OpenGL platform interface: EGL OpenGL shading language version string: 1.30 Driver: Intel GPU class: SandyBridge OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 17.0.7 Linux kernel version: 4.10 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom slidingpopups kwin4_effect_logout kwin4_effect_login kwin4_effect_windowaperture slide kwin4_effect_translucency screenshot minimizeanimation desktopgrid colorpicker kwin4_effect_morphingpopups kwin4_effect_maximize kwin4_effect_frozenapp kwin4_effect_fade presentwindows highlightwindow kwin4_effect_dialogparent blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_logout: kwin4_effect_login: kwin4_effect_windowaperture: sl
[partitionmanager] [Bug 384679] Crash when applying a partition move operation on LVM2 partition
https://bugs.kde.org/show_bug.cgi?id=384679 --- Comment #2 from Revolt media --- (In reply to Andrius Štikonas from comment #1) > Hmm, strange that it crashes in Partition::sectorsUsed function. There used > to be a bug in that function (e.g. #365872) but not in version 3.1.0. > > Can you try to reproduce the crash with debug symbols installed, so that I > get more information about the location of the crash? I followed instructions here https://wiki.ubuntu.com/Debug%20Symbol%20Packages to install debug symbols but I'm not sure it worked correctly, let me know if this helps. This is on KDE Neon LTS 5.8 Live USB Application: partitionmanager (3.1.0) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.8.0-58-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5bf885d940 (LWP 6382))] Thread 2 (Thread 0x7f5be5fee700 (LWP 6384)): #0 0x7f5bf4a8470d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5bf00b238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5bf00b249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5bf53a475b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5bf534f0ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5bf517ef64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5bf89bf735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f5bf5183b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5bf1b026ba in start_thread (arg=0x7f5be5fee700) at pthread_create.c:333 #9 0x7f5bf4a903dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f5bf885d940 (LWP 6382)): [KCrash Handler] #4 0x7f5bf83761bf in Partition::sectorsUsed() const () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.5 #5 0x7f5bf83b74cc in PartWidget::paintEvent(QPaintEvent*) () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.5 #6 0x7f5bf5c76f38 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f5bf5c2fecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f5bf5c378c6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f5bf53510c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f5bf5c6fd7a in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f5bf5c703c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f5bf5c7108c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f5bf5c70f79 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f5bf5c6ff31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f5bf5c7108c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f5bf5c6ff31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f5bf5c7108c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f5bf5c6ff31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f5bf5c40002 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f5bf5c401dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f5bf5c5eebf in QWidgetPrivate::syncBackingStore() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f5bf5c77008 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f5bf5d74e3b in QMainWindow::e
[partitionmanager] [Bug 305469] Adding a new mount point using 'Edit mount point' deleted existing entries in /etc/fstab
https://bugs.kde.org/show_bug.cgi?id=305469 --- Comment #9 from Andrius Štikonas --- I added fstab parsing function to kpmcore, so that we don't have to rely on glibc's getmntend https://cgit.kde.org/kpmcore.git/commit/?id=34712dd2ed499dd2c78ea07de9b3b499f32c86f7 It reads comments as well. However, partition manager still needs to be ported to use this new code. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384603] Camera Creation Date not set from EXIF data
https://bugs.kde.org/show_bug.cgi?id=384603 --- Comment #13 from digi...@homemp3.dyndns.org --- Even simpler: I found out that simply touching the file (updating the last modified timestamp in the file system, using the "touch" command) and then re-reading the metadata from file gives the file its Camera Creation Time (which is then correctly taken from the EXIF tag, not the file timestamp). This seems to imply that Digikam is keeping state about whether a file has changed since last read, and the "re-read ..." command seems a no-op if the file modification time is at or before the time when Digikam thinks it read the file last. I would expect an explicit "re-read..." operation to re-read, no matter what the time stamps say. Above and beyond that, of course, the root cause for the missing Camera Creation Date needs to be found, particularly after Mike suggested that an empty Camera Creation Date cannot occur at all (although it does here). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384679] Crash when applying a partition move operation on LVM2 partition
https://bugs.kde.org/show_bug.cgi?id=384679 --- Comment #1 from Andrius Štikonas --- Hmm, strange that it crashes in Partition::sectorsUsed function. There used to be a bug in that function (e.g. #365872) but not in version 3.1.0. Can you try to reproduce the crash with debug symbols installed, so that I get more information about the location of the crash? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384584] Callee saved registers listed first for AMD64, X86, and PPC architectures
https://bugs.kde.org/show_bug.cgi?id=384584 --- Comment #4 from Ivo Raisr --- The part with %rax, %rcx, %rdx, %r11 removal from getRegUsage_AMD64Instr() will be removed from the patch. The reason is explained in greater detail in: Bug 384676 - VEX AMD64 backend should list more real registers as available for the register allocator https://bugs.kde.org/show_bug.cgi?id=384676 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384584] Callee saved registers listed first for AMD64, X86, and PPC architectures
https://bugs.kde.org/show_bug.cgi?id=384584 Ivo Raisr changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=384676 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384676] VEX AMD64 backend should list more real registers as available for the register allocator
https://bugs.kde.org/show_bug.cgi?id=384676 Ivo Raisr changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=384584 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384603] Camera Creation Date not set from EXIF data
https://bugs.kde.org/show_bug.cgi?id=384603 --- Comment #12 from digi...@homemp3.dyndns.org --- I did another experiment: when I open one of the JPG files affected with GIMP and simply export it again as JPG, keeping all EXIF information, the timestamp is updated property when refreshing the folder. It almost seems as if for some reason the update only happens when the file's contents change (I suppose exporting from GIMP slightly modifies the binary content compared to how the camera produced the JPG). -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 --- Comment #3 from Mayeul Cantan --- Comment on attachment 107842 --> https://bugs.kde.org/attachment.cgi?id=107842 Passing cue file Note that this isn't a useful cue file, and k3b will still output an error, but not the same as the other file. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 380459] read out loud
https://bugs.kde.org/show_bug.cgi?id=380459 Albert Astals Cid changed: What|Removed |Added Resolution|WAITINGFORINFO |--- CC||aa...@kde.org Status|NEEDSINFO |UNCONFIRMED --- Comment #2 from Albert Astals Cid --- It is, see ui/tts.cpp fpg which distribution are you using? You need to use one that provides the dependency for Qt5TextToSpeech -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 Mayeul Cantan changed: What|Removed |Added Attachment #107841|text/plain |application/x-cue mime type|| Attachment #107841|Failing test file |Failing cue file description|| -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 --- Comment #2 from Mayeul Cantan --- Created attachment 107842 --> https://bugs.kde.org/attachment.cgi?id=107842&action=edit Passing cue file -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 384679] New: Crash when applying a partition move operation on LVM2 partition
https://bugs.kde.org/show_bug.cgi?id=384679 Bug ID: 384679 Summary: Crash when applying a partition move operation on LVM2 partition Product: partitionmanager Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: kdebugs...@revoltmedia.com Target Milestone: --- Application: partitionmanager (3.1.0) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.8.0-58-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: I have 4 partitions, with empty space between 3 and 4. I was attempting to move that partition (LVM2 LUKS) adjacent to the previous partition(where empty space currently is) Crash happens when hitting apply. The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7faa37edf940 (LWP 2694))] Thread 2 (Thread 0x7faa25670700 (LWP 2696)): #0 0x7faa3410670d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7faa2f73438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7faa2f73449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7faa34a2675b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7faa349d10ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7faa34800f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7faa38041735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7faa34805b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7faa311846ba in start_thread (arg=0x7faa25670700) at pthread_create.c:333 #9 0x7faa341123dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7faa37edf940 (LWP 2694)): [KCrash Handler] #4 0x7faa379f8230 in Partition::sectorsUsed() const () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.5 #5 0x7faa37a394cc in PartWidget::paintEvent(QPaintEvent*) () from /usr/lib/x86_64-linux-gnu/libkpmcore.so.5 #6 0x7faa352f8f38 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7faa352b1ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7faa352b98c6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7faa349d30c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7faa352f1d7a in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7faa352f23c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7faa352f308c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7faa352f2f79 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7faa352f1f31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7faa352f308c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7faa352f1f31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7faa352f308c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7faa352f1f31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7faa352c2002 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7faa352c21dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7faa352e0ebf in QWidgetPrivate::syncBackingStore() () from /u
[k3b] [Bug 384678] K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 --- Comment #1 from Mayeul Cantan --- Created attachment 107841 --> https://bugs.kde.org/attachment.cgi?id=107841&action=edit Failing test file -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384678] New: K3b fails reading cue files with title larger than 80 bytes
https://bugs.kde.org/show_bug.cgi?id=384678 Bug ID: 384678 Summary: K3b fails reading cue files with title larger than 80 bytes Product: k3b Version: 17.08.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Image Formats Assignee: k...@kde.org Reporter: mayeul.can...@live.fr CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Hello there, I was batch-converting some music files with k3b, ripped with cue files, and it looks like k3b fails to parse the cue file if the TITLE section is larger than 80 bytes. For now, I ran `LANG=C sed -i 's/TITLE\s\+"\(.\{80\}\).\+"/TITLE "\1"/' *.cue` on my files, but this is less than ideal. Tested with k3b 17.08.1 on Arch linux (this version doesn't appear on the bug tracker page). k3b fails with: (K3b::CueFileParser) unknown Cue line: ' "TITLE \"This is a title wider than 80 bytes**\"" ' What's nice is that the bug is EXTREMELY EASY to reproduce: just create a file with the following line and a .cue extension. TITLE "This is a title wider than 80 bytes*" Remove a star, and you instead get: (K3b::CueFileParser) successfully parsed cue file. I would like to see the following happening: - Support for titles longer than 80 bytes, with unicode if possible - If too complicated, cut the title to 80 bytes and warn the user - If this can't be implemented because of manpower constraints, at least provide a decent error message. I could try to do it myself, but I suspect that it will take no time to fix for someone familiar with the codebase. Thanks for maintaining k3b, Mayeul -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384383] dolphin crash w/o kde desktop
https://bugs.kde.org/show_bug.cgi?id=384383 Christoph Feck changed: What|Removed |Added Resolution|BACKTRACE |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #4 from Christoph Feck --- The crash is in the Qt GUI library. It looks like your system has no valid OpenGL configuration, and this confuses Qt. I suggest to report it directly to Qt developers via https://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 384193] [Wayland] Dolphin misplaced context menu + Crash
https://bugs.kde.org/show_bug.cgi?id=384193 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- The crash is a duplicate. *** This bug has been marked as a duplicate of bug 381032 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381032] Crashes when Wayland shows a transient window [wl_shell_surface_set_transient, wl_proxy_marshal_array_constructor]
https://bugs.kde.org/show_bug.cgi?id=381032 Christoph Feck changed: What|Removed |Added CC||jodr...@live.com --- Comment #12 from Christoph Feck --- *** Bug 384193 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 374803] How to change start of the week from Monday to Sunday?
https://bugs.kde.org/show_bug.cgi?id=374803 Allen Winter changed: What|Removed |Added Resolution|WONTFIX |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #4 from Allen Winter --- have you tried setting Locale to he_IL or en_LI? I wonder what happens then. I'm not against adding a special first day of week setting in KOrganizer. I can see where if could come in handy for example if you are working remotely for a company that doesn't observe the same locale as you. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 382686] Dolphin crashed when I was working with multiple tabs
https://bugs.kde.org/show_bug.cgi?id=382686 Christoph Feck changed: What|Removed |Added Resolution|BACKTRACE |INVALID Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[valgrind] [Bug 384676] VEX AMD64 backend should list more real registers as available for the register allocator
https://bugs.kde.org/show_bug.cgi?id=384676 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #1 from Ivo Raisr --- Created attachment 107840 --> https://bugs.kde.org/attachment.cgi?id=107840&action=edit patch -- 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 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from Christoph Feck --- People are annoyed by the autoscaling of icon size in the file dialog places panel, so it certainly should be optional. See bug 182089. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 381910] New user: Starting kleopatra shows 'loading certificate cache ...' forever
https://bugs.kde.org/show_bug.cgi?id=381910 --- Comment #3 from jat...@gmail.com --- More details on system and packages: Linux hostname 4.12.8-2-ARCH #1 SMP PREEMPT Fri Aug 18 14:08:02 UTC 2017 x86_64 GNU/Linux gnupg 2.2.0-1 kleopatra 17.08.1-1 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 381910] New user: Starting kleopatra shows 'loading certificate cache ...' forever
https://bugs.kde.org/show_bug.cgi?id=381910 jat...@gmail.com changed: What|Removed |Added CC||jat...@gmail.com --- Comment #2 from jat...@gmail.com --- I am affected by this bug as well on Arch Linux (fully up-to-date). Trying to list secret keys with both of those gpg commands causes a hang on my system too. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 255603] exp-sgcheck Assertion '!already_present' failed
https://bugs.kde.org/show_bug.cgi?id=255603 Philippe Waroquiers changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #9 from Philippe Waroquiers --- Fixed in commit 621cde90f7d23e916d3ce2716df02d261a72f5f3 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 384677] Missing converting for X-messaging/facebook-All during export to vcard
https://bugs.kde.org/show_bug.cgi?id=384677 Michal Jurzykowski changed: What|Removed |Added CC||michal.jurzykow...@email.cz -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 384677] New: Missing converting for X-messaging/facebook-All during export to vcard
https://bugs.kde.org/show_bug.cgi?id=384677 Bug ID: 384677 Summary: Missing converting for X-messaging/facebook-All during export to vcard Product: kaddressbook Version: GIT Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: michal.jurzykow...@email.cz CC: to...@kde.org Target Milestone: --- Hello, during export to vcard kaddressbook converts many its internal tags for messaging to standard identifier, for example: X-messaging/xmpp-All -> X-JABBER But for X-messaging/facebook-All there is not any converting. So vcard contains X-messaging/facebook-All tag and this is invalid format and some tools/libraries are not able to work with it. Please could you convert it to valid identifier for instance X-FACEBOOK Thank you. Michal -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384676] VEX AMD64 backend should list more real registers as available for the register allocator
https://bugs.kde.org/show_bug.cgi?id=384676 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org |iv...@ivosh.net Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384676] New: VEX AMD64 backend should list more real registers as available for the register allocator
https://bugs.kde.org/show_bug.cgi?id=384676 Bug ID: 384676 Summary: VEX AMD64 backend should list more real registers as available for the register allocator Product: valgrind Version: 3.14 SVN Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: iv...@ivosh.net Target Milestone: --- Currently host_amd64_defs.* list RAX, RCX and RDX as not available to the register allocator. I think this is a mistake and they should be made available. The more Int64 registers available to the register allocator, the better is the final produced code. Running Valgrind regression test suite shows that %rcx and %rdx can be enabled with no problems. For %rax there is some unimplemented functionality (search for FIXME in host_amd64_defs.c) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 378701] Option to disable frames with shadows on selected directories
https://bugs.kde.org/show_bug.cgi?id=378701 --- Comment #6 from Christoph Feck --- The patch was submitted, see https://phabricator.kde.org/D5420 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 255603] exp-sgcheck Assertion '!already_present' failed
https://bugs.kde.org/show_bug.cgi?id=255603 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be Summary|Assertion |exp-sgcheck Assertion |'!already_present' failed |'!already_present' failed -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 376207] Formatted name is not selectable when creating new contact
https://bugs.kde.org/show_bug.cgi?id=376207 Michal Jurzykowski changed: What|Removed |Added CC||michal.jurzykow...@email.cz --- Comment #1 from Michal Jurzykowski --- Additionally, the missing tag "FN" causes an error during import to other systems or synchronization. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 372311] clang detection in FindPythonModuleGeneration.cmake only works in Debian/Ubuntu
https://bugs.kde.org/show_bug.cgi?id=372311 --- Comment #3 from Antonio Rojas --- Equivalent simpler patch: https://git.archlinux.org/svntogit/packages.git/tree/trunk/fix-python-bindings-generation.patch?h=packages/extra-cmake-modules There's an alternative approach in https://phabricator.kde.org/D5289 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384642] Geolocation doesn't appear in digiKam for MacOS and Windows : Marble header files are not installed, only the libraries.
https://bugs.kde.org/show_bug.cgi?id=384642 hardy.pub...@gmail.com changed: What|Removed |Added CC||hardy.pub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380972] Overlapping labels on front page
https://bugs.kde.org/show_bug.cgi?id=380972 --- Comment #3 from Fabian Vogt --- Ping. This makes a default non-english install look awful. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 384675] New: collection update does not find directories with special characters
https://bugs.kde.org/show_bug.cgi?id=384675 Bug ID: 384675 Summary: collection update does not find directories with special characters Product: amarok Version: 2.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Collections/Local Assignee: amarok-bugs-d...@kde.org Reporter: bart.de_ceul...@telenet.be CC: ma...@laitl.cz, ralf-eng...@gmx.de Target Milestone: 2.9 Looks like duplicate of Bug 189527 (which should be solved long time ago) When running amarok in debug mode (amarok -d) and doing an "update collection", the log shows several lines like this : Directory "/fet1/Audio/Classical/Frdric Chopin/" does not exist. The actual directory name is "/fet1/Audio/Classical/Frédéric Chopin/" Amarok diagnostics window : Amarok Version: 2.8.0 KDE Version: 4.14.35 Qt Version: 4.8.7 Phonon Version: 4.9.0 Phonon Backend: GStreamer (4.9.0) PulseAudio: Yes Amarok Scripts: Amarok Script Console 1.0 (stopped) Lyricwiki .2 (running) Free Music Charts 1.6.0 (stopped) Librivox.org 1.0 (stopped) Cool Streams 1.0 (stopped) Amarok Plugins: AudioCd Collection (disabled) DAAP Collection (disabled) MTP Collection (disabled) MySQLServer Collection (enabled) MySQLe Collection (enabled) UPnP Collection (disabled) Universal Mass Storage Collection (enabled) iPod, iPad & iPhone Collection (disabled) Ampache (disabled) Jamendo (disabled) Last.fm (disabled) MP3 Music Store (disabled) MP3tunes (disabled) Magnatune Store (disabled) Podcast Directory (disabled) gpodder.net (disabled) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 384674] Keyboard overview showing used global shortcuts when assigning global shortcuts
https://bugs.kde.org/show_bug.cgi?id=384674 Johannes Tophøj Rasmussen changed: What|Removed |Added CC||johannes.top...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 384674] New: Keyboard overview showing used global shortcuts when assigning global shortcuts
https://bugs.kde.org/show_bug.cgi?id=384674 Bug ID: 384674 Summary: Keyboard overview showing used global shortcuts when assigning global shortcuts Product: systemsettings Version: 5.10.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: johannes.top...@gmail.com Target Milestone: --- When configuring global shortcuts it can be preferable to select a group of shortcuts for a group of actions on keys that layed out in a specific pattern, e.g. close to each other. A view of the keyboard layout (similar to the one shown when selecting keyboard layout during the install process of many distros) where symbols on each key indicate if they are taken by the plain modifier keys. Pressing the modifier keys (or combinations hereof, e.g. ctrl+shift) could update the key colours if they are taken or not. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 384673] New: Global show/hide shortcut does not work
https://bugs.kde.org/show_bug.cgi?id=384673 Bug ID: 384673 Summary: Global show/hide shortcut does not work Product: ktorrent Version: 5.1 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: mini...@poczta.onet.pl Target Milestone: --- Global "Show/hide KTorrent" keyboard shortcut doesn't work. Steps to reproduce 1. Go to System Settings -> Shortcuts -> Global shortcuts -> KTorrent 2. Make sure that there is some shortcut for "Show/hide KTorrent" entry (Alt+Shift+W in my case; Alt+Shift+T by default) 3. Press shortcut set in previous step Expected results KTorrent window appears (if it was hidden). KTorrent window disappears (if it was visible). Actual results Nothing happens -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384667] Java applications appear in same icon
https://bugs.kde.org/show_bug.cgi?id=384667 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Eike Hein --- These are application bugs that need to be fixed by the respective application developers by setting WM_CLASS and/or StartupWMClass correctly. Java developers are for some reason notoriously bad at this. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 372311] clang detection in FindPythonModuleGeneration.cmake only works in Debian/Ubuntu
https://bugs.kde.org/show_bug.cgi?id=372311 --- Comment #2 from Rex Dieter --- As far as I'm concerned, this simple patch works: diff -up extra-cmake-modules-5.38.0/find-modules/FindPythonModuleGeneration.cmake.fedora extra-cmake-modules-5.38.0/find-modules/FindPythonModuleGeneration.cmake --- extra-cmake-modules-5.38.0/find-modules/FindPythonModuleGeneration.cmake.fedora 2017-09-03 13:34:35.0 -0500 +++ extra-cmake-modules-5.38.0/find-modules/FindPythonModuleGeneration.cmake 2017-09-13 13:41:07.333687678 -0500 @@ -199,6 +199,9 @@ if (NOT libclang_LIBRARY) find_library(libclang_LIBRARY clang-3.9) if (NOT libclang_LIBRARY) find_library(libclang_LIBRARY clang-3.8) + if (NOT libclang_LIBRARY) +find_library(libclang_LIBRARY clang) + endif() endif() endif() else() -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 363852] Ktorrent no longer starts hidden in tray
https://bugs.kde.org/show_bug.cgi?id=363852 Mirosław Zalewski changed: What|Removed |Added CC||mini...@poczta.onet.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384660] Part of the screen(s) "often" flickers when showing windows
https://bugs.kde.org/show_bug.cgi?id=384660 --- Comment #3 from Martin Flöser --- Is the hardware the same except for the graphics card? If yes I strongly suggest to do a test of the hardware. What you experience is not normal. It might be driver specific, but that we see such distortions across different drivers is not normal. I have never seen any reports like yours. This indicates to me that there is a problem with your setup - either a general problem with the underlying Linux system or with hardware. Given the look it might be a memory issue. -- You are receiving this mail because: You are watching all bug changes.