[valgrind] [Bug 376869] unhandled syscall: 531
https://bugs.kde.org/show_bug.cgi?id=376869 Ivo Raisrchanged: What|Removed |Added CC||iv...@ivosh.net --- Comment #2 from Ivo Raisr --- That said, if the FreeBSD port is mature enough, its maintainers should initiate talks about integrating it upstream. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376661] When importing ~200,000 video files Digikam crashes in about 2-5 seconds of starting.
https://bugs.kde.org/show_bug.cgi?id=376661 Mario Frankchanged: What|Removed |Added CC||mario.fr...@uni-potsdam.de --- Comment #14 from Mario Frank --- (In reply to Poz from comment #13) > Are the thumbnails not readily available to do the fuzzy search on? I know > they are not the biggest but I think they are big enough, or if there is a > setting to render them a slightly higher resolution... That is how I > imagined it would work anyways, since the thumbnails would already be > generated, half the work is already done to fuzzy search videos... Hey Poz, Sadly, it is not this easy. The fuzzy search creates a signature from images. This does not hold for videos. Videos are quite more complex as the signature creation must be uniformly done for all videos. But if videos have black frames in the beginning, the search would lead to results which are, let's say, rubbish. The most stable way I see is to take the first frame from every video that is not plain, i.e. single-coloured. But this means we would have to generate images until we find the first appropriate frame. This would slow down the fingerprints generation significantly. A stable implementation is not trivial here. I will think about a way more closely over the weekend. Best, Mario -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 359786] No RW2 support on version 15.08.3
https://bugs.kde.org/show_bug.cgi?id=359786 Martin Kyralchanged: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #1 from Martin Kyral --- I think it is safe to close this bug now. libkdcraw-enabled version of kf5 is hanging around for quite some time. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376870] unhandled amd64-darwin syscall: unix:446
https://bugs.kde.org/show_bug.cgi?id=376870 Tom Hugheschanged: What|Removed |Added CC||t...@compton.nu Summary|The impossible happened on |unhandled amd64-darwin |Mavericks 10.9 |syscall: unix:446 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376869] unhandled syscall: 531
https://bugs.kde.org/show_bug.cgi?id=376869 Tom Hugheschanged: What|Removed |Added CC||t...@compton.nu Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Tom Hughes --- The FreeBSD port of valgrind is a separate project that is not part of the upstream code base and is not maintained by us. You will need to report this to the people that maintain the FreeBSD port. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 X.F. Dchanged: What|Removed |Added CC||co...@outlook.com --- Comment #40 from X.F. D --- *** Bug 376569 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 376569] input focus randomly toggle between splited terminals
https://bugs.kde.org/show_bug.cgi?id=376569 X.F. Dchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from X.F. D --- *** This bug has been marked as a duplicate of bug 356853 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 376871] New: KAlarm Crash
https://bugs.kde.org/show_bug.cgi?id=376871 Bug ID: 376871 Summary: KAlarm Crash Product: kalarm Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: djar...@kde.org Reporter: billrori...@gmail.com Target Milestone: --- Application: kalarm (2.11.13-5) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.4.0-64-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: I was trying to select the sound for an alarm, and when i clicked the button to open the file browser window, the application crashed. - Custom settings of the application: it is possible that the option to autoplay the sound file on mouse hover has something to do with it. I do not have solid proof of this, it is just a hunch. was going to try and disable it, but file browser window does not stay open long enough for me to click the radio button. The crash can be reproduced every time. -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7a128569c0 (LWP 13209))] Thread 4 (Thread 0x7f79d8182700 (LWP 13225)): [KCrash Handler] #6 0x7f79f27924cb in vorbis_info_clear () from /usr/lib/x86_64-linux-gnu/libvorbis.so.0 #7 0x7f79cce365f4 in ?? () from /usr/lib/vlc/plugins/demux/libogg_plugin.so #8 0x7f79cce3669a in ?? () from /usr/lib/vlc/plugins/demux/libogg_plugin.so #9 0x7f79cce367b0 in ?? () from /usr/lib/vlc/plugins/demux/libogg_plugin.so #10 0x7f79d375cc60 in vlc_module_unload () from /usr/lib/libvlccore.so.8 #11 0x7f79d37112f2 in ?? () from /usr/lib/libvlccore.so.8 #12 0x7f79d3720436 in ?? () from /usr/lib/libvlccore.so.8 #13 0x7f79d37273cd in ?? () from /usr/lib/libvlccore.so.8 #14 0x7f7a084da6ba in start_thread (arg=0x7f79d8182700) at pthread_create.c:333 #15 0x7f7a0d8e182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f79e1501700 (LWP 13212)): #0 0x7f7a0d8d169d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7a061f86f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7a061b4e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a061b5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7a061b549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7a0e41a75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7a0e3c50ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7a0e1f4f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f7a0e1f9b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f7a084da6ba in start_thread (arg=0x7f79e1501700) at pthread_create.c:333 #10 0x7f7a0d8e182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f79e1d02700 (LWP 13211)): #0 0x7f7a0e419eaf in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f7a061b491d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7a061b52bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a061b549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7a0e41a75b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7a0e3c50ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7a0e1f4f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7a0eb10735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f7a0e1f9b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f7a084da6ba in start_thread (arg=0x7f79e1d02700) at pthread_create.c:333 #10 0x7f7a0d8e182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f7a128569c0 (LWP 13209)): #0 0x7f7a084db98d in pthread_join (threadid=140161293231872, thread_return=0x0) at pthread_join.c:90 #1 0x7f79d372504f in input_Close () from /usr/lib/libvlccore.so.8 #2 0x7f79d34c6460 in libvlc_media_player_release () from /usr/lib/libvlc.so.5 #3 0x7f79d3a0c11b in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #4 0x7f7a0e3f0663 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7a0e3f9814 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79d3a06989 in ?? () from
[plasmashell] [Bug 376826] assign windows to Activities in task manager unriable
https://bugs.kde.org/show_bug.cgi?id=376826 --- Comment #2 from David Edmundson--- Confirmed, checking any menu item isn't working. menuItem.clicked.connect((function(activityId) var checked = menuItem.checked; is always false even though we clearly just checked the damn thing. I have no idea where that puts the real bug. Debug in p-f shows the QAction is unchecked at the time of calling menuItem.checked Virtual desktops doesn't have that problem because it always knows clicking == activate this index, activities are more complex because of the cardinality. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376870] New: The impossible happened on Mavericks 10.9
https://bugs.kde.org/show_bug.cgi?id=376870 Bug ID: 376870 Summary: The impossible happened on Mavericks 10.9 Product: valgrind Version: 3.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: hamish-...@risingsoftware.com Target Milestone: --- I am trying to run my app in memcheck on Mavericks/10.9. (It is actually running in a 10.9 virtual machine in Parallels 11, because the host is running Sierra/10.12 which is not supported yet.) I got quite a few messages about an unhandled syscall: --10283-- WARNING: unhandled amd64-darwin syscall: unix:446 --10283-- You may be able to write your own handler. --10283-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --10283-- Nevertheless we consider this a bug. Please report --10283-- it at http://valgrind.org/support/bug_reports.html. At the point when I expected my program to crash, I got: eq_SyscallStatus: {78 0 43} {78 0 40} valgrind: m_syswrap/syswrap-main.c:438 (Bool eq_SyscallStatus(UInt, SyscallStatus *, SyscallStatus *)): the 'impossible' happened. host stacktrace: ==10283==at 0x238042521: ??? ==10283==by 0x238042932: ??? ==10283==by 0x238042915: ??? ==10283==by 0x2380C13FE: ??? ==10283==by 0x2380C0989: ??? ==10283==by 0x2380BEDDB: ??? ==10283==by 0x2380BCCCD: ??? ==10283==by 0x2380CE1CC: ??? sched status: running_tid=1 and a stack trace. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372779] valgrind will hang
https://bugs.kde.org/show_bug.cgi?id=372779 Hamish Moffattchanged: What|Removed |Added CC||hamish-kde@risingsoftware.c ||om --- Comment #2 from Hamish Moffatt --- I am also seeing this when trying to run a large application in valgrind 3.12 on OS X 10.11. I got a few UNKNOWN mach_msg messages on startup, and then my program hung with valgrind using 100% CPU. I waited over 1 hour and it never launched. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla
https://bugs.kde.org/show_bug.cgi?id=375053 --- Comment #5 from David Edmundson--- Why would that break control+C actions? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376842] Matlab kills KDE
https://bugs.kde.org/show_bug.cgi?id=376842 David Edmundsonchanged: What|Removed |Added Assignee|k...@davidedmundson.co.uk|h...@kde.org Component|general |Task Manager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376866] Can't write anything into plasma dialogues, can into KDE apps.
https://bugs.kde.org/show_bug.cgi?id=376866 --- Comment #3 from David Edmundson--- can you include the output of running "env" in a terminal please. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376869] New: unhandled syscall: 531
https://bugs.kde.org/show_bug.cgi?id=376869 Bug ID: 376869 Summary: unhandled syscall: 531 Product: valgrind Version: 3.10.0 Platform: Other OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: benkasminbull...@gmail.com Target Milestone: --- Version information is as follows: ==9740== Memcheck, a memory error detector ==9740== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==9740== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==9740== Command: /usr/home/ben/projects/kanjivg/t/../www/memory.cgi -q c=6BC5 ==9740== Valgrind produced the following: --9740-- WARNING: unhandled syscall: 531 --9740-- You may be able to write your own handler. --9740-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --9740-- Nevertheless we consider this a bug. Please report --9740-- it at http://valgrind.org/support/bug_reports.html. My OS is like this: FreeBSD mikan 10.3-RELEASE-p11 FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:47:18 UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 According to syscall.h, call 531 is #define SYS_posix_fadvise 531 My package for valgrind is up to date: # pkg upgrade valgrind Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking integrity... done (0 conflicting) Your packages are up to date. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376868] New: Crash Plasma
https://bugs.kde.org/show_bug.cgi?id=376868 Bug ID: 376868 Summary: Crash Plasma Product: plasmashell Version: 5.9.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: federico127...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.9-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - Unusual behavior I noticed: plasma has problem with 2 monitor. I use Nvidia GCard and VGA port The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fad64e42800 (LWP 1247))] Thread 18 (Thread 0x7fac6cd0f700 (LWP 4384)): #0 0x7fad5e5024ed in read () at /usr/lib/libc.so.6 #1 0x7fad514cff51 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7fad51b6030e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7fad51b60d80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fad51b60e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fad51b6ee29 in () at /usr/lib/libpulse.so.0 #6 0x7fad514fefe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7fad5dac5454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fad5e50f7df in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fac6d610700 (LWP 3795)): #0 0x7fad514bc680 in pa_iochannel_is_readable@plt () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #1 0x7fad514ee617 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7fad514ee989 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #3 0x7fad514ef20a in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #4 0x7fad51b6099c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0 #5 0x7fad51b60d9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #6 0x7fad51b60e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #7 0x7fad51b6ee29 in () at /usr/lib/libpulse.so.0 #8 0x7fad514fefe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #9 0x7fad5dac5454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fad5e50f7df in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fac81f2c700 (LWP 3794)): #0 0x7fad5e50648d in poll () at /usr/lib/libc.so.6 #1 0x7fad59324786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fad5932489c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fad5ee2a06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fad5edd389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fad5ebf5a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fad61d2f025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fad5ebfa6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fad5dac5454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fad5e50f7df in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fac6f7fe700 (LWP 1274)): #0 0x7fad5dacb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fad5ebfb58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7faca897d1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7faca89819d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7faca897c263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7faca8981a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7faca897c263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7faca897f249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fad5ebfa6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fad5dac5454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fad5e50f7df in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fac6700 (LWP 1273)): #0 0x7fad5dacb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fad5ebfb58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7faca897d1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7faca89819d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7faca897c263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
[digikam] [Bug 376661] When importing ~200,000 video files Digikam crashes in about 2-5 seconds of starting.
https://bugs.kde.org/show_bug.cgi?id=376661 --- Comment #13 from Poz--- Are the thumbnails not readily available to do the fuzzy search on? I know they are not the biggest but I think they are big enough, or if there is a setting to render them a slightly higher resolution... That is how I imagined it would work anyways, since the thumbnails would already be generated, half the work is already done to fuzzy search videos... -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 376867] New: sftp connect issue "Failed to resolve hostname = (Name or service not known)"
https://bugs.kde.org/show_bug.cgi?id=376867 Bug ID: 376867 Summary: sftp connect issue "Failed to resolve hostname = (Name or service not known)" Product: krusader Version: 2.4.0-beta3 "Single Step" Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: net-connection Assignee: m...@fork.pl Reporter: vadims.zen...@gmail.com Target Milestone: --- cat /etc/issue Ubuntu 16.04.2 LTS \n \l uname -r 4.9.0-040900-generic konsole --version QCoreApplication::arguments: Please instantiate the QApplication object first Qt: 5.5.1 KDE Frameworks: 5.18.0 Konsole: 15.12.3 krusader --version Qt: 4.8.7 KDE Development Platform: 4.14.16 Krusader - ROOT PRIVILEGES: 2.4.0-beta3 "Single Step" dolphin --version QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' dolphin 15.12.3 My ~/.ssh/config ControlPath ~/.ssh/tmp/%h_%p_%r Host * ServerAliveInterval 240 KeepAlive = yes Host = www.mydomain.science 1.2.3.4 HostName = 1.2.3.4 User =myname KeepAlive =yes Port = (4 symbols number) IdentityFile = ~/.ssh/mykey.priv.key I could ping www.mydomain.science . I could ssh by command: ssh www.mydomain.science without any issues. I could not open sftp ether from krusader or dolphin. Connection string: sftp://myname@www.mydomain.science: Error message: Failed to resolve hostname = (Name or service not known) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374142] Contiguous selection tool not always works
https://bugs.kde.org/show_bug.cgi?id=374142 reesebudder...@gmail.com changed: What|Removed |Added CC||reesebudder...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 344617] “Show Filter bar” and “Search” should be converted to toggle buttons
https://bugs.kde.org/show_bug.cgi?id=344617 Don Nguyenchanged: What|Removed |Added CC||don78color...@gmail.com --- Comment #2 from Don Nguyen --- (In reply to Emmanuel Pescosta from comment #1) > Thanks for the feature request! > I agree with you that filter and find should be toggle buttons as well. > > There is already an old patch for the "find" button: > https://git.reviewboard.kde.org/r/107016/ > > Added two tasks: > https://todo.kde.org/?controller=task=show_id=966 > https://todo.kde.org/?controller=task=show_id=967 The filter toggle patch has been committed. I will work on making find a toggle. The patch above seems to not show any diffs anymore. Is todo.kde.org dead? I can't access it right now. -- You are receiving this mail because: You are watching all bug changes.
[Purpose] [Bug 375269] Widget to share files make whole desktop crash
https://bugs.kde.org/show_bug.cgi?id=375269 --- Comment #1 from Aleix Pol--- Git commit 4f5c426fd94392bc4b213c74193beadd9f1b by Aleix Pol. Committed on 23/02/2017 at 23:59. Pushed by apol into branch 'master'. Sanitize use of QObject* in ProcessJob M +1-2src/externalprocess/processjob.cpp M +4-3src/externalprocess/processjob.h https://commits.kde.org/purpose/4f5c426fd94392bc4b213c74193beadd9f1b -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 175414] Icons don't show that a folder is inaccessible
https://bugs.kde.org/show_bug.cgi?id=175414 Don Nguyenchanged: What|Removed |Added CC||don78color...@gmail.com --- Comment #8 from Don Nguyen --- Dolphin 17.03.70 shows a lock in the corner of the folder if a user does not have read access. It will still show a normal folder if the user does not have execute access(cd into it), and write access. Does this current behavior suffice or do we want more specialized behavior(indicating no execute/write access)? I am suggesting that the lock should appear in the case of both no read access, and no execute access because they essential mean you can't see the contents of the folder. No write access doesn't seem that important. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms
https://bugs.kde.org/show_bug.cgi?id=370028 Ivo Raisrchanged: What|Removed |Added Attachment #104189|0 |1 is obsolete|| --- Comment #20 from Ivo Raisr --- Created attachment 104201 --> https://bugs.kde.org/attachment.cgi?id=104201=edit slightly modified patch 1/4 Patch 1/4 slightly modified to fix formatting and with added NEWS entry. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 376864] Motherboard and CPU sensors not seen after upgrade
https://bugs.kde.org/show_bug.cgi?id=376864 --- Comment #2 from K.J. Petrie--- $ uname -r 4.9.8-pclos1 $ cat /proc/stat cpu 73342 75 54660 5070675 9923 4268 3875 0 0 0 cpu0 11129 1 7364 632527 418 327 280 0 0 0 cpu1 11769 32 6561 626557 6201 644 220 0 0 0 cpu2 6724 5 5912 638511 727 397 103 0 0 0 cpu3 8424 6 6533 635593 737 475 189 0 0 0 cpu4 10562 12 7898 632043 568 653 97 0 0 0 cpu5 9823 4 7259 633409 527 633 164 0 0 0 cpu6 6834 11 6155 638454 364 403 84 0 0 0 cpu7 8074 1 6974 633578 380 734 2735 0 0 0 intr 8019356 64 6675 0 0 0 0 0 0 415209 0 0 0 0 0 0 0 1301 2 86772 38048 0 0 0 0 0 0 0 19216 129 0 112770 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ctxt 12680671 btime 1487887051 processes 36475 procs_running 1 procs_blocked 0 softirq 3234466 11 1429155 1092 20692 38525 0 145694 606603 0 992694 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371822] Dolphin should not toggle the terminal panel if Konsole is not installed
https://bugs.kde.org/show_bug.cgi?id=371822 Don Nguyenchanged: What|Removed |Added CC||don78color...@gmail.com --- Comment #2 from Don Nguyen --- > But I agree that Dolphin should not show an empty dock widget (upon pressing > F4) if Konsole is not installed (thus I'm changing the title). I'd like to present some options related to the Terminal Panel when Konsole is not installed and give you my analysis. 1) Do not show the Terminal Panel option in the menu when Konsole is not installed. 2) Disable(gray out) the Terminal Panel option in the menu when Konsole is not installed. 3) Pop up an information dialog to inform the user that Konsole is not installed when the user tries to invoke the Terminal Panel. 4) Display a message inside the Terminal Panel indicating that Konsole is not installed when the user invokes the Terminal Panel. Option 1 hides the fact that we have this feature if Konsole is not installed. Option 2 shows that we have such a feature but does not tell the user why it's disabled - the user will have to search for why this is disabled. Option 3 gives the user information about this feature and why it's missing and how to enable it, but it seems a bit intrusive to me. My preferred choice is option 4. It mimics normal behavior except that instead of having a working Terminal Panel, it lets the user know why the feature is missing and how to enable it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376866] Can't write anything into plasma dialogues, can into KDE apps.
https://bugs.kde.org/show_bug.cgi?id=376866 --- Comment #2 from Tom Kijas--- When I want to type password, I have to type it in kate for example and then copypaste into KDE's dialog. But I have to paste it using mouse, alt+v doesn't work, obviously. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376866] Can't write anything into plasma dialogues, can into KDE apps.
https://bugs.kde.org/show_bug.cgi?id=376866 Tom Kijaschanged: What|Removed |Added CC||t.ki...@gmail.com --- Comment #1 from Tom Kijas --- To clarify, I can write into dolphin, firefox etc. I cannot write password into wireless widget in KDE5, I can't write password when KDE asks for password of admin and I can write only first letter in kickoff (other letters makes plasma freeze for a minutes). I also can'T writer into alf+f2 launcher (as always, nothing happens). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376866] New: Can't write anything into plasma dialogues, can into KDE apps.
https://bugs.kde.org/show_bug.cgi?id=376866 Bug ID: 376866 Summary: Can't write anything into plasma dialogues, can into KDE apps. Product: plasmashell Version: 5.8.6 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: t.ki...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Can't write anything into plasma dialogues, while I can write into KDE apps, gnome apps etc. Same behaviour in Ubuntu 16.04 and KDE NEON LTS. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 376865] New: Loading Cursor Captured in Rectangular Region if Launched Directly
https://bugs.kde.org/show_bug.cgi?id=376865 Bug ID: 376865 Summary: Loading Cursor Captured in Rectangular Region if Launched Directly Product: Spectacle Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: spammonster2...@hotmail.com Target Milestone: --- Created attachment 104200 --> https://bugs.kde.org/attachment.cgi?id=104200=edit Spectacle Loading Cursor Icon Captured in Rectangular Region neon User Edition Intel Haswell-ULT Integrated Graphics Also reproduced in VirtualBox 5.1 live session. To reproduce: 1. In application launcher, type "Capture" 2. Select "Capture Rectangular Region - Spectacle" option Always reproducible. Expected: Only the mouse cursor gets included in the selection screen capture. Actual: See screenshot - the Spectacle cursor icon gets caught in the window selection along with the mouse cursor. This only occurs when the rectangular capture mode is selected directly from the application launcher; selecting rectangular region from the Spectacle UI works as expected. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 376864] Motherboard and CPU sensors not seen after upgrade
https://bugs.kde.org/show_bug.cgi?id=376864 --- Comment #1 from Christoph Feck--- The only change in ksysguardd in 5.8.6 is the crash fix for bug 376537, which affects parsing of the output of /proc/stat Please add a comment with Linux version (uname -r), and output of /proc/stat -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 376864] New: Motherboard and CPU sensors not seen after upgrade
https://bugs.kde.org/show_bug.cgi?id=376864 Bug ID: 376864 Summary: Motherboard and CPU sensors not seen after upgrade Product: ksysguard Version: 5.8.6 Platform: PCLinuxOS OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ksysguardd Assignee: ksysguard-b...@kde.org Reporter: kde.b...@instabook.com Target Milestone: --- In ksysguard 5.8.5 numerous CPU and Motherboard sensors are visible to the thermal monitoring widget. In version 5.8.6 they are not. Only the GPU and HDD/SSD temperatures are visible. Function can be restored by logging out, copying the previous version of /usr/bin/ksysguardd over the newer file and logging back in. Hardware: AMD FX 8350 CPU GA-970A-DS3P (Rev 2.0) MB Asus EN210 (Nvidia) GPU Maxtor STM325031 HDD 3 SSDs -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 374687] Allow per display Screen Scalinng (individually)
https://bugs.kde.org/show_bug.cgi?id=374687 Dustin Raimondichanged: What|Removed |Added CC||raimondi1...@gmail.com --- Comment #3 from Dustin Raimondi --- Is there a workaround for this in Wayland? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374461] Cannot right-click with a Wacom Tablet
https://bugs.kde.org/show_bug.cgi?id=374461 --- Comment #11 from silva--- Just to check if by any chance you encountered the same bug after installing Sierra. Tried Krita 3.1.2 and the issue still persists. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376863] New: First letter is lost when replacing search bar text
https://bugs.kde.org/show_bug.cgi?id=376863 Bug ID: 376863 Summary: First letter is lost when replacing search bar text Product: Discover Version: 5.9.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: aro...@archlinux.org Target Milestone: --- - Type something in the search bar - Select the text - Type something else to replace the selected text (without deleting it first) The first letter of the new search term is lost. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368999] Folders ending with a space in their name are not retrieved from Folder View
https://bugs.kde.org/show_bug.cgi?id=368999 David Faurechanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from David Faure --- The fix is in (for Qt 5.8.1 if there's one, otherwise 5.9) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376530] Map jumps to 0/0 position when using "Zoom into a group"
https://bugs.kde.org/show_bug.cgi?id=376530 --- Comment #3 from Wolfgang Scheffner--- Yes, I can confirm that. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 --- Comment #50 from Tsu Jan--- Recently I started to prepare Kvantum for wayland and found something that might be relevant to Qtcurve too: Although setting WA_TranslucentBackground works fine on X11 (with some precautions), it causes a lot of artifacts on wayland. Instead, on wayland, the alpha channel should be forced on the native handle (with or without private headers). I don't know the reason yet but, at least for now, wayland isn't happy with WA_TranslucentBackground. The problem discussed here still exists with KFileDialog menus - and only with them -- on wayland but, fortunately, there's no freeze anymore; the items of those menus can't be selected when menu translucency is enabled by forcing alpha channel. My tests are done under plasma-wayland-session-5.9.2 and also Weston (both on X11 and with its wayland session) on Linux. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376862] New: Colour scheme editor: little layout bug
https://bugs.kde.org/show_bug.cgi?id=376862 Bug ID: 376862 Summary: Colour scheme editor: little layout bug Product: systemsettings Version: 5.8.6 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_colors Assignee: mwoehlke.fl...@gmail.com Reporter: war...@gmx.de CC: jpwhit...@kde.org Target Milestone: --- Go to systemsettings, select Colours, click on Edit Scheme and select the Colours tab. The preview widget at the top of that dialog expands when changing the window size, although its content does not require this. This also takes away useful space from the colour list at the bottom. I first noticed it in Plasma 5.8, but 5.9 is also affected. In the colour scheme selection dialog the same preview widget uses a fixed size (well nearly, it squishes a little when the window is made small). → Change the vertical size policy of the the QStackedWidgets in kcms/colors/scmeditorcolors.ui from Preferred to Fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376861] New: a process still running after quitting
https://bugs.kde.org/show_bug.cgi?id=376861 Bug ID: 376861 Summary: a process still running after quitting Product: kdenlive Version: 16.12.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jean-paul.que...@wanadoo.fr Target Milestone: --- A process (118400KB) still run after quitting. We can kill it only with the task manager. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376860] New: Add Slideshow Clip
https://bugs.kde.org/show_bug.cgi?id=376860 Bug ID: 376860 Summary: Add Slideshow Clip Product: kdenlive Version: 16.12.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jean-paul.que...@wanadoo.fr Target Milestone: --- Impossible to add Slideshow Clip. KDEnlive return "Clip invalid, will be remove from the project". No problem if we import the file (extension .kendenlive) from Linux. (Windows 7, Ram : 8Go, 85 picture .jpg, 1920 x 1080 px, 60 ko/picture) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376661] When importing ~200,000 video files Digikam crashes in about 2-5 seconds of starting.
https://bugs.kde.org/show_bug.cgi?id=376661 --- Comment #12 from caulier.gil...@gmail.com --- >Also is it possible to do the FUZZY search on the thumb nails to file >>potential duplicates? This is my real intent. I want to cut that 200,000 >>videos down to 100,000. >If not, is this a future feature? Can it be one? High demand I think. Poz, The Fuzzy Search work only with Still Image currently. To see a similar function for video, this will need an algorithm to create a fingerprint of the first frame of video, in goal to compare later with DB. This is how the fuzzy tool work actually. A simplified wavelets matrix is computed with still image. We compare matrix together to found similarities. For video we need a new matrix with the spacial information of video. Not impossible but complex to write and test. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376858] [Regression] Execution prompt shown for desktop files in desktop subfolders
https://bugs.kde.org/show_bug.cgi?id=376858 --- Comment #1 from Kai Uwe Broulik--- Well, that'll introduce a vunerability when you extract an archive onto your desktop which Ark by default puts into a subdirectory. -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 376318] Regression: passwords no longer remembered, asks every time I open a shell
https://bugs.kde.org/show_bug.cgi?id=376318 --- Comment #7 from Christoph Feck--- Your distribution might also have configured Qt to redirect any logging to the syslog daemon instead of to the Konsole. In that case, please ask in a forum of your distribution how to search for ksshaskpass messages in the system wide log files. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376859] Tag Shortcut Key Combination Conflict Dialog Always Appears
https://bugs.kde.org/show_bug.cgi?id=376859 hardy.pub...@gmail.com changed: What|Removed |Added OS|Linux |MS Windows Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376859] New: Tag Shortcut Key Combination Conflict Dialog Always Appears
https://bugs.kde.org/show_bug.cgi?id=376859 Bug ID: 376859 Summary: Tag Shortcut Key Combination Conflict Dialog Always Appears Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tags Assignee: digikam-de...@kde.org Reporter: hardy.pub...@gmail.com Target Milestone: --- Created attachment 104198 --> https://bugs.kde.org/attachment.cgi?id=104198=edit EditTag In Edit Tag -> Shortcut, when Input... appears and I press any key combination, a conflict warning dialog always appears regardless of whether the key combination currently exists or not. In addition, for an existing assigned key combination, it is not displayed in the dialog. See the attached picture. -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 376318] Regression: passwords no longer remembered, asks every time I open a shell
https://bugs.kde.org/show_bug.cgi?id=376318 --- Comment #6 from Christoph Feck--- ksshaskpass uses the new Qt logging. To get the debug output, please add ksshaskpass.*=true to your QT_LOGGING_RULES as described at http://doc.qt.io/qt-5/qloggingcategory.html Either put it into your qtlogging.ini file or set the QT_LOGGING_RULES environment variable. It should then display the failing prompt it needs to recognize. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #64 from caulier.gil...@gmail.com --- Hi Jens, Not for the moment. I'm not at home without all my VM. Please weait next week. We need also to fix some problem with icon overlays before. As well it's not suitbale if some thumbnails options are disabed. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376605] no kwin window decoration after upgrade to 5.9 user
https://bugs.kde.org/show_bug.cgi?id=376605 apachechanged: What|Removed |Added CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376605] no kwin window decoration after upgrade to 5.9 user
https://bugs.kde.org/show_bug.cgi?id=376605 --- Comment #1 from apache--- I purged neon user and installed dev stable and added new user account to be sure that it is not about settings. But the bug still is present. Maybe it has something to do with nvidia in relation to kwin? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376858] New: [Regression] Execution prompt shown for desktop files in desktop subfolders
https://bugs.kde.org/show_bug.cgi?id=376858 Bug ID: 376858 Summary: [Regression] Execution prompt shown for desktop files in desktop subfolders Product: plasmashell Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: k...@privat.broulik.de Reporter: fab...@ritter-vogt.de CC: fa...@kde.org, h...@kde.org, plasma-b...@kde.org Target Milestone: 1.0 While https://phabricator.kde.org/D4534 "[Folder View] Don't show script execution prompt on desktop:/" fixed the prompt for executable .desktop files on the desktop directly, it breaks again when those files are in a subfolder on the desktop and accessed through the cascading view. Maybe the check should be successful for all paths starting from desktop:/ without ".."? This probably needs some discussion first... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376855] Man pages loading error
https://bugs.kde.org/show_bug.cgi?id=376855 Christian Schlaszachanged: What|Removed |Added CC||christian.schla...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376857] Refactor: "Create separate definition" not working as intended (?)
https://bugs.kde.org/show_bug.cgi?id=376857 Christian Schlaszachanged: What|Removed |Added CC||christian.schla...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376857] New: Refactor: "Create separate definition" not working as intended (?)
https://bugs.kde.org/show_bug.cgi?id=376857 Bug ID: 376857 Summary: Refactor: "Create separate definition" not working as intended (?) Product: kdevelop Version: 5.0.3 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: christian.schla...@gmail.com Target Milestone: --- Created attachment 104197 --> https://bugs.kde.org/attachment.cgi?id=104197=edit Error: No source file available When opening the context menu on a class function in the source file, the item "Refactor" -> "Create separate definition" is available. After clicking on it, an error message appears (see attachment). There cannot be found a source file, because the source file is already opened. In the header file, this context menu does not appear at all. Here it would be useful to create a definition for a selected declaration. Probably the available context menu items of header and sources for "Refactor" have to be exchanged. -- You are receiving this mail because: You are watching all bug changes.
[kholidays] [Bug 359708] Updated holiday file for Ukraine
https://bugs.kde.org/show_bug.cgi?id=359708 --- Comment #9 from 38dosb+99yi2ktucs...@guerrillamailblock.com --- Created attachment 104196 --> https://bugs.kde.org/attachment.cgi?id=104196=edit A holiday file with conditional expressions Sorry for my prolonged absence. I've attached a holiday file with the conditionals. It has been tested against KDE 4 only. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368312] Movement on child layer of group layer with transparency mask is not reflected
https://bugs.kde.org/show_bug.cgi?id=368312 Nicholas LaPointechanged: What|Removed |Added CC||mangate...@gmail.com --- Comment #3 from Nicholas LaPointe --- *** Bug 376774 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376774] Translating layer nested in a group layer only refresh if transparency mask is disabled
https://bugs.kde.org/show_bug.cgi?id=376774 Nicholas LaPointechanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||nicholaslapoin...@gmail.com --- Comment #1 from Nicholas LaPointe --- *** This bug has been marked as a duplicate of bug 368312 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376854] patchreview/purpose integration: result dialog doesn't provide review URL
https://bugs.kde.org/show_bug.cgi?id=376854 --- Comment #1 from RJVB--- The signal in question is Purpose::Menu::finished where is that one emitted? I suppose that should be done by `Purpose::Menu`, but I cannot find where in the Purpose code... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 332624] NFS support
https://bugs.kde.org/show_bug.cgi?id=332624 Bug 332624 depends on bug 275261, which changed state. Bug 275261 Summary: Akonadi on NFS mounted home directories is very fragile https://bugs.kde.org/show_bug.cgi?id=275261 What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 275261] Akonadi on NFS mounted home directories is very fragile
https://bugs.kde.org/show_bug.cgi?id=275261 Daniel Vrátilchanged: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- Ever confirmed|0 |1 --- Comment #14 from Daniel Vrátil --- Reopening, NFS support is still rather fragile :) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 190301] Collection and Item ID auto-increment broken
https://bugs.kde.org/show_bug.cgi?id=190301 Daniel Vrátilchanged: What|Removed |Added Resolution|UNMAINTAINED|UPSTREAM Status|RESOLVED|CLOSED --- Comment #6 from Daniel Vrátil --- The issue is still relevant, although things seem to be moving in MySQL land at least to resolve the issue. Until now I don't think we've seen any issues related to this, so I'll keep it closed. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Christoph Feckchanged: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 376856] New: Breeze dark missing icons on plasma menu
https://bugs.kde.org/show_bug.cgi?id=376856 Bug ID: 376856 Summary: Breeze dark missing icons on plasma menu Product: Breeze Version: 5.9.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: a...@piggz.co.uk CC: kain...@gmail.com Target Milestone: --- Created attachment 104195 --> https://bugs.kde.org/attachment.cgi?id=104195=edit Screenshot Breeze-dark appears to be missing the history and leave icons. These icons do not show up in the plasma menu using the breeze-dark theme, but do display with the regular theme. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376852] Akonadi server crash
https://bugs.kde.org/show_bug.cgi?id=376852 Christoph Feckchanged: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376530] Map jumps to 0/0 position when using "Zoom into a group"
https://bugs.kde.org/show_bug.cgi?id=376530 Maik Qualmannchanged: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Wolfgang, can you confirm that only the first mouse click in the group will fail. It works after the second mouse click. Looks for an issue in Marble, let's see if I find a workaround. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376855] New: Man pages loading error
https://bugs.kde.org/show_bug.cgi?id=376855 Bug ID: 376855 Summary: Man pages loading error Product: kdevelop Version: 5.0.3 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: documentation viewer Assignee: kdevelop-bugs-n...@kde.org Reporter: christian.schla...@gmail.com Target Milestone: --- Created attachment 104194 --> https://bugs.kde.org/attachment.cgi?id=104194=edit Man pages loading error in GUI Man pages can not be viewed at all. This happens on (K)Ubuntu 16.04.2 Systems (tested with locales English, German) in the AppImage versions 5.0.3 (stable) and 5.0.8 (unstable). The console output says: couldn't create slave: "Ein-/Ausgabemodul für „man“ nicht auffindbar." trying to load "/tmp/.mount_Y7M9p4/usr/lib/qt5/plugins/kf5/kio/file.so" from "/tmp/.mount_Y7M9p4/usr/lib/qt5/plugins/kf5/kio/file.so" -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 375104] Crash during shutdown: ASSERT: "mDev" in datastream_p_p.h:89
https://bugs.kde.org/show_bug.cgi?id=375104 Daniel Vrátilchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátilchanged: What|Removed |Added CC||kde...@posteo.de --- Comment #28 from Daniel Vrátil --- *** Bug 375104 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátilchanged: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #27 from Daniel Vrátil --- *** Bug 375450 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 375450] akonadiserver crashes on system shudown
https://bugs.kde.org/show_bug.cgi?id=375450 Daniel Vrátilchanged: What|Removed |Added CC||dvra...@kde.org Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 --- Comment #26 from Daniel Vrátil--- *** Bug 375558 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 375558] Akonadiserver crashes on restart
https://bugs.kde.org/show_bug.cgi?id=375558 Daniel Vrátilchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátilchanged: What|Removed |Added CC||kosse...@kde.org --- Comment #25 from Daniel Vrátil --- *** Bug 375714 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 375714] Crash on akonadictl stop (while filteragent was hanging)
https://bugs.kde.org/show_bug.cgi?id=375714 Daniel Vrátilchanged: What|Removed |Added CC||dvra...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376852] Akonadi server crash
https://bugs.kde.org/show_bug.cgi?id=376852 Daniel Vrátilchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- *** This bug has been marked as a duplicate of bug 374734 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátilchanged: What|Removed |Added CC||a...@cryptomilk.org --- Comment #24 from Daniel Vrátil --- *** Bug 376852 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Daniel Vrátilchanged: What|Removed |Added Severity|critical|normal CC||dvra...@kde.org Version Fixed In||5.4.3 Latest Commit||https://commits.kde.org/ako ||nadi/5219f770b998aad16a3d51 ||bbd4f4c7ceb8b143c9 --- Comment #23 from Daniel Vrátil --- The crash itself has been fixed by commit https://commits.kde.org/akonadi/5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 which will be in Akonadi 5.4.3 (KDE Applications 16.12.3) in March. The patch fixes the crash itself, but does not address the underlying problem. I'll keep this opened until the underlying problem is resolved. --- Notes for future me: The root cause is the nested QEventLoop in ItemRetriever::exec(). When Connection is terminated (by server shutdown or connection loss on socket) while the nested QEventLoop in ItemRetriever is running, Connection::quit() will be invoked from the nested loop, destroying certain resources (socket, datastore). This then leads to various crashes once the nested event loop ends and execution within ItemRetriever::exec() continues. I don't think it's possible to prevent nested event loop from executing metacalls on Connection, after all the main reason for using QEventLoop in ItemRetriever was to make it more interactive and interruptable. Connection::quit() cannot directly terminate the nested QEventLoop, because it has been invoked from it. It could however use delay invocation to quit the loop and return early without actually quiting and destroying the thread. The thread would quit once the excecution would return from the Handler back to Connection::slotNewData(). Connection::quit() could probably set a flag or something. However it's not clear how Connection::quit() should detect where it's invoked from and whether it's a nested QEL or not, and how it should interact with it. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376434] release kdesvn 2.0.0 on neon ppa
https://bugs.kde.org/show_bug.cgi?id=376434 --- Comment #2 from Jonathan Riddell--- http://build.neon.kde.org/job/xenial_unstable_forks_kdesvn/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376815] Restore from Trash works incorrectly
https://bugs.kde.org/show_bug.cgi?id=376815 --- Comment #3 from Maik Qualmann--- Git commit 38e1582672ddd32bef4f0dbc3750654fdd128b07 by Maik Qualmann. Committed on 23/02/2017 at 18:50. Pushed by mqualmann into branch 'master'. use QUuid to generate random string for filename M +4-8libs/dtrash/dtrash.cpp https://commits.kde.org/digikam/38e1582672ddd32bef4f0dbc3750654fdd128b07 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 376654] Crashes on restart
https://bugs.kde.org/show_bug.cgi?id=376654 --- Comment #3 from Christoph Feck--- On 23.02.2017 19:18, eric.v...@msg4.us wrote: > Hi Christophe, > I'm sorry that the bug report system is unable to find a bug that > appears every other day and reported with the same title from the same > person > > That's why I HAVE to create a new one each time. > > I can feel your frustration, please consider mine. > > It's also unfortunate that KDE is not suggesting Kmail/Kontact update, > even though I zypper patch AND Zypper up every other day if not every day > > I will do a manual specific update of the package, hopping it won't > smash all my simlinks, it took me ages to find them all and simlink them > one by one > > Thks again for your support ! > Eric > A long time user still novice ;) > > > On 2017-02-22 22:39, Christoph Feck wrote: >> https://bugs.kde.org/show_bug.cgi?id=376654 >> >> Christoph Feck changed: >> >>What|Removed |Added >> >> >> Resolution|--- |INVALID >> Status|UNCONFIRMED |RESOLVED >> >> --- Comment #1 from Christoph Feck --- >> Already reported, and I am not going to search it again. >> >> Please update your software, we already released KMail 5.3 and KMail 5.4. > Hi Eric, I suggest to ask in a forum of your distribution how to update to openSUSE Leap 42.2. It ships with KMail 5.3.x, not the newest, but still should fix at least some of your issues. Manually updating packages from non-standard repositories is also possible, but only recommended for more experienced users. Christoph Feck KDE Bug Triaging team -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376791] akonadiserver crash in moveToRoot () at /lib64/libsqlite3.so.0
https://bugs.kde.org/show_bug.cgi?id=376791 --- Comment #2 from PC LX--- SQLite3 version info: # sqlite3 --version 3.14.2 2016-09-12 18:50:49 29dbef4b8585f753861a36d6dd102ca634197bd6 # rpm -qa | grep -i sqlite | sort lib64qt4-database-plugin-sqlite-4.8.7-14.mga6 lib64qt5-database-plugin-sqlite-5.6.2-6.mga6 lib64sqlite3_0-3.14.2-5.mga6 lib64vsqlite++3-0.3.12-7.mga6 libsqlite3_0-3.14.2-5.mga6 sqlite3-tools-3.14.2-5.mga6 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376385] Restarting Akonadi while it fails to deliver content to frontend makes it crash
https://bugs.kde.org/show_bug.cgi?id=376385 Daniel Vrátilchanged: What|Removed |Added Latest Commit||https://commits.kde.org/ako ||nadi/5219f770b998aad16a3d51 ||bbd4f4c7ceb8b143c9 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.4.3 --- Comment #1 from Daniel Vrátil --- Git commit 5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 by Daniel Vrátil. Committed on 23/02/2017 at 18:45. Pushed by dvratil into branch 'Applications/16.12'. DataStream: throw exception if device is null During Connection destruction it can happen that the socket is deleted, but the actual handler is still running and tries to write to that socket (in which case it passes a nullptr to DataStream). This is caused by the issue described in #376822. To prevent the crash in this case (until the root cause is fixed) the DataStream throws an exception if its used without a valid device. This will effectively cause execution to leave the Handler and return. FIXED-IN: 5.4.3 M +5-2src/private/datastream_p.cpp M +10 -6src/private/datastream_p_p.h https://commits.kde.org/akonadi/5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376854] New: patchreview/purpose integration: result dialog doesn't provide review URL
https://bugs.kde.org/show_bug.cgi?id=376854 Bug ID: 376854 Summary: patchreview/purpose integration: result dialog doesn't provide review URL Product: kdevplatform Version: git master Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: patchreview Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com CC: david.nolden@art-master.de Target Milestone: --- I think that ever since I moved to KDevelop5 the upload-to-ReviewBoard feature has been flaky on Mac: about two times out of three the confirmation dialog fails to show the review URL. I also do not recall ever seeing an error dialog. This also happens with my prototype Phabricator plugin for Purpose, so I dumped the json object that is retrieved in the patchreview plugin (the lambda function that acts as the slot receiving the `finished` signal from the Purpose plugin): `auto PatchReviewToolView::showEditDialog()::(anonymous class)::operator()(const QJsonObject &, int, const QString &) const Purpose finished with output QJsonObject({"uninitialized":"true"})` I have no idea what to do with this information other than reporting it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376853] Plasmashell frequently crashing
https://bugs.kde.org/show_bug.cgi?id=376853 --- Comment #1 from tmoore01+...@gmail.com --- Created attachment 104193 --> https://bugs.kde.org/attachment.cgi?id=104193=edit valgrind log Attaching plasmashell valgrind log started with options: killall plasmashell; valgrind --tool=memcheck --leak-check=yes -v /usr/bin/plasmashell 2>&1 | tee valgrind.log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376853] New: Plasmashell frequently crashing
https://bugs.kde.org/show_bug.cgi?id=376853 Bug ID: 376853 Summary: Plasmashell frequently crashing Product: plasmashell Version: 5.9.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: tmoore01+...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Reading a webpage via chrome. Also crashes after I am away and xscreensaver has been running. Seemingly random. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7db8bec800 (LWP 7723))] Thread 31 (Thread 0x7f7c80ce0700 (LWP 13059)): #0 0x7f7da527e5ba in pa_fdsem_before_poll () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #1 0x7f7da5296217 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7f7da590799c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0 #3 0x7f7da5907d9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f7da5907e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f7da5915e29 in () at /usr/lib/libpulse.so.0 #6 0x7f7da52a5fe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7f7db186c454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f7db22b67df in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f7c82ffd700 (LWP 10995)): #0 0x7f7db187210f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7db29a258b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7cd29b21d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7cd29b69d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7cd29b1263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7cd29b6a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7cd29b1263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7cd29b6a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7cd29b1263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f7cd29b4249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f7db29a16d8 in () at /usr/lib/libQt5Core.so.5 #11 0x7f7db186c454 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f7db22b67df in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f7c837fe700 (LWP 10994)): #0 0x7f7db187210f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7db29a258b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7cd29b21d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7cd29b69d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7cd29b1263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7cd29b4249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7db29a16d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f7db186c454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f7db22b67df in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f7c7b7fe700 (LWP 10993)): #0 0x7f7db187210f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7db29a258b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7cd29b21d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7cd29b69d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7cd29b1263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7cd29b6a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7cd29b1263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7cd29b6a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7cd29b1263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f7cd29b6a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10
[Akonadi] [Bug 376791] akonadiserver crash in moveToRoot () at /lib64/libsqlite3.so.0
https://bugs.kde.org/show_bug.cgi?id=376791 Daniel Vrátilchanged: What|Removed |Added CC||dvra...@kde.org --- Comment #1 from Daniel Vrátil --- Looks like a bug in SQLite. Could you please check which version of sqlite3 do you have? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376822] empty trash or all trash on imap account akonadi doesn't continue
https://bugs.kde.org/show_bug.cgi?id=376822 Daniel Vrátilchanged: What|Removed |Added Ever confirmed|0 |1 CC||dvra...@kde.org Priority|NOR |HI Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Daniel Vrátil --- ItemRetriever now uses QEventLoop to wait for request to be processed. If Akonadi Server is shut down during that, the QEventLoop will cause Connection::quit() to be executed, destroying the QSqlDriver and deleting the thread. When the QEventLoop finishes and ItemRetriever::exec() returns, the QSqlQuery() tries to dereference the already-destroyed QSqlDriver. We need a mechanism to either prevent Connection::quit() from being executed while an event loop is running on the Connection, or we need a way to quickly abort ItemRetriever::exec() from Connection::quit() before destroying the SQL connection and the thread. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 376654] Crashes on restart
https://bugs.kde.org/show_bug.cgi?id=376654 --- Comment #2 from Eric--- Hi Christophe, I'm sorry that the bug report system is unable to find a bug that appears every other day and reported with the same title from the same person That's why I HAVE to create a new one each time. I can feel your frustration, please consider mine. It's also unfortunate that KDE is not suggesting Kmail/Kontact update, even though I zypper patch AND Zypper up every other day if not every day I will do a manual specific update of the package, hopping it won't smash all my simlinks, it took me ages to find them all and simlink them one by one Thks again for your support ! Eric A long time user still novice ;) On 2017-02-22 22:39, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=376654 > > Christoph Feck changed: > >What|Removed |Added > > Resolution|--- |INVALID > Status|UNCONFIRMED |RESOLVED > > --- Comment #1 from Christoph Feck --- > Already reported, and I am not going to search it again. > > Please update your software, we already released KMail 5.3 and KMail > 5.4. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376852] New: Akonadi server crash
https://bugs.kde.org/show_bug.cgi?id=376852 Bug ID: 376852 Summary: Akonadi server crash Product: Akonadi Version: 5.4.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: a...@cryptomilk.org Target Milestone: --- I'm running KMail 5.4.2 on openSUSE Tumbleweed. After some time it stops working and then it crashes. akonadi-server-16.12.2 Backtrace: Thread 10 (Thread 0x7fdfb97fa700 (LWP 12253)): [KCrash Handler] #6 QScopedPointer::data (this=0x8) at ../../src/corelib/tools/qscopedpointer.h:141 #7 qGetPtrHelper (p=...) at ../../src/corelib/global/qglobal.h:980 #8 QIODevice::d_func (this=0x0) at ../../src/corelib/io/qiodevice.h:178 #9 QIODevice::write (this=0x0, data=data@entry=0x7fdfb97f93ec "\227", maxSize=maxSize@entry=1) at io/qiodevice.cpp:1596 #10 0x7fe044385bc0 in Akonadi::Protocol::DataStream::operator<< (this=0x7fdfb97f9470, val=) at /usr/src/debug/akonadi-16.12.2/src/private/datastream_p_p.h:91 #11 0x7fe04438932f in Akonadi::Protocol::CommandPrivate::serialize (stream=..., this=0x7fdf98011a00) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:266 #12 Akonadi::Protocol::ResponsePrivate::serialize (stream=..., this=0x7fdf98011a00) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:425 #13 Akonadi::Protocol::FetchItemsResponsePrivate::serialize (this=0x7fdf98011a00, stream=...) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:3344 #14 0x7fe0443709b4 in Akonadi::Protocol::operator<< (command=..., stream=...) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:383 #15 Akonadi::Protocol::serialize (device=, command=...) at /usr/src/debug/akonadi-16.12.2/src/private/protocol.cpp:636 #16 0x0042cde3 in Akonadi::Server::Connection::sendResponse (this=0x1d6cef0, tag=1339, response=...) at /usr/src/debug/akonadi-16.12.2/src/server/connection.cpp:404 #17 0x00431272 in Akonadi::Server::Handler::sendResponse (response=..., this=0x7fdf9800d160) at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:268 #18 Akonadi::Server::Handler::sendResponse (this=0x7fdf9800d160, response=...) at /usr/src/debug/akonadi-16.12.2/src/server/handler.h:152 #19 Akonadi::Server::Handler::failureResponse (this=this@entry=0x7fdf9800d160, failureMessage=...) at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:261 #20 0x0043142f in Akonadi::Server::Handler::failureResponse (this=0x7fdf9800d160, failureMessage=) at /usr/src/debug/akonadi-16.12.2/src/server/handler.cpp:252 #21 0x0042efbd in Akonadi::Server::Connection::slotNewData (this=0x1d6cef0) at /usr/src/debug/akonadi-16.12.2/src/server/connection.cpp:252 #22 0x7fe0434a1a7e in QtPrivate::QSlotObjectBase::call (a=0x7fdfb97f98d0, r=0x1d6cef0, this=) at ../../src/corelib/kernel/qobject_impl.h:101 #23 QMetaObject::activate (sender=0x7fdf98002cd0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3723 #24 0x7fe0434a1709 in QMetaObject::activate (sender=0x7fdf98002dc8, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3740 #25 0x7fe0440ac265 in ?? () from /usr/lib64/libQt5Network.so.5 #26 0x7fe0440ac31c in ?? () from /usr/lib64/libQt5Network.so.5 #27 0x7fe0440b7121 in ?? () from /usr/lib64/libQt5Network.so.5 #28 0x7fe043475aeb in doNotify (event=0x7fdfb97f9ae0, receiver=0x7fdf98003060) at kernel/qcoreapplication.cpp:1063 #29 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1049 #30 QCoreApplication::notifyInternal2 (receiver=0x7fdf98003060, event=event@entry=0x7fdfb97f9ae0) at kernel/qcoreapplication.cpp:988 #31 0x7fe0434ca61d in QCoreApplication::sendEvent (event=0x7fdfb97f9ae0, receiver=) at ../../src/corelib/kernel/qcoreapplication.h:231 #32 socketNotifierSourceDispatch (source=0x7fdf98002a00) at kernel/qeventdispatcher_glib.cpp:106 #33 0x7fe03f5ab697 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #34 0x7fe03f5ab900 in ?? () from /usr/lib64/libglib-2.0.so.0 #35 0x7fe03f5ab9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #36 0x7fe0434ca16f in QEventDispatcherGlib::processEvents (this=0x7fdf980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #37 0x7fe043473aea in QEventLoop::exec (this=this@entry=0x7fdfb97f9d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #38 0x7fe0432a1813 in QThread::exec (this=) at thread/qthread.cpp:507 #39 0x7fe0432a64c8 in QThreadPrivate::start (arg=0x1d69380) at thread/qthread_unix.cpp:368 #40 0x7fe0417c8454 in start_thread (arg=0x7fdfb97fa700) at pthread_create.c:333 #41 0x7fe04299c37f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358559] akonadi_imap_resource incorrectly handles RFC 5464
https://bugs.kde.org/show_bug.cgi?id=358559 Daniel Vrátilchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||dvra...@kde.org --- Comment #2 from Daniel Vrátil --- Could you please run the following in terminal: export KIMAP_LOGFILE=/tmp/kimap.log akonadictl restart Then reproduce the issue again (wait until you see the error in terminal). After that look into /tmp folder, you should see several files starting with kimap.log - find the one that contains the error line and paste it here. Please also include a few (5 or so) lines above the error. If there are any sensitive information (folder names for instance), you can sanitize them. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 376845] Okular ignores default view setting
https://bugs.kde.org/show_bug.cgi?id=376845 --- Comment #1 from Germano Massullo--- Mmmh I noticed that this happens only with certain documents, not with every document... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375423] folderview applet and icon applet and interaction with Latte-Dock panel
https://bugs.kde.org/show_bug.cgi?id=375423 Ivan Bordonichanged: What|Removed |Added Version|5.8.95 |master -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375423] folderview applet and icon applet and interaction with Latte-Dock panel
https://bugs.kde.org/show_bug.cgi?id=375423 Ivan Bordonichanged: What|Removed |Added Component|Folder |Icon Applet -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 376844] Freeze at channel switching
https://bugs.kde.org/show_bug.cgi?id=376844 --- Comment #1 from Mauro Carvalho Chehab--- (In reply to Tenzin from comment #0) > Hi, > I'm using Kaffeine 2.0.5 on Ubuntu 16.04, to watch DVB with a Hauppauge > nova-t-hd. > It works fine usually but quite often it freezes at channel switching. > Ubuntu is continuing to work, but no way to restart Kaffeine, I have to > reboot the system. And Ubuntu doesn't show any crash message. > > Is there something to do ? What do you mean by "freezing"? just Kaffeine application becomes irresponsible? Can it be killed with "killall -9 kaffeine"? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376379] Calendar folder name cannot be changed for iCal resources
https://bugs.kde.org/show_bug.cgi?id=376379 Daniel Vrátilchanged: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||pim-runtime/c551ad2f4dc3a82 ||9241aec05eb343de020fee67f Status|UNCONFIRMED |RESOLVED Version Fixed In||5.4.3 Resolution|--- |FIXED --- Comment #1 from Daniel Vrátil --- Git commit c551ad2f4dc3a829241aec05eb343de020fee67f by Daniel Vrátil. Committed on 23/02/2017 at 17:42. Pushed by dvratil into branch 'Applications/16.12'. Preserve icaldir resource/collection display name Match the root collection's display name to AgentBase::name() and update the agent name when user modifies the root collection's name. This way it's possible to persistently customize icaldir resource names instead of having multiple "Calendar Folder" entries in Korganizer. It also makes the resource visible under the "nice" name in resource listing, instead of using the agent identifier. FIXED-IN: 5.4.3 M +13 -1resources/icaldir/icaldirresource.cpp M +2-0resources/icaldir/icaldirresource.h https://commits.kde.org/kdepim-runtime/c551ad2f4dc3a829241aec05eb343de020fee67f -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376851] Remove Broken Ubufox Extension
https://bugs.kde.org/show_bug.cgi?id=376851 spammonster2...@hotmail.com changed: What|Removed |Added Summary|Remove Ubufox Extension |Remove Broken Ubufox |from Neon Images|Extension -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375924] Cannot rearrange pinned applications
https://bugs.kde.org/show_bug.cgi?id=375924 --- Comment #14 from Eike Hein--- Follow-up patch under review: https://phabricator.kde.org/D4749 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376851] New: Remove Ubufox Extension from Neon Images
https://bugs.kde.org/show_bug.cgi?id=376851 Bug ID: 376851 Summary: Remove Ubufox Extension from Neon Images Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: spammonster2...@hotmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Remove the xul-ext-ubufox Firefox extension package from the Live/Install images. This extension has bugs in Firefox while on KDE Neon that make it essentially useless: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1664398 https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1664400 Also, the extension will soon stop working in Firefox anyway since it is a legacy XUL extension (https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1663395). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 376758] Network Management in systemsettings
https://bugs.kde.org/show_bug.cgi?id=376758 sedrubalchanged: What|Removed |Added Version|unspecified |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376756] Freese on win 10
https://bugs.kde.org/show_bug.cgi?id=376756 Boudewijn Remptchanged: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi, Thanks for making the effort to file a bug report. Unfortunately, there isn't a lot of information. It must be something specific to your system. Is it something that has just started happening, e.g. after a Windows update? Could you try to reset the configuration? See https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration . Do you have any "security" software installed that's not from microsoft? You could also try to disable opengl (settings/configure krita/display) and see if that helps. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 376808] Akonadi stuck on retrieving folder content, ItemFetchJob Stuck, Failed: Multiple Merge Candidates
https://bugs.kde.org/show_bug.cgi?id=376808 --- Comment #3 from Christian Saemann--- Thanks for your quick reply, this fixed it. I should have probably googled more thoroughly. BTW: You mentioned in the blog post that this bug should be fixed in 16.12.1, I experienced it on 16.12.2 (openSUSE Tumbleweed packages). -- You are receiving this mail because: You are watching all bug changes.