[plasmashell] [Bug 365204] Breeze icons are always used in some places

[Pulfer via KDE Bugzilla]

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

Pulfer  changed:

   What|Removed |Added

 Resolution|INVALID |FIXED

--- Comment #4 from Pulfer  ---
(In reply to Eike Hein from comment #3)
> At least in Kicker's case, the system favorites are supposed to use the 
> Plasma theme. 

Why does it use Breeze icons if Plasma theme is set to Oxygen? Is it a Plasma
bug?

> The Kickoff patch might be valid, please submit it via Phab.

https://git.reviewboard.kde.org/r/128392/

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

[krita] [Bug 362177] Problem with assigning brush tags

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #6 from Boudewijn Rempt  ---
"Something must be done". Please do it, then. I've fixed 18 bugs this week, but
there are a few hundred open bugs that need to be fixed and a hundred things
besides that must be done, sometimes before a certain deadline, like taxes.

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

[plasmashell] [Bug 365204] Breeze icons are always used in some places

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #3 from Eike Hein  ---
At least in Kicker's case, the system favorites are supposed to use the Plasma
theme. The Kickoff patch might be valid, please submit it via Phab.

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

[plasmashell] [Bug 360491] Panel resets size, width, height when display resolution changes

[Jon via KDE Bugzilla]

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

--- Comment #3 from Jon  ---
Is this a flat out "never going to happen" and won't be considered as a feature
request or wishlist?

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

[plasmashell] [Bug 365204] Breeze icons are always used in some places

[Pulfer via KDE Bugzilla]

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

--- Comment #2 from Pulfer  ---
Created attachment 99929
  --> https://bugs.kde.org/attachment.cgi?id=99929=edit
Patch to make kicker and kickoff use icons from icon theme

Not sure if it's desired behaviour for upstream. But as it makes Kicker and
Kickoff look consistent, I'll apply it to ROSA's Plasma Desktop package.

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

[kwin] [Bug 365196] new user: default decoration is Plastik

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Gräßlin  ---
Please report to your distribution. They compiled KWin without the (new)
dependency to Breeze.

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

[digikam] [Bug 365079] Digikam 5.0 beta 7 crashes while showing the splash image.

[Hans-Peter via KDE Bugzilla]

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

Hans-Peter  changed:

   What|Removed |Added

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

--- Comment #10 from Hans-Peter  ---
Surprise, surprise.

I vaguely remembered that someone had problems with the digikamrc file. So i
tried again, removed .config/digikamrc (from older beta 6) before.  And now
digikam5 from Philips ppa starts fine and i can start real testing or even go
and make new images :)

I think there should be an error message. 

Happy again. Thanks Philip and Gilles for the patience and support.

HP

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

[kate] [Bug 353404] My kate version is not listed in the possible versions.

[Sven Brauch via KDE Bugzilla]

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

--- Comment #4 from Sven Brauch  ---
There's an implied "I won't do it right now because I have other things to do
but I agree that somebody should do it, though I see it coming that this
problem will be there again in six months unless it gets automated".

There is no need to question the whole world because of such a minor issue ...
just select unspecified and all will be good.

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

[plasmashell] [Bug 365204] Breeze icons are always used in some places

[Pulfer via KDE Bugzilla]

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

--- Comment #1 from Pulfer  ---
Created attachment 99928
  --> https://bugs.kde.org/attachment.cgi?id=99928=edit
Kickoff menu with messup up icons

Kickoff menu is also affected. Some icons are taken from Breeze them, some from
Oxygen.

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

[konsole] [Bug 362171] Patch review requested for implementation SGR 2/8/9/53 (dim/conceal/strikeout/overline)

[Antonio Russo via KDE Bugzilla]

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

--- Comment #7 from Antonio Russo  ---
The revised patchset has support for all default color schemes. There should be
no issues using these color schemes.

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

[konsole] [Bug 362171] Patch review requested for implementation SGR 2/8/9/53 (dim/conceal/strikeout/overline)

[Antonio Russo via KDE Bugzilla]

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

--- Comment #6 from Antonio Russo  ---
Created attachment 99927
  --> https://bugs.kde.org/attachment.cgi?id=99927=edit
Revised complete patchset

tar.gz of 6 patches

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

[plasmashell] [Bug 365204] New: Breeze icons are always used in some places

[Pulfer via KDE Bugzilla]

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

Bug ID: 365204
   Summary: Breeze icons are always used in some places
   Product: plasmashell
   Version: 5.6.5
  Platform: ROSA RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: pul...@list.ru
CC: plasma-b...@kde.org

Even if icon theme and plasma theme are set to Oxygen (or other themes), Breeze
icons are used for favorite system actions in Kicker. At the same time icons in
system actions submenu are correctly set from current icon theme.

Plasma 5.6.5, KF 5.23.0, Qt 5.6.1.

Reproducible: Always

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

[digikam] [Bug 365125] Win64 version cannot start

[via KDE Bugzilla]

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

--- Comment #27 from pascale-hullm...@web.de ---
Thanks! Your Installer worked. 

P.

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

[kmail2] [Bug 365162] after upgrading today, kmail folder list corrupted

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #4 from Laurent Montel  ---
It's an upgrade from what ?
build from hand ?
If it's package ask to your distro.
4.4.10 is very very old and stable so if a upgrade broke it it's a problem from
distro no us

Regards

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

[plasmashell] [Bug 365199] plasma-pa OSD show speaker with different size if muted.

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Kai Uwe Broulik  ---
That's probably because I changed the icon to be anchored to either progress
bar or text to accommodate for multiple lines and those have slightly varying
heights.

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

[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins [patch]

[Willy Sudiarto Raharjo via KDE Bugzilla]

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

Willy Sudiarto Raharjo  changed:

   What|Removed |Added

 CC||will...@gmail.com

--- Comment #22 from Willy Sudiarto Raharjo  ---
Tested Fabian Vogt's patch for imgur and confirmed to work here on Slackware
14.2

suggestion: is it possible to bump all cmake minimum to 3.0.0 so that it's
consistent in all digiKam/kipi-plugins code?

Thanks

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

[digikam] [Bug 365202] Segfault on faces detect.

[Evert Vorster via KDE Bugzilla]

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

--- Comment #5 from Evert Vorster  ---
Rebuiding takes a while. 
In the meantime, I found the option for using multiple CPU, and on my machine
it is turned off. 

I'll go recompile with debug options.

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

[kde] [Bug 365203] New: Fix/block menu entry in every KDE programs with one click

[Sandro kensan via KDE Bugzilla]

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

Bug ID: 365203
   Summary: Fix/block menu entry in every KDE programs with one
click
   Product: kde
   Version: unspecified
  Platform: unspecified
   URL: http://www.kensan.it/tmp/menu.png
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ken...@kensan.it

The menu entry like "Zoom" in the image http://www.kensan.it/tmp/menu.png can
be a long row like the entry in the menu bookmarks in the firefox menu or other
menus. If you must choice an item like "zoom in" (see png) you must to walk the
entire row with the mouse pointer. I the row is long the mouse point walking is
not straightness so are open the upper menu or the lower menu (sidebar menu or
page style menu, see png).

To avoid this the feature that I proposed is to add an optional click in the
menu "Zoom" that block/fix the entry "Zoom". So if you travel with the mouse
pointer outside the row "Zoom" the entry Zoom is always selected.

For Deselect the entry menu block you can click other menu entry.

Reproducible: Always

Steps to Reproduce:
1.click the menu View (see http://www.kensan.it/tmp/menu.png)
2.descend to the entry "zoom"
3.click (one click) on the entry "zoom" (whatever point of the row "zoom")
4.travel from the begin of the row "zoom" to the right end because you want to
choice the voice "zoom in" (see png)
5.go outside the row "zoom" because the row is long and your mouse pointer path
is not straightness

Actual Results:  
The menu entry "Zoom" is deselected and the sub menu disappear

Expected Results:  
The menu entry "zoom" remain selected and you can selected the voice "zoom in".

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

[digikam] [Bug 365202] Segfault on faces detect.

[via KDE Bugzilla]

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

--- Comment #4 from caulier.gil...@gmail.com ---
The backtrace do not include debug symbols. Please recompile whole digiKam
source code with debug, using cmake option "-DCMAKE_BUILD_TYPE=debug"

Gilles Caulier

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

[krita] [Bug 365185] Krita crashes when using Trust tablet

[wolthera via KDE Bugzilla]

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

--- Comment #3 from wolthera  ---
yay! Let's hope this'll stay stable then.

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

[digikam] [Bug 365202] Segfault on faces detect.

[via KDE Bugzilla]

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

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

   What|Removed |Added

Summary|git master 2016-07-07 : |Segfault on faces detect.
   |Segfault on faces detect.   |

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

[digikam] [Bug 365202] git master 2016-07-07 : Segfault on faces detect.

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Version|unspecified |5.0.0

--- Comment #3 from caulier.gil...@gmail.com ---
Which OpenCV version you use ? Look in Components Info dialog for details.

Did you use multicore CPU option to detect face ?

Gilles Caulier

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

[plasmashell] [Bug 365014] All windows hide on repeating desktop click

[Rog131 via KDE Bugzilla]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

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

[korganizer] [Bug 358106] [REGRESSION] Allow week to start on Monday

[David Wen Riccardi-Zhu via KDE Bugzilla]

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

David Wen Riccardi-Zhu  changed:

   What|Removed |Added

 CC||dwriccardi...@gmail.com

--- Comment #11 from David Wen Riccardi-Zhu  ---
Can also confirm Kubuntu 16.04.

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

[digikam] [Bug 365202] git master 2016-07-07 : Segfault on faces detect.

[Evert Vorster via KDE Bugzilla]

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

--- Comment #2 from Evert Vorster  ---
Created attachment 99926
  --> https://bugs.kde.org/attachment.cgi?id=99926=edit
A different segfault on updating the faces database

I have a feeling that the faces detect, and updating the faces database may be
related. 
With this log I was just sorting through the unknown faces, with no face detect
running.

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

[digikam] [Bug 322946] MYSQL : picture collection and database on a server can handle only one user

[via KDE Bugzilla]

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

--- Comment #8 from swatilodh...@gmail.com ---
Another thought, we could implement the internal locking methods. Since
there're already InnoDB tables present, we could use "row level locking". This
would allow multiple write access, making it suitable for multiple users.

Thus, "SELECT ... FOR UPDATE" (type of InnoDB lock) could be used. 
http://dev.mysql.com/doc/refman/5.7/en/innodb-locking-reads.html

Please let me know if it could be done? 

Thanks

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

[kmymoney4] [Bug 365177] Changing investment fraction doesn't change rounding behavior

[Jack via KDE Bugzilla]

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

Jack  changed:

   What|Removed |Added

 CC||ostroffjh@users.sourceforge
   ||.net

--- Comment #1 from Jack  ---
Please clarify:  do you see the correct numbers after restarting KMM?  If so,
the issue is not that the rounding behaviour isn't change, but that it isn't
changed immediately, and requires a restart of KMM to take effect.  One is a
real bug, the other is simply an inconvenience, although it might be possible
to have the change take effect immediately.

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

[digikam] [Bug 365202] git master 2016-07-07 : Segfault on faces detect.

[Evert Vorster via KDE Bugzilla]

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

--- Comment #1 from Evert Vorster  ---
Created attachment 99925
  --> https://bugs.kde.org/attachment.cgi?id=99925=edit
Backtrace of the fault

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

[digikam] [Bug 365202] New: git master 2016-07-07 : Segfault on faces detect.

[Evert Vorster via KDE Bugzilla]

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

Bug ID: 365202
   Summary: git master 2016-07-07 : Segfault on faces detect.
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Engine
  Assignee: digikam-de...@kde.org
  Reporter: evert.vors...@yandex.com

This looks very similar to bug 262596, but that bug is from 2011, and says it's
fixed, and I am getting segfaults with a compiled from sources from git of
today. 

I was trying out digikam's faces detect on the git master from a couple days
back, and noticed that the application is crash-happy when detecting/tagging
faces. So, I pulled from git today, and retried the operation. 

So, to test, I just opened digikam, pointed it at a directory of photos and let
the face detect do it's thing. 


Reproducible: Always

Steps to Reproduce:
1. Open digikam
2. Select "faces" icon
3. Select scan database for face. 
4. select subset of photo database
5. Set it to detect faces only, not try to recognize them. 
6. Let it run... 


Actual Results:  
The program segfaults after running for a few minutes. 

Expected Results:  
All the faces to be detected without a segfault. 

I am using three MariaDB databases for DigiKam, rather than the internal
sqlite.

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

[plasmashell] [Bug 363597] Incorrect time in digital clock

[Leszek Lesner via KDE Bugzilla]

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

--- Comment #2 from Leszek Lesner  ---
Timezone was correct in the timezone tab and scrolling on the clock itself
didn't change a thing. 
I will check again next week with Plasma 5.7 to see if it's still an issue.

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

[plasmashell] [Bug 363597] Incorrect time in digital clock

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Edmundson  ---
The plasma clock can be set to show a different time zone to your system time
zone.

Please see the time zone tab in the digital clock applet.

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

[plasmashell] [Bug 360165] crash when changing screen resolution

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #8 from David Edmundson  ---
Fixed in Qt5.6. 

Please reopen if you get a crash after that.

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

[trojita] [Bug 365149] parsing error in * STATUS "INBOX" (MESSAGES 702 UNSEEN 0 RECENT 0)

[Jan Kundrát via KDE Bugzilla]

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

--- Comment #2 from Jan Kundrát  ---
> only one space is allowed between the * and the STATUS keyword:

Oh yeah, that server is clearly broken, but we've added similar 
compatibility quirks before.

Jaime, could you please confirm that reinstalling Trojita using [1] fixes 
this issue for you?

[1] 
http://ci-logs.kde.flaska.net/binaries/trojita/win32/check/Trojita-Setup-767-12d9c5a750814e64b4e2483ae862f633.exe

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

[plasmashell] [Bug 365199] plasma-pa OSD show speaker with different size if muted.

[David Rosca via KDE Bugzilla]

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

David Rosca  changed:

   What|Removed |Added

   Target Milestone|--- |1.0
  Component|applet  |general
 CC||bhus...@gmail.com
Product|plasma-pa   |plasmashell
   Assignee|now...@gmail.com|k...@davidedmundson.co.uk

--- Comment #2 from David Rosca  ---
Reassigning to plasmashell OSD.

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

[KScreen] [Bug 365201] New: Primary screen setting not honoured

[via KDE Bugzilla]

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

Bug ID: 365201
   Summary: Primary screen setting not honoured
   Product: KScreen
   Version: 5.7.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: rockonthemoo...@gmail.com

changing primary screen setting in systemsettings is not honoured

Reproducible: Always

Steps to Reproduce:
1. connect VGA screen to laptop
2. reboot
3. change primary monitor in systemconfig

Actual Results:  
nothing happens (except plasma reloading)

Expected Results:  
default workspace should be displayed in primary screen, 
windows should open in primary screen if launched from primary screen

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

[kate] [Bug 353404] My kate version is not listed in the possible versions.

[Eric S via KDE Bugzilla]

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

--- Comment #3 from Eric S  ---
Forgive me if I'm reading too much into that replybut is there an implied
"...therefore we don't / won't do it?" 

Isn't updating the bug tracking system with the new version simply a standard
part of the release process?  Isn't it among the most basic things developers
should do to maintain the most basic level of professionalism? Or is this bug
system deprecated and some other one meant to be used for Kate? Or is Kate
essentially an unmaintained project? I'm really struggling to make sense of
this...

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

[ark] [Bug 365200] Open Recent action is enabled while opening an archive

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasma-pa] [Bug 365199] New: plasma-pa OSD show speaker with different size if muted.

[Till Schäfer via KDE Bugzilla]

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

Bug ID: 365199
   Summary: plasma-pa OSD show speaker with different size if
muted.
   Product: plasma-pa
   Version: 5.7.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: till2.schae...@uni-dortmund.de
CC: plasma-b...@kde.org

The OSD of plasma-pa shows volume changes. If the device gets into muted state
the volume indicator bar (on the bottom) gets replaced with a label "Audio
Muted". This label seems to cause a resize of the OSD symbol on the top. The
speaker symbol for the muted state is smaller that the speaker symbol in
unmuted state.  See the attached screencast for an example.

Reproducible: Always

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

[ark] [Bug 365200] New: Open Recent action is enabled while opening an archive

[Elvis Angelaccio via KDE Bugzilla]

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

Bug ID: 365200
   Summary: Open Recent action is enabled while opening an archive
   Product: ark
   Version: 16.04.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kdemail.net
  Reporter: elvis.angelac...@kdemail.net
CC: rak...@freebsd.org, rthoms...@gmail.com

This means that the user can start another ListJob, leading to a crash.

Reproducible: Always

Steps to Reproduce:
1. Open an huge archive
2. Archive -> Open Recent while the previous archive is still loading

Actual Results:  
Crash

Expected Results:  
Archive -> Open Recent should not be enabled during a ListJob

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

[krita] [Bug 365185] Krita crashes when using Trust tablet

[via KDE Bugzilla]

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

jasminn...@gmail.com changed:

   What|Removed |Added

 Resolution|INVALID |FIXED

--- Comment #2 from jasminn...@gmail.com ---
It works! Happy day! Thank you very much! ♥
(And I am considering getting a better tablet, but I'm first getting a better
phone, and I don't want to spend too much money at once. Perhaps I'll get one
for myself when I graduate as a present!)

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

[plasma-pa] [Bug 365199] plasma-pa OSD show speaker with different size if muted.

[Till Schäfer via KDE Bugzilla]

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

--- Comment #1 from Till Schäfer  ---
Created attachment 99924
  --> https://bugs.kde.org/attachment.cgi?id=99924=edit
plasma pa volume change screencast

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

[plasmashell] [Bug 365198] New: logout dialog always shown in external screen

[via KDE Bugzilla]

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

Bug ID: 365198
   Summary: logout dialog always shown in external screen
   Product: plasmashell
   Version: 5.7.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: rockonthemoo...@gmail.com
CC: plasma-b...@kde.org

connected second display via VGA, logged out: Plasma logout dialog always
appears on second display, no matter what, retaining resolution of primary
screen

Reproducible: Always

Steps to Reproduce:
1. plug VGA screen
2. optionally reboot
3. logout

Actual Results:  
logout dialog in second screen, with resolution as it was in primary

Expected Results:  
logout dialog on primary screen, 
all the monitors are desaturated

photo https://goo.gl/photos/QsXhTDiqnVS3wNSW6

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

[krita] [Bug 365178] Floating docker causes wacom pen to stop registering brush strokes

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

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

--- Comment #1 from wolthera  ---
Does the same happen with the appimage?

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

[plasma-pa] [Bug 365197] New: add a notification settings for volume change events

[Till Schäfer via KDE Bugzilla]

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

Bug ID: 365197
   Summary: add a notification settings for volume change events
   Product: plasma-pa
   Version: 5.7.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: till2.schae...@uni-dortmund.de
CC: plasma-b...@kde.org

KMix plays a sound and shows an OSD whenever the volume changes by "volume
up/down". In contrast, plasma-pa only shows the OSD, but plays no sound. The
sound is helpful to get a feedback about the actual loudness of the sound
device (its sometimes hard to guess how loud X% might be), especially if one
wants to configure the volume before (and not while) playing some media.

As there are also peplle which may prefer a silent volume change, I would like
to propose that  plasma-pa adds a volume change notification event that can be
configured individually.

Reproducible: Always

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

[krita] [Bug 365185] Krita crashes when using Trust tablet

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from wolthera  ---
check if this one works: https://krita.org/en/item/anatomy-of-a-bug-fix/

Do note that we do not support Trust tablets officially as their drivers are
terrible(as detailed in the post), and I am seriously recommending you to get a
different tablet.

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

[kwin] [Bug 365196] New: new user: default decoration is Plastik

[via KDE Bugzilla]

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

Bug ID: 365196
   Summary: new user: default decoration is Plastik
   Product: kwin
   Version: 5.7.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: rockonthemoo...@gmail.com

created a new user, defualt decoration defaulted to Plastik

Reproducible: Always

Steps to Reproduce:
1. create a new user or delete all configs in ~/
2. logout, login

Actual Results:  
Plastik is default deco

Expected Results:  
Breeze is default deco

verified: big present with new user, or when deleting all configs in home

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

[kmix] [Bug 355437] no notification settings for kmix-4.6rc1 (kde apps 12.08.3) volume popup (changing volume)

[Till Schäfer via KDE Bugzilla]

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

Till Schäfer  changed:

   What|Removed |Added

Summary|no notification settings|no notification settings
   |for kmix-4.6rc1 (kde apps   |for kmix-4.6rc1 (kde apps
   |18.08.3) volume popup   |12.08.3) volume popup
   |(changing volume)   |(changing volume)

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

[kate] [Bug 362864] Kate does not save Sidebar state in configuration settings files

[Bob Wya via KDE Bugzilla]

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

--- Comment #2 from Bob Wya  ---
(In reply to Buovjaga from comment #1)
> I don't have this problem.
> 
> Arch Linux 64-bit
> Kate 16.04.2
> KDE Frameworks 5.23.0
> Qt 5.7
> xcb wm

Ditto on the base packages and Kate version. So maybe it's a Plasma 5 specific
issue?

Some more testing ...
1. Ensure you have *NO* saved Kate sessions
2. Start Kate session (either from shell or application menu/krunner)
3. Disable plugin "File system browser"
4. In Kate settings menu : enable save Window state in Session / Load last used
Session
5. Sessions -> Save session (i.e. save to a blank/default session)
6. Close Kate
7. Restart Kate (as per 2.)

In my mind (!!) a blank session name should still be saved to a "default"
location.

But even when I used a named session and the above steps - none of my plugins
are staying enabled. Even when I manually reload the session... The other Kate
settings are being restored successfully. Very weird??!!

I've tried cleaning out the "cruft" - removing my kate* config files from
~/.config.
There are no KDE 4 config kate* config files in my ~/.kde4 profile directories.

So it I guess it might be a cache issue - with Plasma 5. I'll try cleaning this
out next!!

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

[konsole] [Bug 196998] Konsole should reflow the text when resizing

[Shawn Rutledge via KDE Bugzilla]

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

Shawn Rutledge  changed:

   What|Removed |Added

 CC||s...@ecloud.org

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

[plasmashell] [Bug 355122] Crash in krunner with unsafe QIcon::fromTheme

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
   Version Fixed In||5.8.0
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #8 from Kai Uwe Broulik  ---
This is fixed in Plasma 5.8.

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

[plasmashell] [Bug 356446] plasmashell does not respect QT_DEVICE_PIXEL_RATIO

[David Edmundson via KDE Bugzilla]

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

--- Comment #7 from David Edmundson  ---
there's a Qt bug in Text with nativeRendering where it will get the kerning
completely mental.

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

[plasmashell] [Bug 360491] Panel resets size, width, height when display resolution changes

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX
 CC||k...@davidedmundson.co.uk

--- Comment #2 from David Edmundson  ---
@Marco, then close the bug.

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

[plasmashell] [Bug 365158] option to change font color in task manager

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #9 from David Edmundson  ---
It's simpler than that:

run Plasma Theme Rxplorer

Click new

Click "edit colors"

In system settings select your new customised theme

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

[plasmashell] [Bug 365190] Notifications Widget shows up as "Unknown" in panel, doesn't work.

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
Your setup is broken.

Please check your installation.

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

[kmail2] [Bug 365162] after upgrading today, kmail folder list corrupted

[Fred Jackson via KDE Bugzilla]

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

--- Comment #3 from Fred Jackson  ---
dialog for managing accounts is unusable. Unable to even attempt to rebuild
kmail because I cannot add a 'Local Folders' resource, in fact I am unable to
add accounts at all.

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

[trojita] [Bug 365149] parsing error in * STATUS "INBOX" (MESSAGES 702 UNSEEN 0 RECENT 0)

[paalsteek via KDE Bugzilla]

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

paalsteek  changed:

   What|Removed |Added

 CC||k...@paalsteek.de

--- Comment #1 from paalsteek  ---
According to RFC 3501, Section 9
(https://tools.ietf.org/html/rfc3501#section-9) only one space is allowed
between the * and the STATUS keyword:

"(2) In all cases, SP refers to exactly one space.  It is
NOT permitted to substitute TAB, insert additional spaces,
or otherwise treat SP as being equivalent to LWSP."

"response-data   = "*" SP (resp-cond-state / resp-cond-bye /
  mailbox-data / message-data / capability-data) CRLF"

and
"mailbox-data=  "FLAGS" SP flag-list / "LIST" SP mailbox-list /
   "LSUB" SP mailbox-list / "SEARCH" *(SP nz-number) /
   "STATUS" SP mailbox SP "(" [status-att-list] ")" /
   number SP "EXISTS" / number SP "RECENT""

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

[neon] [Bug 365195] PureRef app font became unreadable after update to Neon 5.7

[Denis Moon via KDE Bugzilla]

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

Denis Moon  changed:

   What|Removed |Added

 Resolution|INVALID |WAITINGFORINFO
 Status|RESOLVED|VERIFIED

--- Comment #2 from Denis Moon  ---
I've done this. Looking forward to an answer! The only one thing I don't get is
why the font gets readable with root...

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

[digikam] [Bug 262165] Error message when saving image in exposure blending dialogue

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #13 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 245582] When you try to save the blended image it will some times say can not save jpg such and such

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

--- Comment #5 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 235683] Metadata invalid when converting CRW

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #9 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[neon] [Bug 365195] PureRef app font became unreadable after update to Neon 5.7

[Harald Sitter via KDE Bugzilla]

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

Harald Sitter  changed:

   What|Removed |Added

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

--- Comment #1 from Harald Sitter  ---
Get in touch with PureRef. It occurs to me they have bad path isolation.

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

[digikam] [Bug 255137] Some exif metadata are lost when converting CR2 to DNG

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

--- Comment #15 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 315137] wired color converzion with multi exposure photos

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 330133] crash during workflow in exporting jpeg from raw cr2

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #6 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 348484] extreme long saving times for settings

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 348229] crash if I try to show slideshow in second VGA display

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

--- Comment #5 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 194334] A Fatal Error Occurred The application digiKam (digikam) crashed and caused the signal 11 (SIGSEGV)

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

--- Comment #15 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 279969] Digikam crash after closing the extendet Diashow

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #8 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[digikam] [Bug 307183] Advanced Slideshow turns completely white (Open GL Transitions enabled)

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

--- Comment #12 from caulier.gil...@gmail.com ---
This problem is not reproducible with last 5.0.0
I close this file now. Re-open it if necessary.
Gilles Caulier

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

[kontact] [Bug 361381] Kmail crashes when replying to specific email

[via KDE Bugzilla]

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

noucam...@hotmail.com changed:

   What|Removed |Added

 CC||noucam...@hotmail.com

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

[kontact] [Bug 361381] Kmail crashes when replying to specific email

[via KDE Bugzilla]

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

--- Comment #1 from noucam...@hotmail.com ---
Created attachment 99923
  --> https://bugs.kde.org/attachment.cgi?id=99923=edit
New crash information added by DrKonqi

kontact (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:

Replying to email (IMAP). Although it may be unrelated, I have noticed that
some of my IMAP accounts fail to synchronize after Kmail has been opened for
several hours. This was not the case (this time) with the account I was
replying from.

-- Backtrace (Reduced):
#6  0x7f0f3f3c1c37 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x7f0f3f3c5028 in __GI_abort () at abort.c:89
[...]
#9  0x7f0f3f40a55e in malloc_printerr (ptr=,
str=0x7f0f3f50c7e0 "double free or corruption (out)", action=1) at
malloc.c:4996
#10 _int_free (av=, p=, have_lock=0) at
malloc.c:3840
#11 0x7f0f4082c929 in QTextOption::operator= (this=0x826aa50, o=...) at
text/qtextoption.cpp:129

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

[krita] [Bug 362177] Problem with assigning brush tags

[Denis Moon via KDE Bugzilla]

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

--- Comment #5 from Denis Moon  ---
The bug still annoys me:-( Something must be done! Assigning brush tags from
All Presents works in 1 out of 10 cases. Sometimes I have to restart Krita many
times to get the job done.

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

[neon] [Bug 365195] New: PureRef app font became unreadable after update to Neon 5.7

[Denis Moon via KDE Bugzilla]

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

Bug ID: 365195
   Summary: PureRef app font became unreadable after update to
Neon 5.7
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: lloe...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

After upgrading to Neon 5.7 PureRef app font became so tiny that it's hardly
possible to read. If I start the app in terminal, it says
"Cannot find font directory /usr/local/Qt-5.6.0/lib/fonts - is Qt installed
correctly?
libpng warning: iCCP: known incorrect sRGB profile
QObject::connect: Incompatible sender/receiver arguments
Action::triggered(int) --> MainFrame::setMaximized(bool)
QObject::connect: Incompatible sender/receiver arguments
Action::triggered(int) --> MainFrame::setAlwaysOnTop(bool)
QObject::connect: Incompatible sender/receiver arguments
Action::triggered(int) --> MainFrame::setAlwaysOnBottom(bool)
QObject::connect: Incompatible sender/receiver arguments
Action::triggered(int) --> MainWindow::setMouseTransparent(bool)
QObject::connect: Incompatible sender/receiver arguments
Action::triggered(int) --> MainWindow::setOverlay(bool)
QObject::connect: Incompatible sender/receiver arguments
Action::triggered(int) --> MainWindow::setWindowLocked(bool)
QObject::connect: Incompatible sender/receiver arguments
Action::triggered(int) --> MainWindow::setCanvasLocked(bool)
"
If I start the app as root, the font gets readable. 
What shall I do?

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

[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145

[Bit Twister via KDE Bugzilla]

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

--- Comment #12 from Bit Twister  ---
(In reply to Sebastian Kügler from comment #10)
> Apparently, your distro changes the session file for plasma.desktop. Please
> find out the version in your distro.

You might need to give me specific file name when possible. I am just a dumb
user here. Guessing

$ get_src_rpm /usr/share/xsessions/01plasma.desktop

  Installed rpm : plasma-workspace-5.6.5.1-1.mga6
  Source rpm: plasma-workspace-5.6.5.1-1.mga6.src.rpm
  Information   : https://www.kde.org/

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

[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #11 from Sebastian Kügler  ---
Please upgrade to Plasma 5.7 and show me the output of kscreen-doctor -b

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

[digikam] [Bug 322946] MYSQL : picture collection and database on a server can handle only one user

[Richard Mortimer via KDE Bugzilla]

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

--- Comment #7 from Richard Mortimer  ---
(In reply to swatilodha27 from comment #6)
> (In reply to Richard Mortimer from comment #5)
... snip ...
> > 
> > - this also means that the referential integrity constraints/checks are
> > vital to the correct operation of the database because they help to ensure
> > that no-one add duplicates or add references to tags/images that may have
> > been added/deleted by someone else.
> 
> After your yesterday's patch on this
> https://bugs.kde.org/show_bug.cgi?id=355831, I think referential integrity
> is mostly done, so duplicates could now be avoided.
yes that is correct. However the consequence is that any attempt to add a
duplicate will fail when executing the SQL. Hence we should be vigilant for
this and properly investigate any failures because they may point to a bug
somewhere in the code.

> 
> > 
> > - to my mind this is where the most important preparations for a
> > multi-digikam shared operation mode come in. The database access routines in
> > digikam should (and many are) be arranged as logical operations, e.g. add a
> > tag and give me the database id of the tag. Those operations have to be well
> > tested and able to work around changes made by other users. For instance the
> > add a tag operation SQL might fail because another digikam has already added
> > that tag. In that instance it should find the requested tag and load the
> > data/return the tag id from the other record.
> 
> For 1) and 3) point you wrote:
> In order to ensure that SQL query made by a user doesn't fail (if another
> user has just made a change in the DB), I think we could use INSERT IGNORE
> INTO or REPLACE statements, instead of simply INSERT query?
> If there's no duplicate, INSERT IGNORE INTO will INSERT as general, else
> IGNORE will discard silently without an error. Thus, preventing duplicate
> records.
> Or REPLACE could be better, in order to get the latest change in the DB.
Yes. Those do work although be mindful that many of these are not in the
standard SQL syntax and hence are less portable when it comes to adding
additional databases in the future.

Any use of these also needs to be careful to ensure that it receives the
primary key for any added/replaced rows as appropriate so that the digikam code
can add that to internal data structures.

> 
> > - related to that digikam would need the ability to "rescan" the database in
> > a similar manner to the way that it can rescan a filesystem. This allows it
> > to easily pick up changes made by other users and integrate them into the
> > Tags/Albums trees. I suspect that much of the images operation is already
> > working in that way because digikam generally queries the database to find
> > images etc.
> 
> How to go with the "re-scanning" of DB, so it's updated for all users, if
> changes are made by another user?
>  
It is each digikam instance that needs to re-scan the DB. I am not familiar
with the implementation of the internals of digikam to comment about how best
to do it at the moment. But it could be quite complex trying to merge with the
existing structure or it could be fairly simple by rebuilding (although this
would have problems with keeping selections, open branches and similar.

> > - the next thing related to concurrency is to consider the use of
> > transactions to ensure that a group of operations either completes or does
> > not. This may be of use when adding something like an image and there are a
> > number of different tables that need updating with the properties of that
> > image. This may not be strictly necessary because it might be enough that
> > each table entry is considered on its own merits. But without it some image
> > metadata may not get saved to the database if digikam crashes halfway
> > through an operation.
> 
> Using TRANSACTIONS for all SQL queries? Or with add/delete/update a
> Tag/image/album would suffice? 
All queries do actually use transactions. But by default each statement is
executed in a single transaction (auto commit mode). There should be no need to
change the majority of statements unless there are any sequences that should be
done as a single unit or not done at all.

> 
> > There is nothing stopping digikam allowing multiple users to have concurrent
> > access to the database. I've used it myself but at the moment care has to be
> > taken by the user to make it a mostly read-only sharing otherwise strange
> > behaviour may occur. But there is a lot of preparation that could be made to
> > prepare for more multi-user operation. Possibly the best way to do this is
> > to write unit tests of the individual operations on something like the tags
> > tree and within those tests explicitly inject changes as though they were
> > from another user to make sure that the code handles them correctly.
> 
> If I'm right, making DB "read only" for users could definitely prevent lot
> of confusion that 

[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #10 from Sebastian Kügler  ---
Apparently, your distro changes the session file for plasma.desktop. Please
find out the version in your distro.

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

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

[Julian Seward via KDE Bugzilla]

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

--- 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


+  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.  


+  /* 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?


+  /* -- 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?


 [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.


 [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

+ 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 ) );
Didn't you do a C helper function for this in the previous patch?
This generates terribly verbose code.


-- [4] misc other correctness comments/queries --

+static
+Bool FPU_rounding_mode_isOdd (IRExpr* mode) {
+   /* If the rounding mode is set to odd, the the expr must be a constant U8
+* value equal to 8.  Otherwise, it must be a bin op expressiong that
+* calculates the value.
+*/
+
+   if (mode->tag != Iex_Const)
+  return False;
+
+   vassert(mode->Iex.Const.con->tag == Ico_U32);
+   if (mode->Iex.Const.con->Ico.U8 == 0x8)
+  return True;
+
+   vex_printf("ERROR: FPU_rounding_mode_isOdd(), constant not equal to
expected value\n");
+   return False;
+}
Doesn't seem right to me.  What happens if mode isn't an Iex_Const?
Do you really want to just return False?  Shouldn't the system assert
if that happens?


+++ b/memcheck/mc_translate.c
+#if !(defined(VGA_ppc64be) || defined(VGA_ppc64le))
tl_assert(ty != Ity_I128);
+#endif
Don't make this conditional


-- [5] various typos in comments --

Some of these occur several times -- copy n pasted?  Can you search
to find all dups?

+  /* 128-bit multipy by 10 instruction, result is lower 128-bits */
+  Iop_MulI128by10,
Nit: please fix typos (multipy) (in various places)


+++ 

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

[Julian Seward via KDE Bugzilla]

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

--- Comment #3 from Julian Seward  ---
(In reply to Carl Love from comment #2)
> expected output files are rather large, total size is 33MBytes. 

33 MB is pretty large.  That space will be in the distro tarballs for ever more
and also on the SVN server.  Is it possible to make this a bit smaller, without
losing test coverage?

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

[Baloo] [Bug 360517] Gwenview crashes when using image viewer and navigating to next image with arrowkey on keyboard

[Alexander Potashev via KDE Bugzilla]

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

--- Comment #4 from Alexander Potashev  ---
(In reply to Alexander Potashev from comment #3)
> digiKam-5.x

Oops, I meant KF5-based versions of Gwenview.

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

[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145

[Bit Twister via KDE Bugzilla]

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

--- Comment #9 from Bit Twister  ---
 get_src_rpm /usr/bin/kinfocenter

  Installed rpm : kinfocenter-5.6.5-1.mga6
  Source rpm: kinfocenter-5.6.5-1.mga6.src.rpm
  Information   : https://www.kde.org/

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

[Baloo] [Bug 365126] digiKam is crashing when exporting/saving as new version

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED
 CC||aspotas...@gmail.com

--- Comment #1 from Alexander Potashev  ---
Baloo 4.x is unmaintained. If the problem persists with digiKam-5.x and
Baloo-5.13 or newer, please file another bug report for product
"frameworks-baloo".

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

[Baloo] [Bug 360517] Gwenview crashes when using image viewer and navigating to next image with arrowkey on keyboard

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

   Assignee|gwenview-bugs-n...@kde.org  |pinak.ah...@gmail.com
 CC||aspotas...@gmail.com
  Component|general |General
Product|gwenview|Baloo

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

[plasmashell] [Bug 365194] New: A mess with widget positions after connecting or disconnecting an external primary monitor

[via KDE Bugzilla]

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

Bug ID: 365194
   Summary: A mess with widget positions after connecting or
disconnecting an external primary monitor
   Product: plasmashell
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: z...@yandex.ru
CC: plasma-b...@kde.org

I have a laptop with built-in 1366x768 resolution screen and an external
monitor with 1280x1024 resolution (it is set as a primary display). A main
panel (the one with task manager and application manager) is placed vertically
at the right side of external monitor. Each time I plug the external monitor
out, main panel changes its position and moves to laptop screen (it is OK).
What is not OK is that it shifts down and is partially out of laptop screen
boundaries. If I plug monitor in again, things become even worse. Popup widgets
(I don't really know how to properly name them, I mean ones that appear on
clicking tray icons, for example, network manager or volume control) are
displayed at the top edge of the another monitor, KRunner widget is placed at a
wrong position too (and actually is invisible at all). After i log out and log
in again everything works fine both with a single- and a multi-monitor
configuration.

Reproducible: Always

Steps to Reproduce:
1. Log in with an primary external monitor connected
2. Disconnect the external monitor
3. See panel shifted
4. Connect the monitor again
5. See widgets displaced

Actual Results:  
Main panel shifted (see screenshot — http://imgur.com/ONksD80), popup widgets
are displayed on the wrong screen after clicking on a task icon (see screenshot
— http://imgur.com/gZuWXue), KRunner is not displayed at all (probably
displayed outside screen boundaries)

Expected Results:  
None of the above; widgets are in correct positions and usable

Here is an output of xrandr -q command with external monitor connected:

Screen 0: minimum 8 x 8, current 2646 x 1024, maximum 32767 x 32767
LVDS1 connected 1366x768+0+256 (normal left inverted right x axis y axis) 344mm
x 193mm
   1366x768  60.06*+
   1360x768  59.8059.96  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   680x384   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VGA1 connected primary 1280x1024+1366+0 (normal left inverted right x axis y
axis) 334mm x 270mm
   1280x1024 60.02 +  75.02*
   1024x768  75.0875.0360.00  
   800x600   75.0060.32  
   640x480   75.0060.00  
   720x400   70.08  
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

and here is an output without second monitor (when widgets are broken already):

Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis)
344mm x 193mm
   1366x768  60.06*+
   1360x768  59.8059.96  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   640x480   59.94  
   720x405   60.00  
   680x384   60.00  
   640x360   60.00  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

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

[Baloo] [Bug 360517] Gwenview crashes when using image viewer and navigating to next image with arrowkey on keyboard

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UNMAINTAINED

--- Comment #3 from Alexander Potashev  ---
Baloo 4.x is unmaintained. If the problem persists with digiKam-5.x and
Baloo-5.13 or newer, please file another bug report for product
"frameworks-baloo".

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

[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails

[via KDE Bugzilla]

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

--- Comment #5 from caulier.gil...@gmail.com ---
Mysql support is just an option to turn on at compilation time through cmake...
It's explained in README.

Gilles Caulier

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

[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145

[Bit Twister via KDE Bugzilla]

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

--- Comment #8 from Bit Twister  ---
(In reply to Sebastian Kügler from comment #6)
> That's not the Plasma version, but the Frameworks version. As I said, please
> run kinfocenter to find out.

Can not find any plasma version information in kinfocenter.

See kinfocenter screen shot attachment.

Quick launch of kde splash screen in comment 5, was a leftover/not dead yet
process from previous login.   :(

Guessing this will help
$ plasmashell --version
plasmashell 5.6.5

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

[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145

[Bit Twister via KDE Bugzilla]

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

--- Comment #7 from Bit Twister  ---
Created attachment 99922
  --> https://bugs.kde.org/attachment.cgi?id=99922=edit
kinfocenter screen shot

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

[KScreen] [Bug 365144] Plasma Panel shown in primary monitor and external too

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #12 from Sebastian Kügler  ---
As I mentioned in Comment#11, you're wasting everyone's time posting these
videos in this bugreport. File separate bugs.

What you're trying is unmanageable for us.

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

[kaddressbook] [Bug 365192] kaddressbook corrupts or discards information in it does not know (carddav)

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
I improved a lot vcard4 support in kf5
but perhaps it"s still not perfect.
could you provide some vcard4 file where info are discarded please ?
I will continue to improve it.

thanks

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

[KScreen] [Bug 365144] Plasma Panel shown in primary monitor and external too

[via KDE Bugzilla]

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

--- Comment #11 from rockonthemoo...@gmail.com ---
new video weirdness from the tube (with the newely created user)
https://youtu.be/n8APhqTcWLY

- primary screen setting is broken
- incorrect task manager menu popup placement https://youtu.be/giEwM9vyfNA
- fuzzy screen management widget positioning
- logout plasma screen always on external monitor, but with primary screen
resolution https://goo.gl/photos/6t37qiuvK88YWx2u5
- login screen misaligned in primary screen
https://goo.gl/photos/jgkpMKshsspSKvsA8

not related to window management:
- when cursor is hovering widows decoration, it loses Breeze theme, fallback to
X default.
FIX: change cursor theme to Breeze cold, than back to Breeze
- no transparency/blur in plasma Breeze theme
FIX: unchek "improve background contrast" in Kwin effects

the funny thing is that, after all that, I rebooted: result: primary screen
with Panel on external monitor, laptop screen black
https://goo.gl/photos/54kDGw4yJfNkn2nb8

Should I create a bug report for each one of these issues? 'Cuz, frankly, I
don't know where to start.

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

[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails

[Peter Bauer via KDE Bugzilla]

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

Peter Bauer  changed:

   What|Removed |Added

 CC||peter.m.ba...@gmail.com

--- Comment #4 from Peter Bauer  ---
digiKam 5.0.0 is per default compiled without the experimental MySQL support so
the migration is not possible anyway. It would be very helpful to have a
working migration to SQLite in version 4 so people can use Digikam with SQLite
until the rewritten MySQL support is ready.

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

[kaddressbook] [Bug 365193] New: vCard4 export must use RELATED field instead of custom X- field

[Erik Quaeghebeur via KDE Bugzilla]

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

Bug ID: 365193
   Summary: vCard4 export must use RELATED field instead of custom
X- field
   Product: kaddressbook
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@equaeghe.nospammail.net
CC: to...@kde.org

When exporting a contact to vCard4 with a spouse field, the file contains the
line

X-KADDRESSBOOK-X-SpousesName:testy toster

In vCard4, there is the RELATED field for such information (see
https://tools.ietf.org/html/rfc6350#section-6.6.6):

RELATED;TYPE=spouse;VALUE=text:testy toster

(The vcard4-implementation gives you the opportunity to do away with custom
fields entirely; given that addressbooks are commonly synced, such fields do
more harm than good.)

Reproducible: Always

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

[kaddressbook] [Bug 365192] New: kaddressbook corrupts or discards information in it does not know (carddav)

[Erik Quaeghebeur via KDE Bugzilla]

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

Bug ID: 365192
   Summary: kaddressbook corrupts or discards information in it
does not know (carddav)
   Product: kaddressbook
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@equaeghe.nospammail.net
CC: to...@kde.org

(Kontact 4.14.10)

When modifying an addressbook contact from a carddav resource that contains
fields that are not known to kaddressbook, these fields are silently discarded
or corrupted.

Example:
* IMPP and RELATED fields are discarded.
* fields with group syntax (e.g., item1.ADR or davdroid2.ABLABEL) get
corrupted, i.e., the group (e.g., item1 or davdroid2) and the period get lost
(and also item2.ADR gets thrown away entirely) and sometimes duplication of the
first part of the label name (until a dash) happens. Perhaps kadressbook does
not know the grouping syntax?

kaddressbook should never touch fields it does not know! Just keep them in the
vCard as-is.

Reproducible: Always

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

[kaddressbook] [Bug 365191] New: vCard4 must use LABEL ADR-parameter, not LABEL field

[Erik Quaeghebeur via KDE Bugzilla]

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

Bug ID: 365191
   Summary: vCard4 must use LABEL ADR-parameter, not LABEL field
   Product: kaddressbook
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@equaeghe.nospammail.net
CC: to...@kde.org

vCard4 export uses a LABEL field as in vCard, but it must use a LABEL parameter
to the corresponding ADR field: see
https://tools.ietf.org/html/rfc6350#section-6.3.1

Reproducible: Always

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

[kate] [Bug 362864] Kate does not save Sidebar state in configuration settings files

[Buovjaga via KDE Bugzilla]

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

Buovjaga  changed:

   What|Removed |Added

 CC||todven...@suomi24.fi

--- Comment #1 from Buovjaga  ---
I don't have this problem.

Arch Linux 64-bit
Kate 16.04.2
KDE Frameworks 5.23.0
Qt 5.7
xcb wm

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

[plasmashell] [Bug 365158] option to change font color in task manager

[Jens Reuterberg via KDE Bugzilla]

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

--- Comment #8 from Jens Reuterberg  ---
(In reply to Jens Reuterberg from comment #7)
> So after digging around I found that MX theme DO have a colour file, so it
> sets its own colours. Now in the colour file you can edit [colors:window]
> and ForegroundNormal to change colour theme of the taskmanager. With that
> parts of the theme change as well like the clock - but that you can change
> back by defining it in [colors:view]

Sry that doesnt set clock colour so I guess you have to use the same for all
those.

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

[KScreen] [Bug 365165] org.kde.KScreen kscreen.xcb.helper: Event Error: 145

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Resolution|UNMAINTAINED|WAITINGFORINFO

--- Comment #6 from Sebastian Kügler  ---
That's not the Plasma version, but the Frameworks version. As I said, please
run kinfocenter to find out.

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

[plasmashell] [Bug 365158] option to change font color in task manager

[Jens Reuterberg via KDE Bugzilla]

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

--- Comment #7 from Jens Reuterberg  ---
So after digging around I found that MX theme DO have a colour file, so it sets
its own colours. Now in the colour file you can edit [colors:window] and
ForegroundNormal to change colour theme of the taskmanager. With that parts of
the theme change as well like the clock - but that you can change back by
defining it in [colors:view]

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

[kate] [Bug 353404] My kate version is not listed in the possible versions.

[Sven Brauch via KDE Bugzilla]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #2 from Sven Brauch  ---
Yes, we should add these versions ... but it's quite a lot of versions, that
will be a problem again I guess.

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