[kio-gdrive] [Bug 379292] Doesn't work after installation

[bugzilla_noreply]

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

q...@e.wupics.com changed:

   What|Removed |Added

 CC||q...@e.wupics.com

--- Comment #8 from q...@e.wupics.com ---
(In reply to Elvis Angelaccio from comment #6)
> I don't get that window...
> When does it happen? Before or after you instert username/password?

This happened right after you granted permissions to Akonadi Resources for
Google Services. I googled a little bit and people say it's because google
forcing users to use 2-step verification procedure. But I don't want to use it.
I just want to enter my password once and that's all. Should I create a new bug
ticket for this?

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

[kmymoney4] [Bug 315789] Very useful feature when setting budgets

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||lukasz.wojnilow...@gmail.co
   ||m
 Resolution|--- |DUPLICATE

--- Comment #1 from NSLW  ---
KMM in master branch now respects fiscal year setting and if you want to budget
only half a year then choose individual budget period.

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

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

[kmymoney4] [Bug 297873] Budget year not the same as specified fiscal year

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 CC||spaldingdavid1...@gmail.com

--- Comment #4 from NSLW  ---
*** Bug 315789 has been marked as a duplicate of this bug. ***

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

[kmymoney4] [Bug 244810] For investment reports, use only existing prices

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 CC||lukasz.wojnilow...@gmail.co
   ||m

--- Comment #1 from NSLW  ---
Created attachment 105308
  --> https://bugs.kde.org/attachment.cgi?id=105308=edit
Price graph

For me it shows existing prices when I set "Skip value if price is zero".

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

[kmymoney4] [Bug 244810] For investment reports, use only existing prices

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

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

[kmymoney4] [Bug 378073] wrong investment account balance in per-institution view

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||lukasz.wojnilow...@gmail.co
   ||m
 Resolution|--- |DUPLICATE

--- Comment #1 from NSLW  ---


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

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

[kmymoney4] [Bug 340158] Some discrepancies between stocks displayed in Ledgers and on Institutions screen

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 CC||franco.tanz...@poste.it

--- Comment #8 from NSLW  ---
*** Bug 378073 has been marked as a duplicate of this bug. ***

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

[kmymoney4] [Bug 370242] "Geldinstitute": "Konten ohne zugewiesene Geldinstitute" cannot delete

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||lukasz.wojnilow...@gmail.co
   ||m
 Status|UNCONFIRMED |RESOLVED

--- Comment #8 from NSLW  ---
As explained in comment #4, "Konten ohne zugewiesene Geldinstitute" meant not
to be deleted. They can be set as hidden.

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

[kmymoney4] [Bug 379355] Reports do not print in colour.

[NSLW]

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

NSLW  changed:

   What|Removed |Added

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

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

[kmymoney4] [Bug 379355] Reports do not print in colour.

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 CC||lukasz.wojnilow...@gmail.co
   ||m

--- Comment #1 from NSLW  ---
Created attachment 105307
  --> https://bugs.kde.org/attachment.cgi?id=105307=edit
Printing settings

Uncheck printer friendly mode. In my case PDF print-outs are colorful.

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

[k3b] [Bug 379268] Importing previous session does nothing (version 17.04.0)

[Leslie Zhai]

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

--- Comment #42 from Leslie Zhai  ---
Hi Łukasz,

Please try to compile the git master of k3b for debug and test
https://github.com/KDE/k3b/blob/master/INSTALL.txt#L37

Sorry that I do not have CD/DVD driver nor empty CD/DVD/Blu-ray disc to test,
but only the simulator CDEmu, unfortunately VHBA module
https://sourceforge.net/p/cdemu/code/ci/master/tree/vhba-module/ does not
support multisession? so I can not verify the related issues!

Thanks,
Leslie Zhai

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

[k3b] [Bug 379268] Importing previous session does nothing (version 17.04.0)

[Leslie Zhai]

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

--- Comment #41 from Leslie Zhai  ---
Git commit a8f1221b407b7861771c8d8b1c422bb43d1585ce by Leslie Zhai.
Committed on 02/05/2017 at 04:27.
Pushed by lesliezhai into branch 'master'.

Fix DataMultisessionImportDialog No okClicked or cancelClicked signal issue.

K3b was developed by Sebastian Trueg started in 1998!
and K3b::DataMultisessionImportDialog was migrated by Michał Małek to KF5 in
2014!

There are okClicked and cancelClicked signals for KDialog.
Unfornately KDialog has been deprecated and moved to kde4support.
KF5 Prefer QDialog, but there is no such signal, and clang analyzer was not
taught
to find such migration issue :)

Please (code review) pay more attention to
K3b::DataMultisessionImportDialog::slotOk
and K3b::DataDoc::importSession, I prefer to use the backends provided by
libburnia
developing and maintaining by Thomas if others failed to importSession!

M  +3-3src/projects/k3bdatamultisessionimportdialog.cpp

https://commits.kde.org/k3b/a8f1221b407b7861771c8d8b1c422bb43d1585ce

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

[kiriki] [Bug 379428] New: Select score pattern then submit Vs Select & Play in 1 step

[bugzilla_noreply]

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

Bug ID: 379428
   Summary: Select score pattern then submit Vs Select & Play in 1
step
   Product: kiriki
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aa...@kde.org
  Reporter: boots5...@yahoo.com
CC: kde-games-b...@kde.org
  Target Milestone: ---

Could you please add a step in the game play to first select the score pattern
in which to play and then submit (or "play")
Its terribly when playing to accidentally select the wrong score pattern 
i.e. could you make it so that we select the "play" (e.g. Full House etc) see
the proposed score result of placing in that play and then submit

This would avoid accidentally playing the wrong field


Otherwise - love it!!

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

[krunner] [Bug 379045] Searching in Simple Menu / Application Launcher / KRunner spikes CPU usage ranging from 25% to 100%

[Travis J]

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

--- Comment #8 from Travis J  ---
Alright, I am not longer able to trigger this.
Also, I looked in the redhat bugzilla for fedora and found the bug ticket on
their side. It had to do with baloo zombie child in krunner or the like. And
yes it has been makred resolved with the kde-settings package. I believe you
can close this issue now.

https://bugzilla.redhat.com/show_bug.cgi?id=1432619

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

[kde-windows] [Bug 379427] New: 'C:\Program' not recognized as internal or external command in compilation of zlib.

[bugzilla_noreply]

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

Bug ID: 379427
   Summary: 'C:\Program' not recognized as internal or external
command in compilation of zlib.
   Product: kde-windows
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: buildsystem
  Assignee: kde-wind...@kde.org
  Reporter: r03...@gmail.com
  Target Milestone: ---

Created attachment 105306
  --> https://bugs.kde.org/attachment.cgi?id=105306=edit
log-C_KDE.txt

I can guess what is causing this (a typo) but am not really aware of any way to
fix it. This only occurs when using MSVCC - I switched from MinGW to avoid Bug
379142.

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[Yichao Yu]

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

--- Comment #55 from Yichao Yu  ---
Works for me so far. Haven't got a chance to figure out what's causing the
(absence of) mmap yet...

I assume you'll submit a pull request with this?

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

[tellico] [Bug 379426] Track length in CD audio lookup is wrong

[Robby Stephenson]

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

Robby Stephenson  changed:

   What|Removed |Added

   Version Fixed In||3.1
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/tel
   ||lico/b9f50483012f50e86f227e
   ||493577d5b04eb8e123
 Resolution|--- |FIXED

--- Comment #1 from Robby Stephenson  ---
Git commit b9f50483012f50e86f227e493577d5b04eb8e123 by Robby Stephenson.
Committed on 02/05/2017 at 01:48.
Pushed by rstephenson into branch 'master'.

Fix track length for CD audio read.

Switching to libdiscid missed the fact that track lengths are in sectors
instead of seconds. There are 75 sectors per second.
FIXED-IN: 3.1

M  +4-0ChangeLog
M  +2-1src/translators/freedb_util.cpp

https://commits.kde.org/tellico/b9f50483012f50e86f227e493577d5b04eb8e123

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

[tellico] [Bug 379426] New: Track length in CD audio lookup is wrong

[Robby Stephenson]

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

Bug ID: 379426
   Summary: Track length in CD audio lookup is wrong
   Product: tellico
   Version: 3.0.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ro...@periapsis.org
  Reporter: ro...@periapsis.org
  Target Milestone: ---

libdiscid uses sectors for track lengths instead of seconds.

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

[kdenlive] [Bug 360084] git master - Audio is not synced with 4k UHD video during playback -- video plays faster (sample clip included)

[Jesse]

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

--- Comment #15 from Jesse  ---
I submitted a bug to MLT's github page. You can see the bug report, here:
https://github.com/mltframework/mlt/issues/231

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

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

[bugzilla_noreply]

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

--- Comment #14 from r...@alum.mit.edu ---
Happened again:

#0  0x7ff984e2d13b in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x7ff984db262a in malloc () from /lib64/libc.so.6
#2  0x7ff985170e38 in operator new(unsigned long) () from
/usr/lib64/libstdc++.so.6
#3  0x7ff9867f065d in QQmlProperty::QQmlProperty(QObject*, QString const&)
() from /usr/lib64/libQt5Qml.so.5
#4  0x0040c65e in ?? ()
#5  
#6  0x7ff984daf0b6 in _int_free () from /lib64/libc.so.6
#7  0x7ff984db1980 in _int_realloc () from /lib64/libc.so.6
#8  0x7ff984db2daf in realloc () from /lib64/libc.so.6
#9  0x7ff985590897 in QString::reallocData(unsigned int, bool) () from
/usr/lib64/libQt5Core.so.5
#10 0x7ff9855910d4 in QString::append(QString const&) () from
/usr/lib64/libQt5Core.so.5
#11 0x7ff97f1aa292 in ?? () from /usr/lib64/libQt5DBus.so.5
#12 0x7ff97f1ac253 in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x7ff97f1ac464 in ?? () from /usr/lib64/libQt5DBus.so.5
#14 0x7ff97f1a4013 in QDBusConnection::connect(QString const&, QString
const&, QString const&, QString const&, QObject*, char const*) () from
/usr/lib64/libQt5DBus.so.5
#15 0x7ff97582212b in ?? () from /usr/lib64/libKF5Solid.so.5
#16 0x7ff97581ec04 in ?? () from /usr/lib64/libKF5Solid.so.5
#17 0x7ff9757f387e in
Solid::Device::listFromType(Solid::DeviceInterface::Type const&, QString
const&) () from /usr/lib64/libKF5Solid.so.5
#18 0x7ff9513a24b4 in ?? () from
/usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_powermanagement.so
#19 0x7ff9513a3255 in ?? () from
/usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_powermanagement.so
#20 0x7ff9856f171c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#21 0x7ff975853c06 in Solid::Battery::chargePercentChanged(int, QString
const&) () from /usr/lib64/libKF5Solid.so.5
#22 0x7ff975856817 in ?? () from /usr/lib64/libKF5Solid.so.5
#23 0x7ff9856f10d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#24 0x7ff975853726 in ?? () from /usr/lib64/libKF5Solid.so.5
#25 0x7ff975824c5d in ?? () from /usr/lib64/libKF5Solid.so.5
#26 0x7ff975855a2d in ?? () from /usr/lib64/libKF5Solid.so.5
#27 0x7ff9856f10d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#28 0x7ff97585cce3 in ?? () from /usr/lib64/libKF5Solid.so.5
#29 0x7ff97f1ae49b in ?? () from /usr/lib64/libQt5DBus.so.5
#30 0x7ff9856f2886 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#31 0x7ff9856c930c in QCoreApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Core.so.5
#32 0x7ff9856c9245 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#33 0x7ff9856cb2a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#34 0x7ff985718043 in ?? () from /usr/lib64/libQt5Core.so.5
#35 0x7ff9812b9134 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#36 0x7ff9812b9388 in ?? () from /usr/lib64/libglib-2.0.so.0
#37 0x7ff9812b942c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#38 0x7ff98571788c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#39 0x7ff9856c76ab in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#40 0x7ff9856cf344 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#41 0x00409bf4 in ?? ()
#42 0x7ff984d576e5 in __libc_start_main () from /lib64/libc.so.6
#43 0x00409e49 in _start ()

Again, I don't know this code, but there are some commonalities about the stack
traces:

1) They're always in a signal handler that's invoking
QQmlProperty::QQmlProperty, allocating memory.

2) Above the signal handler, they're allocating or freeing memory (not really
all that surprising; most versions of malloc aren't re-entrant).

3) Above that there are a variety of things, but they all seem to happen from
Solid::Battery::chargePercentChanged or Solid::Battery::chargeStateChanged.

In this case -- it hasn't always been true -- I had just driven home from work
with the laptop suspended, so the battery would have run down a bit.  I had
plugged it back in, resumed it, checked email, and then shut the lid (locking
the screen, but not suspending the laptop).  The hang happened about 10 minutes
after I first resumed it, so it's certainly possible that the laptop's charge
percent might have changed.  In other cases, though, it happened overnight,
when the laptop was surely fully charged.  That doesn't guarantee that the
charge state isn't changing, though.

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

[plasmashell] [Bug 379425] New: Error en placa al añadir panel

[Paulo Rocha]

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

Bug ID: 379425
   Summary: Error en placa al añadir panel
   Product: plasmashell
   Version: 5.9.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rocha.paulovic...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.5)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.33.0
Operating System: Linux 4.10.9-1 x86_64
Distribution: "KaOS"

-- Information about the crash:
EL Gnu/Linux uctilizado fue KaOS. 
falla al añadir nuevo panel por omision.

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

Thread 9 (Thread 0x7fdc20909700 (LWP 9464)):
#0  0x7fdce1d2fbb1 in  () at /usr/lib/libglib-2.0.so.0
#1  0x7fdce1d3238a in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7fdce1d329a8 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fdce1d32b0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fdce8cbdebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fdce8c6bbba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fdce8aa0d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fdc234d5347 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#8  0x7fdce8aa56e9 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fdce796c494 in start_thread () at /lib/libpthread.so.0
#10 0x7fdce83c36ff in clone () at /lib/libc.so.6

Thread 8 (Thread 0x7fdc33fff700 (LWP 2293)):
#0  0x7fdce83b9ffd in poll () at /lib/libc.so.6
#1  0x7fdce1d32a04 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fdce1d32b0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fdce8cbdebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fdce8c6bbba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fdce8aa0d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fdceb0d33a5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fdce8aa56e9 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fdce796c494 in start_thread () at /lib/libpthread.so.0
#9  0x7fdce83c36ff in clone () at /lib/libc.so.6

Thread 7 (Thread 0x7fdc394ec700 (LWP 1572)):
#0  0x7fdce1d77489 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fdce1d31fc9 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fdce1d32933 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fdce1d32b0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fdce8cbdebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fdce8c6bbba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fdce8aa0d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fdceba7d1b2 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7fdce8aa56e9 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fdce796c494 in start_thread () at /lib/libpthread.so.0
#10 0x7fdce83c36ff in clone () at /lib/libc.so.6

Thread 6 (Thread 0x7fdcc9e26700 (LWP 728)):
#0  0x7fdce79725cf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x7fdced537934 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fdced537979 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fdce796c494 in start_thread () at /lib/libpthread.so.0
#4  0x7fdce83c36ff in clone () at /lib/libc.so.6

Thread 5 (Thread 0x7fdccb792700 (LWP 711)):
#0  0x7fdce1d31eb0 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fdce1d32933 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fdce1d32b0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fdce8cbdebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fdce8c6bbba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fdce8aa0d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fdceb0d33a5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fdce8aa56e9 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fdce796c494 in start_thread () at /lib/libpthread.so.0
#9  0x7fdce83c36ff in clone () at /lib/libc.so.6

Thread 4 (Thread 0x7fdcd1792700 (LWP 708)):
#0  0x7fdce83b9ffd in poll () at /lib/libc.so.6
#1  0x7fdce1d32a04 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fdce1d32b0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fdce8cbdebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fdce8c6bbba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fdce8aa0d7c in 

[kmag] [Bug 332303] kmag should remember last used zoom mode

[Jeremy Whiting]

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

Jeremy Whiting  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kma
   ||g/4419029b67676c6ed9e70d5dd
   ||8661a5923bc4f72
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Jeremy Whiting  ---
Git commit 4419029b67676c6ed9e70d5dd8661a5923bc4f72 by Jeremy Whiting.
Committed on 02/05/2017 at 00:17.
Pushed by whiting into branch 'master'.

Use mode reading code for now to fix saving/loading the chosen mode.

M  +2-2kmag.cpp

https://commits.kde.org/kmag/4419029b67676c6ed9e70d5dd8661a5923bc4f72

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

[kwin] [Bug 379424] New: KWin Crash After Waking From Suspend

[Jacob Noori]

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

Bug ID: 379424
   Summary: KWin Crash After Waking From Suspend
   Product: kwin
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jacobno...@icloud.com
  Target Milestone: ---

Application: kwin_x11 (5.8.6)

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

-- Information about the crash:
- What I was doing when the application crashed:
I had put my PC to Suspend the night before and I pressed a keyboard key to
wake it up. KWin crash report opened after entering my password.
- Unusual behavior I noticed:
The fans spun on but the monitor remained in sleep mode until the HDD light
blinked and then it turned on.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7fc6ed153700 (LWP 23031)):
#0  0x7fc70ed2f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc70bf2365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fc7071dd4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fc7071dd995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fc70bf229e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc70ed2a744 in start_thread () at /lib64/libpthread.so.0
#6  0x7fc70ea68d3d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fc6d9477700 (LWP 23030)):
#0  0x7fc70ea61b03 in select () at /lib64/libc.so.6
#1  0x7fc70c131849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7fc70c1330c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7fc70c133527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc70c0e2fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc70bf1df1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc706b089c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc70bf229e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc70ed2a744 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc70ea68d3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fc6d9c78700 (LWP 19990)):
#0  0x7fc70ed2f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc70bf2365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fc7071dd4eb in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fc7071dd995 in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fc70bf229e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc70ed2a744 in start_thread () at /lib64/libpthread.so.0
#6  0x7fc70ea68d3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fc6ef1ba700 (LWP 15044)):
#0  0x7fc70ea61b03 in select () at /lib64/libc.so.6
#1  0x7fc70c131849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7fc70c1330c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7fc70c133527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc70c0e2fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc70bf1df1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc70bf229e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fc70ed2a744 in start_thread () at /lib64/libpthread.so.0
#8  0x7fc70ea68d3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc6d2afe700 (LWP 13222)):
#0  0x7fc70ed2f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc70b0b193b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fc70b0b1969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fc70ed2a744 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc70ea68d3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fc6ee174700 (LWP 13219)):
#0  0x7fc70ea61b03 in select () at /lib64/libc.so.6
#1  0x7fc70c131849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7fc70c1330c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7fc70c133527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc70c0e2fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc70bf1df1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc706b089c8 in  () at 

[plasma4] [Bug 330248] Give More options for control of 'auto-hide' feature of the panels

[bugzilla_noreply]

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

badr2...@gmail.com changed:

   What|Removed |Added

 CC||badr2...@gmail.com

--- Comment #1 from badr2...@gmail.com ---
+1

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Francis Herne]

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

--- Comment #9 from Francis Herne  ---
In this case, it's related to the use of Windows line endings in the file.

When the file is parsed in the background (but not while opened in the editor),
we fail to normalise them properly and the `lines` QStringList is given a
single line containing the whole document. fixAlias() doesn't check that AST
node positions exist in the document before trying to access them, and this
fails when the line doesn't exist.

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

[kdenlive] [Bug 360084] git master - Audio is not synced with 4k UHD video during playback -- video plays faster (sample clip included)

[Jesse]

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

--- Comment #14 from Jesse  ---
UPDATE: Tested to see if this bug is also present in MLT by running "melt" from
Terminal and choosing the file in topic. I can confirm that the audio sync
issue is present even without Kdenlive, so this seems to be an MLT issue? Where
would I go to submit a bug for this?

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

[systemsettings] [Bug 379423] not download kde theme debian 8.7.1

[yozz]

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

--- Comment #3 from yozz  ---
traceroute to kde-look.org (46.101.238.240), 30 hops max, 60 byte packets
 1  192.168.44.1 (192.168.44.1)  0.977 ms  0.959 ms  1.600 ms
 2  192.168.216.129 (192.168.216.129)  1.563 ms  5.362 ms  5.354 ms
 3  193.111.255.193 (193.111.255.193)  5.341 ms  5.331 ms  5.318 ms
 4  irb.101.obt-mx480-b57-414-60.obtel.pro (178.236.128.202)  5.302 ms  5.899
ms  5.884 ms
 5  ae3.313.obt-mx480-bm18-154-68.obtel.pro (178.236.130.65)  5.833 ms  5.822
ms  5.805 ms
 6  rascom.w-ix.net (193.106.112.103)  16.496 ms  12.451 ms  9.658 ms
 7  80-64-96-17.rascom.as20764.net (80.64.96.17)  39.384 ms  41.729 ms  41.672
ms
 8  80-64-96-219.rascom.as20764.net (80.64.96.219)  39.843 ms
80-64-96-17.rascom.as20764.net (80.64.96.17)  41.660 ms  41.612 ms
 9  fra1-edge1.digitalocean.com (80.81.193.141)  44.374 ms  44.368 ms  44.893
ms
10  138.197.250.157 (138.197.250.157)  47.142 ms 138.197.250.155
(138.197.250.155)  48.291 ms 138.197.250.157 (138.197.250.157)  47.377 ms

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

[kdenlive] [Bug 358923] Add function to playback project from beginning when spacebar is pressed at the end of Project Monitor (similar to Clip Monitor behavior)

[Jesse]

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

Jesse  changed:

   What|Removed |Added

Summary|Playback project from   |Add function to playback
   |beginning when spacebar is  |project from beginning when
   |pressed at the end of   |spacebar is pressed at the
   |Project Monitor |end of Project Monitor
   ||(similar to Clip Monitor
   ||behavior)

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

[kdenlive] [Bug 367693] git master - Preview render problem: isn't always rendering timeline properly (video example included)

[Jesse]

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

Jesse  changed:

   What|Removed |Added

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

--- Comment #8 from Jesse  ---
I need to re-open this bug. Looks like it's occurring, again, in 17.07.70
master ppa build. Same issue happens on a project in 1080p, 30fps: changing a
clip's position in Timeline, even Adding a clip to a new track over clips that
have been preview-rendered and starting preview render DOESN'T actually build a
new preview render. Anything that was red (un-rendered) immediately switched to
green (rendered), but doesn't reflect the changes I've made in the timeline.

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

[systemsettings] [Bug 379423] not download kde theme debian 8.7.1

[yozz]

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

--- Comment #2 from yozz  ---
Linux zzz 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64
GNU/Linux

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

[kdenlive] [Bug 373582] Have "Save" and "Load layout" options also remember track size in Timeline.

[Jesse]

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

Jesse  changed:

   What|Removed |Added

Summary|git master - Have save and  |Have "Save" and "Load
   |load layouts also remember  |layout" options also
   |track size in timeline. |remember track size in
   ||Timeline.
   Platform|Archlinux Packages  |Ubuntu Packages

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

[systemsettings] [Bug 379423] not download kde theme debian 8.7.1

[yozz]

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

--- Comment #1 from yozz  ---
Created attachment 105305
  --> https://bugs.kde.org/attachment.cgi?id=105305=edit
kde debian download

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

[systemsettings] [Bug 379423] New: not download kde theme debian 8.7.1

[yozz]

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

Bug ID: 379423
   Summary: not download kde theme debian 8.7.1
   Product: systemsettings
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: aleks...@gmail.com
  Target Milestone: ---

please fix it. from 3 systems not download kde theme kde4. not plasma. in
debian 8.6 in was worked

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

[systemsettings] [Bug 379422] New: not download kde theme debian 8.7.1

[yozz]

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

Bug ID: 379422
   Summary: not download kde theme debian 8.7.1
   Product: systemsettings
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: aleks...@gmail.com
  Target Milestone: ---

please fix it. from 3 systems not download kde theme kde4. not plasma. in
debian 8.6 in was worked

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #7 from Francis Herne  ---
Not fixed, it crashes in visitAlias instead.

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Francis Herne]

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

--- Comment #8 from Francis Herne  ---
Sorry, fixAlias

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

[kio-gdrive] [Bug 379292] Doesn't work after installation

[Jonathan Riddell]

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

--- Comment #7 from Jonathan Riddell  ---
you're a genius.

I've updated the package in KDE neon to depend on libqt5webengine5

Elvis you may want to put a message in cmake output to say it needs this
installed as a runtime dep.

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

[amarok] [Bug 374670] AAC transcoding is broken due to deprecated libfaac

[bugzilla_noreply]

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

--- Comment #7 from rdragonr...@gmail.com ---
Sorry to have taken so long. I got locked out of the KDE reviewboard for some
reason (account creation issues), and have been quite busy with schoolwork.

Unfortunately, I can't seem to submit the patch, with the error that I need a
"git diff". How do I resolve this? I'd like to get this bug submitted, but I am
still very new to this.

Thank you, and sorry to bother again.

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

[konqueror] [Bug 372777] no kwallet integration in 16.12

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||kol...@aon.at

--- Comment #5 from Antonio Rojas  ---
*** Bug 379385 has been marked as a duplicate of this bug. ***

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

[konqueror] [Bug 379385] konqueror does not use kwallet

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||aro...@archlinux.org

--- Comment #1 from Antonio Rojas  ---


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

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

[kwin] [Bug 379421] New: kwin crashes after "unable to claim manager selection, another wm running"

[Loïc Yhuel]

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

Bug ID: 379421
   Summary: kwin crashes after "unable to claim manager selection,
another wm running"
   Product: kwin
   Version: 5.9.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: platform-x11-standalone
  Assignee: kwin-bugs-n...@kde.org
  Reporter: loic.yh...@gmail.com
  Target Milestone: ---

kwin-5.9.5-2.fc25.x86_64
kf5-kwindowsystem-5.33.0-1.fc25.x86_64
kf5-plasma-5.33.0-2.fc25.x86_64
qt5-qtbase-5.7.1-14.fc25.x86_64

On each startup kwin seems to be launched twice (no idea why) :
 - /usr/bin/kwin (no argument)
 - /usr/bin/kwin -session
1011210910f9e00014931285720013200121_1493665183_9480

The second one prints :
kwin: unable to claim manager selection, another wm running? (try using
--replace)
Application::crashHandler() called with signal 11; recent crashes: 1
KCrash: Application 'kwin_x11' crashing...

It seems both threads crashed when trying to use code from an unloaded library,
triggered the KCrash::defaultCrashHandler, then thread 1 (second to crash ?)
crashed again in QGuiApplication::platformNativeInterface.

#0  0x7f33c78c2b22 in QGuiApplication::platformNativeInterface() () at
kernel/qguiapplication.cpp:1588
#1  0x7f33cfc12f2e in QX11Info::display() () at /lib64/libQt5X11Extras.so.5
#2  0x7f33c87c6392 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-5.33.0/src/kcrash.cpp:455
#3  0x7f33c6715990 in  () at /lib64/libc.so.6
#4  0x7f33b7cbdd69 in  ()
#5  0x7f33b6de2d10 in  ()
#6  0x55e9d10e0ab0 in  ()
#7  0x7f33b6de2d50 in  ()
#8  0x55e9d10e0d61 in  ()
#9  0x0001 in  ()
#10 0x7f33c73f49ca in QThreadPrivate::start(void*) (arg=0x55e9d10e0ab0) at
thread/qthread_unix.cpp:368
=> 0x7f33b7cbdd69 seems to be an unloaded address.

#0  0x7f33c67ac81d in nanosleep () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f33c67ac76a in __sleep (seconds=0, seconds@entry=1) at
../sysdeps/posix/sleep.c:55
#2  0x7f33cf9dac3b in KWin::ApplicationX11::crashHandler(int)
(signal=) at /usr/src/debug/kwin-5.9.5/main_x11.cpp:325
#3  0x7f33c87c5ee0 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-5.33.0/src/kcrash.cpp:394
#4  0x7f33c6715990 in  () at /lib64/libc.so.6
#5  0x7f33c75943a2 in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
(this=this@entry=0x55e9d10cd050, receiver=receiver@entry=0x7fff104480a0,
event=event@entry=0x7fff104474c0)
at kernel/qcoreapplication.cpp:1081
#6  0x7f33c7dd4f08 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=0x55e9d10cd050, receiver=0x7fff104480a0, e=0x7fff104474c0) at
kernel/qapplication.cpp:3774
#7  0x7f33c7ddc671 in QApplication::notify(QObject*, QEvent*)
(this=0x7fff104480a0, receiver=0x7fff104480a0, e=0x7fff104474c0) at
kernel/qapplication.cpp:3556
#8  0x7f33c75946fa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x7fff104480a0, event=event@entry=0x7fff104474c0) at
kernel/qcoreapplication.cpp:988
#9  0x7f33c75c2b8d in QCoreApplication::sendEvent(QObject*, QEvent*)
(event=0x7fff104474c0, receiver=) at
kernel/qcoreapplication.h:231
#10 0x7f33c75c2b8d in QObjectPrivate::setParent_helper(QObject*)
(this=this@entry=0x55e9d1139c70, o=o@entry=0x0) at kernel/qobject.cpp:1996
#11 0x7f33c75c3303 in QObject::~QObject() (this=,
__in_chrg=) at kernel/qobject.cpp:1048
#12 0x7f33b4a60b19 in KWin::X11StandalonePlatform::~X11StandalonePlatform()
(this=0x55e9d1137890, __in_chrg=) at
/usr/src/debug/kwin-5.9.5/plugins/platforms/x11/standalone/x11_platform.h:33
#13 0x7f33c758c663 in QLibraryPrivate::unload(QLibraryPrivate::UnloadFlag)
(this=this@entry=0x55e9d11392c0, flag=flag@entry=QLibraryPrivate::NoUnloadSys)
at plugin/qlibrary.cpp:562
#14 0x7f33c758ccb6 in QLibraryStore::cleanup() () at
plugin/qlibrary.cpp:403
#15 0x7f33c758ccb6 in qlibraryCleanup () at plugin/qlibrary.cpp:427
#16 0x7f33c758ccb6 in (anonymous
namespace)::qlibraryCleanup_dtor_class_::~qlibraryCleanup_dtor_class_()
(this=, __in_chrg=) at plugin/qlibrary.cpp:429
#17 0x7f33c671a78a in __cxa_finalize (d=0x7f33c77c6ec0) at
cxa_finalize.c:56
#18 0x7f33c73ccdb3 in __do_global_dtors_aux () at /lib64/libQt5Core.so.5
#19 0x7fff10447d60 in  ()
#20 0x7f33cfbf318a in _dl_fini () at dl-fini.c:235
=> when /usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so is
unloaded, there is an application event filter which has its vtable in an
unloaded library.

I'm able to reproduce the same kind of crashes by launching "kwin" (without
--replace) when the session is launched.
In this case I get a mix of both callstacks : KWinX11Platform.so unload which
calls KCrash::defaultCrashHandler, which crashes directly in

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kde
   ||v-python/6043407c4ee2e1b3ee
   ||fac8e1f8c96a651b92a14e

--- Comment #6 from Sven Brauch  ---
Git commit 6043407c4ee2e1b3eefac8e1f8c96a651b92a14e by Sven Brauch.
Committed on 01/05/2017 at 21:44.
Pushed by brauch into branch '5.1'.

fix crash

This loop is obviously wrong, it iterates over size()+1 indices 0..size(),
but there are only size().

M  +1-1parser/astbuilder.cpp

https://commits.kde.org/kdev-python/6043407c4ee2e1b3eefac8e1f8c96a651b92a14e

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

[digikam] [Bug 377719] Cannot rename file with overwrite [patch]

[Simon]

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

Simon  changed:

   What|Removed |Added

 Attachment #105276|0   |1
is obsolete||
 Attachment #105286|0   |1
is obsolete||

--- Comment #16 from Simon  ---
Created attachment 105304
  --> https://bugs.kde.org/attachment.cgi?id=105304=edit
Add option to overwrite existing files in advance rename dialog (V6)

Shuffling code around usually causes side-effects, sorry for not testing.
Now I did a fair bit of renaming and did find a small issue with auto-detected
sidecar files, which is also fixed in V6.

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Priority|NOR |HI
 Status|UNCONFIRMED |CONFIRMED
 CC||m...@flherne.uk

--- Comment #5 from Francis Herne  ---
Reproducible with UE master and kdev-python 5.1-git.
===

 > AST > building abstract syntax tree for 
"/home/flh/projects/UnrealEngine/Engine/Extras/Maya_AnimationRiggingTools/ArtToolsOSX/MayaTools/General/Scripts/Modules/ART_Core.py"
Got syntax tree from python parser: 1 1
ASSERT: "uint(i) < uint(size())" in file /usr/include/qt/QtCore/qstring.h, line
897

Thread 7 "Queue(0x8ab900)" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffc4c43700 (LWP 27501)]
0x7fffef245a10 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x7fffef245a10 in raise () at /usr/lib/libc.so.6
#1  0x7fffef24713a in abort () at /usr/lib/libc.so.6
#2  0x004058d6 in messageOutput(QtMsgType, QMessageLogContext const&,
QString const&) (type=, context=..., msg=...)
at /home/flh/projects/kdevplatform/util/duchainify/main.cpp:79
#3  0x7fffefefa298 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fffefefbe09 in QMessageLogger::fatal(char const*, ...) const () at
/usr/lib/libQt5Core.so.5
#5  0x7fffefef73de in  () at /usr/lib/libQt5Core.so.5
#6  0x7fffc68d13bc in QString::at(int) const (this=0x7fffc4c41360, i=-1) at
/usr/include/qt/QtCore/qstring.h:897
#7  0x7fffc68e20af in Python::RangeFixVisitor::whitespaceAtEnd(QString
const&) (this=0x7fffc4c41670, line=...) at
/home/flh/projects/kdev-python/parser/astbuilder.cpp:443
#8  0x7fffc68e1fd6 in Python::RangeFixVisitor::fixAlias(Python::Ast*,
Python::Ast*, int, int) (this=0x7fffc4c41670, dotted=0x7fffb8042fb0,
asname=0x7fffb8042ff0, startLine=1, aliasIndex=0)
at /home/flh/projects/kdev-python/parser/astbuilder.cpp:433
#9  0x7fffc68e12c4 in
Python::RangeFixVisitor::visitImport(Python::ImportAst*) (this=0x7fffc4c41670,
node=0x7fffb8059db0) at
/home/flh/projects/kdev-python/parser/astbuilder.cpp:209
#10 0x7fffc68dbddc in Python::AstVisitor::visitNode(Python::Ast*)
(this=0x7fffc4c41670, node=0x7fffb8059db0) at
/home/flh/projects/kdev-python/parser/astvisitor.cpp:57
#11 0x7fffc68e0c55 in Python::RangeFixVisitor::visitNode(Python::Ast*)
(this=0x7fffc4c41670, node=0x7fffb8059db0) at
/home/flh/projects/kdev-python/parser/astbuilder.cpp:104
#12 0x7fffc68d5f3b in
Python::AstDefaultVisitor::visitCode(Python::CodeAst*) (this=0x7fffc4c41670,
node=0x7fffb8051510) at
/home/flh/projects/kdev-python/parser/astdefaultvisitor.cpp:94
#13 0x7fffc68dbba4 in Python::AstVisitor::visitNode(Python::Ast*)
(this=0x7fffc4c41670, node=0x7fffb8051510) at
/home/flh/projects/kdev-python/parser/astvisitor.cpp:41
#14 0x7fffc68e0c55 in Python::RangeFixVisitor::visitNode(Python::Ast*)
(this=0x7fffc4c41670, node=0x7fffb8051510) at
/home/flh/projects/kdev-python/parser/astbuilder.cpp:104
#15 0x7fffc68df46b in Python::AstBuilder::parse(QUrl const&, QString&)
(this=0x7fffc4c41d90, filename=..., contents=...) at
/home/flh/projects/kdev-python/parser/astbuilder.cpp:757
#16 0x7fffc68d3909 in Python::ParseSession::parse() (this=0x7fffb8003900)
at /home/flh/projects/kdev-python/parser/parsesession.cpp:76
#17 0x7fffc6d6dc24 in
Python::ParseJob::run(QSharedPointer,
ThreadWeaver::Thread*) (this=0xb72e20) at
/home/flh/projects/kdev-python/pythonparsejob.cpp:157
#18 0x760ee5d6 in
ThreadWeaver::IdDecorator::run(QSharedPointer,
ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#19 0x760eebd8 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#20 0x760edaea in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5
#21 0x760ed190 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#22 0x7fffeff156d8 in  () at /usr/lib/libQt5Core.so.5
#23 0x7fffe72ba2e7 in start_thread () at /usr/lib/libpthread.so.0
#24 0x7fffef2fe54f in clone () at /usr/lib/libc.so.6
(gdb) bt full
#0  0x7fffef245a10 in raise () at /usr/lib/libc.so.6
#1  0x7fffef24713a in abort () at /usr/lib/libc.so.6
#2  0x004058d6 in messageOutput(QtMsgType, QMessageLogContext const&,
QString const&) (type=, context=..., msg=...)
at /home/flh/projects/kdevplatform/util/duchainify/main.cpp:79
#3  0x7fffefefa298 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fffefefbe09 in QMessageLogger::fatal(char const*, ...) const () at
/usr/lib/libQt5Core.so.5
#5  0x7fffefef73de in  () at /usr/lib/libQt5Core.so.5
#6  0x7fffc68d13bc in QString::at(int) const (this=0x7fffc4c41360, i=-1) at

[kde] [Bug 379420] New: showPhoto crashed after resize

[Kai Krakow]

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

Bug ID: 379420
   Summary: showPhoto crashed after resize
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: k...@kaishome.de
  Target Milestone: ---

Application: showfoto (5.5.0)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.10.13-ck x86_64
Distribution: "Gentoo Base System release 2.3"

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

I was resizing a phote, then clicked "Save as", typed a file name and it
crashed.

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

Thread 4 (Thread 0x7ffaa738e700 (LWP 9844)):
#0  0x003f86adf39d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x003f89e0c8e2 in poll (__timeout=-1, __nfds=1, __fds=0x7ffaa738dba0)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x1c981e0, cond=cond@entry=0x1c98220,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_conn.c:479
#3  0x003f89e0f249 in xcb_wait_for_event (c=0x1c981e0) at
/var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_in.c:693
#4  0x7ffaa8a36279 in QXcbEventReader::run (this=0x1ca4540) at
qxcbconnection.cpp:1343
#5  0x0031fbcaeb18 in QThreadPrivate::start (arg=0x1ca4540) at
thread/qthread_unix.cpp:368
#6  0x003f872073b4 in start_thread (arg=0x7ffaa738e700) at
pthread_create.c:333
#7  0x003f86ae841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7ffaa50ae700 (LWP 9846)):
#0  0x0031fa8a8fc9 in g_mutex_lock (mutex=mutex@entry=0x7ffa98000990) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gthread-posix.c:1336
#1  0x0031fa853f10 in g_main_context_acquire (context=0x7ffa98000990) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3264
#2  0x0031fa855025 in g_main_context_iterate
(context=context@entry=0x7ffa98000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3879
#3  0x0031fa85527c in g_main_context_iteration (context=0x7ffa98000990,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990
#4  0x0031fbed2a9b in QEventDispatcherGlib::processEvents
(this=0x7ffa980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x0031fbe7ccda in QEventLoop::exec (this=this@entry=0x7ffaa50adc90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x0031fbca9ec4 in QThread::exec (this=this@entry=0x31fd494780
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#7  0x0031fd415d95 in QDBusConnectionManager::run (this=0x31fd494780
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x0031fbcaeb18 in QThreadPrivate::start (arg=0x31fd494780 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#9  0x003f872073b4 in start_thread (arg=0x7ffaa50ae700) at
pthread_create.c:333
#10 0x003f86ae841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7ffa97fff700 (LWP 9848)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0031fbcafa1b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x2270380) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x226a900,
mutex=mutex@entry=0x226a8f8, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7ffab1bc4333 in Digikam::ParkingThread::run (this=0x226a8e0) at
/var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core/libs/threads/threadmanager.cpp:115
#4  0x0031fbcaeb18 in QThreadPrivate::start (arg=0x226a8e0) at
thread/qthread_unix.cpp:368
#5  0x003f872073b4 in start_thread (arg=0x7ffa97fff700) at
pthread_create.c:333
#6  0x003f86ae841d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7ffaa93a5900 (LWP 9843)):
[KCrash Handler]
#6  0x09a00024 in ?? ()
#7  0x7ffab1d69e8a in Digikam::EditorTool::~EditorTool (this=0x24e4320,
__in_chrg=) at
/var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core/utilities/imageeditor/editor/editortool.cpp:93
#8  0x7ffab1dfa2e3 in Digikam::ResizeTool::~ResizeTool (this=0x24e4320,
__in_chrg=) at
/var/tmp/portage/media-gfx/digikam-5.5.0/work/digikam-5.5.0/core/utilities/imageeditor/tools/transform/resizetool.cpp:313
#9  

[LabPlot2] [Bug 379098] cannot open labplot2 handbook

[Stefan Gerlach]

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

Stefan Gerlach  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Stefan Gerlach  ---
Help-> Handbook now works with latest Frameworks (5.33.0) as tested on Windows.

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

[kdenlive] [Bug 379419] git master - crashes when trying to Clip Jobs > Stablize (vidstab) [backtrace log included]

[Jesse]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[Discover] [Bug 379418] New: Plasma-discover crash

[Roberto Martins]

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

Bug ID: 379418
   Summary: Plasma-discover crash
   Product: Discover
   Version: 5.9.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: roberto.martins1...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.9.4)

Qt Version: 5.7.1
Frameworks Version: 5.33.0
Operating System: Linux 4.10.12-200.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:
Plasma-discover never opened since installation Fedora 25.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f08d9fb0d40 (LWP 1888))]

Thread 33 (Thread 0x7f08397fa700 (LWP 1925)):
#0  0x7f08d518701d in poll () from /lib64/libc.so.6
#1  0x7f08ce4c0166 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f08ce4c027c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f08d5f8d6eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f08d5f3e68a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f08d5d9b5e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f08d5d9f9ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f08d3cff6ca in start_thread () from /lib64/libpthread.so.0
#8  0x7f08d5192f7f in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f0839ffb700 (LWP 1924)):
#0  0x7f08d3d05460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f08d5da004a in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f08d5d9a0d3 in QSemaphore::acquire(int) () from
/lib64/libQt5Core.so.5
#3  0x7f08d5f6696e in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#4  0x7f08d64a8a98 in QHttpThreadDelegate::encryptedSlot() () from
/lib64/libQt5Network.so.5
#5  0x7f08d653339d in QHttpThreadDelegate::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5Network.so.5
#6  0x7f08d5f66721 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#7  0x7f08d646b14a in QHttpNetworkConnectionChannel::_q_encrypted() () from
/lib64/libQt5Network.so.5
#8  0x7f08d646b62d in
QHttpNetworkConnectionChannel::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) () from /lib64/libQt5Network.so.5
#9  0x7f08d5f66721 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#10 0x7f08d6528176 in QSslSocketBackendPrivate::continueHandshake() () from
/lib64/libQt5Network.so.5
#11 0x7f08d652bc5b in QSslSocketBackendPrivate::startHandshake() () from
/lib64/libQt5Network.so.5
#12 0x7f08d652c65e in QSslSocketBackendPrivate::transmit() () from
/lib64/libQt5Network.so.5
#13 0x7f08d6517c61 in QSslSocket::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5Network.so.5
#14 0x7f08d5f66721 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#15 0x7f08d64eb1a5 in QAbstractSocketPrivate::emitReadyRead() () from
/lib64/libQt5Network.so.5
#16 0x7f08d64eb25c in QAbstractSocketPrivate::canReadNotification() () from
/lib64/libQt5Network.so.5
#17 0x7f08d64f6091 in QReadNotifier::event(QEvent*) () from
/lib64/libQt5Network.so.5
#18 0x7f08d6f79ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#19 0x7f08d6f81671 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#20 0x7f08d5f3f6fa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#21 0x7f08d5f8dfff in socketNotifierSourceDispatch(_GSource*, int
(*)(void*), void*) () from /lib64/libQt5Core.so.5
#22 0x7f08ce4bfe52 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#23 0x7f08ce4c01d0 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#24 0x7f08ce4c027c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#25 0x7f08d5f8d6cf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#26 0x7f08d5f3e68a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#27 0x7f08d5d9b5e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#28 0x7f08d5d9f9ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#29 0x7f08d3cff6ca in start_thread () from /lib64/libpthread.so.0
#30 0x7f08d5192f7f in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f083a7fc700 (LWP 1923)):
#0  

[kdenlive] [Bug 379419] New: git master - crashes when trying to Clip Jobs > Stablize (vidstab) [backtrace log included]

[Jesse]

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

Bug ID: 379419
   Summary: git master - crashes when trying to Clip Jobs >
Stablize (vidstab) [backtrace log included]
   Product: kdenlive
   Version: git-master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com
  Target Milestone: ---

Created attachment 105303
  --> https://bugs.kde.org/attachment.cgi?id=105303=edit
Backtrage log

BEHAVIOR
(1) Right-click on Clip (.mov 1080x1920 portrait) in Project Bin.
(2) Go to Clip Jobs > Stablize (vidstab)
(3) Click "OK" to start stablize job.
(4) Let progress bar reach the end in Project bin.

Kdenlive freezes, then crashes.

EXPECTED BEHAVIOR
Stablize clip without freezing or crashing.

BUG DISCOVERED USING:
Kdenlive 17.07.70 via ppa:kdenlive/kdenlive-master
Ubuntu GNOME 17.04 x64
GNOME 3.24.0 desktop environment
MLT 6.5.0
KDE Frameworks 5.31.0
Qt 5.7.1

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

[krita] [Bug 379417] there is no shortcut configuration in settings dropdown

[bugzilla_noreply]

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

finn.colde...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Severity|critical|minor
 Resolution|--- |FIXED

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

[kmail2] [Bug 379406] White space in message viewer on dark theme

[sedrubal]

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

sedrubal  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #3 from sedrubal  ---
It happens in both cases (in kontact and as standalone app).

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

[krita] [Bug 379417] New: there is no shortcut configuration in settings dropdown

[bugzilla_noreply]

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

Bug ID: 379417
   Summary: there is no shortcut configuration in settings
dropdown
   Product: krita
   Version: 3.1.2
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: shortcuts
  Assignee: krita-bugs-n...@kde.org
  Reporter: finn.colde...@gmail.com
  Target Milestone: ---

the settings menu in does not contain the settings for Configure Shortcuts or
configure krita

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

[kmail2] [Bug 379406] White space in message viewer on dark theme

[Christophe Giboudeaux]

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

--- Comment #2 from Christophe Giboudeaux  ---
This only happens in kontact or also when you're just running KMail ?

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

[krita] [Bug 379387] Major lag

[bugzilla_noreply]

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

--- Comment #3 from sannib...@hotmail.com ---
Thank you,

I will try this tomorrow after work and keep you updated on the results.

Best regards, Sue


Von Outlook gesendet.


Von: Boudewijn Rempt 
Gesendet: Montag, 01. Mai 2017 11:44:48
An: sannib...@hotmail.com
Betreff: [krita] [Bug 379387] Major lag

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||b...@valdyas.org

--- Comment #2 from Boudewijn Rempt  ---
Hi Sue,

We released Krita 3.1.3 today. Your problem sounds like it is caused by a
Windows update that is incompatible with an outdated intel display driver.
Please check whether disabling opengl in Krita makes a difference; if so, try
to update the driver and re-enable opengl again.

--
You are receiving this mail because:
You reported the bug.

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

[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /

[Marty]

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

--- Comment #5 from Marty  ---
Folks i hit this upgrading from from 4.14 to 5.6 (via appimage)

It complained it could not find the existing network collections, an example
was:
networkshareid:?mountpath=%2Fmnt%2Fmunich%2Fphotos

I edited the sqllite database directly replacing the ascii %2F with / and when
i restarted everything was fine again.

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

[krita] [Bug 379416] New: Initial layer bug of template

[foxglove]

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

Bug ID: 379416
   Summary: Initial layer bug of template
   Product: krita
   Version: 3.1.2
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: adjustment layers
  Assignee: krita-bugs-n...@kde.org
  Reporter: fomare.dar...@outlook.jp
  Target Milestone: ---

Use translation tool
Selection layer is not saved
Template Saved file
Convert Kra to Zip
Maindoc.xml internal code
Selected = "true" does not exist
Because this code is not listed
The initial layer of the template always becomes top

Applicable layer code
I can not find selected = "true" anywhere
"Layer x =" 378 "collapsed =" 0 "intimeline =" 0 "locked =" 0 "channelflags
=" "name =" "colorlabel =" 0 "onionskin =" 0 "
  Channellockflags = "" filename = "layer 2" y = "- 240" nodetype =
"paintlayer" uuid = "{16e3a081 - cdab - 446
3 - bc 5 b - 7 ba 9 c 9 b c 4 cf 2} "colorspacename =" RGBA "compositeop ="
normal "visible =" 1 "opacity =" 255 "/>

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

[digikam] [Bug 379415] digikam collection location string format in 5.X different to 4.X

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

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


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

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

[digikam] [Bug 372047] Switch from DK4 to DK5 fails: collection path contains %2F instead of /

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||ma...@nutmeg.at

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

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

[digikam] [Bug 379415] New: digikam collection location string format in 5.X different to 4.X

[Marty]

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

Bug ID: 379415
   Summary: digikam collection location string format in 5.X
different to 4.X
   Product: digikam
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Database-Sqlite
  Assignee: digikam-de...@kde.org
  Reporter: ma...@nutmeg.at
  Target Milestone: ---

Folks, i upgraded from 4.14 to 5.6 (via appimage)

It complained it could not find the existing network collections, an example
was:
networkshareid:?mountpath=%2Fmnt%2Fmunich%2Fphotos

i edited the AlbumRoots table directly converting the ascii %2F to forward
slash and then restarted and everything was fine.

Its not really clear to me why it was represented in hex in 4.X

A local collection did not have same issue and forward slashes were represented
directly.

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

[plasmashell] [Bug 379414] New: [Data Loss] - TaskManager loses launchers from alternative Activities

[Michail Vourlakos]

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

Bug ID: 379414
   Summary: [Data Loss] - TaskManager loses launchers from
alternative Activities
   Product: plasmashell
   Version: 5.9.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: mvourla...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

The issue is the following:

1. add the icon-only taskmanager in the panel
2. add two launchers that are available to all activities
3. add a third launcher which is only available in the current running activity
4. go to another activity
5. add a new launcher which is only available in the new current running
activity
6. after that move between these two activities and just try to change the
order of the launchers, at some point the user can notice that the explicit
assigned launchers are lost


following the code also through Latte what is happening is the following...
many times when changing the order of the launchers the launcherList returned
from the taskModel is the (global launchers + the current activity launchers),
all the rest are dismissed (this is checked for the running one activities but
it could be also and for the not running ones)...

This creates data loss for the user

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

[kdenlive] [Bug 375864] git master - Import images as sequence not working through "Add Clip" method in Project Bin

[Jesse]

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

Jesse  changed:

   What|Removed |Added

Summary|git master - Import images  |git master - Import images
   |as sequence not working |as sequence not working
   ||through "Add Clip" method
   ||in Project Bin

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

[kdenlive] [Bug 375864] git master - Import images as sequence not working through "Add Clip" method in Project Bin

[Jesse]

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

Jesse  changed:

   What|Removed |Added

   Platform|Mint (Ubuntu based) |Ubuntu Packages

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

[kdenlive] [Bug 375864] git master - Import images as sequence not working

[Jesse]

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

--- Comment #6 from Jesse  ---
UPDATE:

Adding an image sequence through the "Add Slideshow Clip" method (using the
Filename pattern method) produces the result I'm looking for: a series of .png
images are imported as a single clip, moving at 1 still image per frame.

Currently, trying to add the same .png files as above using the "Add Clip",
then selecting all and enabling the "Import image sequence" checkbox and
clicking "OK" imports all of the .png files as separate files, each with a
duration of 5-seconds.

CONCLUSION:
Maybe it would be better to remove this check-box from the Add clip import
window (and probably the transparency checkbox next to it, since it would only
logically apply to image sequences, anyways) and simply educate users to use
the Add Slideshow clip method?

If we go this route, I would suggest finding a better term for the Clip.
Industry professionals will recognize "image sequence", typically, as importing
a series of stills into a single clip.

Maybe even separate the two into two different options: "Add Slideshow" and
"Add Image Sequence", then create a layout similar to the "Add Slideshow"
widget, but hard-coded for importing still images in a sequence? Just
brainstorming, here.

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

[kmymoney4] [Bug 272398] KMyMoney 4.5.2 (KDE 4.5.5) Ubuntu 10.10 slowed and is now consistently slow in edit Ledger Entry (Transaction)

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 CC||lukasz.wojnilow...@gmail.co
   ||m
 Resolution|--- |FIXED

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

[kmymoney4] [Bug 272398] KMyMoney 4.5.2 (KDE 4.5.5) Ubuntu 10.10 slowed and is now consistently slow in edit Ledger Entry (Transaction)

[NSLW]

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

--- Comment #14 from NSLW  ---
Marking as fixed as per comment #7.

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

[kmymoney4] [Bug 322620] Speed or reactivity

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED
 CC||lukasz.wojnilow...@gmail.co
   ||m

--- Comment #20 from NSLW  ---
Marking as duplicate, because of the same symptoms.

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

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

[kmymoney4] [Bug 272398] KMyMoney 4.5.2 (KDE 4.5.5) Ubuntu 10.10 slowed and is now consistently slow in edit Ledger Entry (Transaction)

[NSLW]

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

NSLW  changed:

   What|Removed |Added

 CC||nof...@club.fr

--- Comment #13 from NSLW  ---
*** Bug 322620 has been marked as a duplicate of this bug. ***

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

[kile] [Bug 379413] New: Manual spellchecking has a broken UI in Kile

[Andrius Štikonas]

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

Bug ID: 379413
   Summary: Manual spellchecking has a broken UI in Kile
   Product: kile
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: user interface
  Assignee: michel.lud...@kdemail.net
  Reporter: andr...@stikonas.eu
  Target Milestone: ---

Manual spellchecking has a broken UI in Kile. Some UI elements overlap but most
of the spellcheck interface is not visible. It seems to work in Kate.

Version: latest git as of today.
KF5 version: 5.33.0

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

[digikam] [Bug 378873] crash when trying to add album

[Marty]

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

Marty  changed:

   What|Removed |Added

 CC||ma...@nutmeg.at

--- Comment #2 from Marty  ---
Hi

I have same issue.

In the latest ubuntu 17.04 upgrade it upgraded to 5.4. (previous version was
4.14 and had no issues)

May  1 20:17:25 rif digikam[21661]: cannot register existing type 'GdkWindow'
May  1 20:17:25 rif digikam[21661]: g_once_init_leave: assertion 'result != 0'
failed
May  1 20:17:25 rif digikam[21661]: gdk_window_ensure_native: assertion
'GDK_IS_WINDOW (window)' failed

May  1 20:17:45 rif zenity[21768]: GtkDialog mapped without a transient parent.
This is discouraged.

I tried the appimage 5.6 and it worked.

Let me know if i can help you debug issue.

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

[digikam] [Bug 377719] Cannot rename file with overwrite [patch]

[Maik Qualmann]

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

--- Comment #15 from Maik Qualmann  ---
Simon,

I have now always red entries when I try to rename several files.

Maik

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

[kdenlive] [Bug 379412] git master - Title Clip gradient color setting doesn't apply, visually, to Title text. [screenshot included]

[Jesse]

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

--- Comment #1 from Jesse  ---
UPDATE: Pressing "OK" does in fact apply the color effect, but the color
changes aren't seen when re-entering the Title Editor. The user can't properly
see what the text looks like to edit it.

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

[kdenlive] [Bug 379412] git master - Title Clip gradient color setting doesn't apply, visually, to Title text. [screenshot included]

[Jesse]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 379412] New: git master - Title Clip gradient color setting doesn't apply, visually, to Title text. [screenshot included]

[Jesse]

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

Bug ID: 379412
   Summary: git master - Title Clip gradient color setting doesn't
apply, visually, to Title text. [screenshot included]
   Product: kdenlive
   Version: git-master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com
  Target Milestone: ---

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

BEHAVIOR
I created a text item in the Title editor, and selected the radial button for
Gradient to give it a gradient color, but the color didn't apply to the text --
it stayed black.

EXPECTED BEHAVIOR
When I select the radial button to switch to Gradient color, the color changes
are immediately applied to the text.

BUG DISCOVERED USING:
Kdenlive 17.07.70 via ppa:kdenlive/kdenlive-master
Ubuntu GNOME 17.04 x64
GNOME 3.24.0 desktop environment
MLT 6.5.0
KDE Frameworks 5.31.0
Qt 5.7.1

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

[digikam] [Bug 363859] digiKam core port from QWebKit to QWebEngine [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Attachment #102076|0   |1
is obsolete||

--- Comment #7 from Maik Qualmann  ---
Created attachment 105300
  --> https://bugs.kde.org/attachment.cgi?id=105300=edit
portWebEngine4.patch

Update patch to current git/master.

Maik

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

[krita] [Bug 379411] New: Tool switches to rectangle tool when trying to use panning shortcut

[Andy Statia]

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

Bug ID: 379411
   Summary: Tool switches to rectangle tool when trying to use
panning shortcut
   Product: krita
   Version: 3.1.3
  Platform: MS Windows
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: asta...@neverdot.com
  Target Milestone: ---

When trying to use the pan tool via the shortcut (space in this case), the
selected tool switches to the draw rectangle tool instead of pan.  One must
first click anywhere on the canvas first, then press the shortcut key to get it
to properly switch to the pan tool.

Reproduction steps:
1. Select any tool in the tool panel, preferably one with a visibly different
cursor than the rectangle tool (fill or pen tool, for example)
2. Press the space bar (for space bar mapping to the pan tool)
3. Note that the tool has switched to the rectangle tool instead of the pan
tool
4. After releasing the shortcut key (space bar), the tool does not return to
the original tool

Work around steps:
1. Select any tool in the tool panel, preferably one with a visibly different
cursor than the rectangle tool (fill or pen tool, for example)
2. Tap the canvas
3. Press the space bar (for space bar mapping to the pan tool)
4. Note that the tool now correctly switches to the pan tool
5. After releasing the shortcut key (space bar), the tool correctly returns to
the original tool

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

[krita] [Bug 377239] Krita crashed when trying to change fonts

[abnqeut]

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

abnqeut  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from abnqeut  ---
Issue no longer occurs. Setting status to resolved.

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

[frameworks-kwindowsystem] [Bug 379410] New: Window tab dragging has no effect

[Bill Michaelson]

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

Bug ID: 379410
   Summary: Window tab dragging has no effect
   Product: frameworks-kwindowsystem
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: kde...@bill.from.net
CC: kdelibs-b...@kde.org
  Target Milestone: ---

With Window Behavior -> Titlebar Actions -> Middle button set to "Start Window
Tab Drag", attempt use middle button to drag window.  Window does not move.

Using kubuntu-desktop APT bundle in 17.04 distro.  Unable to identify KDE
version.

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

[digikam] [Bug 376074] Display-bookmarked-positions-on-the-map button doesn't work.

[tuxflo]

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

--- Comment #9 from tuxflo  ---
Which version of marble/kbookmarks do you have installed?
I'm running KDE Neon, so KF5 desktop is avalible here.

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

[kdenlive] [Bug 379409] Include "Add Clip" options in context menu when right-clicking folders in Project Bin

[Jesse]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 379409] New: Include "Add Clip" options in context menu when right-clicking folders in Project Bin

[Jesse]

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

Bug ID: 379409
   Summary: Include "Add Clip" options in context menu when
right-clicking folders in Project Bin
   Product: kdenlive
   Version: git-master
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com
  Target Milestone: ---

Currently, right-clicking on a folder in the Project Bin has two or three
context-menu options: delete folder, rename, and (I think) create proxy.

Could we have all of the "Add Clip" options added to the context menu when you
right-click a folder in the Project Bin (e.g. "Add Clip", "Add Color Clip",
etc.)?

This is intuitive for many reasons, but mainly it allows the user to import
clips and media right into that folder. Would be a handy benefit when managing
media in the Project Bin.

SUGGESTED WHILE USING:
Kdenlive 17.07.70 via ppa:kdenlive/kdenlive-master
Ubuntu GNOME 17.04 x64
GNOME 3.24.0 desktop environment
MLT 6.5.0
KDE Frameworks 5.31.0
Qt 5.7.1

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

[kmail2] [Bug 379406] White space in message viewer on dark theme

[Colin J Thomson]

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

--- Comment #1 from Colin J Thomson  ---
I am also seeing this on F25. It happened after the last updates of
qt5-qtwebengine to 5.8.x 
You can downgrade to version qt5-qtwebengine-5.7.1-4.fc25.x86_64.rpm as a
temporary fix.
I have no idea if its a qt5-qtwebengine or Kmail2 bug.

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

[digikam] [Bug 376074] Display-bookmarked-positions-on-the-map button doesn't work.

[Maik Qualmann]

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

--- Comment #8 from Maik Qualmann  ---
The old bookmark administration works here under openSUSE without problems. But
it requires a working KF5 desktop.

Maik

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

[kmail2] [Bug 379408] New: Sender/Receiver not selctable

[Klaus-Dieter Fietze]

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

Bug ID: 379408
   Summary: Sender/Receiver not selctable
   Product: kmail2
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: klaus-dieter.fie...@bluewin.ch
  Target Milestone: ---

Created attachment 105299
  --> https://bugs.kde.org/attachment.cgi?id=105299=edit
Inbox with chosen header columns

I would like to see the date, the subject and, depending where I am, the sender
in „Inbox“ or the receiver in „Sent Items“ of my „Flat Date View“. However,
when I chose „Sender/Receiver“ in the configuration menu of the „Message List“
the sender is always displayed in both in „Inbox“ and in „Sent Items“, no
matter what I chose.
I have tried to right click on the header. As you can see on the attached
pictures, „Sender/Receiver“ is ticked but not shown. When I chose „Receiver“
from the list it is displayed in both the „Inbox“ and „Sent Items“ as everybody
would expect.
Moreover, I use the glider in the header to adjust the column width. But
whenever I start the computer again the column sizes have squeezed together.
Also, I should be able to directly key in the column size but I cannot find
where. Everything is greyed out.
I am using IMAP with openSUSE Leap 42.2, KDE Plasma 5.8.6., KDE Framework
5.26.0, Qt 5.6.1, Kernel 4.4.36-8 (64 bit).
Thank you,
Klaus-Dietrer Fietze

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

[valgrind] [Bug 365327] Support macOS Sierra (10.12)

[Rhys Kidd]

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

--- Comment #25 from Rhys Kidd  ---
I'd strongly suggest running through the regression test suite on your local
setup to provide coverage of a reasonable amount of the Darwin code base. It is
run with 'make regtest'.

The regression test is not quite automated on Darwin. You will probably need to
kill one of the pthread-related tests that hangs at present.

Suggested areas to focus on:
1. pselect syscall
2. Any other missing syscalls that prevent you using a program of interest to
you - more motivated to fix bugs in open source you're personally motivated in!
3. ulock_wait syscall - grep through the regression tests *.stderr.diff for the
test that triggers it
4. Find a fix for the pthread-related hang in the regression test suite.

Create a separate bug report for each, then attach a patch and make it a
blocker for this bug report.

The compiler warnings for 'getentropy' and 'ulock_wake' were fixed before
commiting to SVN.

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

[kio-extras] [Bug 376344] cant write to smb shares which has write access

[bugzilla_noreply]

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

--- Comment #20 from tempel.jul...@gmail.com ---
Two other workarounds:
1.:
Mount a networkfolder to make it look like it was local to Plasma.
Via terminal:
sudo mount -t cifs -o
username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770
//hostname.local/sharename/ /home/user/mountfolder/

Permanent via fstab:
//hostname.local/sharename/ /home/user/mountfolder/ cifs
defaults,username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0
2

Or 2.:
Install a GTK file browser like Thunar with gvfs + gvfs-smb (+gnome-keyring for
saving login data). With it you can drag & drop stuff from and into SMB shares
or open media files without having to fully copy them first.

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

[gwenview] [Bug 202414] allow to hide status bar and toolbar

[bugzilla_noreply]

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

--- Comment #18 from andydecle...@gmail.com ---
(In reply to Valerio Pilo from comment #17)
> Confirmed, the status is not saved. I will fix the persistence and move the
> entry to the View menu (I agree it's a better fit, maybe with a shortcut
> like F6 or the like).

Thank you. Can you please also add a menu entry for showing/hiding the toolbar
(and make sure that's persistent as well)? I believe that falls within the
scope of this bug.

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

[kdenlive] [Bug 379407] New: Crash on video play or clip import

[Kirill Shustov]

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

Bug ID: 379407
   Summary: Crash on video play or clip import
   Product: kdenlive
   Version: 17.04.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: kirill.sus...@gmail.com
  Target Milestone: ---

On adding or playing clips app crashes with seg fault.


[New Thread 0x7fff6fb13700 (LWP 11415)]
[New Thread 0x7fff5e7fc700 (LWP 11416)]
[New Thread 0x7fff44ffc700 (LWP 11417)]

Thread 17 "FrameRenderer" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff90abb700 (LWP 11393)]
0x71741520 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
(gdb) 
(gdb) thread apply all bt

Thread 40 (Thread 0x7fff44ffc700 (LWP 11417)):
#0  0x706216ed in nanosleep () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffa8259bf5 in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so
#2  0x7fffeecdd6da in start_thread (arg=0x7fff44ffc700) at
pthread_create.c:456
#3  0x7065d17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 39 (Thread 0x7fff5e7fc700 (LWP 11416)):
#0  0x70651251 in __GI_ppoll (fds=0x7fff60d8a470, nfds=3,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fffeb3b16ad in pa_mainloop_poll () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7fffeb3b1c9e in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7fffa7ff3feb in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#4  0x7fffa7fc6920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#5  0x7fffa7fd00b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#6  0x7fffa800ff49 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#7  0x7fffeecdd6da in start_thread (arg=0x7fff5e7fc700) at
pthread_create.c:456
#8  0x7065d17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 38 (Thread 0x7fff6fb13700 (LWP 11415)):
#0  0x7fffbbcbd342 in ?? () from /usr/lib/x86_64-linux-gnu/libswscale.so.4
#1  0x0010 in ?? ()
#2  0x7fffbbca600f in ?? () from /usr/lib/x86_64-linux-gnu/libswscale.so.4
#3  0x7fffbbc94351 in ?? () from /usr/lib/x86_64-linux-gnu/libswscale.so.4
#4  0x7fffbbc956b6 in sws_scale () from
/usr/lib/x86_64-linux-gnu/libswscale.so.4
#5  0x7fffb0f8df6a in ?? () from
/usr/lib/x86_64-linux-gnu/mlt/libmltavformat.so
#6  0x76fff928 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#7  0x77015919 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#8  0x76fff8d7 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#9  0x770122dd in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#10 0x7fffeecdd6da in start_thread (arg=0x7fff6fb13700) at
pthread_create.c:456
#11 0x7065d17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 37 (Thread 0x7fff70314700 (LWP 11414)):
#0  0x7173ee97 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#1  0x719580b7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#2  0x719651e1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#3  0x719b1214 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#4  0x719b8442 in QRasterPaintEngine::drawImage(QPointF const&, QImage
const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x719d614b in QPainter::drawImage(QPointF const&, QImage const&) ()
from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#6  0x7fffa7ba43fb in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltqt.so
#7  0x76fff8d7 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#8  0x77015919 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#9  0x76fff8d7 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6



Video cliup is created by phantom 4 PRO

Codec: H264 - MPEG-4 AVC (part 10) (avc1)
Resolution: 2720x1538
Display resolution: 2720x1530
Frame rate: 59.940060
Decoded format: Planar 4:2:0 YUV

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

[kmail2] [Bug 379406] White space in message viewer on dark theme

[Colin J Thomson]

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

Colin J Thomson  changed:

   What|Removed |Added

 CC||colin.thom...@g6avk.co.uk

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

[kmail2] [Bug 379406] New: White space in message viewer on dark theme

[sedrubal]

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

Bug ID: 379406
   Summary: White space in message viewer on dark theme
   Product: kmail2
   Version: 5.4.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: k...@sedrubal.de
  Target Milestone: ---

Created attachment 105298
  --> https://bugs.kde.org/attachment.cgi?id=105298=edit
White space in message viewer on Breeze Dark Theme

When you have a dark theme (Breeze Dark / Arc Dark) you can see are white
squares in the message viewer on places with no content (see screenshot). This
happens with plain text and HTML e-mails.

I'm not sure but I think this happened after switching to Arc Dark theme but
now it also happens with Breeze Dark.

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

[valgrind] [Bug 379373] Syscall param msg->desc.port.name points to uninitialised byte(s) on macOS 10.12

[Louis Brunner]

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

Louis Brunner  changed:

   What|Removed |Added

 CC||louis.brunner...@gmail.com

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

[kwin] [Bug 379397] Startup crash

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||arsenarsen...@outlook.com

--- Comment #65 from Martin Gräßlin  ---
*** Bug 379397 has been marked as a duplicate of this bug. ***

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

[cantor] [Bug 379404] Cantor can't initialize session for maxima backend

[bugzilla_noreply]

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

--- Comment #2 from hackitfor...@gmail.com ---
(In reply to Filipe Saraiva from comment #1)
> Hi @hackitforfun, I could not reproduce your bug. Please, could you provide
> the output of 'maxima -v' command?
> 
> In my case:
> 
> $ maxima -v
> + '[' clisp = clisp ']'
> + '[' true = true ']'
> + '[' -x /usr/lib/maxima/5.39.0/binary-clisp/maxima ']'
> + exec /usr/lib/maxima/5.39.0/binary-clisp/lisp.run -q -M
> /usr/lib/maxima/5.39.0/binary-clisp/maxima.mem '' -- -v
> Maxima 5.39.0 http://maxima.sourceforge.net
> using Lisp CLISP 2.49 (2010-07-07)
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
> (%i1)
Thanks for the reply, here's the output

❯ maxima -v
+ '[' ecl = clisp ']'
+ '[' ecl = cmucl ']'
+ '[' ecl = scl ']'
+ '[' ecl = gcl ']'
+ '[' ecl = acl ']'
+ '[' ecl = openmcl ']'
+ '[' ecl = ccl64 ']'
+ '[' ecl = ecl ']'
+ exec /usr/lib/maxima/5.39.0/binary-ecl/maxima -- -v
;;; Loading #P"/usr/lib/ecl-16.1.2/sb-bsd-sockets.fas"
;;; Loading #P"/usr/lib/ecl-16.1.2/sockets.fas"
;;; Loading #P"/usr/lib/ecl-16.1.2/defsystem.fas"
;;; Loading #P"/usr/lib/ecl-16.1.2/cmp.fas"
Maxima 5.39.0 http://maxima.sourceforge.net
using Lisp ECL 16.1.2
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1)

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

[kwin] [Bug 379398] KWin Crash after installation of VirtualBox extensions

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||wolfgang@aon.at

--- Comment #64 from Martin Gräßlin  ---
*** Bug 379398 has been marked as a duplicate of this bug. ***

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

[cantor] [Bug 379404] Cantor can't initialize session for maxima backend

[Filipe Saraiva]

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

--- Comment #1 from Filipe Saraiva  ---
Hi @hackitforfun, I could not reproduce your bug. Please, could you provide the
output of 'maxima -v' command?

In my case:

$ maxima -v
+ '[' clisp = clisp ']'
+ '[' true = true ']'
+ '[' -x /usr/lib/maxima/5.39.0/binary-clisp/maxima ']'
+ exec /usr/lib/maxima/5.39.0/binary-clisp/lisp.run -q -M
/usr/lib/maxima/5.39.0/binary-clisp/maxima.mem '' -- -v
Maxima 5.39.0 http://maxima.sourceforge.net
using Lisp CLISP 2.49 (2010-07-07)
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1)

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

[plasmashell] [Bug 369430] QQmlDelegateModel::_q_itemsChanged - kickoff version

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||marcboo...@gmail.com

--- Comment #15 from David Edmundson  ---
*** Bug 379393 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 379393] Plasma crashes with pacman

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
thanks

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

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

[valgrind] [Bug 365327] Support macOS Sierra (10.12)

[Louis Brunner]

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

--- Comment #24 from Louis Brunner  ---
Hi Rhys,

Thank you for the merge!

While making the changes for the new dylib loading, I encountered a crash
coming from is_in_syscall.
I blamed it on the experimental nature of my patch at the time and I can't
remember what triggered the crash.

You mentioned that you had older macOS VMs, do you have any advice/guide of any
sort to help me set one up for testing?
I could look into the failing test and the warnings linked to `getentropy` and
`ulock_wake` (if you didn't fix them already).

I was also working on a new version that included a pselect syscall wrapper
(found it missing while testing python with valgrind), I will add it later.

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

[krunner] [Bug 379045] Searching in Simple Menu / Application Launcher / KRunner spikes CPU usage ranging from 25% to 100%

[Jayesh Bhoot]

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

--- Comment #7 from Jayesh Bhoot  ---
(In reply to Travis J from comment #6)
> At this point I guess this bug was fedora specific.

I agree with you; so far only Fedora users have reported this bug.

> If you've been updating
> you may have seen it survive a plasma package update, but after that
> sometime last week a "plasma-settings" package dropped, I assume this is
> fedora's settings for plasma.

I do recall seeing plasma related package(s) in one of the updates, but felt it
was too ambiguous to mention here.

> I haven't seen the bug since, but I've been
> avoiding triggering it.

I suggest you to try. I hope the other participants do the same; it would free
Kai Uwe as soon as possible from this bug.

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