[kate] [Bug 365259] 'Show Sstatusbar' no longer appears in settings menu
https://bugs.kde.org/show_bug.cgi?id=365259 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de Summary|'Show task bar' no longer |'Show Sstatusbar' no longer |appears in settings menu|appears in settings menu -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] New: Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 Bug ID: 365273 Summary: Invalid write to stack location reported after signal handler runs Product: valgrind Version: 3.11 SVN Platform: Compiled Sources URL: http://thread.gmane.org/gmane.comp.debugging.valgrind. devel/32601 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: earl_c...@yahoo.com A complete description of the observed failed is available on the link to the email thread. In summary, I believe that the problem is set up as follows: o Main thread consumes nearly all of its registered stack region o Signal is handled in the main thread (Linux will prefer to deliver to the main thread) o The signal frame causes the stack region to grow, but m_signal.c incorrectly records the base of the grown region o Another thread runs while the signal handler runs in the main thread, causing memcheck to become a little confused o The signal handler returns o An invalid write is observed in the main thread Reproducible: Always Steps to Reproduce: The following test program provides an example of the "Invalid write" message, though in a different context to that observed in the email thread. Actual Results: ==12529== Invalid write of size 4 ==12529==at 0x400E09C: _dl_fixup (dl-runtime.c:69) ==12529==by 0x40144BF: _dl_runtime_resolve (dl-trampoline.S:36) ==12529==by 0x8048768: main (in /home/earl/Development/valgrind/test) ==12529== Address 0xbeeccfb0 is on thread 1's stack ==12529== in frame #0, created by _dl_fixup (dl-runtime.c:66) Expected Results: The proposed patch silences the warnings from memcheck. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 365259] 'Show Statusbar' no longer appears in settings menu
https://bugs.kde.org/show_bug.cgi?id=365259 Burkhard Lueck changed: What|Removed |Added Summary|'Show Sstatusbar' no longer |'Show Statusbar' no longer |appears in settings menu|appears in settings menu -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 caulier.gil...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #43 from caulier.gil...@gmail.com --- The 64 bist installer is compiled with MXE under a dedicated bundle directory. 32 bits version is compiled in a separated bunde dir. Nothing is mixed. I suspect a problem into MXE... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #1 from earl_c...@yahoo.com --- Created attachment 99958 --> https://bugs.kde.org/attachment.cgi?id=99958&action=edit This test program causes memcheck to generate an "Invalid write" warning. The test program was compiled on: Linux bambi 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:32:15 UTC 2015 i686 i686 i686 GNU/Linux Distributor ID:LinuxMint Description:Linux Mint 17 Qiana Release:17 Codename:qiana gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #2 from earl_c...@yahoo.com --- Created attachment 99959 --> https://bugs.kde.org/attachment.cgi?id=99959&action=edit This is the proposed patch to register the extended stack region when delivering a signal. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 342139] KDE 4.14.3 - Kontact when opening the first time shows only half the side bar in summary.
https://bugs.kde.org/show_bug.cgi?id=342139 --- Comment #9 from staka...@freenet.de --- it also helps (as usual) to detach the window from full-screen and then to go back to full screen. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 earl_c...@yahoo.com changed: What|Removed |Added Attachment #99959|0 |1 is obsolete|| Attachment #99959|1 |0 is patch|| --- Comment #3 from earl_c...@yahoo.com --- Comment on attachment 99959 --> https://bugs.kde.org/attachment.cgi?id=99959 This is the proposed patch to register the extended stack region when delivering a signal. Sorry, I copied this from gmane, and the text is broken. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #4 from earl_c...@yahoo.com --- Created attachment 99960 --> https://bugs.kde.org/attachment.cgi?id=99960&action=edit This is the proposed patch to register the extended stack region when delivering a signal. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 295571] Mouse wheel scrolling in Dolphin ignores global setting
https://bugs.kde.org/show_bug.cgi?id=295571 H.H. changed: What|Removed |Added CC||cyberb...@gmx.de --- Comment #21 from H.H. --- For me this bug still exists in dolphin 16.04.2. I found 4 similar bugs about this: https://bugs.kde.org/show_bug.cgi?id=357618 (with a workaround by uninstalling "xf86-input-libinput") https://bugs.kde.org/show_bug.cgi?id=295571 https://bugs.kde.org/show_bug.cgi?id=291144 https://bugs.kde.org/show_bug.cgi?id=358080 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 --- Comment #13 from H.H. --- Also the mouse-speed setting is ignored (pointer acceleration) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364541] Icons in system tray popup are too small
https://bugs.kde.org/show_bug.cgi?id=364541 tom.zoeh...@gmail.com changed: What|Removed |Added CC||tom.zoeh...@gmail.com --- Comment #1 from tom.zoeh...@gmail.com --- Created attachment 99961 --> https://bugs.kde.org/attachment.cgi?id=99961&action=edit Tiny icons in system tray -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364541] Icons in system tray popup are too small
https://bugs.kde.org/show_bug.cgi?id=364541 --- Comment #2 from tom.zoeh...@gmail.com --- Since updating to plasma 5.7 the icons in the system tray are so tiny, they are impossible to read (see attached screenshot from a 24" monitor). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 336253] Create a New tag, Unconfirmed Faces [patch]
https://bugs.kde.org/show_bug.cgi?id=336253 Evert Vorster changed: What|Removed |Added CC||evert.vors...@yandex.com --- Comment #22 from Evert Vorster --- Just using the newest DigiKam 5.0.0 now, and this is still an issue. I have many faces detected in my thousands of photos. The method of finding photos without a tag does not work, as the photo gets a tag when there is another already tagged face in it. Really, we need a tag called unconfirmed face, and grouped by who the software thinks it is. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365274] New: KWin crashed when connecting second display
https://bugs.kde.org/show_bug.cgi?id=365274 Bug ID: 365274 Summary: KWin crashed when connecting second display Product: kwin Version: 5.6.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: denis.smirnov...@gmail.com Application: kwin_x11 (5.6.5) Qt Version: 5.5.1 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-28-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: Logged in with one display enabled (laptop display). Then plugged in secondary display. KWin instantly crashed (and restarted with two displays enabled). The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f286723d900 (LWP 2912))] Thread 5 (Thread 0x7f283bfff700 (LWP 4545)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f28652e5aeb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1e42cc0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x1e42bf0, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f286008892e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7f28600891b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f28652e484e in QThreadPrivate::start (arg=0x1e42b70) at thread/qthread_unix.cpp:331 #6 0x7f2860a436fa in start_thread (arg=0x7f283bfff700) at pthread_create.c:333 #7 0x7f2866d34b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f283b014700 (LWP 2966)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2864468bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f2864468c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f2860a436fa in start_thread (arg=0x7f283b014700) at pthread_create.c:333 #4 0x7f2866d34b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f2847fff700 (LWP 2939)): #0 0x7f2866d2ad13 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f286551710f in qt_safe_select (nfds=12, fdread=fdread@entry=0x7f283c000a78, fdwrite=fdwrite@entry=0x7f283c000d08, fdexcept=fdexcept@entry=0x7f283c000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f2865518c0e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f283c000f98, writefds=0x7f283c000d08, readfds=0x7f283c000a78, nfds=, this=0x7f283c0008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f283c0008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f286551913e in QEventDispatcherUNIX::processEvents (this=0x7f283c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f28654c2dea in QEventLoop::exec (this=this@entry=0x7f2847ffeca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f28652df8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f285fb9f3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f28652e484e in QThreadPrivate::start (arg=0x1957da0) at thread/qthread_unix.cpp:331 #9 0x7f2860a436fa in start_thread (arg=0x7f2847fff700) at pthread_create.c:333 #10 0x7f2866d34b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f284fe48700 (LWP 2916)): #0 0x7f2866d28e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2865026c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f28650288d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2850d28629 in QXcbEventReader::run (this=0x175fe60) at qxcbconnection.cpp:1253 #4 0x7f28652e484e in QThreadPrivate::start (arg=0x175fe60) at thread/qthread_unix.cpp:331 #5 0x7f2860a436fa in start_thread (arg=0x7f284fe48700) at pthread_create.c:333 #6 0x7f2866d34b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f286723d900 (LWP 2912)): [KCrash Handler] #6 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:69 #7 0x7f28605f07b6 in KWin::GLVertexBuffer::setData (this=this@entry=0x18da480, vertexCount=24, dim=dim@entry=2, vertices=0x1c00ce8, texcoords=texcoords@entry=0x0) at /build/kwin-5IHWGx/kwin-5.6.5/libkwineffects/kwinglutils.cpp:2056 #8 0x7f28668daa2e in KWin::SceneOpenGL2::doPaintBackground (this=0x18e6ce0, vertices=...) at /build/kwin-5IHWGx/kwin-5.6.5/scene_opengl.cpp:
[plasmashell] [Bug 365275] New: no MPRIS controls in taskbar tooltips in 5.7
https://bugs.kde.org/show_bug.cgi?id=365275 Bug ID: 365275 Summary: no MPRIS controls in taskbar tooltips in 5.7 Product: plasmashell Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: aro...@archlinux.org CC: plasma-b...@kde.org The MPRIS controls in taskbar tooltips are not appearing in Plasma 5.7. This worked fine in the beta, and downgrading plasma-desktop to 5.6.95 fixes it, so it's a recent regression. The media control applet works fine. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 336253] Create a New tag, Unconfirmed Faces [patch]
https://bugs.kde.org/show_bug.cgi?id=336253 caulier.gil...@gmail.com changed: What|Removed |Added Version|4.10.0 |5.0.0 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 356943] Random albums track progression ignores disc number
https://bugs.kde.org/show_bug.cgi?id=356943 --- Comment #1 from jaroslav.tu...@gmail.com --- Maybe a special case of this bug. After about 15 hours of playback with the correct behavior for the Random Albums progression, Amarok now plays only the first track of an album and then jumps to another album, again playing only the first track, and so on... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #44 from caulier.gil...@gmail.com --- I think i find the bug. It's in Python script which collect shared dlls used by a binary file. On top of script (line 42) we set pathes where dlls can be found (default_path_prefixes) : https://quickgit.kde.org/?p=digikam-software-compilation.git&a=blob&f=project%2Fmxe%2Frll.py As both win32 and win64 are computed in parallel, you can imagine the possible mix. The problem must not touch the 32 bits as 32 bits paths are in first on the list, but with 64 bits... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 365248] Krunner crash when typing first letter or clicking setting button
https://bugs.kde.org/show_bug.cgi?id=365248 Pavel changed: What|Removed |Added CC||zol...@gmail.com --- Comment #1 from Pavel --- Have the same issue. My stack trace from journalctl Process 2060 (kcmshell5) of user 1000 dumped core. Stack trace of thread 2060: #0 0x7f144f8bbd76 strlen (libc.so.6) #1 0x7f144f8bbaae __strdup (libc.so.6) #2 0x7f14318695c9 _ZN10CalculatorC1Ev (libqalculate.so.5) #3 0x7f1431bc2c4d n/a (krunner_calculatorrunner.so) #4 0x7f1431bc3f19 n/a (krunner_calculatorrunner.so) #5 0x7f1431bc5a7f n/a (krunner_calculatorrunner.so) #6 0x7f144e9aa564 _ZN14KPluginFactory6createEPKcP7QWidgetP7QObjectRK5QListI8QVariantERK7QString (libKF5CoreAd #7 0x7f143253817f n/a (libKF5Runner.so.5) #8 0x7f14325395a4 n/a (libKF5Runner.so.5) #9 0x7f14325330d7 _ZN6Plasma13RunnerManager19reloadConfigurationEv (libKF5Runner.so.5) #10 0x7f143274a771 n/a (kcm_plasmasearch.so) #11 0x7f143274f128 n/a (kcm_plasmasearch.so) #12 0x7f144e9aa564 _ZN14KPluginFactory6createEPKcP7QWidgetP7QObjectRK5QListI8QVariantERK7QString (libKF5CoreAd #13 0x7f144f6046b7 _ZN14KCModuleLoader10loadModuleERK12KCModuleInfoNS_14ErrorReportingEP7QWidgetRK11QStringLis #14 0x7f144f60d79f n/a (libKF5KCMUtils.so.5) #15 0x7f144f60e395 _ZNK13KCModuleProxy10realModuleEv (libKF5KCMUtils.so.5) #16 0x7f144f60981b _ZN13KCMultiDialog9addModuleERK12KCModuleInfoP15KPageWidgetItemRK11QStringList (libKF5KCMUt #17 0x7f144fbe6b81 kdemain (libkdeinit5_kcmshell5.so) #18 0x7f144f85e741 __libc_start_main (libc.so.6) #19 0x00400779 _start (kcmshell5) Don't know, what's wrong with libqalculate :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365275] no MPRIS controls for Amarok in taskbar tooltips in 5.7
https://bugs.kde.org/show_bug.cgi?id=365275 Antonio Rojas changed: What|Removed |Added Summary|no MPRIS controls in|no MPRIS controls for |taskbar tooltips in 5.7 |Amarok in taskbar tooltips ||in 5.7 --- Comment #1 from Antonio Rojas --- After some more testing, this seems to affect only Amarok. I've bisected it to commit 0d6442d in plasma-desktop -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 365244] When you open KDE connect via the icon in the taskbar you can't close it by clicking it again.
https://bugs.kde.org/show_bug.cgi?id=365244 Albert Vaca changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Albert Vaca --- It works in the latest version. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 365244] When you open KDE connect via the icon in the taskbar you can't close it by clicking it again.
https://bugs.kde.org/show_bug.cgi?id=365244 --- Comment #2 from Albert Vaca --- *Which will be 1.0 and should be released soon. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #45 from caulier.gil...@gmail.com --- Git commit 5522bf6707a745e8a1bfc712a19aa99654fba6b6 by Gilles Caulier. Committed on 09/07/2016 at 09:48. Pushed by cgilles into branch 'master'. pass the path to current MXE intall prefix to Python script use to collect dlls. This must prevent mix of 32 and 64 bits dlls with 64 bits installer. M +2-2project/mxe/04-build-installer.sh M +1-1project/mxe/config.sh M +13 -9project/mxe/rll.py http://commits.kde.org/scratch/mwiesweg/digikam-sc/5522bf6707a745e8a1bfc712a19aa99654fba6b6 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 365248] Krunner crash when typing first letter or clicking setting button
https://bugs.kde.org/show_bug.cgi?id=365248 syncrt...@gmail.com changed: What|Removed |Added CC||syncrt...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #46 from caulier.gil...@gmail.com --- New digiKam 5.0.0-2 64 bits installer : https://drive.google.com/open?id=0BzeiVr-byqt5S2Izd1ZkMTA1dnM Please install and report if all is fine now... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #5 from Philippe Waroquiers --- Compiled the program on an x86 debian 8.5 and an amd64 debian 7.9. Tried with several valgrind versions, but could not reproduce any write error. Can you run with the traces -v -v -v -d -d -d --trace-signals=yes and attach the resulting trace. Can you attach the trace both with and without your patch ? Thanks -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5
https://bugs.kde.org/show_bug.cgi?id=354082 --- Comment #17 from Viktor Kuzmin --- Already done. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #6 from Philippe Waroquiers --- Just to be sure to be complete, please also add --trace-signals=yes Thanks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365273] Invalid write to stack location reported after signal handler runs
https://bugs.kde.org/show_bug.cgi?id=365273 --- Comment #7 from Philippe Waroquiers --- Humph, I mean: Just to be sure to be complete, please also add --trace-syscalls=yes -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 365276] New: Selecting/deleting an article does not work if 'search article' box has focus
https://bugs.kde.org/show_bug.cgi?id=365276 Bug ID: 365276 Summary: Selecting/deleting an article does not work if 'search article' box has focus Product: akregator Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: get.so...@gmail.com Pressing Delete to delete an article while the 'search articles' text box has focus does not work. In general, I think there's some bigger problem with the way the article list widget and the feeds list widget gets focus. The colour of the selected item in both of these widgets is duller than the usual colour used for selected items. If you doubleclick an item in the feeds list, the feed's name becomes editable and then the item's background colour resembles that of a properly selected item. Reproducible: Always Steps to Reproduce: 1. Select any feed to display the list of articles 2. Select any article to read it in the preview pane 3. Click on the 'search articles' text box 4. Select some other article 5. Notice that the focus is still on the search text box 6. Try to delete the selected article by pressing delete key 7. Nothing happens because the search text box still has the focus 8. The only way to get out is to click somewhere in the preview pane to shift focus out of the search text box and then press Delete key Akregator version: 5.2.2 Using: KDE Frameworks 5.23.0 Qt 5.6.0 (built against 5.6.0) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played
https://bugs.kde.org/show_bug.cgi?id=358223 Camille changed: What|Removed |Added CC||camille.mou...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365277] New: Vertical vs. horizontal scrolling
https://bugs.kde.org/show_bug.cgi?id=365277 Bug ID: 365277 Summary: Vertical vs. horizontal scrolling Product: plasma-pa Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: codestr...@posteo.org CC: plasma-b...@kde.org Created attachment 99962 --> https://bugs.kde.org/attachment.cgi?id=99962&action=edit screenshot with scrollbar I observed two minor things: 1) As seen on the screenshot the vertical scrollbar would not be needed if the applet would gain a little more height. 2) When I use the scrollwheel between the horizontal sliders and the view starts to scroll, then suddenly the scroll events are picked up from the horizontal slider the mouse is then over. I would find it more intuitive that if I start scrolling vertically that it does not switch to the horizontal slider, though I suspect that is tricky to implement. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 365278] New: gwenview crashes wihle opening a image form trash://
https://bugs.kde.org/show_bug.cgi?id=365278 Bug ID: 365278 Summary: gwenview crashes wihle opening a image form trash:// Product: gwenview Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: tho@gmx.net CC: myr...@kde.org Application: gwenview (16.04.2) Qt Version: 5.6.0 Frameworks Version: 5.23.0 Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: gwenview crashes wihle opening a image form trash:// - 100% reproducible! -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3bcc6e99c0 (LWP 8679))] Thread 2 (Thread 0x7f3bc1bdf700 (LWP 8681)): #0 0x7f3bdaa7532d in poll () at /lib64/libc.so.6 #1 0x7f3bd6bf1a46 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f3bd6bf1b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f3bdb87965b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f3bdb828a6a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f3bdb688a03 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f3bdbf743b9 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f3bdb68d03a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f3bd94a15ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f3bdaa80ead in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f3bcc6e99c0 (LWP 8679)): [KCrash Handler] #6 0x7f3bdcf8c2c5 in QGraphicsItemPrivate::invalidateParentGraphicsEffectsRecursively() () at /lib64/libQt5Widgets.so.5 #7 0x7f3bdcf971b5 in QGraphicsItem::update(QRectF const&) () at /lib64/libQt5Widgets.so.5 #8 0x7f3be2b7a49d in Gwenview::RasterImageView::updateImageRect(QRect const&) () at /lib64/libgwenviewlib.so.5 #9 0x7f3be2be54d9 in Gwenview::RasterImageView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /lib64/libgwenviewlib.so.5 #10 0x7f3bdb852012 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #11 0x7f3be2be26f5 in Gwenview::Document::imageRectUpdated(QRect const&) () at /lib64/libgwenviewlib.so.5 #12 0x7f3bdb852012 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #13 0x7f3be2be23d2 in Gwenview::AbstractDocumentImpl::imageRectUpdated(QRect const&) () at /lib64/libgwenviewlib.so.5 #14 0x7f3be2b65d9b in Gwenview::DocumentLoadedImpl::init() () at /lib64/libgwenviewlib.so.5 #15 0x7f3be2b5aae5 in Gwenview::Document::switchToImpl(Gwenview::AbstractDocumentImpl*) () at /lib64/libgwenviewlib.so.5 #16 0x7f3be2b66ea8 in Gwenview::LoadingDocumentImpl::slotImageLoaded() () at /lib64/libgwenviewlib.so.5 #17 0x7f3bdb852012 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #18 0x7f3bdb685666 in QFutureWatcherBase::event(QEvent*) () at /lib64/libQt5Core.so.5 #19 0x7f3bdcca234c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #20 0x7f3bdcca752f in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #21 0x7f3bdb829bfa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #22 0x7f3bdb82bc9f in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #23 0x7f3bdb8795c3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #24 0x7f3bd6bf1703 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #25 0x7f3bd6bf1ab0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #26 0x7f3bd6bf1b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #27 0x7f3bdb87963f in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #28 0x7f3bdb828a6a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #29 0x7f3bdb8305fc in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #30 0x55878b7b1cd8 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5
https://bugs.kde.org/show_bug.cgi?id=354082 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #18 from Antonio Rojas --- (In reply to Viktor Kuzmin from comment #17) > Already done. Link, please? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 364687] Default device is not remembered
https://bugs.kde.org/show_bug.cgi?id=364687 Gregor Mi changed: What|Removed |Added CC||codestr...@posteo.org --- Comment #6 from Gregor Mi --- I use the audio output from my docking station as default device. This setting also gets lost sometimes. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365277] Vertical vs. horizontal scrolling
https://bugs.kde.org/show_bug.cgi?id=365277 --- Comment #1 from David Rosca --- 1) Yes, unfortunately cannot be resized from the applet itself, only you can manually resize it. 2) Yes, very tricky thanks to QML. I've tried to play with it and couldn't get acceptable solution. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365279] New: Hint text for assigning a Playback stream to another device
https://bugs.kde.org/show_bug.cgi?id=365279 Bug ID: 365279 Summary: Hint text for assigning a Playback stream to another device Product: plasma-pa Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: codestr...@posteo.org CC: plasma-b...@kde.org I like the new feature of assigning a Playback Stream to another output device via drag and drop. If I had not seen the latest Plasma promo video I doubt that I would have noticed this feature. Suggestion: A hint text could be placed below the list of playback streams. Something like "Start dragging the icon of a Playback Stream to assign it to another Output device". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365014] All windows hide on repeating desktop click
https://bugs.kde.org/show_bug.cgi?id=365014 boris64 changed: What|Removed |Added CC||bugs@boris64.net -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 365280] New: KMyMoney crashes when going to "Configure KMyMoney"
https://bugs.kde.org/show_bug.cgi?id=365280 Bug ID: 365280 Summary: KMyMoney crashes when going to "Configure KMyMoney" Product: kmymoney4 Version: 4.7.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: julius8...@gmail.com Application: kmymoney (4.7.2) KDE Platform Version: 4.14.21 Qt Version: 4.8.7 Operating System: Linux 4.6.2-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160626) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Using KMyMoney as usual and then I Clicked "Configure KMyMoney" The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f038b118975 in raise () at /lib64/libc.so.6 #7 0x7f038b119d8a in abort () at /lib64/libc.so.6 #8 0x7f038b1543d0 in __libc_message () at /lib64/libc.so.6 #9 0x7f038b159bd6 in malloc_printerr () at /lib64/libc.so.6 #10 0x7f038b15a3ae in _int_free () at /lib64/libc.so.6 #11 0x009e36f7 in KGPGFile::GPGAvailable() () #12 0x00888e24 in KSettingsGpg::KSettingsGpg(QWidget*) () #13 0x0057210b in KMyMoneyApp::slotSettings() () #14 0x005c91cb in () #15 0x7f038c1535c0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #16 0x7f038cbab242 in QAction::triggered(bool) () at /usr/lib64/libQtGui.so.4 #17 0x7f038cbac5a3 in QAction::activate(QAction::ActionEvent) () at /usr/lib64/libQtGui.so.4 #18 0x7f038d007dfd in () at /usr/lib64/libQtGui.so.4 #19 0x7f038d00c269 in () at /usr/lib64/libQtGui.so.4 #20 0x7f038da305c3 in KMenu::mouseReleaseEvent(QMouseEvent*) () at /usr/lib64/libkdeui.so.5 #21 0x7f038cc07970 in QWidget::event(QEvent*) () at /usr/lib64/libQtGui.so.4 #22 0x7f038d0104bb in QMenu::event(QEvent*) () at /usr/lib64/libQtGui.so.4 #23 0x7f038cbb111c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #24 0x7f038cbb9797 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #25 0x7f038d96722a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #26 0x7f038c13f2bd in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #27 0x7f038cbb77bb in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib64/libQtGui.so.4 #28 0x7f038cc3276d in () at /usr/lib64/libQtGui.so.4 #29 0x7f038cc30e9c in QApplication::x11ProcessEvent(_XEvent*) () at /usr/lib64/libQtGui.so.4 #30 0x7f038cc59d62 in () at /usr/lib64/libQtGui.so.4 #31 0x7f038687ce57 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #32 0x7f038687d0c0 in () at /usr/lib64/libglib-2.0.so.0 #33 0x7f038687d16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #34 0x7f038c16f80e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #35 0x7f038cc59e36 in () at /usr/lib64/libQtGui.so.4 #36 0x7f038c13db8f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #37 0x7f038c13def5 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #38 0x7f038c143ae9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #39 0x0056e210 in () #40 0x0056b548 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365281] New: ksystemsettings5 powerdevilprofilesconfig module doesn't fit to height in standalone
https://bugs.kde.org/show_bug.cgi?id=365281 Bug ID: 365281 Summary: ksystemsettings5 powerdevilprofilesconfig module doesn't fit to height in standalone Product: systemsettings Version: 5.7.0 Platform: Other URL: http://i.imgur.com/Pvmuucr.png OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: housegregory...@gmail.com Hi, ksystemsettings powerdevilprofilesconfig module doesn't fit to my height (1366x768) in standalone case. Why window size is hardcoded? I even can't resize it :( That's why I need buy bigger monitor only for KF5/Plasma5 stuff. Dear developer, please don't do hardcode any windows size, thanks. P.S. well it sounds like someone should change or sell own laptop with mentioned resolution because of size-hardcoded windows :) Reproducible: Always Steps to Reproduce: 1. Find display with height 768 2. Run kcmshell5 powerdevilprofilesconfig 3. Try to find ok/cancel, apply :) Expected Results: Module window should fit to any display -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365282] New: Make "Audio Volume Settings" available from the applet
https://bugs.kde.org/show_bug.cgi?id=365282 Bug ID: 365282 Summary: Make "Audio Volume Settings" available from the applet Product: plasma-pa Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: codestr...@posteo.org CC: plasma-b...@kde.org I just rediscovered the Audio Volume Settings dialog (right-click on the Audio Volume applet) where I found the feature of increasing the volume to over 100 % which I read about some time ago. I think an "Advanced..." button which is placed maybe on the bottom of the applet popup-window would make this dialog easier discoverable. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5
https://bugs.kde.org/show_bug.cgi?id=354082 --- Comment #19 from Viktor Kuzmin --- https://bugreports.qt.io/browse/QTBUG-49452 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #47 from Alexandre Alapetite --- Thanks for the fast reaction, @Gilles. The installer https://drive.google.com/open?id=0BzeiVr-byqt5S2Izd1ZkMTA1dnM forks fine for me (Windows 10 x64): the installer defaults to the proper install location, and digiKam starts without crash, as well as Showfoto. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 354082] high cpu usage for screen redrawing with qt5.5
https://bugs.kde.org/show_bug.cgi?id=354082 --- Comment #20 from Viktor Kuzmin --- I had no time currently to investigate problem completely -> this patch is 'hack' for me right now. Will have more time next week. Anyway I have normal cpu usage in konsole (5-7% one core max) and I see no glitches. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365277] Vertical vs. horizontal scrolling
https://bugs.kde.org/show_bug.cgi?id=365277 --- Comment #2 from Gregor Mi --- 1) How can I manually resize it? I tried to use the left or right mouse button on the applet corners while holding Ctrl or Alt key. I thought resizing applets is currently not possible. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365277] Vertical vs. horizontal scrolling
https://bugs.kde.org/show_bug.cgi?id=365277 --- Comment #3 from David Rosca --- Default shortcut for window resizing in kwin is Alt+Right Click -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #48 from caulier.gil...@gmail.com --- Thanks for the report. In the same way, just to verify, i build 32 bits installer : https://drive.google.com/open?id=0BzeiVr-byqt5V3dtLTNKTjUwQmM Please test and report. If all is fine i will upload new installers to download area. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352729] No obvious mute button/tick box for all devices
https://bugs.kde.org/show_bug.cgi?id=352729 Gregor Mi changed: What|Removed |Added CC||codestr...@posteo.org --- Comment #1 from Gregor Mi --- On a related note: the program `pavucontrol` shows an indicator below a playback stream that shows the actual volume of the audio currently being played. This could help to visually identify the stream one wants to mute. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365283] New: Textual representation of the "Mute" state
https://bugs.kde.org/show_bug.cgi?id=365283 Bug ID: 365283 Summary: Textual representation of the "Mute" state Product: plasma-pa Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: codestr...@posteo.org CC: plasma-b...@kde.org I accidentally clicked the mute icon and I did not realized it at once because no audio was playing on this device. When I came back wondering why no audio is played I saw that the slider representing the output device is disabled. I first thought the hardware is somehow disabled. A bit later I found out to click the loudspeaker icon on the left side to unmute. I did not see that earlier because the "normal" and "muted" loudspeaker icons are visually quite similar at the given size. The red "minus" symbol looks like black for me. I have a green/red vision impairment to some degree which means the smaller a red (or green) area becomes the more it looks like gray. So, a textual representation of the muted state would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 365277] Vertical vs. horizontal scrolling
https://bugs.kde.org/show_bug.cgi?id=365277 --- Comment #4 from Gregor Mi --- Created attachment 99963 --> https://bugs.kde.org/attachment.cgi?id=99963&action=edit kwin settings Ah thanks. I found that my settings use the Meta key (for reference I attached a screenshot of location of these settings) -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 363540] detaching-member false positive if non-const reference is stored
https://bugs.kde.org/show_bug.cgi?id=363540 Sergio Martins changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 364974] Filtering on time since last played gives incorrect results for CDs
https://bugs.kde.org/show_bug.cgi?id=364974 --- Comment #4 from robert marshall --- No it's specific to a cd (any cd), I'd expect, when you set a filter to view all tracks played in the last hour, for amarok to show the tracks you have played in the past hour and no other tracks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 345045] MYSQL : images not displayed in album
https://bugs.kde.org/show_bug.cgi?id=345045 --- Comment #13 from swatilodh...@gmail.com --- Vincent, DigiKam 5.0.0 is out. Please see if you could still reproduce the problem and provide necessary updates, if any. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 364204] kactivitymanage segfaults too often.
https://bugs.kde.org/show_bug.cgi?id=364204 --- Comment #6 from Vladislav Kamenev --- KDE is unusable. 5.7 went from testing and bug still persists. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 142568] Digikam is really slow to load a RAW (.CR2) photo
https://bugs.kde.org/show_bug.cgi?id=142568 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 149874] Include dcraw version 8.77
https://bugs.kde.org/show_bug.cgi?id=149874 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 162490] dcraw-8.86 adds newer canon dslr with digic III support
https://bugs.kde.org/show_bug.cgi?id=162490 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 182611] segfault with Samsung S85 RAW images
https://bugs.kde.org/show_bug.cgi?id=182611 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 178760] Conversion of Canon .cr2 files broken as used in Darkroom
https://bugs.kde.org/show_bug.cgi?id=178760 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 218762] libraw is too old
https://bugs.kde.org/show_bug.cgi?id=218762 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 149328] Wish: Let libkdcraw use raw decoding options when generating thumbnails
https://bugs.kde.org/show_bug.cgi?id=149328 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 142055] Which whitebalance is used
https://bugs.kde.org/show_bug.cgi?id=142055 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 196271] libraw_alloc.h: error: The function "bzero" must have a prototype
https://bugs.kde.org/show_bug.cgi?id=196271 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 148561] Missing options in RAW conversion; terrible conversion of dark photos
https://bugs.kde.org/show_bug.cgi?id=148561 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 145482] libkdraw compile fails on Cygwin
https://bugs.kde.org/show_bug.cgi?id=145482 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 221542] build fails due to ambiguities
https://bugs.kde.org/show_bug.cgi?id=221542 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 226799] libkdcraw should use all CPU cores when converting images
https://bugs.kde.org/show_bug.cgi?id=226799 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|kde-imag...@kde.org |digikam-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329976] SCAN : digiKam does not update database after picture renaming
https://bugs.kde.org/show_bug.cgi?id=329976 swatilodh...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In||5.1.0 --- Comment #7 from swatilodh...@gmail.com --- This issue is not reproducible with 5.0.0 Feel free to reopen if you still face this and provide necessary updates, if any. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 304959] Advanced slideshow
https://bugs.kde.org/show_bug.cgi?id=304959 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Presentation Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED --- Comment #6 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #49 from Alexandre Alapetite --- With the installer https://drive.google.com/open?id=0BzeiVr-byqt5V3dtLTNKTjUwQmM both digiKam and Showfoto start fine in 32-bit, but the installer defaults to "C:\Program Files\digiKam\" which is the path for 64-bit software. Just for the record: %ProgramFiles% ==> C:\Program Files\ %ProgramFiles(x86)% ==> C:\Program Files (x86)\ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 299828] Changing folder on Digikam
https://bugs.kde.org/show_bug.cgi?id=299828 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |AlbumsView Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.1.0 --- Comment #7 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 304733] Crash after import new folder from USB-stick or after closing digiKam
https://bugs.kde.org/show_bug.cgi?id=304733 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Crash after import new |Crash after import new |folder from USB-stick or|folder from USB-stick or |after closing digikam (?) |after closing digiKam -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 304733] Crash after import new folder from USB-stick or after closing digikam (?)
https://bugs.kde.org/show_bug.cgi?id=304733 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.1.0 Component|general |Import --- Comment #5 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 212457] Crash after performing batch operation on JPG images
https://bugs.kde.org/show_bug.cgi?id=212457 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED Component|general |BatchQueueManager-Tool-Conv ||ert CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 313500] Crash during modify of a picture
https://bugs.kde.org/show_bug.cgi?id=313500 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED Component|general |ImageEditor --- Comment #5 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 285808] crash at startup (probably related to scan corrupted NEF images)
https://bugs.kde.org/show_bug.cgi?id=285808 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Database-Scan Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.1.0 --- Comment #15 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 300808] Crash while importing pictures
https://bugs.kde.org/show_bug.cgi?id=300808 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED Component|general |Import --- Comment #4 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 313966] crash when applying geolocation
https://bugs.kde.org/show_bug.cgi?id=313966 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Geolocation Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.1.0 --- Comment #4 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 217631] Crashed when I tried to upload from camera. First time user.
https://bugs.kde.org/show_bug.cgi?id=217631 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|BACKTRACE |FIXED Version Fixed In||5.1.0 CC||caulier.gil...@gmail.com Component|general |Import --- Comment #3 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 290966] digikam crashes after loading AVI file from Canon IXUS 75
https://bugs.kde.org/show_bug.cgi?id=290966 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Import Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED --- Comment #7 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 307690] digikam crashed adding files to collection
https://bugs.kde.org/show_bug.cgi?id=307690 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.1.0 Component|general |Import --- Comment #4 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 240318] digikam crashes on mov
https://bugs.kde.org/show_bug.cgi?id=240318 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Import Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED --- Comment #5 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 298547] digikam crashes, if pics of collections are changed externally
https://bugs.kde.org/show_bug.cgi?id=298547 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Database-Scan Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED --- Comment #13 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 223177] digiKam crashes when selecting a picture immediately after showing slideshow
https://bugs.kde.org/show_bug.cgi?id=223177 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|BACKTRACE |FIXED Version Fixed In||5.1.0 Component|general |SlideShow CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 300463] Digikam crashing after opening, possibly related to prior GIMP crash?
https://bugs.kde.org/show_bug.cgi?id=300463 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Database-Scan Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED --- Comment #7 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 234746] digikam crashes while looking a film in HD format .avi
https://bugs.kde.org/show_bug.cgi?id=234746 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|BACKTRACE |FIXED CC||caulier.gil...@gmail.com Component|general |Preview --- Comment #3 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #50 from caulier.gil...@gmail.com --- The install path is selected by NSIS installer depending of window architecture. Look line 100 of NSIS script : https://quickgit.kde.org/?p=digikam-software-compilation.git&a=blob&h=b084e410223a76887423337a7e9ae9487ed84ed3&hb=deaf44067a31158e5f0cb4a5a29f7ca26135bc49&f=project%2Fmxe%2Finstaller%2Fdigikam.nsi#l100 Here, with my Windows 7 32 bits the install path is really C:\Program Files\, not C:\Program Files (x86)\. This last path do not exist on the system. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364433] Crash when using Solve -> Add custom include path
https://bugs.kde.org/show_bug.cgi?id=364433 --- Comment #8 from Sven Brauch --- Git commit f74ec1e6ec16c7e58d34d7fae05867292370b00d by Sven Brauch. Committed on 09/07/2016 at 12:31. Pushed by brauch into branch '5.0'. Fix crash on closing the "missing include" wizard M +16 -9duchain/assistants/missingincludeassistant.cpp http://commits.kde.org/kdev-python/f74ec1e6ec16c7e58d34d7fae05867292370b00d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365284] New: Fault while using Workbench
https://bugs.kde.org/show_bug.cgi?id=365284 Bug ID: 365284 Summary: Fault while using Workbench Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: warleyfd...@yahoo.com.br CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.26-21-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Workbench ( MySQL ) stopped working and after that its launcher stopped also working. After, the Leap also started presenting problems. The panel disappeared but returned. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe148d867c0 (LWP 5153))] Thread 7 (Thread 0x7fe12b9d1700 (LWP 5207)): #0 0x7fe142283c8d in read () at /lib64/libc.so.6 #1 0x7fe13e9a6520 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe13e965d59 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe13e9661b8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe13e96633c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe142bb4d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe142b5bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fe14297d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fe145c91e18 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7fe14298232f in () at /usr/lib64/libQt5Core.so.5 #10 0x7fe141a910a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fe14228ffed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fe11e556700 (LWP 5209)): #0 0x7fe13e9a7684 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fe13e965860 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe13e966140 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe13e96633c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe142bb4d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe142b5bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe14297d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fe145c91e18 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fe14298232f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fe141a910a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fe14228ffed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fe11ccef700 (LWP 5213)): #0 0x7fe142283c8d in read () at /lib64/libc.so.6 #1 0x7fe13e9a6520 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe13e965d59 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe13e9661b8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe13e96633c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe142bb4d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe142b5bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fe14297d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fe145c91e18 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7fe14298232f in () at /usr/lib64/libQt5Core.so.5 #10 0x7fe141a910a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fe14228ffed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fe1171c2700 (LWP 5214)): #0 0x7fe141a9503f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe14846086b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fe148460899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fe141a910a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fe14228ffed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fe08fb47700 (LWP 5268)): #0 0x7fe13e9a7684 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fe13e965860 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe13e966140 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe13e96633c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe142bb4d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe142b5bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe14297d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fe14682d282 in () at /usr/lib64/libQt5Quick.so.5 #8 0x7fe14298232f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fe141a910a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fe14228ffe
[akregator] [Bug 365276] Selecting/deleting an article does not work if 'search article' box has focus
https://bugs.kde.org/show_bug.cgi?id=365276 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 364179] Kcolorchooser doesn't start
https://bugs.kde.org/show_bug.cgi?id=364179 Christoph Feck changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364433] Crash when using Solve -> Add custom include path
https://bugs.kde.org/show_bug.cgi?id=364433 Sven Brauch changed: What|Removed |Added Latest Commit||http://commits.kde.org/kdev ||platform/7cac941ea94fff5fff ||da448030f5f9ef105fc3e2 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #9 from Sven Brauch --- Git commit 7cac941ea94fff5fffda448030f5f9ef105fc3e2 by Sven Brauch. Committed on 09/07/2016 at 12:46. Pushed by brauch into branch 'master'. Project controller: make displaying project config dialog async M +12 -12 shell/projectcontroller.cpp http://commits.kde.org/kdevplatform/7cac941ea94fff5fffda448030f5f9ef105fc3e2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364433] Crash when using Solve -> Add custom include path
https://bugs.kde.org/show_bug.cgi?id=364433 Sven Brauch changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev |platform/7cac941ea94fff5fff |elop/002fbc583524bbb662f47f |da448030f5f9ef105fc3e2 |cdbcbd0395f007a738 --- Comment #10 from Sven Brauch --- Git commit 002fbc583524bbb662f47fcdbcbd0395f007a738 by Sven Brauch. Committed on 09/07/2016 at 12:48. Pushed by brauch into branch '5.0'. IADM: Show config dialog asynchroneously M +9-7 languages/plugins/custom-definesandincludes/noprojectincludesanddefines/noprojectincludepathsmanager.cpp http://commits.kde.org/kdevelop/002fbc583524bbb662f47fcdbcbd0395f007a738 -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 364934] How to disable touchpad after Login
https://bugs.kde.org/show_bug.cgi?id=364934 Christoph Feck changed: What|Removed |Added Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364433] Crash when using Solve -> Add custom include path
https://bugs.kde.org/show_bug.cgi?id=364433 --- Comment #11 from Sven Brauch --- This should do. I do however still not understand why the but originally happened ... valgrind doesn't tell me much either :/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 270808] KDE should spin-down external hard disks when 'safely removed'
https://bugs.kde.org/show_bug.cgi?id=270808 David Polák changed: What|Removed |Added CC||davidp2...@gmail.com --- Comment #34 from David Polák --- I am affected by this bug, HDD spins down and then right back up again and shows up in Device Notifier. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364433] Crash when using Solve -> Add custom include path
https://bugs.kde.org/show_bug.cgi?id=364433 Sven Brauch changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev |elop/002fbc583524bbb662f47f |platform/80bb2205945f53f683 |cdbcbd0395f007a738 |c96a38715f185965944ae1 --- Comment #12 from Sven Brauch --- Git commit 80bb2205945f53f683c96a38715f185965944ae1 by Sven Brauch. Committed on 09/07/2016 at 12:58. Pushed by brauch into branch '5.0'. Project controller: make displaying project config dialog async M +12 -12 shell/projectcontroller.cpp http://commits.kde.org/kdevplatform/80bb2205945f53f683c96a38715f185965944ae1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356035] Panel does not refresh/update/animate when compositor is off
https://bugs.kde.org/show_bug.cgi?id=356035 Stathis changed: What|Removed |Added CC||stath...@gmail.com --- Comment #5 from Stathis --- I have this problem too... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365267] Kwin crashes after adding a new system tray and moving it, displays wrong dialogue
https://bugs.kde.org/show_bug.cgi?id=365267 --- Comment #4 from Jens Reuterberg --- (In reply to Thomas Lübking from comment #3) > Sounds much more like a plasmashell issue - shell and compositor seem to be > running on the screenshots. Ah cheers Thomas (it was five in the morning and I had slept two hours when I did this bugreport so a bit saucy in the head) Also the same applies to my desktop, tested it there to, will test it on another distro as well later to see if it exists there. -- You are receiving this mail because: You are watching all bug changes.
