[plasmashell] [Bug 391595] Icons-only Task Manager spewing out a lot of errors in syslog in KDE 5.12

[Ahmad Samir]

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

Ahmad Samir  changed:

   What|Removed |Added

 CC||a.samir...@gmail.com

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

[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention

[bugzilla_noreply]

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

--- Comment #2 from triffid.hun...@gmail.com ---
https://phabricator.kde.org/D12916

wow, that's the most complicated patch submission process I've ever
experienced!

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

[kaffeine] [Bug 394306] New: not getting title in osd or epg

[Huntx011]

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

Bug ID: 394306
   Summary: not getting title in osd or epg
   Product: kaffeine
   Version: 2.0.14
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mchehab+sams...@kernel.org
  Reporter: huntclx...@gmail.com
  Target Milestone: ---

what info do you need

also, cannot schedule recording from program guide (which has correct program
times / duration)

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

[krusader] [Bug 381675] Can't run shared object (library)

[Nikita Melnichenko]

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

Nikita Melnichenko  changed:

   What|Removed |Added

 CC||nikita+...@melnichenko.name
 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |NEEDSINFO

--- Comment #7 from Nikita Melnichenko  ---
Can't repro:

- test.cpp -

#include 
#include 
using namespace std;

int main () {
  ofstream myfile;
  myfile.open ("example.txt");
  myfile << "Writing this to a file.\n";
  myfile.close();
  return 0;
}

- terminal -

$ g++ -fPIC -pie test.cpp
$ file a.out
a.out: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, not
stripped
$ ./a.out
$ ls
a.out  example.txt  test.cpp
$ rm example.txt
$ # run from krusader
$ ls
a.out  example.txt  test.cpp

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

[BalooWidgets] [Bug 394305] New: autotests fail with baloo from frameworks 5.46

[Rik Mills]

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

Bug ID: 394305
   Summary: autotests fail with baloo from frameworks 5.46
   Product: BalooWidgets
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: baloo-bugs-n...@kde.org
  Reporter: rikmi...@kubuntu.org
  Target Milestone: ---

On KDE CI and ubuntu infra autotests

>From KDE CI

https://build.kde.org/job/Applications%20baloo-widgets%20stable-kf5-qt5%20SUSEQt5.9/8/testReport/

* Start testing of ExtractorTest *
Config: Using QtTest library 5.9.4, Qt 5.9.4 (x86_64-little_endian-lp64 shared
(dynamic) release build; by GCC 7.3.1 20180307 [gcc-7-branch revision 258314])
PASS   : ExtractorTest::initTestCase()
QDEBUG : ExtractorTest::test() "QMap()\n"
FAIL!  : ExtractorTest::test() Compared values are not the same
   Actual   (data.value(QLatin1String("channels")).toInt()): 0
   Expected (2): 2
   Loc: [/home/jenkins/workspace/Applications baloo-widgets stable-kf5-qt5
SUSEQt5.9/autotests/extractortest.cpp(53)]
PASS   : ExtractorTest::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 131ms
* Finished testing of ExtractorTest *

* Start testing of FileMetadataItemCountTest *
Config: Using QtTest library 5.9.4, Qt 5.9.4 (x86_64-little_endian-lp64 shared
(dynamic) release build; by GCC 7.3.1 20180307 [gcc-7-branch revision 258314])
PASS   : FileMetadataItemCountTest::initTestCase()
QWARN  : FileMetadataItemCountTest::testItemCount() Failed enumerating UDisks2
objects: "org.freedesktop.DBus.Error.Disconnected" 
 "Not connected to D-Bus server"
QWARN  : FileMetadataItemCountTest::testItemCount() Failed enumerating UDisks2
objects: "org.freedesktop.DBus.Error.Disconnected" 
 "Not connected to D-Bus server"
FAIL!  : FileMetadataItemCountTest::testItemCount() Compared values are not the
same
   Actual   (items.count()) : 36
   Expected (expectedItems * widgetsPerItem): 38
   Loc: [/home/jenkins/workspace/Applications baloo-widgets stable-kf5-qt5
SUSEQt5.9/autotests/filemetadataitemcounttest.cpp(86)]
PASS   : FileMetadataItemCountTest::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 146ms
* Finished testing of FileMetadataItemCountTest *

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

[frameworks-baloo] [Bug 394160] Search (alt+space, or via app menu) does not display files unless they have been opened in current session

[Ivar Erikson]

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

--- Comment #3 from Ivar Erikson  ---
Problem is that in this case it wasn't just newly created files it didn't find;
it didn't find anything except those files that had been opened during the
active desktop session.

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

[systemsettings] [Bug 394001] Shift+Delete is assigned to two actions (Delete and Cut (Alternate))

[Ivar Erikson]

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

--- Comment #4 from Ivar Erikson  ---
Plasma: 5.12.4
KDE Framework: 5.44.0

Alright, I wasn't aware of it being a common one for cut too. Might be due to
my being used to it as Delete, from using Windows earlier.

But I'm farily certain that on earlier versions [of Plasma] (or at leas as
shipped in Kubuntu <17.04) there was no such ambiguity, i.e. shit+del was
*only* delete (as in bypass the bin).

It does pose a usability/UX problem imo. If you come to KDE expecting shift+del
to have a function [in Dolphin], having a fairly common shortcut give you an
error straight out of the box doesn't look good. And for an unexperienced user
it might not be that easy to solve.

---

Okay, so I tested a bit. In Kate and Libreoffice, shift+delete does work as Cut
(on text / cells), even though I've removed it from Cut in System Settings >
Shortcuts > Standard Shortcuts, and assigned only as Delete. So even when
reassigned to Delete, it still retains the Cut action while inside
applications. Not sure if relevant, just wanted to mention it.

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

[plasmashell] [Bug 394304] New: Plasmashell crashing under wayland

[Pedro Gabriel Drumond Pereira]

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

Bug ID: 394304
   Summary: Plasmashell crashing under wayland
   Product: plasmashell
   Version: 5.12.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: japabras...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.5)

Qt Version: 5.10.1
Frameworks Version: 5.46.0
Operating System: Linux 4.16.8-1-zen x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was openning a image on krita when plasmashell sudenly stopped working

- Unusual behavior I noticed:
Krita crashed, them plasmashell crashed

- Custom settings of the application:
I have no custom settings at all.

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

Thread 18 (Thread 0x7f2ce17fa700 (LWP 1755)):
#0  0x7f2dd30e8ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2dd3f31f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2d1d6fe149 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f2d1d702029 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f2d1d6fd20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f2d1d700079 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f2dd3f30abd in  () at /usr/lib/libQt5Core.so.5
#7  0x7f2dd30e3075 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f2dd383453f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f2ce1ffb700 (LWP 1754)):
#0  0x7f2dd30e8ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2dd3f31f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2d1d6fe149 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f2d1d702029 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f2d1d6fd20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f2d1d700079 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f2dd3f30abd in  () at /usr/lib/libQt5Core.so.5
#7  0x7f2dd30e3075 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f2dd383453f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f2ce27fc700 (LWP 1753)):
#0  0x7f2dd30e8ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2dd3f31f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2d1d6fe149 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f2d1d702029 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f2d1d6fd20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f2d1d702082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f2d1d6fd20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f2d1d700079 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f2dd3f30abd in  () at /usr/lib/libQt5Core.so.5
#9  0x7f2dd30e3075 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f2dd383453f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f2ce2ffd700 (LWP 1751)):
#0  0x7f2dd30e8ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2dd3f31f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2d1d6fe149 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f2d1d702029 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f2d1d6fd20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f2d1d700079 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f2dd3f30abd in  () at /usr/lib/libQt5Core.so.5
#7  0x7f2dd30e3075 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f2dd383453f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f2ce37fe700 (LWP 1750)):
#0  0x7f2dd30e8ffc in 

[dolphin] [Bug 394303] Crash when deleting something in /var folder (for which I don't believe Trash is setup for)

[Eric Fontaine]

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

--- Comment #1 from Eric Fontaine  ---
hmm...I can't reproduce now.  I opened /var/videos folder again, and this time
deleted the same file, and kde does move it to my home's trash folder.

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

[dolphin] [Bug 394303] New: Crash when deleting something in /var folder (for which I don't believe Trash is setup for)

[Eric Fontaine]

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

Bug ID: 394303
   Summary: Crash when deleting something in /var folder (for
which I don't believe Trash is setup for)
   Product: dolphin
   Version: 18.04.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ericrfonta...@hotmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (18.04.1)

Qt Version: 5.10.1
Frameworks Version: 5.46.0
Operating System: Linux 4.16.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

Opened dolphin and navigated to /var/videos (which is a folder when I save a
bunch of videos).  Then pressed delete on keyboard.

- Custom settings of the application:

As I mentioned, I don't actually have trash setup for that folder.  If I were
to use mate's file manager, then the same action of pressing delete will delete
those files permanently.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff5ab236800 (LWP 20982))]

Thread 3 (Thread 0x7ff588f14700 (LWP 20985)):
#0  0x7ff5aaaf7934 in read () from /usr/lib/libc.so.6
#1  0x7ff59b6feed1 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7ff59b6b8ff8 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7ff59b6b94c6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7ff59b6b963e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7ff5a4cf3264 in QEventDispatcherGlib::processEvents
(this=0x7ff58b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7ff5a4c9e96c in
QEventLoop::exec(QFlags) () at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7ff5a4acda09 in QThread::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7ff5a4ad285e in QThreadPrivate::start(void*) () at
thread/qthread_unix.cpp:376
#9  0x7ff5a013c075 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7ff5aab0653f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7ff591403700 (LWP 20984)):
#0  0x7ff5aaaf7934 in read () from /usr/lib/libc.so.6
#1  0x7ff59b6feed1 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7ff59b6b8ff8 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7ff59b6b94c6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7ff59b6b963e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7ff5a4cf3264 in QEventDispatcherGlib::processEvents
(this=0x7ff584000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7ff5a4c9e96c in
QEventLoop::exec(QFlags) () at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7ff5a4acda09 in QThread::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7ff5a511fb56 in QDBusConnectionManager::run (this=0x7ff5a5395080
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#9  0x7ff5a4ad285e in QThreadPrivate::start(void*) () at
thread/qthread_unix.cpp:376
#10 0x7ff5a013c075 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7ff5aab0653f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7ff5ab236800 (LWP 20982)):
[KCrash Handler]
#6  0x7ff5aa774fcf in KStandardItem::setDataValue(QByteArray const&,
QVariant const&) () from /usr/lib/libdolphinprivate.so.5
#7  0x7ff5aa775582 in KStandardItem::setIcon(QString const&) () from
/usr/lib/libdolphinprivate.so.5
#8  0x7ff5aae2f63a in ?? () from /usr/lib/libkdeinit5_dolphin.so
#9  0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaa7b0,
r=0x7ff5ab09e070, this=0x55d6ecdc5aa0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#10 QMetaObject::activate(QObject*, int, int, void**) () at
kernel/qobject.cpp:3750
#11 0x7ff5aae56190 in ?? () from /usr/lib/libkdeinit5_dolphin.so
#12 0x7ff5aae24949 in ?? () from /usr/lib/libkdeinit5_dolphin.so
#13 0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaa8c0,
r=0x7ff5ab09e070, this=0x55d6ec982fd0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#14 QMetaObject::activate(QObject*, int, int, void**) () at
kernel/qobject.cpp:3750
#15 0x7ff5a90a82fd in ?? () from /usr/lib/libKF5KIOCore.so.5
#16 0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaab80,
r=0x7ff5a9313400, this=0x55d6ed10e720) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#17 QMetaObject::activate(QObject*, int, int, void**) () at
kernel/qobject.cpp:3750
#18 0x7ff5a66386ed in KJob::result(KJob*, 

[konsole] [Bug 394276] Alt+Backspace sends wrong sequence

[Ahmad Samir]

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

--- Comment #6 from Ahmad Samir  ---
(In reply to Kurt Hindenburg from comment #5)
> OK my fault, I had an old default.keytab so my testing didn't work.  I'll
> commit the fix shortly and backport it to 18.04.2

Great :)

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

[krita] [Bug 393453] Spacing of brush reset from 0.01 to 0.02 when overwriting it

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kri
   ||ta/65e24ca59b97b8f9fca6b70f
   ||967e24f8045ad101

--- Comment #4 from Scott Petrovic  ---
Git commit 65e24ca59b97b8f9fca6b70f967e24f8045ad101 by Scott Petrovic.
Committed on 16/05/2018 at 03:19.
Pushed by scottpetrovic into branch 'master'.
Related: bug 0, bug 02

M  +1-1plugins/paintops/libpaintop/kis_spacing_selection_widget.cpp

https://commits.kde.org/krita/65e24ca59b97b8f9fca6b70f967e24f8045ad101

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

[ksudoku] [Bug 240947] Red background problem

[Ian Wadham]

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

Ian Wadham  changed:

   What|Removed |Added

 CC||iandw...@gmail.com

--- Comment #3 from Ian Wadham  ---
I think NitroGL is saying that you can cheat if you have the red highlight on
for errors. Just try every possible number in a cell until one comes up
correct. So what?

I would mark this as a WONTFIX.

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

[ksudoku] [Bug 229087] Sudoku rules are wrong

[Ian Wadham]

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

Ian Wadham  changed:

   What|Removed |Added

 CC||iandw...@gmail.com

--- Comment #3 from Ian Wadham  ---
I think this can be safely closed.

KSudoku had had major changes back then, made by an author who left the job
half done. There were some really bad problems which I fixed in 2011 and after.

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

[kwin] [Bug 384091] Add a window placement mode that remembers prior window position

[Nate Graham]

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

--- Comment #8 from Nate Graham  ---
Wow, so I can.

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

[Discover] [Bug 394302] New: plasma-discover crashes after pressing "Applications" or "Installed" tabs

[bugzilla_noreply]

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

Bug ID: 394302
   Summary: plasma-discover crashes after pressing "Applications"
or "Installed" tabs
   Product: Discover
   Version: 5.12.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: ulas...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.12.5)

Qt Version: 5.10.1
Frameworks Version: 5.44.0
Operating System: Linux 4.16.8-300.fc28.x86_64 x86_64
Distribution: "Fedora release 28 (Twenty Eight)"

-- Information about the crash:
- What I was doing when the application crashed:
YouTube video playing and a terminal open. The app opens without any problems
and the other tabs work fine it's just the Applications and Installed tabs that
make it crash.

- Unusual behavior I noticed:
When I run it from the terminal I get this:

invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not
found! Check your KNS3 installation."
Discarding invalid backend "servicemenu.knsrc"
Discarding invalid backend "ksysguard.knsrc"
could not find "org.kde.kdenlive.desktop" ""
could not find "org.kde.development" ""
could not find "org.kde.kdenlive.desktop" ""
could not find "org.kde.development" ""
could not find "org.kde.kdenlive.desktop" ""
could not find "org.kde.development" ""
could not find "org.kde.kdenlive.desktop" ""
could not find "org.kde.development" ""
KCrash: Application 'plasma-discover' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

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 0x7f20b747ae00 (LWP 17461))]

Thread 12 (Thread 0x7f2071280700 (LWP 17578)):
#0  0x7f20bf1a88e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f20c1af7736 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f20c1af4662 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f20c1af711d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f20bf1a2564 in start_thread () from /lib64/libpthread.so.0
#5  0x7f20c0e3431f in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f2087514700 (LWP 17577)):
#0  0x7f20bf1a88e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f20c1af7736 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f20c1af4662 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f20c1af711d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f20bf1a2564 in start_thread () from /lib64/libpthread.so.0
#5  0x7f20c0e3431f in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f20728d6700 (LWP 17473)):
#0  0x7f20c0e29929 in poll () from /lib64/libc.so.6
#1  0x7f20ba89bb06 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f20ba89bc30 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f20c1cf5c2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f20c1ca412b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f20c1af29c6 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f20c1af711d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f20bf1a2564 in start_thread () from /lib64/libpthread.so.0
#8  0x7f20c0e3431f in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f207376f700 (LWP 17470)):
#0  0x7f20c0e29929 in poll () from /lib64/libc.so.6
#1  0x7f20ba89bb06 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f20ba89bec2 in g_main_loop_run () from /lib64/libglib-2.0.so.0
#3  0x7f2085f0b60a in gdbus_shared_thread_func () from
/lib64/libgio-2.0.so.0
#4  0x7f20ba8c3cea in g_thread_proxy () from /lib64/libglib-2.0.so.0
#5  0x7f20bf1a2564 in start_thread () from /lib64/libpthread.so.0
#6  0x7f20c0e3431f in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f2073f70700 (LWP 17469)):
#0  0x7f20ba89b2d5 in g_main_context_query () from /lib64/libglib-2.0.so.0
#1  0x7f20ba89ba87 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f20ba89bc30 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f20ba89bc81 in glib_worker_main () from /lib64/libglib-2.0.so.0
#4  0x7f20ba8c3cea in g_thread_proxy () from /lib64/libglib-2.0.so.0
#5  0x7f20bf1a2564 in start_thread () from /lib64/libpthread.so.0
#6  

[ksudoku] [Bug 342626] Suggestion for additional perform: the numbers in different colors

[Ian Wadham]

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

--- Comment #2 from Ian Wadham  ---
I think the request is for when you have to "guess" a number in a cell, rather
than deduce it logically. As you continue on, a wrong guess will lead to a
situation where there is no valid move. You then have to backtrack and try
another guess (Undo several moves), but it is hard to remember where your
guessing point was, especially if you have had more than one of them.

So it would be handy if you could change the color of the numbers, starting
where the guess occurs, or use some other graphical method, such as
highlighting or lowlighting.

An early version of KSudoku also had "Push" and "Pop", which I think was a
temporary save and restore on a push-down stack, as opposed to the "Save" and
"Load" actions on the Game menu. A similar scheme could be tried, but please
consider players who are not computer scientists and not call the actions
"Push" and "Pop".

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

[ksudoku] [Bug 369206] Layout of "too easy" message has deteriorated

[Ian Wadham]

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

--- Comment #4 from Ian Wadham  ---
I think this may be a problem in KF5 or Qt5 message box implementation. Maybe
report it upstream.

Never happened in earlier version of KDE and Qt, except about 15 years ago when
ALL messages came out as one long line. So back then I used my own wrapping
version of KMessageBox, but no way should that be necessary today.

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

[plasmashell] [Bug 394301] New: Plasma crash upon opening Firefox

[John M . Vietta]

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

Bug ID: 394301
   Summary: Plasma crash upon opening Firefox
   Product: plasmashell
   Version: 5.12.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: johnvie...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.5)

Qt Version: 5.10.0
Frameworks Version: 5.46.0
Operating System: Linux 4.13.0-41-generic x86_64
Distribution: KDE neon User Edition 5.12

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

Just after booting, opened Konsole, then attempted to open Firefox

- Unusual behavior I noticed:

plama crashed then restarted

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
[Current thread is 1 (Thread 0x7ff03d8a08c0 (LWP 1508))]

Thread 15 (Thread 0x7fef58ff9700 (LWP 1655)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff03760a67b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x2d8bba0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x6e51d60,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fef800bca8b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x6b9f240, th=) at
/workspace/build/src/weaver.cpp:594
#4  0x7fef800bd78f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x6b9f240,
th=th@entry=0x7fef500025d0, threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at /workspace/build/src/weaver.cpp:554
#5  0x7fef800c1868 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x514c450, th=0x7fef500025d0, wasBusy=) at
/workspace/build/src/workinghardstate.cpp:66
#6  0x7fef800bc9ed in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fef500025d0, wasBusy=) at
/workspace/build/src/weaver.cpp:568
#7  0x7fef800c18c2 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x514c450, th=0x7fef500025d0, wasBusy=) at
/workspace/build/src/workinghardstate.cpp:73
#8  0x7fef800bc9ed in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fef500025d0, wasBusy=) at
/workspace/build/src/weaver.cpp:568
#9  0x7fef800bf3e0 in ThreadWeaver::Thread::run (this=0x7fef500025d0) at
/workspace/build/src/thread.cpp:103
#10 0x7ff0376096eb in QThreadPrivate::start (arg=0x7fef500025d0) at
thread/qthread_unix.cpp:376
#11 0x7ff0364ae6ba in start_thread (arg=0x7fef58ff9700) at
pthread_create.c:333
#12 0x7ff036f1641d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fef597fa700 (LWP 1654)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff03760a67b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x2d8bba0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x6e51d60,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fef800bca8b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x6b9f240, th=) at
/workspace/build/src/weaver.cpp:594
#4  0x7fef800bd78f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x6b9f240,
th=th@entry=0x6bdabf0, threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at /workspace/build/src/weaver.cpp:554
#5  0x7fef800c1868 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x514c450, th=0x6bdabf0, wasBusy=) at
/workspace/build/src/workinghardstate.cpp:66
#6  0x7fef800bc9ed in ThreadWeaver::Weaver::applyForWork (this=, th=0x6bdabf0, wasBusy=) at
/workspace/build/src/weaver.cpp:568
#7  0x7fef800c18c2 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x514c450, th=0x6bdabf0, wasBusy=) at
/workspace/build/src/workinghardstate.cpp:73
#8  0x7fef800bc9ed in ThreadWeaver::Weaver::applyForWork (this=, th=0x6bdabf0, wasBusy=) at
/workspace/build/src/weaver.cpp:568
#9  0x7fef800c18c2 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x514c450, th=0x6bdabf0, wasBusy=) at
/workspace/build/src/workinghardstate.cpp:73
#10 0x7fef800bc9ed in ThreadWeaver::Weaver::applyForWork (this=, th=0x6bdabf0, wasBusy=) at
/workspace/build/src/weaver.cpp:568
#11 0x7fef800c18c2 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x514c450, th=0x6bdabf0, wasBusy=) at
/workspace/build/src/workinghardstate.cpp:73

[krdc] [Bug 394221] KRDC Remove Bookmark folder

[SirSean]

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

--- Comment #5 from SirSean  ---
Kubuntu folks. I'll let them know. Thanks again!

On Tue, May 15, 2018, 3:38 PM Luigi Toscano 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=394221
>
> Luigi Toscano  changed:
>
>What|Removed |Added
>
> 
>  Resolution|WORKSFORME  |DOWNSTREAM
>
> --- Comment #4 from Luigi Toscano  ---
> More a packaging problem: the krdc package should at least "Suggest" the
> keditbookmarks package). You may want to report this to your distribution.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[KBibTeX] [Bug 394228] kbibtex sets parenthesis in wrong order

[manuel fernández]

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

--- Comment #2 from manuel fernández  ---
'KBibTeX Version Git revision unknown' 
It is the one pakaged with kubuntu bionic 18.04 
I copy the muon package manager version in case this helps:

kbibtex (0.8~20170819git31a77b27e8e83836e-3build2) bionic; urgency=medium
  * No-change rebuild for icu soname change.
 -- Matthias Klose   Tue, 07 Nov 2017 13:55:27 +

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

[ksudoku] [Bug 346143] Allow all similar number to be highlighted

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org
Summary|Allow all similar number to |Allow all similar number to
   |be hilighted|be highlighted

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

[ksudoku] [Bug 240947] Red background problem

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

Summary|Solving related bug |Red background problem

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

[ksudoku] [Bug 240947] Solving related bug

[Gregor Mi]

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

--- Comment #2 from Gregor Mi  ---
I am not sure if I understood the report correctly. I have created screenshot
where I wonder why the left-most "1" in the middle line is not marked red.

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

[kdenlive] [Bug 394300] New: Kdenlive stops responding after playing a clip (windows - 18-04-1)

[xnick]

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

Bug ID: 394300
   Summary: Kdenlive stops responding after playing a clip
(windows - 18-04-1)
   Product: kdenlive
   Version: 18.04.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: nicolascasaba...@gmail.com
  Target Milestone: ---

I want to try out the new 18.04.1 release of kdenlive for windows. What used to
be an annoying glitch in previous releases now makes the program unusable:
after loading some clips and setting up the timeline, I get to use the play
button only once. After stopping and trying to play again, the controls stop
responding and kdenlive appears to be busy doing something for quite some time.

If I wait, I can still do some edits, save files, and so on. But the play
button doesn't work anymore.

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

[ksudoku] [Bug 240947] Solving related bug

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

--- Comment #1 from Gregor Mi  ---
Created attachment 112679
  --> https://bugs.kde.org/attachment.cgi?id=112679=edit
Left-middle 1 is not red. Why?

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

[ksudoku] [Bug 234036] preview for "Abstraction" and "Scrible" are not visible

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Gregor Mi  ---
This was probably fixed by now. At least with my version 1.4 I can see previews
for all three themes.

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

[ksudoku] [Bug 229087] Sudoku rules are wrong

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||codestr...@posteo.org
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Gregor Mi  ---
Hello shino,
thanks for reporting this issue. Eight years have passed and there was some
development in KSudoku. Did you encounter your problem with a more recent
version?

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

[krita] [Bug 394299] New: Wet type color mixture of brushes

[bugzilla_noreply]

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

Bug ID: 394299
   Summary: Wet type color mixture of brushes
   Product: krita
   Version: 4.0.3
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush Engine/Bristle
  Assignee: krita-bugs-n...@kde.org
  Reporter: cok_dr...@hotmail.com
  Target Milestone: ---

This is a bug caused by the wet_Bristles brush.
If you draw on a transparently protected layer, it picks up black from the
transparent part and it will be mixed.
This is not a phenomenon that occurs only in the current version, but it
existed from a long ago version. Previously it was white.
I do not know whether it is a bug or a specification,It is very hard to use, so
I'd like to ask you to fix it.

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

[konsole] [Bug 394276] Alt+Backspace sends wrong sequence

[Kurt Hindenburg]

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

--- Comment #5 from Kurt Hindenburg  ---
OK my fault, I had an old default.keytab so my testing didn't work.  I'll
commit the fix shortly and backport it to 18.04.2

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

[ksudoku] [Bug 381087] Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu.

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||atim...@yandex.ru

--- Comment #6 from Gregor Mi  ---
*** Bug 385792 has been marked as a duplicate of this bug. ***

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

[ksudoku] [Bug 385792] ksudoku: Неизвестный параметр qwindowtitle.

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||codestr...@posteo.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Gregor Mi  ---


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

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

[ksudoku] [Bug 348179] numeric keypad doesn't work with shift (for markers)

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

--- Comment #1 from Gregor Mi  ---
I tried with 4x4 game.

- SHIFT NUMPAD 1 is working properly for me
- SHIFT NUMPAD 3 is working properly for me
- For SHIFT NUMPAD 2 I get this message: "The key sequence 'Down' is ambiguous.
Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No
action will be triggered.". The NUMPAD 2 key has a downarrow.
- For SHIFT NUMPAD 4 I get a similar message for key sequence 'Left'

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

[ksudoku] [Bug 342626] Suggestion for additional perform: the numbers in different colors

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org
   Severity|normal  |wishlist

--- Comment #1 from Gregor Mi  ---
Hello, thanks for the request. I don't understand which numbers you mean. Could
you please explain more.

I change this ticket to wishlist.

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

[ksudoku] [Bug 268265] Game time is not shown at the end of Tiny Samurai.

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||codestr...@posteo.org
 Resolution|--- |WORKSFORME

--- Comment #1 from Gregor Mi  ---
Did you try with a more recent version of KSudoku. It works for me here.

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

[ksudoku] [Bug 357999] Missing word in Low Difficulty warning message

[Gregor Mi]

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

--- Comment #1 from Gregor Mi  ---
This new message could solve this ticket: https://phabricator.kde.org/D12908

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

[ksudoku] [Bug 357999] Missing word in Low Difficulty warning message

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

Summary|Missing word in error   |Missing word in Low
   |message |Difficulty warning message
 CC||codestr...@posteo.org

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

[ksudoku] [Bug 369206] Layout of "too easy" message has deteriorated

[Gregor Mi]

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

--- Comment #3 from Gregor Mi  ---
I suspect that this has nothing to do with KSudoku itself. My development
version has a slightly larger font which might cause the nice wrapping.

I tried this on the console to test the wrapping behaviour in general:

$ kdialog --msgbox "Hallo alkjs dfklaj sdkfjakldjf kl;ajdfk ljaskfaklsdj
klajsdklfj askklasdjf klajsdklfg jaksldfg asdf aksdj kjasdfk lj;askf klasdjf
klasjdf asdkfgjkal sjdkfgj aksdjf klasjdf;kl jasdlkq;'j kasdfg" # wraps nicely

$ kdialog --msgbox "Hallo alkjs dfklaj sdkfjakldjf kl;ajdfk ljaskfaklsdj
klajsdklfj askklasdjf klajsdklfg jaksldfg asdf aksdj kjasdfk lj;askf klasdjf
klasjdf" # shows one long line

As for this particular ticket, one could try to insert manual line breaks but I
am sure this will lead to other problems.

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

[ksudoku] [Bug 369206] Layout of "too easy" message has deteriorated

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

--- Comment #2 from Gregor Mi  ---
With my installed KSudoku 1.4 on KDE Frameworks 5.44.0 and Qt 5.10.0, I can
confirm this bug.

However, when I try with the current development version, the dialog text looks
nicely wrapped.

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

[ksudoku] [Bug 280092] There seems to be now way to tell ksudoku to play no sound

[Ian Wadham]

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

Ian Wadham  changed:

   What|Removed |Added

 CC||iandw...@gmail.com

--- Comment #2 from Ian Wadham  ---
Several KMessageBox methods have an "options" parameter which defaults to
"Notify". You could individually set the value of this parameter to zero in all
messages in KSudoku, I suppose.

But I think the idea of the default is to help implement Accessibility features
in KDE apps, which I think would be of value in KSudoku, eg. to a visually
impaired person who enjoys Sudoku puzzles.

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

[ksudoku] [Bug 357996] Finishing a game should disable hint and solve buttons and menu items

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

--- Comment #1 from Gregor Mi  ---
There is some work in progress here: https://phabricator.kde.org/D12912. But
currently, Undo won't re-enable the buttons again. Only a New game will
re-enable the buttons. The same is true for the menu items (buttons and menu
items will always behave consistent)

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

[krita] [Bug 394298] New: Wont let me save

[Esteban Dawson]

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

Bug ID: 394298
   Summary: Wont let me save
   Product: krita
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: estebandawso...@gmail.com
  Target Milestone: ---

wont save anything and gives me no reason

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

[gwenview] [Bug 394297] Ambiguous Shortcuts - Gwenview

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[gwenview] [Bug 377880] Gwenview There are two actions (Cut, Delete)

[Christoph Feck]

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

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

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

[gwenview] [Bug 394297] New: Ambiguous Shortcuts - Gwenview

[Ron]

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

Bug ID: 394297
   Summary: Ambiguous Shortcuts - Gwenview
   Product: gwenview
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: pinstriped...@yahoo.com
  Target Milestone: ---

There are two actions (Cut, Delete) that want to use the same shortcut
(Shift+Del). This is most probably a bug. Please report it in bugs.kde.org

Every time I try to open a picture file, I get this message:

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

[Discover] [Bug 394270] Launch button has no effect

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/dis
   ||cover/def5203424618f0f29e25
   ||c2a9c66e15decb007c4
 Resolution|--- |FIXED

--- Comment #1 from Aleix Pol  ---
Git commit def5203424618f0f29e25c2a9c66e15decb007c4 by Aleix Pol.
Committed on 15/05/2018 at 23:25.
Pushed by apol into branch 'Plasma/5.12'.

PackageKit: Try harder to find the application desktop file

M  +15   -4libdiscover/backends/PackageKitBackend/AppPackageKitResource.cpp

https://commits.kde.org/discover/def5203424618f0f29e25c2a9c66e15decb007c4

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

[plasmashell] [Bug 393804] Clipboard freezes when KVM/QEMU VM window is opened using virt-manager

[Peter Eszlari]

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

Peter Eszlari  changed:

   What|Removed |Added

 CC||peter.eszl...@gmail.com

--- Comment #2 from Peter Eszlari  ---
I'm seeing this bug too - running Ubuntu 18.04 in virt-manager on Kubuntu
18.04.

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

[ksudoku] [Bug 280092] There seems to be now way to tell ksudoku to play no sound

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 CC||codestr...@posteo.org

--- Comment #1 from Gregor Mi  ---
The sounds you are hearing come from the Plasma Notification system because
standard message boxes are used.

Currently, there are several options:

1) Mute all sounds - which does not work when you are playing music.

2) Go to Plasma "Audio Volume Settings" > Audio Volume > Applications >
Notifications Sounds. Reduce or mute the volume for all notification sounds.

3) Go to Plasma "Notifications" System Settings Module > Event Source: Plasma
Workspace. Look for "Information Message" and disable the "Play a Sound"
option.

I think your request is still valid because all three options are working
globally. I change this request to a wish though.

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

[ksudoku] [Bug 168616] Hint and Solve should have hotkeys that work from within the game

[Gregor Mi]

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

--- Comment #6 from Gregor Mi  ---
Changed ticket from Normal to Wishlist.

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

[ksudoku] [Bug 168616] Hint and Solve should have hotkeys that work from within the game

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org
 Status|CONFIRMED   |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
   Severity|normal  |wishlist

--- Comment #5 from Gregor Mi  ---
The hotkey for Hint is F2. And it works for me from within the game.

Is a hotkey for Solve really needed?

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

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

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
Git commit 7529727e46242d2fdd71c4e8c92363600373fcb6 by Nathaniel Graham.
Committed on 15/05/2018 at 22:33.
Pushed by ngraham into branch 'master'.

Ignore more types of source files

Summary:
Add more types of development-related files to the exclusion lists. These files
aren't useful to index, and having them there can bog down Baloo.
Related: bug 394002, bug 390932
FIXED-IN 5.47

Test Plan: Created a bunch of files of the newly excluded types. Baloo didn't
index them.

Reviewers: michaelh, bruns

Reviewed By: bruns

Subscribers: broulik, cfeck, kde-frameworks-devel, #baloo

Tags: #frameworks, #baloo

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

M  +37   -5src/file/fileexcludefilters.cpp

https://commits.kde.org/baloo/7529727e46242d2fdd71c4e8c92363600373fcb6

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

[frameworks-baloo] [Bug 394002] Ignore some common file patterns

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/bal
   ||oo/7529727e46242d2fdd71c4e8
   ||c92363600373fcb6
 Resolution|--- |FIXED

--- Comment #8 from Nate Graham  ---
Git commit 7529727e46242d2fdd71c4e8c92363600373fcb6 by Nathaniel Graham.
Committed on 15/05/2018 at 22:33.
Pushed by ngraham into branch 'master'.

Ignore more types of source files

Summary:
Add more types of development-related files to the exclusion lists. These files
aren't useful to index, and having them there can bog down Baloo.
Related: bug 390932, bug 382117
FIXED-IN 5.47

Test Plan: Created a bunch of files of the newly excluded types. Baloo didn't
index them.

Reviewers: michaelh, bruns

Reviewed By: bruns

Subscribers: broulik, cfeck, kde-frameworks-devel, #baloo

Tags: #frameworks, #baloo

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

M  +37   -5src/file/fileexcludefilters.cpp

https://commits.kde.org/baloo/7529727e46242d2fdd71c4e8c92363600373fcb6

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

[frameworks-baloo] [Bug 390932] Update default exclude filters

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/bal
   ||oo/7529727e46242d2fdd71c4e8
   ||c92363600373fcb6
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Nate Graham  ---
Git commit 7529727e46242d2fdd71c4e8c92363600373fcb6 by Nathaniel Graham.
Committed on 15/05/2018 at 22:33.
Pushed by ngraham into branch 'master'.

Ignore more types of source files

Summary:
Add more types of development-related files to the exclusion lists. These files
aren't useful to index, and having them there can bog down Baloo.
Related: bug 394002, bug 382117
FIXED-IN 5.47

Test Plan: Created a bunch of files of the newly excluded types. Baloo didn't
index them.

Reviewers: michaelh, bruns

Reviewed By: bruns

Subscribers: broulik, cfeck, kde-frameworks-devel, #baloo

Tags: #frameworks, #baloo

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

M  +37   -5src/file/fileexcludefilters.cpp

https://commits.kde.org/baloo/7529727e46242d2fdd71c4e8c92363600373fcb6

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

[plasmashell] [Bug 394035] "open wallpaper image" from desktop RMB menu does not work

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/pla
   ||sma-workspace/69a0e05bc54d0
   ||488c18bc2f0aad2e310eb581825
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Nate Graham  ---
Git commit 69a0e05bc54d0488c18bc2f0aad2e310eb581825 by Nathaniel Graham, on
behalf of Oded Arbel.
Committed on 15/05/2018 at 22:31.
Pushed by ngraham into branch 'master'.

Fixed access to current slideshow image using correct field in action_open

Summary:
With slideshow desktop wallpaper plugin, selecting "Open wallpaper Image" from
RMB does nothing. It looks like the `action_open` method called by the RMB menu
action is using an old field that no longer exists.

The patch updates the code to use the correct field.

Reviewers: #plasma_workspaces, ngraham, broulik

Reviewed By: #plasma_workspaces, ngraham, broulik

Subscribers: broulik, ngraham, plasma-devel

Tags: #plasma

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

M  +1-1wallpapers/image/imagepackage/contents/ui/main.qml

https://commits.kde.org/plasma-workspace/69a0e05bc54d0488c18bc2f0aad2e310eb581825

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

[ksudoku] [Bug 242300] "Play"-button hangs and Sudoku+Roxdoku 16+25 games do not start

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

--- Comment #7 from Gregor Mi  ---
https://phabricator.kde.org/D12908 extends the Unlimited message box to warn
users that the generation of Unlimited puzzles might take long time.

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

[dolphin] [Bug 354848] file association loophole: application automatically as default, even if i delete it from the list

[Wilfrido Vidana]

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

--- Comment #10 from Wilfrido Vidana  ---
Hi,

I don't use KDE anymore, but i'm glad to see this got resolved at some point,
keep up the good work!

Thanks everyone for the effor :)

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

[clazy] [Bug 394237] IDE-friendly URLs to documentation pages of checks

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/cla
   ||zy/dcac97b866c83d6645e3bc4a
   ||f1f42b255f81d9a3
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #4 from Sergio Martins  ---
Git commit dcac97b866c83d6645e3bc4af1f42b255f81d9a3 by Sergio Martins.
Committed on 15/05/2018 at 21:52.
Pushed by smartins into branch 'master'.

Make it easier to link to READMEs by removing the level name.

After make install they will still be installed to a level0, 1, 2 sub-folder,
as the cmake instructions are generated by generate.py

M  +3-5CMakeLists.txt
M  +75   -75   README.md
M  +42   -4dev-scripts/generate.py
R  +0-0docs/checks/README-assert-with-side-effects.md [from:
src/checks/level3/README-assert-with-side-effects.md - 100% similarity]
R  +0-0docs/checks/README-auto-unexpected-qstringbuilder.md [from:
src/checks/level1/README-auto-unexpected-qstringbuilder.md - 100% similarity]
R  +0-0docs/checks/README-base-class-event.md [from:
src/checks/level2/README-base-class-event.md - 100% similarity]
R  +0-0docs/checks/README-child-event-qobject-cast.md [from:
src/checks/level1/README-child-event-qobject-cast.md - 100% similarity]
R  +0-0docs/checks/README-connect-3arg-lambda.md [from:
src/checks/level1/README-connect-3arg-lambda.md - 100% similarity]
R  +0-0docs/checks/README-connect-by-name.md [from:
src/checks/level0/README-connect-by-name.md - 100% similarity]
R  +0-0docs/checks/README-connect-non-signal.md [from:
src/checks/level0/README-connect-non-signal.md - 100% similarity]
R  +0-0docs/checks/README-connect-not-normalized.md [from:
src/checks/level0/README-connect-not-normalized.md - 100% similarity]
R  +0-0docs/checks/README-const-signal-or-slot.md [from:
src/checks/level1/README-const-signal-or-slot.md - 100% similarity]
R  +0-0docs/checks/README-container-anti-pattern.md [from:
src/checks/level0/README-container-anti-pattern.md - 100% similarity]
R  +0-0docs/checks/README-container-inside-loop.md [from:
src/checks/manuallevel/README-container-inside-loop.md - 100% similarity]
R  +0-0docs/checks/README-copyable-polymorphic.md [from:
src/checks/level2/README-copyable-polymorphic.md - 100% similarity]
R  +0-0docs/checks/README-ctor-missing-parent-argument.md [from:
src/checks/level2/README-ctor-missing-parent-argument.md - 100% similarity]
R  +0-0docs/checks/README-detaching-member.md [from:
src/checks/level3/README-detaching-member.md - 100% similarity]
R  +0-0docs/checks/README-detaching-temporary.md [from:
src/checks/level1/README-detaching-temporary.md - 100% similarity]
R  +0-0docs/checks/README-foreach.md [from:
src/checks/level1/README-foreach.md - 100% similarity]
R  +0-0docs/checks/README-fully-qualified-moc-types.md [from:
src/checks/level0/README-fully-qualified-moc-types.md - 100% similarity]
R  +0-0docs/checks/README-function-args-by-ref.md [from:
src/checks/level2/README-function-args-by-ref.md - 100% similarity]
R  +0-0docs/checks/README-function-args-by-value.md [from:
src/checks/level2/README-function-args-by-value.md - 100% similarity]
R  +0-0docs/checks/README-global-const-char-pointer.md [from:
src/checks/level2/README-global-const-char-pointer.md - 100% similarity]
R  +0-0docs/checks/README-implicit-casts.md [from:
src/checks/level2/README-implicit-casts.md - 100% similarity]
R  +0-0docs/checks/README-incorrect-emit.md [from:
src/checks/level1/README-incorrect-emit.md - 100% similarity]
R  +0-0docs/checks/README-inefficient-qlist-soft.md [from:
src/checks/level1/README-inefficient-qlist-soft.md - 100% similarity]
R  +0-0docs/checks/README-inefficient-qlist.md [from:
src/checks/manuallevel/README-inefficient-qlist.md - 100% similarity]
R  +0-0docs/checks/README-install-event-filter.md [from:
src/checks/level1/README-install-event-filter.md - 100% similarity]
R  +0-0docs/checks/README-isempty-vs-count.md [from:
src/checks/manuallevel/README-isempty-vs-count.md - 100% similarity]
R  +0-0docs/checks/README-lambda-in-connect.md [from:
src/checks/level0/README-lambda-in-connect.md - 100% similarity]
R  +0-0docs/checks/README-lambda-unique-connection.md [from:
src/checks/level0/README-lambda-unique-connection.md - 100% similarity]
R  +0-0docs/checks/README-missing-qobject-macro.md [from:
src/checks/level2/README-missing-qobject-macro.md - 100% similarity]
R  +0-0docs/checks/README-missing-typeinfo.md [from:

[frameworks-kirigami] [Bug 394296] Kirigami tab widget should decide whether it wants to look like a conventional Tab View or a Segmented Control

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
(Note that making this into a Segmented Control-style widget would
automatically fix Bug 394295)

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

[frameworks-kirigami] [Bug 394296] Kirigami tab widget should decide whether it wants to look like a conventional Tab View or a Segmented Control

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
Created attachment 112678
  --> https://bugs.kde.org/attachment.cgi?id=112678=edit
ElementaryOS segmented control example 2

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

[frameworks-kirigami] [Bug 394296] New: Kirigami tab widget should decide whether it wants to look like a conventional Tab View or a Segmented Control

[Nate Graham]

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

Bug ID: 394296
   Summary: Kirigami tab widget should decide whether it wants to
look like a conventional Tab View or a Segmented
Control
   Product: frameworks-kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: n...@kde.org
  Target Milestone: Not decided

Created attachment 112677
  --> https://bugs.kde.org/attachment.cgi?id=112677=edit
ElementaryOS segmented control example 1

The Kirigami tab view widget only has a horizontal line rather than a full
frame, so you can't embed it inside a layout. And the line doesn't actually
touch the window edge and looks bad unless there are no side borders (see
https://phabricator.kde.org/T8707).

My sense is that the goal is to use the tab widget only at the very top and
have it span the full width. If that's the goal, I humbly suggest that creating
and using a Segmented Control widget instead would be more aesthetically
pleasing, and get rid of the horizontal line. ElementaryOS makes heavy use of
these and I think they work great and look fantastic (images attached).

If that's not feasible, I would recommend mimicking the look of the QWidgets
Tab widget and providing a full frame.

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

[frameworks-kirigami] [Bug 394295] New: Tab widget's inactive tabs don't connect with the line below them

[Nate Graham]

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

Bug ID: 394295
   Summary: Tab widget's inactive tabs don't connect with the line
below them
   Product: frameworks-kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: n...@kde.org
  Target Milestone: Not decided

Created attachment 112676
  --> https://bugs.kde.org/attachment.cgi?id=112676=edit
Kirigami tab widget in Gallery - inactive tabs don't connect

in Kirigami gallery, the inactive tabs don't connect with the line underneath
them. This is either a bug, or a design choice that *looks* like a bug. :) See
attached screenshot.

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

[Discover] [Bug 394294] New: Crash after clicking "update" in system tray

[bugzilla_noreply]

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

Bug ID: 394294
   Summary: Crash after clicking "update" in system tray
   Product: Discover
   Version: 5.12.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: wowhellm...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.12.5)

Qt Version: 5.10.0
Frameworks Version: 5.46.0
Operating System: Linux 4.13.0-41-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
- What I was doing when the application crashed:
I just tried to update system and discover crashed 2 seconds after clicking
"update" button in notification.
Now it immediately crashes every time i try to open it, even if i run it from
launcher.
I haven't messed with it any configuration files, everything is by default.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f18f63fb8c0 (LWP 8122))]

Thread 3 (Thread 0x7f18d934a700 (LWP 8125)):
[KCrash Handler]
#6  QByteArray::~QByteArray (this=, __in_chrg=)
at ../../include/QtCore/../../src/corelib/tools/qbytearray.h:469
#7  rawStringData (index=, mo=0x7f18f5a530e0 )
at kernel/qmetaobject.cpp:161
#8  QMetaProperty::name (this=this@entry=0x7f18d9348630) at
kernel/qmetaobject.cpp:2897
#9  0x7f18f2cb035a in QQmlPropertyCache::append
(this=this@entry=0x7f18cc1925d0, metaObject=metaObject@entry=0x7f18f5a530e0
, revision=revision@entry=-1,
propertyFlags=..., propertyFlags@entry=..., methodFlags=...,
methodFlags@entry=..., signalFlags=..., signalFlags@entry=...) at
qml/qqmlpropertycache.cpp:620
#10 0x7f18f2cb1e92 in QQmlPropertyCache::copyAndAppend
(this=0x7f18cc05e540, metaObject=0x7f18f5a530e0
, revision=revision@entry=-1,
propertyFlags=..., methodFlags=..., signalFlags=...) at
qml/qqmlpropertycache.cpp:470
#11 0x7f18f2cb1ec2 in QQmlPropertyCache::copyAndAppend (this=, metaObject=, propertyFlags=..., propertyFlags@entry=...,
methodFlags=..., methodFlags@entry=..., signalFlags=..., signalFlags@entry=...)
at qml/qqmlpropertycache.cpp:451
#12 0x7f18f2c78e49 in QQmlMetaTypeData::propertyCache (this=0x7f18f30275c0
<(anonymous namespace)::Q_QGS_metaTypeData::innerFunction()::holder>,
metaObject=metaObject@entry=0x7f18f5a530e0
) at qml/qqmlmetatype.cpp:2269
#13 0x7f18f2c78f22 in QQmlMetaType::propertyCache
(metaObject=metaObject@entry=0x7f18f5a530e0
) at qml/qqmlmetatype.cpp:2278
#14 0x7f18f2b0d8fc in QJSEnginePrivate::cache (metaObject=0x7f18f5a530e0
, this=) at
../../include/QtQml/5.10.0/QtQml/private/../../../../../src/qml/jsapi/qjsengine_p.h:187
#15 QQmlPropertyCacheCreator::propertyCacheForObject
(this=, obj=, context=..., error=0x7f18d93488c0)
at compiler/qqmlpropertycachecreator_p.h:236
#16 0x7f18f2b0fd4f in
QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=this@entry=0x7f18d9348a70, objectIndex=1, context=...) at
compiler/qqmlpropertycachecreator_p.h:151
#17 0x7f18f2b0fecd in
QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=this@entry=0x7f18d9348a70, objectIndex=objectIndex@entry=0, context=...)
at compiler/qqmlpropertycachecreator_p.h:172
#18 0x7f18f2b0be08 in
QQmlPropertyCacheCreator::buildMetaObjects
(this=0x7f18d9348a70) at compiler/qqmlpropertycachecreator_p.h:111
#19 QQmlTypeCompiler::compile (this=this@entry=0x7f18d9348c30) at
compiler/qqmltypecompiler.cpp:85
#20 0x7f18f2c8c7b1 in
QQmlTypeData::compile(QQmlRefPointer const&,
QV4::CompiledData::ResolvedTypeReferenceMap const&, std::function const&) (this=this@entry=0x7f18cc17bb70,
typeNameCache=..., resolvedTypeCache=..., dependencyHasher=...) at
qml/qqmltypeloader.cpp:2568
#21 0x7f18f2c92b66 in QQmlTypeData::done (this=0x7f18cc17bb70) at
qml/qqmltypeloader.cpp:2287
#22 0x7f18f2c89e4c in QQmlDataBlob::tryDone (this=0x7f18cc17bb70) at
qml/qqmltypeloader.cpp:659
#23 0x7f18f2c8a101 in QQmlTypeLoader::setData (this=this@entry=0x19be000,
blob=blob@entry=0x7f18cc17bb70, d=...) at qml/qqmltypeloader.cpp:1288
#24 0x7f18f2c8ab18 in QQmlTypeLoader::setData (this=this@entry=0x19be000,
blob=0x7f18cc17bb70, fileName=...) at qml/qqmltypeloader.cpp:1268
#25 0x7f18f2c8beda in QQmlTypeLoader::loadThread
(this=this@entry=0x19be000, blob=blob@entry=0x7f18cc17bb70) at
qml/qqmltypeloader.cpp:1143
#26 0x7f18f2c8c053 in PlainLoader::loadThread (this=,
blob=0x7f18cc17bb70, loader=0x19be000) at qml/qqmltypeloader.cpp:988
#27 QQmlTypeLoader::doLoad
(mode=QQmlTypeLoader::PreferSynchronous, blob=0x7f18cc17bb70, loader=...,
this=0x19be000) at qml/qqmltypeloader.cpp:1047
#28 

[dolphin] [Bug 394284] Entering a folder with a password-protected .docx file prompts user for password

[Rog131]

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

--- Comment #5 from Rog131  ---
An opinion: This is an example why the current Dolphin 'preview everything' is
not good idea.  Change was made with:
https://cgit.kde.org/dolphin.git/commit/?id=bebcf035d264410c943e7bad861628c1b14dd1f2

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

[LabPlot2] [Bug 394025] Crash when deleting spreadsheet

[Stefan Gerlach]

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

--- Comment #5 from Stefan Gerlach  ---
This problem also exists on Linux. Just do not select the spreadsheet first.
Here is a crash report:

#6  0x0082a861 in Column::setWidth(int) (this=0x0,
value=value@entry=778) at labplot/src/backend/core/column/Column.cpp:279
#7  0x00659da8 in SpreadsheetView::handleHorizontalSectionResized(int,
int, int) (this=, logicalIndex=1, oldSize=,
newSize=778) at labplot/src/commonfrontend/spreadsheet/SpreadsheetView.cpp:718
#8  0x006adb57 in SpreadsheetView::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=0x2b83a30, _c=,
_id=, _a=) at
labplot/build_debug/src/moc_SpreadsheetView.cpp:356
#9  0x7f31983867d1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f3199dc6e3d in QHeaderView::sectionResized(int, int, int) () at
/usr/lib64/libQt5Widgets.so.5
#11 0x7f3199dcbdea in  () at /usr/lib64/libQt5Widgets.so.5
#12 0x0088a6fc in SpreadsheetHeaderView::refresh() (this=0x2bce860) at
labplot/src/commonfrontend/spreadsheet/SpreadsheetHeaderView.cpp:141
#13 0x0088a73e in SpreadsheetHeaderView::showComments(bool)
(this=, on=) at
labplot/src/commonfrontend/spreadsheet/SpreadsheetHeaderView.cpp:128
#14 0x006577e2 in SpreadsheetView::showComments(bool) (this=, on=) at
labplot/src/commonfrontend/spreadsheet/SpreadsheetView.cpp:767
#15 0x00748746 in SpreadsheetDock::commentsShownChanged(int)
(this=, state=) at
labplot/src/kdefrontend/dockwidgets/SpreadsheetDock.cpp:136
#16 0x7f3198386de3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#17 0x7f3199c7909e in QCheckBox::stateChanged(int) () at
/usr/lib64/libQt5Widgets.so.5
#18 0x7f3199c65e3d in QAbstractButton::setChecked(bool) () at
/usr/lib64/libQt5Widgets.so.5
#19 0x00748c09 in SpreadsheetDock::load() (this=) at
labplot/src/kdefrontend/dockwidgets/SpreadsheetDock.cpp:181
#20 0x007493c7 in SpreadsheetDock::setSpreadsheets(QList)
(this=0x3000aa0, list=...) at
labplot/src/kdefrontend/dockwidgets/SpreadsheetDock.cpp:86
#21 0x006bfaf7 in
GuiObserver::selectedAspectsChanged(QList&) const
(this=0x26fe640, selectedAspects=...) at
labplot/src/kdefrontend/GuiObserver.cpp:153
#22 0x7f31983867d1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#23 0x00699fb9 in
ProjectExplorer::selectedAspectsChanged(QList&)
(this=this@entry=0x25ffc90, _t1=...) at
labplot/build_debug/src/moc_ProjectExplorer.cpp:258
#24 0x0067f51a in ProjectExplorer::selectionChanged(QItemSelection
const&, QItemSelection const&) (this=0x25ffc90, selected=..., deselected=...)
at labplot/src/commonfrontend/ProjectExplorer.cpp:589
#25 0x006a1ffd in ProjectExplorer::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _c=,
_id=, _a=) at
labplot/build_debug/src/moc_ProjectExplorer.cpp:178

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

[okular] [Bug 394288] Feature req: Mouse wheel constant browse speed mode

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
   Severity|normal  |wishlist

--- Comment #1 from Albert Astals Cid  ---
To be honest i don't think this makes much sense given we already have the
shift+up/down arrow automatic scrolling

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

[okular] [Bug 394267] Add auto save feature

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
   Severity|normal  |wishlist

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

[dolphin] [Bug 394284] Entering a folder with a password-protected .docx file prompts user for password

[Rog131]

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

Rog131  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|NEEDSINFO   |CONFIRMED
 CC||samrog...@hotmail.com
 Resolution|WAITINGFORINFO  |---

--- Comment #4 from Rog131  ---
(In reply to chansol98s from comment #2)
> (In reply to Julian Schraner from comment #1)
> > Hmm, I cannot reproduce this behavior. I do also run KDE Neon User Edition
> > 5.12.5 with Dolphin 18.04.1, but for me the password dialog only pops up
> > when I try to open the file (which is the expected behavior). Maybe you
> > could upload a document that triggers the bug for you just to rule out the
> > possibility that I did not create the .docx file the same way you did?
> > Thanks for reporting this bug & have a nice day :)
> 
> 
> After reading your reply, I experimented around a bit more...
> And it looks like Calligra Suite is somehow related to this behavior.
> 
> The bug disappears after running [apt remove calligra --autoremove] and
> reappears after running [apt install calligra].
> 
> So yeah, I think installing calligra may help you reproduce the bug.
> 
> 
> ...and just in case the bug still can't be reproduced, I'll add an
> attachment of a .docx file that cause the bug on my system.

The Calligra suite has the thumbnailer for the docx.

If the Calligra suite is installed and the thumbnailer is enabled for the .docx
then there is the 'Enter password' query when the thumbnailer is trying to make
the thumbnail.

The 'Untitled 1.docx' is Microsoft Word 2007 Dcocument - so the Dolphin 'Show
previews for': https://imgur.com/ZZJOluJ

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

[plasmashell] [Bug 394236] logout confirmation dialog is unreadable with certain light backgrounds and some 3rd party themes

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|CONFIRMED   |RESOLVED

--- Comment #14 from Nate Graham  ---
Yeah, this is a theme issue. It's not appropriate to use such heavy
transparency for button backgrounds, since buttons need to be readable no
matter what they're placed over. Please report this issue to the maintainers of
the affected themes. Thanks!

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

[plasmashell] [Bug 394236] logout confirmation dialog is unreadable with certain light backgrounds and some 3rd party themes

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Keywords|regression  |
   Severity|normal  |minor

--- Comment #13 from Nate Graham  ---
Thanks. I'm tempted to mark this as RESOLVED DOWNSTREAM since it's caused by
3rd-party themes using transparency in a somewhat inappropriate manner...

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

[kdeconnect] [Bug 389904] boot loop caused by AAPT2 + CM libandroidfw.so (android::AssetManager::getBasePackageName)

[bugzilla_noreply]

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

villene...@arcor.de changed:

   What|Removed |Added

 CC||villene...@arcor.de

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

[kwin] [Bug 386304] [Wayland] Several task switchers are not centered on screen

[Nate Graham]

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

--- Comment #13 from Nate Graham  ---
If you fix this, I'll be really close to being able to make the switch to
Wayland full time! :)

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

[clazy] [Bug 394237] IDE-friendly URLs to documentation pages of checks

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |smart...@kde.org

--- Comment #3 from Sergio Martins  ---
I'll just move the READMEs into a docs folder.
make install will still put them in level0, 1, 2 folders, so it's fine

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

[clazy] [Bug 394237] IDE-friendly URLs to documentation pages of checks

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[frameworks-solid] [Bug 394293] Option to disable an action

[Josef Kufner]

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

--- Comment #1 from Josef Kufner  ---
Implementation details: The override can be created simply by a desktop file in
~/.local/share/solid/actions like this:

$ cat ~/.local/share/solid/actions/digikam-opencamera.desktop
[Desktop Entry]
X-KDE-Solid-Predicate=[ false ]
Type=Service
Actions=open;

However, disabling a user-specific action this way will cause loss of the
predicate. So it would be much better to introduce a bollean option
X-KDE-Solid-Enabled (or something like that).

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

[frameworks-solid] [Bug 394293] New: Option to disable an action

[Josef Kufner]

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

Bug ID: 394293
   Summary: Option to disable an action
   Product: frameworks-solid
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: lu...@kde.org
  Reporter: j...@frozen-doe.net
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I have a script to download photos from a SD card and I defined an action on
removable storage device, so I can execute it from a "device connected"
notification. However, there are another two actions in the menu which have
almost the same label as my script and I don't like them. How can I remove
them?

As described in the documentation
(https://docs.kde.org/stable5/en/kde-workspace/kcontrol/solid-actions/index.html),
the system-provided actions cannot be delited. That makes sense. But I really
mis an option to disable them.

Feature request: Please add "Disable"/"Enable" button next to "Add" and
"Remove" buttons. It should create a user-specific override which would disable
the system-provided action.

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

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
No, the image ids do not change. Presumably, many orphaned will no longer exist
after the migration. The database will certainly be smaller, but nothing should
be lost.

Maik

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

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[Kusi]

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

--- Comment #2 from Kusi  ---
my db is over 12 years old I guess. Looking at the mysql dump, there's indeed
alot of garbage (many unneeded constraints and indexes) compared to how a new
db looks like. Digikam with db v9 is now running, but I'll probably do the
migration to a new db anyways. 

Just one question: do the ids for the images change during migration? I've
added another table (for another project) whos foreign key is images.id.
Therefore I currently rely on Images.id not being changed

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

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

[Raúl]

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

Raúl  changed:

   What|Removed |Added

 CC||rasas...@gmail.com

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

[krdc] [Bug 394221] KRDC Remove Bookmark folder

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |DOWNSTREAM

--- Comment #4 from Luigi Toscano  ---
More a packaging problem: the krdc package should at least "Suggest" the 
keditbookmarks package). You may want to report this to your distribution.

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

[krdc] [Bug 394221] KRDC Remove Bookmark folder

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Luigi Toscano  ---
Good to hear

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

[kolourpaint] [Bug 394292] New: Erro on close application

[Ricardo Gavira]

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

Bug ID: 394292
   Summary: Erro on close application
   Product: kolourpaint
   Version: 17.08.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kolourpaint-supp...@lists.sourceforge.net
  Reporter: ricgav...@gmail.com
  Target Milestone: ---

Created attachment 112675
  --> https://bugs.kde.org/attachment.cgi?id=112675=edit
kolourpaint report

Error on close application. See attachment report

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

[kwin] [Bug 388127] Kwin crashes when switching desktops

[Mike Lui]

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

Mike Lui  changed:

   What|Removed |Added

 CC||mike.d@gmail.com

--- Comment #9 from Mike Lui  ---
I've noticed this happening in KDE 5.12.5, KDE Frameworks 5.46 (ArchLinux)

To clarify, this is a Qt issue and we must wait for a fix in Qt?

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

[ksudoku] [Bug 319522] Option to restart current game

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

 CC||codestr...@posteo.org

--- Comment #2 from Gregor Mi  ---
It is being work on that here: https://phabricator.kde.org/D12907

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

[krdc] [Bug 394221] KRDC Remove Bookmark folder

[SirSean]

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

--- Comment #2 from SirSean  ---
That worked. Thank you so much!

On Tue, May 15, 2018, 3:20 PM Luigi Toscano 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=394221
>
> Luigi Toscano  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |WAITINGFORINFO
>  CC||luigi.tosc...@tiscali.it
>  Status|UNCONFIRMED |NEEDSINFO
>
> --- Comment #1 from Luigi Toscano  ---
> You should have an "Edit Bookmarks" entry (the 4th in the Bookmarks menu).
> If
> you don't have it, it may be easily fixed by installing keditbookmarks.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[KBibTeX] [Bug 394228] kbibtex sets parenthesis in wrong order

[Thomas Fischer]

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

Thomas Fischer  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Thomas Fischer  ---
(In reply to manuel fernández from comment #0)
> Application: kbibtex (Git revision unknown)
> 
> Qt Version: 5.9.5
> Frameworks Version: 5.44.0
> Operating System: Linux 4.15.0-20-generic x86_64
> Distribution: Ubuntu 18.04 LTS
> 
> -- Information about the crash:
> - What I was doing when the application crashed:
> kbibtex entered wrongly "{title"} instead of "{title}". [This is a bug that
> should be corrected, it happens consistently]
> I corrected in kile. Then bibtex asked for reload and crashed

About the issue of "{title"}, this is most likely a duplicate of bug 388892.
Please check if the fix provided there solves your problem.

About the crash: Unfortunately, the provided backtraces do not contain
sufficient information to pinpoint the location in code where it happens.
You do not specify which KBibTeX version you are using. Have you tried a recent
Git master version or KBibTeX 0.8-beta1 (0.7.90) or later?

> Thread 1 (Thread 0x7f2978f94c80 (LWP 11889)):
> [KCrash Handler]
> #6  0x7f2976f079f0 in  () at
> /usr/lib/x86_64-linux-gnu/libkbibtexdata.so.0.8
> #7  0x7f2976f05ca0 in File::hasProperty(QString const&) const () at
> /usr/lib/x86_64-linux-gnu/libkbibtexdata.so.0.8
> #8  0x7f29789530f1 in FileSettingsWidget::loadProperties(File*) () at
> /usr/lib/x86_64-linux-gnu/libkbibtexgui.so.0.8
> #9  0x7f2973f726cf in QMetaObject::activate(QObject*, int, int, void**)
> () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #10 0x5605b89037b1 in  ()
> #11 0x7f2973f726cf in QMetaObject::activate(QObject*, int, int, void**)
> () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

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

[KBibTeX] [Bug 388892] Formatting error when saving file ( switching " and } )

[Thomas Fischer]

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

--- Comment #14 from Thomas Fischer  ---
I have also force-pushed an update to the bug branch to rebase it on 'master'.
The patch itself is unchanged.

https://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/c0dec5c5f26ab17fac219f9c749ef3f1f7f28d22

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

[digikam] [Bug 394214] Import .mp4 files does not preserve file mtime as date stamp

[Jens]

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

--- Comment #13 from Jens  ---
The issue I had was about using the file mtime as the "digikam date" (= the
date that is displayed below the thumbnails). You can write a new date to
almost everywhere (EXIF, XMP, IPTC, ...) but not to the Digikam DB. Right?

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

[krusader] [Bug 350654] Krusader cannot send a file over FTP without ".part" extention

[Davide Gianforte]

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

Davide Gianforte  changed:

   What|Removed |Added

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

--- Comment #8 from Davide Gianforte  ---
Resolved with the KF5 port (since 2.5.0)

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

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Your database is probably very old. I can not reproduce at what time the "name"
column in the "Images" table was a BLOB/TEXT field. Log into the database with
mysql and do this:

UPDATE Settings SET value=9 WHERE keyword='DBVersion';

Create a new digiKam database. Then start digiKam and use the migration tool to
export the old current database to the new.

Maik

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

[krdc] [Bug 394221] KRDC Remove Bookmark folder

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||luigi.tosc...@tiscali.it
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Luigi Toscano  ---
You should have an "Edit Bookmarks" entry (the 4th in the Bookmarks menu). If
you don't have it, it may be easily fixed by installing keditbookmarks.

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

[KBibTeX] [Bug 388892] Formatting error when saving file ( switching " and } )

[Thomas Fischer]

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

--- Comment #13 from Thomas Fischer  ---
I have two questions to follow up your problem:

1. When you *compile* this bug fix branch of KBibTeX, do you see an output like
this? Which values do you see?

Git revision is X
Git branch is XX

2. Once you have set all environment variables and run kbuildsyscoca5, what is
the output of running:

ldd ~/opt/kbibtex/bin/kbibtex

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

[dolphin] [Bug 369141] svn commands fail in path containing spaces

[Frank Fischer]

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

Frank Fischer  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Frank Fischer  ---
No, it seems to work now. Thanks a lot.

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

[digikam] [Bug 394291] New: cannot upgrade mysql db from v7 to v9

[Kusi]

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

Bug ID: 394291
   Summary: cannot upgrade mysql db from v7 to v9
   Product: digikam
   Version: 5.9.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Database-Mysql
  Assignee: digikam-bugs-n...@kde.org
  Reporter: k...@forum.titlis.org
  Target Milestone: ---

When I run Digikam 5.9 the first time, the mysql db is upgraded to v9. The
upgrade failed with the error message:

Error messages: "QMYSQL: Unable to execute query" "BLOB/TEXT column 'name' used
in key specification without a key length" 1170 2 
Bound values:  ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV9" ]
Statement [ "ALTER TABLE Images MODIFY COLUMN name LONGTEXT CHARACTER SET utf8
COLLATE utf8_general_ci NOT NULL;" ]
digikam.coredb: Core database: schema update to V 9 failed!

Deleting the guilty index solved the issue for me
ALTER TABLE Images DROP INDEX image_name_index;

Is that a problem in general or where does my index coming from? Do I need to
recreate it manually?

PS: I still cannot convert to v9, but these are other issues, to be
investigated

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

[plasma-nm] [Bug 392351] The networkmanagement kcm should support an UUID arg

[Frank Kruger]

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

--- Comment #3 from Frank Kruger  ---
(In reply to Jacky Alcine from comment #1)
> (In reply to Fabian Vogt from comment #0)
> > It's useful to open the connection editor for a selected connection.
> > 
> > KCMs support passing arguments, it just needs to be wired up properly.
> 
> For clarity; you'd want to open and edit a connection's settings from the
> plasma drop down?

Is there any news regarding the above issue?

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

[ark] [Bug 394145] Ark can't open some ZIP Files

[Elvis Angelaccio]

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

--- Comment #3 from Elvis Angelaccio  ---
Did you try to reproduce the bug after starting ark?

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

[dolphin] [Bug 394284] Entering a folder with a password-protected .docx file prompts user for password

[bugzilla_noreply]

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

--- Comment #3 from chansol...@gmail.com ---
Created attachment 112673
  --> https://bugs.kde.org/attachment.cgi?id=112673=edit
A password-protected .docx file that causes the bug.

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

[dolphin] [Bug 394284] Entering a folder with a password-protected .docx file prompts user for password

[bugzilla_noreply]

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

--- Comment #2 from chansol...@gmail.com ---
(In reply to Julian Schraner from comment #1)
> Hmm, I cannot reproduce this behavior. I do also run KDE Neon User Edition
> 5.12.5 with Dolphin 18.04.1, but for me the password dialog only pops up
> when I try to open the file (which is the expected behavior). Maybe you
> could upload a document that triggers the bug for you just to rule out the
> possibility that I did not create the .docx file the same way you did?
> Thanks for reporting this bug & have a nice day :)


After reading your reply, I experimented around a bit more...
And it looks like Calligra Suite is somehow related to this behavior.

The bug disappears after running [apt remove calligra --autoremove] and
reappears after running [apt install calligra].

So yeah, I think installing calligra may help you reproduce the bug.


...and just in case the bug still can't be reproduced, I'll add an attachment
of a .docx file that cause the bug on my system.

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

[dolphin] [Bug 368684] Dolphin copies symbolic link instead of referenced file

[Freddy Rietdijk]

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

--- Comment #2 from Freddy Rietdijk  ---
As I stated I found it confusing. Because it's been like this for a long time
as well I don't think it should be changed any more. But, it would be good to
have a way to copy the dereferenced link. In general better support for
symbolic links in the UI would ben nice.

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

[Discover] [Bug 385754] [Flatpak] The number of updates available shown by Discover and its tray icon don't match

[bugzilla_noreply]

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

p...@free.fr changed:

   What|Removed |Added

 CC||p...@free.fr

--- Comment #20 from p...@free.fr ---
affects 5.12.4 on kubuntu 18.04

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

[krita] [Bug 394289] Closes application shortly after opening.

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #2 from Boudewijn Rempt  ---
Setting to needsinfo.

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