[plasmashell] [Bug 372721] New: on rtl langs, view problem on the settings of widgets

[bugzilla_noreply]

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

Bug ID: 372721
   Summary: on rtl langs, view problem on the settings of widgets
   Product: plasmashell
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ttv...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 102358
  --> https://bugs.kde.org/attachment.cgi?id=102358=edit
the problem

The setting dialog is rtl bug the block with the setting is ltr
Because of that there is a extra padding
This problem exist in all the widgets settings

see attachment

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

[plasmashell] [Bug 372720] New: on rtl langs, when the panel vertical there is visual problems on kickoff

[bugzilla_noreply]

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

Bug ID: 372720
   Summary: on rtl langs, when the panel vertical there is visual
problems on kickoff
   Product: plasmashell
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: ttv...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 102357
  --> https://bugs.kde.org/attachment.cgi?id=102357=edit
example

see attachment

* The tabs need to be on the right
* There is extra padding without reason (also when the panel is not vertical)

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

[dolphin] [Bug 372719] New: on rtl langs the view engine isn't rtl

[bugzilla_noreply]

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

Bug ID: 372719
   Summary: on rtl langs the view engine isn't rtl
   Product: dolphin
   Version: 16.08.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ttv...@gmail.com
  Target Milestone: ---

The view engine is ltr

It should be rtl

Maybe you add a option to choose if the file manager should be rtl or ltr in
the settings (and option "rtl only in rtl name folder")
because there are people who like it that way

Anyway, if you add the option, the default setting should be rtl everywhere
because most of the users like it that way

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

[gcompris] [Bug 372036] Missing GCompris translations

[Harald Sitter]

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

Harald Sitter  changed:

   What|Removed |Added

   Assignee|neon-b...@kde.org   |bruno.coud...@gcompris.net
  Component|Packages User Edition   |general
Product|neon|gcompris

--- Comment #2 from Harald Sitter  ---
I am wagering a guess that it uses binaries which, when missing, are not
properly reported via cmake, which makes it impossible for integrators to know
that they are missing.

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

[plasmashell] [Bug 370149] Digital and Analog Clock display wrong local time (wrong timezone?)

[aka Tonal]

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

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

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

[aka Tonal]

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

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[dolphin] [Bug 372718] New: on rtl, on dolphin, the panel places is ltr

[bugzilla_noreply]

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

Bug ID: 372718
   Summary: on rtl, on dolphin, the panel places is ltr
   Product: dolphin
   Version: 16.08.2
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: places
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ttv...@gmail.com
  Target Milestone: ---

Created attachment 102356
  --> https://bugs.kde.org/attachment.cgi?id=102356=edit
the problem

all need to be rtl
maybe the partitions name need to be ltr
see attachment

and the default location need to be right

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

[plasma-nm] [Bug 372715] Wireless Connections fail to start on boot up

[Jan Grulich]

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

--- Comment #1 from Jan Grulich  ---
Check if output from "nmcli device wifi list" is empty when you don't see any
wireless network. If so, then the bug is in NetworkManager or somewhere else,
but I would start with report in NM bugzilla.

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

[plasmashell] [Bug 372700] Can not find PO file for translation of new Plasma activity creation

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

--- Comment #1 from Burkhard Lueck  ---
The translations were moved some month's ago:
https://marc.info/?l=kde-commits=145686608608800=2
https://marc.info/?l=kde-commits=145747924524832=2
https://marc.info/?l=kde-commits=145748070525176=2

Please provide the untranslatable strings you noticed

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

[kmail2] [Bug 372678] kmail not opening link

[Bob Miller]

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

--- Comment #4 from Bob Miller  ---
No, I did not, because simply clicking on the URL had always worked.

Following your advice, doing a "right click" and "open URL" activated the 
link!

Working fine.

Thanks,
Bob


On Monday, 21 November 2016 06:30:01 MST you wrote:
https://bugs.kde.org/show_bug.cgi?id=372678

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #3 from Laurent Montel  ---
Hi,
Did you test to use popup menu => right click on url + open ?

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

[kmail2] [Bug 372678] kmail not opening link

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #3 from Laurent Montel  ---
Hi,
Did you test to use popup menu => right click on url + open ?

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

[plasmashell] [Bug 372717] on rtl langs the search bar isn't in the right position

[bugzilla_noreply]

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

ttv...@gmail.com changed:

   What|Removed |Added

 CC|k...@privat.broulik.de   |

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

[plasmashell] [Bug 372717] on rtl langs the search bar isn't in the right position

[bugzilla_noreply]

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

ttv...@gmail.com changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

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

[plasmashell] [Bug 372717] New: on rtl langs the search bar isn't in the right position

[bugzilla_noreply]

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

Bug ID: 372717
   Summary: on rtl langs the search bar isn't in the right
position
   Product: plasmashell
   Version: 5.8.3
  Platform: unspecified
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: ttv...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 102355
  --> https://bugs.kde.org/attachment.cgi?id=102355=edit
the problem

see attachment

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

[digikam] [Bug 372672] File Renaming Options sidebar is missing

[bugzilla_noreply]

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

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

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.4.0

--- Comment #3 from caulier.gil...@gmail.com ---
Import Rename from 5.4.0 AppImage bundle for Linux

https://www.flickr.com/photos/digikam/31035224511/in/dateposted-public/

All is here and fully suitable...

Gilles Caulier

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

[digikam] [Bug 372672] File Renaming Options sidebar is missing

[bugzilla_noreply]

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

--- Comment #2 from caulier.gil...@gmail.com ---
Some feedback here using AppImage Linux bundle ?

Gilles Caulier

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

[digikam] [Bug 372684] No thumbnail shows for some files

[bugzilla_noreply]

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

--- Comment #12 from caulier.gil...@gmail.com ---
In your trace no error appear. So thumbnails are extracted as expected. The
problem is not here...

Do you have color management enabled ?

Can you share some suspect files to try to reproduce the problem here ?

Gilles Caulier

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

[digikam] [Bug 372713] Add options to unique modifier [patch]

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|Add options to unique   |Add options to unique
   |modifier|modifier [patch]

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

[digikam] [Bug 372684] No thumbnail shows for some files

[Rick]

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

Rick  changed:

   What|Removed |Added

Summary|No thumbnail shows for  |No thumbnail shows for some
   |files larger than 2MB   |files

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

[plasmashell] [Bug 372716] New: KDE start menu crashed when searching in the text field

[bugzilla_noreply]

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

Bug ID: 372716
   Summary: KDE start menu crashed when searching in the text
field
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sp3...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.8-2-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Open the start menu and start typing one or two character. It's randomly
crashed and sometimes it won't start up again.

The crash can be reproduced sometimes.

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

Thread 17 (Thread 0x7f700d7fa700 (LWP 1188)):
#0  0x7f70f3b7010f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f70f4a5bc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f703e0701c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f703e074988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f703e06f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f703e0721f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f70f4a5ad78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f70f3b6a454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f70f43707df in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f700dffb700 (LWP 1187)):
#0  0x7f70f3b7010f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f70f4a5bc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f703e0701c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f703e074988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f703e06f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f703e0749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f703e06f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f703e0749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f703e06f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f703e0721f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f70f4a5ad78 in  () at /usr/lib/libQt5Core.so.5
#11 0x7f70f3b6a454 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7f70f43707df in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f700e7fc700 (LWP 1186)):
#0  0x7f70f3b7010f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f70f4a5bc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f703e0701c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f703e074988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f703e06f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f703e0721f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f70f4a5ad78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f70f3b6a454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f70f43707df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f700effd700 (LWP 1185)):
#0  0x7f70f3b7010f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f70f4a5bc2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f703e0701c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f703e074988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f703e06f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f703e0721f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f70f4a5ad78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f70f3b6a454 in start_thread () at 

[systemsettings] [Bug 372621] Usterka w "Ustawienia systemowe" po kliknięciu na link "Wygląd aplikacji GNOME (GTK)"

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #3 from Christoph Feck  ---
Please do not change the bug status. The crash is in Qt's V4 JavaScript engine,
and is caused by the use of QML in some systemsettings modules.

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

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

[kwin] [Bug 344942] deco kcm segfaults in QV4::ExecutionEngine::~ExecutionEngine

[Christoph Feck]

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

--- Comment #43 from Christoph Feck  ---
*** Bug 372621 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 372626] Gnome gtk aspect

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[kwin] [Bug 344942] deco kcm segfaults in QV4::ExecutionEngine::~ExecutionEngine

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||pa...@benso1968.com

--- Comment #42 from Christoph Feck  ---
*** Bug 372626 has been marked as a duplicate of this bug. ***

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

[systemsettings] [Bug 372657] Details

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---
Alexey, your crash is likely unrelated. Please report it separately with your
backtrace.

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

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

[systemsettings] [Bug 355711] System Settings crashed during exit processing.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||bipinsadasiva...@gmail.com

--- Comment #45 from Christoph Feck  ---
*** Bug 372657 has been marked as a duplicate of this bug. ***

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

[frameworks-baloo] [Bug 372710] PLasmashell crashes when searching in application launcher

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|Application Launcher|general
   |(Kickoff)   |
   Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com
   Severity|critical|crash
Product|plasmashell |frameworks-baloo
   Target Milestone|1.0 |---
Version|master  |unspecified

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

[kwin] [Bug 372685] Oxygen theme style configuration icon out of place

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|style   |general
   Assignee|hugo.pereira.da.costa@gmail |kwin-bugs-n...@kde.org
   |.com|
Product|Oxygen  |kwin

--- Comment #1 from Christoph Feck  ---
The configure icon is placed relative to the total decoration size (including
shadows).

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

[plasmashell] [Bug 372694] Systemtray shows icons with wrong background color

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |5.8.0
   Target Milestone|--- |1.0
Product|ksystraycmd |plasmashell
   Assignee|kdelibs-b...@kde.org|plasma-b...@kde.org
  Component|general |XembedSNIProxy

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

[neon] [Bug 372687] User picture not showing up on login screen

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||j...@jriddell.org,
   ||neon-b...@kde.org,
   ||sit...@kde.org
Product|kdm |neon
  Component|general |general
   Assignee|kdm-bugs-n...@kde.org   |neon-b...@kde.org

--- Comment #1 from Christoph Feck  ---
I guess neon uses sddm, but letting neon maintainers decide where to assign
this bug to.

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

[bangarang] [Bug 372709] novembre

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Please report update issues to the bug tracker of your distribution.

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

[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.

[Quiralta]

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

--- Comment #8 from Quiralta  ---
On the newer builds in either Rempt/impex.. or petrovic/impex.. there is a
improvement on the speed. but the lag still too slow to be usable, most
important the point in the pop-up still inaccurate at times.

Let me know if I should try a different branch or if some other information is
needed.

@Chris and @Jelena: I do too share the same opinion, I know there is lots of
work done by the devs on the color spaces and selectors, I wouldn't like to
simply say "doesn't work for me" when it kind of does. Yet I would like to
weight my point of view towards the same situation, to me personally is very
awkward to use the ring when not in full color regardless of the saturation,
don't know if this new system mimics other software and thus was implemented to
easy other's people workflow when they are used to, or may be we are a minority
among the users who prefer the "old" way :)

Either case if Boudewijn and the rest devs think this can be worked then we
should open a different bug for it since it would be a wishlist item, but if
the case is that the work done around the color selectors simply doesn't allows
this to change, then we can focus (as users) on working-around, e.g. lately I'm
simply using the docker more than the pop-up palette to select colors, once I
have a few I like then I use the pop-up history color ring to re-select them.

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

[plasma-nm] [Bug 372715] New: Wireless Connections fail to start on boot up

[Gavin]

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

Bug ID: 372715
   Summary: Wireless Connections fail to start on boot up
   Product: plasma-nm
   Version: 5.7.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: lu...@kde.org
  Reporter: gavin.blandfo...@btinternet.com
CC: jgrul...@redhat.com
  Target Milestone: ---

Sometimes when I boot-up my Kubuntu the network icon goes RED and wont show any
wireless Networks, So I reboot my PC and then I can regain my wireless
connection. I am using the latest version of Kubuntu, Kubutu 16.10, KDE Plasma
Version 5.7.5, KDE Frameworks 5.26.0, QT 5.6.1 and kernel 4.8.0-28-generic Os
type 64 bit

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

[plasmashell] [Bug 370255] Calendar View crashes in certain months

[bugzilla_noreply]

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

--- Comment #7 from kb...@gmx.de ---
(In reply to kbrea from comment #6)
> Created attachment 102354 [details]
> Stack trace of plasmashell crash after opening calendar in one of the
> affected months
> 
> Stack trace of today, December apparently also is affected.
> It wasn't affected before, so some event or todo has been created that also
> causes this. I am running the latest KDE Applications and Framework, also
> kernel 4.8.7.1, distribution is Manjaro Linux 16.10 with the latest updates.

I meant to write November.

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

[plasmashell] [Bug 370255] Calendar View crashes in certain months

[bugzilla_noreply]

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

--- Comment #6 from kb...@gmx.de ---
Created attachment 102354
  --> https://bugs.kde.org/attachment.cgi?id=102354=edit
Stack trace of plasmashell crash after opening calendar in one of the affected
months

Stack trace of today, December apparently also is affected.
It wasn't affected before, so some event or todo has been created that also
causes this. I am running the latest KDE Applications and Framework, also
kernel 4.8.7.1, distribution is Manjaro Linux 16.10 with the latest updates.

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

[systemsettings] [Bug 372714] New: System Settings works in all categories except for window decorations

[bugzilla_noreply]

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

Bug ID: 372714
   Summary: System Settings works in all categories except for
window decorations
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dandcpro...@gmail.com
  Target Milestone: ---

systemsettings  4.11.22 has a bug that does not let you download any window
decorations.

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[Rick]

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

--- Comment #11 from Rick  ---
attached is the complete output, from startup. started up in in thumbnail
view of the album with 11 pics, 2 showing, clicked on the table view where
all 11 pics show up, then an F5

On Sun, Nov 20, 2016 at 5:13 PM, Rick Hallock  wrote:

> I think this must be the relevant info, it is from an F5 on a directory
> where 2 out of 11 pics show up in the thumbnail view.
> Or ah well I thought I saw some errors in there and I don't see them now!
> either way this is what comes out when I do an f5
>
> digikam.general: Using  8  CPU core to run threads
> digikam.general: Action Thread run  11  new jobs
> digikam.general: scan mode: ScheduleCollectionScan ::
>  ("/media/rick/Pictures/years/2016/2016-08-17 Big Girl puppy/")
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_31_00.jpg"  : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_32_00-2.jpg"  : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_32_00-1_v1.jpg"  : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_32_00-3.jpg"  : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_31_00-1.jpg"  : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_30_00.jpg"  : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_29_00.jpg"  : JPEG file identified
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_33_00-1.jpg"  : JPEG file identified
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.general: Event is dispatched to desktop notifier through DBUS
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_31_00-3_v1.jpg"  : JPEG file identified
> digikam.geoiface: 
> digikam.general: Using  8  CPU core to run threads
> digikam.general: One job is done
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.general: Action Thread run  1  new jobs
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_29_00-2.jpg"  : JPEG file identified
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_33_00.jpg"  : JPEG file identified
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.geoiface: 
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.general: One job is done
> digikam.general: Cancel Main Thread
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_31_00-3_v1.jpg"  : JPEG file identified
> digikam.general: One job is done
> digikam.general: One job is done
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_29_00-2.jpg"  : JPEG file identified
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.general: One job is done
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.general: One job is done
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
> digikam.general: One job is done
> digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
> puppy/2016_08_17_18_33_00.jpg"  : JPEG file identified
> digikam.general: One job is done
> digikam.general: List of Pending Jobs is empty
> digikam.general: Event is dispatched to desktop notifier through DBUS
> digikam.general: Cancel Main Thread
> digikam.general: Cancel Main Thread
> digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
>
>
> On Sun, Nov 20, 2016 at 4:55 PM,  wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=372684
>>
>> --- Comment #9 from caulier.gil...@gmail.com ---
>> open a terminal, go to directory where AppImage file is (use "cd" CLI
>> command),
>>  and to run it just use "./file_name"
>>
>> Gilles Caulier
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>>
>
>
>
> --
>
> Thanks
> Rick
>

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[Rick]

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

--- Comment #10 from Rick  ---
I think this must be the relevant info, it is from an F5 on a directory
where 2 out of 11 pics show up in the thumbnail view.
Or ah well I thought I saw some errors in there and I don't see them now!
either way this is what comes out when I do an f5

digikam.general: Using  8  CPU core to run threads
digikam.general: Action Thread run  11  new jobs
digikam.general: scan mode: ScheduleCollectionScan ::
 ("/media/rick/Pictures/years/2016/2016-08-17 Big Girl puppy/")
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_31_00.jpg"  : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_32_00-2.jpg"  : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_32_00-1_v1.jpg"  : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_32_00-3.jpg"  : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_31_00-1.jpg"  : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_30_00.jpg"  : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_29_00.jpg"  : JPEG file identified
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_33_00-1.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: Event is dispatched to desktop notifier through DBUS
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_31_00-3_v1.jpg"  : JPEG file identified
digikam.geoiface: 
digikam.general: Using  8  CPU core to run threads
digikam.general: One job is done
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: Action Thread run  1  new jobs
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_29_00-2.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_33_00.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.geoiface: 
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: One job is done
digikam.general: Cancel Main Thread
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_31_00-3_v1.jpg"  : JPEG file identified
digikam.general: One job is done
digikam.general: One job is done
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_29_00-2.jpg"  : JPEG file identified
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: One job is done
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: One job is done
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1
digikam.general: One job is done
digikam.dimg: "/media/rick/Pictures/years/2016/2016-08-17 Big Girl
puppy/2016_08_17_18_33_00.jpg"  : JPEG file identified
digikam.general: One job is done
digikam.general: List of Pending Jobs is empty
digikam.general: Event is dispatched to desktop notifier through DBUS
digikam.general: Cancel Main Thread
digikam.general: Cancel Main Thread
digikam.metaengine: Orientation => Exif.Image.Orientation =>  1


On Sun, Nov 20, 2016 at 4:55 PM,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=372684
>
> --- Comment #9 from caulier.gil...@gmail.com ---
> open a terminal, go to directory where AppImage file is (use "cd" CLI
> command),
>  and to run it just use "./file_name"
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[digikam] [Bug 372713] New: Add options to unique modifier

[Simon]

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

Bug ID: 372713
   Summary: Add options to unique modifier
   Product: digikam
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: AdvancedRename
  Assignee: digikam-de...@kde.org
  Reporter: freisi...@gmail.com
  Target Milestone: ---

Created attachment 102351
  --> https://bugs.kde.org/attachment.cgi?id=102351=edit
Patch to add some functionality to the unique modifier

My aim was to replace my current bash script for renaming my pictures. My
renaming scheme is:
*date*_*time**uniq*-*title*.*ext*
where the uniq modifier is an alphabetic character in case of naming conflicts.
So I implemented an option to user alphabetic characters instead of numbers and
to use a custom separator (or none at all in my case).
Unfortunately it turned out that there is one major problem with the entire
advancedrename module: Renaming is done file by file, so a single renaming
process can only be aware of already renamed files. Thus the first file that
will be conflicting does not get the *uniq* attachment, e.g. two conflicting
files are renamed:
   datetime-title.jpg
   datetime_1-title.jpg
while the desirable thing to happen would be
   datetime_1-title.jpg
   datetime_2-title.jpg
However I do not see how this could be easily achieved, so I will keep using my
script. However this functionality might be useful to someone, so you might as
well integrate it.

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[bugzilla_noreply]

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

--- Comment #9 from caulier.gil...@gmail.com ---
open a terminal, go to directory where AppImage file is (use "cd" CLI command),
 and to run it just use "./file_name"

Gilles Caulier

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[Rick]

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

--- Comment #8 from Rick  ---
i don't know how to run an appimage from terminal. I just clicked it in
nautilus


On Sun, Nov 20, 2016 at 4:41 PM,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=372684
>
> --- Comment #7 from caulier.gil...@gmail.com ---
> Can you give the full trace of debug statements printed in the console
> when you
> run AppImage, especially when album contents must be show in icon view ?
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[bugzilla_noreply]

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

--- Comment #7 from caulier.gil...@gmail.com ---
Can you give the full trace of debug statements printed in the console when you
run AppImage, especially when album contents must be show in icon view ?

Gilles Caulier

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

[frameworks-ki18n] [Bug 372681] Message with plural forms is not translated if only translation of plural form differs from msgid

[Chusslove Illich]

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

Chusslove Illich  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/ki18
   ||n/a7d5f88c144b51932859b9d3a
   ||74a21feca69fd10
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Chusslove Illich  ---
Git commit a7d5f88c144b51932859b9d3a74a21feca69fd10 by Chusslove Illich (Часлав
Илић).
Committed on 20/11/2016 at 22:31.
Pushed by ilic into branch 'master'.

Check properly pointer inequality from dngettext

If original and translation are same, dngettext will return
the original pointer, which is generally fine, except in
the corner cases where e.g. msgstr[1] is same as msgid.
Therefore check for pointer difference only with msgid or
only with msgid_plural, and not with both.

M  +7-2src/kcatalog.cpp

http://commits.kde.org/ki18n/a7d5f88c144b51932859b9d3a74a21feca69fd10

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[Rick]

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

--- Comment #6 from Rick  ---
Everything always shows up in the tableview, (except sometimes EXIF info)
but many pics do not show up in the thumbnails view.

On Sun, Nov 20, 2016 at 4:02 PM,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=372684
>
> --- Comment #4 from caulier.gil...@gmail.com ---
> Rick,
>
> I'm not sure to understand your previous comment.
>
> Do mean that thumbnail are show properly in icon-view and not in
> table-view, or
> the inverse ?
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[Rick]

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

--- Comment #5 from Rick  ---
I still get the same results using the digikam-5.4.0-01-x86-64 appimage.

I never used an appimage before! that was pretty simple, pretty nice and I
like it!

Also it is not a 2MB size. I just was looking some more and there are
 larger files with thumbs showing up.  It was just that the first dir I
checked had only 2 out of 13 that showed and those 2 were less that 2MB,
the next dir I checked had like 103 and only showed 15 and when I sorted it
by size, there were 15 files less than 2MB.   Then I tried to make one that
show and one that doesn't smaller, so I could put them in my report
question, but they both show up after converting them to a smaller size
using the batch resize to make them tiny.  It must be something in the
header.

The F5 does show doing thumbs but they still don't show up.

Maybe related...
in the thumbs view, any pics i see (have thumbs) the EXIF info changes when
I click on them, in the table view it's flaky, I click on a different album
in the tree, then click back and click a pic, then I  can cursor up and
down and exif data shows and changes, but as soon as I click a pic, exif
data goes away, keyboard cursor up and down does not bring it back.

On Sun, Nov 20, 2016 at 7:41 AM,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=372684
>
> caulier.gil...@gmail.com changed:
>
>What|Removed |Added
> 
> 
>  CC||caulier.gil...@gmail.com
>
> --- Comment #2 from caulier.gil...@gmail.com ---
> >"Thumbnail generation fails on large files" says to change "kcontrol->kde
> >components->file manager->Previes & Metadata (tab)->Maximum file size"
>
> digiKam is fully independent of KDE here. In fact digiKam become more and
> more
> KDE free since 5.x release, especially about the settings.
>
> Can you imagine that we can release DK without to try to see if JPEG fiel
> size
> > 2MB are supported well in thumbnail view. It's ridiculous.
>
> So, i suspect a huge packaging problem here. Please try with digiKam
> AppImage
> bundle instead Kubuntu package.
>
> https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM
>
> Gilles Caulier
>
>
>
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Rick,

I'm not sure to understand your previous comment.

Do mean that thumbnail are show properly in icon-view and not in table-view, or
the inverse ?

Gilles Caulier

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

[digikam] [Bug 370150] Digikam geolocation editor drag and drop works only at the first edit

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||5.4.0

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

[digikam] [Bug 370150] Digikam geolocation editor drag and drop works only at the first edit

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #6 from caulier.gil...@gmail.com ---
Thanks for the feedback.

So i recommend to report this problem as DOWNSTREAM to Ubuntu team. Sound like
a packaging problem.

Gilles Caulier

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

[kcontrol] [Bug 7524] your kde is a DEEP SHIT

[Cássio Mello]

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

--- Comment #2 from Cássio Mello  ---
HORRIBLE

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

[kcontrol] [Bug 7524] your kde is a DEEP SHIT

[Cássio Mello]

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

Cássio Mello  changed:

   What|Removed |Added

 CC||cassiocas...@live.com

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

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Gregory M . Turner]

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

--- Comment #4 from Gregory M. Turner  ---
hm, wierd.  now, after logging in, no crash.

Pretty sure the only thing I changed was to add this to konsole:

>From e434862050abe2ec48a0c506faf8e2a5f0fe99a9 Mon Sep 17 00:00:00 2001
From: "Martin T. H. Sandsmark" 
Date: Sun, 4 Sep 2016 14:12:02 +0200
Subject: [PATCH] Make the config of file filters and url filters separate

REVIEW: 128828
BUG: 368234

Which I haven't carefully looked at.  If it recurs I'll do my best to grab a
trace.  In the meanwhile I'll try to look into whats up with my coredumpctl.

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/digi
   ||kam/cf95a328cdcdd82c63d85dc
   ||bdc4ba5acc0314443
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.4.0
 Resolution|--- |FIXED

--- Comment #11 from Maik Qualmann  ---
Git commit cf95a328cdcdd82c63d85dcbdc4ba5acc0314443 by Maik Qualmann.
Committed on 20/11/2016 at 21:36.
Pushed by mqualmann into branch 'master'.

set QDrag default drop action to Qt::CopyAction
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-1libs/album/albumtreeview.cpp
M  +1-1libs/widgets/common/dragdropimplementations.cpp

http://commits.kde.org/digikam/cf95a328cdcdd82c63d85dcbdc4ba5acc0314443

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

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Gregory M . Turner]

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

--- Comment #3 from Gregory M. Turner  ---
P.S.: I have gentoo ~amd64 not Arch.

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

[kwin] [Bug 372015] kwin_x11 crashes when logging in

[Gregory M . Turner]

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

Gregory M. Turner  changed:

   What|Removed |Added

 CC||g...@be-evil.net

--- Comment #2 from Gregory M. Turner  ---
Looks damn familiar to me.  Every time I log in, decorations are zapped and
replaced, and I get what sure looks to me like OP's trace.  Unfortunately,
drkonqui likes to crash and/or lock up soon afterwards.  Are they stored
somewhere?  Even somewhere temporary that would persist after a drkonqui
segfault?  I seem to have disabled coredumpctl too for some stupid reason :(.

I have lots and lots of symbols for you if I can just manage not to fumble ball
one time.

So long as kwin successfully respawns, which it does about 90% of the time,
everything is more-or-less fine after this.  If I had to pick a likely culprit
I'd tend to suspect it's something to do with some fancy xrandr footwork I
allow to race with my sddm login.

I guess, it's taken me several recurrences to learn that (a) it's not some sort
of transient thing that will magically go away, and (b) drkonqi is never going
to work his usual magic and I'll need to do something other than ask him to
automate my telemetry.

Pretty sure this only started as of 5.8.2 or 5.8.3.  I didn't have any 5.8.x
for long, so, in truth, I could have missed earlier incidents or presumptively
attributed crashes to other stuff.  Anyhow, I'm quite sure the drkonqi report
was not happening two weeks ago.

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

[digikam] [Bug 370150] Digikam geolocation editor drag and drop works only at the first edit

[Jens]

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

--- Comment #5 from Jens  ---
Not reproducible with the AppImage linked above. Also some other issues seem
fixed (application basic font size, missing icons and icon size, etc.)

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

[Akonadi] [Bug 372712] akonadi_imap_resource crashed while I had KMail open in background

[Jure Repinc]

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

Jure Repinc  changed:

   What|Removed |Added

Version|1.13.0  |unspecified

--- Comment #1 from Jure Repinc  ---
Oh and Akonadi version (as reported by akonadictl) is 5.3.3 which is not on the
version list

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

[Akonadi] [Bug 372712] New: akonadi_imap_resource crashed while I had KMail open in background

[Jure Repinc]

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

Bug ID: 372712
   Summary: akonadi_imap_resource crashed while I had KMail open
in background
   Product: Akonadi
   Version: 1.13.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: j...@holodeck1.com
CC: kdepim-b...@kde.org, vkra...@kde.org
  Target Milestone: ---

I had KMail window open and sitting in background when I got a message that
akonadi_imap_resource crashed. This is the backtrace I got

Application: akonadi_imap_resource (akonadi_imap_resource), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa164fb9940 (LWP 1845))]

Thread 7 (Thread 0x7fa1377fe700 (LWP 2065)):
#0  0x7fa159238ea9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fa1591f2d85 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fa1591f379b in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fa1591f398c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fa15ffd979b in QEventDispatcherGlib::processEvents
(this=0x7fa1280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fa15ff831ea in QEventLoop::exec (this=this@entry=0x7fa1377fdc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7fa15fdb18b3 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7fa15fdb6558 in QThreadPrivate::start (arg=0x19fa2c0) at
thread/qthread_unix.cpp:344
#8  0x7fa15c3da454 in start_thread () from /lib64/libpthread.so.0
#9  0x7fa15f4ac39f in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fa137fff700 (LWP 1984)):
#0  0x7fa15f4a368d in poll () from /lib64/libc.so.6
#1  0x7fa1591f3876 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fa1591f398c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fa15ffd979b in QEventDispatcherGlib::processEvents
(this=0x7fa138c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fa15ff831ea in QEventLoop::exec (this=this@entry=0x7fa137ffec80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7fa15fdb18b3 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fa15fdb6558 in QThreadPrivate::start (arg=0x1af2f70) at
thread/qthread_unix.cpp:344
#7  0x7fa15c3da454 in start_thread () from /lib64/libpthread.so.0
#8  0x7fa15f4ac39f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fa145892700 (LWP 1871)):
#0  0x7fa15fe5b6fe in qt_gettime () at tools/qelapsedtimer_unix.cpp:180
#1  0x7fa15ffd7419 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7fa13c002ed0) at kernel/qtimerinfo_unix.cpp:91
#2  0x7fa15ffd79c5 in QTimerInfoList::timerWait (this=0x7fa13c002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#3  0x7fa15ffd8d6e in timerSourcePrepareHelper (timeout=0x7fa145891ab4,
src=) at kernel/qeventdispatcher_glib.cpp:132
#4  timerSourcePrepare (source=, timeout=0x7fa145891ab4) at
kernel/qeventdispatcher_glib.cpp:165
#5  0x7fa1591f2d79 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#6  0x7fa1591f379b in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7fa1591f398c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#8  0x7fa15ffd979b in QEventDispatcherGlib::processEvents
(this=0x7fa13c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#9  0x7fa15ff831ea in QEventLoop::exec (this=this@entry=0x7fa145891c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#10 0x7fa15fdb18b3 in QThread::exec (this=) at
thread/qthread.cpp:507
#11 0x7fa15fdb6558 in QThreadPrivate::start (arg=0x1aaa9e0) at
thread/qthread_unix.cpp:344
#12 0x7fa15c3da454 in start_thread () from /lib64/libpthread.so.0
#13 0x7fa15f4ac39f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fa146aa3700 (LWP 1862)):
#0  0x7fa1591f2d38 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7fa1591f379b in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fa1591f398c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fa15ffd979b in QEventDispatcherGlib::processEvents
(this=0x7fa1380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fa15ff831ea in QEventLoop::exec (this=this@entry=0x7fa146aa2c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7fa15fdb18b3 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fa15fdb6558 in QThreadPrivate::start (arg=0x19d4c10) at
thread/qthread_unix.cpp:344
#7  0x7fa15c3da454 in start_thread () from /lib64/libpthread.so.0
#8  0x7fa15f4ac39f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fa1472a4700 (LWP 1861)):
#0  0x7fa15f4a368d in poll () from /lib64/libc.so.6
#1  

[kwin] [Bug 372705] KWin crash during app move to secondary screen

[Philipp]

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

--- Comment #2 from Philipp  ---
Thanks for your feedback.

I didn't look at the backtrace myself. This makes sense, since I installed a
nvidia driver update just one day ago and never had this issue before. So I
think you'll be right and the issue is caused by a problem within nvidias
driver... one more time :-(

I hope there will be a fix released by nvidia soon. Otherwise I'll have to got
back to the previous version.

I think you may close this issue.

Sorry for bugging you with that request. I'll be more careful next time before
submitting a bugreport.

Greets

Philipp

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

[plasmashell] [Bug 372699] Window minimizes to the center of the screen if multiple windows are open in the same group.

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[kwin] [Bug 372705] KWin crash during app move to secondary screen

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is lacking debug symbols as normal on Archlinux.
This makes it impossible to further investigate.

What we see from the backtrace is that it crashes inside the proprietary nvidia
driver.

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

[digikam] [Bug 372684] No thumbnail shows for files larger than 2MB

[Rick]

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

--- Comment #3 from Rick  ---
No, I have not been able to get thumbnails to show up at all in the the
thumbnail view for those files. Thumbnails to show up on table view.

On Sun, Nov 20, 2016 at 5:32 AM, Maik Qualmann 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=372684
>
> Maik Qualmann  changed:
>
>What|Removed |Added
> 
> 
>  CC||metzping...@gmail.com
>
> --- Comment #1 from Maik Qualmann  ---
> Are thumbnails displayed after reloading (F5)?
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kaddressbook] [Bug 372711] New: kaddressbook crashes on startup

[bugzilla_noreply]

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

Bug ID: 372711
   Summary: kaddressbook crashes on startup
   Product: kaddressbook
   Version: 5.2.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: versue...@gmx.net
CC: to...@kde.org
  Target Milestone: ---

Application: kaddressbook (5.2.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-27-generic i686
Distribution: Ubuntu 16.10

-- Information about the crash:
- What I was doing when the application crashed:
starting the application
- Custom settings of the application:
carddav source on baikal. calendars from the same source are working. Birthdays
from adressbooks are shown in calendar too.

The crash can be reproduced every time.

-- Backtrace:
Application: KAddressBook (kaddressbook), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xacecf840 (LWP 2139))]

Thread 11 (Thread 0xa3095b40 (LWP 2155)):
#0  0xb77d1d05 in __kernel_vsyscall ()
#1  0xb420ac3c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xa6b35a2a in ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
#3  0xb4205305 in start_thread (arg=0xa3095b40) at pthread_create.c:333
#4  0xb5c8647e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113

Thread 10 (Thread 0xa3896b40 (LWP 2154)):
#0  0xb77d1d05 in __kernel_vsyscall ()
#1  0xb420ac3c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xa6b35a2a in ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
#3  0xb4205305 in start_thread (arg=0xa3896b40) at pthread_create.c:333
#4  0xb5c8647e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113

Thread 9 (Thread 0xa788eb40 (LWP 2152)):
#0  0xb77d1d05 in __kernel_vsyscall ()
#1  0xb77d1999 in __vdso_clock_gettime ()
#2  0xb5c93791 in __GI___clock_gettime (clock_id=1, tp=0xa788df04) at
../sysdeps/unix/clock_gettime.c:115
#3  0xb60256b8 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#4  0xb61bcbc2 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#5  0xb61bd104 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6  0xb61be6e9 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#7  0xb40bab37 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb40bb614 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb40bb844 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb61bf214 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#11 0xb6161dad in QEventLoop::exec(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#12 0xb5f83d15 in QThread::exec() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#13 0xb5f83df8 in QThread::run() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#14 0xb5f8942a in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#15 0xb4205305 in start_thread (arg=0xa788eb40) at pthread_create.c:333
#16 0xb5c8647e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113

Thread 8 (Thread 0xa808fb40 (LWP 2150)):
#0  0xb77d1d05 in __kernel_vsyscall ()
#1  0xb5c7511f in read () at ../sysdeps/unix/syscall-template.S:84
#2  0xb41016c5 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb40bb16d in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb40bb6a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb40bb844 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb61bf214 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#7  0xb6161dad in QEventLoop::exec(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#8  0xb5f83d15 in QThread::exec() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#9  0xb5f83df8 in QThread::run() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#10 0xb5f8942a in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#11 0xb4205305 in start_thread (arg=0xa808fb40) at pthread_create.c:333
#12 0xb5c8647e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113

Thread 7 (Thread 0xa8a3ab40 (LWP 2148)):
#0  0xb40bb08b in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb40bb6a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb40bb844 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb61bf214 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#4  0xb6161dad in QEventLoop::exec(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#5 

[plasmashell] [Bug 372604] Black rectangle in top right corner when switching virtual desktops

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

  Component|Pager   |general
   Assignee|h...@kde.org|k...@davidedmundson.co.uk
 CC||bhus...@gmail.com

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #39 from Maik Qualmann  ---
I have now access to a Windows7 computer where I can reproduce the problem. I
will create a special debug version in the next days and look.

Maik

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

[plasmashell] [Bug 372710] New: PLasmashell crashes when searching in application launcher

[DroidFreak]

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

Bug ID: 372710
   Summary: PLasmashell crashes when searching in application
launcher
   Product: plasmashell
   Version: master
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: rushabsha...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 102346
  --> https://bugs.kde.org/attachment.cgi?id=102346=edit
Text file for the bug(same as the one in description)

It always crashes when i try to search anything in the application launcher
Here's what i got in gdb:

(gdb) bt
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x72daf670 in QByteArray::QByteArray(char const*, int) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fff1604c007 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#3  0x7fff1604c389 in Baloo::PostingDB::prefixIter(QByteArray const&) ()
   from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#4  0x7fff16056c1d in
Baloo::Transaction::postingIterator(Baloo::EngineQuery const&) const ()
   from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#5  0x7fff164af283 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#6  0x7fff164ae92a in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#7  0x7fff164af860 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#8  0x7fff1649df8f in Baloo::Query::exec() () from
/usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#9  0x7fff166e76b0 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#10 0x7fff166e8489 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#11 0x7fff3aae3548 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) ()
   from /usr/lib/x86_64-linux-gnu/libKF5Runner.so.5
#12 0x7fff39fe1c28 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x7fff39fe0660 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#14 0x7fff39fe0200 in ThreadWeaver::Thread::run() ()
   from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#15 0x72dabc68 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x71e8b70a in start_thread (arg=0x7ffedf7fe700) at
pthread_create.c:333
---Type  to continue, or q  to quit---
#17 0x726b70af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105
(gdb)

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[Nicolas Brisset]

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

Nicolas Brisset  changed:

   What|Removed |Added

 CC||nicolas.bris...@airbus.com

--- Comment #38 from Nicolas Brisset  ---
I also see this bug (5.2.0 installed, Windows 7 64 bits AND Windows 10 64 bits
on a different PC). I also use a card reader to transfer the pictures, I
suspect this has something to do with the issue.

Now, the interesting thing in my case is that I live close to Salon de Provence
=> @Gilles C.: if you still live in the area, we could maybe organize a live
debug session on the PC with the problem, since it seems you can't reproduce
it. I also have a couple of other problems we could look at... I'd be really
happy to help improve digikam, it's such a great program!

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

[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.

[Jelena]

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

--- Comment #7 from Jelena  ---
Thanks for working on it but the current implementation of the color selector
unfortunately also doesn't work too well for me:

When I choose a black color the whole outer circle turns black and I first have
to select a different saturation to see colour on the outer circle again.
(Acoordingly when I choose a white color the whole circle turns white.)

As I use black or grey most of the times I don't see any colors in the wheel
most of the time which is quite irritating.

Is there a toggle anywhere to switch back to the previous behaviour (i.e.
always showing a colored outer circle)?

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

[digikam] [Bug 372312] database upgrade v7 to v8 failed

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Attachment #102340|0   |1
is obsolete||
 Attachment #102342|0   |1
is obsolete||

--- Comment #13 from Maik Qualmann  ---
Created attachment 102345
  --> https://bugs.kde.org/attachment.cgi?id=102345=edit
dbconfig.xml

Thanks, can you try this file before I commit the patch?

Maik

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

[kdeconnect] [Bug 370890] Media control screen is cut off on smaller devices when cover art is present

[MathB]

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

--- Comment #2 from MathB  ---
Comment on attachment 102344
  --> https://bugs.kde.org/attachment.cgi?id=102344
screenshot

I've the same problem, see attached screenshot.
My phone is running Android 6

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

[kdeconnect] [Bug 370890] Media control screen is cut off on smaller devices when cover art is present

[MathB]

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

MathB  changed:

   What|Removed |Added

 CC||mathieu.benaz...@gmail.com

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

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

[dolphin] [Bug 369286] dolphin 16.08.1's Mousewheel scrolling is very small at all settings in non-Plasma5-desktops (regression from 16.04)

[Shlomi Fish]

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

--- Comment #6 from Shlomi Fish  ---
(In reply to Elvis Angelaccio from comment #5)
> I just tried on a Fedora 25 Gnome VM and scrolling works fine in the Detail
> view mode (latest git master). What's your input driver? evdev or libinput?

How do I tell exactly? Based on ~/.local/share/xorg/Xorg.0.log it seems to be
evdev because it is mentioned several times whereas libinput is completely
absent.

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

[bangarang] [Bug 372709] New: novembre

[Golmard Catherine]

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

Bug ID: 372709
   Summary: novembre
   Product: bangarang
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jamboar...@gmail.com
  Reporter: bion...@yahoo.fr
  Target Milestone: ---

Created attachment 102343
  --> https://bugs.kde.org/attachment.cgi?id=102343=edit
Je n'arrive pas à faire de mise à jour , et de dépot non plus

Je n'arrive pas à faire de mise à jour aux mirroirs et les dépots non plus ne
se font pas

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[digikam] [Bug 372312] database upgrade v7 to v8 failed

[Kusi]

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

--- Comment #12 from Kusi  ---
I've added my dbconfig.xml with which I was successful. In addition to the
modified dbconfig.xml, the following changes to the db were needed

- Since I have many Umlaute, accents etc in my db, I first had to fix the
encoding. You have the utf encoding in your dbconfig.xml, but for unknown
reasons I had to do that explicitly first before running DK. I assume it comes
with the ENGINE change.

  ALTER TABLE digikamdb.Albums 
  DEFAULT CHARSET=utf8;

  ALTER TABLE digikamdb.Images 
  DEFAULT CHARSET=utf8;

- During creation of the Albums_AlbumRoots constraint, you limit the column
"relativePath" to 255 chars, but that didn't do the trick (neither did it for
other users on digikam-user mailing list, as you remember). I don't know why
(again I assume its because of the ENGINE change to InnoDB), though. I had to
change the datatype from LONGTEXT to VARCHAR(255) in the ALTER command of the
v7 to v8 upgrade statement

For me, the issue is resolved, but I don't think the solution to my issues is
applicable for everybody. If needed, you can have my db to experiment (in an
anonymized form), let me know.

Am I the only one with plenty of FK constraint violations? If needed by
someone, I have a (risky) script which resolves them.

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

[Discover] [Bug 367526] Discover is not able to discover NO SEARCH RESULTS !!

[Cris]

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

--- Comment #5 from Cris  ---
How do I get the more updated version? I'm new to Linux as I haven't used it in
years and decided to remote myself from the typical Windows environment. I
tried searching for updates through discover and it doesn't find any updates
and to be honest not sure if after the last update when installing if anything
else is updated or in need of.

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

[konsole] [Bug 372441] Konsole Desktop file missing StartupWMClass

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[karbon] [Bug 353816] garbage values in feConvolveMatrix kernel when size increased

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[konsole] [Bug 332601] "search backwards" option not saved/restored

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[kde-windows] [Bug 366596] Some KDE applications processes remain as background (zombie) processes after closing

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[plasmashell] [Bug 372594] no wallpaper menu for a fresh new .config directory

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[digikam] [Bug 372312] database upgrade v7 to v8 failed

[boospy]

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

--- Comment #11 from boospy  ---
In the meantime it has worked for me too. What have i done. First i migrated do
sqlite. That seems to be not worked. No Pictures no data. Than i've created new
database and migrated the datas back and after this everything was there again.

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

[kdev-python] [Bug 359912] Type not recognized in expressions with multiple subscripts

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[kmail2] [Bug 372708] New: Kmail stopped working

[Ekkehard Blanz]

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

Bug ID: 372708
   Summary: Kmail stopped working
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: ekkehard.bl...@gmail.com
  Target Milestone: ---

Kmail was working fine for me using a gmail IMAP account - for years.  After
upgrading to Kubuntu 16.04 LTS it started to show occasional problems loading
emails in the preview pane.  Double clicking on the mail item to display it in
its own window usually fixed the problem temporarily.  But the time it took to
do that got longer and longer.  Now it stopped working entirely (I know it
sounds a little weird and amateurish - but this is what I observed).  After a
reboot, I get all my mail, but not after that anymore (without additional
akonadi restarting actions).  Restarting kmail won't help - "akonadictl
restart" does fix the problem.  The error message (at the bottom of the kmail
window) is "Unable to fetch item from backend (collection -1): Unable to
retrieve item from resource: Job cancelled" If I would not know how to restart
akonadi, this would render the kmail version that comes with 16.04 LTS useless.
 With restarting akonadictl, I have a usable workaround.

Please let me know if you need any additional information, logs, etc.

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

[digikam] [Bug 372312] database upgrade v7 to v8 failed

[Kusi]

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

--- Comment #10 from Kusi  ---
Created attachment 102342
  --> https://bugs.kde.org/attachment.cgi?id=102342=edit
my dbconfig.xml

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

[plasma4] [Bug 372707] New: shell de plasma falla

[clau]

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

Bug ID: 372707
   Summary: shell de plasma falla
   Product: plasma4
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: claudio...@hotmail.com
  Target Milestone: ---

Application: plasma-desktop (4.11.18)
KDE Platform Version: 4.14.11 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 4.1.13-100.fc21.i686 i686
Distribution: "Korora release 21 (Darla)"

-- Information about the crash:
La shell se va a negro al pulsar sobre "nueva actividad" en el escritorio.

The crash can be reproduced every time.

-- Backtrace:
Application: Shell de escritorio Plasma (plasma-desktop), signal: Segmentation
fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb76fd800 (LWP 4147))]

Thread 8 (Thread 0xa8d80b40 (LWP 4150)):
#0  0x in __kernel_vsyscall ()
#1  0x44cb4e9c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x4b160271 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib/libQtScript.so.4
#3  0x4b1602b0 in QTWTF::TCMalloc_Central_FreeList::Init(unsigned int) () at
/lib/libQtScript.so.4
#4  0x44cb0313 in start_thread () at /lib/libpthread.so.0
#5  0x44bd5f2e in clone () at /lib/libc.so.6

Thread 7 (Thread 0xa6e8fb40 (LWP 4164)):
#0  0x in __kernel_vsyscall ()
#1  0x44bc929b in poll () at /lib/libc.so.6
#2  0x44e7424c in g_poll () at /lib/libglib-2.0.so.0
#3  0x44e64520 in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#4  0x44e64669 in g_main_context_iteration () at /lib/libglib-2.0.so.0
#5  0x49cbce3f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#6  0x49c876e2 in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#7  0x49c87a89 in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#8  0x49b61034 in QThread::exec() () at /lib/libQtCore.so.4
#9  0x49c65741 in QInotifyFileSystemWatcherEngine::run() () at
/lib/libQtCore.so.4
#10 0x49b63d4b in QThreadPrivate::start(void*) () at /lib/libQtCore.so.4
#11 0x44cb0313 in start_thread () at /lib/libpthread.so.0
#12 0x44bd5f2e in clone () at /lib/libc.so.6

Thread 6 (Thread 0xa5b38b40 (LWP 4169)):
#0  0x49cbc794 in timerSourceCheck(_GSource*) () at /lib/libQtCore.so.4
#1  0x44e63eff in g_main_context_check () at /lib/libglib-2.0.so.0
#2  0x44e644ba in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#3  0x44e64669 in g_main_context_iteration () at /lib/libglib-2.0.so.0
#4  0x49cbce3f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#5  0x49c876e2 in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#6  0x49c87a89 in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#7  0x49b61034 in QThread::exec() () at /lib/libQtCore.so.4
#8  0x49c65741 in QInotifyFileSystemWatcherEngine::run() () at
/lib/libQtCore.so.4
#9  0x49b63d4b in QThreadPrivate::start(void*) () at /lib/libQtCore.so.4
#10 0x44cb0313 in start_thread () at /lib/libpthread.so.0
#11 0x44bd5f2e in clone () at /lib/libc.so.6

Thread 5 (Thread 0xa2375b40 (LWP 4174)):
#0  0x in __kernel_vsyscall ()
#1  0x44bc929b in poll () at /lib/libc.so.6
#2  0x44e7424c in g_poll () at /lib/libglib-2.0.so.0
#3  0x44e64520 in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#4  0x44e64669 in g_main_context_iteration () at /lib/libglib-2.0.so.0
#5  0x49cbce3f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQtCore.so.4
#6  0x49c876e2 in
QEventLoop::processEvents(QFlags) () at
/lib/libQtCore.so.4
#7  0x49c87a89 in QEventLoop::exec(QFlags) () at
/lib/libQtCore.so.4
#8  0x49b61034 in QThread::exec() () at /lib/libQtCore.so.4
#9  0x49c65741 in QInotifyFileSystemWatcherEngine::run() () at
/lib/libQtCore.so.4
#10 0x49b63d4b in QThreadPrivate::start(void*) () at /lib/libQtCore.so.4
#11 0x44cb0313 in start_thread () at /lib/libpthread.so.0
#12 0x44bd5f2e in clone () at /lib/libc.so.6

Thread 4 (Thread 0xa1939b40 (LWP 4175)):
#0  0x in __kernel_vsyscall ()
#1  0x44cb4e9c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x4df18354 in WTF::ThreadCondition::wait(WTF::Mutex&) () at
/lib/sse2/libQtWebKit.so.4
#3  0x4db9ac3c in JSC::BlockAllocator::blockFreeingThreadMain() () at
/lib/sse2/libQtWebKit.so.4
#4  0x4def6e19 in WTF::threadEntryPoint(void*) () at /lib/sse2/libQtWebKit.so.4
#5  0x4df17c3a in WTF::wtfThreadEntryPoint(void*) () at
/lib/sse2/libQtWebKit.so.4
#6  0x44cb0313 in start_thread () at /lib/libpthread.so.0
#7  0x44bd5f2e in clone () at /lib/libc.so.6

Thread 3 (Thread 0xa0cd7b40 (LWP 4176)):
#0  0x in __kernel_vsyscall ()
#1  0x44cb7e5b in read () at /lib/libpthread.so.0
#2  0x44ead7b6 in g_wakeup_acknowledge () at /lib/libglib-2.0.so.0
#3  0x44e63fd7 in g_main_context_check () at 

[i18n] [Bug 372675] several kde-l10n 16.12 beta packages fail to build

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #3 from Albert Astals Cid  ---
i've fixed the svn sources for es. it'll be fixed for next release.

In the meantime you can apply https://paste.kde.org/pfgw9drsq

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

[dolphin] [Bug 369286] dolphin 16.08.1's Mousewheel scrolling is very small at all settings in non-Plasma5-desktops (regression from 16.04)

[Elvis Angelaccio]

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

--- Comment #5 from Elvis Angelaccio  ---
I just tried on a Fedora 25 Gnome VM and scrolling works fine in the Detail
view mode (latest git master). What's your input driver? evdev or libinput?

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #17 from RJVB  ---
I'd say that the most important aspect here is that behaviour is as much the
same as possible across platforms. In this case that would mean that they all
have a sufficient line spacing, and that a same font size will give a number of
lines per height unit that's as similar as possible.

I was surprised to see the difference qCeil can make vs. qFloor in that latter
aspect, so I hope you test this properly before making a decision. #ifdefs
don't look very nice, but nice looking code isn't the goal here.

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

[plasmashell] [Bug 360219] Right Click opens files

[Aurélien Murith]

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

Aurélien Murith  changed:

   What|Removed |Added

 CC||aurelienmur...@netc.fr

--- Comment #35 from Aurélien Murith  ---
Problem still present on Plasma 5.8.2 (Qt 5.7).

Right-clicking on files that are on the desktop (folder view) often (not
always) opens them, in addition of opening the context menu.

It's a really annoying bug...

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

[kmail2] [Bug 372706] New: The message list tuns in to a long gray bars, text unreadable

[Roland]

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

Bug ID: 372706
   Summary: The message list tuns in to a long gray bars, text
unreadable
   Product: kmail2
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: roel.ves...@hotmail.com
  Target Milestone: ---

Created attachment 102341
  --> https://bugs.kde.org/attachment.cgi?id=102341=edit
Screenshot of the bug at work

The message list is unreadable, shows the number of threads and unread emails.
Application cant be used because I cant see which line is which email.

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

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[Dominik Haumann]

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

--- Comment #16 from Dominik Haumann  ---
> I would be fine with changing that to ceil, floor
> is a bad idea, no clue why we/I did not use ceil :/

Interestingly, I wondered why you changed if from ceil to floor, but I trusted
you enough that this was intentional :-)

But then it's easy: back to qCeil() and that's it.

Btw: The #ifdef is the worst solution of all, so this is a no-go in my opinion.

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

[lokalize] [Bug 368842] Behavior of navigation in lokalize is broken

[Nick Shaforostoff]

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

--- Comment #2 from Nick Shaforostoff  ---
Git commit bf393c36847f0198668953da97831872433ab04a by Nick Shaforostoff.
Committed on 20/11/2016 at 17:41.
Pushed by shaforo into branch 'Applications/16.12'.
pass also the filename to file save dialog

M  +2-2scripts/xliff2odf-standalone.py
M  +1-1src/editortab.cpp

http://commits.kde.org/lokalize/bf393c36847f0198668953da97831872433ab04a

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

[krunner] [Bug 344328] krunner is not visible when using multiple monitors

[Jonathan Schuett]

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

Jonathan Schuett  changed:

   What|Removed |Added

 CC||bioshacker...@gmail.com

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

[lokalize] [Bug 368842] Behavior of navigation in lokalize is broken

[Nick Shaforostoff]

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

--- Comment #1 from Nick Shaforostoff  ---
Git commit 70662d13782654a2dc9802d835fd26ae99b7fe00 by Nick Shaforostoff.
Committed on 20/11/2016 at 17:39.
Pushed by shaforo into branch 'Applications/16.04'.
pass also the filename to file save dialog

M  +2-2scripts/xliff2odf-standalone.py
M  +1-1src/editortab.cpp

http://commits.kde.org/lokalize/70662d13782654a2dc9802d835fd26ae99b7fe00

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

[kwin] [Bug 372705] New: KWin crash during app move to secondary screen

[Philipp]

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

Bug ID: 372705
   Summary: KWin crash during app move to secondary screen
   Product: kwin
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: phil...@haefelfinger.ch
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.8-2-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

I moved an instance of libre office calc from my primary display to the
secondary display. During the move (the windows was about 60% on the secondary
display) the screens went black and the crash reporting assistant started. The
second try worked as expected.

- System:
Intel Core-i7-2600K
16GB Memory
Nvidia GeForce 960GTX (GM206)

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1d8940a840 (LWP 5467))]

Thread 5 (Thread 0x7f1d66253700 (LWP 5476)):
#0  0x7f1d88e48551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f1d864f89e0 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f1d864fa3b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f1d864a723a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f1d862ca0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f1d862ced78 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f1d820e3454 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f1d88e517df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f1d67254700 (LWP 5475)):
#0  0x7f1d88e48551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f1d864f8ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f1d864fa3b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f1d864a723a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f1d862ca0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f1d80e412d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f1d862ced78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f1d820e3454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f1d88e517df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f1d67fff700 (LWP 5474)):
#0  0x7f1d820e94b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1d862cfb66 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1d862cb274 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f1d862ced78 in  () at /usr/lib/libQt5Core.so.5
#4  0x7f1d820e3454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f1d88e517df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f1d6dba8700 (LWP 5472)):
#0  0x7f1d88e48551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f1d864f8ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f1d864fa3b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f1d864a723a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f1d862ca0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f1d8000be55 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f1d862ced78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f1d820e3454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f1d88e517df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f1d8940a840 (LWP 5467)):
[KCrash Handler]
#6  0x7f1d52ebd9f5 in  () at /usr/lib/libnvidia-glcore.so.375.20
#7  0x7f1d532b7b16 in  () at /usr/lib/libnvidia-glcore.so.375.20
#8  0x7f1d533edeb6 in  () at /usr/lib/libnvidia-glcore.so.375.20
#9  0x7f1d53061a9b in  () at /usr/lib/libnvidia-glcore.so.375.20
#10 0x7f1d53023e6c in  () at /usr/lib/libnvidia-glcore.so.375.20
#11 0x7f1d81c833d1 in KWin::GLShader::link() () at
/usr/lib/libkwinglutils.so.9
#12 0x7f1d81c8a1ef in
KWin::ShaderManager::generateCustomShader(QFlags, QByteArray
const&, QByteArray const&) () at /usr/lib/libkwinglutils.so.9
#13 0x7f1d81c8a312 in
KWin::ShaderManager::generateShader(QFlags) () at
/usr/lib/libkwinglutils.so.9
#14 0x7f1d81c8a3bc in
KWin::ShaderManager::shader(QFlags) () at
/usr/lib/libkwinglutils.so.9
#15 0x7f1d81c8a5ce in
KWin::ShaderManager::pushShader(QFlags) () at
/usr/lib/libkwinglutils.so.9
#16 0x7f1d889ff040 in  () at /usr/lib/libkwin.so.5
#17 0x7f1d889ff366 in KWin::SceneOpenGL::createScene(QObject*) () at
/usr/lib/libkwin.so.5
#18 0x7f1d889d5f0c 

[frameworks-ktexteditor] [Bug 372629] [OS X] line height too low issue(s)

[RJVB]

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

--- Comment #15 from RJVB  ---
Did you compare the spacing with qCeil and qFloor on Linux and/or MS Windows? I
find the line spacing just fine on Linux, and would regret it getting
significantly more ample *). Maybe it can be tied to the hidpi setting, but
when your screen is only 768 pixels high like mine I tend prefer a somewhat
more compact layout than I might otherwise prefer. It just got too compact on
OS X.

*) using ceil instead of floor makes lines approx. 10% higher for me, iow 10
lines instead of 11 lines in the same vertical space with Ubuntu Mono 12pt.

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

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

[Michael Butash]

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

--- Comment #248 from Michael Butash  ---
Thanks Phil, I'll say I tend to agree that I'd not do it that way myself
either, but rather that's what nvidia-settings spits out itself there, and does
tend to work.

That said, it not being correct in the eyes of kde, does that somehow
complicate plasma?  I'm new to nvidia binary drivers, coming from amd prior
where I was using just oss drivers and had all the same oddities with kde
plasma5, but they *were* fixed prior to switching to this new system.  I have
to trust nvidia is setting itself up how it wants as per xorg drivers, but
wouldn't surprise me if this complicates some upstream code.

I've tried deleting the xorg entirely too, which doesn't really change the
unstable nature of where the task bar and wallpapers shift to

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[Rafael]

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

--- Comment #10 from Rafael  ---
This maybe will clear more the Digikam issue, cause we can demonstrate is not a
QT vs GTK+ or GIMP application fail. I CAN D to GIMP canvas from Krusader,
another QT native file manager like Dolphin, that let us D to GIMP canvas.

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

[digikam] [Bug 372683] Attempt to set a screen on a child window and DBusMenuExporterPrivate::fillLayoutItem No id for action

[bugzilla_noreply]

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

--- Comment #8 from e.longuem...@laposte.net ---
Hello,

This has been reported here :
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009

Thanks,

Eric

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

[digikam] [Bug 372640] Can't drag any image file from digikam to GIMP

[Rafael]

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

--- Comment #9 from Rafael  ---
(In reply to caulier.gilles from comment #8)
> I just tested with digiKam AppImage bundle and Gimp. Drag and drop work
> fine. You just to drop item from DK into right region of Gimp GUI.
>
Digikam 5.3 works on that way too, that's not a problem.

> If D do not work to Gimp canvas, well it's a problem into Gimp to support
> this action at the right place in Gimp Implementation. Why it support well
> this action somewhere in Gimp GUI and not in another place ?...

You forgot to try to D from Dolphin or Gwenview to GIMP canvas and it works
like a charm. So, why is Digikam failing and not this two programs?

Hi Gilles

> Gilles Caulier

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