[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[via KDE Bugzilla]

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

--- Comment #12 from caulier.gil...@gmail.com ---
You must to force digiKam to rescan metadata to resync database contents.

Try buttons on the bottom of Captions/Tags sidebar tab.

Other way is to use Maintenance tool.

Gilles Caulier

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

[digikam] [Bug 366104] digikam5 "hangs' @ 100%CPU at exit

[via KDE Bugzilla]

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

--- Comment #3 from caulier.gil...@gmail.com ---
This is for macports OSX. Right ?. Not Linux ?

Gilles Caulier

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

[dolphin] [Bug 366078] Since upgrading opensuse 13.2 to Leap 42.1 i can not use dolphin

[Faeberer via KDE Bugzilla]

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

Faeberer  changed:

   What|Removed |Added

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

--- Comment #1 from Faeberer  ---
Upgrade with the mentioned problem was done online. By reinstalling Leap from
ISO the problem has been solved for me.
Thank you.

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

[plasmashell] [Bug 315488] icon-only task manager groups chrome/chromium web apps with chrome/chromium

[Sudhir Khanger via KDE Bugzilla]

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

--- Comment #33 from Sudhir Khanger  ---
Hi Eike Hein,

In the old code of icon-only-task-manager there was code to show all windows of
an app. Is that same code still available in the newly rewritten icon-only-task
manager?

I will always have a few Chrome, Android Studio, and emulator windows. I find
it extremely annoying that I have to first click the group then click the
window. Or go through the filmsy animations.

So if that code is still available then I would like to learn a little bit
QML/C++ or whatever language it is written it and enable it for my personal
use. I want to disable all grouping in icon-only-task-manager similar to how it
is the regular task-manager widget.

If you could guide me where to look, I would be very grateful for that.

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

[digikam] [Bug 365973] digikam and program hung for a while then crashed

[scott via KDE Bugzilla]

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

--- Comment #3 from scott  ---
digikam ver 5.0 is unstable package  in my ver of LEAP

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

[kwin] [Bug 364699] Kubuntu: Kwin crash random times and windows menu and buttons disappear

[Wellington Torrejais da Silva via KDE Bugzilla]

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

--- Comment #8 from Wellington Torrejais da Silva  ---
In the next crash I will follow the #comment 6 instructions.

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

[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template

[Pulfer via KDE Bugzilla]

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

--- Comment #21 from Pulfer  ---
(In reply to Ivan Čukić from comment #20)
> > I used these ISOs for testing: 
> > https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15726
> 
> Is the live session supposed to crash or do I need to install it? (the live
> session seems to work for me)

Yes, live session supposed to crash. But it's not 100% reproducible. I guess it
may depend on boot speed. Marco could reproduce it (see comment 3).

I suggest to use this ISO for testing:
https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15736

This ISO has
https://quickgit.kde.org/?p=plasma-workspace.git=commit=214443fdff330629104509de9e1738aadcfe36b6
applied and extra debug output (
https://abf.rosalinux.ru/abondrov/plasma5-workspace/blob/rosa2014.1/plasma-workspace-5.7.2-debug.patch
) turned on.

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

[kpat] [Bug 366111] New: Kpatience crashes when clicking on Freecell

[Alexis Kauffmann via KDE Bugzilla]

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

Bug ID: 366111
   Summary: Kpatience crashes when clicking on Freecell
   Product: kpat
   Version: 3.6
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: co...@kde.org
  Reporter: l...@gehspace.com
CC: kde-games-b...@kde.org

Application: kpat (3.6)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 4.6.0-0.bpo.1-amd64 x86_64
Distribution: Debian GNU/Linux 8.5 (jessie)

-- Information about the crash:
- What I was doing when the application crashed: I started KPatience and then,
at the game option Window, I clicked on "Freecell" and, then KPatience crashed.
I then restarted KPatience, repeated the operation and played a Freecell game
with no further incidents. It happened three times today, which means this
problem is erratic (it does not happen every time) but consistent (repeats
frequently).

-- Backtrace:
Application: KPatience (kpat), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
#7  0x7fd3e1038894 in memcpy (__len=, __src=,
__dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:51
#8  SharedMemory::defragment (this=this@entry=0x7fd3cd806000) at
../../kdecore/util/kshareddatacache.cpp:727
#9  0x7fd3e1039a0a in SharedMemory::removeUsedPages (this=0x7fd3cd806000,
numberNeeded=4) at ../../kdecore/util/kshareddatacache.cpp:922
#10 0x7fd3e10326f1 in KSharedDataCache::insert (this=this@entry=0xa87fb0,
key=..., data=...) at ../../kdecore/util/kshareddatacache.cpp:1552
#11 0x7fd3e17f2b61 in KImageCache::insertImage (this=0xa87fb0, key=...,
image=...) at ../../kdeui/util/kimagecache.cpp:103
#12 0x00458d0d in ?? ()
#13 0x00458df0 in KAbstractCardDeck::cardPixmap(unsigned int, bool) ()
#14 0x0045b8e2 in KCard::paint(QPainter*, QStyleOptionGraphicsItem
const*, QWidget*) ()
#15 0x7fd3e03faa91 in QGraphicsScenePrivate::draw (this=0x7fd3cd878000,
this@entry=0x94b340, item=0xbbfad0, painter=0x7fffcf213460,
viewTransform=0x2000, viewTransform@entry=0x7fffcf2134f0, transformPtr=0x72,
transformPtr@entry=0x7fffcf213120, exposedRegion=0x7fd3cd809c68,
exposedRegion@entry=0x9d76b8, widget=0xa08320, opacity=3.2252605360516574e-319,
opacity@entry=1, effectTransform=0x0, wasDirtyParentSceneTransform=true,
drawItem=true) at graphicsview/qgraphicsscene.cpp:4964
#16 0x7fd3e03fb8c7 in QGraphicsScenePrivate::drawSubtreeRecursive
(this=this@entry=0x94b340, item=0xbbfad0, painter=painter@entry=0x7fffcf213460,
viewTransform=viewTransform@entry=0x7fffcf2134f0,
exposedRegion=exposedRegion@entry=0x9d76b8, widget=widget@entry=0xa08320,
parentOpacity=parentOpacity@entry=1, effectTransform=0x0) at
graphicsview/qgraphicsscene.cpp:4857
#17 0x7fd3e03fbfe0 in QGraphicsScenePrivate::drawItems (this=0x94b340,
painter=painter@entry=0x7fffcf213460,
viewTransform=viewTransform@entry=0x7fffcf2134f0,
exposedRegion=exposedRegion@entry=0x9d76b8, widget=0xa08320) at
graphicsview/qgraphicsscene.cpp:4739
#18 0x7fd3e041b17f in QGraphicsView::paintEvent (this=,
event=) at graphicsview/qgraphicsview.cpp:3471
#19 0x7fd3dfe2e748 in QWidget::event (this=0xa777a0, event=0x7fffcf213ba0)
at kernel/qwidget.cpp:8775
#20 0x7fd3e01f083e in QFrame::event (this=0xa777a0, e=0x7fffcf213ba0) at
widgets/qframe.cpp:557
#21 0x7fd3e0419e81 in QGraphicsView::viewportEvent (this=0xa777a0,
event=0x7fffcf213ba0) at graphicsview/qgraphicsview.cpp:2866
#22 0x7fd3e0a8a886 in
QCoreApplicationPrivate::sendThroughObjectEventFilters
(this=this@entry=0x7f8be0, receiver=receiver@entry=0xa08320,
event=event@entry=0x7fffcf213ba0) at kernel/qcoreapplication.cpp:1065
#23 0x7fd3dfddb46c in QApplicationPrivate::notify_helper
(this=this@entry=0x7f8be0, receiver=receiver@entry=0xa08320,
e=e@entry=0x7fffcf213ba0) at kernel/qapplication.cpp:4566
#24 0x7fd3dfde1fa8 in QApplication::notify (this=this@entry=0x7fffcf215510,
receiver=receiver@entry=0xa08320, e=e@entry=0x7fffcf213ba0) at
kernel/qapplication.cpp:4356
#25 0x7fd3e17891aa in KApplication::notify (this=0x7fffcf215510,
receiver=0xa08320, event=0x7fffcf213ba0) at
../../kdeui/kernel/kapplication.cpp:311
#26 0x7fd3e0a8a71d in QCoreApplication::notifyInternal
(this=0x7fffcf215510, receiver=receiver@entry=0xa08320,
event=event@entry=0x7fffcf213ba0) at kernel/qcoreapplication.cpp:955
#27 0x7fd3dfe28e1d in sendSpontaneousEvent (event=0x7fffcf213ba0,
receiver=0xa08320) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#28 QWidgetPrivate::drawWidget (this=this@entry=0xa07670,
pdev=pdev@entry=0x9fc5d0, rgn=..., offset=..., flags=flags@entry=4,
sharedPainter=sharedPainter@entry=0x0, 

[skrooge] [Bug 366025] Skrooge perpetually asks me to save updated tab state

[via KDE Bugzilla]

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

--- Comment #3 from dberg...@gmail.com ---
Thanks for your reply.

Actually, I have tried removing ~/.config/skroogerc a number of times in the
past. It works the first time I open Skrooge after removal--the popup windows
go away--but once it writes a new config file and I close the application and
reopen it, the problem comes back.

There are a few options about saving page states in Skrooge's settings, but
they don't seem to work. One is "Update modified pages on close" and the other
is "Update modified bookmarks on close." I have both set to "Never." I don't
think those are related to my issue though, because those options sound like
they affect behavior when closing the whole application, not just a page or a
bookmark within the application itself.

What I find strange is that I haven't even changed the state of any of these
pages, but Skrooge thinks they've changed and asks me to save the "modified"
state. Based on my observation, it seems that page states are actually saved
into the SKG file and not the skroogerc file, which leads me to believe there's
something wrong with my SKG file. I have attached an anonymized version with
which you may be able to reproduce the issue.

This is occurring on a newly compiled 2.4.0 package in Fedora 24. On Arch
Linux, which I have installed on another computer, I don't get the popups, but
I can see that Skrooge thinks the page states are all modified on startup.

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

[skrooge] [Bug 366025] Skrooge perpetually asks me to save updated tab state

[via KDE Bugzilla]

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

--- Comment #2 from dberg...@gmail.com ---
Created attachment 100305
  --> https://bugs.kde.org/attachment.cgi?id=100305=edit
Anonymized test file

Anonymized SKG file that may have broken page states saved in it.

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

[krita] [Bug 342105] [HUION] Cannot right click with the Pen of Huion H610 Pro

[via KDE Bugzilla]

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

jschl...@gmail.com changed:

   What|Removed |Added

 CC||jschl...@gmail.com

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

[Discover] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied

[Adam Felson via KDE Bugzilla]

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

--- Comment #75 from Adam Felson  ---
Hard to say.  There are no files in the system containing the letters 'systray'
except for ksystraycmd.mo part of kde-l10n-engb (version 4:15.12.3-0ubun) and
the hp-system-tray.

"Discover" and  is version 5.6.2
muon-updater and notifier are both 4:5.6.2-1ubuntu

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

[Discover] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied

[Adam Felson via KDE Bugzilla]

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

--- Comment #74 from Adam Felson  ---
Hard to say.  There are no files in the system containing the letters 'systray'
except for ksystraycmd.mo part of kde-l10n-engb (version 4:15.12.3-0ubun) and
the hp-system-tray.

"Discover" and  is version 5.6.2
muon-updater and notifier are both 4:5.6.2-1ubuntu

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

[okular] [Bug 325650] reading direction Right to Left

[Olivier Churlaud via KDE Bugzilla]

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

Olivier Churlaud  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/okul
   ||ar/04908dba2f93842a0008ef1b
   ||a8c966621c615f9e
 Resolution|--- |FIXED

--- Comment #16 from Olivier Churlaud  ---
Git commit 04908dba2f93842a0008ef1ba8c966621c615f9e by Olivier CHURLAUD.
Committed on 25/07/2016 at 23:37.
Pushed by ochurlaud into branch 'master'.

Adding RTL reading mode feature to okular

Commited on behalf of Fahad Al-Saidi

REVIEW: 125397

M  +1-0conf/dlggeneral.cpp
M  +73   -13   conf/dlggeneralbase.ui
M  +3-0conf/okular.kcfg
M  +25   -6ui/pageview.cpp

http://commits.kde.org/okular/04908dba2f93842a0008ef1ba8c966621c615f9e

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

[kdelibs] [Bug 279592] Allow per-application color scheme

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kdev |http://commits.kde.org/kdev
   |platform/938f1f7f14443180e9 |elop/f6965687228383239cdf5b
   |1a55b0180e42589c3a3af5  |1e97c012e82fd5d119

--- Comment #16 from Aleix Pol  ---
Git commit f6965687228383239cdf5b1e97c012e82fd5d119 by Aleix Pol, on behalf of
Alexander Zhigalin.
Committed on 25/07/2016 at 23:26.
Pushed by apol into branch 'master'.

Implement color scheme selection from these installed in the system using
KColorSchemeManager

Implement color scheme selection from these installed in the system using
KColorSchemeManager

REVIEW: 127980

M  +2-1app/kdevelopui.rc

http://commits.kde.org/kdevelop/f6965687228383239cdf5b1e97c012e82fd5d119

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

[kdelibs] [Bug 279592] Allow per-application color scheme

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdev
   ||platform/938f1f7f14443180e9
   ||1a55b0180e42589c3a3af5

--- Comment #15 from Aleix Pol  ---
Git commit 938f1f7f14443180e91a55b0180e42589c3a3af5 by Aleix Pol, on behalf of
Alexander Zhigalin.
Committed on 25/07/2016 at 23:25.
Pushed by apol into branch 'master'.

Implement color scheme selection from these installed in the system using
KColorSchemeManager

Implement color scheme selection from these installed in the system using
KColorSchemeManager

REVIEW: 127979

M  +3-0shell/CMakeLists.txt
A  +106  -0shell/colorschemechooser.cpp [License: LGPL]
A  +60   -0shell/colorschemechooser.h [License: LGPL]
M  +4-0shell/mainwindow_p.cpp

http://commits.kde.org/kdevplatform/938f1f7f14443180e91a55b0180e42589c3a3af5

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

[kdenlive] [Bug 366105] git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jesse via KDE Bugzilla]

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

--- Comment #7 from Jesse  ---
Thanks for the explanation, JB. It was a minor issue -- no biggie. :) Thanks
for the fix!

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

[kdenlive] [Bug 366105] git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #6 from Jean-Baptiste Mardelle  ---
Thanks for the project file. The crash happened because of a change I made
yesterday to the qtblend filter (called Transform in Kdenlive).

The names of the parameters for this filter have been changed which caused the
crash. I fixed the crash, but for projects created with the older version  of
the filter, all parameters will be reset to default. If you want to recover
your effect parameters, you can open the .kdenlive project file in a text
editor and make the following replacements:

"transition.rect" should become "rect"
"transition.compositing" should become "compositing"
"transition.distort" should become "distort"

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

[krita] [Bug 366001] [Cintiq] Krita crashes on second brush stroke on a newly opened document.

[andyvandalsem via KDE Bugzilla]

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

--- Comment #4 from andyvandalsem  ---
Confirming crash is no longer occurring for me on posted updated build.

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

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Keywords||multiscreen
 Ever confirmed|0   |1

--- Comment #5 from Sebastian Kügler  ---
Thanks for the bug report! I've had a look at the info you provided, here's my
analysis:

Facts: 
- kscreen can write out a working configuration for your setup
- when logging in, kscreen fails to restore the working config
- a new configuration for your setup is written, your external screens are
disabled
- the modes aren't written because the displays are set to disabled
Fiction (my interpretation):
- when logging in, kscreen somehow fails to enable the two external displays
- it then writes out a new configuration with the two externals disabled,
overwriting the correct previous config file
- the correct config is now gone until you set the displays explicitly to
enabled again (crossing fingers that it works this time)
- everything is peachy, until it fails again...

A problem with debugging is is that we can't really see what's going on deep
down in xrandr. These calls are all made out of process, and it's quite hard to
get reliable information from it.

Questions:
- Could you try making the correct config file (in a working setup)
non-writable for your user, for example by chowning it (temporarily) to root?
In this case, do subsequent login attempts work?
- It would indeed be interesting to see if this is only a problem with your MST
setup, so if you could try displayport / hdmi as well, that would be useful
information.

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

[kdenlive] [Bug 366105] git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jesse via KDE Bugzilla]

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

--- Comment #4 from Jesse  ---
Created attachment 100304
  --> https://bugs.kde.org/attachment.cgi?id=100304=edit
project file

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

[kdenlive] [Bug 366105] git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jesse via KDE Bugzilla]

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

--- Comment #3 from Jesse  ---
I believe this was before the preview combo box was implemented, so yes, I
think.

Attaching the project file, now.

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

[frameworks-kguiaddons] [Bug 365053] Icon overlay discards origin

[gandolfi rafael via KDE Bugzilla]

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

--- Comment #3 from gandolfi rafael  ---
Created attachment 100303
  --> https://bugs.kde.org/attachment.cgi?id=100303=edit
Screenshot of KIconUtils::addOverlay with and without the patch

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[Steve via KDE Bugzilla]

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

Steve  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[Steve via KDE Bugzilla]

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

--- Comment #12 from Steve  ---
You fixed it!

Thanks

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

[extra-cmake-modules] [Bug 366110] New: Target "install/strip" is missing in Makefile when BUILD_TESTING=OFF

[Yuri via KDE Bugzilla]

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

Bug ID: 366110
   Summary: Target "install/strip" is missing in Makefile when
BUILD_TESTING=OFF
   Product: extra-cmake-modules
   Version: 5.24.0
  Platform: FreeBSD Ports
OS: FreeBSD
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alex.me...@kde.org
  Reporter: y...@tsoft.com
CC: ecm-bugs-n...@kde.org

FreeBSD calls "make install/strip" during the port build. It only succeeds when
BUILD_TESTING=ON.

Reproducible: Always

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

[Discover] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied

[Aleix Pol via KDE Bugzilla]

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

--- Comment #73 from Aleix Pol  ---
@Adam, what version are you using?

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

[digikam] [Bug 366104] digikam5 "hangs' @ 100%CPU at exit

[RJVB via KDE Bugzilla]

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

--- Comment #2 from RJVB  ---
Not until mid august, I'm purely a user for a couple of weeks.

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

[KScreen] [Bug 362570] Kscreen settings no longer shows display ID since 16.04 update

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

   Version Fixed In||5.7.3
  Latest Commit|http://commits.kde.org/kscr |http://commits.kde.org/kscr
   |een/e6b052db712fbc1d773f0b0 |een/71c5187ac9d3dc239893523
   |3220fab9754db0faf   |22a31e445f7938dd9

--- Comment #8 from Sebastian Kügler  ---
Git commit 71c5187ac9d3dc23989352322a31e445f7938dd9 by Sebastian Kügler.
Committed on 25/07/2016 at 22:15.
Pushed by sebas into branch 'Plasma/5.7'.

[kcm] Show output name in output preview

Summary:
When identical displays are connected, the identify overlay would display
the output name, while the preview in the kcm displays the display vendor
and model. There's no way to tell which display is which.

This patch adds a row in the output preview, it moves the vendor up,displays
and displays the output name underneath (if not duplicated).
FIXED-IN:5.7.3

Before: {F190822}

After: {F190823}

Test Plan:
started kcm with multiple displays connected, I can now distinguish them
based on the name of the connector

Reviewers: #plasma, graesslin

Reviewed By: #plasma, graesslin

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D2248

M  +21   -7kcm/qml/Output.qml

http://commits.kde.org/kscreen/71c5187ac9d3dc23989352322a31e445f7938dd9

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

[digikam] [Bug 366036] Sidecar file is not written when image is symlink to write-protected directory

[Simon via KDE Bugzilla]

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

--- Comment #11 from Simon  ---
So I just opened digikam for the first time after compiling it with 
Maik's commit. It looks like digikam now detects the symlinks as 
duplicates. This output was printed repeatedly while scanning for new items:

 digikam.database: Recognized "*somefile*" as identical to item 56019

For testing I looked up which file has ID 56019 and changed a tag on it. 
This change is then not visible in *somefile*. The same is true the 
other way round. So digikam seems to recognize that these are the same 
items but it does not do anything about it.

On 25/07/16 20:18, Thomas Reifenberger via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=366036
>
> --- Comment #10 from Thomas Reifenberger  ---
> Just FYI: At least on my machine (up-to-date ArchLinux), the darktable 
> versions
> 1.6.7 up to 2.0.5 handle the scenario described above as expected (respect
> symlinks, create/update sidecar file next to symlink).
>
> (In reply to Maik Qualmann from comment #8)
>> Also Darktable created not a sidecar file and prints a exiv2 exception.
>>
>> Maik

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #9 from David Faure  ---
Fixed by
http://commits.kde.org/kcalcore/3023b48e9782ae047c3f9edf122e1cd4958f5e82

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

[plasmashell] [Bug 356175] [wayland] plasmashell crashes at startup

[Lóránt Farkas via KDE Bugzilla]

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

Lóránt Farkas  changed:

   What|Removed |Added

 CC||farkasl...@gmail.com

--- Comment #12 from Lóránt Farkas  ---
I am running an ArchLinux box (I have logind) but plasmashell crashes.

If I run the command:
$kstart plasmashell

Then I get:
>kstart(...) main: Omitting both --window and --windowclass arguments is not 
>recommended
>KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
>sock_file=/run/user/1010/kdeinit5__0
>KCrash: Attempting to  start /usr/lib/drkonqi from kdeinit
>sock_file=/run/user/1010/kdeinit5__0

drkonqi does not start.

For the command:
$/usr/bin/plasmashell 

I get:

>No metadata file in the package, expected it at: 
>"/home/USERNAME/Desktop//metadata.desktop"
3x times, then
>file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:80:
> TypeError: Cannot read property 'formFactor' of null
And a bunch of line like that. Again KCrash ans sockfile and at the end:
QsocketNotifier: Invalid socket 9 and type 'Read', disabling...

(Sorry, the clipboard cannot paste its value to the browser.)

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

--- Comment #8 from David Faure  ---
Found a Qt bug report about this, reopened it with more details,
https://bugreports.qt.io/browse/QTBUG-51758.

Meanwhile it's quite pointless to do all this for an empty container, I'll add
an if() in kcalcore, good for performance, not just as a workaround.

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #11 from Jean-Baptiste Mardelle  ---
Git commit 0bdcee3f687ee1ac655bce896c0a6833fa88ea13 by Jean-Baptiste Mardelle.
Committed on 25/07/2016 at 21:56.
Pushed by mardelle into branch 'Applications/16.08'.

Fix timeline cannot be properly resized

M  +6-6src/ui/timeline_ui.ui

http://commits.kde.org/kdenlive/0bdcee3f687ee1ac655bce896c0a6833fa88ea13

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

--- Comment #7 from David Faure  ---
I have reduced the issue to this testcase, which crashes indeed.

QVector vec;
vec.erase(std::remove(vec.begin(), vec.end(), 42), vec.end());
vec.reserve(0);

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

[kcalcore] [Bug 362724] enable calendar

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED
 CC||fa...@kde.org

--- Comment #3 from David Faure  ---


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

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||m...@xanum.uam.mx

--- Comment #6 from David Faure  ---
*** Bug 362724 has been marked as a duplicate of this bug. ***

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

[korgac] [Bug 358152] korganizer reminder tool crashes at akonadi/kontact start

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||fa...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #2 from David Faure  ---


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

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

[korgac] [Bug 362012] akonadi crashes whenever I try to start it from the command line

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from David Faure  ---


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

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

[korganizer] [Bug 362183] crash while adding new event

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||fa...@kde.org

--- Comment #1 from David Faure  ---


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

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||christiande...@web.de

--- Comment #3 from David Faure  ---
*** Bug 358152 has been marked as a duplicate of this bug. ***

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||amos.elb...@gmail.com

--- Comment #4 from David Faure  ---
*** Bug 362012 has been marked as a duplicate of this bug. ***

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Assignee|korganizer-de...@kde.org|fa...@kde.org
 CC||korganizer-de...@kde.org
 Ever confirmed|0   |1

--- Comment #2 from David Faure  ---
Also happens when disabling/re-enabling some calendars, same backtrace.

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||kol...@aon.at

--- Comment #5 from David Faure  ---
*** Bug 362183 has been marked as a duplicate of this bug. ***

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

[korganizer] [Bug 355736] korganizer crashes in QVector<QSharedPointer >::reserve(int)

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||fa...@kde.org
Summary|korganizer crashes when |korganizer crashes in
   |'akonadictl restart' is run |QVector::reserve(int)

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

[digikam] [Bug 366019] Digikam Crashes when Table view button is clicked

[via KDE Bugzilla]

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

--- Comment #8 from caulier.gil...@gmail.com ---
It's not reproducible for the moment. I must try to have an album with enough
items as specified in comment #5.

It's strange that problem is not reproducible in same conditions under Linux (I
must admit that i use rarely Table View in fact)
Gilles

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

[plasmashell] [Bug 359661] Digital clock is not updated consistently

[Erik Quaeghebeur via KDE Bugzilla]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||kdebugs@equaeghe.nospammail
   ||.net

--- Comment #5 from Erik Quaeghebeur  ---
I can confirm this behavior on plasma 5.5.5. It appears it's also been reported
elsewhere: https://bugzilla.redhat.com/show_bug.cgi?id=1307178

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

[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi

[Holger via KDE Bugzilla]

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

--- Comment #8 from Holger  ---
To be precise: The Java Process is in no way unresponsive = frozen. It's
actually running fine. I'm seeing this with http://tvbrowser.org It will
display the normal reminder-dialogs. From such a reminder, you can open the
details of the tv-show opening in a second dialog. From there you can configure
the left panel and access the settings, from where you can toggle the minimize
to tray, which will correctly remove or add the tray-icon on apply. TV-Browser
itself is running just fine, only it's tray-icon never gets any mouse events.

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

[digikam] [Bug 365410] Fullscreen only shows one image - no way to navigate.

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||alexander-...@xmine128.tk

--- Comment #6 from Maik Qualmann  ---
*** Bug 366109 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 366109] Slideshow freezes on first image (Windows)

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Maik Qualmann  ---


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

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

[digikam] [Bug 366019] Digikam Crashes when Table view button is clicked

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #7 from Maik Qualmann  ---
Yes I remember. But I think that this problem has another cause. We use the
at() function at some places in the table view. Gilles, you can not reproduce
it?

Maik

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

[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi

[Holger via KDE Bugzilla]

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

Holger  changed:

   What|Removed |Added

 CC||h.kl...@gmx.de

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

[Akonadi] [Bug 365991] Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."

[Dieter Zander via KDE Bugzilla]

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

Dieter Zander  changed:

   What|Removed |Added

 CC||dieter...@gmx.de

--- Comment #4 from Dieter Zander  ---
same problem here

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

[digikam] [Bug 366109] New: Slideshow freezes on first image

[Alexander Schlarb via KDE Bugzilla]

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

Bug ID: 366109
   Summary: Slideshow freezes on first image
   Product: digikam
   Version: 5.0.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: SlideShow
  Assignee: digikam-de...@kde.org
  Reporter: alexander-...@xmine128.tk

The first image will be successfully displayed within the fullscreen window,
advancing to another image using the arrows or by waiting for the timer, will
change the image digiKam thinks it's showing, but not update the contents of
the fullscreen window (neither progress bar nor displayed image will change).

Reproducible: Always

Steps to Reproduce:
1. Select an image
2. Click on the "Show full screen" button
3. Click on the "Next image" (double forward arrow) button

Actual Results:  
Nothing (no change in display whatsoever)

Expected Results:  
Change image to something else

Windows 10 Home x86, 3GiB RAM
Graphics: Intel® Q35 Express Chipset (WDDM 1.0)

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

[digikam] [Bug 366109] Slideshow freezes on first image (Windows)

[Alexander Schlarb via KDE Bugzilla]

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

Alexander Schlarb  changed:

   What|Removed |Added

Summary|Slideshow freezes on first  |Slideshow freezes on first
   |image   |image (Windows)

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

[digikam] [Bug 365684] Tags Manager : Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

--- Comment #21 from caulier.gil...@gmail.com ---
>or digikam is somehow being affected by environment of one of the user accounts
>(PATH,DYLD_LIBRARY_PATH etc.).

None of them. digiKam is packaged as a stand alone bundle application.

when you said that it do not crash with a new account, do you point the same
collection and the same DB files than with suspicious account ?

What's about right access to DB file with the problematic account ? User is in
the right group with the the right than good ones ?
The DB file/dir can be open in RW by problematic account ?
What's happen when you create the DB in another place with problematic account
?

Gilles Caulier

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

[digikam] [Bug 366019] Digikam Crashes when Table view button is clicked

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #6 from caulier.gil...@gmail.com ---
Daniel,

No need. This is clear :

digikam.general: Stacked View Mode :  3
ASSERT failure in QList::at: "index out of range", file
/opt/digikam/libexec/qt5/lib/QtCore.framework/Headers/qlist.h, line 531
Abort trap: 6

Maik, 

The famous bug in table view is back. Do you remember ?

Gilles Caulier

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

[digikam] [Bug 366104] digikam5 "hangs' @ 100%CPU at exit

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Can you reproduce the problem with current implementation from git/master (next
5.1.0) ?

Gilles Caulier

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

[digikam] [Bug 365876] Adjust date/time menu entry missing (digikam 5)

[via KDE Bugzilla]

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

--- Comment #6 from caulier.gil...@gmail.com ---
If we add an entry for timeadjust in AlbumView menu, we must do it for all BQM
tools. This will bloat the GUI and it's not the goal.

All tools to manage item metadata are now hosted in BQM section. It's clear, no
more. We wan't no extra dialog for only this tool. Also the way to chain tools
together is a real advantage. This is the goal of BQM, ask by other users...

This tool, previously written as KIPI plugin is not shared anymore. In fact all
batch tools from KIPI will be migrated to BQM as well. Only export/Import to
web services tools will stay in KIPI.

If necessary, the rest of improvements of this tool, GUI behavior included,
must be talk in other report as i said previously...

Gilles Caulier

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

[kio] [Bug 366108] New: MTP recursively allow request.

[Maksim via KDE Bugzilla]

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

Bug ID: 366108
   Summary: MTP recursively allow request.
   Product: kio
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: mtp
  Assignee: philschm...@gmx.net
  Reporter: maksim.mur...@gmail.com

After connect the phone I have endless 'reconnect' which started from 'deny /
allow' request on the phone after seems like it goes reconnect again and ask
this again and so on.

:~$ mtpfs --version
Listing raw device(s)
   No raw devices found.
mf@mf-laptop:~$ mtpfs --version
Listing raw device(s)
Device 0 (VID=1004 and PID=633e) is a LG Electronics Inc. LG G Flex 2.
   Found 1 device(s):
   LG Electronics Inc.: LG G Flex 2 (1004:633e) @ bus 2, dev 22
Attempting to connect device
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object
handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
Listing File Information on Device with name: MF_G4
LIBMTP_Get_Storage() failed:-1

kio-mtp is already the newest version (0.75+git20140304-2).


Reproducible: Always

Steps to Reproduce:
1. connect the phone
2. press allow on popup question
3. goes to 2 stage again

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

[ktorrent] [Bug 365837] KTorrent Web shows ISS Default page

[juan carlos via KDE Bugzilla]

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

juan carlos  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[Steve via KDE Bugzilla]

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

--- Comment #9 from Steve  ---
I just tested and the problem is still present.

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

[kdenlive] [Bug 366068] Can not right-click a guideline and choose "Delete Guide"

[Steve via KDE Bugzilla]

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

Steve  changed:

   What|Removed |Added

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

--- Comment #3 from Steve  ---
That worked. I can now right click and delete a guide.

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

[krita] [Bug 366099] fill tool fills the entire layer

[Sven Langkamp via KDE Bugzilla]

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

Sven Langkamp  changed:

   What|Removed |Added

 CC||sven.langk...@gmail.com

--- Comment #1 from Sven Langkamp  ---
This should already work. It could be that the threshold is too high for your
drawing. Lower the threshold in the tool options  to check if that solves the
problem. 

Otherwise check if fill entire selection is checked or not.

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

[kdenlive] [Bug 366105] git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
did you use the qtblend effect on this clip (called Transform in effect stack)
? Could you attach the project file ?

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

[kdeconnect] [Bug 365731] Error while try to manage files from computer on mobile

[Sinka Péter via KDE Bugzilla]

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

Sinka Péter  changed:

   What|Removed |Added

 CC||sinkape...@hotmail.com

--- Comment #1 from Sinka Péter  ---
Created attachment 100302
  --> https://bugs.kde.org/attachment.cgi?id=100302=edit
syslog

The IP-adress of phone is wrong, if I change it  , and run the sshfs command in
terminal, the phone mounts.

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

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

[Philippe Waroquiers via KDE Bugzilla]

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

Philippe Waroquiers  changed:

   What|Removed |Added

 CC||philippe.waroquiers@skynet.
   ||be

--- Comment #3 from Philippe Waroquiers  ---
Thanks for the bug report.
The program is however still quite big (> 400 SLOC), accesses a bunch of calls
from sound related libraries, is using include files not installed by default
(at least on
my setup), and understanding what this program does is not trivial.
E.g. I do not see why the line after #ifndef BUG
is needed: this seems to get the nr of channels that were set just before ???

So, it would be nice if you could isolate the buffer overflow in the minimal
program
to cause valgrind crash, and largely preferrably without dependencies to sound
libraries
and similar. I understand that this might be far to be easy, so below are other
ideas to help determine what is wrong in Valgrind.


First, it is strange that in the output file, the host stack trace has no
source/line nr.
This valgrind seems to have been built/compiled an unusual way.
Can you re-run with a valgrind compiled the 'classical way', so that the host
stacktrace
contains source/line nrs ?

Also, it is normal that valgrind does not (always) detect buffer overflow.
See e.g. manual for --redzone-size parameter.
Try to re-run with the max allowed redzone size (4096) as this will detect the
buffer overflow
as long as the 'overflow' is less than 4Kb far from the end of the allocated
buffer.

(and of course, valgrind memcheck tool detects buffer overflow in malloc-ed
buffers,
but not buffers on the stack and global (you might try --tool=exp-sgcheck for
that)
or buffer overflows inside array inside struct. 

An undected buffer overflow normally however by itself should not lead to a
SEGV inside
valgrind code, so this is still puzzling.
I am wondering if this is not the result of a side effect of hacking with the
nr of channels
(maybe due to a syscall with arguments not fully checked by Valgrind, leading
to this SIGSEGV).
It would be also nice to re-run with more trace e.g.
   -v -v -v -d -d -d --trace-syscalls=yes

Thanks

Philippe

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

[digikam] [Bug 317210] THUMBDB : delete image removes file, but does not remove thumbnails

[via KDE Bugzilla]

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

--- Comment #36 from swatilodh...@gmail.com ---
I think that what happens now is partially right. 'Cause when an item is "Moved
to trash", it is just removed and not permanently deleted. So it is right to
exist in table with album=NULL

The issue lies when that item is "permanently" deleted and there's no change in
the Images table.

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #8 from Jean-Baptiste Mardelle  ---
Thanks for your screenshots. I cannot reproduce, it might depend on the Qt/KDE
Frameworks version. I reverted a recent change that might fix the issue, please
test whenever you can.

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

[digikam] [Bug 365876] Adjust date/time menu entry missing (digikam 5)

[Kristian via KDE Bugzilla]

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

--- Comment #5 from Kristian  ---
I give up. Apparently, you're not willing to discuss with me about the - in my
eyes - poor usability of the Adjust time tool via BQM compared to the old
solution. I still think that a direct link (or something that eases the use)
would be more user-friendly. Bug #365907 is not about usability.

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

[digikam] [Bug 366019] Digikam Crashes when Table view button is clicked

[Daniel McCubbing via KDE Bugzilla]

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

--- Comment #5 from Daniel McCubbing  ---
Sorry for taking so long to get back to you.

Items in Album: 
Several albums ranging in size from just about 10 to over 1000 with nested
albums
Album used below had 149 images and a sub album.
The Album in my other account only had one image and no nested albums

Image Formats: 
Primarily JPG, with possibly a few PNG and TIF thrown in.

Album View Presentation Options: 
Sort by Folder
Order Ascending
Group by Album
Group Sort Ascending
Include Tag Sub Tree

Color Managed View: is on

Here is the console output from the after I clicked the Table View button in my
personal Account with 149 photos in the album:

digikam.geoiface: 
digikam.geoiface: 
digikam.general: Stacked View Mode :  0
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.general: Using  4  CPU core to run threads
digikam.general: Action Thread run  1  new jobs
digikam.general: Data From DBJobsThread is null:  true
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.general: Using  4  CPU core to run threads
digikam.general: Stacked View Mode :  2
digikam.general: Action Thread run  1  new jobs
digikam.general: Data From DBJobsThread is null:  true
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.general: Using  4  CPU core to run threads
digikam.general: Stacked View Mode :  0
digikam.general: Action Thread run  1  new jobs
digikam.general: Data From DBJobsThread is null:  true
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.general: Using  4  CPU core to run threads
digikam.general: Action Thread run  1  new jobs
digikam.general: Data From DBJobsThread is null:  true
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.general: Using  4  CPU core to run threads
digikam.general: Action Thread run  1  new jobs
digikam.general: Data From DBJobsThread is null:  true
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.geoiface: 
digikam.geoiface: 
digikam.geoiface: 
digikam.general: Using  4  CPU core to run threads
digikam.general: Action Thread run  1  new jobs
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.geoiface: 
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0022.jpg"  : JPEG file identified
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0022.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0024.jpg"  : JPEG file identified
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0024.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0026.jpg"  : JPEG file identified
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0026.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0028.jpg"  : JPEG file identified
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0028.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0030.jpg"  : JPEG file identified
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0030.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0032.jpg"  : JPEG file identified
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0032.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0036.jpg"  : JPEG file identified
digikam.dimg: "/Users/daniel/Pictures/Pictures/Daniel's/BC Roadtrip/File aa
0036.jpg"  : JPEG file identified
digikam.metaengine: Orientation 

[kdenlive] [Bug 366107] New: Crash when clicking on track compositing menu

[farid via KDE Bugzilla]

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

Bug ID: 366107
   Summary: Crash when clicking on track compositing menu
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: snd.no...@gmail.com

When trying to switch between none, preview and high quality from the dropdown
i get a crash.

I am using today's build.

Reproducible: Always

Steps to Reproduce:
1. open kdenlive
2. click on the compositing dropdown menu and try to switch a preview mode
3. crash



Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault.
0x76fa330c in mlt_service_connect_producer () from /usr/lib/libmlt.so.6
(gdb) thread apply all bt

Thread 19 (Thread 0x7fff78edf700 (LWP 9847)):
#0  0x7fffefe66791 in ppoll () from /usr/lib/libc.so.6
#1  0x7fffe7c1a99d in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#2  0x7fffe7c1af8e in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#3  0x7fffb7af7eed in ?? () from /usr/lib/libSDL-1.2.so.0
#4  0x7fffb7acb800 in ?? () from /usr/lib/libSDL-1.2.so.0
#5  0x7fffb7ad3fe8 in ?? () from /usr/lib/libSDL-1.2.so.0
#6  0x7fffb7b158a9 in ?? () from /usr/lib/libSDL-1.2.so.0
#7  0x7fffee328484 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fffefe6f6dd in clone () from /usr/lib/libc.so.6

Thread 18 (Thread 0x7fff796e0700 (LWP 9846)):
#0  0x7fffee32e0af in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x76faa243 in ?? () from /usr/lib/libmlt.so.6
#2  0x0073fe9d in ?? ()
#3  0x70860d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fffee328484 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fffefe6f6dd in clone () from /usr/lib/libc.so.6

Thread 17 (Thread 0x7fff79ee1700 (LWP 9845)):
#0  0x7fffee32e0af in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fffac28ef9f in ?? () from /usr/lib/mlt/libmltsdl.so
#2  0x7fffee328484 in start_thread () from /usr/lib/libpthread.so.0
#3  0x7fffefe6f6dd in clone () from /usr/lib/libc.so.6

Thread 15 (Thread 0x7fff7b7fd700 (LWP 9843)):
#0  0x7fffefe666cd in poll () from /usr/lib/libc.so.6
#1  0x7fffe8097fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fffe80980ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x70a8f59b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x70a390da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7085c0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x70860d78 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fffee328484 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fffefe6f6dd in clone () from /usr/lib/libc.so.6

Thread 14 (Thread 0x7fff7bffe700 (LWP 9842)):
---Type  to continue, or q  to quit---
#0  0x7fffee32e0af in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x70861c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7623a435 in ?? () from /usr/lib/libQt5Quick.so.5
#3  0x7623ad2a in ?? () from /usr/lib/libQt5Quick.so.5
#4  0x70860d78 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fffee328484 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fffefe6f6dd in clone () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7fff94d03700 (LWP 9841)):
#0  0x7fffefe666cd in poll () from /usr/lib/libc.so.6
#1  0x7fffe8097fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fffe80980ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x70a8f57f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x70a390da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7085c0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x70860d78 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7fffee328484 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fffefe6f6dd in clone () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7fff95704700 (LWP 9840)):
#0  0x7fffee32e0af in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x70861c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7623a435 in ?? () from /usr/lib/libQt5Quick.so.5
#3  0x7623ad2a in ?? () from /usr/lib/libQt5Quick.so.5
#4  0x70860d78 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fffee328484 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fffefe6f6dd in clone () from /usr/lib/libc.so.6

Thread 11 (Thread 0x7fff96ffe700 (LWP 9839)):
#0  0x7fffefe666cd in poll () from /usr/lib/libc.so.6
#1  0x7fffe7c29121 in ?? () 

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #7 from Jean-Baptiste Mardelle  ---
Git commit 68c0477b84038e77beb0badcfba93667f229ca1d by Jean-Baptiste Mardelle.
Committed on 25/07/2016 at 20:11.
Pushed by mardelle into branch 'Applications/16.08'.

Fix delete guide hard to reach from timeline ruler on low zoom
Related: bug 366068
Change timline size policy

M  +1-1src/mainwindow.cpp
M  +1-2src/timeline/customruler.cpp
M  +8-5src/timeline/customtrackview.cpp
M  +5-1src/timeline/customtrackview.h

http://commits.kde.org/kdenlive/68c0477b84038e77beb0badcfba93667f229ca1d

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

[kdenlive] [Bug 366068] Can not right-click a guideline and choose "Delete Guide"

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 68c0477b84038e77beb0badcfba93667f229ca1d by Jean-Baptiste Mardelle.
Committed on 25/07/2016 at 20:11.
Pushed by mardelle into branch 'Applications/16.08'.

Fix delete guide hard to reach from timeline ruler on low zoom
Related: bug 366066
Change timline size policy

M  +1-1src/mainwindow.cpp
M  +1-2src/timeline/customruler.cpp
M  +8-5src/timeline/customtrackview.cpp
M  +5-1src/timeline/customtrackview.h

http://commits.kde.org/kdenlive/68c0477b84038e77beb0badcfba93667f229ca1d

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

[konsole] [Bug 366106] New: konsole crash on exit

[Rafis Kamaliev via KDE Bugzilla]

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

Bug ID: 366106
   Summary: konsole crash on exit
   Product: konsole
   Version: 15.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: ra...@pisem.net

Application: konsole (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.27-24-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: send exit comand to konsole. I
was using fdisk, kpart and mkdosfs in it.

- Unusual behavior I noticed: bluetooth apple magic mouse disconnected right
after that

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f41d871f800 (LWP 11869))]

Thread 2 (Thread 0x7f41c14b5700 (LWP 11870)):
#0  0x7f41d80665ab in __lll_lock_wait_private () at /lib64/libc.so.6
#1  0x7f41d7ff3033 in _L_lock_12558 () at /lib64/libc.so.6
#2  0x7f41d7ff131b in calloc () at /lib64/libc.so.6
#3  0x7f41ca7390bb in  () at /usr/lib64/tls/libnvidia-tls.so.340.96
#4  0x7f41cf389e62 in __nptl_deallocate_tsd () at /lib64/libpthread.so.0
#5  0x7f41cf38a0b7 in start_thread () at /lib64/libpthread.so.0
#6  0x7f41d805a02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f41d871f800 (LWP 11869)):
[KCrash Handler]
#6  0x7f41d7fed1d5 in malloc_consolidate () at /lib64/libc.so.6
#7  0x7f41d7fedcfb in _int_free () at /lib64/libc.so.6
#8  0x7f41c383c7a0 in  () at /usr/lib64/libQt5XcbQpa.so.5
#9  0x7f41c380cbc1 in QXcbConnection::~QXcbConnection() () at
/usr/lib64/libQt5XcbQpa.so.5
#10 0x7f41c380d3d9 in QXcbConnection::~QXcbConnection() () at
/usr/lib64/libQt5XcbQpa.so.5
#11 0x7f41c3813f8e in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#12 0x7f41c3814089 in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#13 0x7f41d4b44cb5 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
at /usr/lib64/libQt5Gui.so.5
#14 0x7f41d52db469 in QApplicationPrivate::~QApplicationPrivate() () at
/usr/lib64/libQt5Widgets.so.5
#15 0x7f41d4634314 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#16 0x7f41d52dcfec in QApplication::~QApplication() () at
/usr/lib64/libQt5Widgets.so.5
#17 0x7f41d8345e93 in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#18 0x7f41d7f96b25 in __libc_start_main () at /lib64/libc.so.6
#19 0x004007ee in _start ()

Reported using DrKonqi

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

[plasma-pa] [Bug 365771] Multimedia keys should change volume of active sink or global

[David Rosca via KDE Bugzilla]

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

David Rosca  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-pa/6c2f9f27543bdfef448c8
   ||7601a9aa52d271f7927
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from David Rosca  ---
Git commit 6c2f9f27543bdfef448c87601a9aa52d271f7927 by David Rosca.
Committed on 25/07/2016 at 20:01.
Pushed by drosca into branch 'master'.

Try to be more clever about what sink to use for volume control

This changes the applet to display volume icon and control volume
through scroll / global shortcuts of "preferred" sink.

Preferred sink is currently chosen according to these rules:
  * if there is only one sink, that sink is preferred
  * if there is some sink that is currently playing some sound, that
sink is preferred (if default sink is playing sound, default sink
is used instead)
  * if there is some sink that is currently idle (there are streams on
the device, but not currently playing), that one sink is preferred
(same exception for default sink is used here as in case above)

This should help with changing the volume of correct audio device in
most cases.

Differential Revision: https://phabricator.kde.org/D2270

M  +14   -14   applet/contents/ui/main.qml
M  +21   -0src/device.cpp
M  +21   -0src/device.h
M  +89   -1src/pulseaudio.cpp
M  +11   -0src/pulseaudio.h

http://commits.kde.org/plasma-pa/6c2f9f27543bdfef448c87601a9aa52d271f7927

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

[kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify when searching for transactions

[Rob V via KDE Bugzilla]

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

--- Comment #5 from Rob V  ---
Created attachment 100301
  --> https://bugs.kde.org/attachment.cgi?id=100301=edit
KMyMoney crash with Oxygen widgets

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

[kmymoney4] [Bug 366043] KMyMoney crashes along with KNotify when searching for transactions

[Rob V via KDE Bugzilla]

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

--- Comment #4 from Rob V  ---
Created attachment 100300
  --> https://bugs.kde.org/attachment.cgi?id=100300=edit
KNotify crash with Oxygen widgets

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

[plasmashell] [Bug 359580] High CPU usage

[via KDE Bugzilla]

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

--- Comment #8 from kdde@porcupinefactory.org ---
After upgrading Fedora to kf5-plasma.x86_64-5.23.0-1.fc23, the issue came back
worse. It takes an hour or two for Plasma to reach the whereabouts of 20% CPU
usage (this is total Plasma + X, so maybe display related) and stay there for
days (until killed).
There's nothing special in the logs that I could see.
The plasma-nm plugin is known to me as an offender when it comes to killing CPU
with unnecessary refreshes.

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

[kdenlive] [Bug 365965] git master - Position and Zoom effect isn't working properly (video example included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #3 from Jesse  ---
Some minor testing with new projects seems to confirm that this bug is fixed.
Thanks JB and Vincent!

Marking bug as resolved/fixed.

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

[plasmashell] [Bug 359580] High CPU usage

[via KDE Bugzilla]

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

--- Comment #7 from kdde@porcupinefactory.org ---
Created attachment 100299
  --> https://bugs.kde.org/attachment.cgi?id=100299=edit
plasmashell output

Several minutes of output from plasmashell when the usage increases for no
reason.

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

[kwin] [Bug 360978] Tooltips (task manager, system tray) are rendered incorrectly

[Martin Höher via KDE Bugzilla]

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

--- Comment #12 from Martin Höher  ---
Hey guys,

I just wanted to let you know that after running an update today to Plasma
5.7.1 (from Fedora packages) the described issue seems to be gone :-) So
whatever fixed it: Thank you a lot (also in general, so far I love the 5.7
release)!

Ciao
Martin

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

[kdenlive] [Bug 366105] git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kdenlive] [Bug 366105] git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jesse via KDE Bugzilla]

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

--- Comment #1 from Jesse  ---
Created attachment 100298
  --> https://bugs.kde.org/attachment.cgi?id=100298=edit
Backtrace data

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

[kdenlive] [Bug 366105] git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 366105] New: git master - crashed during use while trying to click on a clip in timeline (backtrace included)

[Jesse via KDE Bugzilla]

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

Bug ID: 366105
   Summary: git master - crashed during use while trying to click
on a clip in timeline (backtrace included)
   Product: kdenlive
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

Was working on a project, and while trying to click on a clip to edit its
effect properties, Kdenlive crashed. I'm attaching the backtrace log from the
crash.

Reproducible: Always




Bug discovered while using Kdenlive git master build via
ppa:kdenlive/kdenlive-master.

Linux Mint 18 (ubuntu base) x64.

KDE Frameworks 5.18.0

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

[kdenlive] [Bug 361360] git master (re-opened) - playback speed/framerate slows WAY down when using video clips in multiple tracks in timeline (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #45 from Jesse  ---
After some more testing, I decided it was easier to post a video with my recent
thoughts -- it'd be a lot to write out, and videos make it really easy to see
what's going on in the program. Terribly sorry, the mic volume was much lower
than I realized; I hope turning up the volume will allow you to hear it.

See video: https://youtu.be/JDxJhLbCjGc

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

[kdenlive] [Bug 366103] git master - consider improving behavior of how Project Bin handles Clip Properties widget (video included)

[Jesse via KDE Bugzilla]

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

--- Comment #1 from Jesse  ---
So sorry, I just noticed how soft the volume was on my mic. I hope if you turn
it up that you can hear it alright.

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

[kdenlive] [Bug 366103] git master - consider improving behavior of how Project Bin handles Clip Properties widget (video included)

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com
URL||https://youtu.be/Uu-Hd9kebK
   ||o

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

[ark] [Bug 363719] Sidebar can not be resized even when the details are too long

[Brendon Higgins via KDE Bugzilla]

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

Brendon Higgins  changed:

   What|Removed |Added

 CC||bren...@quantumfurball.net

--- Comment #4 from Brendon Higgins  ---
Please also apply this fix to the "Type" field, which can also get somewhat
long. For example, I'm currently experiencing "Type:
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet", which makes
the sidebar take half of my (960-pixel-wide) Ark window.

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

[digikam] [Bug 366104] New: digikam5 "hangs' @ 100%CPU at exit

[RJVB via KDE Bugzilla]

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

Bug ID: 366104
   Summary: digikam5 "hangs' @ 100%CPU at exit
   Product: digikam
   Version: 5.0.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: rjvber...@gmail.com

Application: digikam (5.0.0)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.5.7-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.4 LTS

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

- opened digiKam5
- connected an iPhone via USB
- used "import & delete selected"
- closed the import window
- checked the new photos in a fullscreen slideshow (manual advance)
- used Browse/Quit or the window close button to exit digiKam5
- `killall -ABRT digikam` after waiting a suitably long enough time and
checking CPU usage

Qt 5.6.1, frameworks 5.24.0 and digikam are installed in /opt/local .

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0d32090840 (LWP 9905))]

Thread 11 (Thread 0x7f0d0fea8700 (LWP 9906)):
#0  0x7f0d2d610fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f0d1fb99b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f0d1fb9b64f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f0d128f8b09 in QXcbEventReader::run (this=0x22061e0) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1325
#4  0x7f0d2ded6669 in QThreadPrivate::start (arg=0x22061e0) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/thread/qthread_unix.cpp:341
#5  0x7f0d2a168184 in start_thread (arg=0x7f0d0fea8700) at
pthread_create.c:312
#6  0x7f0d2d61e37d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 10 (Thread 0x7f0d0e708700 (LWP 9907)):
#0  0x7ffd711d7aab in ?? ()
#1  0x7f0d2d62c85d in __GI___clock_gettime (clock_id=,
tp=tp@entry=0x7f0d0e707b00) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f0d2df7db76 in qt_clock_gettime (ts=0x7f0d0e707b00, clock=) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/tools/qelapsedtimer_unix.cpp:156
#4  qt_gettime () at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/tools/qelapsedtimer_unix.cpp:165
#5  0x7f0d2e0ec929 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f0d2f20) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qtimerinfo_unix.cpp:84
#6  0x7f0d2e0ece55 in QTimerInfoList::timerWait (this=0x7f0d2f20,
tm=...) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qtimerinfo_unix.cpp:381
#7  0x7f0d2e0ee1ce in timerSourcePrepareHelper (timeout=0x7f0d0e707bb4,
src=) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:126
#8  timerSourcePrepare (source=,
timeout=timeout@entry=0x7f0d0e707bb4) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:159
#9  0x7f0d25c9f68d in g_main_context_prepare
(context=context@entry=0x7f0d0990, priority=priority@entry=0x7f0d0e707c38)
at /build/buildd/glib2.0-2.40.2/./glib/gmain.c:3352
#10 0x7f0d25c9ff03 in g_main_context_iterate
(context=context@entry=0x7f0d0990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3714
#11 0x7f0d25ca00ec in g_main_context_iteration (context=0x7f0d0990,
may_block=may_block@entry=1) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3795
#12 0x7f0d2e0eec6b in QEventDispatcherGlib::processEvents
(this=0x7f0d08c0, flags=...) at

[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template

[Ivan Čukić via KDE Bugzilla]

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

--- Comment #20 from Ivan Čukić  ---
> I used these ISOs for testing: 
> https://abf.rosalinux.ru/platforms/rosa2014.1/products/137/product_build_lists/15726


Is the live session supposed to crash or do I need to install it? (the live
session seems to work for me)

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

[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint

[karsten via KDE Bugzilla]

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

karsten  changed:

   What|Removed |Added

 CC||i...@dr-burger.com

--- Comment #8 from karsten  ---
I had the same behaviour using CentOS 7.2. When I selected "Classic" bluefish
instead of GPG it prompted me for a password and its confirmation, and this
worked to create a kde wallet.

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

[kdenlive] [Bug 366103] New: git master - consider improving behavior of how Project Bin handles Clip Properties widget (video included)

[Jesse via KDE Bugzilla]

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

Bug ID: 366103
   Summary: git master - consider improving behavior of how
Project Bin handles Clip Properties widget (video
included)
   Product: kdenlive
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

See video for details.

I know a lot has changed with the Clip Properties widget and its relationship
with the Project Bin. I've found its behavior to be incongruent with the rest
of the Kdenlive widgets, and wanted to propose a better, more user-friendly
approach.

Reproducible: Always




Suggested while using Kdenlive git master build via
ppa:kdenlive/kdenlive-master.

Linux Mint 18 (ubuntu base) x64.

KDE Frameworks 5.18.0

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[Steve via KDE Bugzilla]

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

--- Comment #6 from Steve  ---
Created attachment 100297
  --> https://bugs.kde.org/attachment.cgi?id=100297=edit
Min-Width-kdenlive-without-timeline.png

I have attached 2 images showing minimum width of kdenlive with and without the
timeline widget

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[Steve via KDE Bugzilla]

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

--- Comment #5 from Steve  ---
Created attachment 100296
  --> https://bugs.kde.org/attachment.cgi?id=100296=edit
Min-Width-kdenlive-with-timeline.png

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

[krita] [Bug 366102] New: Krita default file format now not .kra but openEXR format?

[Putra Arif Prasetyo via KDE Bugzilla]

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

Bug ID: 366102
   Summary: Krita default file format now not .kra but openEXR
format?
   Product: krita
   Version: 3.0.1 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: putraarifprase...@gmail.com

hi i just realize that krita behave strangely. when i make a new canvas > save
it (ctrl+s) > name the file > hit enter i got this http://prntscr.com/bxe5s6

maybe the problem is in here  http://prntscr.com/bxe5hw

but if i write the format within the name still working perfect. :3

thanks :3

Reproducible: Always

Steps to Reproduce:
1.new canvas
2.ctrl+s
3.enter

Actual Results:  
the result get openEXR format not .kra

Expected Results:  
test.kra

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[stiven guillaume via KDE Bugzilla]

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

--- Comment #4 from stiven guillaume  ---
I attached a screenshot. See the size, unresizeable of the window

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

[kdenlive] [Bug 366066] Timeline minimum width is too long on Dual-Monitors

[stiven guillaume via KDE Bugzilla]

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

--- Comment #3 from stiven guillaume  ---
Created attachment 100295
  --> https://bugs.kde.org/attachment.cgi?id=100295=edit
Bug dual screen

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

[valgrind] [Bug 364948] Add IBM ISA 3.0 support, patch set 5

[Carl Love via KDE Bugzilla]

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

--- Comment #5 from Carl Love  ---
> --- Comment #4 from Julian Seward  ---
> (In reply to Carl Love from comment #1)
> > Created attachment 99775 [details]
> > Patch 5 of 5 to add VEX support for Power ISA 3.0 instructions
> 
> I have a number of concerns here, but nothing that can't be relatively
> easily fixed.  They fall into 5 areas:
> 
> [1] naming and possible duplication of new IROps
> 
> [2] front end: duplication of IR trees (the IRExpr* vs IRTemp thing)
> 
> [3] front end: generation of excessively verbose IR for some vector insns
> 
> [4] misc other correctness comments/queries
> 
> [5] various typos in comments
> 
> 
> To go through them in order:
> 
> 
> -- [1] naming and possible duplication of new IROps --
> 
> diff --git a/VEX/pub/libvex_ir.h b/VEX/pub/libvex_ir.h
> +  Iop_MulAddF128,// (A * B) + C
> +  Iop_MulSubF128,// (A * B) - C
> +  Iop_NegMulAddF128, // -((A * B) + C)
> +  Iop_NegMulSubF128, // -((A * B) + C)
> Call these, respectively:  MAddF128, MSubF128, NegMAddF128,
> NegMSubF128, so as to be consistent with the 32/64 bit variants

Renamed the Iops as requested

> 
> 
> +  Iop_ConvI64UtoF128, /*  signed I64  -> F128 */
> +  Iop_ConvI64StoF128, /*  signed I64  -> F128 */
> +  Iop_ConvF64toF128,  /* F64  -> F128 */
> +  Iop_ConvF128toF64,  /* IRRoundingMode(I32) x F128 -> F64*/
> +  Iop_ConvF128toF32,  /* IRRoundingMode(I32) x F128 -> F32*/
> Remove the leading Conv (eg Iop_I64UtoF128), so as to make them
> consistent with other conversion operations.  
> 

Renamed the Iops as requested

> 
> +  /* Conversion signed 32-bit value to signed BCD 128-bit */
> +  Iop_I128StoBCD128,
> +
> +  /* Conversion signed BCD 128-bit to signed 32-bit value */
> +  Iop_BCD128toI128S,
> The comments don't seem to match the names.  Is the integer value
> 32 bits or 128 bits?
> 

fixed comments.  The integer source/result is stored in an I128 value.

> 
> +  /* -- Vector to/from half conversion -- */
> +  Iop_F16x4toF32x4, Iop_F32x4toF16x4, Iop_F64x2toF16x2, Iop_F16x2toF64x2,
> You only need one lane specifier here, so as to be consistent with
> other ops:
>   F16toF32x4, F32toF16x4, F64toF16x2, F16toF64x2
> and in fact the first two already seem to exist.  Are these different?
> 
> 

Renamed the Iops as requested, changed the code in guest_ppc_toIR.c was
then changed to match the Iop arg type with the required changes in
host_ppc_isel.c to handle setting up the src/dest registers for the
backend to issue the instructions.


>  [2] front end: duplication of IR trees (the IRExpr* vs IRTemp thing) 
> 
> +static void putC ( IRExpr* e )
> 
> +static IRExpr * create_FPCC( IRExpr *NaN,   IRExpr *inf,
> + IRExpr *zero,  IRExpr *norm,
> + IRExpr *dnorm, IRExpr *pos,
> + IRExpr *neg ) {
> 
> +static IRExpr * create_C( IRExpr *NaN,   IRExpr *zero,
> +  IRExpr *dnorm, IRExpr *pos,
> +  IRExpr *neg ) {
> 
> These functions all use their input trees more than once and so will
> duplicate them and the computations done by them.  Please change them so
> that the passed arguments are IRTemps instead.
> 
> There may be more such functions -- I am not sure if this is all of
> them.

Fixed, changed the IRExpr to IRTemps in these two functions.
exponent_compare() and fractional_part_compare() use IRExpr but the
value is used once in the true and once in the false path of an if
statement.  I suspect there may be existing functions with this issue.
It is something that needs to be addressed in a follow on cleanup patch.
I have noticed that the formatting of comments through out the code is
not consistent and would like to clean that up as well in a follow
patch.

> 
> 
>  [3] front end:
>  generation of excessively verbose IR for some vector insns 
> 
> +   case 28: // vctzb,  Vector Count Trailing Zeros Byte
> Too complex; use a vector IRop
> 
> +   case 29: // vctzh,  Vector Count Trailing Zeros Halfword
> Ditto
> 
> +   case 30: // vctzw,  Vector Count Trailing Zeros Word
> Ditto
> 
> +   case 31: // vctzd,  Vector Count Trailing Zeros Halfword
> Ditto
> 
> For the above cases (28/29/30/31), make yourself a set of vector IROps
> to do this:
>   Iop_Ctz{8x16, 16x8, 32x4}
> See existing ops Iop_Clz8x16, Iop_Clz16x8, Iop_Clz32x4 as an example

Created Iops  Iop_Ctz8x16, Iop_Ctz16x8, Iop_Ctz32x4, Iop_Ctz64x2 and
re-implemented the instructions using the new Iops rather then using the
existing Iops.


> 
> + case 0:  // bcdctsq.  (Decimal Convert to Signed Quadword VX-form)
> +   /* Check each of the nibbles for a valid digit 0 to 9 */
> +   inv_flag[0] = newTemp( Ity_I1 );
> +   assign( inv_flag[0], mkU1( 0 ) );
>