[kmail2] [Bug 381631] New: KMail does not delete e-mails on POP3 server.
https://bugs.kde.org/show_bug.cgi?id=381631 Bug ID: 381631 Summary: KMail does not delete e-mails on POP3 server. Product: kmail2 Version: 5.4.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: h6zb8-kdebugs20120...@yahoo.de Target Milestone: --- For a POP3 account I set “days to leave messages on the server” to 8 days, but KMail does not delete any e-mails on the server. This happens for example on a Yahoo and GMX server. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377840] [Wayland] Shows windows from all activities and desktops, doesn't respect settings that should disable this functionality
https://bugs.kde.org/show_bug.cgi?id=377840 kishor...@gmail.com changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381630] New: Trying to change the actions associated with mouse clicks on desktop crashes plasmashell on Wayland
https://bugs.kde.org/show_bug.cgi?id=381630 Bug ID: 381630 Summary: Trying to change the actions associated with mouse clicks on desktop crashes plasmashell on Wayland Product: plasmashell Version: 5.10.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 106282 --> https://bugs.kde.org/attachment.cgi?id=106282=edit Bactrace of the crash When running with Wayland, plasmashell crashes if I try to change the action associated with mouse actions on the desktop. Steps to reproduce: 1. Log in to the Wayland session 2. Right click on desktop 3. Configure desktop > mouse actions 4. Try to change the action associated with any mouse action Observed result: Plasmashell crashes when I click on any action from the dropdown list. Expected result: The option should change without plasmashell crashing, like it does when you try the same steps in an X session. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 381629] New: add arrow's option to annotation tools
https://bugs.kde.org/show_bug.cgi?id=381629 Bug ID: 381629 Summary: add arrow's option to annotation tools Product: okular Version: 0.24.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: rikudou__sen...@outlook.com Target Milestone: --- If it is possible, I want you to add an arrow's option to the annotation tools because I need it in some situation and it is difficult to make it with straight line, I don't know if there are some people who need this option too Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 381628] New: Insane ABI instability
https://bugs.kde.org/show_bug.cgi?id=381628 Bug ID: 381628 Summary: Insane ABI instability Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: k...@carewolf.com CC: kdepim-b...@kde.org, vkra...@kde.org Target Milestone: --- Akonadi ABI breaks every single day between packages from different repos. Please keep ABI stable or package everything under the same version number. Having KMail be unlauncable 6 out of 7 days of the week in "stable" KDE Neon is not professional. Feel free to redirect the bug to a more correct place if it is KDE Neon that are not following the correct procedures. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381627] Message Viewing Pane fails to adjust size to correspond to dpi
https://bugs.kde.org/show_bug.cgi?id=381627 Luke McDougaldchanged: What|Removed |Added CC||luke.mcdoug...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381627] New: Message Viewing Pane fails to adjust size to correspond to dpi
https://bugs.kde.org/show_bug.cgi?id=381627 Bug ID: 381627 Summary: Message Viewing Pane fails to adjust size to correspond to dpi Product: kmail2 Version: 5.3.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: luke.mcdoug...@hotmail.com Target Milestone: --- Created attachment 106281 --> https://bugs.kde.org/attachment.cgi?id=106281=edit Sorry for not including the whole window -- didn't want to bother redacting necessary information KDE as a whole appears to scale beautifully with DPI settings, in particular the 1.5x setting I chose. KMail for the most part continues this trend. However, while the frame containing the message view scales appropriately with DPI, the message window itself does not scale appropriately with DPI. The result is a message view that is much too small for the corresponding space (and my eyes). I was unable to find if this was patched upstream. Sorry if this is a duplicate. Luke -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381626] New: filter to add new contact to an addressbook results in duplicates
https://bugs.kde.org/show_bug.cgi?id=381626 Bug ID: 381626 Summary: filter to add new contact to an addressbook results in duplicates Product: kmail2 Version: 5.5.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: m...@domson.at Target Milestone: --- Created attachment 106280 --> https://bugs.kde.org/attachment.cgi?id=106280=edit screenshots of filter dialog, manage tags dialog and addressbook referring to Bug ID 291152 I report that a filter which takes the following parameter Criteria: "Match all of the following" Action: in addressbook <"new contacts"> with category <"new contact"> results in several duplicates: 1. As I "Apply" the Filter Rules Dialog the category tags change back to default and result in tag duplicates in Manage Tag Dialog 2. As I apply the filter on a list of sent emails it results in contact duplicates in the addressbook "new contacts" Thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343690] Missing windows tabbing
https://bugs.kde.org/show_bug.cgi?id=343690 Boian Berberovchanged: What|Removed |Added CC||bberberov+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 340137] Implement support for window groups (window tabs) in Breeze
https://bugs.kde.org/show_bug.cgi?id=340137 Boian Berberovchanged: What|Removed |Added CC||bberberov+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Boian Berberovchanged: What|Removed |Added CC||bberberov+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 362474] Copy To/Move To does not remember path any more
https://bugs.kde.org/show_bug.cgi?id=362474 --- Comment #11 from Simon--- I've updated and improved the fix for the current version of the master branch on GitHub at https://github.com/thielsn/gwenview/commits/fix_362474 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 350499] Kmail/Kontact crashes while dragging a message
https://bugs.kde.org/show_bug.cgi?id=350499 --- Comment #2 from emele...@gmail.com --- (In reply to Denis Kurz from comment #1) > This bug has never been confirmed for a Kontact version that is based on KDE > Frameworks (5.x). Those versions differ significantly from the old 4.x > series. Therefore, I plan to close it in around two or three months. In the > meantime, it is set to WAITINGFORINFO to give reporters the oportunity to > check if it is still valid. As soon as someone confirms it for a recent > version (at least 5.1, ideally even more recent), I'll gladly reopen it. > > Please understand that we lack the manpower to triage bugs reported for > versions almost two years beyond their end of life. Agreed. Never happened again. I maintain my system(s) updated, so long ago I moved away from 4.x and never saw this issue again. Thanks for all your work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381625] Copying/Moving photograph files between albums does not give Overwrite/Rename/Cancel options if file with same name exists in the destination album.
https://bugs.kde.org/show_bug.cgi?id=381625 aslam karachiwalachanged: What|Removed |Added CC||as...@mythicflow.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381625] New: Copying/Moving photograph files between albums does not give Overwrite/Rename/Cancel options if file with same name exists in the destination album.
https://bugs.kde.org/show_bug.cgi?id=381625 Bug ID: 381625 Summary: Copying/Moving photograph files between albums does not give Overwrite/Rename/Cancel options if file with same name exists in the destination album. Product: digikam Version: 5.5.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: as...@mythicflow.com Target Milestone: --- System: Kubuntu 16.04 This issue appeared after recent upgrade to digiKam 5.5. Prior to the upgrade, when copying/moving a photograph file to an album that already contained a file with the same name, a dialog was presented with options to overwrite the existing file, rename the incoming file, or cancel the operation. Now, with v. 5.5, these options are not provided if a copy/move is attempted to a location where a file with the same name already exists. All that happens now is a notification saying a file with the same name already exists, and the copy/move apparently aborts. Bug 377719 may be related. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381280] Increased CPU usage with Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=381280 Boian Berberovchanged: What|Removed |Added CC||bberberov+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381480] Adding second folderview widget in any desktop containment crashes plasmashell after latest updates in KDE Neon
https://bugs.kde.org/show_bug.cgi?id=381480 Boian Berberovchanged: What|Removed |Added CC||bberberov+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381471] High GPU load causing heat and battery drain
https://bugs.kde.org/show_bug.cgi?id=381471 Boian Berberovchanged: What|Removed |Added CC||bberberov+...@gmail.com --- Comment #6 from Boian Berberov --- gr...@sub.red, do you have any FolderView widgets on your desktop? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 Boian Berberovchanged: What|Removed |Added CC||bberberov+...@gmail.com --- Comment #3 from Boian Berberov --- dmidge, do you have any FolderView widgets on your desktop? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381624] New: Problem with Mailsig in HTML with Picture - Preview hang
https://bugs.kde.org/show_bug.cgi?id=381624 Bug ID: 381624 Summary: Problem with Mailsig in HTML with Picture - Preview hang Product: kmail2 Version: 5.5.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composereditor-ng Assignee: mon...@kde.org Reporter: li...@osit.cc Target Milestone: --- Created attachment 106279 --> https://bugs.kde.org/attachment.cgi?id=106279=edit Not working Mailsignature I had an signatur in Kmail on Kubuntu 16.04 including a picture directly. After i changed to KDENeon the mailpreview hangs when i open a mail with this signature. I can click on other mails, but an preview is not possible any more. The only one what is helping is to reopen the program. And... don't click a message with my signature. What have i done to solve the problem for me. All mails in send with my signatur moved to the mailarchiv. And i changed the signature to load the picutre from external. The problem is, all other have the same problem with older mails from me. So hoply it is possible to fix this. The bad sig is attached. So please let me know if i can help! Thanks a lot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381623] Random Plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=381623 Tonychanged: What|Removed |Added Component|general |general Version|unspecified |master Target Milestone|--- |1.0 Product|kde |plasmashell CC||bhus...@gmail.com, ||plasma-b...@kde.org Platform|unspecified |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 381623] New: Random Plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=381623 Bug ID: 381623 Summary: Random Plasmashell crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jodr...@live.com Target Milestone: --- Application: plasmashell (5.10.90) Qt Version: 5.9.0 Frameworks Version: 5.36.0 Operating System: Linux 4.11.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was browsing the web using firefox, had also steam open, when i notice a "flicker" as the buttom panel dissapeard. Plasmeshell restarted right away. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe44fd5fd40 (LWP 1600))] Thread 14 (Thread 0x7fe3611fa700 (LWP 1725)): #0 0x7fe444085bf1 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7fe44408815b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe444088c1b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe444088dfc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe449bfb75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe449ba4d0a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe4499d705a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7fe3627b3f37 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #8 0x7fe4499db73e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7fe448b924e7 in start_thread () from /lib64/libpthread.so.0 #10 0x7fe4492e0a2f in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7fe38b79a700 (LWP 1717)): #0 0x7fe4440cdb34 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fe444088ca6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe444088dfc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe449bfb75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe449ba4d0a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe4499d705a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe44d716292 in QQuickPixmapReader::run() () from /usr/lib64/libQt5Quick.so.5 #7 0x7fe4499db73e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fe448b924e7 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe4492e0a2f in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7fe394dd7700 (LWP 1716)): #0 0x7fe448b985ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe39f5092fb in cnd_wait (mtx=0x55f71ebd1f00, cond=0x55f71ebd1f28) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x55f71eb3fa70) at u_queue.c:158 #3 0x7fe39f509037 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7fe448b924e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7fe4492e0a2f in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fe3955d8700 (LWP 1715)): #0 0x7fe448b985ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe39f5092fb in cnd_wait (mtx=0x55f71ebd1f00, cond=0x55f71ebd1f28) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x55f71eb037e0) at u_queue.c:158 #3 0x7fe39f509037 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7fe448b924e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7fe4492e0a2f in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fe395dd9700 (LWP 1714)): #0 0x7fe448b985ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe39f5092fb in cnd_wait (mtx=0x55f71ebd1f00, cond=0x55f71ebd1f28) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x55f71eb3fa70) at u_queue.c:158 #3 0x7fe39f509037 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7fe448b924e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7fe4492e0a2f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fe3965da700 (LWP 1713)): #0 0x7fe448b985ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe39f5092fb in cnd_wait (mtx=0x55f71ebd1f00, cond=0x55f71ebd1f28) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x55f71ea5b020) at u_queue.c:158 #3 0x7fe39f509037 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7fe448b924e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7fe4492e0a2f in
[frameworks-baloo] [Bug 381622] New: Segfault when reached fs.inotify.max_user_watches limit
https://bugs.kde.org/show_bug.cgi?id=381622 Bug ID: 381622 Summary: Segfault when reached fs.inotify.max_user_watches limit Product: frameworks-baloo Version: 5.35.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: przemek.wal...@gmail.com Target Milestone: --- Created attachment 106278 --> https://bugs.kde.org/attachment.cgi?id=106278=edit baloo_file_extr coredump My logs contain few baloo_file_extr related segfaults (attachment) with error messages indicating reached limit of max fs watches. I do not remember changing it so it is probably a default value: $ cat /proc/sys/fs/inotify/max_user_watches 8192 Log messages like: "Failed to create watch for "/home/przemek/Projects/JS/Logger/node_modules/uglify-to-browserify/test" No space left on device" were a bit misleading - "no space left on device" was not the case. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381618] Kmail collapses days, weeks and months randomly
https://bugs.kde.org/show_bug.cgi?id=381618 Freekchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Severity|normal |minor Resolution|--- |FIXED --- Comment #1 from Freek --- Sorry, I just found the option "Expand all groups", Kmail seems to remember this. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381621] Kmail crashes when trying to attach file to email in dolphin
https://bugs.kde.org/show_bug.cgi?id=381621 --- Comment #2 from Allen Winter--- works fine for me with kdepim master and Qt5.8.0 looks like the crash is in Qt5.9 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381621] Kmail crashes when trying to attach file to email in dolphin
https://bugs.kde.org/show_bug.cgi?id=381621 Allen Winterchanged: What|Removed |Added CC||win...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381621] Kmail crashes when trying to attach file to email in dolphin
https://bugs.kde.org/show_bug.cgi?id=381621 --- Comment #1 from J.Fly--- Probably related to bug# 381613 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381621] New: Kmail crashes when trying to attach file to email in dolphin
https://bugs.kde.org/show_bug.cgi?id=381621 Bug ID: 381621 Summary: Kmail crashes when trying to attach file to email in dolphin Product: kmail2 Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jerry.fl...@gmail.com Target Milestone: --- Application: kmail (5.5.2) Qt Version: 5.9.0 Frameworks Version: 5.34.0 Operating System: Linux 4.11.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: >From dolphin: Right click -> Actions -> Send as Email Attachment Occurs on PDF and ODT files, fairly certain it's filetype agnostic. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2367c5e940 (LWP 19693))] Thread 27 (Thread 0x7f22d5ffb700 (LWP 19747)): #0 0x7f235aa025ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f234f176c85 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f234f177167 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f234f177f01 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f234f1745cb in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f235a9fc4e7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2364d48a2f in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f22d67fc700 (LWP 19746)): #0 0x7f235aa025ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f234f176c85 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f234f177167 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f234f177f01 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f234f1745cb in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f235a9fc4e7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2364d48a2f in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f22d6ffd700 (LWP 19743)): #0 0x7f2364d3adfd in read () from /lib64/libc.so.6 #1 0x7f2342cd85f1 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-10.0.so #2 0x7f23497ebe2e in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #3 0x7f23497ec8a0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f23497ec960 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f23497fa7c9 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f2342d070b8 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-10.0.so #7 0x7f235a9fc4e7 in start_thread () from /lib64/libpthread.so.0 #8 0x7f2364d48a2f in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f22d77fe700 (LWP 19742)): #0 0x7f235aa0291c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f234f1a5572 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f234f16c69e in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f234f1474fb in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f234f143d78 in base::MessageLoop::RunHandler() () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f234f16095b in base::RunLoop::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f234f1784c6 in base::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f234f1745cb in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f235a9fc4e7 in start_thread () from /lib64/libpthread.so.0 #9 0x7f2364d48a2f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f22d7fff700 (LWP 19741)): #0 0x7f235aa025ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f234fa072c0 in cc::SingleThreadTaskGraphRunner::Run() () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f234f177f01 in base::SimpleThread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f234f1745cb in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f235a9fc4e7 in start_thread () from /lib64/libpthread.so.0 #5 0x7f2364d48a2f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f22ecff9700 (LWP 19740)): #0 0x7f235aa025ed in
[kontact] [Bug 312927] kontact summary sorts events by some unknown order; should sort by time
https://bugs.kde.org/show_bug.cgi?id=312927 --- Comment #14 from Carioca--- As Tom Mittelstädt wrote. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner
https://bugs.kde.org/show_bug.cgi?id=381130 Dr. Chapatinchanged: What|Removed |Added CC||yy...@gmx.com --- Comment #8 from Dr. Chapatin --- I can confirm this bug on Arch, plasma 5.10.2, qt 5.9. Sometimes notification from dolphin about finished copy/move files appears on top left corner. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 381620] New: Is not authenticating user
https://bugs.kde.org/show_bug.cgi?id=381620 Bug ID: 381620 Summary: Is not authenticating user Product: Discover Version: 5.8.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: wba...@msn.com Target Milestone: --- Is not authenticating user, so it does not update. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381619] New: Days, weeks and months in the message list should also de-collapse when clickign anywhere in the bar
https://bugs.kde.org/show_bug.cgi?id=381619 Bug ID: 381619 Summary: Days, weeks and months in the message list should also de-collapse when clickign anywhere in the bar Product: kmail2 Version: 5.5.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: fr...@hmrt.nl Target Milestone: --- You can de-collapse days, weeks and months in the message list by clicking on the arrow before the day, week or months. However, de-collapsing using the rest of the bar requires a double click. To me this is inconsistent. Also, because a single click has no added function over the double click. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381618] New: Kmail collapses days, weeks and months randomly
https://bugs.kde.org/show_bug.cgi?id=381618 Bug ID: 381618 Summary: Kmail collapses days, weeks and months randomly Product: kmail2 Version: 5.5.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: fr...@hmrt.nl Target Milestone: --- By default the message list of Kmail randomly collapses days, weeks and months. I keep opening them up but I'd rather just have them all de-collapsed, always. There is no option to do this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381613] KDE Widget Styles Crashes when clicking configure button for QTCurves style
https://bugs.kde.org/show_bug.cgi?id=381613 --- Comment #2 from J.Fly--- (In reply to Paul from comment #1) > (In reply to J.Fly from comment #0) > > Application: systemsettings5 (5.10.2) > > > > Qt Version: 5.9.0 > > Frameworks Version: 5.34.0 > > Operating System: Linux 4.11.6-1-default x86_64 > > Distribution: "openSUSE Tumbleweed" > > > > -- Information about the crash: > > Open system settings -> click Application style -> change widget style to > > QtCurve -> Click configure -> watch it crash. > > > > QtCurve was installed from openSUSE software repo. > > > > The crash can be reproduced every time. > > > > Just for information. I'm also using Tumbleweed with the same versions as > yourself, and I don't see the crash. Click configure and the configuration > window opens, changes can be made and saved. Interesting, what's your hardware configuration? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381617] New: When replying Kmail editor puts the cursor at the bottom of the message
https://bugs.kde.org/show_bug.cgi?id=381617 Bug ID: 381617 Summary: When replying Kmail editor puts the cursor at the bottom of the message Product: kmail2 Version: 5.5.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: fr...@hmrt.nl Target Milestone: --- When replying to an email, every email solution I have every used puts the message you are replying to at the bottom of the new message and inserts the cursor at the top. Not Kmail. There is not even an option change this (although if there was, starting at the top it should be the default). Can this please be changed? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 381581] Expand category doesnt work after edit the parent category
https://bugs.kde.org/show_bug.cgi?id=381581 --- Comment #2 from aper...@gmail.com --- Thank you for replying, Ralf, As I'm totally noobie in this subject, it was like Japanese to new lol Is there any step by step guide to solve this?? Thank you again (In reply to Ralf Habacker from comment #1) > This is caused by a bug introduced with > https://cgit.kde.org/kmymoney.git/commit/ > ?id=593973cd5c6237db698efd27fcc2290309f48da4 > > Reverting this commit fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375954] Faves option inside G'MIC
https://bugs.kde.org/show_bug.cgi?id=375954 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- We've just replaced our own gmic dialog with a plugin that communicates with the official gmic-qt plugin (which still needs to be released with our integration code, but it's already been merged), so we can close all current g'mic bugs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 342900] Apply filter again in filter menu doesn't work for gmic
https://bugs.kde.org/show_bug.cgi?id=342900 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REOPENED|RESOLVED --- Comment #6 from Boudewijn Rempt --- We've just replaced our own gmic dialog with a plugin that communicates with the official gmic-qt plugin (which still needs to be released with our integration code, but it's already been merged), so we can close all current g'mic bugs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 347621] G'MIC "favourite" feature is missing
https://bugs.kde.org/show_bug.cgi?id=347621 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #5 from Boudewijn Rempt --- We've just replaced our own gmic dialog with a plugin that communicates with the official gmic-qt plugin (which still needs to be released with our integration code, but it's already been merged), so we can close all current g'mic bugs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381204] Extract foreground [interactive] result in offset layers with G'mic 0.1.7 in Krita 3.1.4
https://bugs.kde.org/show_bug.cgi?id=381204 Boudewijn Remptchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #3 from Boudewijn Rempt --- We've just replaced our own gmic dialog with a plugin that communicates with the official gmic-qt plugin (which still needs to be released with our integration code, but it's already been merged), so we can close all current g'mic bugs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362740] G'MIC Filter Black & White Interactive Colorize
https://bugs.kde.org/show_bug.cgi?id=362740 Boudewijn Remptchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #3 from Boudewijn Rempt --- We've just replaced our own gmic dialog with a plugin that communicates with the official gmic-qt plugin (which still needs to be released with our integration code, but it's already been merged), so we can close all current g'mic bugs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 342828] Colorise Interactive in GMIC clears control point when relaunching and also the clear control point button is missing
https://bugs.kde.org/show_bug.cgi?id=342828 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt --- We've just replaced our own gmic dialog with a plugin that communicates with the official gmic-qt plugin (which still needs to be released with our integration code, but it's already been merged), so we can close all current g'mic bugs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 353205] Filter descriptions are shown incorrectly in the G'MIC window
https://bugs.kde.org/show_bug.cgi?id=353205 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #3 from Boudewijn Rempt --- We've just replaced our own gmic dialog with a plugin that communicates with the official gmic-qt plugin (which still needs to be released with our integration code, but it's already been merged), so we can close all current g'mic bugs. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380022] kdeconnect: can't browse files
https://bugs.kde.org/show_bug.cgi?id=380022 --- Comment #2 from pmarget...@gmail.com --- Created attachment 106277 --> https://bugs.kde.org/attachment.cgi?id=106277=edit Browsing Xiaomi error -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380022] kdeconnect: can't browse files
https://bugs.kde.org/show_bug.cgi?id=380022 pmarget...@gmail.com changed: What|Removed |Added CC||pmarget...@gmail.com --- Comment #1 from pmarget...@gmail.com --- Archlinux KDE Connect 1.0.3 Xiaomi redmi note 3 pro KDE Connect 1.6.4 Trying to access Xiaomi in places in Dolphin generates this output in journal: Jun 24 19:24:19 loonix dolphin[1176]: Trying to convert empty KLocalizedString to QString. Jun 24 19:24:19 loonix kdeinit5[1277]: kdeconnect.kio: Setting host: "84a764d5d205905a" Jun 24 19:24:19 loonix kdeinit5[1277]: kdeconnect.kio: Listing... QUrl("kdeconnect://84a764d5d205905a/") Jun 24 19:24:19 loonix kdeinit5[1277]: kdeconnect.kio: ListDevice "84a764d5d205905a" Jun 24 19:24:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Mount device: "Xiaomi" Jun 24 19:24:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Created mounter Jun 24 19:24:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Starting loop to wait for mount Jun 24 19:24:19 loonix kdeinit5[1279]: kdeconnect.kio: Setting host: "84a764d5d205905a" Jun 24 19:24:19 loonix kdeinit5[1279]: kdeconnect.kio: Stat: QUrl("kdeconnect://84a764d5d205905a/") Jun 24 19:24:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Unmount QObject(0x0) Jun 24 19:24:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Starting process: "sshfs kdeconnect@192.0.2.1:/ /home/anon/.config/kdeconnect/84a764d5d205905a/kdeconnect_sftp/84a764d5d205905a -p 1739 -f -F /dev/null -o IdentityFile=/home/anon/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=ssh-dss -o password_stdin" Jun 24 19:24:19 loonix kdeconnectd[475]: QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packageReceived(NetworkPackage): Unregistered input type in parameter list: NetworkPackage Jun 24 19:24:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Process started Jun 24 19:24:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: "Xiaomi" "Remote filesystem mounted at /home/anon/.config/kdeconnect/84a764d5d205905a/kdeconnect_sftp/84a764d5d205905a" Jun 24 19:25:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: stdout: "Timeout waiting for prompt\n" Jun 24 19:25:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Process finished (exit code: 1 ) Jun 24 19:25:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: "Xiaomi" Remote filesystem unmounted Jun 24 19:25:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Unmount KProcess(0xe0b260) Jun 24 19:25:19 loonix kdeconnectd[475]: kdeconnect.plugin.sftp: Destroy mounter -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380377] FLAC files show length 0
https://bugs.kde.org/show_bug.cgi?id=380377 --- Comment #3 from Jonathan Ryshpan--- (In reply to Leslie Zhai from comment #2) > Hi Jonathan, > > K3b 2.0.3 is not be maintained any more, please try k3b 17.07.0 > https://github.com/KDE/k3b I am using Fedora 24 :) > http://os.inf.tu-dresden.de/pipermail/l4-hackers/2017/008023.html Very perplexing, since this is the version of k3b in the Fedora-25 release. Maybe the version will be upgraded in Fedora-26. Or maybe the Fedora team is out of contact with the k3b team. Or maybe I should juse build from source. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381613] KDE Widget Styles Crashes when clicking configure button for QTCurves style
https://bugs.kde.org/show_bug.cgi?id=381613 Paulchanged: What|Removed |Added CC||pip@gmx.com --- Comment #1 from Paul --- (In reply to J.Fly from comment #0) > Application: systemsettings5 (5.10.2) > > Qt Version: 5.9.0 > Frameworks Version: 5.34.0 > Operating System: Linux 4.11.6-1-default x86_64 > Distribution: "openSUSE Tumbleweed" > > -- Information about the crash: > Open system settings -> click Application style -> change widget style to > QtCurve -> Click configure -> watch it crash. > > QtCurve was installed from openSUSE software repo. > > The crash can be reproduced every time. > Just for information. I'm also using Tumbleweed with the same versions as yourself, and I don't see the crash. Click configure and the configuration window opens, changes can be made and saved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381616] New: Segfault when previewing app switcher
https://bugs.kde.org/show_bug.cgi?id=381616 Bug ID: 381616 Summary: Segfault when previewing app switcher Product: systemsettings Version: 5.10.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@ashka.me Target Milestone: --- Application: systemsettings5 (5.10.2) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.11.6-3-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I had selected the "Small icons" app switcher, the segfault happened when I clicked the "preview" button. I was not able to reproduce after restarting ksystemsettings. The crash does not seem to be reproducible. -- Backtrace: Application: Configuration du système (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8249cb47c0 (LWP 1466))] Thread 7 (Thread 0x7f8203fff700 (LWP 1593)): #0 0x7f82459662bd in poll () at /usr/lib/libc.so.6 #1 0x7f823f83ebf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f823f83ed0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f824628ee9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f824623521a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f824605740a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f8244349645 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f824605bcbd in () at /usr/lib/libQt5Core.so.5 #8 0x7f824199b297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f824597025f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f82015ed700 (LWP 1499)): #0 0x7f823f83eae8 in () at /usr/lib/libglib-2.0.so.0 #1 0x7f823f83ed0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #2 0x7f824628ee9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f824623521a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f824605740a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f8244349645 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f824605bcbd in () at /usr/lib/libQt5Core.so.5 #7 0x7f824199b297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f824597025f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f8221ce1700 (LWP 1481)): #0 0x7f823f883a29 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f823f83ebbe in () at /usr/lib/libglib-2.0.so.0 #2 0x7f823f83ed0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f824628ee9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f824623521a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f824605740a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f8244349645 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f824605bcbd in () at /usr/lib/libQt5Core.so.5 #8 0x7f824199b297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f824597025f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8219b38700 (LWP 1480)): #0 0x7f823f83e0cd in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7f823f83eb2b in () at /usr/lib/libglib-2.0.so.0 #2 0x7f823f83ed0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f824628ee9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f824623521a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f824605740a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f8244349645 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f824605bcbd in () at /usr/lib/libQt5Core.so.5 #8 0x7f824199b297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f824597025f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f822e491700 (LWP 1468)): #0 0x7f82459662bd in poll () at /usr/lib/libc.so.6 #1 0x7f823f83ebf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f823f83ed0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f824628ee9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f824623521a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f824605740a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f8246bb5d45 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f824605bcbd in () at /usr/lib/libQt5Core.so.5 #8 0x7f824199b297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f824597025f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8236cf7700 (LWP 1467)): #0 0x7f82459662bd in poll () at /usr/lib/libc.so.6 #1
[Discover] [Bug 380496] Discover crashes upon opening
https://bugs.kde.org/show_bug.cgi?id=380496 Antonio Rojaschanged: What|Removed |Added CC||st0r...@gmail.com --- Comment #15 from Antonio Rojas --- *** Bug 381601 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 381601] Discover crashes on startup
https://bugs.kde.org/show_bug.cgi?id=381601 Antonio Rojaschanged: What|Removed |Added CC||aro...@archlinux.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 380496 *** -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 381615] New: Amazon.de search stopped working
https://bugs.kde.org/show_bug.cgi?id=381615 Bug ID: 381615 Summary: Amazon.de search stopped working Product: tellico Version: 3.0.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: peter.fink...@inode.at Target Milestone: --- Have been using the amazon.de search via "ISBN" for a long time. Today I wanted to add two books to my collection, but it would not show any result. The books do exist, because I ordered them from Amazon (ISBN 978-3-89908-646-1 and 978-3-95839-463-6). I have also tried searching by title but no success. I logged into the aws management console, it shows accessing the api, so the credentials are ok. I assume the result returned by amazon.de do not get processed somehow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381614] New: plasma_containmentactions_applauncher.so only shows GenericName
https://bugs.kde.org/show_bug.cgi?id=381614 Bug ID: 381614 Summary: plasma_containmentactions_applauncher.so only shows GenericName Product: plasmashell Version: 5.10.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: p.suetter...@royac.iac.es CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 The simple application launcher that you can bind to plasma rootwindow events only shows the GenericName entry in the menu (but sorts the list based on Name). The panel applets allow to change this to using names, so one can find the proper program looking for. Please add a similar option for the simple one. Or at least then use the GenericName for sorting the menu, so that similar programs are grouped together and not spread over the whole list. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 263428] Allow opening a file‘s location
https://bugs.kde.org/show_bug.cgi?id=263428 XYQuadratchanged: What|Removed |Added CC||juliquad...@gmail.com --- Comment #2 from XYQuadrat --- Option exists in 17.04.2 (Open Path). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #2 from dmidge--- another stacktrace a while later: thread apply all bt full Thread 13 (Thread 0x7ffef7082700 (LWP 17326)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffe5ee5ee1 in () at /usr/lib/libpulse.so.0 #2 0x7fffe5ed76f1 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7fffe5ed7d8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fffe5ed7e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fffe5ee5e29 in () at /usr/lib/libpulse.so.0 #6 0x7fffe5875fe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7ffef870b700 (LWP 17325)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x74d8f645 in () at /usr/lib/libQt5Qml.so.5 #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fff0d57e700 (LWP 17300)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fff0ec03427 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fff3747f700 (LWP 17289)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 ---Type to continue, or q to quit--- #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x75947836 in () at /usr/lib/libQt5Quick.so.5 #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fff3cd0f700 (LWP 17287)): #0 0x70df339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fffc56a52fb in () at /usr/lib/xorg/modules/dri/nouveau_dri.so #2 0x7fffc56a5037 in () at /usr/lib/xorg/modules/dri/nouveau_dri.so #3 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fffc7dea700 (LWP 17285)): #0 0x70df339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x77662ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x77662b09 in () at /usr/lib/libQt5Script.so.5 #3 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fffd1b0b700 (LWP 17284)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #7 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fffd3bb3700 (LWP 17283)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 ---Type to continue, or q to quit--- #4 0x71dfe21a in
[systemsettings] [Bug 381613] New: KDE Widget Styles Crashes when clicking configure button for QTCurves style
https://bugs.kde.org/show_bug.cgi?id=381613 Bug ID: 381613 Summary: KDE Widget Styles Crashes when clicking configure button for QTCurves style Product: systemsettings Version: 5.10.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jerry.fl...@gmail.com Target Milestone: --- Application: systemsettings5 (5.10.2) Qt Version: 5.9.0 Frameworks Version: 5.34.0 Operating System: Linux 4.11.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Open system settings -> click Application style -> change widget style to QtCurve -> Click configure -> watch it crash. QtCurve was installed from openSUSE software repo. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1408a1b8c0 (LWP 12936))] Thread 9 (Thread 0x7f13d762e700 (LWP 12945)): #0 0x7f140072b5ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f13e20392fb in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f13e2039037 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f14007254e7 in start_thread () from /lib64/libpthread.so.0 #4 0x7f14046a2a2f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f13d7e2f700 (LWP 12944)): #0 0x7f140072b5ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f13e20392fb in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f13e2039037 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f14007254e7 in start_thread () from /lib64/libpthread.so.0 #4 0x7f14046a2a2f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f13d8630700 (LWP 12943)): #0 0x7f140072b5ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f13e20392fb in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f13e2039037 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f14007254e7 in start_thread () from /lib64/libpthread.so.0 #4 0x7f14046a2a2f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f13d8e31700 (LWP 12942)): #0 0x7f140072b5ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f13e20392fb in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f13e2039037 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f14007254e7 in start_thread () from /lib64/libpthread.so.0 #4 0x7f14046a2a2f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f13d986d700 (LWP 12941)): #0 0x7f140072b5ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f13e20392fb in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f13e2039037 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f14007254e7 in start_thread () from /lib64/libpthread.so.0 #4 0x7f14046a2a2f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f13da1af700 (LWP 12940)): #0 0x7f140072b5ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f13e20392fb in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f13e2039037 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f14007254e7 in start_thread () from /lib64/libpthread.so.0 #4 0x7f14046a2a2f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f13ed92c700 (LWP 12939)): #0 0x7f140469908d in poll () from /lib64/libc.so.6 #1 0x7f13fe809ce9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f13fe809dfc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1404fb475b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f1404f5dd0a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f1404d9005a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f140592ca45 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f1404d9473e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7f14007254e7 in start_thread () from /lib64/libpthread.so.0 #9 0x7f14046a2a2f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f13f5e49700 (LWP 12938)): #0 0x7f140469908d in poll () from /lib64/libc.so.6 #1 0x7f1400fa1387 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f1400fa317a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f13f8c01249 in QXcbEventReader::run() () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f1404d9473e in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7f14007254e7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f14046a2a2f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f1408a1b8c0 (LWP 12936)): [KCrash Handler] #6
[systemsettings] [Bug 381612] New: configuration does not work
https://bugs.kde.org/show_bug.cgi?id=381612 Bug ID: 381612 Summary: configuration does not work Product: systemsettings Version: 5.5.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lez...@gmail.com Target Milestone: --- Application: systemsettings5 (5.5.5) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.4.0-81-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: openning configuration of systrem - Unusual behavior I noticed: crashed, restatt recrached, and so on The crash can be reproduced every time. -- Backtrace: Application: Configuration du système (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6f23a23900 (LWP 18431))] Thread 3 (Thread 0x7f6f02380700 (LWP 18434)): #0 0x7f6f2013b70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6f1d08b38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6f1d08b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6f20a687eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6f20a0fb4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6f2082c834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6f1f1aa3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f6f208317be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6f1c731754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #9 0x7f6f1d5ac6ba in start_thread (arg=0x7f6f02380700) at pthread_create.c:333 #10 0x7f6f201473dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f6f10ffb700 (LWP 18432)): #0 0x7f6f2013b70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6f1de22c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f6f1de248d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f6f1397f889 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f6f208317be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6f1c731754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #6 0x7f6f1d5ac6ba in start_thread (arg=0x7f6f10ffb700) at pthread_create.c:333 #7 0x7f6f201473dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f6f23a23900 (LWP 18431)): [KCrash Handler] #6 0x7f6f20075428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f6f2007702a in __GI_abort () at abort.c:89 #8 0x7f6f2081ef81 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f6f1f462af1 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f6f1f46b332 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f6f1f46b733 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f6f2193d2b5 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f6f1f49e871 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f6f21ee505c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f6f21eea516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f6f20a1238b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f6f219354ac in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x7f6f2193621d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x7f6f21919f08 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #20 0x7f6f139b1200 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #21 0x7f6f1d08b197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f6f1d08b3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f6f1d08b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f6f20a687cf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f6f20a0fb4a in QEventLoop::exec(QFlags) ()
[plasmashell] [Bug 381611] Task Panel crashes with Segmentation fault after size/behaviour modification.
https://bugs.kde.org/show_bug.cgi?id=381611 Psijicchanged: What|Removed |Added CC||psi...@gmail.com Flags||X11? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381611] New: Task Panel crashes with Segmentation fault after size/behaviour modification.
https://bugs.kde.org/show_bug.cgi?id=381611 Bug ID: 381611 Summary: Task Panel crashes with Segmentation fault after size/behaviour modification. Product: plasmashell Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: psi...@gmail.com Target Milestone: 1.0 Created attachment 106276 --> https://bugs.kde.org/attachment.cgi?id=106276=edit Log Task Panel crashes with Segmentation fault after size/behaviour modification. OpenSuse Leap 42.2, Kernel 4.4.70 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 347045] Sunday is always automatically selected once weekly recurrence drop down is clicked
https://bugs.kde.org/show_bug.cgi?id=347045 --- Comment #5 from bugzy--- Created attachment 106275 --> https://bugs.kde.org/attachment.cgi?id=106275=edit Video Showing the bug and how to reproduce it Attached video of the bug and how to reproduce it -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350555] Unable to handle quotation marks in »To« field.
https://bugs.kde.org/show_bug.cgi?id=350555 --- Comment #5 from Bernhard Scheirle--- Still reproduce able in kmail2 5.5.2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 381610] windows sometimes shifted upwards when starting new program
https://bugs.kde.org/show_bug.cgi?id=381610 Paul Loockchanged: What|Removed |Added CC||paullo...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 381610] New: windows sometimes shifted upwards when starting new program
https://bugs.kde.org/show_bug.cgi?id=381610 Bug ID: 381610 Summary: windows sometimes shifted upwards when starting new program Product: kde Version: 4.14.1 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: paullo...@t-online.de Target Milestone: --- Created attachment 106274 --> https://bugs.kde.org/attachment.cgi?id=106274=edit Detailed description of crashes; my system parameters Desktop-windows are sometimes shifted upwards by the size of the upper decoration. If the window was already at y-position zero the upper decoration is lost and the window is not movable nor can it be closed if no menu or close-button exists. "kde4-config --version" shows KDE: 4.14.22 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 --- Comment #15 from Mark Fraser--- I'm running Akregator 16.12.3 and this is still happening. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351014] Windows sometimes are translated upwards
https://bugs.kde.org/show_bug.cgi?id=351014 Paul Loockchanged: What|Removed |Added CC||paullo...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 381602] support for multi/standalone windows
https://bugs.kde.org/show_bug.cgi?id=381602 Kåre Särschanged: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #3 from Kåre Särs --- The KTextEditor part is only responsible of opening and editing a document. So far the applications take care of keeping track of what files are open and stuff like that. I don't think it is the "renderer's" task to add this kind of feature, but that's just me ;) It is possible to add a "detach" feature if wanted quite easily, but somebody would have to do it and maintain it... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381194] KMail not detecting HTML mails
https://bugs.kde.org/show_bug.cgi?id=381194 --- Comment #2 from Mark Fraser--- Even if I set the "message default format" to prefer HTML or set it in security settings, it will go back to displaying text or not displaying images when I go back to that folder later. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 381609] Different view modes in different windows
https://bugs.kde.org/show_bug.cgi?id=381609 Vishnuchanged: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 381609] New: Different view modes in different windows
https://bugs.kde.org/show_bug.cgi?id=381609 Bug ID: 381609 Summary: Different view modes in different windows Product: okular Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: vishn...@gmail.com Target Milestone: --- I am using Okular version 1.1.2 Currently, I cannot have different view modes in two separate, simultaneous instances. For eg., I can't have a single page view in one, and a double in the other. It would be nice to have this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 --- Comment #1 from dmidge--- Please ask if you need more info. Thanks for your job! :o) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381608] New: Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 Bug ID: 381608 Summary: Plasmashell use 100% cpu Product: plasmashell Version: 5.10.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: quelque_...@yahoo.fr CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 For some reason, plasmashell uses more than 100% cpu, I don't why. I think it is when I leave my computer stalling for more than 5min, but I don't need to get to the screensaver to have that. I'm using plasmashell 5.10.2, on archlinux, with the nouveau driver 1.0.15-1. uname -a: Linux coincoin.mooo.com 4.11.5-1-ARCH #1 SMP PREEMPT Wed Jun 14 16:19:27 CEST 2017 x86_64 GNU/Linux Nothing's relevant in dmesg. Here's the stack trace: Thread 10 (Thread 0x7fff0d27e700 (LWP 16065)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fff0e903427 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fff3747f700 (LWP 16053)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x75947836 in () at /usr/lib/libQt5Quick.so.5 #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fff3cd0f700 (LWP 16052)): #0 0x70df339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fffc56a52fb in () at /usr/lib/xorg/modules/dri/nouveau_dri.so #2 0x7fffc56a5037 in () at /usr/lib/xorg/modules/dri/nouveau_dri.so #3 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fffc7dea700 (LWP 16051)): #0 0x70df339d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x77662ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x77662b09 in () at /usr/lib/libQt5Script.so.5 #3 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fffd1b0b700 (LWP 16050)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #7 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fffd3bb3700 (LWP 16049)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x71dfe21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x71c2040a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x74d8f645 in () at /usr/lib/libQt5Qml.so.5 #7 0x71c24cbd in () at /usr/lib/libQt5Core.so.5 #8 0x70ded297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7153925f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fffda319700 (LWP 16048)): #0 0x7152f2bd in poll () at /usr/lib/libc.so.6 #1 0x7fffec0eabf9 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffec0ead0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x71e57e7f in
[frameworks-ktexteditor] [Bug 381602] support for multi/standalone windows
https://bugs.kde.org/show_bug.cgi?id=381602 --- Comment #2 from RJVB--- > View -> New Window, but then you get the same session, just two windows. That's comparable to what Creator does, though there you don't get an exact clone of the entire session window, complete with side-views and all. The only use case I could think of where I would find this useful myself is if one of the cloned copies didn't change when I was editing the other, as a quick and dirty way to keep a copy of an original version at hand. What I'm thinking of is a possibility of opening just an editor window as if by reparenting a document tab, in a window that doesn't duplicate any unnecessary widgets but that does belong to the same process. Ideally you'd be able to detach an existing tab but also open a document in its own window from the document or file tree view; that choice could even be recorded in the session data and possibly be made the default behaviour. And I'm really also thinking of a feature that's implemented at the level of the framework or kpart, so that it becomes available automatically in any application that uses them, without need for any action. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376377] Smaller left monitor display looks like it's at 0,0 when set to (and acts) 0,90 (wayland)
https://bugs.kde.org/show_bug.cgi?id=376377 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 381602] support for multi/standalone windows
https://bugs.kde.org/show_bug.cgi?id=381602 Kåre Särschanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- Thanks for the report. I think we already have what you are asking for with at least Kate. You can use View -> New Window, but then you get the same session, just two windows. If you open a file with kate with the parameter "-n" you get a new instance of Kate that does not share session with the already running one. I have personally changed the command that Dolphin uses to start Kate to always open in a new instance. If you use the documents view you can also right-click a document in the tree and select to open it with an external application (KWrite, ...). Is this enough for you needs? Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 174977] clicking on system tray icon doesn't open the relevant kontact part
https://bugs.kde.org/show_bug.cgi?id=174977 --- Comment #37 from Clay Weber--- Still happening with kdepim as available in KDE Neon User edition. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=344326 --- Comment #168 from Bob Wya--- (In reply to Martin Flöser from comment #165) > I created a patch for the issue at https://phabricator.kde.org/D6344 > > I do not have an NVIDIA card, so I cannot test. It is based upon the > information which we have in this bug report. Please test whether it works. Martin I get similar results - as with your previous patch (see comments 151-153). Currently testing with a Nvidia GTX 970M + driver 381.22 with KWin 5.10.2. Tested with the KWin compositor enabled and using OpenGL 3.1 rendering backend. WITH the patch and after a suspend to disk the only "damaged surfaces" are things like VDPAU accelerated video playback and Chrome/Chromium content (probably GL accelerated). Moving the Chromium Window is enough to clear the artefacts in the latter case. Pretty similar to Windows IMHO. WITHOUT the patch significant portions of the screen are reproduceably degraded / damaged. E.g. KWin decorations, etc. So (personally) I'd say ship it!"! Thanks for working on this issue... Despite your antithesis towards Nvidia! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 381607] New: krunner crashes during calculation
https://bugs.kde.org/show_bug.cgi?id=381607 Bug ID: 381607 Summary: krunner crashes during calculation Product: krunner Version: 5.10.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: l...@georgemail.de Target Milestone: --- Application: krunner (5.10.2) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.11.6-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: while entering arithmetic queries (e.g. "12*300), krunner freezes from time to time until it crashes. The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbbc877a7c0 (LWP 640))] Thread 14 (Thread 0x7fbb75ffb700 (LWP 964)): #0 0x7fbbc3f443b9 in syscall () at /usr/lib/libc.so.6 #1 0x7fbbc462cad5 in QBasicMutex::lockInternal() () at /usr/lib/libQt5Core.so.5 #2 0x7fbbc4635ff7 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fbb9dccf3cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fbb9dcd42b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fbb9dcce913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fbb9dcd1b6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fbbc4634cbd in () at /usr/lib/libQt5Core.so.5 #8 0x7fbbc1ce2297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fbbc3f4925f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fbb767fc700 (LWP 963)): #0 0x7fbbc1ce839d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fbbc46360eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fbbc462ef7b in QSemaphore::acquire(int) () at /usr/lib/libQt5Core.so.5 #3 0x7fbbc483e778 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #4 0x7fbb9562977f in () at /usr/lib/qt/plugins/krunner_placesrunner.so #5 0x7fbb9def3830 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /usr/lib/libKF5Runner.so.5 #6 0x7fbb9dcd34a8 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fbb9dcd24fe in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fbb9dcd1c2d in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fbbc4634cbd in () at /usr/lib/libQt5Core.so.5 #10 0x7fbbc1ce2297 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fbbc3f4925f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fbb76ffd700 (LWP 962)): #0 0x7fbbc3f443b9 in syscall () at /usr/lib/libc.so.6 #1 0x7fbbc462cad5 in QBasicMutex::lockInternal() () at /usr/lib/libQt5Core.so.5 #2 0x7fbbc4635ff7 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fbb9dccf3cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fbb9dcd42b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fbb9dcce913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fbb9dcd1b6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fbbc4634cbd in () at /usr/lib/libQt5Core.so.5 #8 0x7fbbc1ce2297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fbbc3f4925f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fbb777fe700 (LWP 961)): #0 0x7fbbc3f443b9 in syscall () at /usr/lib/libc.so.6 #1 0x7fbbc462cad5 in QBasicMutex::lockInternal() () at /usr/lib/libQt5Core.so.5 #2 0x7fbb9def5e6d in () at /usr/lib/libKF5Runner.so.5 #3 0x7fbb9dcd293c in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fbb9dcd209b in ThreadWeaver::Job::defaultEnd(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fbb9dcd2531 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fbb9dcd1c2d in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fbbc4634cbd in () at /usr/lib/libQt5Core.so.5 #8 0x7fbbc1ce2297 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fbbc3f4925f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fbb77fff700 (LWP 960)): [KCrash Handler] #5 0x7fbbc3e8f670 in
[kate] [Bug 381606] Kwrite crashes upon close
https://bugs.kde.org/show_bug.cgi?id=381606 Giampaolochanged: What|Removed |Added Version|unspecified |16.12 Keywords||regression CC||giampaolo.ferradini@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381606] New: Kwrite crashes upon close
https://bugs.kde.org/show_bug.cgi?id=381606 Bug ID: 381606 Summary: Kwrite crashes upon close Product: kate Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: giampaolo.ferrad...@gmail.com Target Milestone: --- Hi there, Starting a few weeks ago, Kwrite almost always crashes upon exit (click on the top right X button). 90% of the time it crashes when it is the last instance of kwrite open on my desktop (I often open multiple ones). 10% of the time it seems to happen when other kwrite instances are still open and functioning. Bug is reproduceable. Thank you and kindest regards! Giampaolo Please find below general and developer information: --- Eseguibile: kwrite PID: 14905 Segnale: Segmentation fault (11) Ora: 24/06/17 16:15:50 --- Application: kwrite (kwrite), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f84fbcaa580 (LWP 14905))] Thread 2 (Thread 0x7f84eb83a700 (LWP 14907)): [KCrash Handler] #6 0x7f84f9703f8d in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /lib64/libQt5Core.so.5 #7 0x7f84f994c570 in QDBusConnectionPrivate::closeConnection() () at /lib64/libQt5DBus.so.5 #8 0x7f84f993b0f2 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #9 0x7f84f95399ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f84f611273a in start_thread () at /lib64/libpthread.so.0 #11 0x7f84f8922e0f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f84fbcaa580 (LWP 14905)): #0 0x7f84f6118460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f84f953a04a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f84f95395ce in QThread::wait(unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7f84f9938696 in QDBusConnectionManager::~QDBusConnectionManager() () at /lib64/libQt5DBus.so.5 #4 0x7f84f9938759 in (anonymous namespace)::Q_QGS__q_manager::innerFunction()::Holder::~Holder() () at /lib64/libQt5DBus.so.5 #5 0x7f84f885574a in __cxa_finalize () at /lib64/libc.so.6 #6 0x7f84f9937e03 in __do_global_dtors_aux () at /lib64/libQt5DBus.so.5 #7 0x7ffee3771510 in () #8 0x7f84fdc044ea in _dl_fini () at /lib64/ld-linux-x86-64.so.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 344416] 'make regtest' does not work cleanly on OS X
https://bugs.kde.org/show_bug.cgi?id=344416 Christoph Feckchanged: What|Removed |Added Keywords||Tracking -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 312927] kontact summary sorts events by some unknown order; should sort by time
https://bugs.kde.org/show_bug.cgi?id=312927 Laurent Montelchanged: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED --- Comment #13 from Laurent Montel --- IT's sorted from A to Z Ok I need to look at it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368535] Messageviewer: Line pitch too small on high dpi settings
https://bugs.kde.org/show_bug.cgi?id=368535 Tom Mittelstädtchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Tom Mittelstädt --- seems to be fixed in 5.4.3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 372970] Missing features in Discover
https://bugs.kde.org/show_bug.cgi?id=372970 Christoph Feckchanged: What|Removed |Added Keywords|Brainstorm | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379118] Discover became useless with bug. (He doesn't show programs, only fonts and widgets)
https://bugs.kde.org/show_bug.cgi?id=379118 Christoph Feckchanged: What|Removed |Added Keywords|Brainstorm | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381605] New: Importing large image collection slows down to unacceptable speed
https://bugs.kde.org/show_bug.cgi?id=381605 Bug ID: 381605 Summary: Importing large image collection slows down to unacceptable speed Product: digikam Version: 5.5.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: piotergmo...@hotmail.com Target Milestone: --- There is something wrong with import - speed. My setup is laptop + NAS. On laptop's local SSD drive I have digikam.db, NAS (Synology) is a datastore for images. When I copy images from laptop to NAS (using dolphin) the average speed is 20-50MB/s. The same set of images imported from MPT device (Samsung smart phone, connected with USB) or local folder on SSD drive (using CTRL+ALT+I) makes the process slw. When I monitor the LAN speed during import I can see weird behavior. Net usage is generally very low, with some occasional peaks. >From DK point of view I can see progress, but it is very very slow. The first images are going well, but soon (3-4%) there is huge slowdown and it forces me to interrupt the process. The scale of import is about 350 images/video files (10GB of data). My system is Kubuntu, Digikam package from Phillip5 ppa. Regards P. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374063] file creation date
https://bugs.kde.org/show_bug.cgi?id=374063 Christoph Feckchanged: What|Removed |Added Keywords|accessibility, | |future_project | -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 312927] kontact summary sorts events by some unknown order; should sort by time
https://bugs.kde.org/show_bug.cgi?id=312927 --- Comment #12 from Tom Mittelstädt--- Still present in kontact 5.4.3. Sort order seems to be something like: Today 16:00 Today 09:00 Tomorrow15:00 Tomorrow10:00 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 328652] Crash that happens some times when executing new apps
https://bugs.kde.org/show_bug.cgi?id=328652 Christoph Feckchanged: What|Removed |Added Keywords|pw2-porting | -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 344416] 'make regtest' does not work cleanly on OS X
https://bugs.kde.org/show_bug.cgi?id=344416 Christoph Feckchanged: What|Removed |Added Keywords|Tracking| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380263] Almost everything on my krita isnt working.
https://bugs.kde.org/show_bug.cgi?id=380263 Christoph Feckchanged: What|Removed |Added Severity|critical|normal Resolution|WAITINGFORINFO |INVALID Keywords|accessibility, Tracking,| |usability | Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381600] Plasma crashes with rendering glitches/re-rendering randomly
https://bugs.kde.org/show_bug.cgi?id=381600 Martin Flöserchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Flöser --- As with all Arch bug reports the backtrace is unfortunately useless. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 351993] kmail seems to hang infinitely long on retrieving emails
https://bugs.kde.org/show_bug.cgi?id=351993 --- Comment #10 from Tim Climis--- I can confirm that I have not had this problem with any recent version for at least a year. -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 380085] TortoiseHG fails with Unable to extract keyFile from phrase "git@gitserver's password: "
https://bugs.kde.org/show_bug.cgi?id=380085 Christoph Feckchanged: What|Removed |Added Version Fixed In||5.10.3 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kss ||haskpass/4a6d3f932c3627e0f4 ||d3f1a452ce1097c55f070b --- Comment #2 from Christoph Feck --- Git commit 4a6d3f932c3627e0f4d3f1a452ce1097c55f070b by Christoph Feck. Committed on 24/06/2017 at 11:42. Pushed by cfeck into branch 'Plasma/5.10'. Support mercurial (hg) ssh prompts FIXED-IN: 5.10.3 Differential Revision: https://phabricator.kde.org/D6327 M +10 -1src/main.cpp https://commits.kde.org/ksshaskpass/4a6d3f932c3627e0f4d3f1a452ce1097c55f070b -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 353286] Openxchange calender not showing up in KOrganizer
https://bugs.kde.org/show_bug.cgi?id=353286 --- Comment #6 from Stephan Widor--- Problem still exists on Kubuntu 17.04, KDE 5.31.0, Akonadi 5.2.2, Kontact 5.2.3. Openxchange server is com4.strato.com. If you need more info, let me know. I will be happy to provide it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381604] New: Plasma (plasmashell), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=381604 Bug ID: 381604 Summary: Plasma (plasmashell), signal: Segmentation fault Product: plasmashell Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugrprt21...@online.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.6) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.72-18.12-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Setting the Digital Clock options. Pressed the "Apply" button. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2be5912900 (LWP 12588))] Thread 11 (Thread 0x7f2aeeff0700 (LWP 13060)): #0 0x7f2bdb4907b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2bdb44e969 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2bdb44f230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2bdb44f42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2bdf6ed32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2bdf69afdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2bdf4d5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2bdf4da9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2bde5d3744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2bdeddcaad in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f2afde0a700 (LWP 13044)): #0 0x7f2bdedd028d in read () at /lib64/libc.so.6 #1 0x7f2bdb48f670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2bdb44ee49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2bdb44f2a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2bdb44f42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2bdf6ed32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2bdf69afdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f2bdf4d5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f2be28079c8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f2bdf4da9e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f2bde5d3744 in start_thread () at /lib64/libpthread.so.0 #11 0x7f2bdeddcaad in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f2b1ac22700 (LWP 12729)): #0 0x7f2bdb4907b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2bdb44e837 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2bdb44f230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2bdb44f42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2bdf6ed32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2bdf69afdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2bdf4d5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2b1c0748f7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #8 0x7f2bdf4da9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f2bde5d3744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2bdeddcaad in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f2b25e0a700 (LWP 12698)): #0 0x7f2bdb44c709 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2bdb44e8fb in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2bdb44f230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2bdb44f42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2bdf6ed32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2bdf69afdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2bdf4d5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2be338e632 in () at /usr/lib64/libQt5Quick.so.5 #8 0x7f2bdf4da9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f2bde5d3744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2bdeddcaad in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f2b2f242700 (LWP 12691)): #0 0x7f2bde5d80bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2bba5dd533 in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f2bba5dcd57 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f2bde5d3744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2bdeddcaad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f2da700 (LWP 12690)): #0 0x7f2bde5d80bf in pthread_cond_wait@@GLIBC_2.3.2 () at
[kmymoney4] [Bug 381603] Unsorted list of online quotes
https://bugs.kde.org/show_bug.cgi?id=381603 Ralf Habackerchanged: What|Removed |Added Resolution|--- |FIXED Version Fixed In||4.8.1 Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kmy ||money/ffbc863c4f7873e450ebb ||dabbc97084ed99168e0 --- Comment #1 from Ralf Habacker --- Git commit ffbc863c4f7873e450ebbdabbc97084ed99168e0 by Ralf Habacker. Committed on 24/06/2017 at 11:05. Pushed by habacker into branch '4.8'. Fix 'Unsorted list of online quotes'. FIXED-IN:4.8.1 M +1-0kmymoney/dialogs/settings/ksettingsonlinequotes.cpp https://commits.kde.org/kmymoney/ffbc863c4f7873e450ebbdabbc97084ed99168e0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 381603] New: Unsorted list of online quotes
https://bugs.kde.org/show_bug.cgi?id=381603 Bug ID: 381603 Summary: Unsorted list of online quotes Product: kmymoney4 Version: 4.8.0 Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- In kmymoney settings the online quotes are listed in an unsorted order which makes finding a dedicated quote harder as required. It should be sorted in ascending order. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 381581] Expand category doesnt work after edit the parent category
https://bugs.kde.org/show_bug.cgi?id=381581 Bug 381581 depends on bug 317655, which changed state. Bug 317655 Summary: Various glitches with importing QIF from Quicken https://bugs.kde.org/show_bug.cgi?id=317655 What|Removed |Added Status|CLOSED |REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 317655] Various glitches with importing QIF from Quicken
https://bugs.kde.org/show_bug.cgi?id=317655 Ralf Habackerchanged: What|Removed |Added CC||ralf.habac...@freenet.de Blocks||381581 Resolution|FIXED |--- Status|CLOSED |REOPENED --- Comment #24 from Ralf Habacker --- The bug has been reopended because the related patch introduces a new bug, see blocked bug. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=381581 [Bug 381581] Expand category doesnt work after edit the parent category -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 381581] Expand category doesnt work after edit the parent category
https://bugs.kde.org/show_bug.cgi?id=381581 Ralf Habackerchanged: What|Removed |Added Depends on||317655 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=317655 [Bug 317655] Various glitches with importing QIF from Quicken -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 220536] Can't use external editor with non-UTF8 coding
https://bugs.kde.org/show_bug.cgi?id=220536 --- Comment #14 from Laurent Montel--- (In reply to Lothar from comment #13) > (In reply to Denis Kurz from comment #12) > > Hi Denis, > > it seems, that the recent version of kmail doesn't have the option "Use > external editor", so this bug isn't relevant any more. You can close it if > you want. > > And regarding the lack of manpower: I filed this bug report 7 1/2 years ago > for the recent version of kmail at that time and I've also attached a simple > fix. But this fix was never integrated. But this doesn't matter to me, > because I didn't use kmail any more. It was so full of bugs, slow and > unreliable, therefore I've switched to thunderbird after using kmail for > many years until KDE 3.5.10. I will try kmail again if it stops using the > bloated and buggy akonadi. > > Lothar I readded in 5.6.0 (future version) this feature as plugins Regards -- You are receiving this mail because: You are watching all bug changes.