[digikam] [Bug 379526] Inconsistent separator use in mime setup
https://bugs.kde.org/show_bug.cgi?id=379526 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Hi Simon, There is extension of file with space separator ? I never seen something as "foo.jpg tar.gz". This will not work in source code which handle files. I understand well your description ? In my example "jpg tar.gz" is the expected extension. This is exactly what you want to manage with your patch ? The scheme for multiple extension is to use dot separator. exemple : jpg.tar.gz. This one is well supported by Qt de facto. Gilles Gilles -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 379569] Korganizer crashes when program is closed
https://bugs.kde.org/show_bug.cgi?id=379569 Laurent Montelchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |WONTFIX --- Comment #1 from Laurent Montel --- 4.14.10 is very old. It's unmaintained. Please use 5.5.x and reopen it. Regards. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372672] File Renaming Options sidebar is missing
https://bugs.kde.org/show_bug.cgi?id=372672 --- Comment #8 from caulier.gil...@gmail.com --- Look in Setup dialog, Misc options. There is one entry to configure the sidebar tab behavior Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379511] Introduce additional sidecar types and fix bug in mime setup [patch]
https://bugs.kde.org/show_bug.cgi?id=379511 --- Comment #5 from caulier.gil...@gmail.com --- Note : There is an entry in bugzilla about the all sidecar files support. Look here : https://bugs.kde.org/show_bug.cgi?id=193232 Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379511] Introduce additional sidecar types and fix bug in mime setup [patch]
https://bugs.kde.org/show_bug.cgi?id=379511 --- Comment #4 from caulier.gil...@gmail.com --- Hi Simon, yes a new tab in Metadata panel will be fine to host this kind of settings. In fact i will see a dedicated tab for all sidecar settings. There are many entries in bugzilla about sidecars management. So, in "Behavior" tab, moving : - Read from sidecar files - Write from sidecar files + combo options ... To the new "Sidecar Files" tab will be logic. I recommend to put a tip label in "Reading and Writing" group-box to indicate that sidecar options are now placed in a dedicated tab. Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379571] New: plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=379571 Bug ID: 379571 Summary: plasmashell crash Product: plasmashell Version: 5.9.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sstrin...@shaniac.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.13-1-vfio x86_64 Distribution: "Arch Linux" -- Information about the crash: Using simplemenu plasmoid, I right-clicked on an icon to add it to the Favorites page. I did not get the context menu. Instead, plasmashell crashed. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2aa4c4c800 (LWP 1605))] Thread 11 (Thread 0x7f29ede2b700 (LWP 1770)): #0 0x7f2a9d8af756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f29f43e60cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f29f43e5df7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f2a9d8a92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2a9e30754f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f29ee62c700 (LWP 1769)): #0 0x7f2a9d8af756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f29f43e60cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f29f43e5df7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f2a9d8a92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2a9e30754f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f29eee2d700 (LWP 1768)): #0 0x7f2a9d8af756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f29f43e60cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f29f43e5df7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f2a9d8a92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2a9e30754f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f29ef62e700 (LWP 1767)): #0 0x7f2a9d8af756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f29f43e60cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f29f43e5df7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f2a9d8a92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2a9e30754f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f29f0034700 (LWP 1766)): #0 0x7f2a9d8af756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f29f43e60cb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f29f43e5df7 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f2a9d8a92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2a9e30754f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f2a76b9c700 (LWP 1765)): #0 0x7f2a9d8af756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2aa43cf234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f2aa43cf279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f2a9d8a92e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2a9e30754f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f2a84b5b700 (LWP 1756)): #0 0x7f2a9e2fd67d in poll () at /usr/lib/libc.so.6 #1 0x7f2a990d89b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f2a990d8acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f2a9ec2409b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f2a9ebcd8ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f2a9e9efa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f2aa1b28025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f2a9e9f46d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f2a9d8a92e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f2a9e30754f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f2a86be9700 (LWP 1744)): #0 0x7f2a9e2fd67d in poll () at /usr/lib/libc.so.6 #1 0x7f2a990d89b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f2a990d8acc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f2a9ec2409b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f2a9ebcd8ca in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f2a9e9efa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f2aa1b28025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f2a9e9f46d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f2a9d8a92e7 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f2a9e30754f in
[krusader] [Bug 332791] crash after stopping queued transfer
https://bugs.kde.org/show_bug.cgi?id=332791 xerosto...@seznam.cz changed: What|Removed |Added CC||xerosto...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 332791] crash after stopping queued transfer
https://bugs.kde.org/show_bug.cgi?id=332791 --- Comment #2 from xerosto...@seznam.cz --- Created attachment 105364 --> https://bugs.kde.org/attachment.cgi?id=105364=edit New crash information added by DrKonqi krusader (2.4.0-beta3 "Single Step") on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Cancel copiing queue while generating directories on the new disk. -- Backtrace (Reduced): #6 KIOJobWrapper::createJob (this=0x0) at /build/buildd/krusader-2.4.0~beta3/krusader/VFS/kiojobwrapper.cpp:135 #7 0x0058d12d in KrJobStarter::event (this=, e=) at /build/buildd/krusader-2.4.0~beta3/krusader/VFS/kiojobwrapper.cpp:71 #8 0x7fd77d6cafdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #9 0x7fd77d6d1f16 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x7fd77ff8864a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374546] Issue with content encoding
https://bugs.kde.org/show_bug.cgi?id=374546 Vishnuchanged: What|Removed |Added Summary|Use quoted-printable or |Issue with content encoding |base64 instead of 7-bit | |encoding| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379570] New: KDE crash when I was using steam.
https://bugs.kde.org/show_bug.cgi?id=379570 Bug ID: 379570 Summary: KDE crash when I was using steam. Product: plasmashell Version: 5.8.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: twoentart...@hotmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.2) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.27-2-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed and unusual behavior I noticed: I installed steam by zypper and when I type my steam user name, I find that my name did not show up in the box. About 1 second later, steam exited by itself. Almost at the same time, the KDE desktop exited (all panels disappear) and re-opened. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f61f699a900 (LWP 1509))] Thread 16 (Thread 0x7f6105282700 (LWP 9527)): #0 0x7f61ef8c60af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61f07ad65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f612e10b42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f612e10edea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f612e10945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f612e10ee32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f612e10945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f612e10ca46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f61f07ac9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f61ef8c1734 in start_thread () at /lib64/libpthread.so.0 #10 0x7f61f00c0d3d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f6105a83700 (LWP 9526)): #0 0x7f61ef8c60af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61f07ad65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f612e10b42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f612e10edea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f612e10945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f612e10ca46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f61f07ac9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f61ef8c1734 in start_thread () at /lib64/libpthread.so.0 #8 0x7f61f00c0d3d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f6106284700 (LWP 9525)): #0 0x7f61ef8c60af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61f07ad65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f612e10b42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f612e10edea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f612e10945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f612e10ee32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f612e10945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f612e10ee32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f612e10945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f612e10ee32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f612e10945b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f612e10ca46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f61f07ac9e9 in () at /usr/lib64/libQt5Core.so.5 #13 0x7f61ef8c1734 in start_thread () at /lib64/libpthread.so.0 #14 0x7f61f00c0d3d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f6106a85700 (LWP 9524)): #0 0x7f61ef8c60af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61f07ad65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2
[krita] [Bug 379564] brush size slider is disabled when switching from smart patch tool
https://bugs.kde.org/show_bug.cgi?id=379564 Quiraltachanged: What|Removed |Added CC||rjquira...@gmail.com --- Comment #1 from Quiralta --- I can confirm it, but for me this happens as soon as I open Krita, the bar looks active but as soon as I touch the tablet (first stroke) regardless of the tool, the bar gets disabled. The Smart Patch Tool is the only one where the slider is active, thus I don't need to select it first to trigger the behavior as Scott's steps. Side note, also the tooltip for this tool has some odd characters at the end of the name. specs: master build, archlinux, plasma, nvidia. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 379003] Wallpaper "Picture of the Day" from National Geographics only changing after reboot or not at all.
https://bugs.kde.org/show_bug.cgi?id=379003 --- Comment #8 from Juri Vitali--- Created attachment 105363 --> https://bugs.kde.org/attachment.cgi?id=105363=edit NatGeo POTD patch I implemented a quick and dirty patch to parse the page using QRegularExpression, and it seems to be working (and much faster than before, but that may be just my impression). Can anyone confirm if this works for someone else too? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 Christian Gonzálezchanged: What|Removed |Added CC||chgonzal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379535] Combining 4-byte utf8 characters with color-changing ansi escapes gives extra spaces on output
https://bugs.kde.org/show_bug.cgi?id=379535 --- Comment #3 from Tom Littauer--- Thanks, Egmont. I have no insight into internals at all, but was also struck by the fact that the playing card showed up. It seemed to me that if it shows up it must be OK to use. If it were not supported I would have expected the same empty box you get when you use a glyph you don't have installed. By the way, if using an uninstalled 4-byte glyph you get an empty box that exhibits the same odd space behavior. As for no 4-byte glyphs, that will make the users of Emoji unhappy, as many of them are in 4-byte territory. Thank you both for taking the time to look into the situation. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379535] Combining 4-byte utf8 characters with color-changing ansi escapes gives extra spaces on output
https://bugs.kde.org/show_bug.cgi?id=379535 Egmont Koblingerchanged: What|Removed |Added CC||egm...@gmail.com --- Comment #2 from Egmont Koblinger --- Just wondering, how come then that the Ace of Clubs symbols gets shown at all? :) Combining accents are supported too, so maybe for non-BMP you allocate two QChars per cell using UTF-16 encoding? Notice that highlighting with the mouse is a pretty interesting experience. As you drag the mouse slowly from the left to the right, at every second step you get to see two replacement symbols (one being highlighted and one not). This might be related to the first QChar of a UTF-16 being selected only. And in each step the remaining (not yet highlighted) playing cards are slowly pushed to the right to fill up the gap. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 379569] New: Korganizer crashes when program is closed
https://bugs.kde.org/show_bug.cgi?id=379569 Bug ID: 379569 Summary: Korganizer crashes when program is closed Product: korganizer Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kde...@scaltro.net Target Milestone: --- Application: korganizer (4.14.10) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.39-53-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: application works without problem but crashes when I try to close it. The problem is persistent. The user account data has been transferred from a different system and the file system with config and caches went full a couple of times while application was running. I was trying to clean up caches. This seemed to help for a short period of times but after a while the crashes came back and stayed until now. No full filesystem and migration since cache cleanup. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f799f607600 in QAbstractSlider::maximum() const () at /usr/lib64/libQtGui.so.4 #7 0x7f79a08ef334 in () at /usr/lib64/libkdeui.so.5 #8 0x7f799fed545e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #9 0x7f799f2576fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #10 0x7f799f25dc3d in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #11 0x7f79a091ee3a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #12 0x7f799febd14d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #13 0x7f799fec041d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #14 0x7f799feea7be in () at /usr/lib64/libQtCore.so.4 #15 0x7f79977a5c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #16 0x7f79977a5ed8 in () at /usr/lib64/libglib-2.0.so.0 #17 0x7f79977a5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #18 0x7f799fee9f7e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #19 0x7f799f2f4606 in () at /usr/lib64/libQtGui.so.4 #20 0x7f799febbd0f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #21 0x7f799febc005 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #22 0x7f799fec1459 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #23 0x004082de in () #24 0x7f799e758b25 in __libc_start_main () at /lib64/libc.so.6 #25 0x004085a4 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 360821] Show xcf files (from Gimp 2.9) not (yet...) working
https://bugs.kde.org/show_bug.cgi?id=360821 --- Comment #10 from Janet--- (In reply to Christoph Feck from comment #2) > If possible, add a link with description of the new file format. I only > found references to the old file format. Might help? https://bugzilla.gnome.org/show_bug.cgi?id=782244 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379535] Combining 4-byte utf8 characters with color-changing ansi escapes gives extra spaces on output
https://bugs.kde.org/show_bug.cgi?id=379535 --- Comment #1 from Christoph Feck--- Konsole does not have support for non-BMP characters, because every cell is only stored as a QChar (which is 16 bits). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360506] Crash in XIQueryDevice
https://bugs.kde.org/show_bug.cgi?id=360506 Christoph Feckchanged: What|Removed |Added CC||m.arismendi.a...@gmail.com --- Comment #16 from Christoph Feck --- *** Bug 379536 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 379536] Error to click in the Shut down button
https://bugs.kde.org/show_bug.cgi?id=379536 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 360506 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374719] some spelling fixes
https://bugs.kde.org/show_bug.cgi?id=374719 --- Comment #2 from Ivo Raisr--- Thank you for the patch. It would be nice if you can rerun the analysis on the source code and also on the web pages. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374719] some spelling fixes
https://bugs.kde.org/show_bug.cgi?id=374719 Ivo Raisrchanged: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Ivo Raisr --- Fixed in SVN r16336. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 379347] Long filenames get truncated in the Recent Documents section
https://bugs.kde.org/show_bug.cgi?id=379347 --- Comment #3 from Eike Hein--- There might be an option to display more than one text line at some point. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 379568] New: Program crashes with high definition tv stations
https://bugs.kde.org/show_bug.cgi?id=379568 Bug ID: 379568 Summary: Program crashes with high definition tv stations Product: kaffeine Version: 2.0.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: jcly...@fuse.net Target Milestone: --- The program works fine for ATSC standard definition stations, but crashes within a few seconds when I switch to a high definition station with a segmentation fault. I am using RV610 [Radeon HD 2400 PRO] in a Dell Inspiron computer with Ubuntu 17.04. Here is the terminal output. In this session I viewed two standard def stations and then a high def station. jeffrey@inspiron:~$ kaffeine 05-05-17 17:20:15.024 [Info] Using built-in dvb device manager 05-05-17 17:20:15.359 [Info] Found dvb device : LG Electronics LGDT3305 VSB/QAM Frontend 05-05-17 17:20:15.447 [Warning ] Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/16/" 05-05-17 17:20:15.447 [Warning ] Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/22/" 05-05-17 17:20:15.448 [Warning ] Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/24/" 05-05-17 17:20:15.448 [Warning ] Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/32/" 05-05-17 17:20:15.449 [Warning ] Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/48/" 05-05-17 17:20:15.450 [Warning ] Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/64/" 05-05-17 17:20:15.450 [Warning ] Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/128/" 05-05-17 17:20:15.544 [Debug ] Refilling KProtocolInfoFactory cache in the hope to find "mtp" 05-05-17 17:20:15.821 [Warning ] KServiceTypeTrader: serviceType "ThumbCreator" not found 05-05-17 17:20:15.827 [Warning ] KServiceTypeTrader: serviceType "ThumbCreator" not found 05-05-17 17:20:16.130 [Warning ] KServiceTypeTrader: serviceType "ThumbCreator" not found 05-05-17 17:20:16.136 [Warning ] KServiceTypeTrader: serviceType "ThumbCreator" not found [7fea1001c7e8] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding. [7fe9e4022428] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding. [7fe9f00148f8] avcodec decoder: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding. Segmentation fault (core dumped) jeffrey@inspiron:~$ -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 363983] Add option to hide audio level change OSD popup
https://bugs.kde.org/show_bug.cgi?id=363983 Eike Heinchanged: What|Removed |Added CC||h...@kde.org --- Comment #4 from Eike Hein --- We were hitting this new checkbox at a dev sprint and not even Marco could make sense of what the label means ... could we overhaul that string somehow? :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 340392] Incorrect "Conditional jump..." message
https://bugs.kde.org/show_bug.cgi?id=340392 --- Comment #7 from Ivo Raisr--- Btw. the command line option is called '--expensive-definedness-checks' these days. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379495] sending keyboard input of repeating alternate case ignores case on second character
https://bugs.kde.org/show_bug.cgi?id=379495 --- Comment #1 from scott.notting...@gmail.com --- appears to be fixed in recent version cannot reproduce on 5.9.4 -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 379567] New: Big Break Now
https://bugs.kde.org/show_bug.cgi?id=379567 Bug ID: 379567 Summary: Big Break Now Product: rsibreak Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: aa...@kde.org Reporter: promike1...@gmail.com Target Milestone: --- I'm sorry to disturb you again but I think it would be useful and really easy to accomplish. If you think the opposite just ignore this report. So I thought on the right click menu somewhere around Suspend RSIBreak and Usage Statistics there could be a new option "Big Break Now" or just "Big Break" which would start a full screen big break immediately. As if the time was up. It would be possible to take big breaks earlier then. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 379347] Long filenames get truncated in the Recent Documents section
https://bugs.kde.org/show_bug.cgi?id=379347 --- Comment #2 from Nate Graham--- Indeed there is. That doesn't diminish the problem, though: 1. Mousing over the truncated lines of text one at a time is a frustrating experience. 2. Tooltips don't work with touch-based user interaction where there is no concept of hovering the cursor over something, and the Dashboard appears to be a very touch-centric user interface. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 379347] Long filenames get truncated in the Recent Documents section
https://bugs.kde.org/show_bug.cgi?id=379347 --- Comment #1 from Eike Hein--- There's a tooltip on hover (unless you disabled tooltips in System Settings). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379414] [Data Loss] - TaskManager loses launchers from alternative Activities
https://bugs.kde.org/show_bug.cgi?id=379414 Eike Heinchanged: What|Removed |Added CC||ivan.cu...@kde.org --- Comment #1 from Eike Hein --- I'm currently on a Wayland-focused Plasma dev sprint, but I'll try to look into this at some point this month. Sorry for delays. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 379566] Address Book should be stored under $XDG_DATA_HOME
https://bugs.kde.org/show_bug.cgi?id=379566 Elvis Angelacciochanged: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 379566] New: Address Book should be stored under $XDG_DATA_HOME
https://bugs.kde.org/show_bug.cgi?id=379566 Bug ID: 379566 Summary: Address Book should be stored under $XDG_DATA_HOME Product: trojita Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Other Assignee: trojita-b...@kde.org Reporter: elvis.angelac...@kde.org Target Milestone: --- Trojita currently stores the address book in the ~/.abook folder, but it would be more consistent if it used $XDG_DATA_HOME/trojita/abook instead (at least when trojita runs in a XDG-compliant [1] desktop). [1]: https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 365299] make transition from qtwebkit to qtwebengine
https://bugs.kde.org/show_bug.cgi?id=365299 Elvis Angelacciochanged: What|Removed |Added CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 368859] Use newer upstream gpgme to get rid of kf5-gpgmepp
https://bugs.kde.org/show_bug.cgi?id=368859 Elvis Angelacciochanged: What|Removed |Added CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379233] Can't pin an icon of TeamViewer on Icons-only Task Manager
https://bugs.kde.org/show_bug.cgi?id=379233 Eike Heinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #4 from Eike Hein --- > I added it do desktop now and here are the information .desktop file just means the .desktop file the app installs e.g. into /usr/share/applications, it's not about being on the desktop :) Anyway, basically this is the problem: WM_CLASS(STRING) = "TeamViewer.exe", "Wine" That "Wine" there is useless to be able to figure out that window belongs to that .desktop file. Its a bug TeamViewer needs to fix. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379559] [notifier] Also list updates in the notifier applet
https://bugs.kde.org/show_bug.cgi?id=379559 --- Comment #2 from Elvis Angelaccio--- Well, it would be quicker than Right click -> See Updates (which takes a while, at least here) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379513] Firefox + panel task manager + wayland weird behavior
https://bugs.kde.org/show_bug.cgi?id=379513 --- Comment #4 from Eike Hein--- This is basically because on Wayland we currently don't have all the window metadata the Task Manager needs for sorting, so the window title ends up being the sort string (to simplify), so the moving happens because the window title changes as you switch tabs. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 375080] Crash when trying tu use every to-do action and New-Event or New-Journal
https://bugs.kde.org/show_bug.cgi?id=375080 --- Comment #4 from Pierre Maraval--- Workaround found for Kubuntu 17.04: Update to PIM 16.12.3 (Kontact 5.4.3) by using the backports as described here: http://kubuntu.org/news/kde-pim-update-now-available-for-zesty-zapus-17-04/ Downside: Sorry no backtrace :\ -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379306] Zero values not showing up
https://bugs.kde.org/show_bug.cgi?id=379306 --- Comment #1 from Adam Pigg--- Can you attach an example? -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 379306] Zero values not showing up
https://bugs.kde.org/show_bug.cgi?id=379306 Jarosław Staniekchanged: What|Removed |Added Summary|ZERO VALUES NOT SHOWING UP |Zero values not showing up CC||stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376257] helgrind history full speed up using a cached stack
https://bugs.kde.org/show_bug.cgi?id=376257 --- Comment #3 from Ivo Raisr--- Hi Philippe, that's ok and thank you for letting us know! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379559] [notifier] Also list updates in the notifier applet
https://bugs.kde.org/show_bug.cgi?id=379559 Aleix Polchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Aleix Pol --- Why? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 375080] Crash when trying tu use every to-do action and New-Event or New-Journal
https://bugs.kde.org/show_bug.cgi?id=375080 Pierre Maravalchanged: What|Removed |Added CC||marava...@yahoo.fr --- Comment #3 from Pierre Maraval --- Kubuntu 17.04 Kontact 5.2.3 Steps to reproduce: 1. Open Kontact 2. Go to Calendar 3. Add New Event to remote or local calendar (Crash) 4. Open Kontact again 5. Go to Calendar (Crash) Using Akonadi-console or Kontact Settings one can delete the bugging resource to stop Steps 4 and 5 to lead to a crash. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379565] New: Impossble to load new windows theme
https://bugs.kde.org/show_bug.cgi?id=379565 Bug ID: 379565 Summary: Impossble to load new windows theme Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mathieu.fen...@epitech.eu Target Milestone: --- When we try to research new theme the window stay in initialization forever -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376257] helgrind history full speed up using a cached stack
https://bugs.kde.org/show_bug.cgi?id=376257 Philippe Waroquierschanged: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #2 from Philippe Waroquiers --- (In reply to Ivo Raisr from comment #1) > Hello Philippe, how are you doing with this patch? Have you been able to > polish it more? Hi Ivo, I see you are working hard to make a lot of things advance for the 3.13 release; Thanks for this hard work (a.o. the tilegx cleanup). I am sorry but I had very low free time to work on Valgrind, so I was not able to advance much on this. It will thus not make it for 3.13. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive
https://bugs.kde.org/show_bug.cgi?id=379521 --- Comment #2 from spa...@modanese.net --- Created attachment 105362 --> https://bugs.kde.org/attachment.cgi?id=105362=edit GDB backtrace (with symbols) Ah, I recompiled kscreenlocker with the debug symbols, but forgot about Qt :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 183429] open externally called folder in new tab
https://bugs.kde.org/show_bug.cgi?id=183429 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379437] One column text selection jumps to front
https://bugs.kde.org/show_bug.cgi?id=379437 --- Comment #3 from evea--- To narrow it down.. it happens in: Firfox Chrome Steam Thunderbird qbittorrent Vivaldi ArduinoIDE Atom Works as expected in: mumble dolphin octopi libreOffice -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher
https://bugs.kde.org/show_bug.cgi?id=351055 --- Comment #29 from Marian--- (In reply to Martin Gräßlin from comment #28) > > Where do I have to search for those icons to confirm? > > KWin takes the icon you can see in xprop. If there is only one in 32x32 that > one will be used. KWin does not use any installed icon as that is not how > it's supposed to be done for X11 window managers. > > For Qt/KDE applications we are able to use the installed icons thanks to an > extension. Maybe it could be possible to define a window rule for the > .desktop file of a window. Thanks for clarifying! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher
https://bugs.kde.org/show_bug.cgi?id=351055 --- Comment #28 from Martin Gräßlin--- > Where do I have to search for those icons to confirm? KWin takes the icon you can see in xprop. If there is only one in 32x32 that one will be used. KWin does not use any installed icon as that is not how it's supposed to be done for X11 window managers. For Qt/KDE applications we are able to use the installed icons thanks to an extension. Maybe it could be possible to define a window rule for the .desktop file of a window. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 379487] Elisa doesn’t handle non-default font/display settings
https://bugs.kde.org/show_bug.cgi?id=379487 Matthieu Gallienchanged: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Matthieu Gallien --- I did some tests using my TV screen. In my case some elements are correctly sized and others are too big. I am a bit surprised as in your case, the play button is too small. This is the opposite. Anyway, I am working on this issue. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 379448] There is no information
https://bugs.kde.org/show_bug.cgi?id=379448 --- Comment #3 from Cristian Aravena Romero--- $ sudo apt-get update [...] Err:16 http://ppa.launchpad.net/cdemu/ppa/ubuntu zesty/main i386 Packages 404 Not Found Ign:18 http://ppa.launchpad.net/cdemu/ppa/ubuntu zesty/main amd64 Packages [...] Ign:26 http://ppa.launchpad.net/cdemu/ppa/ubuntu zesty/main DEP-11 64x64 Icons Descargados 178 kB en 14s (12,7 kB/s) Leyendo lista de paquetes... Hecho W: El repositorio «http://ppa.launchpad.net/cdemu/ppa/ubuntu zesty Release» no tiene un fichero de Publicación. N: Los datos de un repositorio como este no se pueden autenticar y por tanto su uso es potencialmente peligroso. N: Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. E: Fallo al obtener http://ppa.launchpad.net/cdemu/ppa/ubuntu/dists/zesty/main/binary-i386/Packages 404 Not Found E: No se han podido descargar algunos archivos de índice, se han omitido, o se han utilizado unos antiguos en su lugar. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 331093] Current desktop not displayed in pager widget
https://bugs.kde.org/show_bug.cgi?id=331093 ska...@gmail.com changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from ska...@gmail.com --- Guessing the fate of this and closing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher
https://bugs.kde.org/show_bug.cgi?id=351055 Marianchanged: What|Removed |Added CC||mariana...@icloud.com --- Comment #27 from Marian --- (In reply to Martin Gräßlin from comment #26) > > I'd like to ask for some specific steps on fixing, for example, Firefox > > icons. > > This can only be fixed by Firefox by installing larger icons on their > windows. The version I use only installs a 48x48 icon and that's too small. > We would need icons of size 128x128 or better 512x512. That's something only > Firefox can do. So to get this fixed you would need to create a bug against > Firefox. Where do I have to search for those icons to confirm? I can reproduce this behaviour for so many applications. Take Vivaldi browser, it ships with a huge variety of dimensions of their icon in .png format in /opt/vivaldi AND in /usr/share/hicolor including sizes of 128 and 256 yet the large icon task switcher totally ignores them and any other icon provided in hicolor or the installed theme or pixmaps or /opt/vivaldi. Indeed xprop tells me that _NET_WM_ICON(CARDINAL) =Icon (32 x 32) Which to me looks like it's actually an issue with some programmed lines not so much icon structures, but that really doesn't help me at all. This is so annoying to even try to get a hint on where to start to report... Another test case for me is Nylas Mail. I played around with their icons in hicolor and pixmaps, replacing their original .png images with own ones. Now the task switcher shows the logo icon for X11 and there is no xprop for _NET_WM_ICON at all. And here is another completely weird example: Encryptr (password storage app). I can find a high resolution .png of their logo in /usr/share/pixmaps, no icons in /opt/encryptr, no icons in hicolor and apparently it has scalable svgs in the installed theme. Yet the large icon task switcher found a totally different high resolution icon for the application which I don't even remotely know where it could be stored since it's completely foreign to me and I have never seen it before nor can I find it in my installed themes...Here xprop tells me that: _NET_WM_ICON(CARDINAL) = Yet it shows a high resolution icon which is not the default X11 icon. Frustrating to debug... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379564] New: brush size slider is disabled when switching from smart patch tool
https://bugs.kde.org/show_bug.cgi?id=379564 Bug ID: 379564 Summary: brush size slider is disabled when switching from smart patch tool Product: krita Version: git master Platform: Windows CE OS: Windows CE Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: scottpetro...@gmail.com Target Milestone: --- steps to reproduce: 1. select the smart patch tool 2. select the freehand brush tool expected: The brush size slider to be active result: the brush size slider is disabled -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 374670] AAC transcoding is broken due to deprecated libfaac
https://bugs.kde.org/show_bug.cgi?id=374670 --- Comment #9 from rdragonr...@gmail.com --- I was the discoverer of the problem, but the other poster, DTL135, was the person to create the fix. He did not want to convert the patch format, however. I am guessing the format is with the diff command, but whatever it is, it is not git. Anyway, I am uncertain of the format and I can't submit it. I was told I could apply it with the patch command, however. I am guessing I can maybe git clone the repo, patch it, and then... what? What git command creates a patch from recent changes like this? (It's probably idiotically simple, but git confuses me) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom
https://bugs.kde.org/show_bug.cgi?id=371199 --- Comment #16 from Andreas Wanka--- I switched to cinnamon because of this bug. However, there, this bug seems to manifest itself by dropdowns (like menues) of kde apps not working in one screen (primary left for me), but working in the other. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379563] New: QML Type errors
https://bugs.kde.org/show_bug.cgi?id=379563 Bug ID: 379563 Summary: QML Type errors Product: plasmashell Version: master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: ska...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 getting a high number of these: file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null and then... networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "AllDevices" networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property "Devices" Notifications service registered file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base/CheckBoxStyle.qml:162:31: QML Item: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base/CheckBoxStyle.qml:162:31: QML Item: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base/CheckBoxStyle.qml:162:31: QML Item: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:353: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:352: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:351: TypeError: Cannot read property 'padding' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:350: TypeError: Cannot read property 'padding' of null networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "RxBytes" networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes" networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "RxBytes" networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "TxBytes" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom
https://bugs.kde.org/show_bug.cgi?id=371199 Andreas Wankachanged: What|Removed |Added CC||awa...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379555] Krita crashes when play button in animation is hit
https://bugs.kde.org/show_bug.cgi?id=379555 --- Comment #4 from Boudewijn Rempt--- Which repo? Please try to install debug symbols and generate a backtrace. I suspect there's a broken brush or setting somewhere on your system, but the first thing we need is a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379562] Calendar widget disappears when clicking away
https://bugs.kde.org/show_bug.cgi?id=379562 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Christoph Feck --- There is a pin in the top-right corner. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379562] New: Calendar widget disappears when clicking away
https://bugs.kde.org/show_bug.cgi?id=379562 Bug ID: 379562 Summary: Calendar widget disappears when clicking away Product: plasmashell Version: master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: ska...@gmail.com Target Milestone: 1.0 When clicking the clock widget calendar opens up. Good. When I click on anything else, the calendar disappears. Bad. It used to remain visible until I clicked the clock again to close it. I need a way to keep the calendar visible whilst doing other things, and only close it with an explicit action. (ESC button may be an additional implicit command to close it, but not clicking on other windows). -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 379561] New: KMix crashes
https://bugs.kde.org/show_bug.cgi?id=379561 Bug ID: 379561 Summary: KMix crashes Product: kmix Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: es...@kde.org Reporter: mar...@woletz.de Target Milestone: --- Application: kmix (4.6) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.62-18.6-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: Some times when I start working with Multimedia (e.g. playing a CD), KMix crashes. After restarting KMix works in most cases. The crash can be reproduced sometimes. -- Backtrace: Application: KMix (kmix), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe8aa73f940 (LWP 2470))] Thread 3 (Thread 0x7fe88f32f700 (LWP 2474)): #0 0x7fe8a9ffd49d in poll () from /lib64/libc.so.6 #1 0x7fe8a00ee3e2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fe8a00effcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fe895a94839 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fe8a59a29e9 in QThreadPrivate::start (arg=0x2445830) at thread/qthread_unix.cpp:341 #5 0x7fe8a1ebc744 in start_thread () from /lib64/libpthread.so.0 #6 0x7fe8aa005d3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe896773700 (LWP 2471)): #0 0x7fe8a9ffd49d in poll () from /lib64/libc.so.6 #1 0x7fe8a1318314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe8a131842c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe8a5bb532b in QEventDispatcherGlib::processEvents (this=0x7fe898e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fe8a5b62fdb in QEventLoop::exec (this=this@entry=0x7fe896772c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fe8a599df1a in QThread::exec (this=this@entry=0x7fe8a71f9ce0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #6 0x7fe8a6f911d5 in QDBusConnectionManager::run (this=0x7fe8a71f9ce0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189 #7 0x7fe8a59a29e9 in QThreadPrivate::start (arg=0x7fe8a71f9ce0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:341 #8 0x7fe8a1ebc744 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe8aa005d3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe8aa73f940 (LWP 2470)): [KCrash Handler] #6 0x7fe8a598c4b7 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x1b) at /usr/include/c++/4.8/bits/atomic_base.h:496 #7 QAtomicOps::load (_q_value=...) at ../../src/corelib/arch/qatomic_cxx11.h:96 #8 QBasicAtomicInteger::load (this=0x1b) at ../../src/corelib/thread/qbasicatomic.h:116 #9 QtPrivate::RefCount::deref (this=0x1b) at ../../src/corelib/tools/qrefcount.h:60 #10 QString::~QString (this=0x7fe89000e198, __in_chrg=) at ../../src/corelib/tools/qstring.h:1065 #11 QList::node_destruct (this=, to=0x7fe89000e198, from=0x7fe89000e278) at ../../src/corelib/tools/qlist.h:486 #12 QList::dealloc (this=, data=0x7fe89000e190) at ../../src/corelib/tools/qlist.h:855 #13 QList::~QList (this=, __in_chrg=) at ../../src/corelib/tools/qlist.h:817 #14 0x7fe8a5baa7e5 in QStringList::~QStringList (this=0x7fe898c0, __in_chrg=) at ../../src/corelib/tools/qstringlist.h:93 #15 v_clear (d=0x7fe898c0) at ../../src/corelib/kernel/qvariant_p.h:169 #16 QVariantDestructor<(anonymous namespace)::CoreTypesFilter>::FilteredDestructor::FilteredDestructor (d=0x7fe898c0, this=) at ../../src/corelib/kernel/qvariant_p.h:413 #17 QVariantDestructor<(anonymous namespace)::CoreTypesFilter>::delegate (this=) at ../../src/corelib/kernel/qvariant_p.h:439 #18 QMetaTypeSwitcher::switcher > (data=0x0, type=, logic=) at ../../src/corelib/kernel/qmetatypeswitcher_p.h:68 #19 (anonymous namespace)::clear (d=0x7fe898c0) at kernel/qvariant.cpp:123 #20 0x7fe8a6f957bc in QList::node_destruct (this=, to=0x7fe890019170, from=0x7fe890019170) at ../../src/corelib/tools/qlist.h:484 #21 QList::dealloc (data=0x7fe890019160, this=) at ../../src/corelib/tools/qlist.h:855 #22 0x7fe8a6fa942b in QDBusMessage::~QDBusMessage (this=, __in_chrg=) at qdbusmessage.cpp:564 #23 0x7fe8a6f9b6bc in QDBusActivateObjectEvent::~QDBusActivateObjectEvent (this=0x7fe89000f750, __in_chrg=) at qdbusintegrator.cpp:1572 #24 0x7fe8a6f9b729 in QDBusActivateObjectEvent::~QDBusActivateObjectEvent (this=0x7fe89000f750, __in_chrg=) at qdbusintegrator.cpp:1582 #25 0x7fe8a5b66db3 in QScopedPointerDeleter::cleanup (pointer=0x7fe89000f750) at
[kio-extras] [Bug 379550] XCF preview thumbnails in dolphin, new format not recognized
https://bugs.kde.org/show_bug.cgi?id=379550 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- If you can provide the information requested in bug 360821 comment #2, please add it there. *** This bug has been marked as a duplicate of bug 360821 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 360821] Show xcf files (from Gimp 2.9) not (yet...) working
https://bugs.kde.org/show_bug.cgi?id=360821 Christoph Feckchanged: What|Removed |Added CC||bugzi...@kerridis.de --- Comment #9 from Christoph Feck --- *** Bug 379550 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 222428] Wish for KDE recognize/compute DPI settings by different plugged screens
https://bugs.kde.org/show_bug.cgi?id=222428 Mike C. Fletcherchanged: What|Removed |Added CC||mcfle...@vrplumber.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 379550] XCF preview thumbnails in dolphin, new format not recognized
https://bugs.kde.org/show_bug.cgi?id=379550 Elvis Angelacciochanged: What|Removed |Added Component|view-engine: icons mode |default Assignee|dolphin-bugs-n...@kde.org |plasma-de...@kde.org Product|dolphin |kio-extras CC||elvis.angelac...@kde.org Version|unspecified |5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 377047] SFTP: All file is owned by root
https://bugs.kde.org/show_bug.cgi?id=377047 Danichanged: What|Removed |Added CC||contusio...@yahoo.es --- Comment #3 from Dani --- Can confirm that all files appear as owned by root in the connected KDE system: Terminal emulator in Phone: u0_a145@g3:/storage/external_SD/Android/data/net.osmand/files/tracks $ ls -l -rwxrwx--- u0_a155 sdcard_r 2130 2016-09-10 22:59 circuit de lesquillon.gpx drwxrwx--- u0_a155 sdcard_r 2017-05-05 16:14 rec -rwxrwx--- u0_a155 sdcard_r 743 2017-05-05 15:04 test.gpx u0_a145@g3:/storage/external_SD/Android/data/net.osmand/files/tracks $ Shell in connected KDE system: dani@setna:~/.config/kdeconnect/60ca260263df1100/kdeconnect_sftp/60ca260263df1100/storage/external_SD/Android/data/net.osmand/files/tracks $ ls -l total 8 -rw--- 1 root root 2130 sep 10 2016 circuit de lesquillon.gpx drwx-- 1 root root0 may 5 16:14 rec -rw--- 1 root root 743 may 5 15:04 test.gpx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379437] One column text selection jumps to front
https://bugs.kde.org/show_bug.cgi?id=379437 --- Comment #2 from Christoph Feck--- Ah wait, you are saying that Dolphin is correct, and Firefox is not? Then you should report it to Firefox developers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379437] One column text selection jumps to front
https://bugs.kde.org/show_bug.cgi?id=379437 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Christoph Feck --- While I do not agree that the jumping behaviour is correct, I suggest to report this to Qt developers, because the mouse handling in QLineEdit is inside the Qt libraries. https://bugreports.qt.io/ Btw, that's "one row", not "one column". -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 362817] Kontact crash on open addressbook from the email window
https://bugs.kde.org/show_bug.cgi?id=362817 Christian Trippechanged: What|Removed |Added CC||christiande...@web.de --- Comment #7 from Christian Trippe --- I hid the bug today several times in the same way as described comment 6 under kmail/kontact from the KDE Application 17.04.0 release. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 379459] Krusader no longer minimizes to system tray.
https://bugs.kde.org/show_bug.cgi?id=379459 --- Comment #6 from Alex Bikadorov--- I would go for "minimize" really only minimizes (and does not close to tray). This is the behaviour most other applications with a tray icon have. And yes, the icon will always be visible (if closed, minimized or open) (if the "close to tray" option is activated). -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 379170] 2.6.0 - Regression: "Spacebar calculates disk space" feature is missing
https://bugs.kde.org/show_bug.cgi?id=379170 Alex Bikadorovchanged: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kru ||sader/c447f1813f288fdf41ecb ||dbbc349086faa76dd25 --- Comment #6 from Alex Bikadorov --- Git commit c447f1813f288fdf41ecbdbbc349086faa76dd25 by Alexander Bikadorov. Committed on 05/05/2017 at 17:16. Pushed by abikadorov into branch 'master'. Panel: re-added quick disk space calculation with space key Was removed in version 2.6.0. New implementation. Uses old (fixed) shortcut. Calculation is async. UI is extended by new panel progress bar and cancel button. Space key for ".." dummy selection does a default, verbose calculation (with popup dialog) for all files and folders in panel (and selects all; this was the old behaviour). FIXED: [ 379170 ] 2.6.0 - Regression: "Spacebar calculates disk space" feature is missing This partially reverts commit 83d3b67274b24dd18fdcb4adf740a0e8452d5ce0. Changed layout.xml. M +5-1krusader/Konfigurator/kgpanel.cpp M +1-0krusader/Panel/krselectionmode.cpp M +8-1krusader/Panel/krselectionmode.h M +4-0krusader/Panel/krview.cpp M +2-0krusader/Panel/krview.h M +47 -18 krusader/Panel/listpanel.cpp M +7-3krusader/Panel/listpanel.h M +1-1krusader/Panel/listpanelactions.cpp M +32 -7krusader/Panel/panelfunc.cpp M +12 -7krusader/Panel/panelfunc.h M +2-0krusader/defaults.h M +9-3krusader/layout.xml https://commits.kde.org/krusader/c447f1813f288fdf41ecbdbbc349086faa76dd25 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive
https://bugs.kde.org/show_bug.cgi?id=379521 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages and attach a new backtrace. Without the debug symbols we do not see where it crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364692] Text tool "glitches" when in multiline mode
https://bugs.kde.org/show_bug.cgi?id=364692 Rosomakchanged: What|Removed |Added CC||kamin...@konto.pl --- Comment #6 from Rosomak --- Krita v3.1.3 Confirming that the text tool is still showing artifacts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371862] xclipboard_syncer goes crazy when kwin_wayland goes down
https://bugs.kde.org/show_bug.cgi?id=371862 Martin Gräßlinchanged: What|Removed |Added Latest Commit||https://commits.kde.org/kwi ||n/572f730e8ecd39767390d9a15 ||68a8cb50625965b Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Martin Gräßlin --- Git commit 572f730e8ecd39767390d9a1568a8cb50625965b by Martin Gräßlin. Committed on 05/05/2017 at 17:17. Pushed by graesslin into branch 'master'. [helper] Terminate xclipboardsyncer if kwin_wayland goes down Summary: Normally the xclipboardsyncer should terminate because the socket becomes unusable. But we have reports of it not really going down and running amok. In order to prevent such situations this change registers SIGTERM to be sent to xclipboardsyncer when the parent process (that is kwin_wayland) dies in whatever way. This ensures that xclipboardsyncer cannot become an orphan. Test Plan: Only compile tested, no way to get into the problematic situation Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D5589 M +1-0CMakeLists.txt M +1-0config-kwin.h.cmake M +9-0helpers/xclipboardsync/main.cpp https://commits.kde.org/kwin/572f730e8ecd39767390d9a1568a8cb50625965b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379278] panel gets added to wrong screen
https://bugs.kde.org/show_bug.cgi?id=379278 --- Comment #1 from Christoph Feck--- Neon packages are not using Plasma 5.7.5. Please correct the version or the distribution. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377901] Window movement breaks after 49 days
https://bugs.kde.org/show_bug.cgi?id=377901 Martin Gräßlinchanged: What|Removed |Added Version Fixed In||5.8.7 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/0bec9ad7337536e319c17c568 ||4d97e1156399fdb --- Comment #16 from Martin Gräßlin --- Git commit 0bec9ad7337536e319c17c5684d97e1156399fdb by Martin Gräßlin. Committed on 03/05/2017 at 19:36. Pushed by graesslin into branch 'Plasma/5.8'. Improve the x11 timestamp handling Summary: So far KWin only updated the x11 timestamp if the new timestamp is larger than the existing one. While this is a useful thing it creates problems when the 32 bit msec based time stamp wraps around which happens after running an X server for 49 days. After the timestamp wrapped around KWin would not update the timestamp any more and thus some calls might fail. Most prominent victims are keyboard and pointer grab which fails as the timestamp is either larger than the server timestamp or smaller than the last grab timestamp. Another problem related to timestamp handling is KWin getting broken by wrong timestamps sent by applications. A prominent example is clusterssh which used to send a timestamp as unix time which is larger than the x timestamp and thus our timestamp gets too large. This change addresses these problems by allowing to reset the timestamp. This is only used from updateXTime (which is normally invoked before we do things like grabKeyboard). Thus we make QX11Info::getTimestamp the ultimate trusted source for timestamps. Related: bug 348569 FIXED-IN: 5.8.7 Test Plan: As I cannot wait 50 days: unit tests for the two conditions added. Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D5704 M +11 -0autotests/CMakeLists.txt A +123 -0autotests/test_x11_timestamp_update.cpp [License: GPL (v2)] M +6-2main.h M +1-1utils.cpp M +3-3utils.h https://commits.kde.org/kwin/0bec9ad7337536e319c17c5684d97e1156399fdb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times
https://bugs.kde.org/show_bug.cgi?id=348569 Martin Gräßlinchanged: What|Removed |Added Version Fixed In||5.8.7 Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/0bec9ad7337536e319c17c568 ||4d97e1156399fdb --- Comment #38 from Martin Gräßlin --- Git commit 0bec9ad7337536e319c17c5684d97e1156399fdb by Martin Gräßlin. Committed on 03/05/2017 at 19:36. Pushed by graesslin into branch 'Plasma/5.8'. Improve the x11 timestamp handling Summary: So far KWin only updated the x11 timestamp if the new timestamp is larger than the existing one. While this is a useful thing it creates problems when the 32 bit msec based time stamp wraps around which happens after running an X server for 49 days. After the timestamp wrapped around KWin would not update the timestamp any more and thus some calls might fail. Most prominent victims are keyboard and pointer grab which fails as the timestamp is either larger than the server timestamp or smaller than the last grab timestamp. Another problem related to timestamp handling is KWin getting broken by wrong timestamps sent by applications. A prominent example is clusterssh which used to send a timestamp as unix time which is larger than the x timestamp and thus our timestamp gets too large. This change addresses these problems by allowing to reset the timestamp. This is only used from updateXTime (which is normally invoked before we do things like grabKeyboard). Thus we make QX11Info::getTimestamp the ultimate trusted source for timestamps. Related: bug 377901 FIXED-IN: 5.8.7 Test Plan: As I cannot wait 50 days: unit tests for the two conditions added. Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D5704 M +11 -0autotests/CMakeLists.txt A +123 -0autotests/test_x11_timestamp_update.cpp [License: GPL (v2)] M +6-2main.h M +1-1utils.cpp M +3-3utils.h https://commits.kde.org/kwin/0bec9ad7337536e319c17c5684d97e1156399fdb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379558] kwin_x11 PID: 2196 Signal: Segmentation fault (11) Time: 05/05/17 12:56:26
https://bugs.kde.org/show_bug.cgi?id=379558 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- as a workaround use the breeze window decoration. *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 Martin Gräßlinchanged: What|Removed |Added CC||felipesabra...@gmail.com --- Comment #119 from Martin Gräßlin --- *** Bug 379558 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379552] Alt Tabbing causes KWin to crash
https://bugs.kde.org/show_bug.cgi?id=379552 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages and attach a new backtrace. Without the debug symbols we do not see where it crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379549] kwin crash after klockscreen+monitor off
https://bugs.kde.org/show_bug.cgi?id=379549 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages and attach a new backtrace. Without the debug symbols we do not see where it crashes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379547] KWin creshed when I touch of left top screen corner with mouse (desktop grid action)
https://bugs.kde.org/show_bug.cgi?id=379547 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages and attach a new backtrace. Without the debug symbols we do not see where it crashes. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 375008] amd64->IR: unhandled instruction bytes: 0x8F 0x6A 0x78 0x10 0xD8 0x4 0x4 0x0 0x0 0x8F
https://bugs.kde.org/show_bug.cgi?id=375008 --- Comment #2 from dcb...@hotmail.com --- Not sure what you are asking for. I think the unhandled instruction is 0x8F 0x6A 0x78 0x10 0xD8 0x4 0x4 0x0 0x0 0x8F and so an arch reference manual (or wikipedia) will tell you which instruction those bytes are. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 Martin Gräßlinchanged: What|Removed |Added CC||heinrich.kieneke@t-online.d ||e --- Comment #69 from Martin Gräßlin --- *** Bug 379544 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379544] Win-Crash after starting the finance software "moneyplex"
https://bugs.kde.org/show_bug.cgi?id=379544 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 363224 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379528] KWin crash
https://bugs.kde.org/show_bug.cgi?id=379528 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Martin Gräßlin --- Crashes in the proprietary NVIDIA driver. Nothing we can do. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379560] New: Preferencia de Netspeed widget
https://bugs.kde.org/show_bug.cgi?id=379560 Bug ID: 379560 Summary: Preferencia de Netspeed widget Product: plasmashell Version: 5.9.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rocha.paulovic...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) (Compiled from sources) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.9-1 x86_64 Distribution: "KaOS" -- Information about the crash: Configuring the Netspeed widget preferences, when every system stopped fuincional at a time. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f11f456dcc0 (LWP 598))] Thread 13 (Thread 0x7f10ed356700 (LWP 459)): #0 0x7f11e87c8bd7 in () at /usr/lib/libglib-2.0.so.0 #1 0x7f11e87cb38a in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f11e87cb9a8 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f11e87cbb0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f11ef756ebb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f11ef704bba in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f11ef539d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f11f1b6c3a5 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f11ef53e6e9 in () at /usr/lib/libQt5Core.so.5 #9 0x7f11ee405494 in start_thread () at /lib/libpthread.so.0 #10 0x7f11eee5c6ff in clone () at /lib/libc.so.6 Thread 12 (Thread 0x7f10dd813700 (LWP 32664)): #0 0x7f11eee52ffd in poll () at /lib/libc.so.6 #1 0x7f11e87cba04 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f11e87cbb0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f11ef756ebb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f11ef704bba in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f11ef539d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f11ef53e6e9 in () at /usr/lib/libQt5Core.so.5 #7 0x7f11ee405494 in start_thread () at /lib/libpthread.so.0 #8 0x7f11eee5c6ff in clone () at /lib/libc.so.6 Thread 11 (Thread 0x7f10de014700 (LWP 32659)): #0 0x7f11e8810489 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f11e87caa00 in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #2 0x7f11e87cb8d5 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f11e87cbb0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f11ef756ebb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f11ef704bba in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f11ef539d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f11ef53e6e9 in () at /usr/lib/libQt5Core.so.5 #8 0x7f11ee405494 in start_thread () at /lib/libpthread.so.0 #9 0x7f11eee5c6ff in clone () at /lib/libc.so.6 Thread 10 (Thread 0x7f11198fc700 (LWP 2702)): #0 0x7f11eee52ffd in poll () at /lib/libc.so.6 #1 0x7f11e2d65f21 in () at /usr/lib/libpulse.so.0 #2 0x7f11e2d57ba1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7f11e2d581de in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f11e2d58290 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f11e2d65e86 in () at /usr/lib/libpulse.so.0 #6 0x7f11e26f76c8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7f11ee405494 in start_thread () at /lib/libpthread.so.0 #8 0x7f11eee5c6ff in clone () at /lib/libc.so.6 Thread 9 (Thread 0x7f111bac6700 (LWP 2629)): #0 0x7f11eee4ef7d in read () at /lib/libc.so.6 #1 0x7f11e880f1c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f11e87cb50e in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f11e87cb9a8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f11e87cbb0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f11ef756ebb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f11ef704bba in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f11ef539d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f11f1b6c3a5 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f11ef53e6e9 in () at /usr/lib/libQt5Core.so.5 #10 0x7f11ee405494 in start_thread () at /lib/libpthread.so.0 #11 0x7f11eee5c6ff in clone () at /lib/libc.so.6 Thread 8 (Thread 0x7f11363b5700 (LWP 1440)): #0 0x7f11ef50ed90 in __tls_get_addr@plt () at /usr/lib/libQt5Core.so.5 #1 0x7f11ef53d6d6 in () at
[plasmashell] [Bug 379233] Can't pin an icon of TeamViewer on Icons-only Task Manager
https://bugs.kde.org/show_bug.cgi?id=379233 Christoph Feckchanged: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379559] New: [notifier] Also list updates in the notifier applet
https://bugs.kde.org/show_bug.cgi?id=379559 Bug ID: 379559 Summary: [notifier] Also list updates in the notifier applet Product: Discover Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: elvis.angelac...@kde.org Target Milestone: --- Right now the notifier applet shows only how many packages need to be updated. It would be handy if the applet had also a listview with the names of those packages. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378585] Old icons appear when toggling compositing on/off
https://bugs.kde.org/show_bug.cgi?id=378585 --- Comment #4 from Christoph Feck--- If you can provide the information requested in comment #3, please add it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359664] xembedsniproxy random crashes (w/core dumps)
https://bugs.kde.org/show_bug.cgi?id=359664 Christoph Feckchanged: What|Removed |Added Severity|normal |crash Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #4 from Christoph Feck --- Thanks for the feedback; changing status. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 378560] Reports show digits and not the fields when sub-tables are used
https://bugs.kde.org/show_bug.cgi?id=378560 Jarosław Staniekchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Jarosław Staniek --- Confirmed. 'Visible' field of the related table isn't used. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377066] Some Valgrind unit tests fail to compile on Ubuntu 16.10 with PIE enabled by default
https://bugs.kde.org/show_bug.cgi?id=377066 Ivo Raisrchanged: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376257] helgrind history full speed up using a cached stack
https://bugs.kde.org/show_bug.cgi?id=376257 Ivo Raisrchanged: What|Removed |Added CC||iv...@ivosh.net Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Ivo Raisr --- Hello Philippe, how are you doing with this patch? Have you been able to polish it more? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 375415] free list of blocks, mempool blocks and describe addr do not work properly together
https://bugs.kde.org/show_bug.cgi?id=375415 Ivo Raisrchanged: What|Removed |Added CC||iv...@ivosh.net --- Comment #3 from Ivo Raisr --- Ruurd, can you please comment? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 375008] amd64->IR: unhandled instruction bytes: 0x8F 0x6A 0x78 0x10 0xD8 0x4 0x4 0x0 0x0 0x8F
https://bugs.kde.org/show_bug.cgi?id=375008 Ivo Raisrchanged: What|Removed |Added CC||iv...@ivosh.net --- Comment #1 from Ivo Raisr --- Thank you for the report. We need the unhandled instruction - can you obtain it for example by gdb or objdump? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379558] New: kwin_x11 PID: 2196 Signal: Segmentation fault (11) Time: 05/05/17 12:56:26
https://bugs.kde.org/show_bug.cgi?id=379558 Bug ID: 379558 Summary: kwin_x11 PID: 2196 Signal: Segmentation fault (11) Time: 05/05/17 12:56:26 Product: kwin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: multiscreen, usability Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: felipesabra...@gmail.com Target Milestone: --- Flags: X11+ Created attachment 105361 --> https://bugs.kde.org/attachment.cgi?id=105361=edit Hardware Information Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f044ade5940 (LWP 2196))] Thread 6 (Thread 0x7f041b7ff700 (LWP 2594)): #0 0x7f044a546b03 in select () from /lib64/libc.so.6 #1 0x7f0447c16849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib64/libQt5Core.so.5 #2 0x7f0447c180c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib64/libQt5Core.so.5 #3 0x7f0447c18527 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f0447bc7fdb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f0447a02f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f04425ed9c8 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f0447a079e9 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f044a80f744 in start_thread () from /lib64/libpthread.so.0 #9 0x7f044a54dd3d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f0418928700 (LWP 2296)): #0 0x7f044a8140bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0446b9693b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f0446b96969 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f044a80f744 in start_thread () from /lib64/libpthread.so.0 #4 0x7f044a54dd3d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f0428f3e700 (LWP 2291)): #0 0x7f044a546b03 in select () from /lib64/libc.so.6 #1 0x7f0447c16849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib64/libQt5Core.so.5 #2 0x7f0447c180c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib64/libQt5Core.so.5 #3 0x7f0447c18527 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f0447bc7fdb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f0447a02f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f04425ed9c8 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f0447a079e9 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f044a80f744 in start_thread () from /lib64/libpthread.so.0 #9 0x7f044a54dd3d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f042b452700 (LWP 2250)): #0 0x7f044a546b03 in select () from /lib64/libc.so.6 #1 0x7f0447c16849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib64/libQt5Core.so.5 #2 0x7f0447c180c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib64/libQt5Core.so.5 #3 0x7f0447c18527 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f0447bc7fdb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f0447a02f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f04417ce1d5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f0447a079e9 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f044a80f744 in start_thread () from /lib64/libpthread.so.0 #9 0x7f044a54dd3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f043150c700 (LWP 2227)): #0 0x7f044a54549d in poll () from /lib64/libc.so.6 #1 0x7f04496c93e2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f04496cafcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f04321bc839 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f0447a079e9 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f044a80f744 in start_thread () from /lib64/libpthread.so.0 #6 0x7f044a54dd3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f044ade5940 (LWP 2196)): [KCrash Handler] #6 0x7f04425d9de0 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags) () from /usr/lib64/libQt5Qml.so.5 #7 0x7f04425db25a in QQmlBinding::update(QFlags) () from /usr/lib64/libQt5Qml.so.5 #8 0x7f04425e4306 in ?? () from /usr/lib64/libQt5Qml.so.5 #9 0x7f044257294b in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () from /usr/lib64/libQt5Qml.so.5 #10 0x7f0442572a07 in QQmlComponentPrivate::completeCreate() () from /usr/lib64/libQt5Qml.so.5 #11