[kdenlive] [Bug 365692] New: git master: titler "show background" works only on first edit

[Wegwerf via KDE Bugzilla]

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

Bug ID: 365692
   Summary: git master: titler "show background" works only on
first edit
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

The "show background" function of Kdenlive's titler currently works only the
first time in an Kdenlive session, that is editing a title. When editing the
same or a different title, show background doesn't work anymore and doesn't
show the background. Only restarting Kdenlive brings back showing the
background for exactly editing one other title. After closing the title editor,
show background doesn't work anymore.

System is Kubuntu 16.04 with recent updates, including kde-backports.

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

[digikam] [Bug 365691] New: Digikam freezes when using «tool» «slideshow»«presentation» and trying to add an image

[via KDE Bugzilla]

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

Bug ID: 365691
   Summary: Digikam freezes when using «tool»
«slideshow»«presentation» and trying to add an image
   Product: digikam
   Version: 5.0.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: SlideShow
  Assignee: digikam-de...@kde.org
  Reporter: philippe.quag...@laposte.net

Using the  «tool» «slideshow»«presentation», we get a new window to select the
images. If we press on the «+» button to add an image, Digikam completely
freeze. 

Reproducible: Always

Steps to Reproduce:
1. Select «tool» «slideshow»«presentation»
2. Press the «+» button
3.

Actual Results:  
Freeze

Expected Results:  
Continue working

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

[digikam] [Bug 294579] GROUP : grouped pictures are not processed together except the first one (Renaming, Tags, Metadata, Labels, etc.)

[via KDE Bugzilla]

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

--- Comment #8 from philippe.quag...@laposte.net ---
Yes, I guess it is still valid, the behaviour is still exactly the same.

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

[digikam] [Bug 331878] GROUP : the «grouped images icon» disapears when working on the main (front) image

[via KDE Bugzilla]

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

--- Comment #2 from philippe.quag...@laposte.net ---
Yes, I get the same problem with digikam 5.0.0, installed from Philips PPA

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

[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar

[Trevor Parsons via KDE Bugzilla]

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

Trevor Parsons  changed:

   What|Removed |Added

 CC||kdeb...@trevorparsons.com

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

[kdenlive] [Bug 365653] git master: title clip cannot be resized beyond its initial length

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #3 from Wegwerf  ---
Just gave it a try and this looks fine now. Jean-Baptiste, thank you very much
for quickly fixing this bug! Will make life for newcomers to Kdenlive 16.08
more smooth :)

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

[kdenlive] [Bug 365656] git master: timeline playhead doesn't extend vertically to full height

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #2 from Wegwerf  ---
Yes, this fixed the playhead cursor being way too short. Jean-Baptiste, thank
you very much for quickly fixing this!

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

[kexi] [Bug 365469] Error while creating table with field type that does not support UNSIGNED but has it set to TRUE

[Jarosław Staniek via KDE Bugzilla]

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

--- Comment #4 from Jarosław Staniek  ---
On Thursday, 14 July 2016, Juan José Morales via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:
> Comment # 3 on bug 365469 from Juan José Morales
>
> Thank you for your response.
> Im trying to involve in the project. I hope i can help improving the
product.
> For now Im learning Qt for help solving bugs and reporting bugs i found.
>

Thanks Juan, that's good news! Have you tried to compile Kexi 3?
Regardless of programming skills bug and wish reporting is welcome. We are
also planning to have distribution-independent Kexi releases.

Cheers.

> Greetings
>
> 
> You are receiving this mail because:
>
> You are on the CC list for the bug.
> You are watching someone on the CC list of the bug.

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

[plasmashell] [Bug 365569] After update to KF5.24 systemtray is missing its icons (and functionalities)

[via KDE Bugzilla]

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

--- Comment #7 from slartibar...@gmail.com ---
just to add my config:
fedora23, qt 5.6.1

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

[konsole] [Bug 303129] Terminus does not look normal in konsole

[Dmitry Bigunyak via KDE Bugzilla]

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

--- Comment #11 from Dmitry Bigunyak  ---
The worst thing is that another bug
(https://bugs.kde.org/show_bug.cgi?id=349350) doesn't allow us to choose other
good monospace fonts in konsole.

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

[Breeze] [Bug 365690] New: kaccessibleapp icon

[via KDE Bugzilla]

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

Bug ID: 365690
   Summary: kaccessibleapp icon
   Product: Breeze
   Version: 5.6.5
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: john.k...@vfemail.net

Dear Developer,

The kaccessibleapp icon on a default panel (36 size) is bigger than blue
underlining of a status & notifications menu.

There is also i think probably  a bug with the panel size. When installed on a
new system it is smaller than a new default panel which size is 36.

Also when changing fonts DPI to a higher value (HiDPI)  the panel size doesn't
change.
The QT_AUTO_SCREEN_SCALE_FACTOR environment variable is set to 1.

Best wishes,
John 

Reproducible: Always

Steps to Reproduce:
I think it is clear from "Details". 

Actual Results:  
Written in "Details" 

Expected Results:  
The icon is smaller. 
The panel size is the same. The panel changes with DPI. 

Thank you.

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

[digikam] [Bug 338050] MYSQL : nested set fields not updating when moving tag within hierarchy [patch]

[via KDE Bugzilla]

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

--- Comment #9 from swatilodh...@gmail.com ---
Created attachment 100102
  --> https://bugs.kde.org/attachment.cgi?id=100102=edit
Please test with this patch.

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

[digikam] [Bug 338050] MYSQL : nested set fields not updating when moving tag within hierarchy [patch]

[via KDE Bugzilla]

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

swatilodh...@gmail.com changed:

   What|Removed |Added

 Attachment #100043|0   |1
is obsolete||

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

[digikam] [Bug 338050] MYSQL : nested set fields not updating when moving tag within hierarchy [patch]

[via KDE Bugzilla]

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

swatilodh...@gmail.com changed:

   What|Removed |Added

 Attachment #100063|0   |1
is obsolete||

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

[Breeze] [Bug 365689] KRDC missing icon

[Soukyuu via KDE Bugzilla]

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

Soukyuu  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

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

[Breeze] [Bug 365689] New: KRDC missing icon

[Soukyuu via KDE Bugzilla]

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

Bug ID: 365689
   Summary: KRDC missing icon
   Product: Breeze
   Version: 5.7.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: chrno-sphe...@hotmail.com
CC: kain...@gmail.com

Since updating from 5.6, KRDC has no icon, neither the small one in the upper
left corner of the window, nor on the icon-only task manager. The pinned
launcher shows the default file icon when KRDC is not launched

Reproducible: Always

Steps to Reproduce:
1. update to 5.7.0/5.7.1
2. observe KRDC icon going missing

Actual Results:  
default file icon on pinned launcher
no icon when KRDC is running

Expected Results:  
KRDC icon being visible

Running arch linux x64, up-to-date as of an hour ago. I can't seem to find the
icon in /usr/share/icons/breeze/, so maybe it got dropped by mistake?

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

[frameworks-kio] [Bug 365356] KIO supports WebDAV, but doesn't accept the dav:// URL scheme (Nautilus syntax)

[anewuser via KDE Bugzilla]

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

--- Comment #3 from anewuser  ---
I installed Nautilus and verified that it doesn't support the KIO syntax
either. Here's the report: https://bugzilla.gnome.org/show_bug.cgi?id=768814

Cryptomator doesn't require you to register an account. It's an offline tool
that creates encrypted directories/vaults and uses webDAV locally as a bridge
to let you explore those vaults as normal folders.

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

[digikam] [Bug 328577] Crash when edition with auto adjust in batch manager

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #8 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 333555] Digikam crashed while exporting photos

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #5 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[Active] [Bug 365688] New: Roku1 8882.8598.46 Roku Tech Support Number

[minda via KDE Bugzilla]

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

Bug ID: 365688
   Summary: Roku1 8882.8598.46 Roku Tech Support Number
   Product: Active
   Version: unspecified
  Platform: Android
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Contour activity screen
  Assignee: notm...@gmail.com
  Reporter: anna.rasca...@gmail.com
CC: act...@kde.org

Roku1 888 285 9846 Roku Tech Support Number
roku customer service 1-888-285-9846 roku tech support 1-888-285-9846 roku
phone number 1-888-285-9846 roku technical support 1-888-285-9846 roku customer
service number 1-888-285-9846 roku service 1-888-285-9846 roku customer support
1-888-285-9846 roku helpline 1-888-285-9846 roku support phone number
1-888-285-9846 roku help 1-888-285-9846 roku 3 support 1-888-285-9846 roku
troubleshooting 1-888-285-9846 roku contact 1-888-285-9846 roku customer
service phone number 1-888-285-9846 roku help number 1-888-285-9846 contact
roku customer service 1-888-285-9846 roku services 1-888-285-9846 roku
telephone number 1-888-285-9846 roku contact number 1-888-285-9846 phone number
for roku 1-888-285-9846 roku help phone number 1-888-285-9846 contact roku
1-888-285-9846 roku customer service telephone number 1-888-285-9846 call roku
1-888-285-9846 call roku customer service 1-888-285-9846 roku 800 number
1-888-285-9846 support.roku 1-888-285-9846 support.roku.com 1-888-285-9846 roku
3 customer service 1-888-285-9846

Reproducible: Always

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

[digikam] [Bug 238527] russian tags wrong after batch recompression

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #19 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[abakus] [Bug 365687] New: Norton customer(((1.8.8.8.2.8.5.9.8.4.6))))Norton Support Phone number, Norton customer support phone number

[minda via KDE Bugzilla]

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

Bug ID: 365687
   Summary: Norton customer(((1.8.8.8.2.8.5.9.8.4.6Norton
Support Phone number, Norton customer support phone
number
   Product: abakus
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k.h...@gmx.de
  Reporter: anna.rasca...@gmail.com

Norton customer(((1.8.8.8.2.8.5.9.8.4.6Norton Support Phone number, Norton
customer support phone number
+¥¥™Uk+(((1-888-240-9846@Norton Support Phone number,1-888-240-9846 Norton
customer support phone number 1-888-240-9846Norton customer care phone
number1-888-240-9846call )(((1+888-240-9846 )))@./Norton contact number, Norton
phone number, Norton telephone number telephone number for Norton online
support,Norton official support number,Norton official number,Norton official
phone number,phone number for Norton supportNorton 24/7 support phone
numberNorton support number,Norton telephone number for support

. Norton phone number,(1-888-240-9846)// Norton customer care
number. Norton Toll Free, Intuit@(1-888.240-9846)@-: Norton Technical
Support Number, Norton help desk phone number vides online solution for all
USA/CANADA clients. For any help of query call 1 888 240 9846 to get all Norton
account solution. For any help of query call 1 888 240 9846 to get all Norton
account solution. @@Call, 1-888-240-9846 for all type help by Norton support
telephone number,Norton support phone number,Norton support phone number,Norton
help phone number, Norton technical support number.Norton support number,
Norton phone number, Norton tech support number, Norton customer support
number, Norton customer support phone number, Norton customer service phone
number, Norton customer service phone number, Norton support phone number
Norton help number-Norton Helpline Number; Norton help phone number-Norton
Helpline Number, Norton Tech Support Toll free Number, Norton Support Telephone
Number, Norton Tech Support Telephone number, Norton Tech Support contact
number, Norton support contact number, Norton technical support contact number,
Norton help desk phone number. Call, @(1-888-240-9846)@-: It is very popular
toll free number which vide by Norton technical support, Norton Customer
Service Phone Number, Norton Customer Service Number, Norton Customer Support
Phone Number, Norton Customer Support Number, Norton Customer Service Helpline
Number, Norton Customer Care Number, Norton support team phone number.
Call,@(1-888-240-9846)@-: Norton help number-Norton Helpline Number; Norton
help phone number, Norton Helpline Number, Norton Tech Support Toll free
Number, Norton Support Telephone Number, Norton Tech Support Telephone number,
Norton Tech Support contact number, Norton support contact number, Norton
technical support contact number, Norton support phone number, Norton support
phone number. Norton customer support phone number for all type help by Norton
support telephone number, Norton help phone number, Norton technical support
number.Norton support number, Norton phone number, Norton tech support number,
Norton customer support number, Norton customer support phone number, Norton
customer service phone number, Norton customer service phone number call (1 888
240 9846) to get all Norton account solution. @@Call,1-888-240-9846 for all
type help by Norton support telephone number,Norton support phone number,Norton
support phone number,Norton help phone number, Norton technical support
number.Norton support number, Norton phone number, Norton tech support number,
Norton customer support number, Norton customer support phone number, Norton
customer service phone number, Norton customer service phone number, Norton
support phone number Norton help number-Norton Helpline Number; Norton help
phone number-Norton Helpline Number, Norton Tech Support Toll free Number,
Norton Support Telephone Number, Norton Tech Support Telephone number, Norton
Tech Support contact number, Norton support contact number, Norton technical
support contact number, Norton help desk phone number. Call,
@(1-888-240-9846)@-: It is very popular toll free number which vide by Norton
technical support, Norton Customer Service Phone Number, Norton Customer
Service Number, Norton Customer Support Phone Number, Norton Customer Support
Number, Norton Customer Service Helpline Number, Norton Customer Care Number,
Norton support team phone number. Call,@(1-888-240-9846)@-: Norton help
number-Norton Helpline Number; Norton help phone number, Norton Helpline
Number, Norton Tech Support Toll free Number, Norton Support Telephone Number,
Norton Tech Support Telephone number, Norton Tech Support contact number,
Norton support contact number, Norton technical support contact number, Norton
support phone number, 

[digikam] [Bug 245678] Pick correct date from selected pictures when creating a new album

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #10 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 162809] Bad names chosen in rename dialog at copy operations when duplicate files are found

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #6 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

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

[Olli Lupton via KDE Bugzilla]

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

--- Comment #1 from Olli Lupton  ---
Two further comments:

1. The operation does seem to succeed (i.e. the tag is removed), despite the
crash.
2. I see a similar crash if, in the tag manager, I try and move a tag (e.g.
SomeName -> People/SomeName).

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

[digikam] [Bug 241799] Digikam: marked images makes scrolling slow

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #9 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 196627] Right-click context menu for the Albums GUI

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WONTFIX

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

[digikam] [Bug 239938] Tags view doesn't show all images with that tag

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #12 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[konsole] [Bug 303129] Terminus does not look normal in konsole

[Dmitry Bigunyak via KDE Bugzilla]

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

--- Comment #10 from Dmitry Bigunyak  ---
Created attachment 100101
  --> https://bugs.kde.org/attachment.cgi?id=100101=edit
kate-terminus.jpeg

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

[digikam] [Bug 218007] when "creating a new album" from a selection of images, digikam should try to *move* them first

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WONTFIX

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

[konsole] [Bug 303129] Terminus does not look normal in konsole

[Dmitry Bigunyak via KDE Bugzilla]

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

--- Comment #9 from Dmitry Bigunyak  ---
Created attachment 100100
  --> https://bugs.kde.org/attachment.cgi?id=100100=edit
xterm-terminus.jpeg

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

[kwin] [Bug 310005] Cannot tile windows horizontally (to the top or bottom)

[Kevin Cox via KDE Bugzilla]

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

--- Comment #30 from Kevin Cox  ---
That would seem less common especially for horizontal languages but I imagine
there may be some use cases for vertical languages.

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

[konsole] [Bug 303129] Terminus does not look normal in konsole

[Dmitry Bigunyak via KDE Bugzilla]

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

--- Comment #8 from Dmitry Bigunyak  ---
Created attachment 100099
  --> https://bugs.kde.org/attachment.cgi?id=100099=edit
konsole-terminus.jpeg

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

[digikam] [Bug 152615] changing viewport of Album when opening panels

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #8 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[kwin] [Bug 310005] Cannot tile windows horizontally (to the top or bottom)

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #29 from Simone Gaiarin  ---
Yes that's a good point. Still the behavior proposed for the portrait mode will
not affect this use case in landscape, and I doubt someone wants to tile
left/right in portrait, having the window be two long stripes (I may be wrong).

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

[konsole] [Bug 303129] Terminus does not look normal in konsole

[Dmitry Bigunyak via KDE Bugzilla]

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

Dmitry Bigunyak  changed:

   What|Removed |Added

 CC||ices...@inbox.ru

--- Comment #7 from Dmitry Bigunyak  ---
I have exactly the same problem and this is a shame the bug has been ignored
for such a long time.
I use KDE-4 (4.14.20), konsole-2.14.2, Qt-4.8.6 on my Gentoo system with locale
set to "en_US.UTF-8".
The strange thing is that the problem occurs only in konsole (see attachment
konsole-terminus.jpeg) , when I use Terminus font (same size 12) in xterm
(xterm-terminus.jpeg) or kate (kate-terminus.jpeg) it looks normal.
There is a related bug report to Qt project as well:
https://bugreports.qt.io/browse/QTBUG-22599

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

[valgrind] [Bug 365686] New: Process terminating with default action of signal 4 (SIGILL): dumping core

[via KDE Bugzilla]

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

Bug ID: 365686
   Summary: Process terminating with default action of signal 4
(SIGILL): dumping core
   Product: valgrind
   Version: 3.11.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: rudici.caz...@litepoint.com

After compiling a fresh version of valgrind 3.11.0 and running memcheck against
an application, I noticed the "Process terminating with default action of
signal 4 (SIGILL): dumping core" error.


Also, related or not, one thing to keep in mind is my configuration.
"./configure --target=arm-none-linux-gnueabi --host=arm-linux-gnueabi
--prefix=/usr/sbin/valgrind CFLAGS=-static". 
That is the only configuration that seems to work.
However, --host should be set to something different because the machine used
for cross-compiling is not an arm-processor. The problem is, if i change my
configuration to 
"./configure --target=arm-none-linux-gnueabi --prefix=/usr/sbin CFLAGS=-static
--host=x86_64-unknown-linux-gnu", it does not compile.
So, the questin is what should --host be set to?

Upon response, I will attach the entire debug output

Reproducible: Always

Steps to Reproduce:
1.configure valgrind 3.11.0 
2. compile
3. run valgrind against the app

Actual Results:  
==1286== Memcheck, a memory error detector
==1286== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1286== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==1286== Command: ./ltel1
==1286== 
--1286-- Valgrind options:
--1286---v
--1286-- Contents of /proc/version:
--1286--   Linux version 3.0.51-rt75 (litepoint@rcazeao-o9020ub) (gcc version
4.5.1 (Sourcery G++ Lite 2010.09-5
0) ) #2 SMP PREEMPT RT Wed May 25 14:41:22 PDT 2016
--1286-- 
--1286-- Arch and hwcaps: ARM, LittleEndian, ARMv7
--1286-- Page sizes: currently 4096, max supported 4096
--1286-- Valgrind library directory: /usr/sbin/valgrind/lib/valgrind
--1286-- Reading syms from /armlp/lte/fdd/phy/ltel1
--1286-- warning: DiCfSI 0x0 .. 0x3 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x13 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x13 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x2f outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1286-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1286-- Reading syms from /lib/ld-2.11.1.so
--1286-- Reading syms from /usr/sbin/valgrind/lib/valgrind/memcheck-arm-linux
--1286--object doesn't have a dynamic symbol table
--1286-- Scheduler: using generic scheduler lock implementation.
--1286-- Reading suppressions file:
/usr/sbin/valgrind/lib/valgrind/default.supp
==1286== embedded gdbserver: reading from
/tmp/vgdb-pipe-from-vgdb-to-1286-by-root-on-???
==1286== embedded gdbserver: writing to  
/tmp/vgdb-pipe-to-vgdb-from-1286-by-root-on-???
==1286== embedded gdbserver: shared mem  
/tmp/vgdb-pipe-shared-mem-vgdb-1286-by-root-on-???
==1286== 
==1286== TO CONTROL THIS PROCESS USING vgdb (which you probably
==1286== don't want to do, unless you know exactly what you're doing,
==1286== or are doing some strange experiment):
==1286==   /usr/sbin/valgrind/lib/valgrind/../../bin/vgdb --pid=1286
...command...
==1286== 
==1286== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==1286==   /path/to/gdb ./ltel1
==1286== and then give GDB the following command
==1286==   target remote | /usr/sbin/valgrind/lib/valgrind/../../bin/vgdb
--pid=1286
==1286== --pid is optional if only one valgrind process is running
==1286== 
==1286== 
==1286== Process terminating with default action of signal 4 (SIGILL): dumping
core
==1286==  Illegal opcode at address 0x38086EB4
==1286==at 0x40007A0: ??? (in /lib/ld-2.11.1.so)
==1286== 
==1286== HEAP SUMMARY:
==1286== in use at exit: 0 bytes in 0 blocks
==1286==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1286== 
==1286== All heap blocks were freed -- no leaks are possible
==1286== 
==1286== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==1286== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction

Expected Results:  
No errors dealing with 
"Process terminating with default action of signal 4 (SIGILL): dumping core"

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

[digikam] [Bug 195891] failed when using "Date-based sub-albums"

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 141940] Image selection bugs (multiple and single selections)

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #24 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 156187] Show album name and comments even when empty

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #4 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[kwin] [Bug 365685] New: "keep below" windows dive below plasmashell (sometimes)

[via KDE Bugzilla]

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

Bug ID: 365685
   Summary: "keep below" windows dive below plasmashell
(sometimes)
   Product: kwin
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ensla...@protonmail.com

Ticking "keep below" moves a window under plasmashell SOMETIMES!
Sure, it doesn't say below what, but i assume it's below other open windows?!
It's not only kde specific apps, but any application with
Qt.WindowStaysOnBottomHint/Qt::WindowStaysOnBottomHint flag.
I can't tell if it's kwin/plasmashell/intel/gl or wayland bug, sorry if this is
the wrong place for this bug.

software versions:
up to date fedora 23
kwin 5.6.5

* happens with/without effects enabled.
* happens on all engines (raster,egl,glx).
* happens on both, kwin & kwin_x11 wrapper



Reproducible: Sometimes

Steps to Reproduce:
1. make a quick qt/qml app with "Qt.WindowStaysOnBottomHint" in it
or
1. open dolphin, tick "keep below" on it's titlebar
2. click somewhere on plasmashell, click back to application's titlebar
3. repeat...



Actual Results:  
"keep below" marked window dives below plasmashell sometimes

Expected Results:  
"keep below" marked window should always be above plasmashell

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

[kwin] [Bug 310005] Cannot tile windows horizontally (to the top or bottom)

[Kevin Cox via KDE Bugzilla]

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

--- Comment #28 from Kevin Cox  ---
@Simone you might be right about the common case but I often want to tile
horizontally on a landscape display. One common use case for me is two
terminals that have long lines but I only need to monitor the last couple.

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

[digikam] [Bug 346433] There are no thumb previews anymore- worst case scenario

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #7 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 262646] I can NOT copy pics _from_ DK _to_ some directory - DK-integration questioned?

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In|5.0.0   |5.1.0

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

[digikam] [Bug 319892] cannot delete selected files in album view

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #9 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 262646] I can NOT copy pics _from_ DK _to_ some directory - DK-integration questioned?

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.0.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #11 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 291309] Album content not updated when deleting next album

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #7 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[kwin] [Bug 310005] Cannot tile windows horizontally (to the top or bottom)

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #27 from Simone Gaiarin  ---
Another idea regarding the placement by touching the edge would be to make the
window expand to the upper half  of the screen when  the upper edge is touched
only when the screen is in portrait mode. And possibly use the right or left
edge to maximize the window.

I guess that tile to top and bottom would be not so common in landscape mode
and the same for left/right in portrait.

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

[digikam] [Bug 299524] Applying settings to multiple selected files makes changes to the wrong files

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #4 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 299957] Shift-selecting images in the album GUI exhibits glitches

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #10 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 275607] Wish: Decoration for more pictures

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID

--- Comment #4 from caulier.gil...@gmail.com ---
No response... Closed

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

[digikam] [Bug 287471] albums context doesn't refresh after moving files

[via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.1.0

--- Comment #9 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 182534] digiKam does not remember its location with session management

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #16 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

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

[Olli Lupton via KDE Bugzilla]

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

Bug ID: 365684
   Summary: Crash when deleting a tag from the list of tags
   Product: digikam
   Version: 5.0.0
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: digikam.2759c...@olupton.com

Digikam consistently crashes if I remove (right click, "Delete Tag") a tag in
the tag manager (2nd tab, left hand side of screen). This happens regardless of
whether or not the tag is applied to any images.



Reproducible: Always

Steps to Reproduce:
1. Install
http://download.kde.org/stable/digikam/digiKam-5.0.0-MacOS-x86-64.pkg
2. Go to tag manager (2nd tab on left hand side of screen)
3. Right click on a tag and click "Delete Tag"

Actual Results:  
Crash.

Expected Results:  
Tag should be removed from all files it is applied to, and the tag should be
removed from the list.

Process:   digikam [47097]
Path:  /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Identifier:digikam
Version:   5.0.0 (5.0.0)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   digikam [47097]
User ID:   501

Date/Time: 2016-07-14 12:34:46.147 -0400
OS Version:Mac OS X 10.11.4 (15E65)
Report Version:11
Anonymous UUID:583E6AEC-FDCB-24D8-BCA5-AE7A115F5214

Sleep/Wake UUID:   7E6C8FA9-F1AA-4223-B792-0CF9182515E1

Time Awake Since Boot: 26 seconds
Time Since Wake:   15000 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   EXC_I386_GPFLT
Exception Note:EXC_CORPSE_NOTIFY

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtCore 0x00010b292042
QSortFilterProxyModel::parent(QModelIndex const&) const + 82
1   org.qt-project.QtWidgets  0x00010a70b9c7
QTreeView::isIndexHidden(QModelIndex const&) const + 71
2   org.qt-project.QtWidgets  0x00010a6fff31
QTreeView::visualRect(QModelIndex const&) const + 97
3   org.qt-project.QtWidgets  0x00010a6a78fc
QAccessibleTableCell::rect() const + 44
4   org.qt-project.QtWidgets  0x00010a6a76b9
QAccessibleTableCell::state() const + 169
5   libqcocoa.dylib   0x000114d4c6ca
QCocoaAccessible::hasValueAttribute(QAccessibleInterface*) + 58
6   libqcocoa.dylib   0x000114d48e3f
-[QMacAccessibilityElement accessibilityAttributeNames] + 431
7   com.apple.AppKit  0x7fff945d6e1a
NSAccessibilityEntryPointAttributeNames + 124
8   com.apple.AppKit  0x7fff94845552
-[NSObject(NSAccessibilityInternal) _accessibilityAttributeNamesClientError:] +
56
9   com.apple.AppKit  0x7fff94848976 CopyAttributeNames +
216
10  com.apple.HIServices  0x7fff90d2923b
_AXXMIGCopyAttributeNames + 245
11  com.apple.HIServices  0x7fff90d32823 _XCopyAttributeNames +
367
12  com.apple.HIServices  0x7fff90d0d012 mshMIGPerform + 199
13  com.apple.CoreFoundation  0x7fff90588019
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41
14  com.apple.CoreFoundation  0x7fff90587f89 __CFRunLoopDoSource1 +
473
15  com.apple.CoreFoundation  0x7fff9057f9bb __CFRunLoopRun + 2171
16  com.apple.CoreFoundation  0x7fff9057eed8 CFRunLoopRunSpecific +
296
17  com.apple.HIToolbox   0x7fff80b2c935
RunCurrentEventLoopInMode + 235
18  com.apple.HIToolbox   0x7fff80b2c76f ReceiveNextEventCommon
+ 432
19  com.apple.HIToolbox   0x7fff80b2c5af
_BlockUntilNextEventMatchingListInModeWithFilter + 71
20  com.apple.AppKit  0x7fff94411efa _DPSNextEvent + 1067
21  com.apple.AppKit  0x7fff9441132a -[NSApplication
_nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
22  com.apple.AppKit  0x7fff94405e84 -[NSApplication run] +
682
23  libqcocoa.dylib   0x000114d3734f
QCocoaEventDispatcher::processEvents(QFlags) +
2191
24  org.qt-project.QtCore 0x00010b2bf3d1
QEventLoop::exec(QFlags) + 417
25  org.qt-project.QtCore 0x00010b2c3885
QCoreApplication::exec() + 341
26  digikam   0x0001044de1dc main + 9084
27  libdyld.dylib 0x7fff874ca5ad start + 1

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib0x7fff81511efa kevent_qos + 10
1   libdispatch.dylib 0x7fff8e769165 _dispatch_mgr_invoke +
216
2   libdispatch.dylib 0x7fff8e768dcd _dispatch_mgr_thread +
52

[kexi] [Bug 365469] Error while creating table with field type that does not support UNSIGNED but has it set to TRUE

[Juan José Morales via KDE Bugzilla]

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

--- Comment #3 from Juan José Morales  ---
Thank you for your response.
Im trying to involve in the project. I hope  i can help improving the product.
For now Im learning Qt for help solving bugs and reporting bugs i found.

Greetings

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

[digikam] [Bug 361336] moving thumb to other album does not delete original after copy (drag + drop)

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[digikam] [Bug 346321] Crash when I add new Key words and confirm the completed Keyword by Pressing "Enter"

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|BACKTRACE   |FIXED

--- Comment #4 from caulier.gil...@gmail.com ---
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[Breeze] [Bug 364426] Right margin too small in KPageDialog

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[Breeze] [Bug 364849] Tooltip Text in several qt apps such as Amarok and Krusader is unreadable (white on white) with the Breeze/Breeze Dark color schemes

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC||hugo.pereira.da.costa@gmail
   ||.com

--- Comment #2 from Hugo Pereira Da Costa  ---
Can you post a screenshot ? 
Here it looks just fine: 
http://wstaw.org/m/2016/07/14/plasma-desktopmp8175.png

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

[digikam] [Bug 332969] EXCEPTION_ACCESS_VIOLATION while going through raw pictures

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.1.0
 Resolution|BACKTRACE   |FIXED

--- Comment #8 from caulier.gil...@gmail.com ---
With digiKam 5.0.0 Windows installer, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

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

[kwin] [Bug 310005] Cannot tile windows horizontally (to the top or bottom)

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||lucas.hartm...@gmail.com

--- Comment #26 from Thomas Lübking  ---
*** Bug 365681 has been marked as a duplicate of this bug. ***

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

[gwenview] [Bug 365683] Strange sorting in gwenview

[Michal Svec via KDE Bugzilla]

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

--- Comment #1 from Michal Svec  ---
Created attachment 100098
  --> https://bugs.kde.org/attachment.cgi?id=100098=edit
screenshot

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

[Breeze] [Bug 365318] KRDC is unreadable under breeze dark theme

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC||hugo.pereira.da.costa@gmail
   ||.com

--- Comment #13 from Hugo Pereira Da Costa  ---
Hi, Chiming in.
>From the screenshots of k3b, ktorrent and okular, it does seem that Qt is set
to use the QT-Gtk theme (which converts a gtk theme into a Qt theme), and then
gtk set to use breeze (breeze-dark ?).
This configuration is not supported. 

I would recommand try to set the Qt theme to use breeze directly (and
breeze-dark as a color theme). this should make (e.g.) okular, look like this: 

http://wstaw.org/m/2016/07/14/plasma-desktopDS8175.png

Which is fine

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

[gwenview] [Bug 365683] Strange sorting in gwenview

[Michal Svec via KDE Bugzilla]

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

--- Comment #2 from Michal Svec  ---
The version is: gwenview-4.14.3-4.3.x86_64

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

[kwin] [Bug 365681] Edge Snapping/Tiling Actions on Vertical Displays

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
s/"full screen"/"maximized"/  - they're not the same concept.

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

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

[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username

[Jakub Schmidtke via KDE Bugzilla]

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

Jakub Schmidtke  changed:

   What|Removed |Added

 CC||sja...@gmail.com

--- Comment #63 from Jakub Schmidtke  ---
I am trying to login on forum.kde.org and it tells me my password is wrong.
When I try to recover it, it takes me to identity.kde.org. Which requires a
username,
and no way to recover it. Which is absolutely ridiculous!
And when I try register (I thought maybe I didn't actually use the forum in the
past)
 it tells me that my e-mail is taken.

So:
1. I can't create a new account, because my e-mail is already used.
2. I cannot login without knowing the username and the password
3. I need the username to recover the password,
4. There is no way to recover the username!

Out of curiosity, who designed this system?

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

[gwenview] [Bug 365683] New: Strange sorting in gwenview

[Michal Svec via KDE Bugzilla]

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

Bug ID: 365683
   Summary: Strange sorting in gwenview
   Product: gwenview
   Version: 4.13.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: re...@atrey.karlin.mff.cuni.cz
CC: myr...@kde.org

For some reason the directories are sorted in a weird way-- "2015something" is
sorted
between "000something" and "2001something", see attached screenshot. Naturally
it
should be the last one (I am using sorting by name).

Elsewhere (eg. dolphin, midnight commander, etc) it works fine.

Reproducible: Always

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

[Breeze] [Bug 365628] SH_Widget_Animate is true despite animations being disabled

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/oxyg
   ||en/a1573b1756fab439c50df0f0
   ||ab060899bf568dfd
 Resolution|--- |FIXED

--- Comment #4 from Hugo Pereira Da Costa  ---
Git commit a1573b1756fab439c50df0f0ab060899bf568dfd by Hugo Pereira Da Costa.
Committed on 14/07/2016 at 16:22.
Pushed by hpereiradacosta into branch 'Plasma/5.7'.

sync SH_Widget_Animate with internal "enable animations" option

M  +1-0kstyle/oxygenstyle.cpp

http://commits.kde.org/oxygen/a1573b1756fab439c50df0f0ab060899bf568dfd

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

[Breeze] [Bug 365628] SH_Widget_Animate is true despite animations being disabled

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #3 from Hugo Pereira Da Costa  ---
Fixed with rBREEZE2b61ea484d05

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

[plasmashell] [Bug 365682] New: Plasma crashes while searching in Application Launcher

[via KDE Bugzilla]

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

Bug ID: 365682
   Summary: Plasma crashes while searching in Application Launcher
   Product: plasmashell
   Version: 5.6.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: aschm...@graphtek.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.5)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
(also, if you click "suggest this is related" nothing happens, and if you close
the window it complains that you haven't suggested anything is related -- this
has been true throughout the life of Fedora 23 and continues to be true in
Fedora 24).

This has been true throughout the life of Fedora 23, and continues to be true
in Fedora 24.

It doesn't crash every time, but it will always pause for about 10 seconds
while it thinks about crashing.

The crash can be reproduced sometimes.

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

Thread 17 (Thread 0x7fbe67fff700 (LWP 29755)):
#0  0x7fbf60dbdbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbf6266a01a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fbe9e3078c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fbe9e30ba68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fbe9e306a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fbe9e30bac2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7fbe9e306a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fbe9e309909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fbf6266999a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fbf60db85ca in start_thread () at /lib64/libpthread.so.0
#10 0x7fbf61a5cead in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fbe7c99a700 (LWP 29754)):
#0  0x7fbf60dbdbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbf6266a01a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7fbe9e3078c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7fbe9e30ba68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7fbe9e306a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fbe9e30bac2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7fbe9e306a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fbe9e30bac2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#8  0x7fbe9e306a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#9  0x7fbe9e30bac2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#10 0x7fbe9e306a3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#11 0x7fbe9e309909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#12 0x7fbf6266999a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#13 0x7fbf60db85ca in start_thread () at /lib64/libpthread.so.0
#14 0x7fbf61a5cead in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fbe7d19b700 (LWP 29753)):
[KCrash Handler]
#6  0x7fbe88149eba in mdb_txn_renew0 () at /lib64/liblmdb.so.0.0.0
#7  0x7fbe8814b2dc in mdb_txn_begin () at /lib64/liblmdb.so.0.0.0
#8  0x7fbe887e32f0 in Baloo::SearchStore::exec(Baloo::Term const&, unsigned
int, int, bool) () at /lib64/libKF5Baloo.so.5
#9  0x7fbe887d1aff in Baloo::Query::exec() () at /lib64/libKF5Baloo.so.5
#10 0x7fbe88a2f490 in SearchRunner::match(Plasma::RunnerContext&, QString
const&, QString const&) () at
/usr/lib64/qt5/plugins/krunner_baloosearchrunner.so
#11 

[kwin] [Bug 365681] New: Edge Snapping/Tiling Actions on Vertical Displays

[Lucas Vinicius Hartmann via KDE Bugzilla]

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

Bug ID: 365681
   Summary: Edge Snapping/Tiling Actions on Vertical Displays
   Product: kwin
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lucas.hartm...@gmail.com

Vertical displays are useful for document reading usually, but not always, as a
secondary display. The current snapping/tiling is targeted solely at the more
common horizontal displays, and does not apply well to vertical orientation.

Current behavior when you drag a window to ___ is to tile it at ___:
- Top edge => Full Screen
- Left edge => Left half of screen
- Right edge => Right half of screen


Reproducible: Always

Steps to Reproduce:
1. Grab and drag a window either by the title bar or by Alt+Click.
2. Drag it to an edges of the display.

Actual Results:  
Window tiles (fills) part of the screen:
Top edge => Full screen
Center of left/right edges => left/right half screen
Top/bottom of left/right edges => quarter screen
Bottom edge => does nothing.

Expected Results:  
Dependent on display orientation.

Horizontal display should stay the same, except maybe:
Bottom edge => minimize? (would feel weird if the menu were somewhere else,
though...)

Vertical display: remove left/right halves, add top/bottom halves. Maybe
something like:
top/bottom edges => top/bottom halves of the screen
center of left/right edges => Full screen
top/bottom part of left/right edges => quarter screen.

While this is a purely cosmetic change I believe it would make vertical
displays a little more productive. The current left/right half tiling creates
pretty much useless "stripes" (3 pages of unreadable  PDFs) in my current
setup. Also placing windows in top/bottom halves requires me to place them in
quarter-screen then resize, and takes some time that could be saved.

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

[Breeze] [Bug 365628] SH_Widget_Animate is true despite animations being disabled

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #2 from Hugo Pereira Da Costa  ---
oh
but then I noticed that the ugly combobox is gone for KF5 ! 
ok. I'll make the switch then.

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

[plasmashell] [Bug 360544] Copy or cut item from desktop containment does not work by keyboard shortcut

[via KDE Bugzilla]

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

leh...@tutanota.com changed:

   What|Removed |Added

 CC||leh...@tutanota.com

--- Comment #6 from leh...@tutanota.com ---
I'm still having the problem on Kubuntu 16.04  with Plasma 5.5.5.

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

[Breeze] [Bug 365628] SH_Widget_Animate is true despite animations being disabled

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC||hugo.pereira.da.costa@gmail
   ||.com

--- Comment #1 from Hugo Pereira Da Costa  ---
Hi Christoph
this ... is complicated. 
right now breeze (and oxygen) style return the value from parent kstyle, which
in turn reads: 
KConfigGroup g(KSharedConfig::openConfig(), "KDE-Global GUI Settings");
return g.readEntry("GraphicEffectsLevel", true);

This option is defined in the fine tuning kcm, is a combobox with many choices,
such as "low display resolution and high cpu", "low display resolution and very
high cpu", "high display resolution and low cpu", etc. 

Based on this code, only the first combobox entry (low resolution low cpu)
disable SH_Widget_Animate

So I can either: 
1/ overwrite this in oxygen and breeze and use their own "disable animations"
flag; 
2/ Or remove the disable animations option and rely on this combobox instead.
3/ leave it as it is now.

To be honest, I would vote for 1/ (which you suggest) or 3/ (as it is now)
because I am really not happy about this fine tuning combobox.

Personally I have no clue what high or low cpu means, (especially these days
where we have multiple cores) , nor high and low screen resolutions (especially
since we can plug the same computer  on multiple screens of the different
resolution)

Besides, on the developer side, I have no clue how to turn these multiple
choices into a "should I enable this animation or not".

Your opinion ? 
You still think I should switch to sync  SH_Widget_Animate with breeze/oxygen
internal "enable animations" options ? 
What about this graphical effects level ? Should this guy be revisited, removed
?

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

[plasmashell] [Bug 365680] New: Mismanagement between Plasma5.7, amarok and pulsaudio ?

[Hans Adler via KDE Bugzilla]

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

Bug ID: 365680
   Summary: Mismanagement between Plasma5.7, amarok and pulsaudio
?
   Product: plasmashell
   Version: 5.7.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ha...@gmx.net
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.1)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.6.4-3-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- Unusual behavior I noticed:
Sometimes plasmashell crashes, while removing music-tracks from AMAROK

The crash can be reproduced sometimes.

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

Thread 8 (Thread 0x7f3e64a63700 (LWP 2074)):
#0  0x7f3e74764bfd in poll () at /lib64/libc.so.6
#1  0x7f3e796ab422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f3e796ad00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f3e66db87b9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f3e74e63a29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f3e73f6e0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f3e7476d02d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f3e62e5c700 (LWP 2075)):
#0  0x7f3e70e86859 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f3e70e45336 in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f3e70e4549c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3e7507634b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3e75023fcb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3e74e5ef5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3e75bdf225 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f3e74e63a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3e73f6e0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3e7476d02d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f3e6161e700 (LWP 2221)):
#0  0x7f3e70e44d15 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f3e70e45318 in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f3e70e4549c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3e7507634b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3e75023fcb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3e74e5ef5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3e7816ab88 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f3e74e63a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3e73f6e0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3e7476d02d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f3e53821700 (LWP )):
#0  0x7f3e74f0e839 in QElapsedTimer::isMonotonic() () at
/usr/lib64/libQt5Core.so.5
#1  0x7f3e75074d1e in QTimerInfoList::repairTimersIfNeeded() () at
/usr/lib64/libQt5Core.so.5
#2  0x7f3e75074f33 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f3e7507611e in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f3e70e449cd in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f3e70e452a0 in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f3e70e4549c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f3e7507634b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#8  0x7f3e75023fcb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#9  0x7f3e74e5ef5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#10 0x7f3e7816ab88 in  () at /usr/lib64/libQt5Qml.so.5
#11 0x7f3e74e63a29 in  () at /usr/lib64/libQt5Core.so.5
#12 0x7f3e73f6e0a4 in start_thread () at /lib64/libpthread.so.0
#13 0x7f3e7476d02d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f3e51bbd700 (LWP 2314)):
#0  0x7f3e73f7203f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3e7a72497b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f3e7a7249a9 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f3e73f6e0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3e7476d02d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f3dc077b700 (LWP 2332)):
#0  0x7f3e74764bfd in poll () at /lib64/libc.so.6
#1  0x7f3e70e45384 in g_main_context_iterate.isra () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f3e70e4549c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  

[kdeplasma-addons] [Bug 361968] wrong focus on button

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 CC||till2.schaefer@uni-dortmund
   ||.de

--- Comment #4 from Friedrich W. H. Kossebau  ---
*** Bug 365623 has been marked as a duplicate of this bug. ***

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

[plasma-pa] [Bug 365679] New: applet does not recognize volume key [unlike kmix]

[via KDE Bugzilla]

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

Bug ID: 365679
   Summary: applet does not recognize volume key [unlike kmix]
   Product: plasma-pa
   Version: 5.7.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: oanonym...@gmail.com
CC: plasma-b...@kde.org

when i use kmix, i can mute/unmute and change the volume with my laptop keys
normally.

However this doesn't work when i only use the plasma-pa applet while having
kmix disabled, so i know it is not that the button(s) are incorrectly
recognized, since kmix recognizes them.
This did happen on plasma 5.6 as well (didn't use plasma before 5.6)

Let me know if i should provide logs or similar. 

Regards

Reproducible: Always

Steps to Reproduce:
1.Disable kmix (if not already disabled)
2. Try to change volume or mute sound with dedicated keys

Actual Results:  
nothing happens

Expected Results:  
i should be able to change sound settings through machine hotkeys

Samsung NP550P5C-S02 with hardware volume hotkeys:

MuteSound=Fn+F6
VolumeUp=Fn+F7
VolumeDown=Fn+F8

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

[Breeze] [Bug 365603] Wrong tab order in the advanced settings for breeze windows decorations

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC||hugo.pereira.da.costa@gmail
   ||.com

--- Comment #3 from Hugo Pereira Da Costa  ---
Thanks for reporting. This is now fixed (and backported)

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

[Breeze] [Bug 365603] Wrong tab order in the advanced settings for breeze windows decorations

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/bree
   ||ze/1b90d45bfae12b61ab3f5b4f
   ||3b2ee82fb03f9731
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Hugo Pereira Da Costa  ---
Git commit 1b90d45bfae12b61ab3f5b4f3b2ee82fb03f9731 by Hugo Pereira Da Costa.
Committed on 14/07/2016 at 15:27.
Pushed by hpereiradacosta into branch 'Plasma/5.7'.

Fixed tab order

M  +4-2kdecoration/config/ui/breezeconfigurationui.ui

http://commits.kde.org/breeze/1b90d45bfae12b61ab3f5b4f3b2ee82fb03f9731

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

[kdeplasma-addons] [Bug 365623] weather widget settings: location search field default action should be "search"

[Friedrich W . H . Kossebau via KDE Bugzilla]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

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

--- Comment #1 from Friedrich W. H. Kossebau  ---


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

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

[kleopatra] [Bug 364296] Send certificate by mail: Wrong attachment path

[Andre Heinecke via KDE Bugzilla]

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

Andre Heinecke  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kleo |http://commits.kde.org/kleo
   |patra/60dc0bc4d6449e384d88a |patra/72a2496f2f0215f736dee
   |8e398261e1bb98f0a04 |f7f682da14ad812a47c

--- Comment #2 from Andre Heinecke  ---
Git commit 72a2496f2f0215f736deef7f682da14ad812a47c by Andre Heinecke, on
behalf of Montel Laurent.
Committed on 06/07/2016 at 10:13.
Pushed by aheinecke into branch 'sigencfiles-3'.

Fix Bug 364296 - Send certificate by mail: Wrong attachment path

FIXED-IN: 16.04.3

M  +11   -7src/newcertificatewizard/newcertificatewizard.cpp

http://commits.kde.org/kleopatra/72a2496f2f0215f736deef7f682da14ad812a47c

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

[kleopatra] [Bug 355084] key:// link not working in verify result html

[Andre Heinecke via KDE Bugzilla]

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

Andre Heinecke  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kleo |http://commits.kde.org/kleo
   |patra/a0c04348d7d2067fef3f6 |patra/cc2804f52fb544d695de8
   |35f17612c56e2a951fe |1c6d19a10368250a2fd

--- Comment #3 from Andre Heinecke  ---
Git commit cc2804f52fb544d695de81c6d19a10368250a2fd by Andre Heinecke.
Committed on 06/07/2016 at 10:03.
Pushed by aheinecke into branch 'sigencfiles-3'.

Fix key links in results

This handles the keyLink directly in the resultitemwidget and
fixes the behavior, by matching the expected format with the
actual keylink format.

M  +14   -5src/crypto/gui/resultitemwidget.cpp

http://commits.kde.org/kleopatra/cc2804f52fb544d695de81c6d19a10368250a2fd

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

[neon] [Bug 365678] New: Massive flicker and repaint problems with Neon 5.7 on remote X

[Jan-Marek Glogowski via KDE Bugzilla]

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

Bug ID: 365678
   Summary: Massive flicker and repaint problems with Neon 5.7 on
remote X
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: glo...@fbihome.de
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org

When starting LibreOffice AKA LO with KDE4 backend on a remote server, there is
a high chance LO starts and gets stuck with refresh problems (no refresh at
all) on startup. I can always deadlock refresh of LO by opening any dialog of
LO. It's a little better with the Gtk+2 backend, where the application starts,
but can still be deadlocked with opening a dialog, easiest done with the
complex extension manager.

To make it worse the whole screen basically breaks. On any mouse movement parts
of the screen flickers and is repainted wrong. At this point you can just hope
to switch to the konsole and Ctrl+C LO, which restores the screen. Luckly the
window switcher (Alt + Tab) let you identify the konsole, even if the image of
the window is completely broken, but it still resembles the konsole.

As I need this connection for my LO development, I just switched to WindowMaker
- no more problems.

I found #363500, but this looks much less severe.

Reproducible: Always

Steps to Reproduce:
1. ssh -X
2. start LibreOffice preferably with KDE4 backend


Actual Results:  
Whole screen is a mess, any interaction flickers.



Expected Results:  
Remote X "just works".

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

[calligraplan] [Bug 365677] New: Calligra crashes trying to create a new plan from a template or openning existing projects

[via KDE Bugzilla]

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

Bug ID: 365677
   Summary: Calligra crashes trying to create a new plan from a
template or openning existing projects
   Product: calligraplan
   Version: 2.9.11
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kosse...@kde.org
  Reporter: cqu...@arcor.de

Application: calligraplan (2.9.11)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

  - I cliked on new -> 8 hours project - > crash
  - I also tried to open old projects created under Fedora 23 and the tool also
crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Plan (calligraplan), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f167904b37e in QObject::objectName() const () at
/lib64/libQtCore.so.4
#7  0x7f165e64391e in
KPlato::Report::findReportData(QList const&, QString
const&) () at /lib64/libkplatoui.so.14
#8  0x7f165e63bfc3 in KPlato::ReportDesigner::setReportData(QString const&)
() at /lib64/libkplatoui.so.14
#9  0x7f167904d090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#10 0x7f165e62fd82 in KPlato::ReportSourceEditor::selectFromChanged(QString
const&) () at /lib64/libkplatoui.so.14
#11 0x7f165e649b5f in KPlato::ReportSourceEditor::slotCurrentIndexChanged()
() at /lib64/libkplatoui.so.14
#12 0x7f167904d090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#13 0x7f167a39f371 in QComboBox::currentIndexChanged(int) () at
/lib64/libQtGui.so.4
#14 0x7f167a39f40e in
QComboBoxPrivate::_q_emitCurrentIndexChanged(QModelIndex const&) () at
/lib64/libQtGui.so.4
#15 0x7f167a39f6c6 in QComboBoxPrivate::setCurrentIndex(QModelIndex const&)
() at /lib64/libQtGui.so.4
#16 0x7f167a39fa0f in QComboBox::setCurrentIndex(int) () at
/lib64/libQtGui.so.4
#17 0x7f165e64a1b9 in KPlato::ReportSourceEditor::setSourceData(QDomElement
const&) () at /lib64/libkplatoui.so.14
#18 0x7f165e63c139 in KPlato::ReportDesigner::setData() () at
/lib64/libkplatoui.so.14
#19 0x7f165e63c3b0 in KPlato::ReportDesigner::setData(QDomDocument const&)
() at /lib64/libkplatoui.so.14
#20 0x7f165e63c3ec in KPlato::ReportView::loadXML(QDomDocument const&) ()
at /lib64/libkplatoui.so.14
#21 0x7f165ec56374 in KPlato::View::createViews() () at
/lib64/libplanprivate.so.14
#22 0x7f165ec5752e in KPlato::View::initiateViews() () at
/lib64/libplanprivate.so.14
#23 0x7f165ec59710 in KPlato::View::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) [clone .part.161] () at
/lib64/libplanprivate.so.14
#24 0x7f167904d090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#25 0x7f167905786a in QSingleShotTimer::timerEvent(QTimerEvent*) () at
/lib64/libQtCore.so.4
#26 0x7f1679052c83 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4
#27 0x7f1679fb0edc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#28 0x7f1679fb7ddc in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#29 0x7f167e33d8c5 in KoApplication::notify(QObject*, QEvent*) () at
/lib64/libkomain.so.14
#30 0x7f1679038eed in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQtCore.so.4
#31 0x7f167906b910 in QTimerInfoList::activateTimers() () at
/lib64/libQtCore.so.4
#32 0x7f1679068a81 in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() at /lib64/libQtCore.so.4
#33 0x7f1672f8d703 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#34 0x7f1672f8dab0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#35 0x7f1672f8db5c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#36 0x7f167906945e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#37 0x7f167a0595b6 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#38 0x7f16790377bf in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#39 0x7f1679037b25 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#40 0x7f167903d779 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#41 0x7f167e5f2b15 in kdemain () at /lib64/libkdeinit4_calligraplan.so
#42 0x7f167803b731 in __libc_start_main () at /lib64/libc.so.6
#43 0x55994a071a09 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 364060.

Possible duplicates by query: bug 364060, bug 359537.

Reported using DrKonqi

-- 

[konsole] [Bug 349350] Some monospaced fonts missing in the fonts menu

[Dmitry Bigunyak via KDE Bugzilla]

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

Dmitry Bigunyak  changed:

   What|Removed |Added

 CC||ices...@inbox.ru

--- Comment #5 from Dmitry Bigunyak  ---
I also have the same problem.
I'm using Konsole-2.14.2 in KDE-4 (4.14.20) on my Gentoo system and can't
choose neither of just installed following monospace fonts:
* anonymous-pro
* inconsolata
* monaco

They are perfectly available in all other applications but in Konsole.
Looks very much like a bug, not sure where though.

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

[kipiplugins] [Bug 365676] New: improper handling of temporary directory

[Piotr Keplicz via KDE Bugzilla]

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

Bug ID: 365676
   Summary: improper handling of temporary directory
   Product: kipiplugins
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: SendImages
  Assignee: kde-imag...@kde.org
  Reporter: kepl...@cmc.pl

When exporting images using Digikam 5 with kipi-plugins 5.0.0 to resize and
send by email there are some problems with using temporary directory.

1) When started through KDE menu, resizing stops with "Unable to write to a
temporary directory" error.

2) When started from the terminal, images are written to the current directory,
but KMail is unable to pick them up.

While exporting, a temporary directory under /tmp appears, but is not used.

Using Plasma 5.6.5 on Ubuntu 16.04, Digikam 5.0.0 with kipi 5.0.0 from the PPA.

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

[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys

[Janek Bevendorff via KDE Bugzilla]

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

--- Comment #37 from Janek Bevendorff  ---
No, I can reproduce it at least once after a fresh reboot.

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

[kde] [Bug 232246] Autostart ignores symbolic links

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED
  Latest Commit||http://commits.kde.org/libk
   ||sieve/ee4afdd78597cb9379a39
   ||951b9eca94a8e927f98

--- Comment #2 from David Faure  ---
Git commit ee4afdd78597cb9379a39951b9eca94a8e927f98 by David Faure.
Committed on 14/07/2016 at 14:51.
Pushed by dfaure into branch 'master'.

KSieve Session: fix race while handling SSL errors.

Summary:
No need to post a request to the thread for handling an ignored ssl error,
which the thread will simply handle by emitting the sslDone signal,
which goes back to the main thread. By doing that we were making it possible
for the thread to emit other things meanwhile - like the received data from the
server,
out of sequence (the main thread can only handle it after receiving sslDone)

This fixes the never-ending spinning in "Manage Sieve Scripts" in kmail
for me (which happened about 20% of the time).

Test Plan: Manage Sieve Scripts in kmail, > 5 times.

Reviewers: dvratil, mlaurent

Reviewed By: mlaurent

Subscribers: kde-pim, #kde_pim

Tags: #kde_pim

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

M  +5-1src/kmanagesieve/session.cpp
M  +0-21   src/kmanagesieve/sessionthread.cpp
M  +0-2src/kmanagesieve/sessionthread_p.h

http://commits.kde.org/libksieve/ee4afdd78597cb9379a39951b9eca94a8e927f98

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

[parley] [Bug 365675] New: Beim Schreiben in die Datei „ *.kvtml“ ist ein Fehler aufgetreten: Die Sperrdatei kann nicht angelegt werden.

[Werner via KDE Bugzilla]

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

Bug ID: 365675
   Summary: Beim Schreiben in die Datei „ *.kvtml“ ist ein Fehler
aufgetreten: Die Sperrdatei kann nicht angelegt
werden.
   Product: parley
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: parley-bugs-n...@kde.org
  Reporter: simba...@email.de

nach Beendigung einer Übung zurück auf die Übersichtsseite, oder nach Arbeit
mit dem Editor wenn die Eintragungen abgespeichert werden sollen. Dann tritt
dieser Fehler auf.

Beim Schreiben in die Datei „ *.kvtml“ ist ein Fehler aufgetreten: Die
Sperrdatei kann nicht angelegt werden.

Wobei es egal ist welche Sprachdatei benutzt wurde (deshalb schreibe ich auch
*)

Reproducible: Always

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

[frameworks-kio] [Bug 352927] Copying symbolic links with Dolphin adds absolute path to link

[David Faure via KDE Bugzilla]

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

--- Comment #7 from David Faure  ---
varlesh: please open new bug reports for unrelated problems. This bug report
was about *copying* symlinks, your report is about *creating* symlinks. I can
confirm the bug and I'm looking into it, but please don't hijack existing bug
reports for new issues. Can you open a new bug report?

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

[frameworks-kio] [Bug 365356] KIO supports WebDAV, but doesn't accept the dav:// URL scheme (Nautilus syntax)

[David Faure via KDE Bugzilla]

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

--- Comment #2 from David Faure  ---
Did you also report a Nautilus bug saying that they should handle webdav://,
KIO syntax? :-)

In any case Elvis is right, if we are to support dav:/ then it's not just
dolphin that should support it, e.g. kioclient should support it too, this has
to happen one layer below, in kio. Not sure how though.

1) Supporting dav and webdav equally (without redirect) is feasible, but with
some mess in kio_http's code
 (e.g. there are quite some if (m_protocol == "webdav" || m_protocol ==
"webdavs") around, although this could certainly be factorized)

2) The problem is we don't really have the concept of "aliases" for protocols,
apart from the KProtocolManager::slaveProtocol mechanism, not sure it still
works (FTP handled by HTTP proxies is a rather old concept afaik, so this has
probably been untested for a while).

3) One could write a kio_dav ioslave that redirects stat(), listDir(), get()
and put() to webdav (there's probably more?).
Ah, either with actual redirection, or using ForwardingSlaveBase (i.e. internal
delegation).

In any case I don't have enough motivation (nor even a webdav account) to do
this myself, but I'll be happy to review a patch;-)

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

[korgac] [Bug 365674] New: Kontact crashed upon creation of calendar entry

[Robby Engelmann via KDE Bugzilla]

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

Bug ID: 365674
   Summary: Kontact crashed upon creation of calendar entry
   Product: korgac
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: robby.engelm...@igfs-ev.de

Application: korgac (5.2.2)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.6.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160712) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
create a new calendar event lead to the observed crash. First time I saw that
crash

-- Backtrace:
Application: KOrganizer Reminder Daemon (korgac), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f80e7a58940 (LWP 2224))]

Thread 7 (Thread 0x7f80bc91f700 (LWP 8050)):
#0  0x7f80e1636a1d in poll () at /lib64/libc.so.6
#1  0x7f80d9a85056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f80d9a8516c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f80e2178aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f80e212076a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f80e1f463b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f80e1f4b2d8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f80d9fa4474 in start_thread () at /lib64/libpthread.so.0
#8  0x7f80e163f3ed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f80bd330700 (LWP 7977)):
#0  0x7f80e1636a1d in poll () at /lib64/libc.so.6
#1  0x7f80d9a85056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f80d9a8516c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f80e2178aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f80e212076a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f80e1f463b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f80e1f4b2d8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f80d9fa4474 in start_thread () at /lib64/libpthread.so.0
#8  0x7f80e163f3ed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f80bdb31700 (LWP 2291)):
#0  0x7f80d9ac90c4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f80d9a848a9 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f80d9a84fc8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f80d9a8516c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f80e2178aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f80e212076a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f80e1f463b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f80e1f4b2d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f80d9fa4474 in start_thread () at /lib64/libpthread.so.0
#9  0x7f80e163f3ed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f80be332700 (LWP 2290)):
#0  0x7f80e1636a1d in poll () at /lib64/libc.so.6
#1  0x7f80d9a85056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f80d9a8516c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f80e2178aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f80e212076a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f80e1f463b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f80e1f4b2d8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f80d9fa4474 in start_thread () at /lib64/libpthread.so.0
#8  0x7f80e163f3ed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f80bf74d700 (LWP 2273)):
#0  0x7f80e1636a1d in poll () at /lib64/libc.so.6
#1  0x7f80d9a85056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f80d9a8516c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f80e2178aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f80e212076a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f80e1f463b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f80e25889b5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f80e1f4b2d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f80d9fa4474 in start_thread () at /lib64/libpthread.so.0
#9  0x7f80e163f3ed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f80c51bd700 (LWP 2261)):
#0  0x7f80e1636a1d in poll () at /lib64/libc.so.6
#1  0x7f80daaaf410 in  () at /usr/lib64/libxcb.so.1
#2  0x7f80daab11a9 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f80c70f77b9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f80e1f4b2d8 in  () at 

[digikam] [Bug 365375] Open with... ignores parameters of Exec line in Desktop Entry

[David Faure via KDE Bugzilla]

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

--- Comment #5 from David Faure  ---
The (admitted quite new) KRun::runApplication does exactly what you want : it
computes the process arguments and then passes them to QProcess. No runtime
dependency on anything else. It should work just fine on Windows.

I'm surprised that running desktop files with %f/%u/etc. in them is a required
feature on Windows though ?

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

[plasmashell] [Bug 365365] All widgets moved to center monitor after reboot (multi monitor setup)

[via KDE Bugzilla]

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

tom.zoeh...@gmail.com changed:

   What|Removed |Added

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

--- Comment #1 from tom.zoeh...@gmail.com ---
The issue doesn't exist anymore with plasma 5.7.1

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

[digikam] [Bug 365375] Open with... ignores parameters of Exec line in Desktop Entry

[via KDE Bugzilla]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Because KRun do not work on Windows. We need a multiplatform solution
Because we want to reduce KDE dependencies to provide a pure Qt5 application
Because we want to reduce the puzlle provided by KDE dependencies.

Gilles Caulier

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

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

[Sourish Basu via KDE Bugzilla]

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

Sourish Basu  changed:

   What|Removed |Added

 CC||sourish.b...@gmail.com

--- Comment #7 from Sourish Basu  ---
I have the same problem. From time to time, the window decorations, title bar,
borders etc. disappear, and Alt+Tab to cycle through windows, or clicking on a
window to bring it to the foreground no longer works. This is on a fresh
install of Kubuntu 16.04, with KDE 5.5.5. Strange thing is, it never says that
anything crashed, so there is no dialog box to get a crash report from.

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

[kdeconnect] [Bug 365666] Sending files from desktop to app is broken in latest update 1.3.1

[via KDE Bugzilla]

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

--- Comment #2 from g547...@rmqkr.net ---
works great again, thank you

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

[plasmashell] [Bug 365659] Icons-only task manager isn't refreshed

[Heiko Tietze via KDE Bugzilla]

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

--- Comment #2 from Heiko Tietze  ---
(In reply to Eike Hein from comment #1)
> There have been various changes since 5.7.1 that fix things in Icontasks.
> Are you able to test the 5.7 branches of plasma-desktop or plasma-workspace?

It's a productive system, well more or less since I still run KDE (scnr). I
will install what Arch offers - and try to observe if the issue persists.

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

[systemsettings] [Bug 157272] disable system notification for all applications should be possible (as in kde 3.5.x) (disable sounds for all apps)

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-desktop/49eec39d11e7f689
   ||a763e837bc82869bb08db4df
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #26 from David Faure  ---
Git commit 49eec39d11e7f689a763e837bc82869bb08db4df by David Faure.
Committed on 14/07/2016 at 13:54.
Pushed by dfaure into branch 'master'.

Add button "Disable sounds for all of these events".

Requires KF 5.24 for knotifyconfig commit 9d5440c.

M  +17   -3kcms/knotify/knotify.cpp
M  +1-0kcms/knotify/knotify.h

http://commits.kde.org/plasma-desktop/49eec39d11e7f689a763e837bc82869bb08db4df

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

[plasmashell] [Bug 365673] New: Some applications are missing their icon in system tray

[Gery via KDE Bugzilla]

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

Bug ID: 365673
   Summary: Some applications are missing their icon in system
tray
   Product: plasmashell
   Version: 5.7.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: bugzi...@cablelink.at

Since updating to Plasma 5.7.0, some apps are missing their tray icon in the
systemtray. Instead they show the grey standard icon from the breeze icon set. 
Affected apps I have found are: All electron based app (e.g. the new Skype
Alpha [1]), but also applications like the kaccessible tray icon.

[1]
https://community.skype.com/t5/Linux/Skype-for-Linux-Alpha-and-calling-on-Chrome-amp-Chromebooks/td-p/4434299

Reproducible: Always

Steps to Reproduce:
1. Start the affected app.
2. Look at the task bar.

Actual Results:  
Tray icon is replaced by grey standard icon.

Expected Results:  
Show the normal application icon like in 5.6.x.

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