[digikam] [Bug 382002] Lazy synchronization not working
https://bugs.kde.org/show_bug.cgi?id=382002 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Metadata|Metadata-Hub -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382001] Wishlist: Copy metadata from one file to another
https://bugs.kde.org/show_bug.cgi?id=382001 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 155384 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 155384] Easily copy properties from one image to another one
https://bugs.kde.org/show_bug.cgi?id=155384 caulier.gil...@gmail.com changed: What|Removed |Added CC||aegor...@gmail.com --- Comment #12 from caulier.gil...@gmail.com --- *** Bug 382001 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 381664] Plugin leads to the home page of Flickr and 'An error has occurred: Invalid Frob It can not be continued.'
https://bugs.kde.org/show_bug.cgi?id=381664 --- Comment #2 from jon33...@yahoo.co.uk --- I can't reproduce this right now due to other issues but I did see it over the weekend before my flickr installation got broken. The thread from the flickr APIs group discussion referenced in the first comment suggests flickr have turned off the deprecated mechanism with no notice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 Koen changed: What|Removed |Added CC||kdejae...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 --- Comment #34 from Koen --- Is there any workaround for this at the moment? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 382004] New: [Wayland] System Settings crashed after closing it
https://bugs.kde.org/show_bug.cgi?id=382004 Bug ID: 382004 Summary: [Wayland] System Settings crashed after closing it Product: systemsettings Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jodr...@live.com Target Milestone: --- Application: systemsettings5 (5.10.90) Qt Version: 5.9.0 Frameworks Version: 5.36.0 Operating System: Linux 4.11.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Change the cursor theme for KDE and GTK apps under "Application style" then close it. The crash window pop right after. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faeffe7c400 (LWP 32196))] Thread 10 (Thread 0x7faea700 (LWP 32207)): #0 0x7faefba8f08d in poll () from /lib64/libc.so.6 #1 0x7faef5938d09 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7faef5938e1c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7faefc3b375b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7faefc35cd0a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7faefc18f05a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7faefa23ed45 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #7 0x7faefc19373e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7faef787a4e7 in start_thread () from /lib64/libpthread.so.0 #9 0x7faefba98a2f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7faecdc72700 (LWP 32205)): #0 0x7faef597db54 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7faef5938c2e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7faef5938e1c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7faefc3b375b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7faefc35cd0a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7faefc18f05a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7faefa23ed45 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #7 0x7faefc19373e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7faef787a4e7 in start_thread () from /lib64/libpthread.so.0 #9 0x7faefba98a2f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7faed4217700 (LWP 32204)): #0 0x7faef78805ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7faedecd92fb in cnd_wait (mtx=0x5610af445620, cond=0x5610af445648) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5610af2583e0) at u_queue.c:158 #3 0x7faedecd9037 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7faef787a4e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7faefba98a2f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7faed4a18700 (LWP 32203)): #0 0x7faef78805ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7faedecd92fb in cnd_wait (mtx=0x5610af445620, cond=0x5610af445648) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5610af32d250) at u_queue.c:158 #3 0x7faedecd9037 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7faef787a4e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7faefba98a2f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7faed5219700 (LWP 32202)): #0 0x7faef78805ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7faedecd92fb in cnd_wait (mtx=0x5610af445620, cond=0x5610af445648) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5610af269de0) at u_queue.c:158 #3 0x7faedecd9037 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7faef787a4e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7faefba98a2f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7faed5a1a700 (LWP 32201)): #0 0x7faef78805ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7faedecd92fb in cnd_wait (mtx=0x5610af445620, cond=0x5610af445648) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5610af2583e0) at u_queue.c:158 #3 0x7faedecd9037 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7faef787a4e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7faefba98a2f in clone () from /lib64/libc.so.6 Thre
[plasmashell] [Bug 381964] Invalid drivers error handling
https://bugs.kde.org/show_bug.cgi?id=381964 --- Comment #2 from legolord...@krake.one --- (In reply to David Edmundson from comment #1) > There's not a great deal we can do; nvidia replaces the openGL lib that gets > loaded, if that can't load the kernel module, it's that which crashes. > > We can't use openGL when the setup is broken at all. > Also you said the login manager crashed, which is before plasmashell. > > There was some work by me to use Qt's 2D renderer, but you need to know that > openGL won't work before you load a broken module. Right, okay. Kinda confused to how Linux Mint Cinnamon does it, but then again that might just be because it uses another graphics card or something. Thanks for everything! Cheers! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382005] New: Palette docker has dark scrollbars and background in Krita bright theme [minor]
https://bugs.kde.org/show_bug.cgi?id=382005 Bug ID: 382005 Summary: Palette docker has dark scrollbars and background in Krita bright theme [minor] Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: raghavendr.ra...@gmail.com Target Milestone: --- This is a minor UI papercut, the palette docker background stays dark in Krita bright theme and the scrollbars that appear are dark too To reproduce 1) Open Krita and Open a new document 2) Switch to Krita bright theme Expected Results: The palette docker should have light theme background and scrollbar like the rest of the docker for consistency thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382005] Palette docker has dark scrollbars and background in Krita bright theme [minor]
https://bugs.kde.org/show_bug.cgi?id=382005 --- Comment #1 from Raghavendra kamath --- Created attachment 106443 --> https://bugs.kde.org/attachment.cgi?id=106443&action=edit A screenshot showing palette docker under bright theme Adding a screen-shot of the palette docker in the bright theme -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381997] Kate doesn't receive a lenghty text paste from Firefox
https://bugs.kde.org/show_bug.cgi?id=381997 Kåre Särs changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- Thanks for the report. I can confirm that there is a real problem there! If you wait long enough the text will appear in Kate, but for me it took over a minute to get pasted. While it was being pasted Kate was using 100% of one core. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377878] Pinned folder icon less sharp when panel is wide
https://bugs.kde.org/show_bug.cgi?id=377878 Alex changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Alex --- Seems to be ok after Neon 5.10.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 --- Comment #35 from Koen --- At the moment I just do 'killall plasmashell' to be able to work without the sound of a space shuttle taking of next to me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration
https://bugs.kde.org/show_bug.cgi?id=179678 --- Comment #18 from 林博仁 --- Polkit is triggered when I accidentally tried to save a root-owned file in Kate in neon 5.10 user edition, is this feature implemented? -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 380864] Persist "find in files" history across KDevelop restarts
https://bugs.kde.org/show_bug.cgi?id=380864 Kevin Funk changed: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||vplatform/42eb6bb62c28923e5 ||f6f4ff0cee3e8e6ee07bd2e Version Fixed In||5.2.0 URL||https://phabricator.kde.org ||/D6262 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 381754] Drop-down list is not saved
https://bugs.kde.org/show_bug.cgi?id=381754 Kevin Funk changed: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||vplatform/42eb6bb62c28923e5 ||f6f4ff0cee3e8e6ee07bd2e Version Fixed In||5.2.0 URL||https://phabricator.kde.org ||/D6262 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 381754] Drop-down list is not saved
https://bugs.kde.org/show_bug.cgi?id=381754 Kevin Funk changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 380864] Persist "find in files" history across KDevelop restarts
https://bugs.kde.org/show_bug.cgi?id=380864 Kevin Funk changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371489] Breeze style elements are looking too big
https://bugs.kde.org/show_bug.cgi?id=371489 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment #5 from RJVB --- +++ The elements are not just looking too big, they are. I've been mentioning this since the first time I tried the new Oxygen theme for KDE4. I've never worked on a very high res screen (1080p is more than enough for me) but I kind of expect that the size of the style elements will be proportional to the font size you're using. IOW, the screen estate waste will be comparable on a 4k screen when fonts are configured to have a comparable apparent size as on a normal resolution screen. Remember you can buy a new hires screen which a certain company calls a Retina screen, but you cannot replace those 2 actual screens we biologists call retinas. And their effective resolving power doesn't increase over time... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382006] New: kwin crash after closing window
https://bugs.kde.org/show_bug.cgi?id=382006 Bug ID: 382006 Summary: kwin crash after closing window Product: kwin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: s...@advert.com.pl Target Milestone: --- Application: kwin_x11 (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-26-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: It happens sometimes, quite often (once or twice a day), with different applications. After closing window, kwin crashes and restarts. Some applications cannot handle this situation and for example leaves uncloseable small window (I suppose it was hidden before crash). The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd105171900 (LWP 1410))] Thread 5 (Thread 0x7fd0dd302700 (LWP 1499)): #0 0x7fd104b89e51 in __GI_ppoll (fds=0x7fd0d4000b38, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fd102450251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd102451b4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd1023fe88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd10222bfe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd0fcff6df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fd102230c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd0fe2896da in start_thread (arg=0x7fd0dd302700) at pthread_create.c:456 #8 0x7fd104b95d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7fd0cd83f700 (LWP 1455)): #0 0x7fd0fe28f510 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fd1015ba2c4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fd1015ba309 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fd0fe2896da in start_thread (arg=0x7fd0cd83f700) at pthread_create.c:456 #4 0x7fd104b95d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fd0de303700 (LWP 1445)): #0 0x7fd104b89e51 in __GI_ppoll (fds=0x7fd0dac8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fd102450251 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd102451b4a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd1023fe88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd10222bfe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd0fcff6df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fd102230c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd0fe2896da in start_thread (arg=0x7fd0de303700) at pthread_create.c:456 #8 0x7fd104b95d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fd0ed9ce700 (LWP 1420)): #0 0x7fd104b89d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd0f985c576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd0f985c68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd102454f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd1023fe88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd10222bfe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd0fc1cf5c5 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fd102230c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd0fe2896da in start_thread (arg=0x7fd0ed9ce700) at pthread_create.c:456 #9 0x7fd104b95d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fd105171900 (LWP 1410)): [KCrash Handler] #6 0x in () #7 0x7fd1024326e0 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd1015fb037 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #9 0x7fd1015fb0ff in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #10 0x7fd1015fb382 in QScriptEngine::newQObject(QObject*, QScriptEngine::ValueOwnership, QFlags const&) () at /
[valgrind] [Bug 381805] arm32 needs ld.so index hardwire for new glibc security fixes
https://bugs.kde.org/show_bug.cgi?id=381805 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Mark Wielaard --- valgrind svn r16458. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362522] Cursor becomes "hand grab cursor" stuck after using "Set horizontal mirror mode"
https://bugs.kde.org/show_bug.cgi?id=362522 Laurence changed: What|Removed |Added CC||laure...@notbyhalf.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362522] Cursor becomes "hand grab cursor" stuck after using "Set horizontal mirror mode"
https://bugs.kde.org/show_bug.cgi?id=362522 --- Comment #5 from Laurence --- Has this been fixed for OS X? Found this thread while logging this bug. Using Version 3.1.3 The hand cursor gets stuck after moving the mirror line. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 233970] Printwizard do not retaining settings
https://bugs.kde.org/show_bug.cgi?id=233970 caulier.gil...@gmail.com changed: What|Removed |Added Summary|tool : printwizard Not|Printwizard do not |retaining settings |retaining settings -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 233970] Printwizard do not retaining settings
https://bugs.kde.org/show_bug.cgi?id=233970 caulier.gil...@gmail.com changed: What|Removed |Added Status|REOPENED|RESOLVED Latest Commit||https://commits.kde.org/dig ||ikam/000fd1a154389d8e954a23 ||a122fe3fb4b389f432 Version Fixed In||5.7.0 Resolution|--- |FIXED --- Comment #9 from caulier.gil...@gmail.com --- Git commit 000fd1a154389d8e954a23a122fe3fb4b389f432 by Gilles Caulier. Committed on 05/07/2017 at 10:12. Pushed by cgilles into branch 'master'. Remove Same to All option. This will be the default mode now, as customization of caption for each image do not work. Same the settings when caption page is validated. FIXED-IN: 5.7.0 M +1-19 utilities/assistants/printcreator/ui/advprintcaptionpage.ui M +21 -9utilities/assistants/printcreator/wizard/advprintcaptionpage.cpp M +1-0utilities/assistants/printcreator/wizard/advprintcaptionpage.h M +9-61 utilities/assistants/printcreator/wizard/advprintwizard.cpp M +0-1utilities/assistants/printcreator/wizard/advprintwizard.h https://commits.kde.org/digikam/000fd1a154389d8e954a23a122fe3fb4b389f432 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382007] New: sent mail reply on invitation shows ics in plain text
https://bugs.kde.org/show_bug.cgi?id=382007 Bug ID: 382007 Summary: sent mail reply on invitation shows ics in plain text Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kol...@aon.at Target Milestone: --- When I accept an invitation I got, kmail correctly sends an email back. Looking into the sent mail folder and clicking on this sent email shows the ics in plain, e.g. starting with: BEGIN:VCALENDAR PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN VERSION:2.0 X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0 METHOD:REPLY ... END:VCALENDAR This invitation has been updated by an attendee. Your status for this invitation is Accepted. The Accepted response has been recorded and just below this kmail shows the nicely rendered HTML version. (this is independent of the "view attachments ..." setting) 1) the plain text version is not needed 2) the "bold" tags should not be shown on the "button" but it should be really shown in bold text -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382002] Lazy synchronization not working
https://bugs.kde.org/show_bug.cgi?id=382002 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Problem with Lazy Synchronization is not reproducible. Lazy Synchronization writes only to the files if the sync button pressed on the status bar. Or when you close at end digiKam. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 382008] New: preferred languages missing C and en
https://bugs.kde.org/show_bug.cgi?id=382008 Bug ID: 382008 Summary: preferred languages missing C and en Product: systemsettings Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_language Assignee: jl...@kde.org Reporter: alpeter...@gmail.com Target Milestone: --- I am trying to figure out how to have Chinese language input... and I ended up changing the system language... but I did include American English as the most preferred language... but then apt is in Chinese.. .and some gnu image scanner is in Chinese... it is ambiguous what order the languages are selected in... does top win, or bottom win? Also, there is no obvious way to enable Chinese input within System Settings... and this regional panel is more confusing than helpful. It should probably say something about UI Language preferences. C and en should be included in the laguages.. those are the default if nothing is specified I believe? en_US and en_GB are ok... but I'll take any en before Chinese... Yes, I do want to switch quickly between zh and en... so I can learn zh.. but that's not likely to happen any time soon. It would be nice to consider it in updates. So, this bug is basically saying that the Regional Settings is confusing, and too easy to bork the system. Please update documenation/description of what it does, and include en and C so I don't get screwed when a program supports en but not en_US -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 382009] New: Yakuake search shortcut
https://bugs.kde.org/show_bug.cgi?id=382009 Bug ID: 382009 Summary: Yakuake search shortcut Product: yakuake Version: 3.0.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: digikam-b...@reg.valik.sk Target Milestone: --- Hello. Yakuake has a search function but it is only accessible using menu (or I did not find a way to do it differently). I believe that it would help a lot if an user could specify keyboard shortcut for this feature and would not be forced to move hands from keyboard to mouse... Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 382010] New: Kile: width of tabs is inconsistent
https://bugs.kde.org/show_bug.cgi?id=382010 Bug ID: 382010 Summary: Kile: width of tabs is inconsistent Product: kile Version: 2.9.60 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: nortex...@gmail.com Target Milestone: --- The tab width is inconsistent when compared with dolphin and kate. I know that kate uses some hackish tab interface, and Kile must be doing something of its own, but is it possible to set the tab width to the width of the filename to make it consistent with what dolphin does? Or else give the same apparently fixed width that Kate uses. It looks strange that one tab fills up basically the whole window length. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382007] sent mail reply on invitation shows ics in plain text
https://bugs.kde.org/show_bug.cgi?id=382007 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- "1) the plain text version is not needed" I confirm that it's not necessary. But when mailer doesn't have renderer ical support we need to provide a text. But for sure not the plain text version. I will investigate it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382011] New: SyncTeX 2017 upgrade
https://bugs.kde.org/show_bug.cgi?id=382011 Bug ID: 382011 Summary: SyncTeX 2017 upgrade Product: okular Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: laurens.trib...@gmail.com Target Milestone: --- Please find at https://github.com/jlaurens/synctex/tree/2017 the pre release version of the synctex parser. It would be great if you could test it ASAP and hopefully give me your agreement to release that code. Read the synctex_parser_readme.md for very minor upgrading instructions. Thanks Jérôme -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382007] sent mail reply on invitation shows ics in plain text
https://bugs.kde.org/show_bug.cgi?id=382007 --- Comment #2 from Laurent Montel --- Git commit 30313e40ea098575e921a4b06ec007e9525136ca by Montel Laurent. Committed on 05/07/2017 at 11:20. Pushed by mlaurent into branch 'master'. Fix problem in Bug 382007 - sent mail reply on invitation shows ics in plain text We want to render as bold M +1-1src/templates/itip.html https://commits.kde.org/kcalutils/30313e40ea098575e921a4b06ec007e9525136ca -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382007] sent mail reply on invitation shows ics in plain text
https://bugs.kde.org/show_bug.cgi?id=382007 --- Comment #3 from Laurent Montel --- Git commit 1287715939f49093061753fda38f166e2c4603b5 by Montel Laurent. Committed on 05/07/2017 at 11:36. Pushed by mlaurent into branch 'Applications/17.04'. Fix problem in Bug 382007 - sent mail reply on invitation shows ics in plain text We want to render as bold (cherry picked from commit 30313e40ea098575e921a4b06ec007e9525136ca) M +1-1src/templates/itip.html https://commits.kde.org/kcalutils/1287715939f49093061753fda38f166e2c4603b5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382007] sent mail reply on invitation shows ics in plain text
https://bugs.kde.org/show_bug.cgi?id=382007 Laurent Montel changed: What|Removed |Added Version Fixed In||5.6.0 Latest Commit||https://commits.kde.org/kde ||pim-addons/226827c5d6eee50b ||7af11ea28889d7c7050299e7 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Laurent Montel --- Git commit 226827c5d6eee50b7af11ea28889d7c7050299e7 by Montel Laurent. Committed on 05/07/2017 at 11:35. Pushed by mlaurent into branch 'master'. Fix Bug 382007 - sent mail reply on invitation shows ics in plain text FIXED-IN: 5.6.0 M +4-2 plugins/messageviewer/bodypartformatter/calendar/text_calendar.cpp https://commits.kde.org/kdepim-addons/226827c5d6eee50b7af11ea28889d7c7050299e7 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376393] Regression kMail 5.4.1/2: Invitations are not displayed as such any more
https://bugs.kde.org/show_bug.cgi?id=376393 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel --- Do you have kdepim-addons installed ? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Christos Gourdoupis changed: What|Removed |Added CC||xri...@otenet.gr --- Comment #142 from Christos Gourdoupis --- Recently openSUSE TW upgraded to Qt 5.9, and now en_DK is available as a time format. But guess what, it gives "05/07/2017 14.52". Why? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382012] New: Plasma crashes when stopping VPN
https://bugs.kde.org/show_bug.cgi?id=382012 Bug ID: 382012 Summary: Plasma crashes when stopping VPN Product: plasmashell Version: 5.10.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: a.r.wel...@gmx.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.1) Qt Version: 5.7.1 Frameworks Version: 5.35.0 Operating System: Linux 4.11.8-300.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: Plasma always crashes when I stop a acitve VPN connection through the KDE NetworkManager Applet. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0cd0fd04c0 (LWP 4408))] Thread 9 (Thread 0x7f0bfdd1e700 (LWP 2581)): #0 0x7f0cdcf31aad in poll () from /lib64/libc.so.6 #1 0x7f0cd5c80569 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f0cd5c8067c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f0cddd4cd0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f0cddcfcb8a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f0cddb51efa in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f0ce0dd79b5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f0cddb561ee in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f0cdc27936d in start_thread () from /lib64/libpthread.so.0 #9 0x7f0cdcf3db9f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f0c13cb7700 (LWP 5320)): #0 0x7f0cdcf31aad in poll () from /lib64/libc.so.6 #1 0x7f0cd5c80569 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f0cd5c8067c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f0cddd4cd0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f0cddcfcb8a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f0cddb51efa in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f0c1661d497 in KCupsConnection::run() () from /lib64/libkcupslib.so #7 0x7f0cddb561ee in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f0cdc27936d in start_thread () from /lib64/libpthread.so.0 #9 0x7f0cdcf3db9f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f0c2637a700 (LWP 5070)): #0 0x7f0cd5c80668 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #1 0x7f0cddd4cd0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #2 0x7f0cddcfcb8a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f0cddb51efa in QThread::exec() () from /lib64/libQt5Core.so.5 #4 0x7f0ce175eff6 in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #5 0x7f0cddb561ee in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #6 0x7f0cdc27936d in start_thread () from /lib64/libpthread.so.0 #7 0x7f0cdcf3db9f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f0cb3fff700 (LWP 4544)): #0 0x7f0cdc27f81b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0ce3831534 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f0ce3831579 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f0cdc27936d in start_thread () from /lib64/libpthread.so.0 #4 0x7f0cdcf3db9f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f0cbe130700 (LWP 4510)): #0 0x7f0cdcf2d1ad in read () from /lib64/libc.so.6 #1 0x7f0cd5cc4170 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f0cd5c80078 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f0cd5c80510 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f0cd5c8067c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f0cddd4cd0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f0cddcfcb8a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f0cddb51efa in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f0ce0dd79b5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #9 0x7f0cddb561ee in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f0cdc27936d in start_thread () from /lib64/libpthread.so.0 #11 0x7f0cdcf3db9f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f0cbf9d3700 (LWP 4474)): #0 0x7f0cd5c7d4b2 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7f0cd5c7f9fb in
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 Mads changed: What|Removed |Added CC||m...@ab3.no --- Comment #23 from Mads --- (In reply to Brian Mastenbrook from comment #21) > I'm not sure I understand the question. For clarity, here's my setup: I'm > using a laptop with an internal 4K display and an external 4K monitor, both > of which have a scaling factor of 2. The external display is set as primary. > When I run dolphin, the default window with my home directory appears on the > external display. I can't select any items in the file view or sidebar, > though the address bar and toolbar remain responsive. If I drag the window > so that it is entirely on the internal display, I can select and open files > and directories as usual. However, when I drag the window back to the > external display, I can no longer select or open items again. Do you still have this issue? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 319465] Kmail crashed on reply
https://bugs.kde.org/show_bug.cgi?id=319465 --- Comment #13 from abulak --- (In reply to Denis Kurz from comment #12) > This bug has never been confirmed for a Kontact version that is based on KDE > Frameworks, except possibly a Technology Preview version 5.0.x. Those > versions differ significantly from the old 4.x series. Therefore, I plan to > close it in around two or three months. In the meantime, it is set to > WAITINGFORINFO to give reporters the opportunity to check if it is still > valid. As soon as someone confirms it for a recent version (at least 5.1, > ideally even more recent), I'll gladly reopen it. > > Please understand that we lack the manpower to triage bugs reported for > versions almost two years beyond their end of life. Feel free to close it now -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 332267] Edit of payment method in schedule not usually retained
https://bugs.kde.org/show_bug.cgi?id=332267 Ralf Habacker changed: What|Removed |Added Version Fixed In||4.7.0 CC||ralf.habac...@freenet.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382013] New: Crash during or after adding a new remote collection
https://bugs.kde.org/show_bug.cgi?id=382013 Bug ID: 382013 Summary: Crash during or after adding a new remote collection Product: digikam Version: 5.5.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- Application: digikam (5.5.0) (Compiled from sources) Qt Version: 5.8.0 Frameworks Version: 5.35.0 Operating System: Linux 4.9.30-ck1-mainline-core2-rjvb x86_64 Distribution: Ubuntu 14.04.5 LTS -- Information about the crash: - What I was doing when the application crashed: I changed my DB backend from SQLite to MySQL (MariaDB) and thus had to add all my collections anew. This crash happened at some point after adding the last remote collection (I came back to the machine to find DrKonqi instead of DigiKam). Probably a bug in dbus or even libc (reported: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1702477), reporting here for reference (and just in case digiKam actually did do something naughty). -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff88dbe1880 (LWP 28796))] Thread 15 (Thread 0x7ff869a6b700 (LWP 28799)): #0 0x7ff888ff7c5d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7ff87b312b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff87b31464f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff86c0d0549 in QXcbEventReader::run (this=0x857c10) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1345 #4 0x7ff8898c0cf9 in QThreadPrivate::start (arg=0x857c10) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/thread/qthread_unix.cpp:368 #5 0x7ff885d94184 in start_thread (arg=0x7ff869a6b700) at pthread_create.c:312 #6 0x7ff889004ffd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 14 (Thread 0x7ff860380700 (LWP 28800)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7ff888f8c0da in _L_lock_13302 () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7ff888f89ad5 in __GI___libc_malloc (bytes=128) at malloc.c:2889 #3 0x7ff8898c1e1c in QArrayData::allocate (objectSize=objectSize@entry=2, alignment=alignment@entry=8, capacity=capacity@entry=52, options=...) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/tools/qarraydata.cpp:106 #4 0x7ff88993c66f in allocate (options=..., capacity=52) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/include/QtCore/../../src/corelib/tools/qarraydata.h:222 #5 QString::reallocData (this=this@entry=0x7ff86037f930, alloc=52, grow=grow@entry=true) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/tools/qstring.cpp:1781 #6 0x7ff88993c7b8 in QString::resize (this=this@entry=0x7ff86037f930, size=size@entry=32) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/tools/qstring.cpp:1692 #7 0x7ff889942bb2 in append_utf8 (len=32, cs=0x7ff889be5a50 "QSocketNotifier: Invalid socket %d and type '%s', disabling...", qs=...) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/tools/qstring.cpp:5974 #8 QString::vasprintf (cformat=cformat@entry=0x7ff889be5a50 "QSocketNotifier: Invalid socket %d and type '%s', disabling...", ap=ap@entry=0x7ff86037fa58) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/tools/qstring.cpp:6067 #9 0x7ff8898a659e in qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtWarningMsg, context=..., msg=msg@entry=0x7ff889be5a50 "QSocketNotifier: Invalid socket %d and type '%s', disabling...", ap=ap@entry=0x7ff86037fa58) at /opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/corelib/global/qlogging.cpp:279 #10 0x7ff8898a7329 in QMessageLogger::warning (this=this@entry=0x7ff86037fb30, msg=msg@entry=0x7ff889be5a50 "QSocketNotifi
[digikam] [Bug 382013] Crash during or after adding a new remote collection
https://bugs.kde.org/show_bug.cgi?id=382013 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- It crash in DBUS, not digiKam. If you cross compile for MacOS under Linux, in all case, DBus must be disable at DK compilation time. DBus do not work outside Linux Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 328964] Konversation crashed when Ctrl+W was pressed
https://bugs.kde.org/show_bug.cgi?id=328964 Syam changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Syam --- This is an old report. I can no longer reproduce with the current version. So closing. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 337882] Search misbehaves when searching for titles containing single quotes
https://bugs.kde.org/show_bug.cgi?id=337882 Syam changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Syam --- Seems to work fine with Akregator 5.4.3, KDE Frameworks 5.34.0, Qt 5.7.1, Fedora 25. Searching for single-quote and words with single-quote (what's, customer's etc.) seem to work fine. Searching for double-quotes has some incomprehensible behaviour though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380008] System randomly freezes or crashes to the login screen, glitches until rebooted
https://bugs.kde.org/show_bug.cgi?id=380008 --- Comment #9 from Mircea Kitsune --- Created attachment 106444 --> https://bugs.kde.org/attachment.cgi?id=106444&action=edit Screenshot of "top" Lots of important new information on this freeze, which was of course ported to the latest openSUSE Tumbleweed system packages and still works: First and foremost, the problem does not happen in every session, and this is not always influenced by updates! During an interval in which I installed absolutely no relevant package changes, the following has happened: The freeze occurred after about just 8 hours of uptime... after that I restarted the machine, but then I had 4 days of uptime with no freeze! This leads me to believe that certain applications or system actions prepare the system with a "time bomb", which then causes switching between windows or desktops to produce the freeze... however I have no way to know what mines the system and what doesn't yet, as I use too many applications at once to figure out which might be responsible. Anyway another crash happened today. Once more I quickly hit Control + Alt + F1 to switch to a different runlevel; This caused the image to become corrupted on the monitor, however the system remained responsive and didn't actually freeze. So I went to my mother's computer and logged in via SSH, which indeed still worked. I was able to issue a reboot command, which caused the image to briefly unfreeze as the monitor turned on and off a few more times... I could see a few KDE error messages about applications crashing, before the system actually went ahead and rebooted successfully! However this is only possible if I switch to a console quickly enough when noticing the freeze start to happen, if not the whole machine freezes and not even SSH responds from other devices! While I was in SSH, I decided to run "top" and take a screenshot of my processes (while the computer was frozen and with corrupt image stuck on the screen). I can't tell if anything is out of the ordinary such as a memory leak, but I'm attaching a screenshot of it here. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 365276] Selecting/deleting an article does not work if 'search article' box has focus
https://bugs.kde.org/show_bug.cgi?id=365276 Syam changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Syam --- Seems to work fine with Akregator 5.4.3, KDE Frameworks 5.34.0, Qt 5.7.1, Fedora 25. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382013] Crash during or after adding a new remote collection
https://bugs.kde.org/show_bug.cgi?id=382013
--- Comment #2 from RJVB ---
Yes, I reported this mostly for reference. It actually crashes in libc as far
as I can tell. I don't think it's a bug in digiKam but the a crash like this
could also be due to improper usage in Qt.
FWIW, dbus works just fine outside of Linux ("out-of-the-box", as long as you
don't need privileged services).
--
You are receiving this mail because:
You are watching all bug changes.
[akregator] [Bug 373688] Akregator crashes at startup if more than one instance of Qt Creator is running
https://bugs.kde.org/show_bug.cgi?id=373688 Syam changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Syam --- Seems to work OK now. Fedora 25, x86_64 Akregator 5.4.3 KDE Frameworks 5.34.0 Qt 5.7.1 (built against 5.7.1) Qt Creator 4.1.0 Based on Qt 5.7.1 (GCC 6.3.1 20161221 (Red Hat 6.3.1-1), 64 bit) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 Robby Engelmann changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #18 from Robby Engelmann --- I can confirm that for openSUSE Tumbleweed and latest Qt, Frameworks, Plasma, Apps... "Title bar button Menubar style, as soon as I switched from Title bar button to In application Akregator stopped crashing" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382013] Crash during or after adding a new remote collection
https://bugs.kde.org/show_bug.cgi?id=382013 --- Comment #3 from caulier.gil...@gmail.com --- No. under OSX, this never work properly. Under Windows, it just the hell. This is why for non Linux, DBUS must be disabled with digiKam. This is what i do for Windows + OSX bundle. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 381416] Crash on kontact launch
https://bugs.kde.org/show_bug.cgi?id=381416 Robby Engelmann changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 381416] Crash on kontact launch
https://bugs.kde.org/show_bug.cgi?id=381416 --- Comment #2 from Robby Engelmann --- Created attachment 106445 --> https://bugs.kde.org/attachment.cgi?id=106445&action=edit New crash information added by DrKonqi kontact (5.5.2) using Qt 5.9.0 - What I was doing when the application crashed: The same here. Qt 5.9, Frameworks 5.34, Apps 17.04.2 and also trouble with akregator feeds -- Backtrace (Reduced): #6 0x7fd04134b7b4 in Akregator::MainWidget::setFeedList (this=0x0, list=...) at /usr/src/debug/akregator-17.04.2/src/mainwidget.cpp:459 #7 0x7fd04133c4e6 in Akregator::Part::feedListLoaded (this=0x5592871362c0, list=...) at /usr/src/debug/akregator-17.04.2/src/akregator_part.cpp:507 [...] #9 0x7fd041316d69 in Akregator::LoadFeedListCommand::result (_t1=..., this=) at /usr/src/debug/akregator-17.04.2/build/src/akregatorpart_autogen/include/moc_loadfeedlistcommand.cpp:140 #10 Akregator::LoadFeedListCommand::Private::emitResult (this=this@entry=0x55928734e870, list=...) at /usr/src/debug/akregator-17.04.2/src/command/loadfeedlistcommand.cpp:64 #11 0x7fd04131720d in Akregator::LoadFeedListCommand::Private::handleDocument (this=this@entry=0x55928734e870, doc=...) at /usr/src/debug/akregator-17.04.2/src/command/loadfeedlistcommand.cpp:88 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 382014] New: No opening balance edit for investment accounts
https://bugs.kde.org/show_bug.cgi?id=382014 Bug ID: 382014 Summary: No opening balance edit for investment accounts Product: kmymoney4 Version: 4.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- On creating investment accounts it is possible to enter an opening balance but it could not be edited afterwards because the opening balance field is not displayed in the account editing dialog. How to reproduce: 1. Create an investment account and set a non zero opening balance 2. Edit the account and try to set the opening balance to zero What happens: There is no input field displaying the opening balance account What should happen: The opening balance account field should be displayed in the account editor to be able to set it to zero. Further informations: Any other account type except categories has the possibility to edit the opening balance. A workaround is to delete the opening balance transaction for this account in the ledger view. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381352] Can't assign or change to indian keyboard layout, system tray icon is also missing.
https://bugs.kde.org/show_bug.cgi?id=381352
--- Comment #10 from Raghavendra kamath ---
With the help of fellow kde user Tuxtoriel on #kde IRC channel I have a
workable input switcher.
Tuxtoriel found that the following section in the /usr/share/X11/xkb/symbols/in
file was the problem.
xkb_symbols "tel-sarala" { name[Group1] = "Telugu (Sarala)";
key.type="FOUR_LEVEL"; // sequence base, shift, alt, alt + shift key { [
U0C4A, U0C12 ] }; // ొ ఒ key { [ U0C42, U0C0A ] }; // ూ ఊ key { [
U0C21, U0C22 ] }; // డ ఢ key { [ U0C35, U0C39 ] }; // వ హ key { [
U0C2C, U0C2D ] }; // బ భ key { [ U0C28, U0C23 ] }; // న ణ key { [
U0C2E, U0C01 ] }; // మ ఁ key { [ U002C, U0C1E, leftcaret ] }; // , ఞ <
key { [ U002E, U0C19, rightcaret ] }; // . ఙ > key { [ U0C36,
question, KP_Divide ] }; // శ ? / key { [ U0C2F, U0C3D ] }; // య ఽ key
{ [ U0C02, U0C03 ] }; // ం ః key { [ U0C26, U0C27 ] }; // ద ధ key
{ [ U0C4D, U0C05 ] }; // ్ అ key { [ U0C17, U0C18 ] }; // గ ఘ key
{ [ U0C1A, U0C1B, U0C58, U0C59 ] }; // చ ఛ ౘ ౙ key { [ U0C3E,
U0C06 ] }; // ా ఆ key { [ U0C15, U0C16, U0C62, U0C63 ] }; // క ఖ ౢ ౣ key
{ [ U0C32, U0C33, U0C0C, U0C61 ] }; // ల ళ ఌ ౡ key { [ U0C1F,
U0C20, semicolon, colon ] }; // ట ఠ ; : key { [ quoteright, quotedbl ]
}; // ' " key { [ U0C46, U0C0E, U0C44 U0C34 ] }; // ె ఎ ౄ ఴ key {
[
U0C38, U0C37, U0C44 ] }; // స ష ౄ key { [ U0C47, U0C0F, U0C44 ] }; // ే
ఏ ౄ
key { [ U0C30, U0C31, U0C44, U0C60 ] }; // ర ఱ ౄ ౠ key { [ U0C24,
U0C25 ] }; // త థ key { [ U0C40, U0C08 ] }; // ీ ఈ key { [ U0C41,
U0C09 ] }; // ు ఉ key { [ U0C3F, U0C07 ] }; // ి ఇ key { [ U0C4B,
U0C13 ] }; // ో ఓ key { [ U0C2A, U0C2B ] }; // ప ఫ key { [ U0C1C,
U0C1D, bracketleft, braceleft ] }; // జ ఝ [ { key { [ U0C48, U0C10,
bracketright, braceright ] }; // ై ఐ ] } key { [ KP_1, exclam, U0C67,
U0C78 ] }; // 1 ! ౦ ౸ key { [ KP_2, at, U0C68, U0C79 ] }; // 2 @ ౨ ౹ key
{ [ KP_3, numbersign, U0C69, U0C7A ] }; // 3 # ౩ ౺ key { [ KP_4,
dollar, U0C6A, U0C7B ] }; // 4 $ ౪ ౻ key { [ KP_5, percent, U0C6B, U0C7C
] }; // 5 % ౫ ౼ key { [ KP_6, asciicircum, U0C6C, U0C7D ] }; // 6 ^ ౬ ౽
key { [ KP_7, ampersand, U0C6D, U0C7E ] }; // 7 & ౭ ౾ key { [
KP_8, KP_Multiply, U0C6E, U0C7F ] }; // 8 * ౮ ౿ key { [ KP_9, U0028,
U0C6F, U20B9 ] }; // 9 ( ౯ ₹ key { [ KP_0, U0029, U0C66, U0C55 ] }; // 0
) ౦ ౕ key { [ KP_Subtract, underbar, NoSymbol, U0C56 ] }; // - _ ౖ key
{ [ KP_Equal, KP_Add ] }; // = + key { [ U0C4C, U0C14, U0964,
U0965 ] }; // ౌ ఔ । ॥ key { [ U0C43, U0C0B, quoteleft, asciitilde ] }; //
ఋ ` ~ include "level3(ralt_switch)" };
I removed this section and everything is working fine now :) So this is a
workaround for now.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 381902] Plasma crashes leaving only a blank screen
https://bugs.kde.org/show_bug.cgi?id=381902 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Marco Martin --- *** This bug has been marked as a duplicate of bug 375860 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375860] Crash in QTXML Patterns parsing
https://bugs.kde.org/show_bug.cgi?id=375860 Marco Martin changed: What|Removed |Added CC||tbp...@gmx.de --- Comment #27 from Marco Martin --- *** Bug 381902 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381953] plasma wayland crash on opening application launcher
https://bugs.kde.org/show_bug.cgi?id=381953 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Component|general |generic-wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381974] Start menu crashed
https://bugs.kde.org/show_bug.cgi?id=381974 Marco Martin changed: What|Removed |Added CC||zbygniu...@gmail.com --- Comment #1 from Marco Martin --- *** Bug 381006 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381006] Crash after switching activities (QSortFilterProxyModelPrivate::updateChildrenMapping)
https://bugs.kde.org/show_bug.cgi?id=381006 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Marco Martin --- *** This bug has been marked as a duplicate of bug 381974 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382003] i checked kde and saw this unhappy icon, also get kworker error when poweroff
https://bugs.kde.org/show_bug.cgi?id=382003 Marco Martin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||notm...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 381525 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381525] Crash in QQmlBinding::getPropertyData
https://bugs.kde.org/show_bug.cgi?id=381525 Marco Martin changed: What|Removed |Added CC||azzmm...@gmail.com --- Comment #21 from Marco Martin --- *** Bug 382003 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 382012] Plasma crashes when stopping VPN
https://bugs.kde.org/show_bug.cgi?id=382012 Marco Martin changed: What|Removed |Added Target Milestone|1.0 |--- Component|general |applet Product|plasmashell |plasma-nm Assignee|k...@davidedmundson.co.uk|jgrul...@redhat.com CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 382015] New: discovering devices failed: QNativeSocketEngine::bind() was not called in ...
https://bugs.kde.org/show_bug.cgi?id=382015 Bug ID: 382015 Summary: discovering devices failed: QNativeSocketEngine::bind() was not called in ... Product: kdeconnect Version: 1.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: l...@aosc.xyz Target Milestone: --- KDE Connect Version: 1.0.2 This always happens since I upgrade Qt-5 from 5.8.0 to 5.9.0. >> QNativeSocketEngine::bind() was not called in >> QAbstractSocket::UnconnectedState << Log: ``` 21:53:48 kdeconnectd[1270]: kdeconnect.core: Broadcasting identity packet 21:53:48 kdeconnectd[1270]: QNativeSocketEngine::bind() was not called in QAbstractSocket::UnconnectedState 21:53:52 kdeconnectd[1270]: kdeconnect.core: Sending onNetworkChange to 1 LinkProviders 21:53:52 kdeconnectd[1270]: kdeconnect.core: Broadcasting identity packet 21:53:52 kdeconnectd[1270]: QNativeSocketEngine::bind() was not called in QAbstractSocket::UnconnectedState 21:53:55 kdeconnectd[1270]: kdeconnect.core: Sending onNetworkChange to 1 LinkProviders 21:53:55 kdeconnectd[1270]: kdeconnect.core: Broadcasting identity packet 21:53:55 kdeconnectd[1270]: QNativeSocketEngine::bind() was not called in QAbstractSocket::UnconnectedState ``` Network: ``` 95 131.063031253 192.168.1.103 → 192.168.1.109 UDP 861 39351 → 1716 Len=819 96 131.063408694 192.168.1.103 → 192.168.1.109 UDP 861 39351 → 1714 Len=819 97 131.063466932 192.168.1.109 → 192.168.1.103 ICMP 590 Destination unreachable (Port unreachable) ``` Connection: ``` lion@Lion-Laptop [ ~ ] $ ss --listen --udp --tcp --numeric | grep 171 udpUNCONN 0 0 *:1716 *:* tcpLISTEN 0 50 :::1716 :::* ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382016] New: crash on changing wallpaper positioning
https://bugs.kde.org/show_bug.cgi?id=382016 Bug ID: 382016 Summary: crash on changing wallpaper positioning Product: plasmashell Version: 5.10.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: varikonni...@hush.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 106446 --> https://bugs.kde.org/attachment.cgi?id=106446&action=edit journalctl relevant output When i change the positioning mode it sometimes crashes the plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382013] Crash during or after adding a new remote collection
https://bugs.kde.org/show_bug.cgi?id=382013 --- Comment #4 from RJVB --- Not that it's the issue at hand (the backtrace comes from Linux) but I don't do anything to disable dbus in my `port:kf5-digikam` and I have yet to run into issues. Mind you, I have never tried to use any dbus features as far as I can remember (but then again I didn't do that now either). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381953] plasma wayland crash on opening application launcher
https://bugs.kde.org/show_bug.cgi?id=381953 --- Comment #3 from Marco Martin --- this theme doesn't seem to have shadows for the dialogs/background.svg element, and that's probably the reason, investigating -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381352] Can't assign or change to indian keyboard layout, system tray icon is also missing.
https://bugs.kde.org/show_bug.cgi?id=381352 Raghavendra kamath changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #11 from Raghavendra kamath --- Ok found the problem it was because of a missing coma in the symbol file in that sarala section. which is fixed upstreams in xkeyboard config with this commit -> https://cgit.freedesktop.org/xkeyboard-config/commit/?id=b3fb72308942f705e3e8e17765e4097773ed5483 So closing this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 354513] drop comment field from "new User ID" dialog and from OpenPGP Certificate Creation Wizard
https://bugs.kde.org/show_bug.cgi?id=354513 Andre Heinecke changed: What|Removed |Added Latest Commit||https://commits.kde.org/kle ||opatra/7c143754d14f29fe1553 ||f82f38df46a46aa97d73 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Andre Heinecke --- Git commit 7c143754d14f29fe1553f82f38df46a46aa97d73 by Andre Heinecke, on behalf of Justus Winter. Committed on 05/07/2017 at 14:50. Pushed by aheinecke into branch 'master'. Remove comment field from OpenPGP key generation The comment part of OpenPGP user ids is nowadays seen as a misfeature. There is no consensus about what kind of information to put there, and worse, users may not be aware that this information is published as part of the certificate. Some more rationale for this can be found under: https://debian-administration.org/users/dkg/weblog/97 Differential: D6416 Signed-off-by: Justus Winter Commit message slightly amended by Andre Heinecke M +0-17 src/newcertificatewizard/enterdetailspage.ui M +3-27 src/newcertificatewizard/newcertificatewizard.cpp https://commits.kde.org/kleopatra/7c143754d14f29fe1553f82f38df46a46aa97d73 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 382017] New: A dialog asks me password again, after I entered password and clicked on "Connect" in applet
https://bugs.kde.org/show_bug.cgi?id=382017
Bug ID: 382017
Summary: A dialog asks me password again, after I entered
password and clicked on "Connect" in applet
Product: plasma-nm
Version: 5.10.0
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: applet
Assignee: jgrul...@redhat.com
Reporter: l...@aosc.xyz
Target Milestone: ---
Version:
plasma-nm/os-amd64,now 5.10.0
networkmanager-qt/os-amd64,now 5.34.0
networkmanager/os-amd64,now 1.8.0-3
Here is the log (119 lines):
```
>> Here, I entered password for this WiFi ("TP501"), clicked connect button on
>> applet.
17:30:07 NetworkManager[916]: [1499247007.2037] keyfile: add connection
in-memory (85494039-6684-4671-bdcb-ab0f9281260c,"TP501")
17:30:07 NetworkManager[916]: [1499247007.2052] device (wlp0s20u2):
Activation: starting connection 'TP501' (85494039-6684-4671-bdcb-ab0f9281260c)
17:30:07 NetworkManager[916]: [1499247007.2183] keyfile: update
/etc/NetworkManager/system-connections/TP501
(85494039-6684-4671-bdcb-ab0f9281260c,"TP501") and persist connection
17:30:07 NetworkManager[916]: [1499247007.2193] keyfile: update
/etc/NetworkManager/system-connections/TP501
(85494039-6684-4671-bdcb-ab0f9281260c,"TP501") after persisting connection
17:30:07 NetworkManager[916]: [1499247007.2195] audit:
op="connection-add-activate" uuid="85494039-6684-4671-bdcb-ab0f9281260c"
name="TP501" pid=1257 uid=1000 result="success"
17:30:07 NetworkManager[916]: [1499247007.2265] device (wlp0s20u2):
state change: disconnected -> prepare (reason 'none') [30 40 0]
17:30:07 NetworkManager[916]: [1499247007.2267] manager: NetworkManager
state is now CONNECTING
17:30:07 NetworkManager[916]: [1499247007.2276] device (wlp0s20u2):
state change: prepare -> config (reason 'none') [40 50 0]
17:30:07 NetworkManager[916]: [1499247007.2278] device (wlp0s20u2):
Activation: (wifi) access point 'TP501' has security, but secrets are required.
17:30:07 NetworkManager[916]: [1499247007.2279] device (wlp0s20u2):
state change: config -> need-auth (reason 'none') [50 60 0]
17:30:07 kdeinit5[1217]: plasma-nm: Unhandled active connection state change:
1
17:30:07 kdeinit5[1217]: plasma-nm: virtual void SecretAgent::SaveSecrets(const
NMVariantMapMap&, const QDBusObjectPath&)
17:30:07 kdeinit5[1217]: plasma-nm: Path:
"/org/freedesktop/NetworkManager/Settings/6"
17:30:07 kdeinit5[1217]: plasma-nm: virtual NMVariantMapMap
SecretAgent::GetSecrets(const NMVariantMapMap&, const QDBusObjectPath&, const
QString&, const QStringList&, uint)
17:30:07 kdeinit5[1217]: plasma-nm: Path:
"/org/freedesktop/NetworkManager/Settings/6"
17:30:07 kdeinit5[1217]: plasma-nm: Setting name: "802-11-wireless-security"
17:30:07 kdeinit5[1217]: plasma-nm: Hints: ()
17:30:07 kdeinit5[1217]: plasma-nm: Flags: 5
17:30:07 plasmashell[1257]:
file:///usr/lib/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read
property of null
(Repeated 35 times)
17:30:07 plasmashell[1257]:
file:///usr/lib/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read
property of null
17:30:07 plasmashell[1257]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:44:32:
Unable to assign [undefined] to int
>> Here *the dialog* showed, immediately, everthing happened at 17:30:07.
>> 14 seconds, I entered the password again, on dialog. Go on.
17:30:21 NetworkManager[916]: [1499247021.8609] device (wlp0s20u2):
state change: need-auth -> prepare (reason 'none') [60 40 0]
17:30:21 NetworkManager[916]: [1499247021.8617] device (wlp0s20u2):
state change: prepare -> config (reason 'none') [40 50 0]
17:30:21 NetworkManager[916]: [1499247021.8619] device (wlp0s20u2):
Activation: (wifi) connection 'TP501' has security, and secrets exist. No new
secrets needed.
17:30:21 NetworkManager[916]: [1499247021.8620] Config: added 'ssid'
value 'TP501'
17:30:21 NetworkManager[916]: [1499247021.8620] Config: added
'scan_ssid' value '1'
17:30:21 NetworkManager[916]: [1499247021.8620] Config: added
'key_mgmt' value 'WPA-PSK'
17:30:21 NetworkManager[916]: [1499247021.8620] Config: added
'auth_alg' value 'OPEN'
17:30:21 NetworkManager[916]: [1499247021.8620] Config: added 'psk'
value ''
17:30:21 plasmashell[1257]:
file:///usr/lib/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read
property of null
17:30:21 plasmashell[1257]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:44:32:
Unable to assign [undefined] to int
17:30:21 plasmashell[1257]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:74:
TypeError: Cannot read property 'title' of null
17:30:21 plasmashell[1257]:
file:///usr/lib/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read
property of null
(Repeated 10 times)
17:30:22 plasmashell[1
[kwin] [Bug 376801] kwin disables compositing with mesa 17
https://bugs.kde.org/show_bug.cgi?id=376801 --- Comment #17 from Martin Flöser --- @Paul: how come that you use OpenGL ES? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382006] kwin crash after closing window
https://bugs.kde.org/show_bug.cgi?id=382006 Martin Flöser changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 363224 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 302945] Backup can't be performed on Windows
https://bugs.kde.org/show_bug.cgi?id=302945 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Ralf Habacker --- Thanks for this fix which has the disadvantage to have a dependency to a 3rdparty tool. I'm going to fix this by using the windows build in copy command. -- 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 Flöser changed: What|Removed |Added CC||s...@advert.com.pl --- Comment #82 from Martin Flöser --- *** Bug 382006 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 325472] Import log file uses Invalid file path
https://bugs.kde.org/show_bug.cgi?id=325472 --- Comment #18 from Ralf Habacker --- Git commit 071693e961e7666b4f2f94d8f6f3724b18d29ff1 by Ralf Habacker. Committed on 05/07/2017 at 14:16. Pushed by habacker into branch '4.8'. Use introduced log file path also on removing log files. M +2-3kmymoney/kmymoney.cpp https://commits.kde.org/kmymoney/071693e961e7666b4f2f94d8f6f3724b18d29ff1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 302945] Backup can't be performed on Windows
https://bugs.kde.org/show_bug.cgi?id=302945 Ralf Habacker changed: What|Removed |Added Status|REOPENED|RESOLVED Version Fixed In||4.8.1 Latest Commit||https://commits.kde.org/kmy ||money/d5674713e0c6ce002f54a ||5e894f22f77b5109b64 Resolution|--- |FIXED --- Comment #4 from Ralf Habacker --- Git commit d5674713e0c6ce002f54a5e894f22f77b5109b64 by Ralf Habacker. Committed on 05/07/2017 at 14:51. Pushed by habacker into branch '4.8'. Fix 'Backup can't be performed on Windows' Avoid the need of a 3rdparty tool to support file backup on windows by using build in copy command. FIXED-IN:4.8.1 M +7-3kmymoney/kmymoney.cpp https://commits.kde.org/kmymoney/d5674713e0c6ce002f54a5e894f22f77b5109b64 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 382014] No opening balance edit for investment accounts
https://bugs.kde.org/show_bug.cgi?id=382014 Ralf Habacker changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/cb25aca805b461f211fe0 ||85570e110696bc7d1df Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||4.8.1 --- Comment #1 from Ralf Habacker --- Git commit cb25aca805b461f211fe085570e110696bc7d1df by Ralf Habacker. Committed on 05/07/2017 at 14:03. Pushed by habacker into branch '4.8'. Fix 'No opening balance edit for investment accounts' Enable editing of opening balance value for investment accounts. FIXED-IN:4.8.1 M +1-1kmymoney/kmymoney.cpp https://commits.kde.org/kmymoney/cb25aca805b461f211fe085570e110696bc7d1df -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376801] kwin disables compositing with mesa 17
https://bugs.kde.org/show_bug.cgi?id=376801 --- Comment #18 from Paul de Vrieze --- @martin I am not sure about that configuration, but I believe that it was due to attempts to use wayland as well. I will try to have a look tomorrow, but it is one of those gentoo choice things. I hadn't realised that kwin was using es. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382018] New: Plasmashell crashed
https://bugs.kde.org/show_bug.cgi?id=382018 Bug ID: 382018 Summary: Plasmashell crashed Product: plasmashell Version: 5.10.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mukenio_argent...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.3) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.10.0-21-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - Custom settings of the application: Apps open at the moment of crash: Chrome IntelliJ (suspect this is causing the crash) Chromium Radiotray The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f99ff3f28c0 (LWP 9559))] Thread 21 (Thread 0x7f9905cf2700 (LWP 11315)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f99fa3433a6 in QWaitConditionPrivate::wait_relative (time=3, this=0x49559f0) at thread/qwaitcondition_unix.cpp:133 #2 QWaitConditionPrivate::wait (time=3, this=0x49559f0) at thread/qwaitcondition_unix.cpp:141 #3 QWaitCondition::wait (this=this@entry=0x3fbbad0, mutex=mutex@entry=0x4effb20, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f99fa33ebea in QThreadPoolThread::run (this=0x3fbbac0) at thread/qthreadpool.cpp:133 #5 0x7f99fa342509 in QThreadPrivate::start (arg=0x3fbbac0) at thread/qthread_unix.cpp:368 #6 0x7f99f91e86ba in start_thread (arg=0x7f9905cf2700) at pthread_create.c:333 #7 0x7f99f9c503dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 20 (Thread 0x7f9906ffc700 (LWP 10334)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f99fa34346b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3e2e270) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x3a88cf0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f994822807f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f994822c078 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f994822726d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f994822c0d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f994822726d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f9948229bf0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f99fa342509 in QThreadPrivate::start (arg=0x7f98f0003580) at thread/qthread_unix.cpp:368 #10 0x7f99f91e86ba in start_thread (arg=0x7f9906ffc700) at pthread_create.c:333 #11 0x7f99f9c503dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7f99077fd700 (LWP 10333)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f99fa34346b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x3e2e270) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x3a88cf0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f994822807f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f994822c078 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f994822726d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f994822c0d2 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f994822726d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f9948229bf0 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f99fa342509 in QThreadPrivate::start (arg=0x7f98fc002b90) at thread/qthread_unix.cpp:368 #10 0x7f99f91e86ba in start_thread (arg=0x7f99077fd700) at pthread_create.c:333 #11 0x7f99f9c503dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f9907ffe700 (LWP 10332)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:1
[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 Martin Flöser changed: What|Removed |Added Flags||Wayland-, X11+ --- Comment #23 from Martin Flöser --- Daniel, thanks for your investigation. Based on that I did quite some additional investigation. I noticed that it is not trivial to fix. Everything I tried so far did not solve the problem properly and I think a larger refactoring of the code is needed. The "root" problem is that struts are constructed from the edge of the overall screen layout. So the strut of a panel in between restricts on all screens. This code was so problematic that the Wayland implementation never got implemented and only has a TODO. Which explains why I couldn't reproduce this issue on Wayland. But on the other hand we also need to make it work on Wayland. Given that a larger refactoring is required. Luckily it's well contained and given the investigation so far it is possible. But due to the fact that I think it will require a larger refactoring I doubt that this can be provided as a bug fix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381048] MEMORY LEAK
https://bugs.kde.org/show_bug.cgi?id=381048 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com --- Comment #2 from Vadym Krevs --- I've just updated to latest Qt 5.9.1, Frameworks 5.35, etc from the following repos on openSUSE 42.2 http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_42.2/ http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.2/ http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42.2/ http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_42.2 and now plasmashell leaks 5-7 mb every 10 seconds (according to the Memory column in System Activity). An hour ago I killed an 18Gb plasmashell process, and within minutes of restarting plasmashell's memory usage is over 800Mb. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381048] MEMORY LEAK
https://bugs.kde.org/show_bug.cgi?id=381048 --- Comment #3 from Vadym Krevs --- $ rpm -qf `which plasmashell` plasma5-workspace-5.10.3-331.3.x86_64 vadymk@stal-dev-lx1 ~ $ rpm -qa | grep -i framework plasma-framework-components-debuginfo-5.35.0-178.3.x86_64 plasma-framework-5.35.0-178.3.x86_64 plasma-framework-lang-5.35.0-178.3.noarch plasma-framework-private-debuginfo-5.35.0-178.3.x86_64 plasma-framework-private-5.35.0-178.3.x86_64 plasma-framework-components-5.35.0-178.3.x86_64 frameworkintegration-plugin-5.35.0-139.4.x86_64 plasma-framework-debuginfo-5.35.0-178.3.x86_64 $ rpm -qa | grep libQt5Core5 libQt5Core5-5.9.1-5.1.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 382019] New: Reboot, Shutdown buttons doesn't appear again when changing in System Settings
https://bugs.kde.org/show_bug.cgi?id=382019 Bug ID: 382019 Summary: Reboot, Shutdown buttons doesn't appear again when changing in System Settings Product: kdeplasma-addons Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Dashboard Assignee: h...@kde.org Reporter: idmresettr...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Before the bug: - There are 3 buttons: Logout, Reboot, Shutdown in the Application Dashboard widget. Steps to reproduce the bug: 1. Go to System Settings > Startup and Shutdown > Desktop sessions 2. Uncheck the option "Offer shutdown options" -> Result: the Application Dashboard now has only one button "Logout" 3. Redo step 1+2, but in step 2 check the option "Offer shutdown options" -> Result: the Application Dashboard now still has only one button "Logout" -> bug. (temporary fix: Change Application Dashboard to Application Menu and change it again) Expected behavior: - After the step #3 above, the Application Dashboard has 3 buttons: Logout, Reboot, Shutdown. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381953] plasma wayland crash on opening application launcher
https://bugs.kde.org/show_bug.cgi?id=381953 --- Comment #4 from Marco Martin --- possible fix in https://phabricator.kde.org/D6518 -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 38416] kmozilla some remarks and ideas
https://bugs.kde.org/show_bug.cgi?id=38416 Allen Winter changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||win...@kde.org --- Comment #3 from Allen Winter --- oops. wrong bug number -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 38416] kmozilla some remarks and ideas
https://bugs.kde.org/show_bug.cgi?id=38416 Allen Winter changed: What|Removed |Added Latest Commit||https://commits.kde.org/akr ||egator/470801bd845ce6544018 ||c7da9258d1e66ab662fa Resolution|WONTFIX |FIXED --- Comment #2 from Allen Winter --- Git commit 470801bd845ce6544018c7da9258d1e66ab662fa by Allen Winter. Committed on 05/07/2017 at 15:49. Pushed by winterz into branch 'Applications/17.04'. akregator_part.cpp - add a crash guard in case the mainWidget isn't set yet M +11 -1src/akregator_part.cpp https://commits.kde.org/akregator/470801bd845ce6544018c7da9258d1e66ab662fa -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 381416] Crash on kontact launch
https://bugs.kde.org/show_bug.cgi?id=381416 Allen Winter changed: What|Removed |Added CC||win...@kde.org Status|UNCONFIRMED |RESOLVED Version Fixed In||17.08 Resolution|--- |FIXED --- Comment #3 from Allen Winter --- fixed in commit 470801bd845ce6544018c7da9258d1e66ab662fa -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382002] Lazy synchronization not working
https://bugs.kde.org/show_bug.cgi?id=382002 --- Comment #2 from Andrius --- (In reply to Maik Qualmann from comment #1) > Problem with Lazy Synchronization is not reproducible. Lazy Synchronization > writes only to the files if the sync button pressed on the status bar. Or > when you close at end digiKam. > > Maik Hello Maik, Thanks for looking at this issue. For your convenience I have recorded a video. Here is the link: https://youtu.be/hMD4-fomSVc Hopefully it helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372384] Memory leak in plasmashell
https://bugs.kde.org/show_bug.cgi?id=372384 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379375] Memory leak
https://bugs.kde.org/show_bug.cgi?id=379375 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 371765] Documents suddenly open as archives
https://bugs.kde.org/show_bug.cgi?id=371765 Paul changed: What|Removed |Added CC|pip@gmx.com | -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #19 from Allen Winter --- can someone give me instructions on how to set the "Title bar button Menubar style"? so I can try to also get this crash and then try to fix. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382020] New: Feature request to add Opendesktop.org App
https://bugs.kde.org/show_bug.cgi?id=382020 Bug ID: 382020 Summary: Feature request to add Opendesktop.org App Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: dequ...@mykolab.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 106447 --> https://bugs.kde.org/attachment.cgi?id=106447&action=edit Screenshot of Opendesktop.org Electron App As the title states, this is a request for KDE Neon to ship an enabled Opendesktop.org App and change the default settings to point to store.kde.org. Doing so would easily enlighten KDE Plasma users towards an easy and user-friendly way to install things like * Wallpapers * Icon packs * Look and Feel Themes * Plasma Widgets * etc, etc. About the app: "Using the App allows you to directly “Install” items by clicking on the “Install” button of a file, as well as Manage the downloaded items under “My Collection”. Starting with wallpapers, it is also now possibly to directly “Apply” a downloaded item within the App, so it is then set as current background under most Linux distros and desktop environments." I believe this is an Electron app, basically wrapping the Opendesktop.org sites into a launchable application which gives it many advantages over assuming a user is aware of store.kde.org to begin with, as there is no reference to it in Neon. This leaves only KGHNS as the featured way, which of course has the tragic limitation of not allowing a user to install files if they are hosted on a 3rd party site. I am aware that this is not a native Plasma application, and can be easily dismissed for not including in Neon based on this fact alone. However, exceptions are made for usability-purposes (i.e. Firefox), and to me this would also fit that bill. It also has a (somewhat) consistent look to the newer Plasma applications using the Kirigami framework such as Discover and the upcoming new System Settings revamp. This could also fix bug 331162, by allowing Marble users to have direct access to maps hosted on Opendektop.org. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 381603] Unsorted list of online quotes
https://bugs.kde.org/show_bug.cgi?id=381603 --- Comment #3 from Ralf Habacker --- Git commit dbe58201103fac1eaaa5fc96c9adfbdb7030aad6 by Ralf Habacker. Committed on 05/07/2017 at 17:10. Pushed by habacker into branch '4.8'. Fix sorting after rename of an entry in list of online quotes. M +1-0kmymoney/dialogs/settings/ksettingsonlinequotes.cpp https://commits.kde.org/kmymoney/dbe58201103fac1eaaa5fc96c9adfbdb7030aad6 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376393] Regression kMail 5.4.1/2: Invitations are not displayed as such any more
https://bugs.kde.org/show_bug.cgi?id=376393 Gunter Ohrner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Gunter Ohrner --- No, I hadn't. You already told me about this dependency concerning the kAddressbook problems I had, and after installing it it also fixed the issues I had with kMail. I just forgot to close this bug. However, it's not really obvious to the user that kdepim-addons will provide such features - maybe it would somehow be possible to point a user to it in future versions. I.e. in the empty kAddressbook menu entries "Action" etc. add an empty disabled menuentry "Install Addons for additional features" or similar... Similar with kMail Message Themes/Styles etc... But that's now a wishlist item... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 --- Comment #35 from Chris Holland --- Running the following with slideshow and image shows that something is making the scenegraph "dirty". killall plasmashell; QT_LOGGING_RULES="*.debug=true" plasmashell With slideshow, we get this spammed nonstop. qt.quick.dirty: QQuickWindowPrivate::updateDirtyNodes(): qt.scenegraph.time.renderer: time in renderer: total=15ms, preprocess=0, updates=0, binding=0, rendering=14 qt.scenegraph.time.renderloop: Frame rendered with 'basic' renderloop in 16ms, polish=0, sync=0, render=15, swap=0, frameDelta=16 qt.quick.dirty: QQuickWindowPrivate::updateDirtyNodes(): qt.scenegraph.time.renderer: time in renderer: total=15ms, preprocess=0, updates=0, binding=0, rendering=15 qt.scenegraph.time.renderloop: Frame rendered with 'basic' renderloop in 16ms, polish=0, sync=0, render=15, swap=0, frameDelta=17 qt.quick.dirty: QQuickWindowPrivate::updateDirtyNodes(): https://gist.github.com/Zren/c52c4bceb0aa5390dea137cc031745c2#file-gistfile1-txt-L546 Where as with image it's not spammed. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 382021] New: Updates Comets NEA Supernovae KStars 2.7.8 linux
https://bugs.kde.org/show_bug.cgi?id=382021 Bug ID: 382021 Summary: Updates Comets NEA Supernovae KStars 2.7.8 linux Product: kstars Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: john.s...@onlinehome.de Target Milestone: --- Are the correct sources for Comets, NEAs and Supernovae included in KStars? In CdC comets are at http://www.minorplanetcenter.net/iau/Ephemerides/Comets/Soft00Cmt.txt and Asteroids (including NEAs) are at http://www.minorplanetcenter.net/iau/MPCORB/MPCORB.DAT.gz Is there a way for a user to nominate or at least see the links of the sources? Similar concern for new supernovae. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 382022] New: What is Interesting Tonight KStars 2.7.8 Linux Ubuntu MATE 16.04.1 crashes
https://bugs.kde.org/show_bug.cgi?id=382022 Bug ID: 382022 Summary: What is Interesting Tonight KStars 2.7.8 Linux Ubuntu MATE 16.04.1 crashes Product: kstars Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: john.s...@onlinehome.de Target Milestone: --- The WIT window crashes to white when the main sky view is dragged. Closing the window (top right X) and then opening it again from the Tools menu will restore it. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 382023] New: KStars' NEO (Near-Earth-Object) data query from NASA's JPL KStars 2.7.8
https://bugs.kde.org/show_bug.cgi?id=382023 Bug ID: 382023 Summary: KStars' NEO (Near-Earth-Object) data query from NASA's JPL KStars 2.7.8 Product: kstars Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: john.s...@onlinehome.de Target Milestone: --- "KStars' NEO (Near-Earth-Object) data query from NASA's JPL KStars' NEO (Near-Earth-Object) data query from NASA's JPL is now properly working again" Where is this feature? or How to use it? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 --- Comment #20 from Robby Engelmann --- Systemsettings --> Application Style --> Widget Style --> Fine Tuning --> Set "Menubar Style" to "Title Bar Button" -- You are receiving this mail because: You are watching all bug changes.
