[krunner] [Bug 386896] New: KRunner crash when trying to convert dkk to sek

[Alex]

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

Bug ID: 386896
   Summary: KRunner crash when trying to convert dkk to sek
   Product: krunner
   Version: 5.10.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: s...@kamstrup.com
  Target Milestone: ---

Application: krunner (5.10.5)

Qt Version: 5.7.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.9-200.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"

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

using alt+f2 wrote 1 dkk in <--- then crash

The computer had been in hybernation for 16 hours approx.

-- Backtrace:
Application: krunner (krunner), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f37c8af2380 (LWP 1438))]

Thread 14 (Thread 0x7f3765e4b700 (LWP 25643)):
#0  0x7f37c0fe1e0a in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37c51f62e3 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f37c51f2d5f in QThreadPoolThread::run() () at /lib64/libQt5Core.so.5
#3  0x7f37c51f5c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#4  0x7f37c0fdb36d in start_thread () at /lib64/libpthread.so.0
#5  0x7f37c45d8e1f in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f3766e4d700 (LWP 25641)):
#0  0x7f37bc53651d in g_source_iter_next () at /lib64/libglib-2.0.so.0
#1  0x7f37bc5389fb in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f37bc53949b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f37bc53967c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f37c53e8e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f37c539960a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f37c51f199a in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f37c51f5c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f37c0fdb36d in start_thread () at /lib64/libpthread.so.0
#9  0x7f37c45d8e1f in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f378534e700 (LWP 10571)):
#0  0x7f37c0fe190b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37c51f63fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f37a04d40d5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f37a04d8048 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f37a04d329d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f37a04d5f8b in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f37c51f5c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f37c0fdb36d in start_thread () at /lib64/libpthread.so.0
#8  0x7f37c45d8e1f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f3785b4f700 (LWP 10570)):
#0  0x7f37c0fe190b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37c51f63fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f37a04d40d5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f37a04d8048 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f37a04d329d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f37a04d5f8b in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f37c51f5c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f37c0fdb36d in start_thread () at /lib64/libpthread.so.0
#8  0x7f37c45d8e1f in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f3786350700 (LWP 10569)):
#0  0x7f37c0fe190b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f37c51f63fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f37a04d40d5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f37a04d8048 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f37a04d329d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f37a04d5f8b in 

[krita] [Bug 386889] Blue colour shows up as orange wqhen drawing

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

   Platform|Windows CE  |MS Windows
 Status|UNCONFIRMED |NEEDSINFO
 OS|Windows CE  |MS Windows
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Boudewijn Rempt  ---
Needinfo

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

[krita] [Bug 386889] Blue colour shows up as orange wqhen drawing

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

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

As you can see from the screenshot, this displays fine. Could you attach a
screenshot of the color management tab in the settings dialog?

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

[LabPlot2] [Bug 386796] changing decimal precision has no immediate effect

[Alexander Semke]

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

Alexander Semke  changed:

   What|Removed |Added

   Version Fixed In||2.5
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/lab
   ||plot/5deaa913d65d646ff5bb37
   ||6ef605d3696b94be86
 Resolution|--- |FIXED

--- Comment #1 from Alexander Semke  ---
Git commit 5deaa913d65d646ff5bb376ef605d3696b94be86 by Alexander Semke.
Committed on 14/11/2017 at 07:46.
Pushed by asemke into branch 'master'.

Update values in the spreadsheet view on precision changes in the columns.
FIXED-IN: 2.5

M  +22   -2src/backend/spreadsheet/SpreadsheetModel.cpp
M  +1-0src/backend/spreadsheet/SpreadsheetModel.h

https://commits.kde.org/labplot/5deaa913d65d646ff5bb376ef605d3696b94be86

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

[Breeze] [Bug 386895] dialog-password grossly oversized in gtk3

[Andrew Chen]

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

--- Comment #1 from Andrew Chen  ---
Actually now that I think about it again, maybe the icon should've never been
used in a taskbar in the first place. Although Adwaita's version of this icons
is in-line with the other toolbar icon sizes.

Could you let me know what you think about this. If this is indeed a misuse of
the icon, I'll go file a bug with blueman instead.

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

[valgrind] [Bug 208052] strlcpy error when n = 0

[Ivo Raisr]

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

--- Comment #7 from Ivo Raisr  ---
Tom, would you mind integrating the fix into Valgrind source code base at this
point? Alternatively, I could do it myself - just let me know.

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

[kmymoney] [Bug 386893] kmymoney language setting

[Thomas Baumgart]

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

--- Comment #1 from Thomas Baumgart  ---
The reason for that is: you're using a KDE4 program in a KF5 environment which
stores the information about the language and date format in a different
position than the prior version does it. So the KDE4 libs have no chance to
find that information and work with the standard settings.

"KMMY 'Settings' / Settings language KDE" does not work for the same reason.
You can try to get a KDE4 version of the systemsettings for Mageia 7. I found
the KF5 version as systemsettings5 here on my openSUSE system. The resp. KDE4
version is called systemsettings. Hope that helps.

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

[Breeze] [Bug 386895] New: dialog-password grossly oversized in gtk3

[Andrew Chen]

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

Bug ID: 386895
   Summary: dialog-password grossly oversized in gtk3
   Product: Breeze
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: andrew.chuanye.c...@gmail.com
CC: kain...@gmail.com
  Target Milestone: ---

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

Gtk3 applications that use the `dialog-password` icon have them displayed much
larger than other icons.

`blueman-manager` is used as an example here. In the screenshot, notice the 3rd
icon from the left in the taskbar.

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

[yakuake] [Bug 367634] Copying text with ctrl+ins does not work

[Constantine]

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

Constantine  changed:

   What|Removed |Added

 CC||constantine@gmail.com

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

[amarok] [Bug 386894] New: Amarok crashes upon start

[bugzilla_noreply]

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

Bug ID: 386894
   Summary: Amarok crashes upon start
   Product: amarok
   Version: 2.8.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: ravibo...@gmail.com
  Target Milestone: 2.9

Application: amarok (2.8.0)
KDE Platform Version: 4.14.33
Qt Version: 4.8.6
Operating System: Linux 4.4.92-31-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
Env: Opensuse Leap 42.3
Current user applications in the system - Firefox, Thunderbird, Dolphin,
CherryTree (note), WiFi, HPLIP service, KNotes, Plasma5.
Start Amarok. It crashes and displays error message. 
Re-start Amarok. It crashes and displays error message.

The crash can be reproduced every time.

-- Backtrace:
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f86dbfb8940 (LWP 17702))]

Thread 2 (Thread 0x7f86b3b58700 (LWP 17704)):
#0  0x7f86c5e3ba40 in pa_pstream_unref () at
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#1  0x7f86c5e3bfc7 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7f86c5e3c84a in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#3  0x7f86cfd0aa14 in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0
#4  0x7f86cfd0adea in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#5  0x7f86cfd0ae90 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#6  0x7f86cfd19006 in  () at /usr/lib64/libpulse.so.0
#7  0x7f86c5e4c408 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#8  0x7f86d7883744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f86d8c78aad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f86dbfb8940 (LWP 17702)):
[KCrash Handler]
#6  0x7f86b7d98ce7 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#7  0x7f86b7d98ee2 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#8  0x7f86b7d98697 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#9  0x7f86b7d992f2 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#10 0x7f86b7d8f973 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#11 0x7f86d86ba19e in  () at /usr/lib64/libphonon.so.4
#12 0x7f86d86ba855 in Phonon::Path::reconnect(Phonon::MediaNode*,
Phonon::MediaNode*) () at /usr/lib64/libphonon.so.4
#13 0x7f86d86bb10d in Phonon::createPath(Phonon::MediaNode*,
Phonon::MediaNode*) () at /usr/lib64/libphonon.so.4
#14 0x7f86db9a2b10 in EngineController::initializePhonon() () at
/usr/lib64/libamaroklib.so.1
#15 0x7f86db9a91c5 in  () at /usr/lib64/libamaroklib.so.1
#16 0x7f86d9446218 in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const () at
/usr/lib64/libQtCore.so.4
#17 0x7f86d94486f2 in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at
/usr/lib64/libQtCore.so.4
#18 0x7f86dba690fd in  () at /usr/lib64/libamaroklib.so.1
#19 0x7f86dba69161 in  () at /usr/lib64/libamaroklib.so.1
#20 0x7f86db99babd in App::continueInit() () at
/usr/lib64/libamaroklib.so.1
#21 0x7f86db99cc16 in App::App() () at /usr/lib64/libamaroklib.so.1
#22 0x00407f97 in  ()
#23 0x7f86d8baf6e5 in __libc_start_main () at /lib64/libc.so.6
#24 0x004080c9 in _start ()

Reported using DrKonqi

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

[kwin] [Bug 386490] Crash in Atomic DRM setting

[Bhushan Shah]

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

--- Comment #12 from Bhushan Shah  ---
Can I re-open this bug, the commit above fixes the issue of crash, but right
after starting plasma kwin_wayland is hung, and there is no mouse pointer as
well, so it's still impossible to interact with Plasma.. or should I report
separate bug?

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

[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time

[bugzilla_noreply]

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

tprotopope...@gmail.com changed:

   What|Removed |Added

 CC||tprotopope...@gmail.com

--- Comment #16 from tprotopope...@gmail.com ---
I also have this problem. Note that this also affects the work day times etc.
Go to `Configure Korganizer > Date and Time'. All the times there cannot be set
to AM times either. Switching to US_en is a workaround (but I agree it is not a
very good one if you don't want to use the US's non-standard date scheme
(mm/dd/yy)).

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

[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

[Eric Fontaine]

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

Eric Fontaine  changed:

   What|Removed |Added

 CC||ericrfonta...@hotmail.com

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

[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

[Eric Fontaine]

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

--- Comment #2 from Eric Fontaine  ---
Created attachment 108855
  --> https://bugs.kde.org/attachment.cgi?id=108855=edit
New crash information added by DrKonqi

plasmashell (5.11.3) using Qt 5.9.2

I've just reproduced the crash, and this time am using the crash reporting
assistant.

(Note again I'm on fresh install of Parabola Linux, the FOSS-only version of
Arch)

-- Backtrace (Reduced):
#5  0x7fd62018cc81 in wl_proxy_create_wrapper () at
/usr/lib/libwayland-client.so.0
#6  0x7fd60258185a in  () at /usr/lib/libEGL_mesa.so.0
#7  0x7fd60256e6df in  () at /usr/lib/libEGL_mesa.so.0
#8  0x7fd602bba722 in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#9  0x7fd602bb8bce in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so

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

[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

[Eric Fontaine]

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

--- Comment #1 from Eric Fontaine  ---
I can reproduce with these following steps:

1. Right click panel
2. select "Panel Settings"
3. press the "+ Add Widgets" button

at this point the background wallpaper flickers (although all my other
applications that are up don't seem to be affected).

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

[kmymoney] [Bug 386893] New: kmymoney language setting

[lajoie]

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

Bug ID: 386893
   Summary: kmymoney language setting
   Product: kmymoney
   Version: 4.8.1
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: arbed...@gmail.com
  Target Milestone: ---

Created attachment 108854
  --> https://bugs.kde.org/attachment.cgi?id=108854=edit
settings KDE

i am on Mageia 7
noyau : 4.14.0-desktop-1.mga7
arch: 64-bit  Bureau : KDE5 
Yesterday i loaded the update KMyMoney 4. 8. 1 from Mageia deposits.
The KMMY controls are now in English. I verified KDE settings => everything is
OK in french. I raised several times. KMMY remains in English !!!
In KMMY 'Settings' / Settings language KDE=> nothing happens (no window to
adjust the language).
My others KDE softs works correctly in french.
I also have another problem that could be related to the previous one:
the dates are in English:  / MM / DD instead of DD / MM /  in French.

It's seems quite différent from bug 69332.

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

[plasmashell] [Bug 386892] New: Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

[Eric Fontaine]

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

Bug ID: 386892
   Summary: Segfault on fresh install of parabola (Arch) linux
with kde plasa wayland
   Product: plasmashell
   Version: 5.11.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: ericrfonta...@hotmail.com
  Target Milestone: 1.0

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

I right clicked on panel and tried to add wiget, then screen briefly flashed,
and the error reporter appeared and produced the attached kcrash.txt

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

[digikam] [Bug 386891] New: Crashed while adding pictures

[Ryk van Donselaar]

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

Bug ID: 386891
   Summary: Crashed while adding pictures
   Product: digikam
   Version: 4.14.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: ry...@gmx.com
  Target Milestone: ---

Application: digikam (4.14.0)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.10.0-38-generic x86_64
Distribution: Linux Mint 18.2 Sonya

-- Information about the crash:
- What I was doing when the application crashed: I was importing pictures for
the first time after a brand new install. tried several times but at about 46%
it crashes every time. Linux Mint 18.2 64 bit.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f440de9fb80 (LWP 11738))]

Thread 3 (Thread 0x7f43d88fb700 (LWP 11748)):
#0  0x7f44068df70d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f43fea2838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f43fea2849c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f44075842ce in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f440755218f in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f44075524f5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f4407441549 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f4407532223 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f4407443e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f440335e6ba in start_thread (arg=0x7f43d88fb700) at
pthread_create.c:333
#10 0x7f44068eb3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f43d90fc700 (LWP 11747)):
[KCrash Handler]
#6  0x7f4406819428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f440681b02a in __GI_abort () at abort.c:89
#8  0x7f440685b7ea in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7f4406974e98 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7f440686437a in malloc_printerr (ar_ptr=,
ptr=, str=0x7f4406974f10 "free(): invalid next size (fast)",
action=3) at malloc.c:5006
#10 _int_free (av=, p=, have_lock=0) at
malloc.c:3867
#11 0x7f440686853c in __GI___libc_free (mem=) at
malloc.c:2968
#12 0x7f440604f4e1 in Exiv2::RiffVideo::nikonTagsHandler() () from
/usr/lib/x86_64-linux-gnu/libexiv2.so.14
#13 0x7f4406052c75 in Exiv2::RiffVideo::decodeBlock() () from
/usr/lib/x86_64-linux-gnu/libexiv2.so.14
#14 0x7f4406052898 in Exiv2::RiffVideo::tagDecoder(Exiv2::DataBuf&,
unsigned long) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.14
#15 0x7f4406052c75 in Exiv2::RiffVideo::decodeBlock() () from
/usr/lib/x86_64-linux-gnu/libexiv2.so.14
#16 0x7f44060530a8 in Exiv2::RiffVideo::readMetadata() () from
/usr/lib/x86_64-linux-gnu/libexiv2.so.14
#17 0x7f440d679605 in KExiv2Iface::KExiv2::load(QString const&) const ()
from /usr/lib/libkexiv2.so.11
#18 0x7f440b9ef616 in Digikam::DMetadata::load(QString const&) const ()
from /usr/lib/digikam/libdigikamcore.so.4.14.0
#19 0x7f440bfa07a7 in Digikam::ImageScanner::loadFromDisk() () from
/usr/lib/digikam/libdigikamdatabase.so.4.14.0
#20 0x7f440bfa09e0 in Digikam::ImageScanner::newFile(int) () from
/usr/lib/digikam/libdigikamdatabase.so.4.14.0
#21 0x7f440bf30f2b in Digikam::CollectionScanner::scanNewFile(QFileInfo
const&, int) () from /usr/lib/digikam/libdigikamdatabase.so.4.14.0
#22 0x7f440bf35997 in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.14.0
#23 0x7f440bf35886 in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.14.0
#24 0x7f440bf35886 in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.14.0
#25 0x7f440bf35886 in
Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&,
QString const&) () from /usr/lib/digikam/libdigikamdatabase.so.4.14.0
#26 0x7f440bf36443 in
Digikam::CollectionScanner::scanAlbumRoot(Digikam::CollectionLocation const&)
() from /usr/lib/digikam/libdigikamdatabase.so.4.14.0
#27 0x7f440bf374eb in Digikam::CollectionScanner::completeScan() () from

[kstars] [Bug 386782] Simulation is much faster than requested "2 mins" per second

[Jasem Mutlaq]

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

Jasem Mutlaq  changed:

   What|Removed |Added

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

--- Comment #1 from Jasem Mutlaq  ---
It's fixed in GIT now. Interesting solving this bug also resolved another
decade old bug as well, completely unrelated to this.

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

[kwin] [Bug 386888] kwin crashes while switching tasks using task manager

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---
Crashes in the Radeon driver. Please report to Radeon developers.

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

[digikam] [Bug 381432] Olympus ORF files to DNG conversion fails in Windows 10

[Paul]

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

--- Comment #29 from Paul  ---
I emailed a file link to you through Dropbox. I hope it helps!

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

[plasmashell] [Bug 386890] New: Can't start Plasma after installing Nvidia driver

[Joe Shields]

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

Bug ID: 386890
   Summary: Can't start Plasma after installing Nvidia driver
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: joedang...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.10.0-37-generic x86_64
Distribution: Ubuntu 16.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I'd just finished running Nvidia's driver installer. When logging into Plasma,
I immediately got a black screen and the bug tracker came up.
- Custom settings of the application:
I had allowed the install script to change the X configuration.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f37ee49d8c0 (LWP 6143))]

Thread 6 (Thread 0x7f37bd6b3700 (LWP 6152)):
#0  0x7f37e8b9d70d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f37e593138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f37e593149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f37e94ca7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f37e9471b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f37e928e834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f37ec4bced6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f37e92937be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f37e837f6ba in start_thread (arg=0x7f37bd6b3700) at
pthread_create.c:333
#9  0x7f37e8ba93dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f37b700 (LWP 6151)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f37ededbbd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f37ededbc19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f37e837f6ba in start_thread (arg=0x7f37b700) at
pthread_create.c:333
#4  0x7f37e8ba93dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f37c59f7700 (LWP 6150)):
#0  0x7ffc627d6a4b in clock_gettime ()
#1  0x7f37e8bb7836 in __GI___clock_gettime (clock_id=1, tp=0x7f37c59f6a50)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f37e9343b86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f37e94c8279 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f37e94c87e5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f37e94c9bce in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f37e593091d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f37e59312bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f37e593149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f37e94ca7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f37e9471b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f37e928e834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f37ebb363c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f37e92937be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f37e837f6ba in start_thread (arg=0x7f37c59f7700) at
pthread_create.c:333
#15 0x7f37e8ba93dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f37c78a6700 (LWP 6149)):
#0  0x7f37e928b93a in QMutex::lock() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f37e94c9d6f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f37e593091d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f37e59312bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f37e593149c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f37e94ca7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f37e9471b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f37e928e834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f37ebb363c5 in ?? () from 

[digikam] [Bug 381432] Olympus ORF files to DNG conversion fails in Windows 10

[bugzilla_noreply]

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

--- Comment #28 from caulier.gil...@gmail.com ---
yes, an ORF test file will help. Please share through an Internet cloud link

Thanks in advance

Gilles Caulier

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

[krita] [Bug 386889] New: Blue colour shows up as orange wqhen drawing

[Katherine Villarreal]

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

Bug ID: 386889
   Summary: Blue colour shows up as orange wqhen drawing
   Product: krita
   Version: 3.3.2
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Color models
  Assignee: krita-bugs-n...@kde.org
  Reporter: keepitgr...@gmail.com
  Target Milestone: ---

Created attachment 108852
  --> https://bugs.kde.org/attachment.cgi?id=108852=edit
If you look at the file attached in the Krita application, the orange flowers
are blue. At least that's how it is for me.

When I draw with blue selected it shows up as orange, when I draw with orange
it shows up as blue. When the picture is saved the colours then revert and now
what looked blue in the Krita application is orange and what looked orange is
now blue. Its the shades red-yellow and purple to blue that do this.

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

[Breeze] [Bug 384473] Missing icon sizes

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/bre
   ||eze-icons/cb168d3a0bd568797
   ||46fc534e4cf09648ae2d7cc
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Nate Graham  ---
Git commit cb168d3a0bd56879746fc534e4cf09648ae2d7cc by Nathaniel Graham.
Committed on 14/11/2017 at 03:02.
Pushed by ngraham into branch 'master'.

Add missing icon sizes

Summary:
Add missing scalable icon sizes

Test Plan:
Add missing scalable icon sizes at index.theme. If not all size are covered by
scalable icons some desktop environment other than PLASMA may show icons not
properly scaled.

See also bug #384473 for more detailed explaination and screenshot
https://bugs.kde.org/show_bug.cgi?id=384473

Update:
>From the MATE Desktop environment you may use 'Appearance' (the binary is 
>(/usr/bin/mate-appearance-properties) to modify its look-and-feel. There is 
>not a Breeze theme listed there here but from the 'Theme' tab you may click 
>the 'Customise...' button and from the new window you may select 'Breeze' in 
>'Controls', 'Pointer' and 'Icons' tabs.

{F5404548}

Then restart MATE to see the applied changes. Here is how MATE desktop appears
with Breeze icons before the changes.

{F5402571}

As you may see (scalable) icons from Breeze theme are bigger than others (which
are .svg icons too). In caja application this is even more evident especially
for 'computer' icon

{F5402644}

After I inspected the caja code I found it uses scalable icons and I found the
problem is Breeze does not provide for some icon sizes for some scalable icons
required  by caja so it uses a bigger sized icon (all works fine with MATE
default theme, of course). So I modified the Breeze index.theme as reported
here and ,as you may see from the screenshots below, all icons are of the right
size

desktop
{F5403169}

caja
{F5403202}

I used the fixed Breeze theme both in PLASMA and LXQt and I not noticed any
differences from before to after so I believe my changes are not dangerous for
other DE.

Reviewers: #breeze, #vdg, jensreuterberg, #frameworks, hein, mandian

Reviewed By: hein

Subscribers: andreask, hein, ngraham, cfeck, #frameworks

Tags: #frameworks, #breeze

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

M  +4-4icons-dark/index.theme
M  +3-3icons/index.theme

https://commits.kde.org/breeze-icons/cb168d3a0bd56879746fc534e4cf09648ae2d7cc

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

[frameworks-kio] [Bug 386859] KF5 KIO runs /usr/bin/kioslave instead of /usr/libexec/kf5/kioslave, crashing the kdelibs3 kioslave

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
Great, thanks!

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

[frameworks-kio] [Bug 386859] KF5 KIO runs /usr/bin/kioslave instead of /usr/libexec/kf5/kioslave, crashing the kdelibs3 kioslave

[Kevin Kofler]

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

--- Comment #3 from Kevin Kofler  ---
https://phabricator.kde.org/D8810

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

[kmime] [Bug 386831] Dataloss warnings in kmime_headers, charfreqtest and test_charfreq

[Michael Pyne]

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

Michael Pyne  changed:

   What|Removed |Added

Version|5.40.0  |unspecified
   Assignee|mp...@kde.org   |kdepim-b...@kde.org
Product|frameworks-kcoreaddons  |kmime
  Component|general |general

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

[kmime] [Bug 386830] Dataloss warning in kmime_charfreq.cpp

[Michael Pyne]

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

Michael Pyne  changed:

   What|Removed |Added

  Component|general |general
Product|frameworks-kcoreaddons  |kmime
   Assignee|mp...@kde.org   |kdepim-b...@kde.org
Version|5.40.0  |unspecified

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

[digikam] [Bug 381432] Olympus ORF files to DNG conversion fails in Windows 10

[Paul]

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

--- Comment #27 from Paul  ---
Would it be helpful to have an orf file to test with?

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

[digikam] [Bug 381432] Olympus ORF files to DNG conversion fails in Windows 10

[Paul]

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

--- Comment #26 from Paul  ---
Sorry, pressed save too soon on that comment. 

The problem persists with 5.8pr

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

[digikam] [Bug 381432] Olympus ORF files to DNG conversion fails in Windows 10

[Paul]

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

--- Comment #25 from Paul  ---
Sorry to report... the issue persists.

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

[plasmashell] [Bug 386839] High memory utilization for plasmshell

[Kedar]

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

--- Comment #4 from Kedar  ---
Issue seems to have fixed. Looks like openshot was the culprit. I uninstalled
it  and gave the machine a restart and since then it is working as usual.

I also changed from the onboard display card to ATI / Radeon display card. The
performance has since improved dramatically. Can see that the displays don't
lag any more. I guess it was more of a display card issue for me.

Cheers

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

[kwin] [Bug 386888] New: kwin crashes while switching tasks using task manager

[bugzilla_noreply]

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

Bug ID: 386888
   Summary: kwin crashes while switching tasks using task manager
   Product: kwin
   Version: 5.11.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: keith.miy...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.11.3)

Qt Version: 5.9.2
Frameworks Version: 5.40.0
Operating System: Linux 4.13.12-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
hitting alt-tab (task manager) to switch tabs multiple times in a row (holding
alt, hitting tab several times) crashes kwin. Tried using breeze theme and the
tab preview theme and both cause the same behavior.

The crash can be reproduced every time.

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

Thread 13 (Thread 0x7f96fa6d1700 (LWP 4253)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f96e8c26ddc in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f96e8c26ce8 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f96c67fc700 (LWP 2183)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f97175e3ef7 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f97175e3f39 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f96c77fe700 (LWP 2179)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f96e8c26ddc in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f96e8c26ce8 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f96c7fff700 (LWP 2178)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f96e8c26ddc in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f96e8c26ce8 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f96dcf77700 (LWP 2177)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f96e8c26ddc in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f96e8c26ce8 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f96dd778700 (LWP 2176)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f96e8c26ddc in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f96e8c26ce8 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f96ddf79700 (LWP 2175)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f96e8c26ddc in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f96e8c26ce8 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f96de77a700 (LWP 2174)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f96e8c26ddc in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f96e8c26ce8 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f96df180700 (LWP 2173)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f96e8c26ddc in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f96e8c26ce8 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f971402a08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f971b09a47f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f96dfac2700 (LWP 2172)):
#0  0x7f971403038d in pthread_cond_wait@@GLIBC_2.3.2 () at

[wacomtablet] [Bug 338453] Hide the wacom plasmoid if no tablet is connected.

[Weng Xuetian]

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

Weng Xuetian  changed:

   What|Removed |Added

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

--- Comment #2 from Weng Xuetian  ---
(In reply to Valeriy Malov from comment #1)
> This has been implemented in KF5 port of the plasmoid, right? It seems to
> autohide when I disconnect my tablet.

Yeah.. and probably it's implemented by me.

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

[kwalletmanager] [Bug 386887] New: Kwallet should more clearly identify the program asking for access

[sparhawk]

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

Bug ID: 386887
   Summary: Kwallet should more clearly identify the program
asking for access
   Product: kwalletmanager
   Version: 17.08
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: kdeb...@plast.id.au
  Target Milestone: ---

Created attachment 108851
  --> https://bugs.kde.org/attachment.cgi?id=108851=edit
Screenshot of -m in kwalletmanager

I just upgraded kwallet in Arch Linux from 5.39.0-1 -> 5.40.0-1.

I was then asked if "-m" could access kwallet. This sounded suspicious, but it
was just kwallet failing to correctly identify/parse the following command
clearly.

python -m keyring get mbsync foo@bar

In the past, I think it listed this as "Python program", which was better, but
could still be clearer.

https://i.imgur.com/BrP3VNa.png

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

[kdevplatform] [Bug 386863] patchreview button text size

[RJVB]

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

--- Comment #2 from RJVB  ---
Can't discuss taste, but the difference here is most likely not a result of
using a different widget style but of using the general font as the toolbar
font too.

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

[frameworks-bluez-qt] [Bug 386886] New: Bluez-Qt leaks rfkill file descriptor into all child processes of KDE session

[bugzilla_noreply]

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

Bug ID: 386886
   Summary: Bluez-Qt leaks rfkill file descriptor into all child
processes of KDE session
   Product: frameworks-bluez-qt
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: o.freyerm...@googlemail.com
  Target Milestone: ---

All processes in my KDE session have an extra FD open pointing to 
/dev/rfkill, easily checkable with:
ls -la /proc/self/fd
lrwx-- 1 olifre olifre 64 14. Nov 00:11 0 -> /dev/pts/13
lrwx-- 1 olifre olifre 64 14. Nov 00:11 1 -> /dev/pts/13
lrwx-- 1 olifre olifre 64 14. Nov 00:11 2 -> /dev/pts/13
lr-x-- 1 olifre olifre 64 14. Nov 00:11 30 -> /dev/rfkill

Fix is simple and put up here:
https://phabricator.kde.org/D8806

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

[kde] [Bug 386560] apt-get upgrade fails: kde-cli-tools dpkg reports depends newer than installed for other pkgs

[Michael]

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

--- Comment #6 from Michael  ---
apt-get install --reinstall --install-suggests plasma-desktop is what worked.

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 plasma-desktop-dbg : Depends: plasma-desktop (=
4:5.6.5-0ubuntu1~ubuntu16.04~ppa1) but 4:5.8.8-0ubuntu1~ubuntu16.04~ppa1 is to
be installed
  Recommends: qtbase5-dbg but it is not going to be
installed
 plasma-discover : Conflicts: plasma-discover-private but
5.6.5-0ubuntu1~ubuntu16.04~ppa3 is to be installed
   Conflicts: plasma-discover-updater but
5.6.5-0ubuntu1~ubuntu16.04~ppa3 is to be installed
 plasma-discover-common : Conflicts: plasma-discover-private but
5.6.5-0ubuntu1~ubuntu16.04~ppa3 is to be installed
  Conflicts: plasma-discover-updater but
5.6.5-0ubuntu1~ubuntu16.04~ppa3 is to be installed
 plasma-framework-dbg : Depends: libkf5plasma5 (= 5.18.0-0ubuntu1.1) but
5.36.0-0ubuntu2~ubuntu16.04~ppa1 is to be installed
Depends: libkf5plasmaquick5 (= 5.18.0-0ubuntu1.1) but
5.36.0-0ubuntu2~ubuntu16.04~ppa1 is to be installed
 plasma-integration-dbg : Depends: plasma-integration (=
5.6.5-0ubuntu1~ubuntu16.04~ppa1) but 5.8.8-0ubuntu1~ubuntu16.04~ppa1 is to be
installed
  Recommends: qtbase5-dbg but it is not going to be
installed
 plasma-nm-dbg : Depends: plasma-nm (= 4:5.6.5-0ubuntu1~ubuntu16.04~ppa1) but
4:5.8.8-0ubuntu1~ubuntu16.04~ppa1 is to be installed
 Recommends: qtbase5-dbg but it is not going to be installed
 plasma-pa-dbg : Depends: plasma-pa (= 4:5.6.5-0ubuntu1~ubuntu16.04~ppa1) but
4:5.8.8-0ubuntu1~ubuntu16.04~ppa1 is to be installed
 plasma-sdk-dbg : Depends: plasma-sdk (= 4:5.6.5-0ubuntu1~ubuntu16.04~ppa1) but
4:5.8.8-0ubuntu1~ubuntu16.04~ppa1 is to be installed
 plasma-workspace : Conflicts: plasma-systray-legacy but
0~git20151104-ded1538-2 is to be installed
 plasma-workspace-dbg : Depends: plasma-workspace (=
4:5.6.5-0ubuntu1~ubuntu16.04~ppa1) but 4:5.8.8-0ubuntu1~ubuntu16.04~ppa2 is to
be installed or
 libweather-ion7 (=
4:5.6.5-0ubuntu1~ubuntu16.04~ppa1) but 4:5.8.8-0ubuntu1~ubuntu16.04~ppa2 is to
be installed or
 libplasma-geolocation-interface5 (=
4:5.6.5-0ubuntu1~ubuntu16.04~ppa1) but 4:5.8.8-0ubuntu1~ubuntu16.04~ppa2 is to
be installed or
 libkworkspace5-5 (=
4:5.6.5-0ubuntu1~ubuntu16.04~ppa1) but 4:5.8.8-0ubuntu1~ubuntu16.04~ppa2 is to
be installed
E: Unable to correct problems, you have held broken packages.

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

[digikam] [Bug 385863] Trojita email client

[Andrius]

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

--- Comment #4 from Andrius  ---
Maik can you take a look at their dev's response please
https://bugs.kde.org/show_bug.cgi?id=386860

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

[LabPlot2] [Bug 386885] New: importing Origin projects misses fit plots

[Uwe Stöhr]

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

Bug ID: 386885
   Summary: importing Origin projects misses fit plots
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

Created attachment 108850
  --> https://bugs.kde.org/attachment.cgi?id=108850=edit
Hysteresis fit orogon project file

With LabPlot 2.5RC2 I tried to import the attached small Origin project file.

result:
- data is imported
- the information if a column represents an x or y value or if it represents an
x or y error is missing
- no plots are imported
- no fits are imported, therefore also the used fit function and the fit
results are missing

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

[kwin] [Bug 380428] Touch screen gestures don't work

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

 CC||stefan.bruens@rwth-aachen.d
   ||e

--- Comment #12 from Stefan Brüns  ---
I see the same on my XPS 12 (9Q33, Haswell generation)

I think this not a problem of the actual code, but the config is neither
properly saved and applied:

1. Setting an edge action is not saved to .kwinrc when hitting "Apply" in the
"Touch screen" systemsettings

Workaround: Set the edge action, go to the "Display and Monitor" ->
"Compositor" setting, modify something, hit "Apply" -> kwinrc is updated

---
grep -A5 TouchEdges ~/.config/kwinrc 
[TouchEdges]
Bottom=ShowDesktop
Left=None
Right=None
Top=ShowDesktop
---

2. The new config is not directly applied, but works after "kwin_x11 --replace
&"

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

[LabPlot2] [Bug 386884] incorrect spacing in export window

[Uwe Stöhr]

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

--- Comment #2 from Uwe Stöhr  ---
Created attachment 108849
  --> https://bugs.kde.org/attachment.cgi?id=108849=edit
export window with again shown options

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

[LabPlot2] [Bug 386884] incorrect spacing in export window

[Uwe Stöhr]

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

--- Comment #1 from Uwe Stöhr  ---
Created attachment 108848
  --> https://bugs.kde.org/attachment.cgi?id=108848=edit
export window with hidden options

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

[LabPlot2] [Bug 386884] New: incorrect spacing in export window

[Uwe Stöhr]

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

Bug ID: 386884
   Summary: incorrect spacing in export window
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: frontend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

Created attachment 108847
  --> https://bugs.kde.org/attachment.cgi?id=108847=edit
Initial export window

- create a plot
- use the menu File -> Export

Attached is how the export windows looks. You can see that the spacing is not
correct since there is too much space.

- now click on "Hide option"

Now the spacing is correct, see attached.

- now click on Show Options

result: now the export window looks correct, see attached.

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

[LabPlot2] [Bug 386883] Missing file extension when exporting to file

[Uwe Stöhr]

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

--- Comment #1 from Uwe Stöhr  ---
Created attachment 108846
  --> https://bugs.kde.org/attachment.cgi?id=108846=edit
export to file window without preset file extension

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

[LabPlot2] [Bug 386883] New: Missing file extension when exporting to file

[Uwe Stöhr]

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

Bug ID: 386883
   Summary: Missing file extension when exporting to file
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: frontend
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

- create a plot
- use the menu File -> Export

The predefined export format is PDF.

- now click the button behind the File name field to specify a path and
filename for the PDF export

result: Instead of the PDF export window a generic one named "Export to file"
(see attached) pops up. There you cannot set a file type.

- thus enter "test.pdf"

This works but since the specified file format is PDF, the export window should
have the .pdf extension as preset.

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

[LabPlot2] [Bug 386882] New: Printing from print preview fails but exports to PDF

[Uwe Stöhr]

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

Bug ID: 386882
   Summary: Printing from print preview fails but exports to PDF
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

- create a plot
- use the menu File -> Print Preview
- in the appearing print preview window use the rightmost button (shows a
printer icon) to print

result: unexpectedly a window called "Export to PDF" appears

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

[LabPlot2] [Bug 386881] New: Printing does not work

[Uwe Stöhr]

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

Bug ID: 386881
   Summary: Printing does not work
   Product: LabPlot2
   Version: latest
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alexander.se...@web.de
  Reporter: uwesto...@web.de
  Target Milestone: ---

- create a  plot
- use the menu File -> Print

result: nothing happens

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

[kdevplatform] [Bug 386863] patchreview button text size

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||aleix...@kde.org

--- Comment #1 from Aleix Pol  ---
Created attachment 108845
  --> https://bugs.kde.org/attachment.cgi?id=108845=edit
On breeze

Yes, on breeze it looks much nicer

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

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

[Austin English]

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

--- Comment #7 from Austin English  ---
Re arm/thumb:
 so you said it's arm encoding. I noticed that configure.ac
requires thumb? Do both get used?
 yes, most of wine should be arm
 what's thumb used for?
 Windows Apps are Thumb-2, and to call into such functions we need the
command "blx" (branch and link while exchanging instruction set if necessary,
or something like that), if the compiler targets non-thumb (e.g. arm-only) it
doesn't like bx and blx
 so it targets both arm and thumb?
 the compiler, yes
 the instruction I'm checking this right now
 the instruction encoding seems to be exactly the same for both arm
and thumb-2
 it's definitely arm

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

[konsole] [Bug 357255] cannot copy via CTRL+INS

[Sic Volo]

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

Sic Volo  changed:

   What|Removed |Added

 CC||sickv...@gmail.com

--- Comment #7 from Sic Volo  ---
Add ctrl+ins/shift+ins to alternate copy/paste shortcuts in konsole. That
solved it for me.

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

[yakuake] [Bug 384813] Yakuake keyboard shortcuts not following KDE global shortcuts.

[Sic Volo]

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

--- Comment #1 from Sic Volo  ---
Confirming the same behaviour on 3.0.4 with KDE from kubuntu 17.10

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

[yakuake] [Bug 367634] Copying text with ctrl+ins does not work

[Sic Volo]

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

Sic Volo  changed:

   What|Removed |Added

 CC||sickv...@gmail.com

--- Comment #5 from Sic Volo  ---
I dont think the bug is related to 
https://bugs.kde.org/show_bug.cgi?id=357255, but rather to
https://bugs.kde.org/show_bug.cgi?id=384813.

I was able to fix #357255 by simply adding ctrl+ins, shift+ins to the list of
shortcuts in konsole, however these shortcuts are not being inherited by
yakuake, so no luck making it work in yakuake 3.0.4 on kubuntu 17.10 distro.

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

[kdenlive] [Bug 386877] moving a clip with speed effect in a group of clips on timeline breaks playback of the clip

[bugzilla_noreply]

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

--- Comment #1 from mikko.rap...@iki.fi ---
Sigh, sorry. Spoke too soon. Now I have ghost clips, unpreviewable still
images, broken in and out points etc on timeline. Disabling and enabling speed
effect from the clip causes it reduce in length and in and out points go way
off the originals.

All this seems be caused by moving groups of clips which have speed effect
applied. Tried to use undo changes to this but it seemed to make things worse.

Need to manually redo large sections of timeline now. Similar things happened
already several years ago sadly. I think speed effect needs a big fat warning
sign.

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

[plasmashell] [Bug 386880] Plasma doesn't automatically detect system tray widgets

[Mircea Kitsune]

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

Mircea Kitsune  changed:

   What|Removed |Added

 CC||sonichedgehog_hyperblast00@
   ||yahoo.com

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

[plasmashell] [Bug 386880] New: Plasma doesn't automatically detect system tray widgets

[Mircea Kitsune]

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

Bug ID: 386880
   Summary: Plasma doesn't automatically detect system tray
widgets
   Product: plasmashell
   Version: 5.11.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: sonichedgehog_hyperblas...@yahoo.com
  Target Milestone: 1.0

Plasma does not automatically detect whether widgets with system tray entries
are added or removed, for the purpose of making them available in the tray.
This leads to situations where, even if a plasmoid has
X-Plasma-NotificationArea=true in its metadata.desktop file, the feature
doesn't work because the file ~/.local/share/plasma/plasmoids/kpluginindex.json
is outdated. To get the widget listed under General - Extra Items in the system
tray settings, you must manually run the following command after installing
your widget:

kpackagetool5 --generate-index -t Plasma/Applet

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

[yakuake] [Bug 384813] Yakuake keyboard shortcuts not following KDE global shortcuts.

[Sic Volo]

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

Sic Volo  changed:

   What|Removed |Added

 CC||sickv...@gmail.com

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

[kwin] [Bug 386370] kwin randomly crashes when switching desktops

[bugzilla_noreply]

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

--- Comment #5 from malek@gmail.com ---
Sorry, I did not notice the first comment. I am just facing the same bug as Mr.
Jesse. And guys here too: https://bbs.archlinux.org/viewtopic.php?id=231042.

I will try to search a way how to provide a kwin backtrace.

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

[kde] [Bug 386560] apt-get upgrade fails: kde-cli-tools dpkg reports depends newer than installed for other pkgs

[Michael]

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

--- Comment #5 from Michael  ---
Upgrades now work because I did the following:

I decided to continue with the updates and did:
apt-get install --reinstall --install-suggests plasma*

This install went OK and when it asked for the choice of lightdm or sddm, this
time I chose lightdm. Although this dm continues to ask for login whereas I did
not need to previously (I had set it that way) many of the previous problems
(especially updates) have resolved. 

kde_X11 continues to crash often whenever a window already on screen is
overwritten and then the dm has to redraw it behind the new window. The larger
the windows, the more likely it is to happen.

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

[krita] [Bug 386620] Canvas framerate limiter might not be working as intended

[Bernhard Liebl]

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

--- Comment #2 from Bernhard Liebl  ---
see https://phabricator.kde.org/D8804

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

[Craft] [Bug 386879] New: install updated version of libofx

[Uwe Stöhr]

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

Bug ID: 386879
   Summary: install updated version of libofx
   Product: Craft
   Version: master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Core
  Assignee: vonr...@kde.org
  Reporter: uwesto...@web.de
CC: kde-wind...@kde.org
  Target Milestone: ---

craft libofx

installs version 0.9.10 of libofx. This version was released more than 3 years
ago. Therefore upgrading to version 0.9.12 should be considered.

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

[Craft] [Bug 386878] New: install updated version of libfftw

[Uwe Stöhr]

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

Bug ID: 386878
   Summary: install updated version of libfftw
   Product: Craft
   Version: master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Core
  Assignee: vonr...@kde.org
  Reporter: uwesto...@web.de
CC: kde-wind...@kde.org
  Target Milestone: ---

craft libfftw

installs version 3.2.2 of FFTW. This version cannot be compiled with MSCV2015,
see
https://bugs.kde.org/show_bug.cgi?id=386788

Therefore craft should install the latest version FFTW 3.3.7 or at least a
3.3.x version.

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

[kdenlive] [Bug 386877] New: moving a clip with speed effect in a group of clips on timeline breaks playback of the clip

[bugzilla_noreply]

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

Bug ID: 386877
   Summary: moving a clip with speed effect in a group of clips on
timeline breaks playback of the clip
   Product: kdenlive
   Version: 17.08.1
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: mikko.rap...@iki.fi
  Target Milestone: ---

kdenlive master branch commit v17.08.1-35-gf2b70a17c

I have always had various problems with speed effect ranging from silent time
line corruption, unmovable clips, broken end and out points to crashes during
playback. Thus I was a bit afraid of using it on my latest project. These were
an indication that a serious rewrite and tests was needed for the effect at
that time (past 7 years or so).

Luckily I had not seen time line corruptions or crashes now, but the playback
of clips with speed effect on time line stops, if the clip is moved in a group.
Have not tested if this happens in rendering to but at least on the instant
preview this happens every time on my project. Tested various 17.08.1 git
commits and they all behave like this.

Workaround is to enable and disable the effect provided that there is enough
space on timeline for that.

But no crashes or timeline corruptions, woohoo! :)

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

[plasmashell] [Bug 372789] Plasma freezes with black screen when logging out

[Ongun Kanat]

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

Ongun Kanat  changed:

   What|Removed |Added

 CC||ongun.ka...@gmail.com

--- Comment #22 from Ongun Kanat  ---
I also have been encountering this problem for a while. It is still
reproducible for me on Plasma 5.11.3. The system becomes unresponsive to
keyboard so Ctrl+Alt+F(1,2,3...) doesn't work. My attempts to gain keyboard
input via magic SysRq combination Alt+SysRq+R then trying to switch TTYs were
also failed. I don't have ssh on my machine so after an unsuccessful trial I
continue the sequence of Alt + SysRq + {R,E,I,S,U,B} and reboot my laptop.

The problem is always reproducible and occurs when I log out from X11 session
and log in to Wayland. If I log in to Wayland session directly after a reboot,
logout and reboot works correctly. Thinking it might be a cleanup/clean exit
issue I have recorded process trees as well as the journalctl log you can find
them below. The second clue that it might be a cleanup issue is that
systemd/dbus residue after logging out X11 session. Killing all the processes
from previous session results in correct behavior. It still might be a SDDM
issue though. Unfortunately I cannot test Wayland session without systemd.

Journalctl of failed wayland session: https://paste.kde.org/prrtatzh7
Process Trees:
Before logging in to X11: https://paste.kde.org/p1snpbw04
In X11 session: https://paste.kde.org/p01hfjadd
After logging out from X11: https://paste.kde.org/pgd3wnxwl

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

[frameworks-kactivities-stats] [Bug 386788] installing libfftw via craft fails

[Uwe Stöhr]

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

Uwe Stöhr  changed:

   What|Removed |Added

 CC||plasma-b...@kde.org
Version|master  |5.40.0
 Resolution|--- |INVALID
  Component|Core|general
 Status|UNCONFIRMED |RESOLVED
Product|Craft   |frameworks-kactivities-stat
   ||s

--- Comment #1 from Uwe Stöhr  ---
OK, I see now that it is a bug in FFTW 3.2.2 but the current version is FFTW
3.3.7.
I'll open a new bug report to get the latest version of fftw via craft.

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

[ksmserver] [Bug 344967] 99 minute maximum for lock screen

[Jason Mancini]

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

Jason Mancini  changed:

   What|Removed |Added

 CC||jayrus...@hotmail.com

--- Comment #15 from Jason Mancini  ---
> What are you from the gnome project?

This comment was golden.  The fact that the dev cannot accept/comprehend that
people use software in a various manners is quite alarming.

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

[digikam] [Bug 386874] Cursor changes to forbidden symbol when dragging picture(s) to map

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.8.0
 CC||metzping...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Maik Qualmann  ---
There is already a workaround for this problem in digiKam-5.8.0. Question:
Which Qt version is used? I close this bug.

Maik

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

[kdevelop] [Bug 386876] New: After click in entry found in "Code Browser" there is no cursor in editor (no focus)

[Piotr Mierzwinski]

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

Bug ID: 386876
   Summary: After click in entry found in "Code Browser" there is
no cursor in editor (no focus)
   Product: kdevelop
   Version: git master
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

As in subject.
I have some results in "Code browser" after use function "Show uses", when I
click in found entry I get this file with highlighted line, but there is no
focus in editor. I need to click in editor to get focus. IMO this second
clicking is annoying 

Tested with Appimage package, nightly build version 5.2, downloaded at
2017/11/13 at 09:14pm

Appimage has been run in following env.: Plasma 5.11.3, Qt-5.9.2

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

[frameworks-kio] [Bug 386875] New: Dataloss warning in kcookiejartest and kioslavetest

[Uwe Stöhr]

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

Bug ID: 386875
   Summary: Dataloss warning in kcookiejartest and kioslavetest
   Product: frameworks-kio
   Version: 5.40.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: uwesto...@web.de
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I get:

[807/877] Building CXX object
autotests\kcookiejar\CMakeFiles\kcookiejartest.dir\kcookiejartest.cpp.obj
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\kcookiejar\kcookiejartest.cpp(233):
warning C4267: 'initializing
': conversion from 'size_t' to 'int', possible loss of data

and:

[831/877] Building CXX object
tests\CMakeFiles\kioslavetest.dir\kioslavetest.cpp.obj
R:\build\frameworks\tier3\kio\work\kio-5.40.0\tests\kioslavetest.cpp(453):
warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of
data

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

[digikam] [Bug 386874] New: Cursor changes to forbidden symbol when dragging picture(s) to map

[bugzilla_noreply]

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

Bug ID: 386874
   Summary: Cursor changes to forbidden symbol when dragging
picture(s) to map
   Product: digikam
   Version: 5.7.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Geolocation-Editor
  Assignee: digikam-bugs-n...@kde.org
  Reporter: silvanoc...@gmx.net
  Target Milestone: ---

When I drag one or more pictures to a map (no matter if Marble Virtual Globe or
Google Maps) the mouse cursor changes to an arrow with a small
forbidden/prohibited symbol next to it and no click (neither left nor right)
generates a reaction. The only possibility to restore the normal mouse cursor
is pressing the Escape key.

I've tried different combinations and the result is the same.

This is the output in the console when starting Digikam from the command line:

digikam.geoiface: Loading GPS bookmarks from
"/home/silvavlis/.local/share/digikam/geobookmarks.xml"
digikam.geoiface: "setting backend marble"
digikam.geoiface: "HYBRID"
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: "backend marble is ready!"
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: "marble:900"
digikam.geoiface: 900 3500 900
digikam.geoiface: "backend marble is ready!"
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: "marble:900"
digikam.geoiface: 900 3500 900
digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => 
QDateTime(2017-08-20 15:28:19.000 CEST Qt::TimeSpec(LocalTime))
digikam.geoiface: 
digikam.general: 0 1
digikam.geoiface: "level 5: 0 non empty tiles sorted into 0 clusters (0
searched)"
digikam.geoiface: "level 5: 0 non empty tiles sorted into 0 clusters (0
searched)"
digikam.geoiface: "level 5: 0 non empty tiles sorted into 0 clusters (0
searched)"

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

[frameworks-kio] [Bug 386873] New: Dataloss warnings in http.cpp

[Uwe Stöhr]

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

Bug ID: 386873
   Summary: Dataloss warnings in http.cpp
   Product: frameworks-kio
   Version: 5.40.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: uwesto...@web.de
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I get:

[793/877] Building CXX object
autotests\http\CMakeFiles\httpobjecttest.dir\__\__\src\ioslaves\http\http.cpp.obj
r:\build\frameworks\tier3\kio\work\kio-5.40.0\src\ioslaves\http\parsinghelpers.cpp(281):
warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of
data
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\ioslaves\http\http.cpp(2033):
warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss
of data
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\ioslaves\http\http.cpp(2033):
warning C4267: 'initializing': conversion from 'size_t' to 'const int',
possible loss of data
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\ioslaves\http\http.cpp(2054):
warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of
data
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\ioslaves\http\http.cpp(2861):
warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\ioslaves\http\http.cpp(4197):
warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss
of data
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\ioslaves\http\http.cpp(4197):
warning C4267: 'initializing': conversion from 'size_t' to 'const int',
possible loss of data
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\ioslaves\http\http.cpp(4216):
warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss
of data

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

[frameworks-kio] [Bug 386872] New: Deprecation warning for KUrlNavigator::url

[Uwe Stöhr]

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

Bug ID: 386872
   Summary: Deprecation warning for KUrlNavigator::url
   Product: frameworks-kio
   Version: 5.40.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: uwesto...@web.de
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I get:

[767/877] Building CXX object
autotests\CMakeFiles\kurlnavigatortest.dir\kurlnavigatortest.cpp.obj
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\kurlnavigatortest.cpp(252):
warning C4996: 'KUrlNavigator::url':
 was declared deprecated
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\filewidgets\kurlnavigator.h(310):
note: see declaration of 'KUrlNavigator::url'
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\kurlnavigatortest.cpp(262):
warning C4996: 'KUrlNavigator::url':
 was declared deprecated
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\filewidgets\kurlnavigator.h(310):
note: see declaration of 'KUrlNavigator::url'

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

[frameworks-kio] [Bug 386871] New: Deprecation warning for KFileWidget::setSelection

[Uwe Stöhr]

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

Bug ID: 386871
   Summary: Deprecation warning for KFileWidget::setSelection
   Product: frameworks-kio
   Version: 5.40.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: uwesto...@web.de
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I get:

[727/877] Building CXX object
autotests\CMakeFiles\kfilewidgettest.dir\kfilewidgettest.cpp.obj
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\kfilewidgettest.cpp(162):
warning C4996: 'KFileWidget::setSelection': was declared deprecated
R:\build\frameworks\tier3\kio\work\kio-5.40.0\src\filewidgets\kfilewidget.h(159):
note: see declaration of 'KFileWidget::setSelection'

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

[frameworks-kio] [Bug 386870] New: AutoMoc warning with ktcpsockettest

[Uwe Stöhr]

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

Bug ID: 386870
   Summary: AutoMoc warning with ktcpsockettest
   Product: frameworks-kio
   Version: 5.40.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: uwesto...@web.de
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I get:

[657/877] Automatic MOC for target ktcpsockettest
AutoMoc: Warning:
"R:/build/frameworks/tier3/kio/work/kio-5.40.0/autotests/ktcpsockettest.cpp"
The file includes the moc file "ktcpsockettest.moc", but does not contain a
Q_OBJECT or Q_GADGET macro.

R:/build/frameworks/tier3/kio/work/kio-5.40.0/autotests/ktcpsockettest.cpp(0):
Note: No relevant classes found. No output generated.

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

[frameworks-kio] [Bug 386869] Deprecation warnings for KIO::pasteClipboard

[Uwe Stöhr]

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

Uwe Stöhr  changed:

   What|Removed |Added

Summary|Deprecation warning for |Deprecation warnings for
   |KIO::pasteClipboard |KIO::pasteClipboard

--- Comment #1 from Uwe Stöhr  ---
and also this one:

[740/877] Building CXX object
autotests\CMakeFiles\jobguitest.dir\jobguitest.cpp.obj
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\jobguitest.cpp(76):
warning C4996: 'KIO::pasteClipboard': was declared deprecated
R:/build/frameworks/tier3/kio/work/kio-5.40.0/src/widgets/paste.h(46): note:
see declaration of 'KIO::pasteClipboard'

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

[frameworks-kio] [Bug 386869] New: Deprecation warning for KIO::pasteClipboard

[Uwe Stöhr]

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

Bug ID: 386869
   Summary: Deprecation warning for KIO::pasteClipboard
   Product: frameworks-kio
   Version: 5.40.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: uwesto...@web.de
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I get:

[708/877] Building CXX object
autotests\CMakeFiles\clipboardupdatertest.dir\clipboardupdatertest.cpp.obj
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\clipboardupdatertest.cpp(126):
warning C4996: 'KIO::pasteClipboard': was declared deprecated
R:/build/frameworks/tier3/kio/work/kio-5.40.0/src/widgets/paste.h(46): note:
see declaration of 'KIO::pasteClipboard'
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\clipboardupdatertest.cpp(148):
warning C4996: 'KIO::pasteClipboard': was declared deprecated
R:/build/frameworks/tier3/kio/work/kio-5.40.0/src/widgets/paste.h(46): note:
see declaration of 'KIO::pasteClipboard'
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\clipboardupdatertest.cpp(169):
warning C4996: 'KIO::pasteClipboard': was declared deprecated
R:/build/frameworks/tier3/kio/work/kio-5.40.0/src/widgets/paste.h(46): note:
see declaration of 'KIO::pasteClipboard'
[709/877] Building CXX object
autotests\CMakeFiles\kdynamicjobtrackernowidgetstest.dir\kdynamicjobtrackernowidgetstest.cpp.obj

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

[frameworks-kio] [Bug 386868] New: missing argument list warning with threadtest.cpp

[Uwe Stöhr]

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

Bug ID: 386868
   Summary: missing argument list warning with threadtest.cpp
   Product: frameworks-kio
   Version: 5.40.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: uwesto...@web.de
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I get :

[671/877] Building CXX object
autotests\CMakeFiles\threadtest.dir\threadtest.cpp.obj
R:\build\frameworks\tier3\kio\work\kio-5.40.0\autotests\threadtest.cpp(53):
warning C4551: function call missing argument list

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

[gwenview] [Bug 346565] A photo whose orientation I've corrected (rotated) subsequently becomes inverted

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #15 from Nate Graham  ---
Excellent, thanks for the info.

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

[gwenview] [Bug 346565] A photo whose orientation I've corrected (rotated) subsequently becomes inverted

[Trevor Parsons]

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

--- Comment #14 from Trevor Parsons  ---
(In reply to Nate Graham from comment #13)
> Is anybody able to reproduce this with Gwenview 16.x or 17.x? I can't.

With Gwenview 17.08.2 I'm no longer able to reproduce this bug.

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

[frameworks-kemoticons] [Bug 386867] New: several AutoMoc warnings in kemoticons

[Uwe Stöhr]

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

Bug ID: 386867
   Summary: several AutoMoc warnings in kemoticons
   Product: frameworks-kemoticons
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: uwesto...@web.de
  Target Milestone: ---

Compiling master with MSVC 2015 I get these AutoMoc warnings:

[11/41] Automatic MOC for target emoticonstheme_kde
AutoMoc: Warning:
"Q:/frameworks/tier3/kemoticons/src/providers/kde/kde_emoticons.cpp"
The file includes the moc file "kde_emoticons.moc", but does not contain a
Q_OBJECT or Q_GADGET macro.

and:

[13/41] Automatic MOC for target emoticonstheme_xmpp
AutoMoc: Warning:
"Q:/frameworks/tier3/kemoticons/src/providers/xmpp/xmpp_emoticons.cpp"
The file includes the moc file "xmpp_emoticons.moc", but does not contain a
Q_OBJECT or Q_GADGET macro.

and:

[18/41] Automatic MOC for target emoticonstheme_adium
AutoMoc: Warning:
"Q:/frameworks/tier3/kemoticons/src/providers/adium/adium_emoticons.cpp"
The file includes the moc file "adium_emoticons.moc", but does not contain a
Q_OBJECT or Q_GADGET macro.

and:

[24/41] Automatic MOC for target emoticonstheme_pidgin
AutoMoc: Warning:
"Q:/frameworks/tier3/kemoticons/src/providers/pidgin/pidgin_emoticons.cpp"
The file includes the moc file "pidgin_emoticons.moc", but does not contain a
Q_OBJECT or Q_GADGET macro.

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

[valgrind] [Bug 208052] strlcpy error when n = 0

[Jan Kryl]

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

--- Comment #6 from Jan Kryl  ---
I tested the patch from Tom with version 3.10.1 (the latest available in
freebsd ports) and it solved the problem for me.

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

[Craft] [Bug 386787] compiling cantor via craft fails

[Uwe Stöhr]

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

Uwe Stöhr  changed:

   What|Removed |Added

 CC||kf...@kde.org

--- Comment #7 from Uwe Stöhr  ---
> craft --target=master -i cantor

many thanks Kevin!

I was looking for a full documentation of craft but couldn't find one. 

I only found this page:
https://community.kde.org/Craft

Could you maybe add the info for the --target option and the one with
KDEApplications = master to this page?

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

[krita] [Bug 386801] marching ants are gone

[bugzilla_noreply]

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

--- Comment #5 from rasa.putn...@gmail.com ---
(In reply to Alvin Wong from comment #4)
> You can try updating the graphics driver, but since your graphics chipset is
> pretty ancient it might not help. (This might be the latest driver, install
> at your own risk:
> https://downloadcenter.intel.com/download/22521/Intel-Graphics-Media-
> Accelerator-Driver-Windows-7-64-Windows-Vista-64-exe-?v=t )
> 
> If that really does not work, go to "Configure Krita" and in "Display"
> section untick "Canvas Graphics Acceleration".

Thank you, unticking the thing worked ^^
Have a wonderful day/night

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

[cantor] [Bug 386866] Linking error with cantor_plot3dassistant makes it uncompilable under Windows

[bugzilla_noreply]

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

uwesto...@web.de changed:

   What|Removed |Added

   Severity|major   |grave
Summary|Linking error with  |Linking error with
   |cantor_plot3dassistant  |cantor_plot3dassistant
   ||makes it uncompilable under
   ||Windows

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

[cantor] [Bug 386866] New: Linking error with cantor_plot3dassistant

[bugzilla_noreply]

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

Bug ID: 386866
   Summary: Linking error with cantor_plot3dassistant
   Product: cantor
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: fil...@kde.org
  Reporter: uwesto...@web.de
CC: alexanderrie...@gmail.com
  Target Milestone: ---

Using MSVC 2015 and today's master of cantor I get this linking error:

[60/235] Linking CXX shared module bin\cantor_plot3dassistant.dll
FAILED: bin/cantor_plot3dassistant.dll
cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E vs_link_dll
--intdir=src\assistants\plot3d\CMakeFiles\cantor_plot3dassistant.dir
--manifests  -- C:\PR85A6~1\MSVC2015\VC\bin\amd64\link.exe /nologo
src\assistants\plot3d\CMakeFiles\cantor_plot3dassistant.dir\plot3dassistant.cpp.obj
src\assistants\plot3d\CMakeFiles\cantor_plot3dassistant.dir\cantor_plot3dassistant_autogen\mocs_compilation.cpp.obj
 /out:bin\cantor_plot3dassistant.dll /implib:lib\cantor_plot3dassistant.lib
/pdb:bin\cantor_plot3dassistant.pdb /dll /version:0.0 /machine:x64
/INCREMENTAL:NO  lib\cantorlibs.lib R:\\lib\KF5
KIOFileWidgets.lib R:\\lib\KF5Bookmarks.lib R:\\lib\KF5Solid.lib
R:\\lib\KF5KIOWidgets.lib R:\\lib\KF5KIOCore.lib R:\\li
b\KF5JobWidgets.lib R:\\lib\KF5XmlGui.lib R:\\lib\KF5Completion.lib
R:\\lib\KF5IconThemes.lib R:\\lib\KF5Archive.lib R:\
\lib\KF5ItemViews.lib R:\\lib\KF5Service.lib R:\\lib\KF5ConfigWidgets.lib
R:\\lib\KF5ConfigGui.lib R:\\lib\KF5ConfigCore
.lib R:\\lib\KF5I18n.lib R:\\lib\KF5WidgetsAddons.lib R:\\lib\KF5Codecs.lib
R:\\lib\KF5Auth.lib R:\\lib\KF5CoreAddons.lib
C:\Qt\Qt5.9.2\5.9.2\msvc2015_64\lib\Qt5DBus.lib
C:\Qt\Qt5.9.2\5.9.2\msvc2015_64\lib\Qt5Widgets.lib C:\Qt\Qt5.9.2\5.9.2
\msvc2015_64\lib\Qt5Gui.lib C:\Qt\Qt5.9.2\5.9.2\msvc2015_64\lib\Qt5Network.lib
C:\Qt\Qt5.9.2\5.9.2\msvc2015_64\lib\Qt5Xml.lib
C:\Qt\Qt5.9.2\5.9.2\msvc2015_64\lib\Qt5Core.lib kernel32.lib user32.lib
gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib
advapi32.lib  && cd ."
   Creating library lib\cantor_plot3dassistant.lib and object
lib\cantor_plot3dassistant.exp
plot3dassistant.cpp.obj : error LNK2019: unresolved external symbol "public:
static struct QMetaObject const Cantor::Ass
istant::staticMetaObject"
(?staticMetaObject@Assistant@Cantor@@2UQMetaObject@@B) referenced in function
"protected: void
 __cdecl KPluginFactory::registerPlugin(class QString
const &,class QObject * (__cdecl*)(class QWidget *,class QObject *,class
QList const &))"
(??$registerPlugin@VPlot3dAssistant@@@KPluginFactory@@IEAAXAEBVQString@@P6APEAVQObject@@PEAVQWidget@@PEAV2@AEBV?$QList@VQVariant@Z@Z)
plot3dassistant.cpp.obj : error LNK2019: unresolved external symbol "public:
static struct QMetaObject const Cantor::Backend::staticMetaObject"
(?staticMetaObject@Backend@Cantor@@2UQMetaObject@@B) referenced in function
"public: static class QString __cdecl Cantor::Backend::tr(char const *,char
const *,int)" (?tr@Backend@Cantor@@SA?AVQString@@PEBD0H@Z)
bin\cantor_plot3dassistant.dll : fatal error LNK1120: 2 unresolved externals
LINK failed. with 1120

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

[cantor] [Bug 386865] New: AutoMoc warnings with plot2dassistant, plot3dassistant, antor_advancedplotassistant and cantorpart

[bugzilla_noreply]

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

Bug ID: 386865
   Summary: AutoMoc warnings with plot2dassistant,
plot3dassistant, antor_advancedplotassistant and
cantorpart
   Product: cantor
   Version: 17.08
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fil...@kde.org
  Reporter: uwesto...@web.de
CC: alexanderrie...@gmail.com
  Target Milestone: ---

Compiling cantor master with MSVC 2015 I get:

[44/235] Automatic MOC for target cantor_plot2dassistant
AutoMoc: Warning:
"Q:/kde/applications/cantor/src/assistants/plot2d/plot2dassistant.cpp"
The file includes the moc file "plot2dassistant.moc", but does not contain a
Q_OBJECT or Q_GADGET macro.

and:

[50/235] Automatic MOC for target cantor_plot3dassistant
AutoMoc: Warning:
"Q:/kde/applications/cantor/src/assistants/plot3d/plot3dassistant.cpp"
The file includes the moc file "plot3dassistant.moc", but does not contain a
Q_OBJECT or Q_GADGET macro.

and:

[58/235] Automatic MOC for target cantor_advancedplotassistant
AutoMoc: Warning:
"Q:/kde/applications/cantor/src/assistants/advancedplot/advancedplotassistant.cpp"
The file includes the moc file "advancedplotassistant.moc", but does not
contain a Q_OBJECT or Q_GADGET macro.

and:

[61/235] Automatic MOC for target cantorpart
AutoMoc: Warning: "Q:/kde/applications/cantor/src/cantor_part.cpp"
The file includes the moc file "cantor_part.moc", but does not contain a
Q_OBJECT or Q_GADGET macro.

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

[kdialog] [Bug 386864] New: Some glitches on zoom and zoom-out

[bugzilla_noreply]

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

Bug ID: 386864
   Summary: Some glitches on zoom and zoom-out
   Product: kdialog
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: voidar...@gmail.com
  Target Milestone: ---

Created attachment 108844
  --> https://bugs.kde.org/attachment.cgi?id=108844=edit
Some glitches on zoom

Some glitches when scaling and decreasing with CTRL and mouse scroll.
See screenshot. 

Wait about year, but it still no fixed.

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

[plasmashell] [Bug 386519] A bug in the global kde menu when switching between tabs.

[D1mon]

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

--- Comment #2 from D1mon  ---
Settings->Configure Okular->General->Open new files in tabs->checked(true)

Open file1.pdf and open file2.pdf then switch between tabs.

Kde global menu checked "Auto Hide".

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

[kdevplatform] [Bug 386863] New: patchreview button text size

[RJVB]

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

Bug ID: 386863
   Summary: patchreview button text size
   Product: kdevplatform
   Version: unspecified
  Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: patchreview
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com
CC: david.nolden@art-master.de
  Target Milestone: ---

Created attachment 108843
  --> https://bugs.kde.org/attachment.cgi?id=108843=edit
patch review toolview (detail)

Don't you think the buttons look a little off in the attached screenshot?

I think this was always the case but I just never noticed it because until I
went back to a smaller toolbar button font very recently.

My standard font is `Segoe UI,10,-1,5,63,0,0,0,0,0,Semibold`, the toolbar font
is `Novarese Bk BT [bitstream],9.5,-1,5,63,0,0,0,0,0,Medium`

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

[kwin] [Bug 386490] Crash in Atomic DRM setting

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kwi
   ||n/c601e875cfa7d673f1567c710
   ||87036631e42d272
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #11 from Martin Flöser  ---
Git commit c601e875cfa7d673f1567c71087036631e42d272 by Martin Flöser.
Committed on 13/11/2017 at 20:19.
Pushed by graesslin into branch 'master'.

[platforms/drm] At safety checks for the properties

Summary:
The AMS code accesses elements in a vector which might not be valid. This
change refactors the code to be more robust, especially the DrmPlane,
which started to crash after adding transformation support.

Reviewers: #kwin, #plasma, fvogt, subdiff

Subscribers: plasma-devel, kwin

Tags: #kwin

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

M  +14   -5plugins/platforms/drm/drm_object.cpp
M  +17   -14   plugins/platforms/drm/drm_object.h
M  +2-2plugins/platforms/drm/drm_object_connector.cpp
M  +5-2plugins/platforms/drm/drm_object_crtc.cpp
M  +24   -9plugins/platforms/drm/drm_object_plane.cpp
M  +3-0plugins/platforms/drm/egl_gbm_backend.cpp

https://commits.kde.org/kwin/c601e875cfa7d673f1567c71087036631e42d272

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

[krita] [Bug 386801] marching ants are gone

[Alvin Wong]

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

Alvin Wong  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WONTFIX
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Alvin Wong  ---
You can try updating the graphics driver, but since your graphics chipset is
pretty ancient it might not help. (This might be the latest driver, install at
your own risk:
https://downloadcenter.intel.com/download/22521/Intel-Graphics-Media-Accelerator-Driver-Windows-7-64-Windows-Vista-64-exe-?v=t
)

If that really does not work, go to "Configure Krita" and in "Display" section
untick "Canvas Graphics Acceleration".

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

[digikam] [Bug 385471] Geolocation Editor Opens Map To A Random Location

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #2 from caulier.gil...@gmail.com ---
The next 5.8.0 pre-version bundle can be downloaded from there for testing :

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

About the jump to coordinates of an image in the list, i join the Maik
viewpoint. This can be a problematic behavior.

Gilles Caulier

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

[dolphin] [Bug 386838] Dolphin doesn't update view (doesn't show new files)

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
Glad to hear it! Yes, noatime is preferred to lazytime if that's something that
you're concerned about. Modern SSDs are pretty good about working around wear
issues though, so unless you've got a really unusual workflow, your SSDs
shouldn't wear out in normal use.

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

[valgrind] [Bug 386425] running valgrind + wine on armv7l gives illegal opcode

[Austin English]

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

--- Comment #6 from Austin English  ---
(In reply to Julian Seward from comment #4)
> (In reply to Julian Seward from comment #3)
> > IIUC, TPIDRURW is a 32 bit register that can be both read and
> > written from user space.  Yes?  Does it require any special handling?
> 
> To clarify .. what I mean to ask is: does TPIDRURW behave like a "normal"
> integer register, in that each thread has its own copy and can read and
> write it independently of other threads?  Or does it have some other
> behaviour?

>From Andre:
>> Sure,
>>
>> it should be ARM encoding. trpidrurw is rw from userspace and needs no 
>> permissions

> Is it specific per thread or shared across?
>

per thread
maybe https://github.com/AndreRH/tpidrurw-test can help to understand it

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

[amarok] [Bug 386765] missing information

[bugzilla_noreply]

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

--- Comment #2 from altodr...@gmail.com ---
Thanks to have taken time to answer me. And sorry for the previous lack of
information. Hope information below will help.

Platform:
- Kubuntu 17.10
- KDE Plasma 5.10.5
- Kernel 4.13.0-16-generic

Theme: Brise (default theme)
(I tried the two default theme with the same issue.)

(In reply to Myriam Schweingruber from comment #1)
> we would need a lot more information, as this works perfectly fine for me on
> 2.8.0 and 2.9 beta.
> What platform do you use Amarok on? Which theme do you use? Which exact
> distribution and system version do you use?

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

[dolphin] [Bug 386838] Dolphin doesn't update view (doesn't show new files)

[bugzilla_noreply]

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

jeremy9...@gmail.com changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from jeremy9...@gmail.com ---
Thank to your feedback I found the problem ! I use a SSD and I saw somewhere
that to preserve it you could use noatime or lazytime in fstab. I used
lazytime, so I removed it, rebooted and the problem is gone !

Should I use noatime or something else or nothing maybe to preserve my SSD ?

Thanks !

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

[kig] [Bug 386862] Cubic Curve by Nine Points is visually disconnected

[Alexander Potashev]

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

--- Comment #1 from Alexander Potashev  ---
Created attachment 108842
  --> https://bugs.kde.org/attachment.cgi?id=108842=edit
kig document

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

[kig] [Bug 386862] New: Cubic Curve by Nine Points is visually disconnected

[Alexander Potashev]

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

Bug ID: 386862
   Summary: Cubic Curve by Nine Points is visually disconnected
   Product: kig
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: david.narv...@computer.org
  Reporter: aspotas...@gmail.com
  Target Milestone: ---

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

A Cubic Curve by Nine Points may be rendered with disruptions in Kig, see
screenshot.

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

[krita] [Bug 386801] marching ants are gone

[bugzilla_noreply]

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

rasa.putn...@gmail.com changed:

   What|Removed |Added

  Alias||Rasa

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