[Discover] [Bug 385587] tasks view not too compatible with local package install
https://bugs.kde.org/show_bug.cgi?id=385587 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385559] "Copy to Clibboard" CLI option for spectacle
https://bugs.kde.org/show_bug.cgi?id=385559 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385626] New: KWin crashed when Alt+Tab-ing through open windows
https://bugs.kde.org/show_bug.cgi?id=385626 Bug ID: 385626 Summary: KWin crashed when Alt+Tab-ing through open windows Product: kwin Version: 5.10.5 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: kwin_x11 (5.10.5) Qt Version: 5.9.2 Frameworks Version: 5.38.0 Operating System: Linux 4.13.5-gentoo x86_64 Distribution: "Gentoo Base System release 2.4.1" -- Information about the crash: - What I was doing when the application crashed: I was Alt+Tab-ing through the open windows, when KWin crashed. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1771820840 (LWP 5560))] Thread 14 (Thread 0x7f17519da700 (LWP 12411)): #0 0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f174279b7f3 in cnd_wait (mtx=0x2a72ab8, cond=0x2a72ae0) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x28b1910) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/src/util/u_queue.c:158 #3 0x7f174279b717 in impl_thrd_routine (p=) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:87 #4 0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0 #5 0x7f177132160f in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f172fe6c700 (LWP 12392)): #0 0x7f17713165c3 in ppoll () from /lib64/libc.so.6 #1 0x7f176f244419 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f1724000c38) at kernel/qcore_unix.cpp:81 #3 qt_safe_poll (fds=0x7f1724000c38, nfds=nfds@entry=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:102 #4 0x7f176f245663 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f176f1f866a in QEventLoop::exec (this=this@entry=0x7f172fe6bd50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f176f05c3bb in QThread::exec (this=this@entry=0x27e4150) at thread/qthread.cpp:515 #7 0x7f1769eb3675 in QQmlThreadPrivate::run (this=0x27e4150) at qml/ftw/qqmlthread.cpp:147 #8 0x7f176f0605e0 in QThreadPrivate::start (arg=0x27e4150) at thread/qthread_unix.cpp:368 #9 0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0 #10 0x7f177132160f in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f172f635700 (LWP 5779)): #0 0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f176e366634 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f176e366679 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0 #4 0x7f177132160f in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f173066d700 (LWP 5749)): #0 0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f174279b7f3 in cnd_wait (mtx=0x25bb758, cond=0x25bb780) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x2464d20) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/src/util/u_queue.c:158 #3 0x7f174279b717 in impl_thrd_routine (p=) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:87 #4 0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0 #5 0x7f177132160f in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f1730e6e700 (LWP 5748)): #0 0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f174279b7f3 in cnd_wait (mtx=0x2460710, cond=0x2460738) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x249f350) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/src/util/u_queue.c:158 #3 0x7f174279b717 in impl_thrd_routine (p=) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:87 #4 0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0 #5 0x7f177132160f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f173166f700 (LWP 5747)): #0 0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f174279b7f3 in cnd_wait (mtx=0x2460710, cond=0x2460738) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x247e640) at /var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/src/util/u_queue.c:158 #3 0x7f174279b717 in impl_thrd_routine (p=)
[amarok] [Bug 385447] Play time is displayed improperly.
https://bugs.kde.org/show_bug.cgi?id=385447 --- Comment #2 from Lee the Geek --- Really? Do you suppose a font issue is causing incorrect time displays? On Sat, Oct 7, 2017 at 9:09 AM, Myriam Schweingruber < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=385447 > > Myriam Schweingruber changed: > >What|Removed |Added > > > Resolution|--- |WORKSFORME > Status|UNCONFIRMED |RESOLVED > > --- Comment #1 from Myriam Schweingruber --- > Displayed correctly for me, are you sure you do not just have a font/theme > issue? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385623] Clicking on left screen edge ignored
https://bugs.kde.org/show_bug.cgi?id=385623 --- Comment #2 from kdebuac@porcupinefactory.org --- Do you mean the configuration setting "Touch Screen -> Touch screen swipe gestures"? Immediately after disabling it, there's no change. After `kwin --replace`, there's also no change in behaviour. Did I choose the right option? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput
https://bugs.kde.org/show_bug.cgi?id=383379 H.d.V. changed: What|Removed |Added CC||josef...@freenet.de -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385556] documentation viewer window undocks and redocks seemingly at random across session restarts
https://bugs.kde.org/show_bug.cgi?id=385556 --- Comment #4 from RJVB --- One more observation, and this one is reproducible on Mac AND Linux: 1. Add the "Documentation" toolview to a toolbar (no need to open and use it). Close the documentation toolview if it was already open. 2. Use e.g. Git/Show Differences to launch the patchreview toolview. Don't use the documentation toolview. 3. Exit from the patchreview toolview (Finish button) You'd expect the toolview to remain closed. It doesn't, for me, it reopens systematically until I remove the toolview button from the toolbar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385619] Regression: Icons Only Taskbar pinned items change positions when opened.
https://bugs.kde.org/show_bug.cgi?id=385619 Piotr Keplicz changed: What|Removed |Added CC||kepl...@cmc.pl -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 384653] [zip kioslave] Journal spammed with “kf5.kio.core: error() called twice! Please fix the KIO slave.”
https://bugs.kde.org/show_bug.cgi?id=384653 --- Comment #17 from Martin Kostolný --- Thanks. That is unfortunately a distribution I currently don't have in my virtualbox. I have several though and tried with Kubuntu 16.10 which has older packages and didn't encounter the issue either. On my native system is Arch btw. Just a really stupid thought :) - is it possible that you have krarc binaries installed twice in different locations in your system? Can you check in running processes that while browsing archive with krarc protocol, only one kio_krarc.so process is running? Is there anybody else having these problems? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364746] Crash when accessing 'Font Management' inside Fonts section of 'Settings'
https://bugs.kde.org/show_bug.cgi?id=364746 Christoph Feck changed: What|Removed |Added CC||bug2...@wolke7.net --- Comment #10 from Christoph Feck --- *** Bug 385245 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385245] System Settings Segmentation fault on Font or Display configuration
https://bugs.kde.org/show_bug.cgi?id=385245 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 364746 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385573] desktop-cubes do not start automatically
https://bugs.kde.org/show_bug.cgi?id=385573 --- Comment #2 from bod...@ok.de --- (In reply to Martin Flöser from comment #1) > What is "desktop-cubes"? What is in German "Arbeitsflächen-Würfel". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385625] Plasma crash while rearanging the task-bar (drag&drop) on wayland
https://bugs.kde.org/show_bug.cgi?id=385625 Christian Hägele changed: What|Removed |Added Summary|Plasma crash while |Plasma crash while |rearanging the task-bar on |rearanging the task-bar |wayland |(drag&drop) on wayland --- Comment #1 from Christian Hägele --- I did the rearrangement via drag&drop. Maybe that was the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385623] Clicking on left screen edge ignored
https://bugs.kde.org/show_bug.cgi?id=385623 Martin Flöser changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- Please disable the touch screen border. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned
https://bugs.kde.org/show_bug.cgi?id=372340 Andreas Seifert changed: What|Removed |Added CC||aseif...@t-online.de --- Comment #8 from Andreas Seifert --- I also use Picasa as the 2nd program. It seems the problem exists with digicam 5.6.0 (Windows). My pictures are not twisted. I use only the Exif orientation tag to display the image in the right orientation. In this case the picasa face-frames are not twisted with the image on portrait oriented images. The frame-position is the position on the untwisted image. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs
https://bugs.kde.org/show_bug.cgi?id=384987 --- Comment #21 from Ivo Raisr --- Thank you all for your responses! They were really helpful. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs
https://bugs.kde.org/show_bug.cgi?id=384987 Ivo Raisr changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #20 from Ivo Raisr --- Pushed as commits: 83cabd32492e6d19d483a63522e4e874fa64b617 074de238d44c0cdaf394489ea69a67b76916fbce https://sourceware.org/git/?p=valgrind.git;a=commit;h=83cabd32492e6d19d483a63522e4e874fa64b617 https://sourceware.org/git/?p=valgrind.git;a=commit;h=074de238d44c0cdaf394489ea69a67b76916fbce -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385592] digikam segfaults occasionally, when renaming/moving multiple images
https://bugs.kde.org/show_bug.cgi?id=385592 --- Comment #6 from Johannes Hirte --- (In reply to Johannes Hirte from comment #5) > (In reply to Maik Qualmann from comment #4) > > I do not see an probleme in the ImageInfo::filePath() function. And it > > crashes in system or Qt. Which distribution do you use? > > > > Maik > > I'm using Gentoo with live-ebuild for digikam. > > I don't think ImageInfo::filePath() is the problem in the first place. It > seems to me, m_data is invalidated by some other thread, and this way a > nullptr is pushed down. Sorry, not a nullptr, an invalid pointer. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385592] digikam segfaults occasionally, when renaming/moving multiple images
https://bugs.kde.org/show_bug.cgi?id=385592 --- Comment #5 from Johannes Hirte --- (In reply to Maik Qualmann from comment #4) > I do not see an probleme in the ImageInfo::filePath() function. And it > crashes in system or Qt. Which distribution do you use? > > Maik I'm using Gentoo with live-ebuild for digikam. I don't think ImageInfo::filePath() is the problem in the first place. It seems to me, m_data is invalidated by some other thread, and this way a nullptr is pushed down. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384987] VEX register allocator: allocate caller-save registers for short lived vregs
https://bugs.kde.org/show_bug.cgi?id=384987 --- Comment #19 from Ivo Raisr --- (In reply to Julian Seward from comment #17) > I expect arm(32) would also get a quite big improvement, because > it's also pretty low on registers. [This is not a request to measure, > just random speculation.] Unfortunately I do not have any machine with arm32 architecture. > Assuming power looks sane (the generated code is at least not any bigger > with the patch), and that everything is stable, I suggest you just land > it whenever you like. Actually profiling for the most used 200 blocks in perf/bz2 shows only the following difference: -VexExpansionRatio 228 3228 141 :10 +VexExpansionRatio 228 3196 140 :10 So this means that the majority of the blocks remained the same size; one block is slightly smaller now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385625] New: Plasma crash while rearanging the task-bar on wayland
https://bugs.kde.org/show_bug.cgi?id=385625 Bug ID: 385625 Summary: Plasma crash while rearanging the task-bar on wayland Product: plasmashell Version: 5.11.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: christian_haeg...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.0) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.4-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I rearranged the taskbar. I tried to put a plasmaoid into the task-bar and it crashed. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 27return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7fd111aaa900 (LWP 18900))] Thread 30 (Thread 0x7fcfc19d7700 (LWP 20307)): #0 0x7fd10a9a882d in futex_wait_cancelable (private=, expected=0, futex_word=0x56357975dd24) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd10a9a882d in __pthread_cond_wait_common (abstime=0x0, mutex=0x56357975dcd0, cond=0x56357975dcf8) at pthread_cond_wait.c:502 #2 0x7fd10a9a882d in __pthread_cond_wait (cond=0x56357975dcf8, mutex=0x56357975dcd0) at pthread_cond_wait.c:655 #3 0x7fd10b7f004b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd10f541958 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fd10f541d8a in () at /usr/lib64/libQt5Quick.so.5 #6 0x7fd10b7eed2e in () at /usr/lib64/libQt5Core.so.5 #7 0x7fd10a9a2558 in start_thread (arg=0x7fcfc19d7700) at pthread_create.c:465 #8 0x7fd10b0f345f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fcfc37fe700 (LWP 20306)): #0 0x7fd10a9a882d in futex_wait_cancelable (private=, expected=0, futex_word=0x56357901e7ac) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd10a9a882d in __pthread_cond_wait_common (abstime=0x0, mutex=0x56357901e758, cond=0x56357901e780) at pthread_cond_wait.c:502 #2 0x7fd10a9a882d in __pthread_cond_wait (cond=0x56357901e780, mutex=0x56357901e758) at pthread_cond_wait.c:655 #3 0x7fd06628bcab in () at /usr/lib64/dri/radeonsi_dri.so #4 0x7fd06628bbc7 in () at /usr/lib64/dri/radeonsi_dri.so #5 0x7fd10a9a2558 in start_thread (arg=0x7fcfc37fe700) at pthread_create.c:465 #6 0x7fd10b0f345f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fcfc21d8700 (LWP 20148)): #0 0x7fd10a9a882d in futex_wait_cancelable (private=, expected=0, futex_word=0x563578372a94) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd10a9a882d in __pthread_cond_wait_common (abstime=0x0, mutex=0x563578372a40, cond=0x563578372a68) at pthread_cond_wait.c:502 #2 0x7fd10a9a882d in __pthread_cond_wait (cond=0x563578372a68, mutex=0x563578372a40) at pthread_cond_wait.c:655 #3 0x7fd10b7f004b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd10f541958 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7fd10f541d8a in () at /usr/lib64/libQt5Quick.so.5 #6 0x7fd10b7eed2e in () at /usr/lib64/libQt5Core.so.5 #7 0x7fd10a9a2558 in start_thread (arg=0x7fcfc21d8700) at pthread_create.c:465 #8 0x7fd10b0f345f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fcfc3fff700 (LWP 20147)): #0 0x7fd10a9a882d in futex_wait_cancelable (private=, expected=0, futex_word=0x5635799600ac) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd10a9a882d in __pthread_cond_wait_common (abstime=0x0, mutex=0x563579960058, cond=0x563579960080) at pthread_cond_wait.c:502 #2 0x7fd10a9a882d in __pthread_cond_wait (cond=0x563579960080, mutex=0x563579960058) at pthread_cond_wait.c:655 #3 0x7fd06628bcab in () at /usr/lib64/dri/radeonsi_dri.so #4 0x7fd06628bbc7 in () at /usr/lib64/dri/radeonsi_dri.so #5 0x7fd10a9a2558 in start_thread (arg=0x7fcfc3fff700) at pthread_create.c:465 #6 0x7fd10b0f345f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7fcfd146f700 (LWP 19808)): #0 0x7fd10a9a882d in futex_wait_cancelable (private=, expected=0, futex_word=0x563579f06630) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd10a9a882d in __pthread_cond_wait_common (abstime=0x0, mutex=0x563579f065e0, cond=0x563579f06608) at pthread_cond_wait.c:502 #2 0x7fd10a9a882d in __pthread_cond_wait (cond=0x563579f06608, mutex=0x563579f065e0) at pthread_cond_wait.c:655 #3 0x7fd10b7f004b in QWaitCondition::wait(QMutex
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #41 from Till Schäfer --- confirmed has no special meaning here. It does not mean that anybody is working on it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385624] New: kmail crash after resize of window after startup
https://bugs.kde.org/show_bug.cgi?id=385624 Bug ID: 385624 Summary: kmail crash after resize of window after startup Product: kmail2 Version: 5.5.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ba...@barrys-emacs.org Target Milestone: --- Application: kmail (5.5.1) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.13.4-200.fc26.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: booted fedora login to KDE start kmail resize window - kmail crash here -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f7f55461940 (LWP 2242))] Thread 26 (Thread 0x7f7eb783a700 (LWP 2305)): #0 0x7f7f7384190b in futex_wait_cancelable (private=, expected=0, futex_word=0x7f7f5ab60478) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f7f7384190b in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f7f5ab60428, cond=0x7f7f5ab60450) at pthread_cond_wait.c:502 #2 0x7f7f7384190b in __pthread_cond_wait (cond=0x7f7f5ab60450, mutex=0x7f7f5ab60428) at pthread_cond_wait.c:655 #3 0x7f7f5aa65534 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #4 0x7f7f5aa65579 in () at /lib64/libQt5Script.so.5 #5 0x7f7f7383b36d in start_thread (arg=0x7f7eb783a700) at pthread_create.c:456 #6 0x7f7f778eabbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 25 (Thread 0x7f7ec1689700 (LWP 2292)): #0 0x7f7f778deacd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7f63883569 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f7f6388367c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f7f786f6e6b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f7eb80008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7f786a760a in QEventLoop::exec(QFlags) (this=this@entry=0x7f7ec1688c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f7f784ff99a in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f7f78503c9e in QThreadPrivate::start(void*) (arg=0x562ed8f3cf10) at thread/qthread_unix.cpp:368 #7 0x7f7f7383b36d in start_thread (arg=0x7f7ec1689700) at pthread_create.c:456 #8 0x7f7f778eabbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 24 (Thread 0x7f7ee27fc700 (LWP 2277)): #0 0x7f7f778da22d in write () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7f7785822d in _IO_new_file_write (f=0x7f7f77ba6500 <_IO_2_1_stderr_>, data=0x7f7ee27f8ce0, n=39) at fileops.c:1271 #2 0x7f7f77858bcf in new_do_write (to_do=, data=0x7f7ee27f8ce0 "[warn] epoll_wait: Bad file descriptor\n", fp=0x7f7f77ba6500 <_IO_2_1_stderr_>) at fileops.c:526 #3 0x7f7f77858bcf in _IO_new_file_xsputn (f=0x7f7f77ba6500 <_IO_2_1_stderr_>, data=, n=39) at fileops.c:1350 #4 0x7f7f7782c747 in buffered_vfprintf (s=s@entry=0x7f7f77ba6500 <_IO_2_1_stderr_>, format=format@entry=0x7f7f5ddefb10 "[%s] %s\n", args=args@entry=0x7f7ee27fb2a0) at vfprintf.c:2346 #5 0x7f7f77829786 in _IO_vfprintf_internal (s=s@entry=0x7f7f77ba6500 <_IO_2_1_stderr_>, format=0x7f7f5ddefb10 "[%s] %s\n", ap=ap@entry=0x7f7ee27fb2a0) at vfprintf.c:1293 #6 0x7f7f778fb2d6 in ___fprintf_chk (fp=0x7f7f77ba6500 <_IO_2_1_stderr_>, flag=1, format=) at fprintf_chk.c:35 #7 0x7f7f5ddd7880 in _warn_helper () at /lib64/libevent-2.0.so.5 #8 0x7f7f5ddd7a44 in event_warn () at /lib64/libevent-2.0.so.5 #9 0x7f7f5dddc1e0 in epoll_dispatch () at /lib64/libevent-2.0.so.5 #10 0x7f7f5ddc6dbe in event_base_loop () at /lib64/libevent-2.0.so.5 #11 0x7f7f6afbc559 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #12 0x7f7f6afb8828 in base::MessageLoop::RunHandler() () at /lib64/libQt5WebEngineCore.so.5 #13 0x7f7f6afd526b in base::RunLoop::Run() () at /lib64/libQt5WebEngineCore.so.5 #14 0x7f7f6afecf66 in base::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #15 0x7f7f6afe906b in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #16 0x7f7f7383b36d in start_thread (arg=0x7f7ee27fc700) at pthread_create.c:456 #17 0x7f7f778eabbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 23 (Thread 0x7f7ee2ffd700 (LWP 2276)): #0 0x7f7f7384190b in futex_wait_cancelable (private=, expected=0, futex_word=0x7f7ee2ffc988) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f7f7384190b in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f7ee2ffc9
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 Till Schäfer changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385623] New: Clicking on left screen edge ignored
https://bugs.kde.org/show_bug.cgi?id=385623 Bug ID: 385623 Summary: Clicking on left screen edge ignored Product: kwin Version: 5.10.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: kdebuac@porcupinefactory.org Target Milestone: --- Flags: X11+ Clicking on the left edge of the screen does nothing with respect to focusing. This did not happen with previous KDE update - around 5.9 Setup: Fedora 25 + KDE 5.10.5-1 Left, top edges of the screen unoccupied Panels on right, bottom Steps: 1. Open a small window A and make it cross (overlap) the left edge 2. Open a small window B and place it besides A 3. Focus B 4. Move cursor to the very left edge over A 5. Click Result: Nothing happens Expected: A gets focused -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #40 from Stefano --- Is anyone working on this? It's more than a year old, with lots of user comments confirming it, but the status is still "unconfirmed". -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385622] New: Please add Back Button to Gwenview
https://bugs.kde.org/show_bug.cgi?id=385622 Bug ID: 385622 Summary: Please add Back Button to Gwenview Product: gwenview Version: 16.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: rrock...@gmail.com Target Milestone: --- Created attachment 108285 --> https://bugs.kde.org/attachment.cgi?id=108285&action=edit Screenshot of what happens anytime I use gwenview on anything more complicated than a folder of images Please please add the back button as an optional toolbar button to gwenview. The Up arrow and the back button ARE NOT the same thing and I run into constant frustration as I click on an archive, view an image, click up to "go back", and get an error message because some file handler (i.e. krarc://) cannot doesn't work on a file path that doesn't include the actual file it is supposed to handle. The back button is not an up button, and there is no intuitive way to go "back" to where I just was with the current configuration. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385621] New: Settings blurry with HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=385621 Bug ID: 385621 Summary: Settings blurry with HiDPI scaling Product: systemsettings Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zachho...@gmail.com Target Milestone: --- When I add HiDPI scaling I see issues in a few apps, for example #373232 on Konsole. But the biggest issues are with the Settings app and Discover app. In the settings app, the left navigation panels are very blurry, and the content panels are blurry for some sections and not others. These sections are blurry: - Workspace Theme (all but "Curser Theme" sub section) - Desktop Behavior -> Desktop Effects Examples of sections that are not blurry: - Colors - Fonts - Icons - Desktop Behavior -> (all EXCEPT Desktop Effects) I'm on KDE Neon, Plasma 5.11. Nvidia drivers, 3840x2160 display, 1.3 scaling factor. When I take a screenshot with Spectacle all the windows are blurry, so decided not to include a screenshot example. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385619] Regression: Icons Only Taskbar pinned items change positions when opened.
https://bugs.kde.org/show_bug.cgi?id=385619 Michail Vourlakos changed: What|Removed |Added CC||mvourla...@gmail.com --- Comment #2 from Michail Vourlakos --- I can add that I tried to set separateLaunchers:false at plasma taskmanager and even though it fixed things after repositioning my tasks, on the next reload of plasma the launchers were put in the start and all the windows (including those that they had a launcher) at the end. So the launchers position becomes broken from a user point view in every plasma relogin. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 385620] New: app crashed after i put in a command
https://bugs.kde.org/show_bug.cgi?id=385620 Bug ID: 385620 Summary: app crashed after i put in a command Product: konsole Version: 15.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: animerocks...@gmail.com Target Milestone: --- after typing sudo add-apt-repository universe && sudo apt-get update the konsole application froze -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385619] Regression: Icons Only Taskbar pinned items change positions when opened.
https://bugs.kde.org/show_bug.cgi?id=385619 --- Comment #1 from Vasyl Demin --- Same problem after today's update to 5.11.0 on Arch Linux x86_64. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385619] Regression: Icons Only Taskbar pinned items change positions when opened.
https://bugs.kde.org/show_bug.cgi?id=385619 Vasyl Demin changed: What|Removed |Added CC||vasyl.de...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #39 from Till Schäfer --- still reproducible in plasma 5.11, qt 5.9.2, frameworks 5.38, and kdepim 17.08.1 (on Gentoo) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385563] Regression: Taskbar pinned items change positions when opened
https://bugs.kde.org/show_bug.cgi?id=385563 --- Comment #6 from Paul --- New report opened against Icon Only Task manager. Bug # 385619 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385619] New: Regression: Icons Only Taskbar pinned items change positions when opened.
https://bugs.kde.org/show_bug.cgi?id=385619 Bug ID: 385619 Summary: Regression: Icons Only Taskbar pinned items change positions when opened. Product: plasmashell Version: 5.11.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: pip@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Previously when an application was launched the icon would be underlined and remain in it's (placed) position within the task manager. Now the icon is underlined and moves to the rightmost position, upon closure of the application it returns to it's original position. Further details and screen shots: https://forums.opensuse.org/showthread.php/527592-KDE-Icon-only-task-manager-chase-the-icon (Forked from bug # 385563 as that referred to the "Normal" taskbar) -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 382291] System settings GTK apps configurations resets.
https://bugs.kde.org/show_bug.cgi?id=382291 Timi changed: What|Removed |Added CC||eagle.bugs.kde.org@airpost. ||net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385618] New: Lauching a pinned application moves the pinned icon to the front of all other pinned applicatons
https://bugs.kde.org/show_bug.cgi?id=385618 Bug ID: 385618 Summary: Lauching a pinned application moves the pinned icon to the front of all other pinned applicatons Product: plasmashell Version: 5.11.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: joaomiguelb...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Lauching a pinned application moves the pinned icon to the front of all other pinned applicatons. The icon will revert to its original position upon application exit. Expected behaviour is the icon remain in its pinned place. Or a option should exist to define either behaviour. -- You are receiving this mail because: You are watching all bug changes.
[krecipes] [Bug 385617] New: Krecipes on Ubuntu 17.04 doesn't show recipe photo when viewing
https://bugs.kde.org/show_bug.cgi?id=385617 Bug ID: 385617 Summary: Krecipes on Ubuntu 17.04 doesn't show recipe photo when viewing Product: krecipes Version: 2.1.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krecipes-de...@kde.org Reporter: ian.smit...@virgin.net Target Milestone: --- I am using Krecipes 2.1.0 on Ubuntu 17.04. I have used it for many years, and am a complete fan. Sadly, I have updated to Ubuntu 17.04, and now when I try to save a recipe photo, when I view the recipe, it isn't displayed. I have had a look in the database, and the field for the photos is blank when the photo is not visible. This seems to be that although the image is loaded in the recipe, and the recipe is saved, for some reason, the photo is not saved in the database. Please let me know if there is more debug information I might supply. Any clues as to how to remedy this? Many thanks, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385563] Regression: Taskbar pinned items change positions when opened
https://bugs.kde.org/show_bug.cgi?id=385563 --- Comment #5 from Paul --- (In reply to Eike Hein from comment #3) > Disable "Keep launchers seperate" in the settings. This bug also affects the icons only task manager, which does not appear to have the setting you refer to. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385563] Regression: Taskbar pinned items change positions when opened
https://bugs.kde.org/show_bug.cgi?id=385563 --- Comment #4 from Shitikanth --- (In reply to Eike Hein from comment #3) > Disable "Keep launchers seperate" in the settings. Why? What does that have to do with this bug?! Why are the sort settings being applied to the pinned apps now when they were not being applied to them earlier? This was the original behaviour and the behaviour most people would expect, so even if the change in behaviour is intentional, I would still call it a regression. Also, can you please wait for feedback from users before marking issue as resolved/fixed? From what I can tell from various forum links people have posted, this issue seems to be affecting a lot of people. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385616] New: launcherPosition, launcherActivities is broken in libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=385616
Bug ID: 385616
Summary: launcherPosition, launcherActivities is broken in
libtaskmanager
Product: plasmashell
Version: 5.11.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Task Manager
Assignee: h...@kde.org
Reporter: mvourla...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
These two functions from TasksModel are broken, what is happening is the
following. Plasma possibly added new functionality in 5.11 for which a task's
launcher url is changed in something more generic. For systemsettings that
would be, applications:systemsettings.desktop . I found that this is happening
for launchers and windows in 5.11, I dont know for startups. Because of this
launcherPosition and launcherActivities return -1 and null accordingly. For
cases that instead of the above the desktop url is used e.g.
file:///usr/share/applications/systemsettings.desktop
then the functions I think they worked correctly. I used the following code on
the click event of a task in Latte in order to check the behavior.
console.log("POS "+ tasksModel.launcherPosition(LauncherUrlWithoutIcon) +
" - " + tasksModel.launcherPosition(LauncherUrl) + " - "
+ tasksModel.launcherActivities(LauncherUrl));
at all cases of launchers and windows the results where "POS -1 - -1 -"
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 385616] launcherPosition, launcherActivities are broken in libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=385616 Michail Vourlakos changed: What|Removed |Added Summary|launcherPosition, |launcherPosition, |launcherActivities is |launcherActivities are |broken in libtaskmanager|broken in libtaskmanager -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385592] digikam segfaults occasionally, when renaming/moving multiple images
https://bugs.kde.org/show_bug.cgi?id=385592 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #4 from Maik Qualmann --- I do not see an probleme in the ImageInfo::filePath() function. And it crashes in system or Qt. Which distribution do you use? Maik -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 Kevin Funk changed: What|Removed |Added CC||kf...@kde.org Summary|plasma-desktop crashed |plasma-desktop crashed |after configuring printer |after configuring printer |applet |applet ||[JobModel::updateJob] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376104] Quick tile window to any screen edge or corner de-maximizes the window without tiling as a first action since plasma 5.9.0
https://bugs.kde.org/show_bug.cgi?id=376104 jingyu9...@hotmail.com changed: What|Removed |Added CC||jingyu9...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 385370] Crash System Settings Module
https://bugs.kde.org/show_bug.cgi?id=385370 Christoph Feck changed: What|Removed |Added CC||mikefarme...@web.de --- Comment #3 from Christoph Feck --- *** Bug 385613 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 385613] NetworkManager always crashes while setting up / editing an wifi-ap
https://bugs.kde.org/show_bug.cgi?id=385613 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 385370 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385563] Regression: Taskbar pinned items change positions when opened
https://bugs.kde.org/show_bug.cgi?id=385563 Eike Hein changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Eike Hein --- Disable "Keep launchers seperate" in the settings. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 385613] NetworkManager always crashes while setting up / editing an wifi-ap
https://bugs.kde.org/show_bug.cgi?id=385613 Christoph Feck changed: What|Removed |Added Product|kde |plasma-nm Version|unspecified |5.8.7 Component|general |general Assignee|unassigned-b...@kde.org |jgrul...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 385610] Lockscreen: don't time block password entry - only login attempts.
https://bugs.kde.org/show_bug.cgi?id=385610 Martin Flöser changed: What|Removed |Added Product|kwin|kscreenlocker Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED CC||bhus...@gmail.com, ||mgraess...@kde.org Version|5.11.0 |unspecified Component|general |greeter --- Comment #1 from Martin Flöser --- This is just another case of the old: security vs. comfort. The password field is disabled for increased security to make it more annoying to brute force the password. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 385615] NetworkManager always crashes while setting up / editing an wifi-ap
https://bugs.kde.org/show_bug.cgi?id=385615 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christoph Feck --- Reported as bug 385613. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 385614] NetworkManager always crashes while setting up / editing an wifi-ap
https://bugs.kde.org/show_bug.cgi?id=385614 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christoph Feck --- Reported as bug 385613. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 384201] SMB3 is broken in Dolphin
https://bugs.kde.org/show_bug.cgi?id=384201 Evotopid changed: What|Removed |Added CC||evoto...@gmail.com --- Comment #1 from Evotopid --- I have the same issue (same error message) on Arch Linux with Dolphin v17.08.1 Dolphin is able to list my shares but any attempt to actually connect fails, while it works fine with thunar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384703] Pinned items rearranging, displaying multiple times
https://bugs.kde.org/show_bug.cgi?id=384703 --- Comment #1 from raist...@gmail.com --- The bug is still present in 5.11.0 release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384703] Pinned items rearranging, displaying multiple times
https://bugs.kde.org/show_bug.cgi?id=384703 raist...@gmail.com changed: What|Removed |Added Version|5.10.95 |5.11.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385563] Regression: Taskbar pinned items change positions when opened
https://bugs.kde.org/show_bug.cgi?id=385563 Paul changed: What|Removed |Added CC||pip@gmx.com --- Comment #2 from Paul --- Also affecting the icon only task manager. (openSUSE Tumbleweed 20171009) ( https://forums.opensuse.org/showthread.php/527592-KDE-Icon-only-task-manager-chase-the-icon ) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 385615] New: NetworkManager always crashes while setting up / editing an wifi-ap
https://bugs.kde.org/show_bug.cgi?id=385615 Bug ID: 385615 Summary: NetworkManager always crashes while setting up / editing an wifi-ap Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mikefarme...@web.de Target Milestone: --- Application: kcmshell5 (5.8.7) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.12.0-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Trying to set up an wifi-ap in NetworkManager. NetworkManager crashes when pressing "OK" after editing the wifi settings of the ap-hotspot The set-up wifi is visible in the connection manager of the Linux host, but not on mobile devices (two different were tested). The crash can be reproduced every time. -- Backtrace: Application: Modul für Systemeinstellungen (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0c26af7600 (LWP 2181))] Thread 3 (Thread 0x7f0c0a34e700 (LWP 2183)): #0 0x7fffdab7b979 in ?? () #1 0x7fffdab7bc2a in clock_gettime () #2 0x7f0c2647d956 in __GI___clock_gettime (clock_id=1, tp=0x7f0c0a34da40) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f0c23b12d31 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0c23b11569 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0c23b11b45 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0c23b1318e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0c1e6bf658 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f0c1e6c004b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f0c1e6c022c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f0c23b1341b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0c23ab8dba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f0c238d83ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0c2577fe45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #14 0x7f0c238dd29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f0c20890494 in start_thread (arg=0x7f0c0a34e700) at pthread_create.c:333 #16 0x7f0c26470abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7f0c1329a700 (LWP 2182)): #0 0x7f0c2646766d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0c21105150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f0c21106ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f0c157fbf09 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f0c238dd29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0c20890494 in start_thread (arg=0x7f0c1329a700) at pthread_create.c:333 #6 0x7f0c26470abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 1 (Thread 0x7f0c26af7600 (LWP 2181)): [KCrash Handler] #6 0x7f0c23f72940 in typeinfo for QDynamicMetaObjectData () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0c24ac66c5 in QWidget::destroy(bool, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f0c24a92070 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f0c2672ce02 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kcmshell5.so #10 0x7f0c263a82e1 in __libc_start_main (main=0x55adc51e4790, argc=2, argv=0x7fffdab3a378, init=, fini=, rtld_fini=, stack_end=0x7fffdab3a368) at ../csu/libc-start.c:291 #11 0x55adc51e47ca in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 385613] New: NetworkManager always crashes while setting up / editing an wifi-ap
https://bugs.kde.org/show_bug.cgi?id=385613 Bug ID: 385613 Summary: NetworkManager always crashes while setting up / editing an wifi-ap Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mikefarme...@web.de Target Milestone: --- Application: kcmshell5 (5.8.7) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.12.0-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Trying to set up an wifi-ap in NetworkManager. NetworkManager crashes when pressing "OK" after editing the wifi settings of the ap-hotspot The set-up wifi is visible in the connection manager of the Linux host, but not on mobile devices (two different were tested). The crash can be reproduced every time. -- Backtrace: Application: Modul für Systemeinstellungen (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0c26af7600 (LWP 2181))] Thread 3 (Thread 0x7f0c0a34e700 (LWP 2183)): #0 0x7fffdab7b979 in ?? () #1 0x7fffdab7bc2a in clock_gettime () #2 0x7f0c2647d956 in __GI___clock_gettime (clock_id=1, tp=0x7f0c0a34da40) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f0c23b12d31 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0c23b11569 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0c23b11b45 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0c23b1318e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0c1e6bf658 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f0c1e6c004b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f0c1e6c022c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f0c23b1341b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0c23ab8dba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f0c238d83ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0c2577fe45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #14 0x7f0c238dd29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f0c20890494 in start_thread (arg=0x7f0c0a34e700) at pthread_create.c:333 #16 0x7f0c26470abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7f0c1329a700 (LWP 2182)): #0 0x7f0c2646766d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0c21105150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f0c21106ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f0c157fbf09 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f0c238dd29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0c20890494 in start_thread (arg=0x7f0c1329a700) at pthread_create.c:333 #6 0x7f0c26470abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 1 (Thread 0x7f0c26af7600 (LWP 2181)): [KCrash Handler] #6 0x7f0c23f72940 in typeinfo for QDynamicMetaObjectData () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0c24ac66c5 in QWidget::destroy(bool, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f0c24a92070 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f0c2672ce02 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kcmshell5.so #10 0x7f0c263a82e1 in __libc_start_main (main=0x55adc51e4790, argc=2, argv=0x7fffdab3a378, init=, fini=, rtld_fini=, stack_end=0x7fffdab3a368) at ../csu/libc-start.c:291 #11 0x55adc51e47ca in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 385614] New: NetworkManager always crashes while setting up / editing an wifi-ap
https://bugs.kde.org/show_bug.cgi?id=385614 Bug ID: 385614 Summary: NetworkManager always crashes while setting up / editing an wifi-ap Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mikefarme...@web.de Target Milestone: --- Application: kcmshell5 (5.8.7) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.12.0-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Trying to set up an wifi-ap in NetworkManager. NetworkManager crashes when pressing "OK" after editing the wifi settings of the ap-hotspot The set-up wifi is visible in the connection manager of the Linux host, but not on mobile devices (two different were tested). The crash can be reproduced every time. -- Backtrace: Application: Modul für Systemeinstellungen (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0c26af7600 (LWP 2181))] Thread 3 (Thread 0x7f0c0a34e700 (LWP 2183)): #0 0x7fffdab7b979 in ?? () #1 0x7fffdab7bc2a in clock_gettime () #2 0x7f0c2647d956 in __GI___clock_gettime (clock_id=1, tp=0x7f0c0a34da40) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f0c23b12d31 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0c23b11569 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0c23b11b45 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0c23b1318e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0c1e6bf658 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f0c1e6c004b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f0c1e6c022c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f0c23b1341b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0c23ab8dba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f0c238d83ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0c2577fe45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #14 0x7f0c238dd29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f0c20890494 in start_thread (arg=0x7f0c0a34e700) at pthread_create.c:333 #16 0x7f0c26470abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7f0c1329a700 (LWP 2182)): #0 0x7f0c2646766d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0c21105150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f0c21106ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f0c157fbf09 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f0c238dd29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0c20890494 in start_thread (arg=0x7f0c1329a700) at pthread_create.c:333 #6 0x7f0c26470abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 1 (Thread 0x7f0c26af7600 (LWP 2181)): [KCrash Handler] #6 0x7f0c23f72940 in typeinfo for QDynamicMetaObjectData () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0c24ac66c5 in QWidget::destroy(bool, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f0c24a92070 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f0c2672ce02 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kcmshell5.so #10 0x7f0c263a82e1 in __libc_start_main (main=0x55adc51e4790, argc=2, argv=0x7fffdab3a378, init=, fini=, rtld_fini=, stack_end=0x7fffdab3a368) at ../csu/libc-start.c:291 #11 0x55adc51e47ca in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385612] New: System Settings Apperence Crashes
https://bugs.kde.org/show_bug.cgi?id=385612 Bug ID: 385612 Summary: System Settings Apperence Crashes Product: systemsettings Version: 5.10.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rgbe...@gmail.com Target Milestone: --- Application: systemsettings5 (5.10.5) (Compiled from sources) Qt Version: 5.9.2 Frameworks Version: 5.38.0 Operating System: Linux 4.9.8-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Clicked on Apperences and then Systems Settings crashes. - Unusual behavior I noticed: I can not edit tool bar or type searches in krunner or application launcher. - Custom settings of the application: None that I kknow of. 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 0x7f33b9ffe740 (LWP 5364))] Thread 4 (Thread 0x7f33995f0700 (LWP 5368)): #0 0x7f33b1b66697 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f33b1b68b7b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f33b1b69638 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f33b1b6981c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f33b7081c2c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f33b70328ca in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f33b6e8c3f4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f33b5721c75 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f33b6e90951 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f33b3ad3444 in start_thread () from /lib64/libpthread.so.0 #10 0x7f33b673c5ed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f33a3fff700 (LWP 5366)): #0 0x7f33b67334ed in poll () from /lib64/libc.so.6 #1 0x7f33b1b6970c in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f33b1b6981c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f33b7081c2c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f33b70328ca in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f33b6e8c3f4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f33ba0f5885 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f33b6e90951 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f33b3ad3444 in start_thread () from /lib64/libpthread.so.0 #9 0x7f33b673c5ed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f33a9ff6700 (LWP 5365)): #0 0x7f33b67334ed in poll () from /lib64/libc.so.6 #1 0x7f33b434d8f2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f33b434f6df in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f33acb95ac9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f33b6e90951 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f33b3ad3444 in start_thread () from /lib64/libpthread.so.0 #6 0x7f33b673c5ed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f33b9ffe740 (LWP 5364)): [KCrash Handler] #6 0x7f33a00bded4 in ?? () from /usr/lib64/qt5/qml/QtQuick/Controls/libqtquickcontrolsplugin.so #7 0x7f33b5a51b37 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () from /usr/lib64/libQt5Quick.so.5 #8 0x7f33b5a52493 in QQuickWindowPrivate::updateDirtyNodes() () from /usr/lib64/libQt5Quick.so.5 #9 0x7f33b5a53922 in QQuickWindowPrivate::syncSceneGraph() () from /usr/lib64/libQt5Quick.so.5 #10 0x7f33b5b0fc39 in QQuickRenderControl::sync() () from /usr/lib64/libQt5Quick.so.5 #11 0x7f33ba0d3ec0 in ?? () from /usr/lib64/libQt5QuickWidgets.so.5 #12 0x7f33ba0d6fd3 in QQuickWidget::resizeEvent(QResizeEvent*) () from /usr/lib64/libQt5QuickWidgets.so.5 #13 0x7f33b84d40ee in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #14 0x7f33b8493f1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f33b849b9b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7f33b7033e30 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #17 0x7f33b84cc772 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f33b84d0516 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f33b84d33e5 in QWidget::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #20 0x7f33b84d04a0 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #21 0x7f33b84d0532 in QWidgetPriva
[karbon] [Bug 385611] New: Toolbax icons not visible
https://bugs.kde.org/show_bug.cgi?id=385611 Bug ID: 385611 Summary: Toolbax icons not visible Product: karbon Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: usability Assignee: ja...@gmx.net Reporter: m.sai...@protonmail.ch Target Milestone: --- Created attachment 108284 --> https://bugs.kde.org/attachment.cgi?id=108284&action=edit karbon-icons-bug The icons are clickable but any drawing is visible on them. Check the screenshot. Linux (x86_64) release 4.13.0-12-generic Karbon : 3.0.1 LInux Ubuntu 17.10 on Gnome. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 383675] highlight makes text disappear
https://bugs.kde.org/show_bug.cgi?id=383675 Orion Poplawski changed: What|Removed |Added CC||or...@cora.nwra.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 331697] can't fill out pdf form
https://bugs.kde.org/show_bug.cgi?id=331697 --- Comment #12 from Nate Graham --- So that would mean, for bugs like these, we would close the bug against Okular and re-open it against Poppler saying "Poppler should better handle the following case of the PDF file being malformed." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385563] Regression: Taskbar pinned items change positions when opened
https://bugs.kde.org/show_bug.cgi?id=385563 Vasyl Demin changed: What|Removed |Added CC||vasyl.de...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 331697] can't fill out pdf form
https://bugs.kde.org/show_bug.cgi?id=331697 --- Comment #11 from Nate Graham --- My strong preference would be to make Poppler more flexibly able to handle malformed files like these. It isn't reasonable to expect all PDF documents to be well-formed, given the apparent state of PDF generation software out there. We shouldn't make our users suffer for the sins of the generator software used to produce PDFs that they may need to fill out. Users shouldn't be made to understand any of this; it should Just Work.™ -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 385590] Red separator line too thin, better use different colors for used and cache
https://bugs.kde.org/show_bug.cgi?id=385590 Martin Ueding changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Martin Ueding --- Looking through the source code I realized that everything is there, just my choice of colors is not very useful. The small red line apparently is the “buffer” part and “used” and “cache” are both the same color. This is simply resolved by choosing the colors manually. Therefore there is nothing that needs fixing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385610] New: Lockscreen: don't time block password entry - only login attempts.
https://bugs.kde.org/show_bug.cgi?id=385610 Bug ID: 385610 Summary: Lockscreen: don't time block password entry - only login attempts. Product: kwin Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- If I mistype my password on the lock screen I have to wait ca. 3-5 seconds to reenter it. I could have spent the time to reenter the password. It should in my opinion only time block the login attempts. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385606] System Settings crashed after applying fonts changes.
https://bugs.kde.org/show_bug.cgi?id=385606 Antonio Rojas changed: What|Removed |Added Resolution|FIXED |DOWNSTREAM CC||aro...@archlinux.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=385594 Piotr Keplicz changed: What|Removed |Added CC||kepl...@cmc.pl --- Comment #3 from Piotr Keplicz --- Also reported in bug 385563. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 385603] Unlock screen text near top of screen got cropped when font dpi is at 120 vs default 96
https://bugs.kde.org/show_bug.cgi?id=385603 --- Comment #1 from Martin Flöser --- Please use display scaling instead of adjusting font dpi. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385595] KWin::WorkspaceWrapper signal clientAdded(KWin::Client *client) doesn't trigger on Wayland
https://bugs.kde.org/show_bug.cgi?id=385595 Martin Flöser changed: What|Removed |Added Resolution|--- |LATER Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- Yes, this is on purpose. We don't have a security concept yet for Scripts on Wayland, so Wayland windows are excluded from scripting. I have an idea for how to implement the security. Once that is in, scripting will be activated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385573] desktop-cubes do not start automatically
https://bugs.kde.org/show_bug.cgi?id=385573 --- Comment #1 from Martin Flöser --- What is "desktop-cubes"? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385291] entire desktop freezing, cursor works and i can still drag windows around but framebuffer is frozen
https://bugs.kde.org/show_bug.cgi?id=385291 --- Comment #7 from Martin Flöser --- So from output: compositing is clearly not active. I fear this is a bug in a different stack. When compositing is not active the X server is responsible for rendering. That seems to not work any more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384765] Title bar: Blurry fonts and symbols with scaling factor
https://bugs.kde.org/show_bug.cgi?id=384765 Jan Wiele changed: What|Removed |Added CC||j...@wiele.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385556] documentation viewer window undocks and redocks seemingly at random across session restarts
https://bugs.kde.org/show_bug.cgi?id=385556 RJVB changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from RJVB --- An additional observation (unique hence anecdotal for now): 3 The documentation window opened automatically in floating mode when I closed a source document. I had used the context help "Show Documentation for QFoo" action, this opened a docked documentation window which I had closed by clicking on the toolbar "Documentation" button. 4 The floating window remained empty and I could only restore normal operation by removing the Documentation button from the toolbar and restoring it afterwards. I have seen that last issue before, but only when the floating window opens out uninvitedly so I think it's related. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385609] New: Switching from 3 column to 2 column view should show submodules in left column
https://bugs.kde.org/show_bug.cgi?id=385609 Bug ID: 385609 Summary: Switching from 3 column to 2 column view should show submodules in left column Product: systemsettings Version: 5.11.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: j...@wiele.org Target Milestone: --- Hi, I find it a bit confusing that the left column does not show the submodule view, when resizing the systemsettings window from fullscreeen to non-fullscreen (3 to 2 column layout). I have to reselect the item in the left column to start the transition to the submodule view. Steps to Reproduce 1) Start systemsettings 2) Make it a fullscreen window 3) Select item with submodules (e.g. "symbols") 4) Resize the window so that it switches to the two cloumn layout Actual Results: Left sidebar shows the main module Expected Results: Left sidebar shows the submodule entries -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385608] New: Main list jumps when scrolling (mostly down)
https://bugs.kde.org/show_bug.cgi?id=385608 Bug ID: 385608 Summary: Main list jumps when scrolling (mostly down) Product: systemsettings Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: w01dn...@gmail.com Target Milestone: --- There are small jumps (usually down) when scrolling main list (up or down doesn't matter). Well noted when scrolling with touchpad, it's very hard to scroll to the list top with touchpad as that jumps happen almost constantly. When mouse scroll is used jumps are present but not so badly. But mouse scroll is too slow (about 15-20px per scroll), but that's unrelated bug, I saw bugreport somewhere. Reproduce: 1. Open systemsettings. 2. Scroll main list using touchpad to the list bottom. 3. Scroll main list to list top. Expected results: Both 2nd and 3rd step work fine. Actual results: 2nd step works but scrolling is jagged. 3rd step is hard to achieve as scroll area jumps down. Scroll (using touchpad) in other QML dialogs (like plasma desktop settings) works fine. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385606] System Settings crashed after applying fonts changes.
https://bugs.kde.org/show_bug.cgi?id=385606 Alexander Popel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Alexander Popel --- Well, it seems like I fixed this by installing glib2-2.54.1-2. I just tried to fix Dolphin dialogs crashes, but it seems that this crash also happened because of dialog that System Settings invokes after applying font changes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385607] New: Panel drawn badly after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=385607 Bug ID: 385607 Summary: Panel drawn badly after resume from suspend Product: plasmashell Version: 5.8.7 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kdeb...@mkcollins.org Target Milestone: 1.0 Flags: Wayland-, X11-, VisualDesign- New bug in plasmashell 5.8.7 After resuming from suspend the bottom few pixels of the panel are black and also a small rectangle in the bottom right of the screen which obscures the last digit of the clock. Restarting plasmashell fixes it. I am running nouveau graphics driver. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=385594 lingtj...@hotmail.com changed: What|Removed |Added CC||lingtj...@hotmail.com --- Comment #2 from lingtj...@hotmail.com --- I can confirm, I observe the same behavior since the latest upgrade today to plasma 5.11 (Arch Linux) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385606] New: System Settings crashed after applying fonts changes.
https://bugs.kde.org/show_bug.cgi?id=385606 Bug ID: 385606 Summary: System Settings crashed after applying fonts changes. Product: systemsettings Version: 5.11.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: omerit...@airmail.cc Target Milestone: --- Application: systemsettings5 (5.11.0) Qt Version: 5.9.2 Frameworks Version: 5.38.0 Operating System: Linux 4.13.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Just picked another font in System Settings and applied. Crashes every time after changing at least one category (General, Small, Menu, etc.). The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6fc982a800 (LWP 3059))] Thread 5 (Thread 0x7f6f9b9e9700 (LWP 3066)): #0 0x7f6fbf075664 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f6fbf04d761 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f6fbf04ddf6 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f6fbf04dfae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f6fc5d9acf4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6fc5d3e48b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f6fc5b5727e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f6fc3bfdbc9 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f6fc5b5bfcb in () at /usr/lib/libQt5Core.so.5 #9 0x7f6fc121408a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f6fc546824f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f6fa2809700 (LWP 3064)): #0 0x7f6fbf0755f9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f6fbf04c81e in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f6fbf04de76 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f6fbf04dfae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f6fc5d9acf4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6fc5d3e48b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f6fc5b5727e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f6fc3bfdbc9 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f6fc5b5bfcb in () at /usr/lib/libQt5Core.so.5 #9 0x7f6fc121408a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f6fc546824f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f6fad27a700 (LWP 3062)): #0 0x7f6fbf075664 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f6fbf04dcac in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #2 0x7f6fbf04dd77 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f6fbf04dfae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f6fc5d9acf4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6fc5d3e48b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f6fc5b5727e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f6fc61b6376 in () at /usr/lib/libQt5DBus.so.5 #8 0x7f6fc5b5bfcb in () at /usr/lib/libQt5Core.so.5 #9 0x7f6fc121408a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f6fc546824f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f6fb64d2700 (LWP 3061)): #0 0x7f6fc545dd4b in poll () at /usr/lib/libc.so.6 #1 0x7f6fc1a978e0 in () at /usr/lib/libxcb.so.1 #2 0x7f6fc1a99679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f6fb906d85a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f6fc5b5bfcb in () at /usr/lib/libQt5Core.so.5 #5 0x7f6fc121408a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f6fc546824f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f6fc982a800 (LWP 3059)): [KCrash Handler] #5 0x7f6fc5400d4a in __strcmp_sse2_unaligned () at /usr/lib/libc.so.6 #6 0x7f6fbf02a4ba in g_str_equal () at /usr/lib/libglib-2.0.so.0 #7 0x7f6fbf02bd8c in g_hash_table_lookup () at /usr/lib/libglib-2.0.so.0 #8 0x7f6fbf009d9f in g_quark_from_static_string () at /usr/lib/libglib-2.0.so.0 #9 0x7f6f8a80eca5 in () at /usr/lib/libgobject-2.0.so.0 #10 0x7f6fc965f57a in call_init.part () at /lib64/ld-linux-x86-64.so.2 #11 0x7f6fc965f686 in _dl_init () at /lib64/ld-linux-x86-64.so.2 #12 0x7f6fc9663b5e in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #13 0x7f6fc54a3f14 in _dl_catch_error () at /usr/lib/libc.so.6 #14 0x7f6fc966337a in _dl_open () at /lib64/ld-linux-x86-64.so.2 #15 0x7f6fbf300e86 in () at /usr/lib/libdl.so.2 #1
[digikam] [Bug 385592] digikam segfaults occasionally, when renaming/moving multiple images
https://bugs.kde.org/show_bug.cgi?id=385592 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 385601] no "HTML" parameter in contact card in "Contact" tab
https://bugs.kde.org/show_bug.cgi?id=385601 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Laurent Montel --- Fixed in 17.08 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370676] Screenlock: no input widgets, loginctl unlock-session not working
https://bugs.kde.org/show_bug.cgi?id=370676 Pekka Helenius changed: What|Removed |Added CC||fince...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 385576] exporting organization contact to vcard 4 => name is _.vcf
https://bugs.kde.org/show_bug.cgi?id=385576 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel --- 17.12 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379345] Addons repository not load
https://bugs.kde.org/show_bug.cgi?id=379345 spa...@ymail.com changed: What|Removed |Added CC||spa...@ymail.com --- Comment #5 from spa...@ymail.com --- I see the same errors in Win7 64bit version. I am seeing the same bug now in the last 3 versions of KDENLIVE. For all addons from repos, Render, wipes, and Templates Also posted here: https://bugs.kde.org/show_bug.cgi?id=380055# I have searched many times, but cannot find a link to manualy download the files, and either the repo links are broken or were never valid. Suprised more people do not see this error. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380055] Configuration file is invalid
https://bugs.kde.org/show_bug.cgi?id=380055 spa...@ymail.com changed: What|Removed |Added CC||spa...@ymail.com --- Comment #1 from spa...@ymail.com --- Same errorn in Win7 64bit version. I am seeing the same bug now in the last 3 versions of KDENLIVE. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355747] New color adjustment filter
https://bugs.kde.org/show_bug.cgi?id=355747 wolthera changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/b3f9a490011abb5c7c717789 ||ba68c55f89897db8 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from wolthera --- Git commit b3f9a490011abb5c7c717789ba68c55f89897db8 by Wolthera van Hövell tot Westerflier. Committed on 11/10/2017 at 13:35. Pushed by woltherav into branch 'master'. [Feature] ASC-CDL color balance filter(Slope, Offset, Power) This is a simple color balance filter as decided by the American Society of Cinematographers. It's purpose is to make communicating color balance easier over different applications. It is also interesting in that it is so simple it does not clip high-bit depth values. There's still some issues with the filter, but they are mostly GUI issues, so I am pushing this to prevent bitrot. I have noted the possible list of improvements in the header of the widget class. Differential revision: https://phabricator.kde.org/D8184 CCMAIL:kimages...@kde.org M +1-0plugins/filters/CMakeLists.txt A +11 -0plugins/filters/asccdl/CMakeLists.txt A +127 -0plugins/filters/asccdl/kis_asccdl_filter.cpp [License: GPL (v2+)] A +61 -0plugins/filters/asccdl/kis_asccdl_filter.h [License: GPL (v2+)] A +103 -0plugins/filters/asccdl/kis_wdg_asccdl.cpp [License: GPL (v2+)] A +62 -0plugins/filters/asccdl/kis_wdg_asccdl.h [License: GPL (v2+)] A +9-0plugins/filters/asccdl/kritaasccdl.json A +105 -0plugins/filters/asccdl/wdg_asccdl.ui https://commits.kde.org/krita/b3f9a490011abb5c7c717789ba68c55f89897db8 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 385452] akonadi_baloo_indexer crash
https://bugs.kde.org/show_bug.cgi?id=385452 Christoph Feck changed: What|Removed |Added Assignee|unassigned-b...@kde.org |kdepim-b...@kde.org CC||chrig...@fastmail.fm, ||dvra...@kde.org Component|general |Indexer Version|unspecified |4.13 Product|kde |Akonadi -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 338669] GHNS dialog does not work, server newstuff.kde.org does not function properly
https://bugs.kde.org/show_bug.cgi?id=338669 --- Comment #5 from Harald Sitter --- On an additional note it seems we currently do not have ksysguard pages in the KDE store. It may be wise to get that set up and then use the store for content delivery. (instead of using some other random thing) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385605] New: Plasma crashed when Hard Disk Usage widget were added to right side vertical panel
https://bugs.kde.org/show_bug.cgi?id=385605 Bug ID: 385605 Summary: Plasma crashed when Hard Disk Usage widget were added to right side vertical panel Product: plasmashell Version: 5.11.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: episy...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.0) Qt Version: 5.9.2 Frameworks Version: 5.38.0 Operating System: Linux 4.13.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Removed Hard Disk Usage from vertical panel and placed a new one to vertical panel. After the crash widget was in place. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc12b319800 (LWP 744))] Thread 15 (Thread 0x7fc0357f0700 (LWP 2679)): #0 0x7fc12418138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc124fc345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc128d5e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc128d5ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc124fc1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7fc12417b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc1248ce24f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fc0362fd700 (LWP 1976)): #0 0x7fc12418138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc124fc345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc128d5e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc128d5ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc124fc1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7fc12417b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc1248ce24f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fc036dfe700 (LWP 1868)): #0 0x7fc12418138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc124fc345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc128d5e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc128d5ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc124fc1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7fc12417b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc1248ce24f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fc037fff700 (LWP 1659)): #0 0x7fc12418138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc124fc345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc128d5e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc128d5ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc124fc1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7fc12417b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc1248ce24f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fc050c77700 (LWP 903)): #0 0x7fc12418138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc124fc345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc128d5e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc128d5ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc124fc1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7fc12417b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc1248ce24f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fc052989700 (LWP 902)): #0 0x7fc12418138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc124fc345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc128d5e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc128d5ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc124fc1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7fc12417b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc1248ce24f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fc05378b700 (LWP 901)): #0 0x7fc12418138d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc124fc345c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc128d5e7ba in () at /usr/lib/libQt5Quick.so.5 #3 0x7fc128d5ec44 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc124fc1fcb in () at /usr/lib/libQt5Core.so.5 #5 0x7fc12417b08a in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fc1248ce24f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fc0588e0700 (LWP 900)): #0
[ksysguard] [Bug 338669] GHNS dialog does not work, server newstuff.kde.org does not function properly
https://bugs.kde.org/show_bug.cgi?id=338669 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Harald Sitter --- So, it appears to me ksysguard still has newstuff as knewstuff url, that service was however shut down IIRC. I am not quite sure what it should be using instead, but what it has right now is definitely wrong and broken in every release for the last couple of years. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 318078] PDF-links don't work as expected in text selection mode.
https://bugs.kde.org/show_bug.cgi?id=318078 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/oku ||lar/6d7403ff13871b068a121cd ||0afbb1ee1157ff375 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Albert Astals Cid --- Git commit 6d7403ff13871b068a121cd0afbb1ee1157ff375 by Albert Astals Cid, on behalf of Renato Araujo Oliveira Filho. Committed on 11/10/2017 at 13:03. Pushed by aacid into branch 'master'. Interact with hyperlinks in TextSelect mode Allow user to click on url while on any selection mode Based on https://git.reviewboard.kde.org/r/124961/ by Jake Linder Includes several autotests to try to minimize possible regressions as much as possible REVIEW: 130246 A +---autotests/data/pdf_with_links.pdf M +484 -10 autotests/parttest.cpp M +201 -104 ui/pageview.cpp M +4-0ui/pageview.h https://commits.kde.org/okular/6d7403ff13871b068a121cd0afbb1ee1157ff375 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385604] illegal hardware instruction (OpenCV cv::namedWindow)
https://bugs.kde.org/show_bug.cgi?id=385604 Sebastian Höffner changed: What|Removed |Added CC||shoeff...@uos.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385604] New: illegal hardware instruction (OpenCV cv::namedWindow)
https://bugs.kde.org/show_bug.cgi?id=385604
Bug ID: 385604
Summary: illegal hardware instruction (OpenCV cv::namedWindow)
Product: valgrind
Version: 3.14 SVN
Platform: Homebrew (Mac OS X)
OS: OS X
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: shoeff...@uos.de
Target Milestone: ---
When running valgrind on a simple program opening an OpenCV namedWindow
(https://docs.opencv.org/3.3.0/d7/dfc/group__highgui.html#ga5afdf8410934fd099df85c75b2e0888b),
it reports:
UNKNOWN workq_ops option 128
==88358== valgrind: Unrecognised instruction at address 0x10219bb50.
==88358==at 0x10219BB50: _dispatch_kq_init (in
/usr/lib/system/libdispatch.dylib)
(Full report and example code below)
It is not impossible that this is a bug on OpenCV's site.
Versions etc:
OS:
macOS Sierra 10.12.6 (MB Pro, 15inch, Mid 2015 / 2.8 GHz Intel Core i7)
Installed most things straight with brew package manager.
valgrind --version:
valgrind-3.14.0.SVN
(brew HEAD-16470)
clang --version:
Apple LLVM version 9.0.0 (clang-900.0.37)
Target: x86_64-apple-darwin16.7.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
pkg-config --modversion opencv:
3.3.0
ls /usr/lib/libstdc++.*:
/usr/lib/libstdc++.6.0.9.dylib
/usr/lib/libstdc++.6.dylib
/usr/lib/libstdc++.dylib
Example code: test.cpp:
```
#include "opencv2/highgui.hpp"
int main(const int argc, const char** const argv) {
cv::namedWindow("NamedWindow");
// while (true) if (cv::waitKey(1) != -1) break;
}
```
You might want to add the commented line to see the window in action when
running the program normally.
Compile commands:
```
clang -lstdc++ $(pkg-config --cflags --libs opencv) test.cpp -o test
```
Report (simple `valgrind ./test`):
```
==88358== Memcheck, a memory error detector
==88358== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==88358== Using Valgrind-3.14.0.SVN and LibVEX; rerun with -h for copyright
info
==88358== Command: ./test
==88358==
--88358-- run: /usr/bin/dsymutil "./test"
warning: no debug symbols in executable (-arch x86_64)
==88358== Syscall param msg->desc.port.name points to uninitialised byte(s)
==88358==at 0x1023AF34A: mach_msg_trap (in
/usr/lib/system/libsystem_kernel.dylib)
==88358==by 0x1023AE796: mach_msg (in
/usr/lib/system/libsystem_kernel.dylib)
==88358==by 0x1023A8485: task_set_special_port (in
/usr/lib/system/libsystem_kernel.dylib)
==88358==by 0x10254410E: _os_trace_create_debug_control_port (in
/usr/lib/system/libsystem_trace.dylib)
==88358==by 0x102544458: _libtrace_init (in
/usr/lib/system/libsystem_trace.dylib)
==88358==by 0x1020749DF: libSystem_initializer (in
/usr/lib/libSystem.B.dylib)
==88358==by 0x100018A1A:
ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) (in
/usr/lib/dyld)
==88358==by 0x100018C1D:
ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) (in
/usr/lib/dyld)
==88358==by 0x1000144A9:
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) (in /usr/lib/dyld)
==88358==by 0x100014440:
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) (in /usr/lib/dyld)
==88358==by 0x100013523:
ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int,
ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) (in
/usr/lib/dyld)
==88358==by 0x1000135B8:
ImageLoader::runInitializers(ImageLoader::LinkContext const&,
ImageLoader::InitializerTimingList&) (in /usr/lib/dyld)
==88358== Address 0x104889a2c is on thread 1's stack
==88358== in frame #2, created by task_set_special_port (???:)
==88358==
--88358-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--88358-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--88358-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
UNKNOWN workq_ops option 128
==88358== valgrind: Unrecognised instruction at address 0x10219bb50.
==88358==at 0x10219BB50: _dispatch_kq_init (in
/usr/lib/system/libdispatch.dylib)
==88358==by 0x1021998FB: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==88358==by 0x1021998B8: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
==88358==by 0x10219BA90: _dispatch_kq_update (in
/usr/lib/system/libdispatch.dylib)
==88358==by 0x10219D0CD: _dispatch_kevent_resume (in
/usr/lib/system/libdispatch.dylib)
==88358==by 0x10219D03D: _dispatch_source_kevent_resume (in
/usr/lib/system/libdispatch.dylib)
==88358==by 0x10219CE85: _dispatch_source_kevent_register (in
/usr/lib/system/libdis
[kscreenlocker] [Bug 385603] New: Unlock screen text near top of screen got cropped when font dpi is at 120 vs default 96
https://bugs.kde.org/show_bug.cgi?id=385603 Bug ID: 385603 Summary: Unlock screen text near top of screen got cropped when font dpi is at 120 vs default 96 Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: shawnbo...@yahoo.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- I have my font forced at 120 dpi due to high resolution on a 11.6" display. When unlocking the screen, the text look bigger but the top of the screen text is cropped. The displayed time is almost completely cropped off the screen. I tried to include a screen shot but can't seem to get one on the lock screen using the Print Screen key. I'm sure this is something easy to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385602] New: Add option to show volume level in OSD
https://bugs.kde.org/show_bug.cgi?id=385602 Bug ID: 385602 Summary: Add option to show volume level in OSD Product: plasma-pa Version: 5.10.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: petr.ne...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 108283 --> https://bugs.kde.org/attachment.cgi?id=108283&action=edit volume-osd I would like to see the current volume level in OSD because I often use my headset in noisy environment. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 385094] "copy medium" icon is missing on Gnome
https://bugs.kde.org/show_bug.cgi?id=385094 --- Comment #2 from Christoph Feck --- The QPA for the Gnome platform probably does not look up application-local icons. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 385601] New: no "HTML" parameter in contact card in "Contact" tab
https://bugs.kde.org/show_bug.cgi?id=385601 Bug ID: 385601 Summary: no "HTML" parameter in contact card in "Contact" tab Product: kaddressbook Version: 5.5.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: philippe.roub...@free.fr CC: to...@kde.org Target Milestone: --- opensuse 42.3 there is no "HTML" parameter in contact card in "Contact" tab -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385600] New: Reverse Clip function make kdenlive crashes immediately
https://bugs.kde.org/show_bug.cgi?id=385600 Bug ID: 385600 Summary: Reverse Clip function make kdenlive crashes immediately Product: kdenlive Version: 17.08.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: maizuddi...@gmail.com Target Milestone: --- kdenlive crashes after I want to make one of the clip reverse. here is a gif of the moment, when it crashes https://tenor.com/view/gif-9971674 and here is the output from terminal https://hastebin.com/ajimerefod -- You are receiving this mail because: You are watching all bug changes.
