[kipiplugins] [Bug 363913] Improve export menu structure

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=363913

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In|5.0.0   |

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 101455] Wish: Make it possible to enter numbers with 2 digit precision in RAW converter dialog.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=101455

caulier.gil...@gmail.com changed:

   What|Removed |Added

Product|kipiplugins |digikam
  Component|general |BatchQueueManager-Tool-RAWP
   ||rocessing
 CC||caulier.gil...@gmail.com
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 93161] Do'nt use i18n texts as a config value.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=93161

caulier.gil...@gmail.com changed:

   What|Removed |Added

Product|kipiplugins |digikam
Version|0.1.3   |unspecified
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
  Component|general |Searches-Fuzzy

-- 
You are receiving this mail because:
You are watching all bug changes.

[libkipi] [Bug 348333] kipicmd crashes if I click Cancel while resizing images

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=348333

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|general |General
Version|4.10.0  |unspecified
Product|kipiplugins |libkipi

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382142] New: Panel icon wrong: Does not match window icon

[Ralf Jung]

https://bugs.kde.org/show_bug.cgi?id=382142

Bug ID: 382142
   Summary: Panel icon wrong: Does not match window icon
   Product: plasmashell
   Version: 5.8.7
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: p...@ralfj.de
  Target Milestone: 1.0

Created attachment 106513
  --> https://bugs.kde.org/attachment.cgi?id=106513=edit
Screenshot demonstrating the issue. Notice how the icon in the window does not
match the icon in the panel.

Plasma sometimes displays the wrong panel icon for Firefox Nightly.  The icon
shown in the top-left corner of the window is correct, so I assume that the
application is properly setting its window properties -- but Plasma, for some
reason, decides to use the "normal" Firefox icon rather than the Firefox
Nightly icon for these windows.

I've already seen this happen some days ago, but then it was fixed by
restarting Firefox Nightly.  Now the bug has come back, and this time, restarts
do not help.

Unfortunately, I have no idea how Plasma picks the icon, so I don't know where
to start debugging.

This is with Debian testing amd64.

-- 
You are receiving this mail because:
You are watching all bug changes.

[calligrawords] [Bug 382141] New: Crash when changing BiDi text from 1 to 4 columns

[Brian Sakal]

https://bugs.kde.org/show_bug.cgi?id=382141

Bug ID: 382141
   Summary: Crash when changing BiDi text from 1 to 4 columns
   Product: calligrawords
   Version: 2.9.11
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: briansa...@gmail.com
  Target Milestone: ---

Application: calligrawords (2.9.11)
KDE Platform Version: 4.14.26
Qt Version: 4.8.7
Operating System: Linux 4.9.0-3-amd64 x86_64
Distribution: Debian GNU/Linux 9.0 (stretch)

-- Information about the crash:
- What I was doing when the application crashed:

I had typed 9 pages'-worth of text, without any fancy layouts or fonts (expect
that it was mixed BiDi text); and when I tried to change from the default
1-column to 4-column layout, it crashed. I tried this another two times, with
the same result.

The crash can be reproduced every time.

-- Backtrace:
Application: Calligra Words (calligrawords), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f4600d55a2c in QTextLine::y() const () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x7f45ff687782 in KoTextDocumentLayout::positionAnchorTextRanges(int,
int, QTextDocument const*) () from /usr/lib/libkotextlayout.so.14
#8  0x7f45ff670003 in KoTextLayoutArea::layoutBlock(FrameIterator*) () from
/usr/lib/libkotextlayout.so.14
#9  0x7f45ff672a4b in KoTextLayoutArea::layout(FrameIterator*) () from
/usr/lib/libkotextlayout.so.14
#10 0x7f45ff68576d in KoTextLayoutRootArea::layoutRoot(FrameIterator*) ()
from /usr/lib/libkotextlayout.so.14
#11 0x7f45ff688add in KoTextDocumentLayout::doLayout() () from
/usr/lib/libkotextlayout.so.14
#12 0x7f45ff689168 in KoTextDocumentLayout::layout() () from
/usr/lib/libkotextlayout.so.14
#13 0x7f46000df381 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x7f4600ae554c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#15 0x7f4600aec52c in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#16 0x7f460165de75 in KoApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkomain.so.14
#17 0x7f46000c4f1d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x7f46000c8a16 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x7f46000f5703 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#20 0x7f45fcaa47f7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f45fcaa4a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f45fcaa4b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f46000f5854 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x7f4600b8f5d6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x7f46000c37ef in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x7f46000c3b55 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x7f46000c9bd9 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x7f4601cb23b5 in kdemain () from
/usr/lib/kde4/libkdeinit/libkdeinit4_calligrawords.so
#29 0x7f46019302b1 in __libc_start_main (main=0x55db2696c780, argc=1,
argv=0x7ffc2ea41e88, init=, fini=,
rtld_fini=, stack_end=0x7ffc2ea41e78) at ../csu/libc-start.c:291
#30 0x55db2696c7ba in _start ()

Possible duplicates by query: bug 378424, bug 375011, bug 372670.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Mauro Carvalho Chehab]

https://bugs.kde.org/show_bug.cgi?id=368907

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #44 from Mauro Carvalho Chehab  ---
@Jan: thanks for identifying what part of Kaffeine was causing high CPU load!

Fixed on those two patches:

https://cgit.kde.org/kaffeine.git/commit/?id=7df55bf402a21778a945478ff44fca304fe06ab3:

dvbliveview: disable write ready notifications if nothing to write

The write notifier only makes sense if there's something to write.

Signed-off-by: Mauro Carvalho Chehab 

https://cgit.kde.org/kaffeine.git/commit/?id=a233d847ab7fdf13215f41e7240dcd307215ae42:

dvbliveview: better handle errors when writing to pipe

The current logic of writeToPipe() loops forever if an error
occurs. That causes CPU load to be 100%, as it will call write()
in non-block mode inside a loop until it succeeds. That's not
needed, as the write logic can already monitor the file descriptor
availability via QSocketNotifier.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381130

--- Comment #19 from personaldesignertec...@gmail.com ---
I know it's a minor bug, but isn't an LTS suppose to NOT have any glaring bugs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 382139] Sidebar button text unreadable on hover

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=382139

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

[Kirill A . Korinsky]

https://bugs.kde.org/show_bug.cgi?id=381815

--- Comment #4 from Kirill A. Korinsky  ---
Hey,

I can't trace valgrind because it calls fcntl over this code:
https://gist.github.com/catap/a20b8b1f46b0ba79b9f7297e73df0563

But I can run it in lldb ant provide some output to you.

With ulimit -n 1024:

➜  bin ulimit -n 1024
➜  bin env RETRACE_CONFIG=./retrace.conf.rnp
VALGRIND_LAUNCHER=/Users/catap/Documents/Riboseinc/valgrind/bin/executable_path=./valgrind
lldb -- ../lib/valgrind/memcheck-amd64-darwin /tmp/a.out
(lldb) target create "../lib/valgrind/memcheck-amd64-darwin"
Current executable set to '../lib/valgrind/memcheck-amd64-darwin' (x86_64).
(lldb) settings set -- target.run-args  "/tmp/a.out"
(lldb) b vgPlain_safe_fd
Breakpoint 1: where = memcheck-amd64-darwin`vgPlain_safe_fd + 18 at
m_libcfile.c:59, address = 0x000258081452
(lldb) r
Process 14822 launched: '../lib/valgrind/memcheck-amd64-darwin' (x86_64)
Process 14822 stopped
* thread #1, stop reason = breakpoint 1.1
frame #0: 0x000258081452 memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:59
   56   {
   57  Int newfd;
   58   
-> 59  vg_assert(VG_(fd_hard_limit) != -1);
   60   
   61  newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
   62  if (newfd != -1)
(lldb) n
Process 14822 stopped
* thread #1, stop reason = step over
frame #0: 0x0002580814ac memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:61
   58   
   59  vg_assert(VG_(fd_hard_limit) != -1);
   60   
-> 61  newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
   62  if (newfd != -1)
   63 VG_(close)(oldfd);
   64   
(lldb) n
Process 14822 stopped
* thread #1, stop reason = step over
frame #0: 0x0002580814ba memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:62
   59  vg_assert(VG_(fd_hard_limit) != -1);
   60   
   61  newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
-> 62  if (newfd != -1)
   63 VG_(close)(oldfd);
   64   
   65  /* Set the close-on-exec flag for this fd. */
(lldb) p newfd
(Int) $0 = 1024
(lldb) ^D


With ulimit 262144:

➜  bin env RETRACE_CONFIG=./retrace.conf.rnp
VALGRIND_LAUNCHER=/Users/catap/Documents/Riboseinc/valgrind/bin/executable_path=./valgrind
lldb -- ../lib/valgrind/memcheck-amd64-darwin /tmp/a.out
(lldb) target create "../lib/valgrind/memcheck-amd64-darwin"
Current executable set to '../lib/valgrind/memcheck-amd64-darwin' (x86_64).
(lldb) settings set -- target.run-args  "/tmp/a.out"
(lldb) b vgPlain_safe_fd
Breakpoint 1: where = memcheck-amd64-darwin`vgPlain_safe_fd + 18 at
m_libcfile.c:59, address = 0x000258081452
(lldb) r
Process 14653 launched: '../lib/valgrind/memcheck-amd64-darwin' (x86_64)
Process 14653 stopped
* thread #1, stop reason = breakpoint 1.1
frame #0: 0x000258081452 memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:59
   56   {
   57  Int newfd;
   58   
-> 59  vg_assert(VG_(fd_hard_limit) != -1);
   60   
   61  newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
   62  if (newfd != -1)
(lldb) n
Process 14653 stopped
* thread #1, stop reason = step over
frame #0: 0x0002580814ac memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:61
   58   
   59  vg_assert(VG_(fd_hard_limit) != -1);
   60   
-> 61  newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
   62  if (newfd != -1)
   63 VG_(close)(oldfd);
   64   
(lldb) n
Process 14653 stopped
* thread #1, stop reason = step over
frame #0: 0x0002580814ba memcheck-amd64-darwin`vgPlain_safe_fd(oldfd=3)
at m_libcfile.c:62
   59  vg_assert(VG_(fd_hard_limit) != -1);
   60   
   61  newfd = VG_(fcntl)(oldfd, VKI_F_DUPFD, VG_(fd_hard_limit));
-> 62  if (newfd != -1)
   63 VG_(close)(oldfd);
   64   
   65  /* Set the close-on-exec flag for this fd. */
(lldb) p newfd
(Int) $0 = -1
(lldb)

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 382140] New: Opening a file launches a new application window

[Pidh]

https://bugs.kde.org/show_bug.cgi?id=382140

Bug ID: 382140
   Summary: Opening a file launches a new application window
   Product: krita
   Version: 3.1.4
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: qamp...@hotmail.com
  Target Milestone: ---

When I double clicking a krita file from the windows explorer, instead of
opening in the same instance of application (new tab), it launches a new krita
window.

bug appears after upgrading to krita v3.1.4

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 382139] New: Sidebar button text unreadable on hover

[Ryan Aird]

https://bugs.kde.org/show_bug.cgi?id=382139

Bug ID: 382139
   Summary: Sidebar button text unreadable on hover
   Product: okular
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: r...@ryanaird.com
  Target Milestone: ---

Created attachment 106512
  --> https://bugs.kde.org/attachment.cgi?id=106512=edit
okular hover effect

It is very difficult to read the white text and on light blue background that
you get when hovering over a button such as thumbnails in the sidebar with the
default plasma 5 breeze theme. The button text should only turn from black to
white when the button is in the focused state and therefore has a deep blue
background. In any other state, the button text should remain black. See the
attached photo to get a better understanding of the issue. Occurs on 1.1.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 378262] krdb/kcminit sets wrong font for Qt4 applications on login

[boospy]

https://bugs.kde.org/show_bug.cgi?id=378262

--- Comment #11 from boospy  ---
When is it planed to go to kdeneon?

Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Damian Nowak]

https://bugs.kde.org/show_bug.cgi?id=356225

Damian Nowak  changed:

   What|Removed |Added

 CC||ofe...@nowaker.net

--- Comment #261 from Damian Nowak  ---
This bug is unfixable - it's been around for years and will be around for
years. Let's think of a workaround for it. An ability to save an existing panel
as template so it can be recreated with a single click at any later point would
make this bug pretty unrelevant. I reported this feature request here:
https://bugs.kde.org/show_bug.cgi?id=382138. If y'all think it's a good idea,
please upvote.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 169952] pictures on nfs-drive crashes digikam when i send picture as mail

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=169952

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|pictures on nfs-drive   |pictures on nfs-drive
   |crashes digikam when i send |crashes digikam when i send
   |picture as mail |picture as mail
   |(kipi-plugins/SendImages|
   |component)  |
   Version Fixed In||5.7.0
 CC||caulier.gil...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382138] Feature request: save existing panel as "template" - then available in "Add Panel" menu

[Damian Nowak]

https://bugs.kde.org/show_bug.cgi?id=382138

Damian Nowak  changed:

   What|Removed |Added

 CC||ofe...@nowaker.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 368779] Missing translations to Categories column in settings

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=368779

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|Missing translations to |Missing translations to
   |Categories column in Kipi   |Categories column in
   |Plugins settings|settings

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 116518] Use digiKam tool for displaying slideshows

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=116518

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|Use KIPI plugin for |Use digiKam tool for
   |displaying slideshows   |displaying slideshows

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 228056] digiKam doesn't autorotate images anymore

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=228056

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|digiKam doesn't autorotate  |digiKam doesn't autorotate
   |images anymore -|images anymore
   |kipi-plugin problem?|

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 114514] Do not delete the temporary folder after each encoding process.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=114514

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|Do not delete the temporary |Do not delete the temporary
   |folder  |folder after each encoding
   |"~/tmp/kde-user/kipi-mpegen |process.
   |coderplugin-PID/" after |
   |each encoding process.  |
 CC||caulier.gil...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382138] New: Feature request: save existing panel as "template" - then available in "Add Panel" menu

[Damian Nowak]

https://bugs.kde.org/show_bug.cgi?id=382138

Bug ID: 382138
   Summary: Feature request: save existing panel as "template" -
then available in "Add Panel" menu
   Product: plasmashell
   Version: master
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: ofe...@nowaker.net
  Target Milestone: 1.0

Created attachment 106511
  --> https://bugs.kde.org/attachment.cgi?id=106511=edit
Add Panel menu

When connecting and disconnecting monitors, panels move around and some even
disappear. It's been a problem since forever in KDE and is generally unfixable.
(https://bugs.kde.org/show_bug.cgi?id=356225). Instead of trying to fix
something that cannot be fixed, let's approach a problem from a different
angle.

I'd like to have an easy way to *recreate* a missing panel. An easy way would
be to *save* an existing panel as a "template", and then be able to recreate it
by right click on desktop, "Add Panel", and choosing the newly created template
(see attached image). A template panel would retain all the configuration -
widgets positioning and configuration.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevplatform] [Bug 382135] error: 'nodiscard' attribute cannot be applied to types

[Kevin Funk]

https://bugs.kde.org/show_bug.cgi?id=382135

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.1.2
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kde
   ||vplatform/94fca963169b9d442
   ||1acb5b4ab22a043aed29fea

--- Comment #1 from Kevin Funk  ---
Git commit 94fca963169b9d4421acb5b4ab22a043aed29fea by Kevin Funk.
Committed on 08/07/2017 at 23:00.
Pushed by kfunk into branch '5.1'.

Fix build with Qt 5.9.1 and clang

Summary:
Qt 5.9.1 expands Q_REQUIRED_RESULT to the `[[nodiscard]]` attribute
(see commit d254d8c19 in qtbase). This breaks the build with clang
compilers because `[[nodiscard]]` cannot be used at the end of a function
declaration:

```
error: 'nodiscard' attribute cannot be applied to types
```

For the record, GCC just issues a 'attribute ignored' warning when
`[[nodiscard]]` is used at the end of a declaration
FIXED-IN: 5.1.2

M  +1-1project/abstractfilemanagerplugin.cpp

https://commits.kde.org/kdevplatform/94fca963169b9d4421acb5b4ab22a043aed29fea

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 119070] difficult behaviour of MPEG slide slide show

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=119070

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|difficult behaviour of MPEG |difficult behaviour of MPEG
   |slide slide show kipi   |slide slide show
   |plugin  |

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 290932] Up to date website

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=290932

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|KIPI Plugins - up to date   |Up to date website
   |website |

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 170131] create dvd menu for a slide show

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=170131

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|WONTFIX

--- Comment #1 from caulier.gil...@gmail.com ---
This is not the goal of this tool to make authoring for DVD

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevplatform] [Bug 382107] kdevplatform FTBFS due to missing __cpu_model

[Kevin Funk]

https://bugs.kde.org/show_bug.cgi?id=382107

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Kevin Funk  ---
Already fixed in 5.1, but I didn't merge the patch to master yet. I just did
that.

commit d8410d4f2ac775d6bee657b8485bccf8c8da6e3f
Author: Kevin Funk 
Date:   Fri Jul 7 13:56:07 2017 +0200

welcomepage: Work-around GCC 5.x bug

Problem: plugins/welcomepage/welcomepageplugin.cpp:40: undefined
reference to `__cpu_model'

Fix: Explicitly link kdevwelcomepage shared lib against gcc and gcc_s as
suggested in https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1568899

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 194947] Original Image link is 'hidden' by css colour setting

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=194947

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|FIXED
   Version Fixed In||5.7.0

--- Comment #4 from caulier.gil...@gmail.com ---
Problem is not reproducible with current HTML Gallery tool implemented in
digiKam core version 5.7.0

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 219068] Export items to html gallery using tags doesn't sort by date or file-name

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=219068

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|FIXED
   Version Fixed In||5.7.0

--- Comment #4 from caulier.gil...@gmail.com ---
Problem is not reproducible with current HTML Gallery tool implemented in
digiKam core version 5.7.0

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 140374] HTML Gallery export fails to parse xml from non-UTF8 metadata in jpeg

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=140374

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|FIXED
   Version Fixed In||5.7.0

--- Comment #7 from caulier.gil...@gmail.com ---
Problem is not reproducible with current HTML Gallery tool implemented in
digiKam core version 5.7.0

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 342645] Export button inoperable

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=342645

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|FIXED
   Version Fixed In||5.7.0

--- Comment #2 from caulier.gil...@gmail.com ---
Problem is not reproducible with current HTML Gallery tool implemented in
digiKam core version 5.7.0

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 311510] HTML export crashing

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=311510

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|UNMAINTAINED|FIXED

--- Comment #15 from caulier.gil...@gmail.com ---
Problem is not reproducible with current HTML Gallery tool implemented in
digiKam core version 5.7.0

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 294062] Digikam crashes on HTML export

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=294062

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|FIXED
   Version Fixed In||5.7.0

--- Comment #9 from caulier.gil...@gmail.com ---
Problem is not reproducible with current HTML Gallery tool implemented in
digiKam core version 5.7.0

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 210228] Next button is disabled in html gallery

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=210228

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|FIXED
   Version Fixed In||5.7.0

--- Comment #7 from caulier.gil...@gmail.com ---
Problem is not reproducible with current HTML Gallery tool implemented in
digiKam core version 5.7.0

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382137] New: KDE Crashes Upon Quitting Lazarus IDE

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382137

Bug ID: 382137
   Summary: KDE Crashes Upon Quitting Lazarus IDE
   Product: plasmashell
   Version: 5.10.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: john4deidre2...@xtra.co.nz
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.3)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.8-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

i pressed the close icon on the Lazarus IDE window

- Unusual behavior I noticed:

After quitting Lazarus IDE KDE crashed, screent went black and the KDE desktop
and task bar were restarted without having to log back in.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ffa5b5328c0 (LWP 1907))]

Thread 9 (Thread 0x7ff984b82700 (LWP 2022)):
#0  0x7ffa4f860e17 in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#1  0x7ffa553cb75b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#2  0x7ffa55374d0a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#3  0x7ffa551a705a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#4  0x7ff98746bf37 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#5  0x7ffa551ab73e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7ffa5436a4e7 in start_thread () at /lib64/libpthread.so.0
#7  0x7ffa54ab8a2f in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7ff998f9a700 (LWP 2012)):
#0  0x7ffa4f8a5b54 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7ffa4f860cc6 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffa4f860e1c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffa553cb75b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffa55374d0a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffa551a705a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffa58ee6292 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7ffa551ab73e in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ffa5436a4e7 in start_thread () at /lib64/libpthread.so.0
#9  0x7ffa54ab8a2f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7ff9a27a9700 (LWP 2011)):
#0  0x7ffa543705ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff9aaee12fb in  () at /usr/lib64/dri/r600_dri.so
#2  0x7ff9aaee1037 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7ffa5436a4e7 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffa54ab8a2f in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7ff9a2faa700 (LWP 2010)):
#0  0x7ffa543705ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff9aaee12fb in  () at /usr/lib64/dri/r600_dri.so
#2  0x7ff9aaee1037 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7ffa5436a4e7 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffa54ab8a2f in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7ffa3592a700 (LWP 2009)):
#0  0x7ffa543705ed in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ffa5abeca04 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7ffa5abeca49 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7ffa5436a4e7 in start_thread () at /lib64/libpthread.so.0
#4  0x7ffa54ab8a2f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7ffa37bb2700 (LWP 2008)):
#0  0x7ffa54aaf08d in poll () at /lib64/libc.so.6
#1  0x7ffa4f860d09 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ffa4f860e1c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffa553cb75b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ffa55374d0a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ffa551a705a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ffa5832ed45 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7ffa551ab73e in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ffa5436a4e7 in start_thread () at /lib64/libpthread.so.0
#9  0x7ffa54ab8a2f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7ffa3d9ca700 (LWP 1994)):
#0  0x7ffa551a3c27 in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5
#1  0x7ffa553cb057 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7ffa4f860711 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ffa4f860cb0 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7ffa4f860e1c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7ffa553cb75b in
QEventDispatcherGlib::processEvents(QFlags) ()

[konsole] [Bug 380879] [Qt 5.9] Konsole tabbar does not have empty space at the right side anymore

[Kurt Hindenburg]

https://bugs.kde.org/show_bug.cgi?id=380879

Kurt Hindenburg  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED

--- Comment #11 from Kurt Hindenburg  ---
A temporary workaround is to use below

qdbus ${KONSOLE_DBUS_SERVICE} ${KONSOLE_DBUS_WINDOW} setTabWidthToText true

Also should test using a special .css file.

Obviously something else needs to be done.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 382081] Selection should only follow the mouse cursor when you move it.

[lctrgk]

https://bugs.kde.org/show_bug.cgi?id=382081

--- Comment #3 from lctrgk  ---
Thanks a lot for your answers. If you need for me to do anything that can help
you just tell me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 382136] New: KWin script KCM does not refresh after uninstalling scripts

[Fabian Vogt]

https://bugs.kde.org/show_bug.cgi?id=382136

Bug ID: 382136
   Summary: KWin script KCM does not refresh after uninstalling
scripts
   Product: kwin
   Version: 5.10.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: scripting
  Assignee: kwin-bugs-n...@kde.org
  Reporter: fab...@ritter-vogt.de
  Target Milestone: ---

- Open kwin script kcm
- Install a new script using GHNS
- Close the GHNS dialog -> new script shown
- Uninstall the script again
- Close the GHNS dialog -> new script still shown

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 381978] konsole applies scaling twice when using two HiDPI monitors and moving the konsole window away from primary screen

[Kurt Hindenburg]

https://bugs.kde.org/show_bug.cgi?id=381978

Kurt Hindenburg  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 380879] [Qt 5.9] Konsole tabbar does not have empty space at the right side anymore

[Kurt Hindenburg]

https://bugs.kde.org/show_bug.cgi?id=380879

Kurt Hindenburg  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|UPSTREAM|---

--- Comment #10 from Kurt Hindenburg  ---
Let's leave this open for now while I look at it and others can provide
comments.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 382116] konsole does not set KONSOLE_DBUS_WINDOW in sessions started with D-Bus

[Kurt Hindenburg]

https://bugs.kde.org/show_bug.cgi?id=382116

Kurt Hindenburg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kon
   ||sole/51cc49e95ebde8fde3f2ca
   ||ce9cf00cecf4b3da1e

--- Comment #2 from Kurt Hindenburg  ---
Git commit 51cc49e95ebde8fde3f2cace9cf00cecf4b3da1e by Kurt Hindenburg.
Committed on 08/07/2017 at 20:43.
Pushed by hindenburg into branch 'master'.

Set KONSOLE_DBUS_WINDOW for new sessions started with DBus

M  +4-0src/ViewManager.cpp

https://commits.kde.org/konsole/51cc49e95ebde8fde3f2cace9cf00cecf4b3da1e

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=381877

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #8 from Maik Qualmann  ---
Which libexiv2 version do you use, see digiKam component info? Please try the
beta AppImage from www.digikam.org to reproduce the error. Can you share a few
samples from the Olympus camera files?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381877

--- Comment #7 from giggi1...@yahoo.com ---
The log of digikam up to the ctrl+c

digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
   Type: "QSQLITE"
   DB Core Name:
"/run/media/simone/esterno_xfs/data/Pictures/digikam4.db"
   DB Thumbs Name:  
"/run/media/simone/esterno_xfs/data/Pictures/thumbnails-digikam.db"
   DB Face Name:
"/run/media/simone/esterno_xfs/data/Pictures/recognition.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  8
digikam.coredb: Core database: makeUpdates  8  to  8
digikam.database: Creating new Location  "/data/Pictures"  uuid 
"volumeid:?uuid=83fe5e0a-66fa-42c9-ad66-05f1bee9c0b2"
digikam.database: location for  "/run/media/simone/esterno_xfs/data/Pictures" 
is available  true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  8356839424
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.general: Switch to widget style:  "oxygen"
digikam.dimg: ("/usr/share/color/icc")
digikam.dimg: No X.org XICC profile installed for screen  0
digikam.general: Camera XML data:  "/home/sim/.local/share/digikam/cameras.xml"
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: Face database: have a structure version  "2"
digikam.facesengine: Face database ready for use
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
digikam.facesengine: Face database ready for use
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
digikam.geoiface: "setting backend marble"
QtAV 1.12.0(Jun 21 2017, 14:33:46)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai University->S3 Graphics->Deepin->PPTV, Shanghai, China Copyright (C)
2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
digikam.general: AudioOutput backends: ("OpenAL", "Pulse", "null")
digikam.general: Stacked View Mode :  0
digikam.geoiface: "setting backend marble"
digikam.geoiface: "setting backend marble"
digikam.general: "browse_album"
digikam.general: "browse_tag"
digikam.general: "browse_labels"
digikam.general: "browse_date"
digikam.general: "browse_timeline"
digikam.general: "browse_search"
digikam.general: "browse_fuzzysearch"
digikam.general: "browse_gpssearch"
digikam.general: "browse_people"
digikam.widgets: Paths to color scheme :  ("/usr/share/digikam/colorschemes")
digikam.widgets: "Breeze"  ::  ""
digikam.widgets: "DarkRoom"  :: 
"/usr/share/digikam/colorschemes/darkroom.colors"
QFSFileEngine::open: No file name specified
digikam.dimg: Root lens database dir:  "/usr/share/lensfun"
digikam.dimg: Load lens database file:  "6x6.xml"
digikam.dimg: Load lens database file:  "actioncams.xml"
digikam.dimg: Load lens database file:  "compact-canon.xml"
digikam.dimg: Load lens database file:  "compact-casio.xml"
digikam.dimg: Load lens database file:  "compact-fujifilm.xml"
digikam.dimg: Load lens database file:  "compact-kodak.xml"
digikam.dimg: Load lens database file:  "compact-konica-minolta.xml"
digikam.dimg: Load lens database file:  "compact-leica.xml"
digikam.dimg: Load lens database file:  "compact-nikon.xml"
digikam.dimg: Load lens database file:  "compact-olympus.xml"
digikam.dimg: Load lens database file:  "compact-panasonic.xml"
digikam.dimg: Load lens database file:  "compact-pentax.xml"
digikam.dimg: Load lens database file:  "compact-ricoh.xml"
digikam.dimg: Load lens database file:  "compact-samsung.xml"
digikam.dimg: Load lens database file:  "compact-sigma.xml"
digikam.dimg: Load lens database file:  "compact-sony.xml"
digikam.dimg: Load lens database file:  "contax.xml"
digikam.dimg: Load lens database file:  "generic.xml"
digikam.dimg: Load lens database file:  "mil-canon.xml"
digikam.dimg: Load lens database file:  "mil-fujifilm.xml"
digikam.dimg: Load lens database file:  "mil-nikon.xml"
digikam.dimg: 

[Discover] [Bug 382045] discover update icon missing

[Delfino]

https://bugs.kde.org/show_bug.cgi?id=382045

Delfino  changed:

   What|Removed |Added

 CC||delfino.nunez@gmail.com

--- Comment #4 from Delfino  ---
I can see the icon. Same version.

http://i.imgur.com/NyEbiPh.png

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381877

--- Comment #6 from giggi1...@yahoo.com ---
Created attachment 106510
  --> https://bugs.kde.org/attachment.cgi?id=106510=edit
What's happen

This is the snapshot of the RAM usage caused by digikam.

-- 
You are receiving this mail because:
You are watching all bug changes.

[tellico] [Bug 275066] bibtex export: add brackets around capital letters in titles

[Robby Stephenson]

https://bugs.kde.org/show_bug.cgi?id=275066

Robby Stephenson  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 382116] konsole does not set KONSOLE_DBUS_WINDOW in sessions started with D-Bus

[Kurt Hindenburg]

https://bugs.kde.org/show_bug.cgi?id=382116

Kurt Hindenburg  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Kurt Hindenburg  ---
Thanks, also in master

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevplatform] [Bug 382135] New: error: 'nodiscard' attribute cannot be applied to types

[Yurii Kolesnykov]

https://bugs.kde.org/show_bug.cgi?id=382135

Bug ID: 382135
   Summary: error: 'nodiscard' attribute cannot be applied to
types
   Product: kdevplatform
   Version: git master
  Platform: Homebrew (Mac OS X)
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: yuriko...@gmail.com
  Target Milestone: ---

full log is here: https://gist.github.com/bb9529787dabefdee6f92129035d924b

/Users/yurikoles/kdesrc/extragear/kdevelop/kdevplatform/project/abstractfilemanagerplugin.cpp:81:63:
error: 'nodiscard' attribute cannot be applied to types
KIO::Job* eventuallyReadFolder( ProjectFolderItem* item )
Q_REQUIRED_RESULT;
  ^
/usr/local/opt/qt/lib/QtCore.framework/Headers/qcompilerdetection.h:1177:31:
note: expanded from macro 'Q_REQUIRED_RESULT'
#  define Q_REQUIRED_RESULT [[nodiscard]]

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevplatform] [Bug 382135] error: 'nodiscard' attribute cannot be applied to types

[Yurii Kolesnykov]

https://bugs.kde.org/show_bug.cgi?id=382135

Yurii Kolesnykov  changed:

   What|Removed |Added

 CC||yuriko...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382133] processing fails, caused by too long filename

[Maik Qualmann]

https://bugs.kde.org/show_bug.cgi?id=382133

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.7.0
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/78329a5b3edda0992974c7
   ||dba8d9692ef185c857

--- Comment #1 from Maik Qualmann  ---
Git commit 78329a5b3edda0992974c7dba8d9692ef185c857 by Maik Qualmann.
Committed on 08/07/2017 at 19:04.
Pushed by mqualmann into branch 'master'.

fix growing the temporary batch tool filenames
FIXED-IN: 5.7.0

M  +2-1NEWS
M  +6-5utilities/queuemanager/manager/batchtool.cpp

https://commits.kde.org/digikam/78329a5b3edda0992974c7dba8d9692ef185c857

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kcoreaddons] [Bug 381583] potential crash in KDirWatch::~KDirWatch()

[Michael Pyne]

https://bugs.kde.org/show_bug.cgi?id=381583

Michael Pyne  changed:

   What|Removed |Added

   Version Fixed In||5.37
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kco
   ||readdons/b8cb28bcd0709a0ff4
   ||9ac1ae40c0f44e7ea36f33
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Michael Pyne  ---
Git commit b8cb28bcd0709a0ff49ac1ae40c0f44e7ea36f33 by Michael Pyne, on behalf
of René J.V. Bertin.
Committed on 08/07/2017 at 19:00.
Pushed by mpyne into branch 'master'.

kdirwatch: Avoid potential crash if d-ptr destroyed before KDirWatch.

Found in a code review and patch proposed by René, although we've not
actually gone so far as to create a test case that forces a crash.

Committed by mpyne to get the bug closed out.
FIXED-IN:5.37

M  +1-1src/lib/io/kdirwatch.cpp

https://commits.kde.org/kcoreaddons/b8cb28bcd0709a0ff49ac1ae40c0f44e7ea36f33

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 377609] [Windows] Icons missing

[Pas]

https://bugs.kde.org/show_bug.cgi?id=377609

Pas  changed:

   What|Removed |Added

 CC||pasthe...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Mauro Carvalho Chehab]

https://bugs.kde.org/show_bug.cgi?id=368907

--- Comment #43 from Mauro Carvalho Chehab  ---
(In reply to coekbe from comment #41)
> Created attachment 106508 [details]
> Demo app to show infinite signal emission
> 
> It looks like using a write notifier on a FIFO (or an ordinary file) is
> invalid. I attached a small application to demonstrate this. After unzipping
> and changing to the directory, try it with:
> 
> qmake -project
> qmake
> make
> mkfifo testpipe
> ./testapp
> 
> On my system, writeToPipe() will be called on and on and starting
> immediately even though there is nothing going on at the fifo. 

That's the expected behavior. Basically, reads and writes are buffered
internally at the Kernel. When such buffer is filled, a write to the
buffer will return an error code, if the file descriptor is opened in
non-blocking mode, until the buffer is flushed. So, if you do something
like (with is what the writeToPipe loop actually does):

while (write(fd, data, size) < 0) {}

it will call write() several times, spending a lot of CPU cycles doing nothing.

the usage of a QSocketNotifier there is meant to avoid doing that.
Basically, if write() returns an error (typically, EAGAIN), indicating
that the Kernel buffer is full, the routine will exit and called later,
when the buffer is flushed.

That should save some CPU load during normal Kaffeine operation.

> On the other
> hand, (if the app is modified accordingly) as a read notifier it appears to
> work as expected even on FIFOs. Perhaps the notifier should be on reading
> instead?

A read notifier doesn't make much sense with the current code. Take a look at
processData(): basically, when some data is received, it updates the buffer,
then it calls writeToPipe().

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 382134] breeze-gtk doesn't follow KDE colour scheme

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382134

scionicspec...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from scionicspec...@gmail.com ---
This is a known issue resulting from upstream GTK removing theme engine
functionality in GTK 3. There is some preliminary work on honoring color
schemes dynamically using a script for both GTK 2 and 3 themes, but it is
incomplete.

Even when that work is done, integration and automation will require some
cooperation which means it may only be available as an optional, manual feature
when it first lands. However, it should be noted that this is very much against
GTK's intended use so it's always going to be a bit of a hack underneath.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 349344] Screen Energy Saving and Dim Screen do not work reliably

[Ralf HArtmann]

https://bugs.kde.org/show_bug.cgi?id=349344

Ralf HArtmann  changed:

   What|Removed |Added

 CC||ralfhartm...@gmx.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381130

--- Comment #18 from personaldesignertec...@gmail.com ---
I was running the User LTS version of KDE Neon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382131] Notifications don't always appear in the spot you set.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382131

personaldesignertec...@gmail.com changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382131] Notifications don't always appear in the spot you set.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382131

personaldesignertec...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from personaldesignertec...@gmail.com ---


*** This bug has been marked as a duplicate of bug 381130 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381130

--- Comment #17 from personaldesignertec...@gmail.com ---
*** Bug 382131 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 382019] Reboot, Shutdown buttons don't appear again when changing in System Settings

[idmresettrial]

https://bugs.kde.org/show_bug.cgi?id=382019

idmresettrial  changed:

   What|Removed |Added

Summary|Reboot, Shutdown buttons|Reboot, Shutdown buttons
   |doesn't appear again when   |don't appear again when
   |changing in System Settings |changing in System Settings

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381130

personaldesignertec...@gmail.com changed:

   What|Removed |Added

 CC||personaldesignertechie@gmai
   ||l.com

--- Comment #16 from personaldesignertec...@gmail.com ---
I can confirm that this also occurs on KDE 5.8.7 with KDE Frameworks 5.35.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=368907

--- Comment #42 from coe...@gmail.com ---
Created attachment 106509
  --> https://bugs.kde.org/attachment.cgi?id=106509=edit
A patch using a read notifier

Another patch fixing the 100% cpu usage

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 375969] add option to adjust size of digital clock manually / font is tiny when combined with date

[Vladimir Pavljuchenkov]

https://bugs.kde.org/show_bug.cgi?id=375969

Vladimir Pavljuchenkov  changed:

   What|Removed |Added

 CC||spid...@spiderx.dp.ua

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=368907

coe...@gmail.com changed:

   What|Removed |Added

 CC||coe...@gmail.com

--- Comment #41 from coe...@gmail.com ---
Created attachment 106508
  --> https://bugs.kde.org/attachment.cgi?id=106508=edit
Demo app to show infinite signal emission

It looks like using a write notifier on a FIFO (or an ordinary file) is
invalid. I attached a small application to demonstrate this. After unzipping
and changing to the directory, try it with:

qmake -project
qmake
make
mkfifo testpipe
./testapp

On my system, writeToPipe() will be called on and on and starting immediately
even though there is nothing going on at the fifo. On the other hand, (if the
app is modified accordingly) as a read notifier it appears to work as expected
even on FIFOs. Perhaps the notifier should be on reading instead?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 382134] New: breeze-gtk doesn't follow KDE colour scheme

[Coacher]

https://bugs.kde.org/show_bug.cgi?id=382134

Bug ID: 382134
   Summary: breeze-gtk doesn't follow KDE colour scheme
   Product: Breeze
   Version: 5.10.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: scionicspec...@gmail.com
  Reporter: itumaykin+...@gmail.com
  Target Milestone: ---

Both gtk2 and gtk3 are affected. oxygen-gtk with gtk2 doesn't have this
problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382133] processing fails, caused by too long filename

[Paul Neuwirth]

https://bugs.kde.org/show_bug.cgi?id=382133

Paul Neuwirth  changed:

   What|Removed |Added

 CC||m...@paul-neuwirth.nl

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 382133] New: processing fails, caused by too long filename

[Paul Neuwirth]

https://bugs.kde.org/show_bug.cgi?id=382133

Bug ID: 382133
   Summary: processing fails, caused by too long filename
   Product: digikam
   Version: 5.6.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: BatchQueueManager
  Assignee: digikam-de...@kde.org
  Reporter: m...@paul-neuwirth.nl
  Target Milestone: ---

There's obviously no check for too long filenames:
in my case processing works if there are no more than 4 steps. If a 5th step is
added the job will fail:
digikam.general: Action Thread run  1  new jobs
digikam.general: Tool : index=  1  :: name=  "Resize"  :: group=  4  :: wurl= 
QUrl("file:///storage/photos/")
digikam.general: path: 
"/storage/photos/BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg"
digikam.general: Tool:"Resize"
digikam.general: Input url:  
QUrl("file:///storage/photos/IMG_20170616_151042.jpg")
digikam.general: Output url: 
QUrl("file:///storage/photos/BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg")
digikam.dimg: "/storage/photos/IMG_20170616_151042.jpg"  : JPEG file identified
digikam.metaengine: Loading image history  ""
digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => 
QDateTime(2017-06-16 15:10:42.000 CEST Qt::TimeSpec(LocalTime))
digikam.general: Detected change, triggering rescan of "/storage/photos//"
digikam.database: Starting scan!
digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC
profile.
digikam.general: Tool : index=  2  :: name=  "AssignTemplate"  :: group=  8  ::
wurl=  QUrl("file:///storage/photos/")
digikam.general: path: 
"/storage/photos/BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg"
digikam.general: Tool:"Apply Metadata Template"
digikam.general: Input url:  
QUrl("file:///storage/photos/BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg")
digikam.general: Output url: 
QUrl("file:///storage/photos/BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg")
digikam.general: Detected change, triggering rescan of "/storage/photos//"
[...]
digikam.general: Tool : index=  3  :: name=  "WaterMark"  :: group=  5  ::
wurl=  QUrl("file:///storage/photos/")
digikam.general: path: 
"/storage/photos/BatchTool-M29661-BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg"
digikam.general: Tool:"Add Watermark"
digikam.general: Input url:  
QUrl("file:///storage/photos/BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg")
digikam.general: Output url: 
QUrl("file:///storage/photos/BatchTool-M29661-BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg")
digikam.general: Detected change, triggering rescan of "/storage/photos//"
digikam.database: No itemShortInfo could be retrieved from the database for
image
"BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg"
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.database: Starting scan!
digikam.database: No itemShortInfo could be retrieved from the database for
image
"BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg"
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: Tool : index=  4  :: name=  "WaterMark"  :: group=  5  ::
wurl=  QUrl("file:///storage/photos/")
digikam.general: path:  ""
digikam.general: Tool:"Add Watermark"
digikam.general: Input url:  
QUrl("file:///storage/photos/BatchTool-M29661-BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg")
digikam.general: Output url:  QUrl("")
digikam.database: No itemShortInfo could be retrieved from the database for
image
"BatchTool-M29661-BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg

I assume this is caused by a too long filename:
~> touch
Batchtool-A12345-BatchTool-M29661-BatchTool-T29661-BatchTool-J29661-IMG_20170616_151042.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg.digikamtempfile.jpg
touch: cannot touch

[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=381130

--- Comment #15 from Dr. Chapatin  ---
I can confirm notification on left bottom, Arch running frameworks 5.36.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382131] Notifications don't always appear in the spot you set.

[Rog131]

https://bugs.kde.org/show_bug.cgi?id=382131

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #3 from Rog131  ---
A possible dublicate of https://bugs.kde.org/show_bug.cgi?id=381130

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382131] Notifications don't always appear in the spot you set.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382131

--- Comment #2 from personaldesignertec...@gmail.com ---
More likely to occur if you have the Application Launcher open.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Jan Palus]

https://bugs.kde.org/show_bug.cgi?id=368907

--- Comment #40 from Jan Palus  ---
Looks like this was it! After applying last patch issue did not occur within
10min of constant channel switching. Thanks a lot Mauro!

-- 
You are receiving this mail because:
You are watching all bug changes.

[krusader] [Bug 382086] Manage bookmarks

[Toni Asensi Esteve]

https://bugs.kde.org/show_bug.cgi?id=382086

--- Comment #6 from Toni Asensi Esteve  ---
Note: To see which files are included in a Debian package we can use, for
example:
https://packages.debian.org/kde-baseapps-bin
and then click on links until arriving for example to:
https://packages.debian.org/sid/amd64/kde-baseapps-bin/filelist

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382132] Plasma se detuvo luego de subir y bajar el volumen

[JPatagonico]

https://bugs.kde.org/show_bug.cgi?id=382132

JPatagonico  changed:

   What|Removed |Added

   Platform|unspecified |Neon Packages

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382132] New: Plasma se detuvo luego de subir y bajar el volumen

[JPatagonico]

https://bugs.kde.org/show_bug.cgi?id=382132

Bug ID: 382132
   Summary: Plasma se detuvo luego de subir y bajar el volumen
   Product: plasmashell
   Version: 5.10.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jpherr...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.3)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.4.0-83-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
Plasma se detuvo luego de subir y bajar el volumen utilizando la rueda del
mouse. Continuamente pasa esto.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7feeeb6888c0 (LWP 1506))]

Thread 14 (Thread 0x7fee027fe700 (LWP 2560)):
#0  0x7feee5e6d24d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7feee15f36f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7feee15afe74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7feee15b0330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7feee15b049c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7feee679dadb in QEventDispatcherGlib::processEvents
(this=0x7fede40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7feee674730a in QEventLoop::exec (this=this@entry=0x7fee027fdce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7feee6576af4 in QThread::exec (this=this@entry=0x3a235c0) at
thread/qthread.cpp:515
#8  0x7feee8c59075 in QQmlThreadPrivate::run (this=0x3a235c0) at
qml/ftw/qqmlthread.cpp:147
#9  0x7feee657b509 in QThreadPrivate::start (arg=0x3a235c0) at
thread/qthread_unix.cpp:368
#10 0x7feee54056ba in start_thread (arg=0x7fee027fe700) at
pthread_create.c:333
#11 0x7feee5e7d3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fee037ff700 (LWP 1739)):
#0  0x7feeda87d263 in pa_pstream_unref () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#1  0x7feeda87d789 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7feeda87e01a in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#3  0x7feedb6120b7 in pa_mainloop_dispatch () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7feedb6124bc in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7feedb612560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7feedb6207a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7feeda88e078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#8  0x7feee54056ba in start_thread (arg=0x7fee037ff700) at
pthread_create.c:333
#9  0x7feee5e7d3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fee09de5700 (LWP 1738)):
#0  0x7feee5e7170d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7feee15b038c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7feee15b049c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7feee679dadb in QEventDispatcherGlib::processEvents
(this=0x7fedfc151d50, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7feee674730a in QEventLoop::exec (this=this@entry=0x7fee09de4ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7feee6576af4 in QThread::exec (this=this@entry=0x2bd5d90) at
thread/qthread.cpp:515
#6  0x7feee8c59075 in QQmlThreadPrivate::run (this=0x2bd5d90) at
qml/ftw/qqmlthread.cpp:147
#7  0x7feee657b509 in QThreadPrivate::start (arg=0x2bd5d90) at
thread/qthread_unix.cpp:368
#8  0x7feee54056ba in start_thread (arg=0x7fee09de5700) at
pthread_create.c:333
#9  0x7feee5e7d3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fee16e15700 (LWP 1633)):
#0  0x7feee5e7170d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7feee15b038c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7feee15b049c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7feee679dadb in QEventDispatcherGlib::processEvents
(this=0x7fee18c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7feee674730a in QEventLoop::exec (this=this@entry=0x7fee16e14cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7feee6576af4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7fee1932d587 in KCupsConnection::run() () from

[plasmashell] [Bug 357125] Allow sorting favorites by name

[Marco Parillo]

https://bugs.kde.org/show_bug.cgi?id=357125

--- Comment #4 from Marco Parillo  ---
Can a regression be defined as a wishlist item?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382131] Notifications don't always appear in the spot you set.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382131

--- Comment #1 from personaldesignertec...@gmail.com ---
I was running KDE Neon LTS 5.8.

-- 
You are receiving this mail because:
You are watching all bug changes.

[drkonqi] [Bug 382130] New: closed unexpectly

[Dwight Joseph]

https://bugs.kde.org/show_bug.cgi?id=382130

Bug ID: 382130
   Summary: closed unexpectly
   Product: drkonqi
   Version: 5.8.6
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: backtraceparsing
  Assignee: unassigned-b...@kde.org
  Reporter: dwigh...@gmail.com
  Target Milestone: ---

keeps crashing whilst trying to delete files.Cannot delete anything because the
application keeps crashing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382131] New: Notifications don't always appear in the spot you set.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382131

Bug ID: 382131
   Summary: Notifications don't always appear in the spot you set.
   Product: plasmashell
   Version: 5.8.7
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: personaldesignertec...@gmail.com
CC: mklape...@kde.org
  Target Milestone: 1.0

Even though I set the setting for notifications to appear in the bottom right
corner, it sometimes randomly pops up in the upper left corner instead.

-- 
You are receiving this mail because:
You are watching all bug changes.

[marble] [Bug 339867] Some data is stored in $XDG_DATA_HOME (~/.local/share) but $XDG_CACHE_HOME (~/.cache) would be more appropriate

[Adrien]

https://bugs.kde.org/show_bug.cgi?id=339867

Adrien  changed:

   What|Removed |Added

 CC||pe...@adrieng.fr

--- Comment #9 from Adrien  ---
Hi,

I would add that the backup systems like backintime usually do backup .local
but not .cache by default.

Putting all the cache data in .cache would certainly be more "backup friendly",
as the marble folder can be quite heavy (2.7Go on my PC for instance).

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 382125] Vector Objects are not selectable and movable in windows with the default tool

[Scott Petrovic]

https://bugs.kde.org/show_bug.cgi?id=382125

--- Comment #1 from Scott Petrovic  ---
a little more testing...it is working with my stylus if I use that on my
surface pro. There might be something where the tablet events are being picked
up, but mouse events are not with this tool

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 382129] New: Amarok crashes when clicking "quit" in context menu

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382129

Bug ID: 382129
   Summary: Amarok crashes when clicking "quit" in context menu
   Product: amarok
   Version: 2.8-git
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: m4n...@gmx.de
  Target Milestone: 2.9

Application: amarok (2.8-git)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.8-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

When Amarok is minimized to the system tray and I want to close it by using the
right mouse button and clicking quit in the context menu, it crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Amarok (amarok), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6a823b6940 (LWP 5407))]

Thread 26 (Thread 0x7f69d5c7f700 (LWP 5437)):
#0  0x7f6a7dca85ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f69e87412fb in cnd_wait (mtx=0x56216a1519b0, cond=0x56216a1519d8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x56216a152140) at u_queue.c:158
#3  0x7f69e8741037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f6a7dca24e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f6a7f170a2f in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f69d6480700 (LWP 5436)):
#0  0x7f6a7dca85ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f69e87412fb in cnd_wait (mtx=0x56216a1519b0, cond=0x56216a1519d8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x56216a124c90) at u_queue.c:158
#3  0x7f69e8741037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f6a7dca24e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f6a7f170a2f in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7f69d6c81700 (LWP 5435)):
#0  0x7f6a7dca85ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f69e87412fb in cnd_wait (mtx=0x56216a1519b0, cond=0x56216a1519d8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x56216a152140) at u_queue.c:158
#3  0x7f69e8741037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f6a7dca24e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f6a7f170a2f in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7f69d7482700 (LWP 5434)):
#0  0x7f6a7dca85ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f69e87412fb in cnd_wait (mtx=0x56216a1519b0, cond=0x56216a1519d8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x56216a124c90) at u_queue.c:158
#3  0x7f69e8741037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f6a7dca24e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f6a7f170a2f in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7f69d7ec2700 (LWP 5433)):
#0  0x7f6a7dca85ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f69e87412fb in cnd_wait (mtx=0x56216a151fc0, cond=0x56216a151fe8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x56216a152590) at u_queue.c:158
#3  0x7f69e8741037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f6a7dca24e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f6a7f170a2f in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7f69d880a700 (LWP 5432)):
#0  0x7f6a7dca85ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f69e87412fb in cnd_wait (mtx=0x56216a150af0, cond=0x56216a150b18) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x56216a151250) at u_queue.c:158
#3  0x7f69e8741037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f6a7dca24e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f6a7f170a2f in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7f69ebfff700 (LWP 5430)):
#0  0x7f6a7f16708d in poll () from /lib64/libc.so.6
#1  0x7f6a76cd0d09 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6a76cd0e1c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6a7fa87a0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f6a7fa3053a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f6a7f86031a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f6a7f864d2e in QThreadPrivate::start(void*) () from

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Mauro Carvalho Chehab]

https://bugs.kde.org/show_bug.cgi?id=368907

Mauro Carvalho Chehab  changed:

   What|Removed |Added

 Attachment #106506|0   |1
is obsolete||

--- Comment #39 from Mauro Carvalho Chehab  ---
Created attachment 106507
  --> https://bugs.kde.org/attachment.cgi?id=106507=edit
Disable notifier if no data - v2

It makes sense to also disable the notifier at the resetPipe(), with is called
when a channel changes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 382128] New: wayland: kinfocenter still crashing when clicking on "Graphical information -> OpenGL"

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382128

Bug ID: 382128
   Summary: wayland: kinfocenter still crashing when clicking on
"Graphical information -> OpenGL"
   Product: kinfocenter
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: m4n...@gmx.de
  Target Milestone: ---

Application: kinfocenter (5.10.90)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.8-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

As the title says: I opened kinfocenter and clicked on "Graphical Information
-> OpenGL".
As soon as I clicked on it, kinfocenter crashed.

This bug was reported as fixed in different QT versions (5.7, 5.8?) but it is
still present.

The crash can be reproduced every time.

-- Backtrace:
Application: Info Center (kinfocenter), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f70a7174680 (LWP 2039))]

Thread 8 (Thread 0x7f707af77700 (LWP 2047)):
#0  0x7f709fd105ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7085a712fb in cnd_wait (mtx=0x562a339e42b0, cond=0x562a339e42d8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x562a3385d3b0) at u_queue.c:158
#3  0x7f7085a71037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f709fd0a4e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f70a3968a2f in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f707b778700 (LWP 2046)):
#0  0x7f709fd105ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7085a712fb in cnd_wait (mtx=0x562a339e42b0, cond=0x562a339e42d8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x562a33800330) at u_queue.c:158
#3  0x7f7085a71037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f709fd0a4e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f70a3968a2f in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f707bf79700 (LWP 2045)):
#0  0x7f709fd105ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7085a712fb in cnd_wait (mtx=0x562a339e42b0, cond=0x562a339e42d8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x562a3385d3b0) at u_queue.c:158
#3  0x7f7085a71037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f709fd0a4e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f70a3968a2f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f707c77a700 (LWP 2044)):
#0  0x7f709fd105ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7085a712fb in cnd_wait (mtx=0x562a339e42b0, cond=0x562a339e42d8) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x562a338423f0) at u_queue.c:158
#3  0x7f7085a71037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f709fd0a4e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f70a3968a2f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f707d1ba700 (LWP 2043)):
#0  0x7f709fd105ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7085a712fb in cnd_wait (mtx=0x562a33835840, cond=0x562a33835868) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x562a338075c0) at u_queue.c:158
#3  0x7f7085a71037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f709fd0a4e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f70a3968a2f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f707db3a700 (LWP 2042)):
#0  0x7f709fd105ed in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7085a712fb in cnd_wait (mtx=0x562a33ce28e0, cond=0x562a33ce2908) at
../../include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x562a337fce50) at u_queue.c:158
#3  0x7f7085a71037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#4  0x7f709fd0a4e7 in start_thread () from /lib64/libpthread.so.0
#5  0x7f70a3968a2f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f7092572700 (LWP 2041)):
#0  0x7f70a427fd00 in idleTimerSourcePrepare(_GSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#1  0x7f709df10248 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f709df10c3b in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f709df10e1c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f70a427fa0b in

[drkonqi] [Bug 382127] New: Crashed

[Dwight Joseph]

https://bugs.kde.org/show_bug.cgi?id=382127

Bug ID: 382127
   Summary: Crashed
   Product: drkonqi
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dwigh...@gmail.com
  Target Milestone: ---

Crashed whlist saving information

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 369514] KMail crash on starting (nouveau-related)

[Florian Bruhin]

https://bugs.kde.org/show_bug.cgi?id=369514

Florian Bruhin  changed:

   What|Removed |Added

 CC||kde@the-compiler.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 381608] Plasmashell use 100% cpu

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=381608

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #12 from David Edmundson  ---
Trace shows it's processing an X event, which doesn't tell us much  - we're
meant to be doing that.

There does seem an issue nvidia we've seen of Qt getting the framerate wrong
and just constantly rendering instantly, 

If you're willing to build your own Qt from scratch and apply patches we can go
somewhere with this.   Otherwise, not really.

*** This bug has been marked as a duplicate of bug 373368 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 373368] Spurious XCB Events causing high CPU

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=373368

David Edmundson  changed:

   What|Removed |Added

 CC||quelque_...@yahoo.fr

--- Comment #12 from David Edmundson  ---
*** Bug 381608 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 382110] Fill tool does not work if brush eraser is selected

[Thiago]

https://bugs.kde.org/show_bug.cgi?id=382110

--- Comment #2 from Thiago  ---
I guess a warning is enough. It took me a while to understand what was
happening as the canvas was already transparent and I had no feedback. 

On a more important topic I had a couple crashes, wish I could help but they
were random and I don't know how to report. Is there a tutorial for that? To
deal with this issue many programs have an option to automatically send a
report with the data you need for debugging.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Mauro Carvalho Chehab]

https://bugs.kde.org/show_bug.cgi?id=368907

--- Comment #38 from Mauro Carvalho Chehab  ---
Created attachment 106506
  --> https://bugs.kde.org/attachment.cgi?id=106506=edit
Disable notifier if no data

(In reply to Jan Palus from comment #36)
> Looks like it's still the same, but I'm not really sure whether we are on
> the same page -- writeToPipe() is not looping. It is rather called a lot
> once the bug is triggered. I've made following small adjustment to its code:
> 
>  void DvbLiveViewInternal::writeToPipe()
>  {
> +  static int notEmptyCnt = 0;
> +  static int emptyCnt = 0;
> +  if (buffers.isEmpty()) {
> +++emptyCnt;
> +  } else {
> +++notEmptyCnt;
> +  }
> +printf("empty: %d, not empty: %d\n", emptyCnt, notEmptyCnt);
>   while (!buffers.isEmpty()) {
>   const QByteArray  = buffers.at(0);
>   int bytesWritten = int(write(writeFd, currentBuffer.constData(),
> currentBuffer.size()));
> 
> That's output after 10 seconds "without bug":
> 
> empty: 0, not empty: 614
> 
> Now after bug is triggered empty counter skyrockets to some crazy value
> after 10 secs (and continues which is most probably the cause of high CPU
> usage):
> 
> empty: 5053133, not empty: 534
> 
> as if notifications about pipe being ready for writing were suddenly coming
> very very frequently

Ah, OK. Well, I guess all we need to do is to disable the notifier to solve
this issue. Still, I think that the first patch will make it more reliable.

Please test with both the previous patch and this one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 382115] Rendering artifacts on desktop Icon Text after resume from suspend.

[pdf]

https://bugs.kde.org/show_bug.cgi?id=382115

pdf  changed:

   What|Removed |Added

 CC||k...@obfusc8.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 382126] New: Bad aspect ratio on clip monitor

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382126

Bug ID: 382126
   Summary: Bad aspect ratio on clip monitor
   Product: kdenlive
   Version: 17.04.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: thealchemist...@gmail.com
  Target Milestone: ---

Created attachment 106505
  --> https://bugs.kde.org/attachment.cgi?id=106505=edit
The clip have an standard 1080 res, but it still gets the project aspect ratio

Trying to preview a video on the clip monitor where the video have a different
aspect ratio than the project, it will use the project aspect ratio instead of
the clip's one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 382125] New: Vector Objects are not selectable and movable in windows with the default tool

[Scott Petrovic]

https://bugs.kde.org/show_bug.cgi?id=382125

Bug ID: 382125
   Summary: Vector Objects are not selectable and movable in
windows with the default tool
   Product: krita
   Version: git master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Vector Objects and Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: scottpetro...@gmail.com
  Target Milestone: ---

I am on my Surface Pro 4 (Windows 10) device.  

Steps to reproduct:
1. Create a vector layer
2. Add a rectangle
3. switch to the default tool
4. try to select or move the rectangle

Expected results
The rectangle would be selected or movable

Actual results
The rectangle is not selectable or movable

I moved around to different commits for testing to see where it starts. The
touch painting merge seems to be the cause. 

Commit hash:8c8ed9ae4ed50e6e4e506cbe6cf8621e53e56b54
committed on 7/3/2017 9:12:08 AM
message: branch 'rempt/touch-paint-4'

just one commit back and this works ok.

I didn't play with the code too much, but my first stab at trying to fix it
might be the removal of a "updateShapeController" that was removed with this
commit. That potentially might be related. Haven't tested it though to know.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Jan Palus]

https://bugs.kde.org/show_bug.cgi?id=368907

--- Comment #37 from Jan Palus  ---
And just to be clear -- not empty counter continues to increase with the same
pace once bug is triggered and everything works fine (TV runs smoothly), it's
just high CPU usage in the background that changes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[sieveeditor] [Bug 370239] CRAM-MD5 authentication does not work

[Laurent Montel]

https://bugs.kde.org/show_bug.cgi?id=370239

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Laurent Montel  ---
wait info

-- 
You are receiving this mail because:
You are watching all bug changes.

[sieveeditor] [Bug 360202] Add SSL server support

[Laurent Montel]

https://bugs.kde.org/show_bug.cgi?id=360202

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Laurent Montel  ---
needs info

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom

[Daniel Lichtenberger]

https://bugs.kde.org/show_bug.cgi?id=371199

--- Comment #25 from Daniel Lichtenberger  ---
Hi Martin,

thanks for the patch! This does seem to solve the issue for me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[Jan Palus]

https://bugs.kde.org/show_bug.cgi?id=368907

--- Comment #36 from Jan Palus  ---
Looks like it's still the same, but I'm not really sure whether we are on the
same page -- writeToPipe() is not looping. It is rather called a lot once the
bug is triggered. I've made following small adjustment to its code:

 void DvbLiveViewInternal::writeToPipe()
 {
+  static int notEmptyCnt = 0;
+  static int emptyCnt = 0;
+  if (buffers.isEmpty()) {
+++emptyCnt;
+  } else {
+++notEmptyCnt;
+  }
+printf("empty: %d, not empty: %d\n", emptyCnt, notEmptyCnt);
while (!buffers.isEmpty()) {
const QByteArray  = buffers.at(0);
int bytesWritten = int(write(writeFd,
currentBuffer.constData(), currentBuffer.size()));

That's output after 10 seconds "without bug":

empty: 0, not empty: 614

Now after bug is triggered empty counter skyrockets to some crazy value after
10 secs (and continues which is most probably the cause of high CPU usage):

empty: 5053133, not empty: 534

as if notifications about pipe being ready for writing were suddenly coming
very very frequently

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 382124] The "Problems" view reports Qt includes as "not found" whereas the CPP parser reports the opposite

[Ignat Semenov]

https://bugs.kde.org/show_bug.cgi?id=382124

--- Comment #1 from Ignat Semenov  ---
Created attachment 106504
  --> https://bugs.kde.org/attachment.cgi?id=106504=edit
CMakelists.txt for the project I'm developing

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 382124] New: The "Problems" view reports Qt includes as "not found" whereas the CPP parser reports the opposite

[Ignat Semenov]

https://bugs.kde.org/show_bug.cgi?id=382124

Bug ID: 382124
   Summary: The "Problems" view reports Qt includes as "not found"
whereas the CPP parser reports the opposite
   Product: kdevelop
   Version: 5.1.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: i.semenov@gmail.com
  Target Milestone: ---

Created attachment 106503
  --> https://bugs.kde.org/attachment.cgi?id=106503=edit
A screenshot of kdevelop showing the parser error in the bottom view with the
include being correctly located as reported in the popup over the source code

I'm developing a project with Qt5 and CMake. The Qt5 includes are reported as
"not found" in the "Problems" view ("Current project" selected as the scope),
but, at the same time, when I hover the problematic include in the source code
editor, the popup displays the correct full path to the said include, and the
symbols that the include defines are correctly imported by the CPP parser.
Still, the first angular bracket in the include is underlined with a red wave,
which probably is another manifestation of the fact that the problem view
reports in issue about the header not being found and a part of the same
problem reporting mechanism.

Attached are the screenshot of the whole KDevelop window with the CPP parser
popup related to the problematic include, and the CMakeLists.txt file for the
project.

The project builds and runs fine within the same KDevelop session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 372474] Syntax error. l2sm18082790wji.7 - gsmtp when sending invite

[Laurent Montel]

https://bugs.kde.org/show_bug.cgi?id=372474

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org

--- Comment #3 from Laurent Montel  ---
Fixed in 5.6.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 369179] Reply function not working when receive a sms text

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=369179

--- Comment #11 from voncl...@gmail.com ---
anyone have a solution - beuler...beuler...BEULER?

-- 
You are receiving this mail because:
You are watching all bug changes.