[digikam] [Bug 377849] albums disappear when the network is interrupted.

[bugzilla_noreply]

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

raphael.muell...@gmail.com changed:

   What|Removed |Added

 CC||raphael.muell...@gmail.com

--- Comment #12 from raphael.muell...@gmail.com ---
What is the current status about this?
I am having the same problem.

I launched digiKam yesterday afternoon at home and my network collection wasn't
there. It started the scan (which took the whole night) and in the morning the
collection looked good.
Then I put my notebook to standby, drove to work and now my collection is gone
again :(

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

[plasmashell] [Bug 393929] Plasmashell gobbles all my memory leak

[whoopsdecade]

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

--- Comment #8 from whoopsdecade  ---
In reply to Christoph Feck from comment #7)
> Is this massif output created with Qt 5.11?

Infocenter says Qt is 5.9.4. I'm on Fedora 27.

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

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Rob Walker]

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

Rob Walker  changed:

   What|Removed |Added

 CC||r...@ladle.net

--- Comment #42 from Rob Walker  ---
I tested this today (Inkscape wasn't honoring the changes in my KDE settings)
by modifying ~/.config/gtkrc-2.0

There are a few interesting lines:

# style "ToolTip"
# {
#   bg[NORMAL] = { 0.937, 0.941, 0.945 }
#   base[NORMAL] = { 0.988, 0.988, 0.988 }
#   text[NORMAL] = { 0.192, 0.212, 0.231 }
#   fg[NORMAL] = { 0.192, 0.212, 0.231 }
# }

widget "gtk-tooltip" style "ToolTip"
widget "gtk-tooltips" style "ToolTip"


If I comment out the first call to "gtk-tooltip", all is well.  If I comment
out the style, all is well.  I am moving forward with the solution I have
pasted here.

Thanks,
Rob

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

[kaffeine] [Bug 394306] not getting title in osd or epg

[Huntx011]

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

Huntx011  changed:

   What|Removed |Added

 CC||huntclx...@gmail.com

--- Comment #5 from Huntx011  ---
Created attachment 112962
  --> https://bugs.kde.org/attachment.cgi?id=112962=edit
configure television...

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

[krusader] [Bug 372023] ISO files listing/extracting broken

[Nikita Melnichenko]

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

Nikita Melnichenko  changed:

   What|Removed |Added

   Keywords||triaged

--- Comment #7 from Nikita Melnichenko  ---
Theo, thanks for providing the details, it will help with debugging. Indeed, I
completely missed that I needed to read file contents. I confirm on my end that
viewing files on the first try shows binary garbage.

I think we don't have people who know the code of kio_iso and ISO format very
well (original dev is retired long ago), so if you feel like you can help
figuring out the reason, you're more than welcome to do this. I can help you
with the debugging setup, etc.

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

[kstars] [Bug 393949] QHY driver crashing

[bugzilla_noreply]

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

--- Comment #14 from ni...@canamaero.ca ---
Created attachment 112960
  --> https://bugs.kde.org/attachment.cgi?id=112960=edit
Screen Shot 2018-05-29 at 11.36.54 PM.png

--- Comment #15 from ni...@canamaero.ca ---
Created attachment 112961
  --> https://bugs.kde.org/attachment.cgi?id=112961=edit
Screen Shot 2018-05-29 at 11.42.48 PM.png

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

[kstars] [Bug 393949] QHY driver crashing

[bugzilla_noreply]

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

--- Comment #13 from ni...@canamaero.ca ---
More info…

Nigels-MBP-2:~ Nigel$
/Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field -O
--no-plots --no-verify --resort --downsample 2 -3 10.9208 -4 41.365 -5 30
--config /Applications/kstars.app/Contents/MacOS/astrometry/bin/astrometry.cfg
-W /var/folders/w7/cwbv031967qgksh_6xqzf688gn/T/solution.wcs
/var/folders/w7/cwbv031967qgksh_6xqzf688gn/T/fitsaKdRPh
dyld: Library not loaded: @loader_path/../../../Frameworks/libcfitsio.5.dylib
  Referenced from:
/Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field
  Reason: image not found
Abort trap: 6

> Begin forwarded message:
> 
> From: Nigel Waterhouse Transport Canada DAR & EASA CVE 
> Subject: Re: [kstars] [Bug 393949] QHY driver crashing
> Date: May 29, 2018 at 11:43:32 PM GMT-4
> To: bug-cont...@kde.org
> Cc: Greg Beaton 
> 
> Hi Jasem,
> 
> I downloaded the new version and the QHY camera now works, but the plate 
> solver is failing.  Apparently in the setup, no plots and O are supposed to 
> be locked and check, in this case they are locked and unchecked.  Please see 
> attached and advise as soon as possible.
> 
> Many thanks, again.
> 
> Nigel.
> 
>> On May 26, 2018, at 3:55 AM, Jasem Mutlaq > > wrote:
>> 
>> https://bugs.kde.org/show_bug.cgi?id=393949 
>> 
>> 
>> Jasem Mutlaq  changed:
>> 
>>   What|Removed |Added
>> 
>> Status|CONFIRMED   |RESOLVED
>> Resolution|--- |FIXED
>> 
>> --- Comment #9 from Jasem Mutlaq  ---
>> Fixed in 2.9.6 release for MacOS.
>> 
>> -- 
>> You are receiving this mail because:
>> You reported the bug.

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

[kstars] [Bug 393949] QHY driver crashing

[bugzilla_noreply]

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

--- Comment #10 from ni...@canamaero.ca ---
Hi Jasem,

I downloaded the new version and the QHY camera now works, but the plate solver
is failing.  Apparently in the setup, no plots and O are supposed to be locked
and check, in this case they are locked and unchecked.  Please see attached and
advise as soon as possible.

Many thanks, again.

Nigel.

> On May 26, 2018, at 3:55 AM, Jasem Mutlaq  wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=393949
> 
> Jasem Mutlaq  changed:
> 
>   What|Removed |Added
> 
> Status|CONFIRMED   |RESOLVED
> Resolution|--- |FIXED
> 
> --- Comment #9 from Jasem Mutlaq  ---
> Fixed in 2.9.6 release for MacOS.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

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

[neon] [Bug 394846] New: kipi-plugins doesn't install due to broken dependencies

[Nate Graham]

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

Bug ID: 394846
   Summary: kipi-plugins doesn't install due to broken
dependencies
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [unstable]
  Assignee: neon-b...@kde.org
  Reporter: n...@kde.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

KDE Neon dev unstable. The pastebomb says it all:


sudo apt install kipi-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libkf5kipi-data [ amd64 ] < 18.04.1+p16.04+git20180509.1334-0
> ( libs )
Broken libkf5kipi-data:amd64 Breaks on libkipi-data [ amd64 ] < none ->
4:15.08.3-0ubuntu1 > ( universe/libs )
  Considering libkipi-data:amd64 -1 as a solution to libkf5kipi-data:amd64 4
  Added libkipi-data:amd64 to the remove list
  Fixing libkf5kipi-data:amd64 via keep of libkipi-data:amd64
Investigating (0) libkipi11 [ amd64 ] < none -> 4:15.08.3-0ubuntu1 > (
universe/libs )
Broken libkipi11:amd64 Depends on libkipi-data [ amd64 ] < none ->
4:15.08.3-0ubuntu1 > ( universe/libs ) (>= 4:15.08.3-0ubuntu1)
  Considering libkipi-data:amd64 -1 as a solution to libkipi11:amd64 0
  Holding Back libkipi11:amd64 rather than change libkipi-data:amd64
Investigating (1) kipi-plugins [ amd64 ] < none -> 4:4.12.0-0ubuntu7 > (
universe/kde )
Broken kipi-plugins:amd64 Depends on libkipi11 [ amd64 ] < none ->
4:15.08.3-0ubuntu1 > ( universe/libs ) (>= 4:4.9.80)
  Considering libkipi11:amd64 0 as a solution to kipi-plugins:amd64 
  Re-Instated libkipi-data:amd64
  Re-Instated libkipi11:amd64
Investigating (1) libkf5kipi-data [ amd64 ] < 18.04.1+p16.04+git20180509.1334-0
> ( libs )
Broken libkf5kipi-data:amd64 Breaks on libkipi-data [ amd64 ] < none ->
4:15.08.3-0ubuntu1 > ( universe/libs )
  Considering libkipi-data:amd64 -1 as a solution to libkf5kipi-data:amd64 4
  Added libkipi-data:amd64 to the remove list
  Fixing libkf5kipi-data:amd64 via keep of libkipi-data:amd64
Investigating (1) libkipi11 [ amd64 ] < none -> 4:15.08.3-0ubuntu1 > (
universe/libs )
Broken libkipi11:amd64 Depends on libkipi-data [ amd64 ] < none ->
4:15.08.3-0ubuntu1 > ( universe/libs ) (>= 4:15.08.3-0ubuntu1)
  Considering libkipi-data:amd64 -1 as a solution to libkipi11:amd64 0
  Holding Back libkipi11:amd64 rather than change libkipi-data:amd64
Investigating (2) kipi-plugins [ amd64 ] < none -> 4:4.12.0-0ubuntu7 > (
universe/kde )
Broken kipi-plugins:amd64 Depends on libkipi11 [ amd64 ] < none ->
4:15.08.3-0ubuntu1 > ( universe/libs ) (>= 4:4.9.80)
  Considering libkipi11:amd64 0 as a solution to kipi-plugins:amd64 
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kipi-plugins : Depends: libkipi11 (>= 4:4.9.80) but it is not going to be
installed
E: Unable to correct problems, you have held broken packages.

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

[kate] [Bug 394845] New: Syntax highlighting does not show bold and underline

[Shriramana Sharma]

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

Bug ID: 394845
   Summary: Syntax highlighting does not show bold and underline
   Product: kate
   Version: 17.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: samj...@gmail.com
  Target Milestone: ---

Created attachment 112955
  --> https://bugs.kde.org/attachment.cgi?id=112955=edit
screenshots demonstrating the bug

Starting from Kubuntu Bionic LTS, Katepart doesn't highlight keywords, control
words etc in bold or underline. Italic and strikeout work. I have attached
screenshots from Trusty, Xenial and Bionic LTS versions demonstrating this.

Further, if we select underline highlighting, even clicking on Apply clears the
underline checkbox. This doesn't happen with bold but the effect doesn't get
applied though it is shown in the preview in the settings.

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

[kdeconnect] [Bug 394818] Adverse battery usage on Android P

[Mal Haak]

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

--- Comment #3 from Mal Haak  ---
Since uninstall, with battery saver forced off battery drain has been <2%.
Before uninstall estimated battery time remaining was 15 mins

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

[kdeconnect] [Bug 394818] Adverse battery usage on Android P

[Mal Haak]

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

--- Comment #2 from Mal Haak  ---
Upgraded to Android P. Battery started lasting till 11am when removed from
charge at 8am.

Android P has a different battery stats page.

KDEConnect was listed as being active the whole 3 hour period. 

Uninstalled and battery life went back to full day on a single charge.

Reinstalled last night after your update to this ticket. Can confirm the
vibrations have stopped. It's 11:56 and my battery again is at 10%. 

Checked the battery stats and it's reporting KDEConnect as being active the
whole time.

Have uninstalled again. 

What logs or other details can I get for you to assist with debug?

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

[yakuake] [Bug 394844] New: Don't open window if pointer touches screen edge while mouse button held down

[Jonathan Liu]

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

Bug ID: 394844
   Summary: Don't open window if pointer touches screen edge while
mouse button held down
   Product: yakuake
   Version: 3.0.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: net...@gmail.com
  Target Milestone: ---

Yakuake can open unexpectedly when dragging a window to the top screen edge to
maximize it. It would be better if Yakuake could identify if any mouse buttons
were held down when the screen edge was touched and if so, not open Yakuake and
ignore any screen edge triggering until the mouse is moved away from the screen
edge.

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

[yakuake] [Bug 394843] New: Scroll down/up when mouse at top screen edge to open/retract Yakuake

[Jonathan Liu]

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

Bug ID: 394843
   Summary: Scroll down/up when mouse at top screen edge to
open/retract Yakuake
   Product: yakuake
   Version: 3.0.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: net...@gmail.com
  Target Milestone: ---

I think it would be neat to have the ability to scroll down/up while mouse is
at the top screen edge to open/retract Yakuake. This could be implemented by
showing a 1 pixel high window when the mouse touches the top screen edge which
would receive the mouse up/down events. If there is no mouse down event within
a certain period of time, it will timeout and automatically close the 1 pixel
high window.

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

[plasmashell] [Bug 394395] plasmashell crash on login after upgrade

[Craig]

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

--- Comment #6 from Craig  ---
Not looking good a dupe of a year old bug haha, what's odd is don't even use
kdepim at least yet, is there any workaround you're aware of so plasmashell
stops crashing constantly? Even the toolbar freezes when get plasmashell
running and don't relog to cause the crash and while buttons work it's frozen
so the clock being hours off keeps throwing me ha. I'll check the other reports
as well, thanks

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

[plasmashell] [Bug 393975] Calendar popup reports incorrect day (but, hover, date, and settings are correct)

[Kurt Marasco]

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

Kurt Marasco  changed:

   What|Removed |Added

 CC||kurtmara...@gmail.com

--- Comment #6 from Kurt Marasco  ---
Same issue for me also on on Arch Linux running:
plasma-desktop 5.12.5
qt5-base 5.11.0

I'm running KDE Neon User Edition on my laptop and do not have the issue.
Digital Clock version on Neon is: 4.5.12.5-0neon+16.04+xenial+build121

Still trying to locate the Digital Clock widget version on Arch, but have yet
to find it.

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

[frameworks-baloo] [Bug 392878] baloo crashes when reading corrupted data from the Terms db

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/bal
   ||oo/e1d1b7e87ff1e8ce6a7e03ec
   ||df2902322cb8624a
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Stefan Brüns  ---
Git commit e1d1b7e87ff1e8ce6a7e03ecdf2902322cb8624a by Stefan Brüns.
Committed on 29/05/2018 at 23:47.
Pushed by bruns into branch 'master'.

Avoid crash when reading corrupt data from document terms db

Summary:
The terms db contains terms, where each terms is stored independently
(terminated with 0), or as a suffix to the previous term (terminated with
1).
In case of corrupted data, the first terminator seen may be a 1, which
leads to a crash when trying to access the previous term with
QVector<>::last().
Show a debug message, to give a hint about the bad data, which can be
fixed by reindexing the relevant file.
Related: bug 392877

Test Plan:
Corrupt the database
Run balooshow -x 

Reviewers: #baloo, michaelh, ngraham, #frameworks, dhaumann

Reviewed By: dhaumann

Subscribers: dhaumann, kde-frameworks-devel, #frameworks

Tags: #frameworks, #baloo

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

M  +5-0src/codecs/doctermscodec.cpp
M  +5-1src/engine/documentdb.cpp

https://commits.kde.org/baloo/e1d1b7e87ff1e8ce6a7e03ecdf2902322cb8624a

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

[frameworks-baloo] [Bug 392877] balooctl index command with large number of files corrupts db

[Stefan Brüns]

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

--- Comment #2 from Stefan Brüns  ---
Git commit e1d1b7e87ff1e8ce6a7e03ecdf2902322cb8624a by Stefan Brüns.
Committed on 29/05/2018 at 23:47.
Pushed by bruns into branch 'master'.

Avoid crash when reading corrupt data from document terms db

Summary:
The terms db contains terms, where each terms is stored independently
(terminated with 0), or as a suffix to the previous term (terminated with
1).
In case of corrupted data, the first terminator seen may be a 1, which
leads to a crash when trying to access the previous term with
QVector<>::last().
Show a debug message, to give a hint about the bad data, which can be
fixed by reindexing the relevant file.
Related: bug 392878

Test Plan:
Corrupt the database
Run balooshow -x 

Reviewers: #baloo, michaelh, ngraham, #frameworks, dhaumann

Reviewed By: dhaumann

Subscribers: dhaumann, kde-frameworks-devel, #frameworks

Tags: #frameworks, #baloo

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

M  +5-0src/codecs/doctermscodec.cpp
M  +5-1src/engine/documentdb.cpp

https://commits.kde.org/baloo/e1d1b7e87ff1e8ce6a7e03ecdf2902322cb8624a

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

[plasmashell] [Bug 394395] plasmashell crash on login after upgrade

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #5 from David Edmundson  ---


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

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

[plasmashell] [Bug 385011] Crash in DaysModel::update

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||craig.finne...@gmail.com

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

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

[plasmashell] [Bug 385011] Crash in DaysModel::update

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
Summary|Plasma crashed  |Crash in DaysModel::update

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

[plasmashell] [Bug 394812] Wrong placement of animation when minimizing windows on HiDPI

[bugzilla_noreply]

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

--- Comment #7 from el...@seznam.cz ---
Removing PLASMA_USE_QT_SCALING 1 actually worked and animation was placed
correctly.

However System Tray icons were smaller than expected, so for now I'm keeping
PLASMA_USE_QT_SCALING 1.

Thanks anyway.

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

[krita] [Bug 394842] Animation timeline's "Remove Frames and Pull" works inconsistently when the frame after the currently selected frame is null/empty/hold.

[Emmet O'Neill]

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

Emmet O'Neill  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[krita] [Bug 394842] New: Animation timeline's "Remove Frames and Pull" works inconsistently when the frame after the currently selected frame is null/empty/hold.

[Emmet O'Neill]

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

Bug ID: 394842
   Summary: Animation timeline's "Remove Frames and Pull" works
inconsistently when the frame after the currently
selected frame is null/empty/hold.
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: emmetoneill@gmail.com
  Target Milestone: ---

Animation timeline's "Remove Frames and Pull" works inconsistently when the
frame after the currently selected frame is null/empty/hold.

This is a minor bug with the "Remove Frames and Pull" action from the Animation
Timeline's right-click context menu. 

This feature seems to work as expected when the frame *after* the selected
frame contains a keyframe (including blank keyframes) - the currently selected
frame is removed and all of the following frames are shifted back/left.

However, when the frame immediately *after* the selected frame is
null/empty/hold, there is a bug where the selected frame is not removed, even
though all subsequent frames are still shifted back. As such, the
last/rightmost frame in the timeline can never be removed with "Remove Frames
and Pull".

---

Here's how to test this:

You can test this by creating two adjacent frames. Draw an "A" on the first one
and a "B" on the second. If you select the first (A) and try "Remove Frames and
Pull" you'll see the expected behavior - the frame with the "A" will be deleted
and the frame with the "B" will shift back to take its place. However, if you
select the second frame (B) and try "Remove Frames and Pull" you'll see that
neither frame is deleted, although the subsequent frames will still be shifted
back.

---

This is probably a small error with indices or early-returning in either
KisTimeBasedItemModel::removeFramesAndOffset or
KisTimeBasedItemModel::createOffsetFramesCommand functions.

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

[plasmashell] [Bug 393975] Calendar popup reports incorrect day (but, hover, date, and settings are correct)

[Andrew Brouwers]

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

--- Comment #5 from Andrew Brouwers  ---
It's still an issue for me on 5.12.90 as well.  Could this be related to Qt
5.11?  I'm not sure how to provide more information for troubleshooting.  I
have the issue with a fresh KDE instance (new config) with the following:

[andrew@thinkpad]$ pacman -Q plasma-desktop qt5-base
plasma-desktop 5.12.90.1-1
qt5-base 5.11.0-1

[andrew@thinkpad]$ ls -l /etc/localtime 
lrwxrwxrwx 1 root root 37 May 19 22:16 /etc/localtime ->
../usr/share/zoneinfo/America/Detroit

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

[digikam] [Bug 393205] Advanced rename very slow

[Flaviu Tamas]

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

--- Comment #22 from Flaviu Tamas  ---
(In reply to caulier.gilles from comment #19)
> Comment on attachment 112936 [details]
> new flamegraph after the patch was applied
> 
> Which profiling tool did you use to capture cpu idle with digiKam ? 

I used perf, but I wouldn't trust the cpu idle info to be accurate.

For details on how to use perf, there's Brendan Gregg's excellent guide at
http://www.brendangregg.com/perf.html#OneLiners. The tool I used to generate
the flame graph can be found at
http://www.brendangregg.com/perf.html#FlameGraphs.

> Which modifications did you introduce in compilation workflow of digiKam to
> achieve this profiling ?

You must compile with debug information to get accurate stack traces, but
that's it.

> Gilles Caulier

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

[plasma-nm] [Bug 394580] Wrong icon size on network manager applet

[Jonathan]

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

--- Comment #9 from Jonathan  ---
(In reply to Jonathan from comment #6)
> (In reply to TYY331 from comment #5)
> > > thanks for response my ask.  Another question. This cache files will be
> > > regenerated after delete them?
> > 
> > Every cache file by definition is regenerated if not found, Qt isn't the
> > exception.
> 
> thanks... I will try

Not work :(:(:(

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

[Discover] [Bug 394841] New: Discover crashes due to retrying install of Flatpack that's already installed

[bugzilla_noreply]

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

Bug ID: 394841
   Summary: Discover crashes due to retrying install of Flatpack
that's already installed
   Product: Discover
   Version: 5.12.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: ljl...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.12.4)

Qt Version: 5.9.1
Frameworks Version: 5.44.0
Operating System: Linux 4.13.0-43-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
- What I was doing when the application crashed:
Discover has been telling me for weeks that I need to update the Gnome 3.26
flatpack, however it's already installed. For some reason, it won't go away in
Discover as an installable update. I clicked on the Update button multiple
times, which then crashed Discover.

What would be really nice here would be a way I can tell Discover to ignore
this Flatpack because it is already installed.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff94348d900 (LWP 29144))]

Thread 12 (Thread 0x7ff8f9ee5700 (LWP 24494)):
#0  0x7ff93ebc0951 in __GI___poll (fds=0x7ff8a40036e0, nfds=1,
timeout=94312) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff93949f169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff93949f27c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff93f50049b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff93f4a5e3a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff93f2c53ca in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff93f2ca29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff93b4297fc in start_thread (arg=0x7ff8f9ee5700) at
pthread_create.c:465
#8  0x7ff93ebccb5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7ff8d4da2700 (LWP 30259)):
#0  0x7ff93b430072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55776bc9a6b4) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55776bc9a660,
cond=0x55776bc9a688) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55776bc9a688, mutex=0x55776bc9a660) at
pthread_cond_wait.c:655
#3  0x7ff93f2cb6cb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff942711ae8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7ff942711f4a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7ff93f2ca29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff93b4297fc in start_thread (arg=0x7ff8d4da2700) at
pthread_create.c:465
#8  0x7ff93ebccb5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7ff8ebfff700 (LWP 30142)):
#0  0x7ff93ebbc06d in __GI___libc_read (fd=83, buf=0x7ff8ebffea90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7ff937a4f073 in ?? () from
/usr/lib/nvidia-390/tls/libnvidia-tls.so.390.59
#2  0x7ff9394e3280 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff93949ec4b in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff93949f110 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff93949f27c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7ff93f50049b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff93f4a5e3a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ff93f2c53ca in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7ff93f2ca29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7ff93b4297fc in start_thread (arg=0x7ff8ebfff700) at
pthread_create.c:465
#11 0x7ff93ebccb5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7ff8f8ee3700 (LWP 29720)):
#0  0x7ff93ebc0951 in __GI___poll (fds=0x7ff8e4516d50, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff93949f169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff93949f27c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff93f50049b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff93f4a5e3a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff93f2c53ca in QThread::exec() () 

[systemsettings] [Bug 394840] "Show detailed tooltips" option should disable normal tooltips.

[uRohan]

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

uRohan  changed:

   What|Removed |Added

 Attachment #112954|When the "Show detailed |When the "Show detailed
description|tooltip" option is enabled, |tooltips" option is
   |the normal tooltips are |enabled, the normal
   |still displayed.|tooltips are still
   ||displayed.

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

[systemsettings] [Bug 394840] "Show detailed tooltips" option should disable normal tooltips.

[uRohan]

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

uRohan  changed:

   What|Removed |Added

Summary|"Show detailed tooltip" |"Show detailed tooltips"
   |option should disable   |option should disable
   |normal tooltips.|normal tooltips.

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

[systemsettings] [Bug 394840] New: "Show detailed tooltip" option should disable normal tooltips.

[uRohan]

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

Bug ID: 394840
   Summary: "Show detailed tooltip" option should disable normal
tooltips.
   Product: systemsettings
   Version: 5.12.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: navigator.ro...@gmail.com
  Target Milestone: ---

Created attachment 112954
  --> https://bugs.kde.org/attachment.cgi?id=112954=edit
When the "Show detailed tooltip" option is enabled, the normal tooltips are
still displayed.

OS: openSUSE Tumbleweed 20180525
KDE Frameworks Version: 5.46.0
Qt Version: 5.10.0
Kernel Version: 4.16.7-1-default
OS Type: 64-bit

"Show detailed tooltip" option should disable normal tooltips (Configure-System
Settings-Show detailed tooltips).

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

[frameworks-syntax-highlighting] [Bug 379005] Kate highlights the word END inside Bash comments

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
This already improved: Only if END is a word with word boundaries, it is
highlighted.

In fact, this is a feature by design, called region markers that define code
folding regions:

# BEGIN asdf
...
# END

Here, BEGIN will start a code folding region that is ended with END. This is
similar to other conventions such as {{{ ... }}}. So this is not a classical
bug, but rather intended.

Therefore, I'll close for now as NOT-A-BUG.

The Kate developers certainly can discuss whether this feature is really
valuable - and if not, we can also remove it. But it's not possible to only
disable it for Bash, and even if we did, it would not help much, since this is
an issue with all highlighting files. The respective rules are in Alert.xml.

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

[frameworks-syntax-highlighting] [Bug 386827] Errors in syntax definitions

[Dominik Haumann]

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

--- Comment #10 from Dominik Haumann  ---
@Gene Thomas: Friendly ping again.

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

[frameworks-syntax-highlighting] [Bug 393129] Red underline in kdevelop+kwrite on valid numerical constants (with invalid octal substrings)

[Dominik Haumann]

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

--- Comment #4 from Dominik Haumann  ---
What also does not work:
const float min = -0.5f;

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

[ktorrent] [Bug 363852] Ktorrent no longer starts hidden in tray

[Janek]

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

Janek <2...@web.de> changed:

   What|Removed |Added

 CC||2...@web.de

--- Comment #3 from Janek <2...@web.de> ---
This is still happening! It bugs me that a KTorrent window opens every single
time upon startup. I might stop it from autostarting due to that, which means
I'd stop seeding. I don'T want to do that, but why is such a seemingly simple
issue still not fixed?

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

[frameworks-syntax-highlighting] [Bug 393129] Red underline in kdevelop+kwrite on valid numerical constants (with invalid octal substrings)

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||silverunicorn2...@yandex.ru

--- Comment #3 from Dominik Haumann  ---
*** Bug 388091 has been marked as a duplicate of this bug. ***

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

[frameworks-syntax-highlighting] [Bug 388091] Negative float literals (e.g. -0.5f) are marked as incorrect in C++ mode

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #2 from Dominik Haumann  ---
Yes, indeed a bug.

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

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

[Akonadi] [Bug 394839] New: pimitemtable.remoteid Column Too Small For Exchange Calendar Via davmail

[Garry Williams]

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

Bug ID: 394839
   Summary: pimitemtable.remoteid Column Too Small For Exchange
Calendar Via davmail
   Product: Akonadi
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

I was unable to configure an Exchange calendar via the davmail proxy because
the item ID was longer than the column length for the pimitemtable.remoteid
column (255).

The error resulted in log messages like this:

DATABASE ERROR:
  Error code: "1406"
  DB error:  "Data too long for column 'remoteId' at row 1"
  Error text: "Data too long for column 'remoteId' at row 1 QMYSQL3: Unable
to execute statement"
  Query: "INSERT INTO PimItemTable (rev, remoteId, remoteRevision, gid,
collectionId, mimeTypeId, datetime, atime, dirty, size) VALUES (:0, :1, :2, :3,
:4, :5, :6, :7, :8, :9)"

I turned on general_log in mysql to catch the error.

The fix was:

alter table pimitemtable modify column remoteId varchar(1024);

(I imagine that 1024 is larger than what is strictly needed, but it costs
nothing to specify it.)

The problem data looks like this:

   
http://localhost:1080/users/garry_willia...@comcast.com/calendar/AAMkADE0ZTY4YjY0LTM3ZmUtNGQ3Yy1hMzdjLTdlNTZlYjgzMTNkZgBGAABv2lgKJBYZRoOfK2MzkdgNBwCAS5PvJdbcTKxWQLEnWOAHAAENAACAS5PvJdbcTKxWQLEnWOAHAAAaQl7dAAA%3D.EML#04008200E00074C5B7101A82E008A059FC7E8054D201100067BF664FED94F14D8772488D96A9E4E92017-01-17T19:30:00+00:00

My pimitemtable now has this:

MariaDB [akonadi]> select length(remoteid) from pimitemtable where
length(remoteid) > 255;
+--+
| length(remoteid) |
+--+
|  361 |
|  361 |
|  361 |
|  361 |
|  361 |
|  361 |
|  361 |
|  363 |
|  363 |
+--+
9 rows in set (0.01 sec)

MariaDB [akonadi]>

And the calendar is finally working.

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

[frameworks-syntax-highlighting] [Bug 392468] No Perl 6 syntax highlighting

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.47
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/syn
   ||tax-highlighting/cd9068f802
   ||bc3e5e5211ad1c0c765afc76598
   ||6fe

--- Comment #1 from Dominik Haumann  ---
Git commit cd9068f802bc3e5e5211ad1c0c765afc765986fe by Dominik Haumann.
Committed on 29/05/2018 at 20:59.
Pushed by dhaumann into branch 'master'.

Perl6: Add support for extensions .pl6, .p6, or .pm6
FIXED-IN: 5.47

M  +1-1data/syntax/perl.xml

https://commits.kde.org/syntax-highlighting/cd9068f802bc3e5e5211ad1c0c765afc765986fe

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

[lokalize] [Bug 343371] Whole project is refreshed when file in project is changed

[Adrián Chaves]

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

Adrián Chaves (Gallaecio)  changed:

   What|Removed |Added

 CC||adr...@chaves.io

--- Comment #3 from Adrián Chaves (Gallaecio)  ---
This issue seems to have been introduced by the fix for
https://bugs.kde.org/show_bug.cgi?id=342959

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

[frameworks-syntax-highlighting] [Bug 393129] Red underline in kdevelop+kwrite on valid numerical constants (with invalid octal substrings)

[Dominik Haumann]

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

--- Comment #2 from Dominik Haumann  ---
Git commit db2cbfd50c22da2e0dd633b6ae8f9dfd7babee11 by Dominik Haumann.
Committed on 29/05/2018 at 20:56.
Pushed by dhaumann into branch 'master'.

Add unit test for C++ Octal number misdetection

M  +2-0autotests/folding/highlight.cpp.fold
M  +3-1autotests/html/highlight.cpp.html
M  +2-0autotests/input/highlight.cpp
M  +3-1autotests/reference/highlight.cpp.ref

https://commits.kde.org/syntax-highlighting/db2cbfd50c22da2e0dd633b6ae8f9dfd7babee11

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

[frameworks-syntax-highlighting] [Bug 393129] Red underline in kdevelop+kwrite on valid numerical constants (with invalid octal substrings)

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Dominik Haumann  ---
Indeed. The problem is that it seems the Octal rule matches due to the leading
0, and 9 is not part of the Octal system. Usually, the  rule should
match earlier, but this does not seem to work properly. Needs further
investigation.

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

[plasmashell] [Bug 393912] The Activities switcher steal the focus after I switch using meta+tab and after that it does not autohide

[Thomas Surrel]

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

--- Comment #11 from Thomas Surrel  ---
Created attachment 112953
  --> https://bugs.kde.org/attachment.cgi?id=112953=edit
Desktop.qml

I have eattached the full file, if it can help others while the fix makes its
way into an official release.

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

[frameworks-syntax-highlighting] [Bug 394184] DoxygenLua syntax highlighting for block comments is broken

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

   Version Fixed In||5.47

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

[frameworks-syntax-highlighting] [Bug 394184] DoxygenLua syntax highlighting for block comments is broken

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/syn
   ||tax-highlighting/b136c9fd1c
   ||4901d9716148e6299a45955a60c
   ||506

--- Comment #2 from Dominik Haumann  ---
Git commit b136c9fd1c4901d9716148e6299a45955a60c506 by Dominik Haumann.
Committed on 29/05/2018 at 20:38.
Pushed by dhaumann into branch 'master'.

DoxygenLua: fix closing comment blocks

Summary:
Kate-editor needs the context to be marked dynamic to use a placeholder in a
dynamic rule.

Test Plan:
Open Kate with the code lua below:

```
--[[
commented out
]]
local test
```

An equivalent is already in autotests/input/highlight.lua

Reviewers: #framework_syntax_highlighting, dhaumann

Reviewed By: #framework_syntax_highlighting, dhaumann

Subscribers: kde-frameworks-devel

Tags: #frameworks

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

M  +9-9data/syntax/doxygenlua.xml

https://commits.kde.org/syntax-highlighting/b136c9fd1c4901d9716148e6299a45955a60c506

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

[frameworks-syntax-highlighting] [Bug 394184] DoxygenLua syntax highlighting for block comments is broken

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

URL||https://phabricator.kde.org
   ||/D12860
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Dominik Haumann  ---
Proposed patch: https://phabricator.kde.org/D12860

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

[Falkon] [Bug 394813] [Feature request] scrollbars inherit color scheme

[Juraj]

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

Juraj  changed:

   What|Removed |Added

 CC||sgd.or...@gmail.com

--- Comment #1 from Juraj  ---
Described scrollbars are same as in chromium and can be changed with proper
CSS.

Or you can use native scrollbars (Preferences > Browsing > Use native
scrollbars)
but when these are enabled you can see some bugs...

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

[plasmashell] [Bug 394837] KDE menu (start button) refuses to show any menu

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |plasmashell
 CC||plasma-b...@kde.org
  Component|general |Application Launcher
   ||(Kickoff)
Version|unspecified |5.12.5
   Assignee|unassigned-b...@kde.org |k...@davidedmundson.co.uk
   Target Milestone|--- |1.0

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

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

[Paul Floyd]

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

--- Comment #19 from Paul Floyd  ---
I think that -fsized-deallocation would be better as it’s more specific.

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

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

[Philippe Waroquiers]

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

--- Comment #18 from Philippe Waroquiers  ---
(In reply to Paul Floyd from comment #17)
> Great. I also have a small test case for this, but it uses a Makefile rather
> than the Valgrind perl mechanism. I'll look into adapting it to the Valgrind
> infrastructure.

That would be nice.
You might maybe have to check if gcc accepts the -std=c++14 flag
(not too sure what past gcc we want to support)

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

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

[Paul Floyd]

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

--- Comment #17 from Paul Floyd  ---
Great. I also have a small test case for this, but it uses a Makefile rather
than the Valgrind perl mechanism. I'll look into adapting it to the Valgrind
infrastructure.

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

[kde] [Bug 394837] KDE menu (start button) refuses to show any menu

[John Andersen]

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

John Andersen  changed:

   What|Removed |Added

URL||https://forum.manjaro.org/t
   ||/kde-menu-wont-pop-up/48138
   ||/12

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

[kontact] [Bug 394838] New: kontact crash on exit

[bugzilla_noreply]

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

Bug ID: 394838
   Summary: kontact crash on exit
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: p...@bandavelo.org
  Target Milestone: ---

Application: kontact (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-22-generic x86_64
Distribution: Ubuntu 18.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I had just quit the application, I did nothing special before I quit

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4c0a1a2080 (LWP 9278))]

Thread 30 (Thread 0x7f4a8cf3f700 (LWP 12037)):
#0  0x7f4c0641bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4a8cf3e7e0, expected=0, futex_word=0x7f4bb8004530) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f4c0641bed9 in __pthread_cond_wait_common (abstime=0x7f4a8cf3e880,
mutex=0x7f4bb80044e0, cond=0x7f4bb8004508) at pthread_cond_wait.c:533
#2  0x7f4c0641bed9 in __pthread_cond_timedwait (cond=0x7f4bb8004508,
mutex=0x7f4bb80044e0, abstime=0x7f4a8cf3e880) at pthread_cond_wait.c:667
#3  0x7f4bf76f8652 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f4bf76ce799 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f4bf76cecfb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f4bf76c75eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f4c064156db in start_thread (arg=0x7f4a8cf3f700) at
pthread_create.c:463
#8  0x7f4c0695288f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7f4bbe7fc700 (LWP 12036)):
#0  0x7f4c0641bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f4bbe7fb7e0, expected=0, futex_word=0x7f4bb8004530) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f4c0641bed9 in __pthread_cond_wait_common (abstime=0x7f4bbe7fb880,
mutex=0x7f4bb80044e0, cond=0x7f4bb8004508) at pthread_cond_wait.c:533
#2  0x7f4c0641bed9 in __pthread_cond_timedwait (cond=0x7f4bb8004508,
mutex=0x7f4bb80044e0, abstime=0x7f4bbe7fb880) at pthread_cond_wait.c:667
#3  0x7f4bf76f8652 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f4bf76ce799 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f4bf76cecfb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f4bf76c75eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f4c064156db in start_thread (arg=0x7f4bbe7fc700) at
pthread_create.c:463
#8  0x7f4c0695288f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7f4bbeffd700 (LWP 11576)):
#0  0x7f4c074ab67e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f4c0064f998 in g_main_context_prepare () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4c0065036b in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4c0065054c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f4c074ab90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4c074509ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4c0726f22a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f4c0727416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f4c064156db in start_thread (arg=0x7f4bbeffd700) at
pthread_create.c:463
#9  0x7f4c0695288f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f4aa93b8700 (LWP 11334)):
#0  0x7f4c06945bf9 in __GI___poll (fds=0x7f4aa0004be0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f4c00650439 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4c0065054c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4c074ab90b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f4c074509ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4c0726f22a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4c0727416d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f4c064156db in start_thread (arg=0x7f4aa93b8700) at
pthread_create.c:463
#8  0x7f4c0695288f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f4ab0bad700 (LWP 9358)):
#0  0x7f4c06945bf9 in 

[systemsettings] [Bug 394835] System Settings Default Web Browser reverts to Firefox

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[kde] [Bug 394837] New: KDE menu (start button) refuses to show any menu

[John Andersen]

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

Bug ID: 394837
   Summary: KDE menu (start button) refuses to show any menu
   Product: kde
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jsam...@gmail.com
  Target Milestone: ---

The KDE "start button", (K Button) usually found at the Left of the Panel, can
cease to function (will not pop up the menu) if you: 
1) accidentally drag some arbitrary distance while clicking the menu button, or 
2) switch desktops with the menu open.

Occurs with the menu alternatives: Application Menu, Application Launcher 

How to reproduce: (easiest way)
Select either App-menu or App-launcher menu alternative.
Click K button (start button) menu appears
Switch desktop via pager (while menu still showing)
Click K button again, and menu will no longer show, but K button becomes
underlined briefly

How to restore Menu functionality:
Any of these methods will restore Menu functionality to the K button
1) Right click the K-button and choose a different Menu Alternative.
2) killall plasmashell && plasmashell  (in krunner or a shell)
3) Logout.

Found using Manjaro Stable packages
KDE Plasma Version 5.12.5
KDE Frameworks Version 5.46.0
QT Version 5.10.1
Kernel 4.14.44-1 (Manjaro) x86-64.

Can not reproduce with OpenSuse Leap 15
KDE Plasma Version 5.12.5
KDE Frameworks Version 5.45.0  <--<<< ?
QT Version 5.9.4
Kernel 4.12.14-4 (Opensus Leap 15) x86-64.

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

[plasmashell] [Bug 393975] Calendar popup reports incorrect day (but, hover, date, and settings are correct)

[NewmanIsaac]

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

NewmanIsaac  changed:

   What|Removed |Added

 CC||newmanisaa...@gmail.com

--- Comment #4 from NewmanIsaac  ---
I have the same problem. The date seems to be correct everywhere except the
digital/analog clock popup. My calendar weekday starts on Sunday and I couldn't
find a place to change it.

If I change the date to June 1st, the popup calendar switches to June, but the
highlighted day is still incorrect (May 31).

I have only noticed this after the recent qt5 and frameworks packages updates
(2018-05-25).

plasma: 5.12.5
frameworks: 5.46.0
qt: 5.11.0
system: 4.16.11-1-ARCH x86_64

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

[valgrind] [Bug 394731] allow building if arch=amd64 instead of x86-64

[Philippe Waroquiers]

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

--- Comment #2 from Philippe Waroquiers  ---
(when testing on a amd64 cpu machine, it does not need this patch)

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

[valgrind] [Bug 394731] allow building if arch=amd64 instead of x86-64

[Philippe Waroquiers]

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

Philippe Waroquiers  changed:

   What|Removed |Added

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

--- Comment #1 from Philippe Waroquiers  ---
Which platforms are reporting amd64 ?

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

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

[Philippe Waroquiers]

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

Philippe Waroquiers  changed:

   What|Removed |Added

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

--- Comment #16 from Philippe Waroquiers  ---
Fixed in 6ef6f738a

Thanks for the patch

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

[plasma-browser-integration] [Bug 394673] icon in system tray offers plasma-browser-integration even if it's already installed and working

[Dr . Chapatin]

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

--- Comment #4 from Dr. Chapatin  ---
Every time I open Firefox notification/icon of plasma borwser integration
appears in system tray. The icon remains visible in system tray even after I
close Firefox.

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

[k3b] [Bug 394836] K3B unable to handle the following files due to an unsupported format

[Viktor]

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

Viktor  changed:

   What|Removed |Added

Summary|UnK3B able to handle the|K3B unable to handle the
   |following files due to an   |following files due to an
   |unsupported format  |unsupported format

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

[k3b] [Bug 394836] UnK3B able to handle the following files due to an unsupported format

[Viktor]

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

Viktor  changed:

   What|Removed |Added

 CC||viktor.mastori...@gmail.com

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

[k3b] [Bug 394836] New: UnK3B able to handle the following files due to an unsupported format

[Viktor]

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

Bug ID: 394836
   Summary: UnK3B able to handle the following files due to an
unsupported format
   Product: k3b
   Version: 2.0.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Audio Project
  Assignee: k...@kde.org
  Reporter: viktor.mastori...@gmail.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

Created attachment 112952
  --> https://bugs.kde.org/attachment.cgi?id=112952=edit
A wav file downloaded from landr.com and not accepted by k3b

When creating an audio project, I try to import wav files (16b, 44.1khz) and
get the error as in the title. Further I get this: 
"You may manually convert these audio files to wave using another application
supporting the audio format and then add the wave files to the K3b project.
~/Downloads/LANDR-Fisarmonika[add.silence]orig.wav"

These wav files are downloaded from landr.com, an online mastering service. 

I contacted the LandR customer service and they told me that "...This suggests
that your CD burning software does not like the metadata attached to LANDR
masters downloaded from the cloud. Masters downloaded from the cloud include
metadata related to it's origin server location."

On K3B, I can burn mp3 files downloaded from the same website, I can burn wav
files from any other source.

I can also burn these downloaded wav files files with Brasero disk burning
software. 

I attach a sample wav file downloaded from landr.com

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

[plasma-nm] [Bug 392549] Use WIFI password entered in one user's session for another user's session

[Gregor Mi]

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

--- Comment #2 from Gregor Mi  ---
Thanks for the hint, I'll try that.

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

[i18n] [Bug 392899] Items duplicados na barra de status do ksysguard

[Luiz Fernando Ranghetti]

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

Luiz Fernando Ranghetti  changed:

   What|Removed |Added

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

--- Comment #7 from Luiz Fernando Ranghetti  ---
Olá,

Traduzi as strings novamente após a correção do problema no código.

https://websvn.kde.org/trunk/l10n-kf5/pt_BR/messages/kde-workspace/ksysguard.po?r1=1515895=1516683

Disponível nas próximas versões do KDE

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

[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet

[Krzysztof Nowicki]

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

Krzysztof Nowicki  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://commits.kde.org/kde
   ||pim-runtime/b5ee6ff11cd3a7e
   ||0c28305b351d28c5f244f101e
 Resolution|--- |FIXED

--- Comment #5 from Krzysztof Nowicki  ---
Git commit b5ee6ff11cd3a7e0c28305b351d28c5f244f101e by Krzysztof Nowicki.
Committed on 29/05/2018 at 10:02.
Pushed by nowicki into branch 'Applications/18.04'.

resources/ews: Fix saving passwords to KWallet

This is a regression after switching to asynchronous wallet
opening. When saving the password the wallet is opened and a callback is
registered to write the password once the wallet is ready. Unfortunately
all this is done in an instance of the EwsSettings class that is local
to the configuration dialog class. This means that this instance is
destroyed once the configuration dialog is dismissed, so when opening
the wallet takes a split second too long the object dies before the
callback has a chance to do its job.

The fix is not to use a local instance of the EwsSettings class in the
configuration dialog and instead work on a pointer to this object kept
by the root resource class, which is alive at all times.

M  +3-2resources/ews/ewsconfigdialog.cpp
M  +4-2resources/ews/ewsconfigdialog.h
M  +1-1resources/ews/ewsresource.cpp

https://commits.kde.org/kdepim-runtime/b5ee6ff11cd3a7e0c28305b351d28c5f244f101e

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

[systemsettings] [Bug 394835] New: System Settings Default Web Browser reverts to Firefox

[bugzilla_noreply]

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

Bug ID: 394835
   Summary: System Settings Default Web Browser reverts to Firefox
   Product: systemsettings
   Version: 5.12.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: devin.inspire...@gmail.com
  Target Milestone: ---

Attempting to set the default web browser from the settings in Chrome or
Chromium does nothing.

Selecting Google Chrome as the default web browser in System Settings also does
not set the default browser properly.  Links from outside Chrome continue to
open in Firefox.  

Running '$ sudo update-alternatives --config x-www-browser' and selecting
Chrome corrected this.

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

[plasmashell] [Bug 394830] Can't Pin WINE applications to Icon-Only Task Manager or Latte Dock

[Matt Eaves]

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

--- Comment #2 from Matt Eaves  ---
(In reply to Eike Hein from comment #1)
> Support for Wine's quirks was recently overhauled (last week, in fact). The
> improved code will be in the next 5.12.x release as well as 5.13. Please try
> those and reopen if the problem persists (please pin anew).

Upgraded to the Developer (Stable) branch of Neon and the problem is resolved,
didn't even need to unpin/re-pin. Thank you!

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

[korganizer] [Bug 394416] by default displayed day is monday instead ot the current day

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kor
   ||ganizer/7a2df1e6ed39cc5a752
   ||898bd1b90099418a0ce58
   Version Fixed In||5.8.2
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Allen Winter  ---
Git commit 7a2df1e6ed39cc5a752898bd1b90099418a0ce58 by Allen Winter.
Committed on 29/05/2018 at 17:35.
Pushed by winterz into branch 'Applications/18.04'.

koviewmanager.cpp - use the fallback when selecting the date for Day View
FIXED-IN: 5.8.2

M  +1-1src/koviewmanager.cpp

https://commits.kde.org/korganizer/7a2df1e6ed39cc5a752898bd1b90099418a0ce58

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

[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia

[Antonio Orefice]

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

--- Comment #39 from Antonio Orefice  ---
I just tried on another system (gtx 1060 + driver from nvidia) and it does not
crash, however screen corruption persists.
I'm running Arch Linux

qt5-base 5.11.0-1
plasma-framework 5.46.0-2

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

[plasmashell] [Bug 394830] Can't Pin WINE applications to Icon-Only Task Manager or Latte Dock

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Hein  ---
Support for Wine's quirks was recently overhauled (last week, in fact). The
improved code will be in the next 5.12.x release as well as 5.13. Please try
those and reopen if the problem persists (please pin anew).

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

[skrooge] [Bug 390202] problème commande boobank

[Stephane MANKOWSKI]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INVALID

--- Comment #12 from Stephane MANKOWSKI  ---
C'est le problème.
Boobank ne doit pas retourner d'erreur pour que Skrooge puisse correctement
importer les données.

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

[plasmashell] [Bug 393912] The Activities switcher steal the focus after I switch using meta+tab and after that it does not autohide

[bugzilla_noreply]

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

--- Comment #10 from mathoj...@gmail.com ---
Nice work, but I'm not developer. How do I use the attached file with my
Desktop.qml  ??

A copy/paste ? where?

Sorry

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

[plasmashell] [Bug 394812] Wrong placement of animation when minimizing windows on HiDPI

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

--- Comment #6 from Nate Graham  ---
Perhaps we should keep this bug open to track fixing the issue so we can
eventually use Qt scaling?

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

[digikam] [Bug 382474] Thumbnail regeneration

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dig
   ||ikam/35e125ac8445e9e77db75e
   ||85aa0d4e53ab7a0e36
 Resolution|--- |FIXED
   Version Fixed In||6.0.0
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Maik Qualmann  ---
Git commit 35e125ac8445e9e77db75e85aa0d4e53ab7a0e36 by Maik Qualmann.
Committed on 29/05/2018 at 16:45.
Pushed by mqualmann into branch 'master'.

fix rename by overwrite
Related: bug 393205
FIXED-IN: 6.0.0

M  +3-1NEWS
M  +1-0core/libs/album/albummanager.cpp
M  +3-3core/libs/database/coredb/coredb.cpp
M  +1-1core/libs/database/coredb/coredb.h
M  +1-1core/libs/database/item/imageinfo.cpp
M  +1-0core/libs/database/models/imagelistmodel.cpp
M  +11   -1core/libs/database/utils/dio.cpp
M  +1-0core/libs/models/imagealbummodel.cpp
M  +1-0core/utilities/queuemanager/views/queuelist.cpp

https://commits.kde.org/digikam/35e125ac8445e9e77db75e85aa0d4e53ab7a0e36

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

[digikam] [Bug 393205] Advanced rename very slow

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dig
   ||ikam/35e125ac8445e9e77db75e
   ||85aa0d4e53ab7a0e36
 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||6.0.0

--- Comment #21 from Maik Qualmann  ---
Git commit 35e125ac8445e9e77db75e85aa0d4e53ab7a0e36 by Maik Qualmann.
Committed on 29/05/2018 at 16:45.
Pushed by mqualmann into branch 'master'.

fix rename by overwrite
Related: bug 382474
FIXED-IN: 6.0.0

M  +3-1NEWS
M  +1-0core/libs/album/albummanager.cpp
M  +3-3core/libs/database/coredb/coredb.cpp
M  +1-1core/libs/database/coredb/coredb.h
M  +1-1core/libs/database/item/imageinfo.cpp
M  +1-0core/libs/database/models/imagelistmodel.cpp
M  +11   -1core/libs/database/utils/dio.cpp
M  +1-0core/libs/models/imagealbummodel.cpp
M  +1-0core/utilities/queuemanager/views/queuelist.cpp

https://commits.kde.org/digikam/35e125ac8445e9e77db75e85aa0d4e53ab7a0e36

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

[skrooge] [Bug 390202] problème commande boobank

[bugzilla_noreply]

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

--- Comment #11 from chos...@laposte.net ---
Lorsque j'exécute directement la commande:
a="" && b="2000-01-01" && m=$( [[ ${a} > ${b} ]] && echo "$a" || echo "$b" ) &&
PYTHONIOENCODING=utf_8 boobank -q -f csv history "CC-4000XXX@ing" -s
rdate,type,raw,label,amount --condition "rdate>$m OR date>$m OR rdate>$m
00:00:00 OR date>$m 00:00:00" -n 9

j'obtiens la liste des opérations du compte jusqu'au 4 septembre 2017 puis ça
se termine par:
Bug(ing): HTTPSConnectionPool(host='secure.ingdirect.fr', port=443): Max
retries exceeded with url: /protected/pages/index.jsf (Caused by
ProtocolError('Connection aborted.', error(104, 'Connection reset by peer')))
(If --auto-update is passed on the command-line, new versions of the module
will be checked automatically)
Use --debug option to print backtraces

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

[okular] [Bug 394834] New: Okular not release memory (ram) taken by closed documents

[CnZhx]

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

Bug ID: 394834
   Summary: Okular not release memory (ram) taken by closed
documents
   Product: okular
   Version: 1.4.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: z...@cnzhx.net
  Target Milestone: ---

Hi there, I report this but I am not really sure about this problem. I used
Okular a lot for paper reading. The settings are almost the same as default,
especially the Performance is set to Normal.

I used to open a lot of papers at the same time and switching between them.
Okular responses quickly. After a while, Okular takes around 5 to 6 GB of ram,
which is not a problem for me as long as the memory is not exhausted. After I
close some PDFs and open some others, the taken RAM keeps increasing but seems
never being released after closure of some documents. That is fine, I think.
However, when there is little memory left for my system to use, like only 0.5
GB left, and I need to open another programme, that causes problem and the
system starts to use swap space. Okular still does not release the memory it
takes. I think this situation need improvement so that Okular could somewhat
release some memory space when some documents have been closed for a long time.

Thank you.

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

[dolphin] [Bug 384080] Dolphin crashes after switching GPU's

[Julian Schraner]

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

Julian Schraner  changed:

   What|Removed |Added

 CC||juliquad...@gmail.com
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Julian Schraner  ---
Does this crash still happen with an updated system? I am relatively clueless
when it comes to driver problems/interactions, so @Elvis can probably guide you
further than I could.

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

[plasmashell] [Bug 394395] plasmashell crash on login after upgrade

[Craig]

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

--- Comment #4 from Craig  ---
Sorry took me a bit there had a busy weekend - rebuilt plasma-framework without
stripping and with build mode debug then reproduced, see below and let me know
if need anything else

Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe95fa64800 (LWP 6555))]

Thread 22 (Thread 0x7fe831bdb700 (LWP 6753)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe95d4905fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe95d490a84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe95968babd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe95883e075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe958f8f53f in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7fe832735700 (LWP 6752)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe95d4905fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe95d490a84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe95968babd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe95883e075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe958f8f53f in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7fe83328f700 (LWP 6751)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe95d4905fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe95d490a84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe95968babd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe95883e075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe958f8f53f in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7fe833dc9700 (LWP 6750)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe95d4905fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe95d490a84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe95968babd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe95883e075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe958f8f53f in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7fe858949700 (LWP 6749)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe95d4905fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe95d490a84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe95968babd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe95883e075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe958f8f53f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7fe8594a3700 (LWP 6748)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe95d4905fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe95d490a84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe95968babd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe95883e075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe958f8f53f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7fe85a1ed700 (LWP 6747)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe95d4905fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe95d490a84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe95968babd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe95883e075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe958f8f53f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7fe85adee700 (LWP 6746)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fe95d4905fa in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fe95d490a84 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fe95968babd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fe95883e075 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fe958f8f53f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fe85b5ef700 (LWP 6745)):
#0  0x7fe958843ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe95968cf9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2 

[kate] [Bug 394833] Katepart swap file feature not available for unsaved or moved files

[Shriramana Sharma]

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

--- Comment #1 from Shriramana Sharma  ---
Under "expected behaviour" I forgot to add a fourth point:

4. Same swap behaviour should be available for moved files also. Of course,
Katepart can't know where the file has been moved *to*, but it should know
where the file was earlier and should offer to save there or at least it should
offer to save it somewhere if that location no longer exists.

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

[kate] [Bug 394833] New: Katepart swap file feature not available for unsaved or moved files

[Shriramana Sharma]

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

Bug ID: 394833
   Summary: Katepart swap file feature not available for unsaved
or moved files
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: samj...@gmail.com
  Target Milestone: ---

Steps to reproduce:
Test A:
1. Open Kate/KWrite.
2. Type something.
3. Save to a file on disk.
4. Type some more.
5. Kill the process without closing the app correctly.
6. Reopen the file in Kate/KWrite.
7. It flags the file as "not closed properly" and offers to recover the unsaved
data.

Test B:
1. Close the above file without recovering the data.
2. Move the file on disk (without the unsaved data) to another location.
3. Open it from there in Kate/KWrite.
4. It does NOT flag the file as "not closed properly" and does not offer to
recover the unsaved data.

Test C:
1. Open a new document in Kate/KWrite.
2. Type something.
3. Kill the process as before but *without* saving to disk.
4. Reopen Kate/KWrite.
5. It does NOT advise you that a document was not saved and does not offer to
recover the unsaved data.

Observed behaviour:
Test A is the nominal behaviour. In Test B and Test C, there is no way to
recover the lost data. Other applications such as LibreOffice which are used
for other purposes and not really useful for plaintext editing such as
Kate/KWrite however have a data recovery feature which only depends on the
existence of the swap file and not on the existence of the saved file or of
such a file being located in the same directory.

Expected behaviour:
1. Loss of data is unacceptable.
2. Katepart should save swap data for unsaved files also.
3. When Kate/KWrite (or at least Kate only) is reopened after an abnormal
termination, it should advise the user of the availability of such swap data,
whether for saved or unsaved documents, and offer to recover the data.

Comment:
1. This behaviour is already found in LibreOffice etc but which aren't useful
for the usecase of Kate/KWrite etc. Hence I request for Kate to have this
ability.
2. I lost many paragraphs of writing this morning because of this limitation,
prompting me to file this bug.

Thanks!

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

[plasma-browser-integration] [Bug 394673] icon in system tray offers plasma-browser-integration even if it's already installed and working

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #3 from David Edmundson  ---
was the extension installed before you started firefox and then saw this
notification?

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

[krita] [Bug 394817] My palette crashed and now doesn't work

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

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

[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically

[Simone Lazzaris]

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

--- Comment #8 from Simone Lazzaris  ---
The bug persists, in spite of 
Archlinux, KDE 18.04.1, KDE Frameworks 5.46.0, QT 5.10.1

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

[krita] [Bug 394817] My palette crashed and now doesn't work

[Alan Buck]

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

--- Comment #2 from Alan Buck  ---
Thank you for your response. I did finally get it to work. I'm not sure what
made it happen but I kept reinstalling. You can close this bug. 

On Monday, May 28, 2018 11:39 PM, Boudewijn Rempt
 wrote:


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

Boudewijn Rempt  changed:

          What    |Removed                    |Added

        Resolution|---                        |WAITINGFORINFO
                CC|                            |b...@valdyas.org
            Status|UNCONFIRMED                |NEEDSINFO

--- Comment #1 from Boudewijn Rempt  ---
Please try resettin Krita's settings:
https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration . It is
the kritarc file that contains all the settings.

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

[krita] [Bug 394151] Brush glitches

[bugzilla_noreply]

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

--- Comment #12 from jurcsekisintheem...@gmail.com ---
Thanks!

On Tue, May 29, 2018, 03:49 Boudewijn Rempt 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=394151
>
> Boudewijn Rempt  changed:
>
>What|Removed |Added
>
> 
>  Status|NEEDSINFO   |UNCONFIRMED
>  Resolution|WAITINGFORINFO  |---
>
> --- Comment #10 from Boudewijn Rempt  ---
> Settign to unconfirmed since we now have the tablet log. Alvin is
> travelling,
> though.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[telepathy] [Bug 393841] Scrolling is broken in chat windows

[Simone Lazzaris]

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

Simone Lazzaris  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||sim...@omni.it

--- Comment #3 from Simone Lazzaris  ---


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

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

[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically

[Simone Lazzaris]

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

Simone Lazzaris  changed:

   What|Removed |Added

 CC||kde...@mailinator.com

--- Comment #7 from Simone Lazzaris  ---
*** Bug 393841 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 394832] JJ: "CTRL+G" does not work if the last selected layer is a filter.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|"CTRL+G" does not work if   |JJ: "CTRL+G" does not work
   |the last selected layer is  |if the last selected layer
   |a filter.   |is a filter.
   Keywords||junior-jobs

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

[krita] [Bug 394832] "CTRL+G" does not work if the last selected layer is a filter.

[Boudewijn Rempt]

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

--- Comment #1 from Boudewijn Rempt  ---
I can confirm this: what happens is that Krita sees that the current node is a
mask, and thinks that the group layer action cannot be performed. If you'd
select the mask, then shift select to the top layer, the action works.

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

[krita] [Bug 394832] "CTRL+G" does not work if the last selected layer is a filter.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||b...@valdyas.org

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

[krita] [Bug 394832] "CTRL+G" does not work if the last selected layer is a filter.

[mvowada]

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

mvowada  changed:

   What|Removed |Added

Summary|"CTRL+G" does not work if   |"CTRL+G" does not work if
   |the last level selected is  |the last selected layer is
   |a filter.   |a filter.

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

[krita] [Bug 394832] New: "CTRL+G" does not work if the last level selected is a filter.

[mvowada]

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

Bug ID: 394832
   Summary: "CTRL+G" does not work if the last level selected is a
filter.
   Product: krita
   Version: git master
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: freebo...@tiscali.it
  Target Milestone: ---

On Ubuntu Unity - Krita 4.1.0-pre-alpha (git dac4dc7)

Steps:

1) Add a "Transparency Mask" to the lowest layer you want to group
2) click the topmost layer in the docker 
3) SHIFT + click the T. Mask
4) CTRL + G

Actual Results: nothing happens.
Expected Results: group layers.

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

[krusader] [Bug 394831] New: Alphabetical sorting

[Andrej Valek]

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

Bug ID: 394831
   Summary: Alphabetical sorting
   Product: krusader
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: synchronize
  Assignee: krusader-bugs-n...@kde.org
  Reporter: andrej.va...@siemens.com
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Created attachment 112949
  --> https://bugs.kde.org/attachment.cgi?id=112949=edit
synchronize dirs

Listed files are not alphabetical sorted by names.

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

[krita] [Bug 394151] Brush glitches

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

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

--- Comment #11 from Alvin Wong  ---
To be honest, to me these tablet logs often just doesn't really seem to help.
All it shows is that the coordinates from the mouse and WinTab doesn't match,
which we already know even without the log. It doesn't log the raw coordinates
values from the WinTab support code, but even if it does it probably wouldn't
help either, unless the offset is so large that the tablet events are all sent
outside of the canvas area that wouldn't be captured by the tablet debugger.

> Switching to Windows Ink didn't do anything either.
Can you clarify how it didn't do anything? Did pressure sensitivity not work
with Windows Ink? Did you still get the same exact offset with Windows Ink? Can
you perhaps also generate a tablet log with Windows Ink enabled?

Do note that you have to restart Krita after switching to Windows Ink for it to
be in effect, so please remember to do that.

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

[plasmashell] [Bug 394830] New: Can't Pin WINE applications to Icon-Only Task Manager or Latte Dock

[Matt Eaves]

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

Bug ID: 394830
   Summary: Can't Pin WINE applications to Icon-Only Task Manager
or Latte Dock
   Product: plasmashell
   Version: 5.12.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: mr.matthew.ea...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

See: https://github.com/psifidotos/Latte-Dock/issues/823

Also applies to Icon-only Task Manager. 
.desktop files for WINE apps can be pinned, provided there are no spaces in the
name. However, the icon acts only as a launcher and a separate icon appears for
the task on launch. I thought including a StartupWMClass in the .desktop would
work (in this case WINWORD.EXE) would work -- it doesn't. Is there a way of
forcing the task icon and launcher icon to integrate? The task itself cannot be
pinned. 

Using KDE Neon 5.12.5 with all updates installed as of 29th May 2018.

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

[kate] [Bug 394254] Symbol List and Document plugins only work separately

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
This is fixed - this regression was only temporary in the KMultiTabBar, but
never released. Maybe Mageia released an updated version which has this
regression. Please update.

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

[kwin] [Bug 393723] Kwin master with bad blur effect on secondary monitor ( works perfectly on primary )

[Alex Nemeth]

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

Alex Nemeth  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/99532fb95c1edb855ffeedf85
   ||51130d7a783feff
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #11 from Alex Nemeth  ---
Git commit 99532fb95c1edb855ffeedf8551130d7a783feff by Alex Nemeth.
Committed on 29/05/2018 at 13:32.
Pushed by anemeth into branch 'master'.

Fix multimonitor blur

Summary:
On wayland blur on secondary monitor would not render correctly.
Depends on D12452

Test Plan:
 - use more than one output
 - log in in a wayland session
 - open a transparent window (for example: Konsole with transparent and blur
enabled profile)
 - drag the window to another screen
 - blurs the content under the window corretly

Reviewers: #kwin, graesslin, davidedmundson

Reviewed By: #kwin, davidedmundson

Subscribers: apol, zzag, davidedmundson, kwin, #kwin

Tags: #kwin

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

M  +22   -23   effects/blur/blur.cpp
M  +1-1effects/blur/blur.h
M  +4-7effects/blur/blurshader.cpp
M  +0-1effects/blur/blurshader.h

https://commits.kde.org/kwin/99532fb95c1edb855ffeedf8551130d7a783feff

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

[pimsettingexporter] [Bug 394829] New: Support for archive formats other than ZIP in PIM Setting Exporter

[Francesco Turco]

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

Bug ID: 394829
   Summary: Support for archive formats other than ZIP in PIM
Setting Exporter
   Product: pimsettingexporter
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mon...@kde.org
  Reporter: ftu...@fastmail.fm
  Target Milestone: ---

I have PIM Setting Exporter 5.8.1 on a Gentoo Linux system.

As far as I know PIM Setting Exporter can only create ZIP archives. In my
opinion it should also support other archive formats, such as .tar.gz, .tar.bz2
and .tar.xz. Personally I would choose .tar.xz because it has the highest
compression ratio.

What do you think?

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