[digikam] [Bug 387515] Crash on start-up

[Maik Qualmann]

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

--- Comment #6 from Maik Qualmann  ---
Thanks for the TIFF image. I can not reproduce the crash with the TIFF image. I
use also libexiv2-0.26. Can you try the AppImage?

https://files.kde.org/digikam/

Maik

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

[krusader] [Bug 386217] Pressing Arrow keys behaves incorrectly in quicksearch

[Nikita Melnichenko]

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

--- Comment #12 from Nikita Melnichenko  ---
BTW, I don't mind to work on a change to bring the proposal from comment #6 to
life, however we must agree on the behavior spec first. I need a confidence
that my patch won't be declined because of differences in views on UI.

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

[gwenview] [Bug 387573] New: Select first item item in folder does not work with semantic filter active

[Peter Mühlenpfordt]

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

Bug ID: 387573
   Summary: Select first item item in folder does not work with
semantic filter active
   Product: gwenview
   Version: Git (add output of "git log -1 --oneline" to
description)
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: de...@ukn8.de
  Target Milestone: ---

When entering a folder in browse mode, the first item should be selected.
This does not work, if a semantic filter (e.g. rating) is active.
See patch https://phabricator.kde.org/D8934 for more technical details.

Steps to reproduce:
1. Open gwenview in browse mode
2. Add filter "Filter by Rating"
3. Navigate to another folder with some images inside (and no subfolders)

Expected: First thumbnail is selected
What happens: Nothing is selected

$ git log -1 --oneline
0dd3654c (HEAD -> master, origin/master, origin/HEAD) GIT_SILENT made messages
(after extraction)

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

[digikam] [Bug 372831] Digikam crashes when trying to fix red eyes.

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||germ...@backspace.bz

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

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

[digikam] [Bug 387571] Red Eye Correction crashes ShowFoto

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

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

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


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

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

[digikam] [Bug 387571] Red Eye Correction crashes ShowFoto

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Platform|unspecified |openSUSE RPMs

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

[digikam] [Bug 387571] Red Eye Correction crashes ShowFoto

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |digikam-bugs-n...@kde.org
  Component|general |Faces-RedEyes
 CC||metzping...@gmail.com
Version|unspecified |5.2.0
Product|kde |digikam

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

[KScreen] [Bug 353637] Cannot enable second monitor in Display Configuration

[bugzilla_noreply]

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

--- Comment #20 from y...@riseup.net ---
For some months the external monitor worked fine. Now the problem is back.
Syslog contains the following:

HPD interrupt storm detected on connector DP-2: switching from hotplug
detection to polling

Any more ideas?

I'm running Kubuntu 16.04 (LTS) with Kernel 4.10.40 currently.

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

[gwenview] [Bug 387567] Panning and window resizing in gwenview is laggy

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[phonon-backend-gstreamer] [Bug 380214] music stop playing when using gstreamer as backend

[TOM Harrison]

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

--- Comment #3 from TOM Harrison  ---
This will happened when I have both mp4 and mp3 in the amarok or clementime.
When It play mp4 file finish, and switch to mp3 file, sometimes It will stock.

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

[konversation] [Bug 387572] New: Konversation always starts at top-left corner

[clementine]

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

Bug ID: 387572
   Summary: Konversation always starts at top-left corner
   Product: konversation
   Version: 1.7.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: vela...@outlook.com
  Target Milestone: ---

I'm runing konversation 1.7.4 on openSUSE 42.3 with KDE 5.8.7, Qt 5.6.1. I've
set window placement policy to 'centered'. But konversation semms not to obey
that and always start at top-left corner. Konversation 1.6 at openSUSE 42.2 is
normal.

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

[kde] [Bug 387571] New: Red Eye Correction crashes ShowFoto

[Charles German y]

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

Bug ID: 387571
   Summary: Red Eye Correction crashes ShowFoto
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: germ...@backspace.bz
  Target Milestone: ---

Application: showfoto (5.2.0)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.92-18.36-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed: I simply had a photo and
started to use the Red Eye correction and it crashed- twice.

The crash can be reproduced every time.

-- Backtrace:
Application: Showfoto (showfoto), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f29d1a179c0 (LWP 7602))]

Thread 48 (Thread 0x7f28e67fc700 (LWP 1925)):
#0  0x7f29cd0d30bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f29c8ef97bd in ?? () from /usr/lib64/libopencv_core.so.6.3
#2  0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#3  0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 47 (Thread 0x7f291d7fa700 (LWP 1924)):
#0  0x7f29cd0d30bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f29c8ef97bd in ?? () from /usr/lib64/libopencv_core.so.6.3
#2  0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#3  0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 46 (Thread 0x7f291e7fc700 (LWP 1923)):
#0  0x7f29cd0d30bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f29c8ef97bd in ?? () from /usr/lib64/libopencv_core.so.6.3
#2  0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#3  0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 45 (Thread 0x7f291f7fe700 (LWP 1922)):
#0  0x7f29cd0d30bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f29c8ef97bd in ?? () from /usr/lib64/libopencv_core.so.6.3
#2  0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#3  0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 44 (Thread 0x7f297af8d700 (LWP 1921)):
#0  0x7f29cd0d30bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f29c8ef97bd in ?? () from /usr/lib64/libopencv_core.so.6.3
#2  0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#3  0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 43 (Thread 0x7f297ee97700 (LWP 1920)):
#0  0x7f29cd0d30bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f29c8ef97bd in ?? () from /usr/lib64/libopencv_core.so.6.3
#2  0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#3  0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 42 (Thread 0x7f291dffb700 (LWP 1919)):
#0  0x7f29cd0d30bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f29c8ef97bd in ?? () from /usr/lib64/libopencv_core.so.6.3
#2  0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#3  0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 41 (Thread 0x7f291effd700 (LWP 1918)):
#0  0x7f29cd0d30bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f29c8ef97bd in ?? () from /usr/lib64/libopencv_core.so.6.3
#2  0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#3  0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 40 (Thread 0x7f28e6ffd700 (LWP 31618)):
[KCrash Handler]
#6  std::vector::size (this=,
this=) at /usr/include/c++/4.8/bits/stl_vector.h:646
#7  std::vector::vector (__x=...,
this=) at /usr/include/c++/4.8/bits/stl_vector.h:312
#8  Digikam::redeye::ShapePredictor::operator() (rect=..., img=...,
this=) at
/usr/src/debug/digikam-5.2.0/core/libs/facesengine/shape-predictor/shapepredictor.h:450
#9  Digikam::RedEyeCorrectionFilter::filterImage (this=0x57e3580) at
/usr/src/debug/digikam-5.2.0/core/libs/dimg/filters/redeye/redeyecorrectionfilter.cpp:158
#10 0x7f29d0be0908 in Digikam::DImgThreadedFilter::startFilterDirectly
(this=0x57e3580) at
/usr/src/debug/digikam-5.2.0/core/libs/dimg/filters/dimgthreadedfilter.cpp:197
#11 0x7f29d0e1593e in Digikam::DynamicThread::DynamicThreadPriv::run
(this=0x26001b0) at
/usr/src/debug/digikam-5.2.0/core/libs/threads/dynamicthread.cpp:183
#12 0x7f29cdf2a81e in QThreadPoolThread::run (this=0x2a43b00) at
thread/qthreadpool.cpp:93
#13 0x7f29cdf2d9e9 in QThreadPrivate::start (arg=0x2a43b00) at
thread/qthread_unix.cpp:341
#14 0x7f29cd0ce744 in start_thread () from /lib64/libpthread.so.0
#15 0x7f29cd617aad in clone () from /lib64/libc.so.6

Thread 39 (Thread 

[kwin] [Bug 387486] kwin hangs when trying to start on another seat other than seat0

[bugzilla_noreply]

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

--- Comment #4 from bluescreenaven...@gmail.com ---
That's my assumption as well... ...let me know if you need me to try anything

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

[kde] [Bug 387316] Shift-Tab in Kicker crashes kde

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Please add the backtrace for the crash. For more information, please read
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[dolphin] [Bug 387430] Dolphin Crash on exit

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |dolphin-bugs-n...@kde.org
  Component|general |general
 CC||elvis.angelac...@kde.org
Version|unspecified |16.12.3
Product|kde |dolphin

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

[kdenlive] [Bug 387520] Shutdown Computer after Renderings not working. (Specific to Linux Mint.)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Product|kde |kdenlive
  Component|general |User Interface
   Assignee|unassigned-b...@kde.org |j...@kdenlive.org

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

[systemsettings] [Bug 387541] Tema da área de trabalho

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Reported as bug 387569.

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

[systemsettings] [Bug 387568] 387541

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Reported as bug 387569.

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

[krita] [Bug 387570] New: "Constrain proportions" resets the user selected "Anchor" in "Resize Canvas..." - (Krita 4.0.0-pre-alpha appimage)

[mvowada]

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

Bug ID: 387570
   Summary: "Constrain proportions" resets the user selected
"Anchor" in "Resize Canvas..." - (Krita
4.0.0-pre-alpha appimage)
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: freebo...@tiscali.it
  Target Milestone: ---

(Tested with Krita 4.0.0-pre-alpha appimage on Ubuntu 14.04)
"Constrain proportions" resets the user selected "Anchor" point in "Image" >
"Resize Canvas...". Steps to reproduce:

1. (main menu) "Image" > "Resize Canvas..." > just set a different "Anchor"
point than center
2. enable "Constrain proportions" (either by checking its checkbox -or- by
clicking the little chain icon)

Actual results: Krita resets the user selected "Anchor" point to center
Expected results: don't reset the user selected "Anchor" point when enabling
the "Constrain proportions" option

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

[systemsettings] [Bug 387569] New: Configurações do Sistema

[MAICON ROBERTO DE CAMPOS]

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

Bug ID: 387569
   Summary: Configurações do Sistema
   Product: systemsettings
   Version: 5.8.7
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: maicon.r.cam...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.7)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.102-34-default x86_64
Distribution: "openSUSE Leap 42.3"

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

- Unusual behavior I noticed:When you activate the "workspace theme" icon and
then the "desktop theme" icon, clicking on the last icon mentioned; dates
inexpertly.
I can no longer access the desktop theme, the rest of the System settings are
perfect.

- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: Configurações do Sistema (systemsettings5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7f022d4780 (LWP 5113))]

Thread 5 (Thread 0x7f7eccff1700 (LWP 5119)):
#0  0x7f7efe00720d in poll () at /lib64/libc.so.6
#1  0x7f7ef9c14314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7ef9c1442c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7efe9141ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f7efe8c1bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7efe6fcf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f7efca5f3d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f7efe701a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f7efa131744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f7efe00faad in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f7ed74a3700 (LWP 5118)):
#0  0x7f7efe00720d in poll () at /lib64/libc.so.6
#1  0x7f7ef9c14314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7ef9c1442c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7efe9141ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f7efe8c1bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7efe6fcf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f7efca5f3d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f7efe701a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f7efa131744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f7efe00faad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f7ee4720700 (LWP 5116)):
#0  0x7f7efe00328d in read () at /lib64/libc.so.6
#1  0x7f7ef56d5f55 in  () at /usr/lib64/tls/libnvidia-tls.so.340.104
#2  0x7f7ef9c54750 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7ef9c13e49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7ef9c142a8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f7ef9c1442c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f7efe9141ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f7efe8c1bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f7efe6fcf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f7eff218295 in  () at /usr/lib64/libQt5DBus.so.5
#10 0x7f7efe701a29 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f7efa131744 in start_thread () at /lib64/libpthread.so.0
#12 0x7f7efe00faad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f7eeddaa700 (LWP 5115)):
#0  0x7f7efe00720d in poll () at /lib64/libc.so.6
#1  0x7f7efa9a83e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f7efa9a9fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f7ef09370d9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f7efe701a29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f7efa131744 in start_thread () at /lib64/libpthread.so.0
#6  0x7f7efe00faad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7f022d4780 (LWP 5113)):
[KCrash Handler]
#6  0x7f7efdf5a8d7 in raise () at /lib64/libc.so.6
#7  0x7f7efdf5bcaa in abort () at /lib64/libc.so.6
#8  0x7f7efe6ed3be in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f7eff929bb0 in KPluginInfo::website() const () at
/usr/lib64/libKF5Service.so.5
#10 0x7f7ed7bdf380 in  () at /usr/lib64/libKF5Plasma.so.5
#11 0x7f7ed7bd6016 in Plasma::Theme::findInRectsCache(QString const&,
QString const&, QRectF&) const () at /usr/lib64/libKF5Plasma.so.5
#12 0x7f7ed7bced6e in  () at /usr/lib64/libKF5Plasma.so.5
#13 0x7f7ed7bcf094 in  () at /usr/lib64/libKF5Plasma.so.5
#14 0x7f7ed7bcfe60 in  () at /usr/lib64/libKF5Plasma.so.5
#15 0x7f7ed7bcffc0 in Plasma::Svg::setTheme(Plasma::Theme*) () at

[systemsettings] [Bug 387568] New: 387541

[MAICON ROBERTO DE CAMPOS]

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

Bug ID: 387568
   Summary: 387541
   Product: systemsettings
   Version: 5.8.7
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: maicon.r.cam...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.7)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.102-34-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:Application: Configurações do
Sistema (systemsettings5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3451f5c780 (LWP 4848))]

Thread 5 (Thread 0x7f341ccbd700 (LWP 5071)):
#0  0x7f344dc8f20d in poll () at /lib64/libc.so.6
#1  0x7f344989c314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f344989c42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f344e59c1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f344e549bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f344e384f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f344c6e73d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f344e389a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3449db9744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f344dc97aad in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f342740b700 (LWP 5070)):
#0  0x7f344dc8f20d in poll () at /lib64/libc.so.6
#1  0x7f344989c314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f344989c42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f344e59c1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f344e549bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f344e384f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f344c6e73d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f344e389a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3449db9744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f344dc97aad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f343446f700 (LWP 4850)):
#0  0x7f344dc8f20d in poll () at /lib64/libc.so.6
#1  0x7f344989c314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f344989c42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f344e59c1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f344e549bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f344e384f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f344eea0295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f344e389a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3449db9744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f344dc97aad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f343da32700 (LWP 4849)):
#0  0x7f344dc8f20d in poll () at /lib64/libc.so.6
#1  0x7f344a6303e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f344a631fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f34405bf0d9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f344e389a29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f3449db9744 in start_thread () at /lib64/libpthread.so.0
#6  0x7f344dc97aad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f3451f5c780 (LWP 4848)):
[KCrash Handler]
#6  0x7f344dbe28d7 in raise () at /lib64/libc.so.6
#7  0x7f344dbe3caa in abort () at /lib64/libc.so.6
#8  0x7f344e3753be in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f344f5b1bb0 in KPluginInfo::website() const () at
/usr/lib64/libKF5Service.so.5
#10 0x7f3427b47380 in  () at /usr/lib64/libKF5Plasma.so.5
#11 0x7f3427b3e016 in Plasma::Theme::findInRectsCache(QString const&,
QString const&, QRectF&) const () at /usr/lib64/libKF5Plasma.so.5
#12 0x7f3427b36d6e in  () at /usr/lib64/libKF5Plasma.so.5
#13 0x7f3427b37094 in  () at /usr/lib64/libKF5Plasma.so.5
#14 0x7f3427b37e60 in  () at /usr/lib64/libKF5Plasma.so.5
#15 0x7f3427b37fc0 in Plasma::Svg::setTheme(Plasma::Theme*) () at
/usr/lib64/libKF5Plasma.so.5
#16 0x7f341e4613c2 in  () at
/usr/lib64/qt5/plugins/kcms/kcm_desktoptheme.so
#17 0x7f341e463208 in  () at
/usr/lib64/qt5/plugins/kcms/kcm_desktoptheme.so
#18 0x7f341e46343b in  () at
/usr/lib64/qt5/plugins/kcms/kcm_desktoptheme.so
#19 0x7f344c6a36c9 in  () at /usr/lib64/libQt5Qml.so.5
#20 0x7f344c62dfec in  () at /usr/lib64/libQt5Qml.so.5
#21 0x7f344c62f2ec in  () at /usr/lib64/libQt5Qml.so.5
#22 0x7f344c62fc3f in QV4::QObjectMethod::callInternal(QV4::CallData*)
const () at /usr/lib64/libQt5Qml.so.5
#23 

[kmymoney] [Bug 382826] Price update failed

[Jack]

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

Jack  changed:

   What|Removed |Added

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

--- Comment #2 from Jack  ---
Should this be closed as a duplicate of bug 386462?

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

[gwenview] [Bug 387567] New: Panning and window resizing in gwenview is laggy

[george]

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

Bug ID: 387567
   Summary: Panning and window resizing in gwenview is laggy
   Product: gwenview
   Version: 17.04.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: stu...@anchev.net
  Target Milestone: ---

Panning images bigger than the viewport is stepped/laggy. (Panning the same
images in gimp is fast and fluid)

Also resizing the window of gwenview when the image is zoomed in is also laggy.

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

[kate] [Bug 387363] scrollbar preview is useless with normal Qt scrollbar

[Nate Graham]

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

--- Comment #8 from Nate Graham  ---
That seems sensible enough to me.

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

[kate] [Bug 387358] Kate reloads files from disk without confirmation

[bugzilla_noreply]

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

--- Comment #3 from nfx...@gmail.com ---
Yes, this is in git repos.

I definitely want the old behavior. There are a lot of cases where you can
actually lose the data forever, and in a few cases the reload notification
saved me. (Cases include e.g. git reset --hard.)

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

[kate] [Bug 386758] Large numbers of tabs become hard to access

[Dominik Haumann]

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

--- Comment #2 from Dominik Haumann  ---
The problem is that a large number of files is always hard to access with a
tabbar. That is why Kate always had (and still has) the vertical Documents
sidebar, listing all documents.

If you need quick access to all files, you should try using the quick open
feature through the shortcut CTRL+ALT+O, then type part of the file you want to
open, and select the file with cursors, and press enter. This is extremely fast
and scales if you get used to this workflow.

I agree that the tabbar will not solve your problem in your case, if you do not
use the keyboard for navigation. Then again, even if we change it to your
liking, then it is just a matter of +N open files and you will have the issue
again...

That said, we are of course also open for patches that improve Kate. So if you
have suggestions, best send patches :-)

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

[kate] [Bug 387363] scrollbar preview is useless with normal Qt scrollbar

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #7 from Dominik Haumann  ---
In fact, I do not think this is a duplicate: In case of the minimap, you indeed
want to jump to the final location. Maybe we should disallow the scrollbar
preview if a normal scrollbar is used. This would prevent this usability issue.
And then we could also simply jump to the correct location if the minimap is
enabled.

Would that be a good solution in your eyes?

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

[kate] [Bug 387358] Kate reloads files from disk without confirmation

[Dominik Haumann]

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

--- Comment #2 from Dominik Haumann  ---
How do the files on disk change?

Do you use git pull, and then the files change? Or is it not version
controlled?

I am asking, since for git controlled files, we do not show a reload message
anymore, since the reload is wanted in 99% of the time (i.e. many users like
this).

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

[krita] [Bug 387566] New: Python scripting UI - submenus

[Brendan]

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

Bug ID: 387566
   Summary: Python scripting UI - submenus
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Please provide a means to implement submenu items in the Python scripting menu.
At the moment it is already looking crowded.  See, eg, GIMP scripting, where
scripts use metadata to specify the menu/submenu structure that they will be
listed under. 

It may even make sense to permit Python scripts to appear under different menus
(eg File, Edit etc)

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

[elisa] [Bug 387435] Cannot reset the Rating filter

[Matthieu Gallien]

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

Matthieu Gallien  changed:

   What|Removed |Added

 Resolution|--- |LATER
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Matthieu Gallien  ---
An overhaul of the rating widget should help discover how to use it and provide
a long term solution to the reported problem.

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

[elisa] [Bug 387435] Cannot reset the Rating filter

[Alexander Potashev]

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

--- Comment #4 from Alexander Potashev  ---
(In reply to Matthieu Gallien from comment #3)
> A task has been created in Elisa workboard to improve the rating widget.
> Can I close this request given that it is already possible to deselect the
> first star even if it is not very good ?

ok

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

[elisa] [Bug 387435] Cannot reset the Rating filter

[Matthieu Gallien]

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

--- Comment #3 from Matthieu Gallien  ---
A task has been created in Elisa workboard to improve the rating widget.
Can I close this request given that it is already possible to deselect the
first star even if it is not very good ?

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

[KBibTeX] [Bug 386432] Broken google scholar search

[Thomas Fischer]

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

Thomas Fischer  changed:

   What|Removed |Added

  Latest Commit|9e95172cef34ac5852c51df15a0 |6c6ac4d48f6fa0b79f9e7594d09
   |bb1750cec7951   |53019296717d6

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

[KBibTeX] [Bug 386432] Broken google scholar search

[Thomas Fischer]

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

Thomas Fischer  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
   Version Fixed In||0.7
 Resolution|--- |FIXED

--- Comment #9 from Thomas Fischer  ---
No news on this bug. The proposed commits seem to fix Google Scholar, so
closing this bug. The commits fixing this bug will be incorporated into KBibTeX
0.7.

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

[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14

[bugzilla_noreply]

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

--- Comment #4 from weltq...@gmail.com ---
Problem pertains with Plasma 5.14.4 and Kernel 4.14.3. No problems when using
last LTS Kernel (4.9.66).
Last kernel version where it functioned was EOL 4.13 series.

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

[okular] [Bug 387424] Layers and Reviews categories use the same icon ("draw-freehand")

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
Ok, thanks!

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

[okular] [Bug 387424] Layers and Reviews categories use the same icon ("draw-freehand")

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #4 from Luigi Toscano  ---
(In reply to Nate Graham from comment #3)
> Sorry, I thought the bug would get closed automatically because I added
> "BUG: 387424" to the pPhabricator revision.

The line is "Summary: BUG: 387424", and that's probably why it was not parsed.

> In general, should I always ask which branch to commit to, or always commit
> to the latest stable branch and then merge to master, or do something else?

As Albert wrote: bugfixes (no features, no string changes (but exceptions are
possible), etc) can go directly to the stable branch (and then merge to
master). Anything else to master.

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

[okular] [Bug 387424] Layers and Reviews categories use the same icon ("draw-freehand")

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
Sorry, I thought the bug would get closed automatically because I added "BUG:
387424" to the pPhabricator revision.

In general, should I always ask which branch to commit to, or always commit to
the latest stable branch and then merge to master, or do something else?

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

[okular] [Bug 387424] Layers and Reviews categories use the same icon ("draw-freehand")

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #2 from Albert Astals Cid  ---
And you commited your patch, only to master and forgot to close this bug.

Please pay more attention to detail when developing.

Bugfixes like this go to stable branches.

I'll close the bug manually.

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

[frameworks-baloo] [Bug 382117] Exclude folders ignores wildcard patterns

[Morten Sjoegren]

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

Morten Sjoegren  changed:

   What|Removed |Added

 CC||kdest...@mabs.dk

--- Comment #1 from Morten Sjoegren  ---
I have the same problem.

I work with alot of nodejs and NativeScript projects, both results in alot of
files being indexed that shouldn't be.

My desktop becomes unusable when the baloo indexer is runnning, everything just
hangs. So I had to disable it.

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

[okular] [Bug 373388] allow user to have "merge highlighting and notes directly into pdf" as a setable option

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #2 from Albert Astals Cid  ---
Yeah, this is done anyway for next version.

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

[plasma-pa] [Bug 387565] Not possible to route music via bluetooth from phone, but works with pavucontrol

[H . H .]

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

--- Comment #3 from H.H.  ---
Created attachment 109197
  --> https://bugs.kde.org/attachment.cgi?id=109197=edit
PavuControl

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

[plasma-pa] [Bug 387565] Not possible to route music via bluetooth from phone, but works with pavucontrol

[H . H .]

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

--- Comment #1 from H.H.  ---
Created attachment 109195
  --> https://bugs.kde.org/attachment.cgi?id=109195=edit
Plasma Volume Mixer 1

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

[plasma-pa] [Bug 387565] Not possible to route music via bluetooth from phone, but works with pavucontrol

[H . H .]

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

--- Comment #2 from H.H.  ---
Created attachment 109196
  --> https://bugs.kde.org/attachment.cgi?id=109196=edit
Plasma Volume Mixer 2

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

[plasma-pa] [Bug 387565] New: Not possible to route music via bluetooth from phone, but works with pavucontrol

[H . H .]

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

Bug ID: 387565
   Summary: Not possible to route music via bluetooth from phone,
but works with pavucontrol
   Product: plasma-pa
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: cyberb...@gmx.de
CC: plasma-b...@kde.org
  Target Milestone: ---

I connected my android phone via bluetooth to my laptop, which is connected to
good speakers. I have multiple soundcards.

In plasma volume control, the phone only is displayed as a recording device. So
I cannot route it to a special sound card.

In pavucontrol it is displayed as a loopback playback device, for which I can
select the right sound card. Something like that should also work in kde.

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

[gcompris] [Bug 357248] SVG image looks like bad raster

[Jazeix Johnny]

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

Jazeix Johnny  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 CC||jaz...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jazeix Johnny  ---
Moved to phabricator: https://phabricator.kde.org/T7534

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

[gcompris] [Bug 377600] gcompris 0.70 64 bit flashes and closes

[Jazeix Johnny]

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

--- Comment #2 from Jazeix Johnny  ---
Hi,

can you try:
http://gcompris.net/download/qt/windows/gcompris-qt-0.81-win64-gcc.exe
It uses software renderer instead of openGL that was causing some crashes,
maybe it will fix yours.

Johnny

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

[okular] [Bug 387247] okular [12.17beta] crash upon highlighting text in pdfs

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #11 from Albert Astals Cid  ---
(In reply to Robby Engelmann from comment #3)
> The pdf I currently use is found here (too large to upload as attachment):
> http://onlinelibrary.wiley.com/doi/10.1002/eji.201646632/pdf

Please send us one with all your existing annotations and also describe clearly
which annotation you add and in which page.

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

[krita] [Bug 387564] New: Crash on closing Krita if a new window had been opened and closed previously

[Alvin Wong]

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

Bug ID: 387564
   Summary: Crash on closing Krita if a new window had been opened
and closed previously
   Product: krita
   Version: git master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: alvinhoc...@gmail.com
  Target Milestone: ---

Steps to reproduce:

1. Open file
2. Draw a few strokes
3. Window->New Window
4. Close the new window
5. Draw a few more strokes
6. Close Krita, discard changes

Might take more than a few tries...



krita.exe caused an Access Violation at location 07FED6532E01 in module
libkritaui.dll Reading from location .

AddrPC   Params
07FED6532E01 0E8D19E0 0022AA10 108E6670 
libkritaui.dll!updateGUI  [F:/dev/krita/new/src/libs/ui/kis_action_manager.cpp
@ 332]
   330: }
   331: 
>  332: action->setActionEnabled(enable);
   333: }
   334: }
07FED66A8E17 07FED7171480  063E0004000E 
libkritaui.dll!subWindowActivated 
[F:/dev/krita/new/src/libs/ui/KisMainWindow.cpp @ 1990]
  1988: 
  1989: updateCaption();
> 1990: d->actionManager()->updateGUI();
  1991: }
  1992: 
07FED66B3D35 0E8D8120   
libkritaui.dll!qt_static_metacall 
[F:/dev/krita/new/build_x64/build_krita/libs/ui/kritaui_autogen/include/moc_KisMainWindow.cpp
@ 346]
   344: case 51: _t->showErrorAndDie(); break;
   345: case 52: _t->setActiveView((*reinterpret_cast<
KisView*(*)>(_a[1]))); break;
>  346: case 53: _t->subWindowActivated(); break;
   347: case 54: _t->initializeGeometry(); break;
   348: case 55: _t->showManual(); break;
07FED6E7B2EA 0E8D8120 07FED5FF6924 0022ABE0 
Qt5Core.dll!activate 
[F:/dev/krita/new/build_x64/build_3rdparty/ext_qt/s/qtbase/src/corelib/kernel/qobject.cpp
@ 3766]
  3764:
qt_signal_spy_callback_set.slot_begin_callback(receiver, methodIndex, argv ?
argv : empty_argv);
  3765: 
> 3766: callFunction(receiver, QMetaObject::InvokeMetaMethod, 
> method_relative, argv ? argv : empty_argv);
  3767: 
  3768: if (qt_signal_spy_callback_set.slot_end_callback != 0)
07FED5FF2DE1 0080 0080 004B0308 
Qt5Widgets.dll!resetActiveWindow 
[F:/dev/krita/new/build_x64/build_3rdparty/ext_qt/b/qtbase/src/widgets/.moc/release/moc_qmdiarea.cpp
@ 308]
   306: {
   307: void *_a[] = { nullptr, const_cast(reinterpret_cast(&_t1)) };
>  308: QMetaObject::activate(this, , 0, _a);
   309: }
   310: QT_WARNING_POP
07FED5FF8998 0007 0040 01B300250007 
Qt5Widgets.dll!viewportEvent 
[F:/dev/krita/new/build_x64/build_3rdparty/ext_qt/s/qtbase/src/widgets/widgets/qmdiarea.cpp
@ 2432]
  2430: d->childWindows.removeAt(i);
  2431: d->indicesToActivatedChildren.removeAll(i);
> 2432: d->updateActiveWindow(i, activeRemoved);
  2433: d->arrangeMinimizedSubWindows();
  2434: break;
07FED6E4F62C 0001 07FEFD7313D2 0002 
Qt5Core.dll! ??  
[F:/dev/krita/new/build_x64/build_3rdparty/ext_qt/s/qtbase/src/corelib/kernel/qcoreapplication.cpp
@ 1129]
  1127: continue;
  1128: }
> 1129: if (obj->eventFilter(receiver, event))
  1130: return true;
  1131: }
07FED5E97B55 144EC6F0 07FEFD7310C8 0080 
Qt5Widgets.dll!notify_helper 
[F:/dev/krita/new/build_x64/build_3rdparty/ext_qt/s/qtbase/src/widgets/kernel/qapplication.cpp
@ 3718]
  3716: 
  3717: // send to all receiver event filters
> 3718: if (sendThroughObjectEventFilters(receiver, e))
  3719: return true;
  3720: 
07FED5E9EDF0 0004 07FED6C70DEF 140C8C40 
Qt5Widgets.dll!notify 
[F:/dev/krita/new/build_x64/build_3rdparty/ext_qt/s/qtbase/src/widgets/kernel/qapplication.cpp
@ 3481]
  3479: }
  3480: }
> 3481: res = d->notify_helper(w, e);
  3482: if (e->type() != QEvent::DragMove
  3483: #if QT_CONFIG(graphicsview)
07FED667D0F6 13D09B10 140C8C40 0002000A 
libkritaui.dll!notify  [F:/dev/krita/new/src/libs/ui/KisApplication.cpp @ 599]
   597: {
   598: try {
>  599: return QApplication::notify(receiver, event);
   600: } catch (std::exception ) {
   601: qWarning("Error %s sending event %i to object %s",
07FED6E50668 0022B0C0 0939A1C8 0030 
Qt5Core.dll! ??  
[F:/dev/krita/new/build_x64/build_3rdparty/ext_qt/s/qtbase/src/corelib/kernel/qcoreapplication.cpp
@ 1018]
  1016: if (!selfRequired)
  

[krita] [Bug 387561] Krita won't use KDE's color scheme

[Quiralta]

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

Quiralta  changed:

   What|Removed |Added

 CC||rjquira...@gmail.com

--- Comment #4 from Quiralta  ---
(In reply to acidrums4 from comment #0)
> Since 3.0.0 release, Krita won't use the color scheme set on KDE's
> "Settings" - nor won't let you select a custom/user color scheme that wasn't
> shipped with KDE.
> 
> For example, if you downloaded another color scheme from KDE's "Settings"
> and you set it so KDE will use it among KDE apps, Krita won't use it - even
> it won't list it under Krita -> Settings -> Themes so you can pick it from
> there. That will happen if you created a custom KDE color scheme and place
> it under ~/.kde4/share/apps/color-schemes/ (Frameworks 5 is still using that
> folder to load/save custom color schemes).

For the time been you can simply do it manually, copy the color schemes from
KDE directory into Krita's ~/.local/share/krita/color-schemes, that will give
you the missing options on Krita itself.

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

[krita] [Bug 387560] Krita won't use KDE file dialog within KDE

[Boudewijn Rempt]

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

--- Comment #4 from Boudewijn Rempt  ---
If checking that checkbox gave you kde dialogs, it is shipped with gentoo.

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

[systemsettings] [Bug 387541] Tema da área de trabalho

[MAICON CAMPOS]

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

MAICON CAMPOS  changed:

   What|Removed |Added

 CC||maicon.r.cam...@gmail.com
   Severity|normal  |critical
   Platform|Other   |openSUSE RPMs

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

[krita] [Bug 387563] not responding

[Ray]

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

--- Comment #2 from Ray  ---
I have been using Krita for about a year. in the last week or so it is very
unstable. I have tried loading the latest version but the same thing.

It freezes and says not responding when saving, merging layers, rotating
image.

I have been a big fan of Krita but getting very frustrated.

Ray

On Sun, Dec 3, 2017 at 6:40 PM, Boudewijn Rempt 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=387563
>
> Boudewijn Rempt  changed:
>
>What|Removed |Added
> 
> 
>Platform|Other   |MS Windows
>  CC||b...@valdyas.org
>  Status|UNCONFIRMED |NEEDSINFO
>  Resolution|--- |WAITINGFORINFO
>  OS|Linux   |MS Windows
>
> --- Comment #1 from Boudewijn Rempt  ---
> So, what _is_ your problem? It's excellent to give us the system info, but
> apart from that, what is up?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

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

[Dominik Haumann]

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

--- Comment #6 from Dominik Haumann  ---
Current state (as of 2017-12-03):

Unused keyword lists:
- "ample.xml" Unused keyword lists: QSet("icprops", "sgfct", "dvafct")
- "ansforth94.xml" Unused keyword lists: QSet("attention")
- "css.xml" Unused keyword lists: QSet("mediatypes_op")
- "dosbat.xml" Unused keyword lists: QSet("not", "else")
- "euphoria.xml" Unused keyword lists: QSet("constants")
- "freebasic.xml" Unused keyword lists: QSet("Assembly Operators")
- "fsharp.xml" Unused keyword lists: QSet("symbols")
- "ilerpg.xml" Unused keyword lists: QSet("pkeywords", "evalopcodes8")
- "metafont.xml" Unused keyword lists: QSet("notDefined", "EnvDelimiters")
- "pango.xml" Unused keyword lists: QSet("endtags", "tags", "int_attributes",
"plain_attributes", "color_attributes")
- "pony.xml" Unused keyword lists: QSet("literal", "types")
- "powershell.xml" Unused keyword lists: QSet("operators", "attributes")
- "prolog.xml" Unused keyword lists: QSet("lists ISO", "listing non-ISO",
"directives non-ISO", "lists non-ISO", "terms non-ISO", "streams deprecated",
"list+is_list non-ISO")
- "scss.xml" Unused keyword lists: QSet("mediatypes_op")
- "vhdl.xml" Unused keyword lists: QSet("forOrWhile", "directions")
- "xonotic-console.xml" Unused keyword lists: QSet("Aliases")
- "build/frameworks/syntax-highlighting/data/css-php.xml" Unused keyword lists:
QSet("mediatypes_op")

Unused contexts (attention: might be used via IncludeRules):
- "abc.xml" Unused contexts: QSet("Part")
- "ample.xml" Unused contexts: QSet("AfterHash", "Region Marker", "Outscoped")
- "ansys.xml" Unused contexts: QSet("functions_arg", "functions")
- "asterisk.xml" Unused contexts: QSet("Commentar 1")
- "boo.xml" Unused contexts: QSet("Single A-comment", "Single Q-comment")
- "cg.xml" Unused contexts: QSet("Commentar/Preprocessor", "Outscoped")
- "cisco.xml" Unused contexts: QSet("Parameter", "String")
- "dosbat.xml" Unused contexts: QSet("Assign")
- "elixir.xml" Unused contexts: QSet("Find closing block brace", "Comment
Line", "regexpr_rules")
- "email.xml" Unused contexts: QSet("body-context")
- "fasm.xml" Unused contexts: QSet("Preprocessor")
- "ferite.xml" Unused contexts: QSet("unknown 2", "unknown")
- "fgl-4gl.xml" Unused contexts: QSet("Normal Text 2", "Normal Text 3")
- "fgl-per.xml" Unused contexts: QSet("Normal Text 2", "Normal Text 3")
- "ftl.xml" Unused contexts: QSet("comment", "values")
- "gcc.xml" Unused contexts: QSet("GNUMacros")
- "haml.xml" Unused contexts: QSet("comment2", "Comment Line", "stringx",
"string", "comment0")
- "ilerpg.xml" Unused contexts: QSet("EvalOCCont")
- "isocpp.xml" Unused contexts: QSet("DetectIdentifierEnd")
- "jam.xml" Unused contexts: QSet("RuleDefinitionFull")
- "julia.xml" Unused contexts: QSet("curly", "squared", "nested")
- "kotlin.xml" Unused contexts: QSet("symbols")
- "latex.xml" Unused contexts: QSet("ToEndOfLine")
- "metafont.xml" Unused contexts: QSet("ToEndOfLine")
- "modula-2.xml" Unused contexts: QSet("Comment3")
- "nesc.xml" Unused contexts: QSet("Some Context2", "Some Context")
- "perl.xml" Unused contexts: QSet("package_qualified_blank", "end_handle")
- "povray.xml" Unused contexts: QSet("Commentar")
- "protobuf.xml" Unused contexts: QSet("Commentar")
- "ruby.xml" Unused contexts: QSet("Comment Line")
- "sisu.xml" Unused contexts: QSet("indent")
- "stata.xml" Unused contexts: QSet("Comment 2", "Base")
- "systemverilog.xml" Unused contexts: QSet("Define", "Outscoped")
- "tcsh.xml" Unused contexts: QSet("SubstCommand", "HereDoc", "SubstFile",
"AssignSubscr", "ProcessSubst")
- "varnishtest.xml" Unused contexts:
QSet("varnish_expectation_arg1_quoted-string",
"varnish_expectation_arg1_brace-string",
"varnish_expectation_arg1_unquoted-string")
- "varnishtest4.xml" Unused contexts:
QSet("varnish_expectation_arg1_quoted-string",
"varnish_expectation_arg1_brace-string",
"varnish_expectation_arg1_unquoted-string")
- "verilog.xml" Unused contexts: QSet("Some Context2", "Port")
- "xharbour.xml" Unused contexts: QSet("logic")
- "xmldebug.xml" Unused contexts: QSet("45:Enumeration or End", "51:unused")

Reference of non-existing keyword list:
- "asp.xml" Reference of non-existing keyword list: QSet("Others")
- "qml.xml" Reference of non-existing keyword list: QSet("keywords")
- "template-toolkit.xml" Reference of non-existing keyword list: QSet("Others")

Reference of non-existing itemData:
- "haml.xml" Reference of non-existing itemData attributes: QSet("Escaped
Text", "Ruby embedded in haml", "Array")
- "lilypond.xml" Reference of non-existing itemData attributes: QSet("Tremolo")
- "metafont.xml" Reference of non-existing itemData attributes: QSet("Tex",
"Bullet", "Verbatim")
- "relaxng.xml" Reference of non-existing itemData attributes: QSet("Entity
Reference")
- "rhtml.xml" Reference of non-existing itemData attributes: QSet("RUBY RAILS
ERB Text")
- "rmarkdown.xml" Reference of non-existing itemData attributes:
QSet("Markdown", "Document 

[gwenview] [Bug 381535] Left panel is not indented properly

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability

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

[krita] [Bug 387563] not responding

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

   Platform|Other   |MS Windows
 CC||b...@valdyas.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 OS|Linux   |MS Windows

--- Comment #1 from Boudewijn Rempt  ---
So, what _is_ your problem? It's excellent to give us the system info, but
apart from that, what is up?

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

[i18n] [Bug 387519] Dolphin context menu "Paste" text is confusing to first time users

[FabianR]

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

--- Comment #2 from FabianR  ---
Created attachment 109193
  --> https://bugs.kde.org/attachment.cgi?id=109193=edit
Dolphin copy-paste context menu

This is how it looks on a recent kde neon version.

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

[krita] [Bug 387563] New: not responding

[Ray]

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

Bug ID: 387563
   Summary: not responding
   Product: krita
   Version: 3.3.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: ray.ro...@gmail.com
  Target Milestone: ---

Version: 3.3.2

OS Information
  Build ABI: i386-little_endian-ilp32
  Build CPU: i386
  CPU: i386
  Kernel Type: winnt
  Kernel Version: 10.0.10586
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10

OpenGL Info 
  Vendor:  Google Inc. 
  Renderer:  "ANGLE (Mobile Intel(R) 4 Series Express Chipset Family (Microsoft
Corporation - WDDM 1.1) Direct3D11 vs_4_0 ps_4_0)" 
  Version:  "OpenGL ES 3.0 (ANGLE 2.1.0.8613f4946861)" 
  Shading language:  OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.8613f4946861) 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile 
QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) 
  Current format:QSurfaceFormat(version 3.0, options
QFlags(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples 0, swapBehavior QSurfaceFormat::SwapBehavior(DefaultSwapBehavior),
swapInterval 0, profile  QSurfaceFormat::OpenGLContextProfile(NoProfile)) 
 Version: 3.0
 Supports deprecated functions false 
 is OpenGL ES: true 

QPA OpenGL Detection Info 
  supportsDesktopGL: false 
  supportsAngleD3D11: true 
  isQtPreferAngle: true 
  overridePreferAngle: false 
== log ==
 createPlatformOpenGLContext QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile 
QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
Basic wglCreateContext gives version 1.1
OpenGL version too low
OpenGL 2.0 entry points not found
GPU features: QSet()
supportedRenderers GpuDescription(vendorId=0x8086, deviceId=0x2a42,
subSysId=0xc571144d, revision=9, driver: "igdumd32.dll", version=8.15.10.2702,
"Mobile Intel(R) 4 Series Express Chipset Family (Microsoft Corporation - WDDM
1.1)") renderer:  QFlags(0x2|0x4|0x8|0x20)
Qt: Using EGL from libEGL
Qt: Using OpenGL ES 2.0 from libGLESv2
create Created EGL display 0x2839df8 v 1 . 4
createPlatformOpenGLContext QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile 
QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
~QWindowsEGLStaticContext Releasing EGL display  0x2839df8 
== end log ==

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

[krita] [Bug 387561] Krita won't use KDE's color scheme

[acidrums4]

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

--- Comment #3 from acidrums4  ---
Sorry, but though I barely understand the technical reasons behind, I don't get
why you're marking this as "wontfix" nor why you're saying "this isn't a bug
but a feature".

Many other "cross platform" Non-KDE-but-Qt apps will obey KDE color schemes
(say Scribus, VLC, Otter...) and you're doing efforts to make Krita integrated
with other DE/OS. Why are you leaving KDE behind on this? I mean, at least the
option to select those user color schemes would be great.

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

[gwenview] [Bug 359909] Monitor profile should use relative colorimetric rendering intent by default

[DrSlony]

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

--- Comment #17 from DrSlony  ---
The red tape here seriously discourages further contribution to Gwenview. The
patch is banal, the concept is simple, and Gwenview's current behavior breaks
colors.

We will soon be celebrating the patch's first anniversary.

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

[krita] [Bug 387560] Krita won't use KDE file dialog within KDE

[acidrums4]

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

acidrums4  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #3 from acidrums4  ---
Didn't knew about that option under Krita's settings. Activated, KDE file
dialogs are back. Thanks!

I'm marking by myself this bug as "resolved invalid" but still I'm curious
about the "KDE platform integration plugin". Where can I get that? Why isn't it
shipped with the Gentoo ebuild?

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

[gwenview] [Bug 359909] Monitor profile should use relative colorimetric rendering intent by default

[Nate Graham]

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

--- Comment #16 from Nate Graham  ---
The patch is undergoing review, but it seems that not many of us have much of a
background in color profiles, so it could take a while.

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

[plasmashell] [Bug 387562] New: plasmashell crash after click on Application Launcher

[bugzilla_noreply]

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

Bug ID: 387562
   Summary: plasmashell crash after click on Application Launcher
   Product: plasmashell
   Version: 5.11.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lackohnili...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.4)

Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.9.66-1-lts x86_64
Distribution: "Arch Linux"

-- Information about the crash:
everytime I click on Application Launcher, plasmashell crashes

The crash can be reproduced every time.

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

Thread 11 (Thread 0x7fc362aca700 (LWP 7915)):
#0  0x7fc43a3d038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fc43b22065c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fc43eff50ba in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fc43eff5544 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fc43b21f1cb in  () at /usr/lib/libQt5Core.so.5
#5  0x7fc43a3ca08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fc43ab2947f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7fc368c32700 (LWP 7898)):
#0  0x7fc435407d64 in  () at /usr/lib/libglib-2.0.so.0
#1  0x7fc435407fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#2  0x7fc43b45e204 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7fc43b40199b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7fc43b21a27e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7fc36b60b1aa in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#6  0x7fc43b21f1cb in  () at /usr/lib/libQt5Core.so.5
#7  0x7fc43a3ca08a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fc43ab2947f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fc381806700 (LWP 7849)):
#0  0x7fc43a3d038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fc43b22065c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fc43eff50ba in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fc43eff5544 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fc43b21f1cb in  () at /usr/lib/libQt5Core.so.5
#5  0x7fc43a3ca08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fc43ab2947f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fc3826c2700 (LWP 7840)):
#0  0x7fc43ab1aa98 in read () at /usr/lib/libc.so.6
#1  0x7fc43542f521 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fc43540690b in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fc435407e76 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fc435407fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fc43b45e204 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fc43b40199b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fc43b21a27e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fc43ef73c1b in  () at /usr/lib/libQt5Quick.so.5
#9  0x7fc43b21f1cb in  () at /usr/lib/libQt5Core.so.5
#10 0x7fc43a3ca08a in start_thread () at /usr/lib/libpthread.so.0
#11 0x7fc43ab2947f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fc38c0b0700 (LWP 7810)):
#0  0x7fc43aaf71e0 in nanosleep () at /usr/lib/libc.so.6
#1  0x7fc43ab216c4 in usleep () at /usr/lib/libc.so.6
#2  0x7fc38f644d00 in  () at /usr/lib/xorg/modules/dri//fglrx_dri.so
#3  0x7fc38ed45332 in  () at /usr/lib/xorg/modules/dri//fglrx_dri.so
#4  0x7fc38ed45385 in  () at /usr/lib/xorg/modules/dri//fglrx_dri.so
#5  0x7fc43a3ca08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fc43ab2947f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fc416782700 (LWP 7809)):
#0  0x7fc43a3d038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fc440cc0ef7 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fc440cc0f39 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fc43a3ca08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fc43ab2947f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fc420b1a700 (LWP 7808)):
#0  0x7fc43ab1aa98 in read () at /usr/lib/libc.so.6
#1  0x7fc43542f521 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fc43540690b in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fc435407e76 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fc435407fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  

[krita] [Bug 387557] Chaos with working with shortcuts and simple operations on canvas.

[Boudewijn Rempt]

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

--- Comment #5 from Boudewijn Rempt  ---
Okay, then it's not a regression after moving to a new version of Qt. I haven't
seen these problems on other OS's (which I use more often), but I also haven't
seen them on OSX with 3.2.0, which is the last version I used to create work.

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

[krita] [Bug 387561] Krita won't use KDE's color scheme

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #2 from Boudewijn Rempt  ---
make it portable across operating systems, and this was one of the things that
got cut.

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

[krita] [Bug 387561] Krita won't use KDE's color scheme

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Your observation is correct, but it is not a bug, but intentional. We had to
fork part of a KDE frameworks library to

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

[dolphin] [Bug 371383] Tip:Add Bulk rename function

[Raghavendra kamath]

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

--- Comment #6 from Raghavendra kamath  ---
+1 for this feature

In addition to regex and other options there should also be an option to append
or prepend characters to exisiting filenames.

thank you.

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

[krita] [Bug 387557] Chaos with working with shortcuts and simple operations on canvas.

[Kamil]

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

--- Comment #4 from Kamil  ---
Yes, with 3.2.0 is even worst. Because when I paste to the new layer, I can't
switch to move tool at all. When I try to click in toolbar - while hover mouse
onto toolbar, tool move is selected (automatic) but without any click on
buttons I move out from toolbar, brush tool is selected instantly.
Zoom with wheel is broken after first keystroke.
Almost all shortcuts not working one after another, I must first switch between
another window/app then go back to Krita and then shortcut working.

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

[dolphin] [Bug 371383] Tip:Add Bulk rename function

[Raghavendra kamath]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

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

[krita] [Bug 387561] New: Krita won't use KDE's color scheme

[acidrums4]

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

Bug ID: 387561
   Summary: Krita won't use KDE's color scheme
   Product: krita
   Version: 3.3.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: acidrums4+st...@gmail.com
  Target Milestone: ---

Since 3.0.0 release, Krita won't use the color scheme set on KDE's "Settings" -
nor won't let you select a custom/user color scheme that wasn't shipped with
KDE.

For example, if you downloaded another color scheme from KDE's "Settings" and
you set it so KDE will use it among KDE apps, Krita won't use it - even it
won't list it under Krita -> Settings -> Themes so you can pick it from there.
That will happen if you created a custom KDE color scheme and place it under
~/.kde4/share/apps/color-schemes/ (Frameworks 5 is still using that folder to
load/save custom color schemes).

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

[krita] [Bug 387560] Krita won't use KDE file dialog within KDE

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #2 from wolthera  ---
Also make sure that you've checked "use native dialog" in the settings.
https://docs.krita.org/General_Settings#Miscellaneous

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

[okular] [Bug 338061] Okular modify a PDF content when highlight

[Brallan Aguilar]

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

--- Comment #12 from Brallan Aguilar  ---
(In reply to Henrik Fehlauer from comment #10)
> Thanks, Brallan (and sorry for misspelling your name). Can confirm that even
> with Poppler 0.61 the rendering gets in a bad state as soon as you add any
> annotation, and upon saving we get "Lost annotation on document save,
> something went wrong", but no crash on exit.
> 
> Extracting a single page with pdfseparate, pdftk and qpdf does not trigger
> the bug (tested with page 21, i.e. page 3 as written on the page). This
> means that as a workaround you can "repair" the PDF with "qpdf in.pdf
> out.pdf".
> 
> Albert: I think this problem might be in Poppler, as with Okular's MuPDF
> backend highlighting works fine.
> 
> Bug 334343 sounds similar.

I am using Poppler 0.61.1

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

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

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #5 from Dominik Haumann  ---
The following checks are now in the KSyntaxHighlighting Framework 5.42:

- Validate that for all attributes an itemData exists
  https://phabricator.kde.org/R216:2b8b664e15c0dd2945458d9373f2324e0c69056e

- Highlighting indexer: Check DetectChar and Detect2Chars
  https://phabricator.kde.org/R216:9d30439abda876601d8b6bb1ba2785b9d49e88a8

- Highlighting Indexer: Check for duplicate itemDatas
  https://phabricator.kde.org/R216:6b7cd0c8735aecf543abf54bf8dcabb783ce6b98

- Highlighting Indexer: Warn about duplicate contexts
  https://phabricator.kde.org/R216:621e282acbcb98d486e61f3d65d3293bf342489d

- Highlighting Indexer: Check keyword lists
  https://phabricator.kde.org/R216:463dfc78b4be7b11150420c076a8582be8b98607

- Try detecting unused contexts
  https://phabricator.kde.org/R216:cd7f2837aad12f18b908e7e733a891ed71fdd400

That is, the highlighting indexer has a lot of checks now, and currently raises
many many warnings. These should be fixed until the next 5.42 release.

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

[krita] [Bug 387560] Krita won't use KDE file dialog within KDE

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---
After making sure you've got the KDE platform integration plugin installed,
check whether Settings/Configure Krita/General/Miscelleneous/Enable native file
dialogs is enabled.

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

[krita] [Bug 387560] New: Krita won't use KDE file dialog within KDE

[acidrums4]

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

Bug ID: 387560
   Summary: Krita won't use KDE file dialog within KDE
   Product: krita
   Version: 3.3.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: acidrums4+st...@gmail.com
  Target Milestone: ---

On recent releases (I seem to recall 3.0.x won't have this issue), Krita won't
use KDE file dialog within KDE Frameworks 5 to open/save files, import layers
and stuff like that, but default Qt file dialog. Which is pretty annoying - no
previews, no bookmarks, no KIO...

Right now I'm under Gentoo GNU/Linux with KDE Frameworks 5.40, and Krita was
emerged with Qt 5.9.2. Let me know if you need something from my part. :)

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

[krita] [Bug 387557] Chaos with working with shortcuts and simple operations on canvas.

[Boudewijn Rempt]

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

--- Comment #3 from Boudewijn Rempt  ---
Oh, and can you check whether this also happen for you with an older version of
Krita, say 3.2.0 ? (https://download.kde.org/stable/krita/3.2.0/) You might
have to clean out your preferences first.

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

[krita] [Bug 387453] Stylus will become decalibrated with Krita open

[Boudewijn Rempt]

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

--- Comment #6 from Boudewijn Rempt  ---
No, that wouldn't matter. It's the same application. But like I said, it's most
likely a problem with the wacom tablet settings, not a bug in Krita. Offset
issues are _always_ a problem with the tablet's driver settings.

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

[krita] [Bug 384195] empty window on no action with toolbar new button

[Boudewijn Rempt]

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

--- Comment #8 from Boudewijn Rempt  ---
Sorry, it's still completely unclear what you're talking about. Does it make a
difference if you disable opengl?

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

[dolphin] [Bug 321575] Dolphin window title gets set to ugly strings ("Baloosearch -/", ) when displaying a Place that comes from a KIOSlave

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dol
   ||phin/702429ac8e64a5aff4e110
   ||a56f526b96ecb795fd

--- Comment #8 from Nate Graham  ---
Git commit 702429ac8e64a5aff4e110a56f526b96ecb795fd by Nathaniel Graham, on
behalf of Julian Schraner.
Committed on 03/12/2017 at 15:00.
Pushed by ngraham into branch 'master'.

Change window title when searching

Summary:
When you search for a file (e.g. "hello world") the window title of Dolphin
will now change to "Search for [input]" instead of "baloosearch - /".

Test Plan:
  - Disables it iself after search bar is hidden
  - Works with multiple word searches

Reviewers: #dolphin, ngraham, elvisangelaccio

Reviewed By: #dolphin, ngraham, elvisangelaccio

Subscribers: anthonyfieroni, elvisangelaccio, rkflx, emmanuelp, ngraham,
#dolphin

Tags: #dolphin

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

M  +10   -0src/dolphinmainwindow.cpp
M  +5-0src/dolphinviewcontainer.cpp
M  +2-0src/dolphinviewcontainer.h

https://commits.kde.org/dolphin/702429ac8e64a5aff4e110a56f526b96ecb795fd

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

[krita] [Bug 387557] Chaos with working with shortcuts and simple operations on canvas.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #2 from Boudewijn Rempt  ---
Um... Are you sure you can confirm it? I could imagine that this might be a
regression on OSX after updating the version of Qt to 5.10, but I haven't seen
something like this on other platforms, and I haven't seen this on OSX with
earlier releases.

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

[kmail2] [Bug 387559] New: KMail crashes when retrieving mails

[micu]

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

Bug ID: 387559
   Summary: KMail crashes when retrieving mails
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: micuin...@gmx.de
  Target Milestone: ---

Application: kmail (5.6.3)

Qt Version: 5.9.2
Frameworks Version: 5.40.0
Operating System: Linux 4.13.16-300.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

-- Information about the crash:
Its always similar. At a sudden moment, Kmail starts fetching all of the mails
(it has already retrieved) again, then filters go loco... gets slower and
slower and then it would crash.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0b79ba5340 (LWP 3104))]

Thread 25 (Thread 0x7f0a17263700 (LWP 9564)):
#0  0x7f0b6f41613a in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b6691d462 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f0b668f3519 in base::PosixDynamicThreadPool::WaitForTask() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f0b668f3a7b in base::(anonymous
namespace)::WorkerThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5
#4  0x7f0b668ec35b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f0a167f8700 (LWP 4502)):
#0  0x7f0b734eb8bb in poll () at /lib64/libc.so.6
#1  0x7f0b5e270ed9 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f0b5e270fec in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f0b7435635b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f0b743040ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f0b741558ba in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f0b74159b92 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#8  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f0ab4dab700 (LWP 3154)):
#0  0x7f0b6f415c3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b668eea15 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f0b668eeef7 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f0b668efc91 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f0b668ec35b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f0ab55ac700 (LWP 3153)):
#0  0x7f0b6f415c3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b668eea15 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f0b668eeef7 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f0b668efc91 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f0b668ec35b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f0ab6c4e700 (LWP 3152)):
#0  0x7f0b6f415c3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0b548dd604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f0b548dd649 in  () at /lib64/libQt5Script.so.5
#3  0x7f0b6f40f609 in start_thread () at /lib64/libpthread.so.0
#4  0x7f0b734f7e6f in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f0ae57fa700 (LWP 3138)):
#0  0x7f0b7350698c in __lll_lock_wait_private () at /lib64/libc.so.6
#1  0x7f0b73508764 in __fprintf_chk () at /lib64/libc.so.6
#2  0x7f0b57e463e0 in _warn_helper () at /lib64/libevent-2.0.so.5
#3  0x7f0b57e465a4 in event_warn () at /lib64/libevent-2.0.so.5
#4  0x7f0b57e4ad40 in epoll_dispatch () at /lib64/libevent-2.0.so.5
#5  0x7f0b57e358de in event_base_loop () at /lib64/libevent-2.0.so.5
#6  0x7f0b668bf849 in
base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#7  

[krita] [Bug 387557] Chaos with working with shortcuts and simple operations on canvas.

[wolthera]

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

wolthera  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||griffinval...@gmail.com
 Ever confirmed|0   |1

--- Comment #1 from wolthera  ---
This is all caused by the canvas not focussing right. We had fixed it in 2.9,
but the qt5 port for 3.0 brought it back again. 
I'll set it to confirmed because we know about it, but I am not sure if there's
anything we can do...

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

[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway

[Konstantin Kharlamov]

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

--- Comment #31 from Konstantin Kharlamov  ---
Just to mention an alternative people might not know about.

I used to like Dolphin. A week ago I stumbled upon fun stats of Archlinux
https://pkgstats.archlinux.de/fun turns out nowadays it's basically used by
nobody, however many peoples are prefer pcmanfm instead, which I've never
tried.

Long story short: pcmanfm with Qt backend upon running like
`XDG_CURRENT_DESKTOP=kde pcmanfm-qt` looks almost completely like Dolphin! And
guess what: upon entering a phone through mtp, and pressing F4 to open a
terminal I see in the path
"/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C008%5D/Phone"! It's using gvfs!

The only missing feature I noted so far is lack of split-screen — but I can't
remember the last time I used it, tabs are usually satisfy me; and I think I
can sacrifice it in exchange to ability of using a terminal and non-Qt apps on
every file system I'm entering.

Just make sure to install optional dependencies.

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

[Plasma Vault] [Bug 387543] Vault randomly disables

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 387546] Virtual keyboard on login screen is not available if there is no session

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Nate Graham  ---
This is an SDDM issue, which is tracked elsewhere:
https://github.com/sddm/sddm/issues/100

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

[plasmashell] [Bug 387546] Virtual keyboard on login screen is not available if there is no session

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords||usability
 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 387555] Open new instance on middle mouse click.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||pointedst...@zoho.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Nate Graham  ---
There is. :) Check out the plasmoid's settings:

On middle-click: [New Instance]

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

[okular] [Bug 368758] Printing with grayscale option do not work

[Dainius Masiliūnas]

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

Dainius Masiliūnas  changed:

   What|Removed |Added

 CC||past...@gmail.com

--- Comment #4 from Dainius Masiliūnas  ---
I can confirm both issues on openSUSE Leap 42.3. If either the greyscale option
worked OR the advanced printing tab was there, it would be possible to print
greyscale PDFs. As it is, CUPS defaults need to be changed instead, and that's
way too involved for such a simple task...

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

[kdeplasma-addons] [Bug 382320] Wikimedia Picture of the Day does not work

[bugzilla_noreply]

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

filtrationun...@gmail.com changed:

   What|Removed |Added

 CC||filtrationun...@gmail.com

--- Comment #2 from filtrationun...@gmail.com ---
I'm running Arch Linux with KDE Plasma 5.11.4, and I can also reproduce this
issue on my system. Like the others, i get a black screen when I try to select
it as my wallpaper.

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

[kajongg] [Bug 387517] fails with cannot find kmahjonggtileset traditional.desktop

[Wolfgang Rohdewald]

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

Wolfgang Rohdewald  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Wolfgang Rohdewald  ---


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

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

[kajongg] [Bug 366566] kajongg can't start due to an "AttributeError: 'Tileset'"

[Wolfgang Rohdewald]

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

Wolfgang Rohdewald  changed:

   What|Removed |Added

 CC||leon...@comcast.net

--- Comment #5 from Wolfgang Rohdewald  ---
*** Bug 387517 has been marked as a duplicate of this bug. ***

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

[frameworks-plasma] [Bug 387558] New: PlasmaComponents3.ComboBox doesnt align properly its items in RTL

[Michail Vourlakos]

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

Bug ID: 387558
   Summary: PlasmaComponents3.ComboBox doesnt align properly its
items in RTL
   Product: frameworks-plasma
   Version: 5.40.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: mvourla...@gmail.com
  Target Milestone: ---

The PlasmaComponents3.ComboBox doesnt align its list items to the right when
used in an RTL environment.

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

[i18n] [Bug 387519] Dolphin context menu "Paste" text is confusing to first time users

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

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

--- Comment #1 from Burkhard Lueck  ---
Welche Version von Dolphin und Ubuntu?
Bitte Bildschirmfotos hier hochladen

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

[frameworks-plasma] [Bug 387416] PlasmaComponents2.ComboBox in RTL shows its list items out of place

[Michail Vourlakos]

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

Michail Vourlakos  changed:

   What|Removed |Added

Summary|ComboBox in RTL shows its   |PlasmaComponents2.ComboBox
   |list items out of place |in RTL shows its list items
   ||out of place

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

[frameworks-plasma] [Bug 387415] PlasmaComponents2.ComboBox in RTL shows wrong the selected item

[Michail Vourlakos]

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

Michail Vourlakos  changed:

   What|Removed |Added

Summary|ComboBox in RTL shows wrong |PlasmaComponents2.ComboBox
   |the selected item   |in RTL shows wrong the
   ||selected item

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

[digikam] [Bug 387552] Digikam suddenly is unable to read or display any images

[bugzilla_noreply]

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

--- Comment #7 from caulier.gil...@gmail.com ---
AppImage is a binary bundle that you can run as well without to install
anything. All is included inside. The contents is just decompressed in memory.

It's explained here : https://en.wikipedia.org/wiki/AppImage

Just download it somewhere in your home directory, turn on the file executable
property, and just start it. digiKam will appear on screen. It's fully
compatible with your data, managed with your system based digiKam.

Gilles Caulier

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

[gwenview] [Bug 359909] Monitor profile should use relative colorimetric rendering intent by default

[DrSlony]

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

--- Comment #15 from DrSlony  ---
Status?

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

[LabPlot2] [Bug 387131] table column is inserted to the wrong side

[Alexander Semke]

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

Alexander Semke  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[LabPlot2] [Bug 386925] toolbars are not draggable by default

[Alexander Semke]

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

--- Comment #7 from Alexander Semke  ---
This should be fixed now. To check the current default behavior you'll need to
delete .config/labplot2rc file first and re-start the application.

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

[LabPlot2] [Bug 386925] toolbars are not draggable by default

[Alexander Semke]

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

Alexander Semke  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/lab
   ||plot/48fc7298cac8b694c5dd83
   ||954ec575bb8b6fcd4c
   Version Fixed In||2.5

--- Comment #6 from Alexander Semke  ---
Git commit 48fc7298cac8b694c5dd83954ec575bb8b6fcd4c by Alexander Semke.
Committed on 03/12/2017 at 13:15.
Pushed by asemke into branch 'master'.

Changed the default behaviour of the toolbars to:
1. show icons only
2. don't lock the toolbars
3. move the cartesian plot toolbar to the left toolbar area.
FIXED-IN: 2.5

M  +26   -22   src/kdefrontend/MainWin.cpp
M  +7-10   src/kdefrontend/labplot2ui.rc

https://commits.kde.org/labplot/48fc7298cac8b694c5dd83954ec575bb8b6fcd4c

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