[keditbookmarks] [Bug 372206] The split keditbookmarks repo doesn't contain a COPYING/LICENSE file

[David Faure]

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

--- Comment #2 from David Faure  ---
Sure, make it all consistent.

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

[kde] [Bug 372328] New: baloo

[AlexURS]

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

Bug ID: 372328
   Summary: baloo
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: iskender...@gmail.com
  Target Milestone: ---

Application: baloo_file (5.21.0)

Qt Version: 5.5.1
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
after restart system and start this
я просто перезагружаю систему и это появляется

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5b695c5780 (LWP 2149))]

Thread 2 (Thread 0x7f5a1e5c5700 (LWP 2436)):
#0  0x7f5b670e1bfd in poll () at /lib64/libc.so.6
#1  0x7f5b63b22e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5b63b22f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5b67d0fd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5b67cb6d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x0041531b in  ()
#6  0x7f5b67ada382 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f5b67add32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5b6611e0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f5b670ea02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f5b695c5780 (LWP 2149)):
[KCrash Handler]
#6  0x7f5b64e0e25c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so
#7  0x7f5b683ab4cd in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8  0x7f5b683a8dc0 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x7f5b683ba949 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x0041d453 in  ()
#11 0x0041d50d in  ()
#12 0x7f5b67ce873f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x00427145 in  ()
#14 0x0041b6f6 in  ()
#15 0x7f5b67ce873f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x7f5b67cf5f22 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x7f5b67ce98bc in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7f5b67cb918d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x7f5b67cb8e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x7f5b67d0f77d in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#21 0x7f5b67d0fad9 in  () at /usr/lib64/libQt5Core.so.5
#22 0x7f5b63b22c84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x7f5b63b22ed8 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x7f5b63b22f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x7f5b67d0fd6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#26 0x7f5b67cb6d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#27 0x7f5b67cbe8f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#28 0x0040a832 in  ()
#29 0x7f5b67026b25 in __libc_start_main () at /lib64/libc.so.6
#30 0x0040a9a8 in _start ()

Possible duplicates by query: bug 359672, bug 355210.

Reported using DrKonqi

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

[krita] [Bug 372327] New: Snapping cannot be turned off using Guides

[bugzilla_noreply]

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

Bug ID: 372327
   Summary: Snapping cannot be turned off using Guides
   Product: krita
   Version: 3.0.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: skinnune...@gmail.com
  Target Milestone: ---

Created attachment 102165
  --> https://bugs.kde.org/attachment.cgi?id=102165=edit
Snapping cannot be turned off using Guides

I have drawn guides. In the Guides- panel snapping is turned off. Yet it snaps
to guides. The only way to disable snapping is to turn off the guides. I have
disabled all snapping options from Shift+S options.

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

[digikam] [Bug 372326] New: digiKam crashed when closing it

[Dennis Schridde]

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

Bug ID: 372326
   Summary: digiKam crashed when closing it
   Product: digikam
   Version: 5.3.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: devuran...@gmx.net
  Target Milestone: ---

Application: digikam (5.3.0)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-1-ARCH x86_64
Distribution: "Arch Linux"

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

I had started digiKam for the first time (but old data from an installation on
another computer might have been left in the ~/Pictures folder). Apart from a
quick inspection of the import/export menu, I did not use digiKam at all during
this run today. When I closed it again, I received the message that it had
crashed.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa51d8648c0 (LWP 11687))]

Thread 10 (Thread 0x7fa4497fa700 (LWP 12561)):
[KCrash Handler]
#6  0x7fa519a20f44 in QMutex::lock() () at /usr/lib/libQt5Core.so.5
#7  0x7fa51c08a71e in  () at /usr/lib/libdigikamcore.so.5.3.0
#8  0x7fa51c05dcd4 in Digikam::LoadSaveThread::run() () at
/usr/lib/libdigikamcore.so.5.3.0
#9  0x7fa51c0b615e in Digikam::DynamicThread::DynamicThreadPriv::run() ()
at /usr/lib/libdigikamcore.so.5.3.0
#10 0x7fa519a2601f in  () at /usr/lib/libQt5Core.so.5
#11 0x7fa519a29d78 in  () at /usr/lib/libQt5Core.so.5
#12 0x7fa5136a3454 in start_thread () at /usr/lib/libpthread.so.0
#13 0x7fa518d307df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fa48e7fa700 (LWP 12248)):
#0  0x7fa5136a910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa50c1eb5f3 in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fa50c523911 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fa5136a3454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa518d307df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fa48effb700 (LWP 12247)):
#0  0x7fa5136a910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa50c1eb5f3 in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fa50c523911 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fa5136a3454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa518d307df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fa48f7fc700 (LWP 12246)):
#0  0x7fa5136a910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa50c1eb5f3 in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fa50c523911 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fa5136a3454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa518d307df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fa48fffd700 (LWP 12245)):
#0  0x7fa5136a910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa50c1ea4a1 in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fa50c523911 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fa5136a3454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa518d307df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fa4d650d700 (LWP 12227)):
#0  0x7fa5136a910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa50c4f277b in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fa50c4f27b9 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fa5136a3454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa518d307df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fa4de12a700 (LWP 1)):
#0  0x7fa5136a910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa519a2ac2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fa51c0b4b14 in  () at /usr/lib/libdigikamcore.so.5.3.0
#3  0x7fa519a29d78 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fa5136a3454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fa518d307df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fa4e5cb4700 (LWP 11689)):
#0  0x7ffc7e19e930 in  ()
#1  0x7ffc7e19ebc5 in clock_gettime ()
#2  0x7fa518d3d6b6 in clock_gettime () at /usr/lib/libc.so.6
#3  0x7fa519acf1a1 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fa519c563a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#5  0x7fa519c56955 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#6  0x7fa519c57cfe in  () at /usr/lib/libQt5Core.so.5
#7  0x7fa50d1f6c89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#8  0x7fa50d1f76ab in  () at /usr/lib/libglib-2.0.so.0
#9  0x7fa50d1f789c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0

[kwin] [Bug 372325] New: KATE - Open File Selection Dialog

[Paul Adams]

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

Bug ID: 372325
   Summary: KATE - Open File Selection Dialog
   Product: kwin
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: paul.zrexx...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
Editing text file in KATE, running Konsole, requested another file to TAB BAR
Open option... crash occurred on dialog box opening

- Unusual behavior I noticed:

The crash can be reproduced sometimes.

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

Thread 5 (Thread 0x7f3b7998b700 (LWP 3185)):
#0  0x7f3ba0b2e751 in ppoll () at /lib64/libc.so.6
#1  0x7f3b9e202b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f3b9e204428 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f3b9e1b11ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f3b9dfdf8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f3b9897aa75 in  () at /usr/lib64/libQt5Qml.so.5
#6  0x7f3b9dfe4558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f3b99e49454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f3ba0b3739f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f3b6b3c1700 (LWP 3013)):
#0  0x7f3b99e4f10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3b9d16c834 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f3b9d16c879 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f3b99e49454 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3ba0b3739f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f3b7aa0d700 (LWP 3002)):
#0  0x7f3ba0b2e751 in ppoll () at /lib64/libc.so.6
#1  0x7f3b9e202b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f3b9e204428 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f3b9e1b11ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f3b9dfdf8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f3b9897aa75 in  () at /usr/lib64/libQt5Qml.so.5
#6  0x7f3b9dfe4558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f3b99e49454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f3ba0b3739f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f3b89c9d700 (LWP 2931)):
#0  0x7f3ba0b2e68d in poll () at /lib64/libc.so.6
#1  0x7f3b95624876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3b9562498c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3b9e20779b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3b9e1b11ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3b9dfdf8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3b97b533e5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f3b9dfe4558 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3b99e49454 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3ba0b3739f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f3ba11a2940 (LWP 2912)):
[KCrash Handler]
#6  0x7f3b98966130 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/usr/lib64/libQt5Qml.so.5
#7  0x7f3b98967095 in
QQmlBinding::update(QFlags) () at
/usr/lib64/libQt5Qml.so.5
#8  0x7f3b98970d35 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f3b988fa5fe in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5
#10 0x7f3b988fa6c7 in QQmlComponentPrivate::completeCreate() () at
/usr/lib64/libQt5Qml.so.5
#11 0x7f3b988fa530 in QQmlComponent::create(QQmlContext*) () at
/usr/lib64/libQt5Qml.so.5
#12 0x7f3b7aa2d4b7 in  () at
/usr/lib64/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so
#13 0x7f3ba0756ed9 in  () at /usr/lib64/libkwin.so.5
#14 0x7f3ba0637572 in KWin::Client::createDecoration(QRect const&) () at
/usr/lib64/libkwin.so.5
#15 0x7f3ba063815d in KWin::Client::updateDecoration(bool, bool) () at
/usr/lib64/libkwin.so.5
#16 0x7f3ba0697175 in KWin::Client::manage(unsigned int, bool) () at
/usr/lib64/libkwin.so.5
#17 0x7f3ba061aa84 in KWin::Workspace::createClient(unsigned int, bool) ()
at /usr/lib64/libkwin.so.5
#18 0x7f3ba0684387 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
() at /usr/lib64/libkwin.so.5
#19 

[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin  ---
which mesa version are you using?

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

[kwin] [Bug 372324] virt-manager reopen when I add a device

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- 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||jalal...@yahoo.com

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

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

[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps

[Martin Gräßlin]

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

--- Comment #15 from Martin Gräßlin  ---
On X11 I don't see a possibility. The complete feature is built up on bypassing
keyboard grabs. AFAIK we cannot get a notification if another window grabs the
keyboard.

On Wayland we will have more control, though there is no support for
applications grabbing the keyboard at all.

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

[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

Summary|kwin crash after|Crash in
   |disconnecting external  |ContrastEffect::uploadRegio
   |monitor (including  |n
   |resolution change)  |

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

[kwin] [Bug 372305] kwin crash after disconnecting external monitor (including resolution change)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|general |effects-various

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

[kwin] [Bug 372304] kwin_x11 crashes frequently on me when opening a window/application (Intel Skylake Graphics)

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is lacking debug symbols, due to that we don't see
why and where it crashes.

As you mention Plastik: please try using breeze. We have seen lots of crashes
with the Aurorae based decoration unfortunately.

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

[plasmashell] [Bug 372296] "Keep window thumbnails" set to "Always" doesn't work with shaded windows.

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|glx |Task Manager
Product|kwin|plasmashell
   Target Milestone|--- |1.0
   Assignee|kwin-bugs-n...@kde.org  |h...@kde.org
 CC||plasma-b...@kde.org

--- Comment #1 from Martin Gräßlin  ---
Window thumbnails are done by Plasma and not by KWin. Given that reassigning to
Plasma.

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

[plasmashell] [Bug 372204] Crashing on reboot after package update

[bugzilla_noreply]

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

ig...@encompasscorporation.com changed:

   What|Removed |Added

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

--- Comment #2 from ig...@encompasscorporation.com ---
This is NOT same as the pointed bug. First of all this is on Ubuntu-16.04
Xenial which is not the same as the ubuntu release from the other bug.

Downgrading the nvidia driver did not solve anything. Still have the same
problem with 304 driver as well.

Apart from downgrading the driver I also reinstalled the kde* and kde plasma
packages and still same issue.

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

[kwin] [Bug 372324] New: virt-manager reopen when I add a device

[Jalal Ahmed]

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

Bug ID: 372324
   Summary: virt-manager reopen when I add a device
   Product: kwin
   Version: 5.8.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jalal...@yahoo.com
  Target Milestone: ---

Application: kwin_x11 (5.8.2)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
I am using KDE on Fedora 25, today, I was using virt-manager, it works fine,
but when I try to add any more hardware to the exist virtual machine, after I
click apply it reopen or rerun the app and all windows related to it.

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 0x7f37d5760940 (LWP 2543))]

Thread 6 (Thread 0x7f37accae700 (LWP 2573)):
#0  0x7f37e8922460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f37ee168bd4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7f37ee168c19 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7f37e891c6ca in start_thread () from /lib64/libpthread.so.0
#4  0x7f37e5afaf6f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f37b00a5700 (LWP 2570)):
#0  0x7f37e68f25e3 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#1  0x7f37e68a60ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#2  0x7f37e6703643 in QThread::exec() () from /lib64/libQt5Core.so.5
#3  0x7f37ed3c0735 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#4  0x7f37e6707a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7f37e891c6ca in start_thread () from /lib64/libpthread.so.0
#6  0x7f37e5afaf6f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f37c5fc4700 (LWP 2568)):
#0  0x7f37e5b08f0f in __libc_enable_asynccancel () from /lib64/libc.so.6
#1  0x7f37e5aef0b3 in ppoll () from /lib64/libc.so.6
#2  0x7f37e68f1051 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib64/libQt5Core.so.5
#3  0x7f37e68f2566 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f37e68a60ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f37e6703643 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f37ed3c0735 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7f37e6707a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f37e891c6ca in start_thread () from /lib64/libpthread.so.0
#9  0x7f37e5afaf6f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f37c7fff700 (LWP 2566)):
#0  0x7f37e5aef0d1 in ppoll () from /lib64/libc.so.6
#1  0x7f37e68f1051 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib64/libQt5Core.so.5
#2  0x7f37e68f2566 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7f37e68a60ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7f37e6703643 in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7f37e84187a9 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#6  0x7f37e6707a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f37e891c6ca in start_thread () from /lib64/libpthread.so.0
#8  0x7f37e5afaf6f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f37cde1f700 (LWP 2565)):
#0  0x7f37e5aef00d in poll () from /lib64/libc.so.6
#1  0x7f37e81e6d10 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7f37e81e8aa9 in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7f37ceacfa19 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7f37e6707a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7f37e891c6ca in start_thread () from /lib64/libpthread.so.0
#6  0x7f37e5afaf6f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f37d5760940 (LWP 2543)):
[KCrash Handler]
#6  0x0004 in ?? ()
#7  0x7f37e68d4178 in QObject::connect(QObject const*, char const*, QObject
const*, char const*, Qt::ConnectionType) () from /lib64/libQt5Core.so.5
#8  0x7f37ee1ab5af in QScriptEnginePrivate::qobjectData(QObject*) () from
/lib64/libQt5Script.so.5
#9  0x7f37ee1ab674 in QScriptEnginePrivate::newQObject(QObject*,
QScriptEngine::ValueOwnership, QFlags const&)
() from /lib64/libQt5Script.so.5
#10 0x7f37ee1ab962 in QScriptEngine::newQObject(QObject*,
QScriptEngine::ValueOwnership, QFlags const&)
() from 

[digikam] [Bug 372323] New: Camera autodetection fails when using AppImage bundle

[Leonard]

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

Bug ID: 372323
   Summary: Camera autodetection fails when using AppImage bundle
   Product: digikam
   Version: 5.3.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Import
  Assignee: digikam-de...@kde.org
  Reporter: leon...@lausen.nl
  Target Milestone: ---

Dear all,

I am using Maui Linux (which is based on Neon). When starting digiKam 5.3 from
the AppImage bundle it is not able to detect my camera. However, when compiling
the version 5.3 from source, the autodetection works fine.

I assume that this is due to some mismatch between the versions of the
dependencies with which the AppImage bundle is built compared to the versions
provided in Maui Linux.

Can we do anything to fix this issue?

I can only see the following issue on the command line:
> digikam.import: Failed to autodetect camera!
> digikam.import: Libgphoto2 error:  No error  ( 0 )

Best regards
Leonard

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

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

[bugzilla_noreply]

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

--- Comment #12 from red...@cox.net ---
Okay, looks I need to continue to try and reproduce the original issue.

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

[kdenlive] [Bug 372322] New: KServiceTypeTrader: serviceType "ThumbCreator" not found

[Mohammed]

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

Bug ID: 372322
   Summary: KServiceTypeTrader: serviceType "ThumbCreator" not
found
   Product: kdenlive
   Version: 16.08.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: alisumer2...@gmail.com
  Target Milestone: ---

Created attachment 102164
  --> https://bugs.kde.org/attachment.cgi?id=102164=edit
KServiceTypeTrader: serviceType "ThumbCreator" not found

When i Add an effect such crop scale  or Alpha shape I get that bug as I
wathed in terminal

KServiceTypeTrader: serviceType "ThumbCreator" not found

Can you help me?

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

[plasmashell] [Bug 372321] New: Plasma crashes when switching source of one monitor in dual head

[Curtis Seizert]

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

Bug ID: 372321
   Summary: Plasma crashes when switching source of one monitor in
dual head
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: cseiz...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

Whenever I switch the source of one monitor (dual head configuration), plasma
crashes when I switch back.  This pushes all windows to the monitor not
switched and erases the desktop of the monitor that was switched.

The crash can be reproduced every time.

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

Thread 15 (Thread 0x7f7cb1213700 (LWP 7123)):
#0  0x7f7dc151810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7dc2403c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7dc636f395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f7dc636fc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f7dc2402d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f7dc1512454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f7dc1d187df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f7cb1cbb700 (LWP 6360)):
#0  0x7f7dc151810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7dc2403c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7dc636f395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f7dc636fc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f7dc2402d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f7dc1512454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f7dc1d187df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f7cb24bc700 (LWP 6359)):
#0  0x7f7dc151810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7dc2403c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7dc636f395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f7dc636fc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f7dc2402d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f7dc1512454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f7dc1d187df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f7cb2cbd700 (LWP 6349)):
#0  0x7f7dc151810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7dc2403c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7dc636f395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f7dc636fc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f7dc2402d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f7dc1512454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f7dc1d187df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f7cb34be700 (LWP 6348)):
#0  0x7f7dc151810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7dc2403c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7dc636f395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f7dc636fc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f7dc2402d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f7dc1512454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f7dc1d187df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f7ce5171700 (LWP 6304)):
#0  0x7f7dc151810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7dc2403c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7dc636f395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f7dc636fc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f7dc2402d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f7dc1512454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f7dc1d187df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f7cec806700 (LWP 6303)):
#0  0x7f7dbcfe15d0 in g_poll () at /usr/lib/libglib-2.0.so.0
#1  0x7f7dbcfd1786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f7dbcfd189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f7dc263172b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f7dc25db23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  

[partitionmanager] [Bug 372320] New: Unusable 1MB partition created when making a new partition table with Mint18 Sarah on notebook disk.

[Lee Berry]

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

Bug ID: 372320
   Summary: Unusable 1MB partition created when making a new
partition table with Mint18 Sarah on notebook disk.
   Product: partitionmanager
   Version: unspecified
  Platform: Mint (Debian based)
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: berry.whiteti...@gmail.com
  Target Milestone: ---

Created attachment 102163
  --> https://bugs.kde.org/attachment.cgi?id=102163=edit
Mint18 Sarah install fails on /sda config manager creates unusable 1MB on front
of the disk.

KDE Partition Manager(1.2.1) Mint18-Sarah clears the partition table then
creates an unusable 1MB. Partition on the front of /sda notebook SATA-disk. 

Reproducible: Always several attempts to make a bootable disk failed.

Steps to Reproduce:
1. Use KDE Partition Manager to create a new MBR and then create a /boot node
of 100MB & a /root node of 30gb with 2k-swap space with Sarah installer.
2. use gdisk to unmount all disk except USB-Sarah.
disk.
3. Create a new partition, or edit the disk with KDE Partition Manager to
create a bootdisk.
4. Verify with gdisk that the MBR is changed.

Actual Results:  
The new partition table is created.

Expected Results:  
Allows the user to setup any partition size for the linux /boot disk.

This bug makes the computer unbootable. My experience is that the new "KDE
Partition Manager" is buggy with Frameworks 5.23.0. Perhaps it's a new release
bug. It creates an unusable 1MB parition on the front of my disk when a new
partition table is created see my snapshot. Everything works fine with Kubuntu
15 using ver Frameworks 5.10.0 on KDE Partition manager version1.2.1. Look at
my photo closely. I did not manually create the 1MB partition. It was created
by the KDE partition manager (ver 1.2.1) Because the same version is used for
both kubuntu & mint18 I expect a change took place in the frameworks
(5.23.0-vers5.10.0) that broken the installer for grub1.99. I have not tried it
for grub2.0 since I have no tool for that.

Workaround:

Using Kubuntu15.2 (ver: 1.2.1 (frameworks 5.10.0) i was able to create a usable
partition on my internal SATA-disk. I reinstalled Kubuntu without any error.

PCI Information:

Yes hardware is old. I know.

lee@kbuntu15-Aspire-4349:~$ inxi -f
CPU:   Dual core Intel Celeron B815 (-MCP-) cache: 2048 KB 
   clock speeds: max: 1600 MHz 1: 799 MHz 2: 799 MHz

Linux versions used:
Kubuntu 15.1 kernel:3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:09:58 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux

Mint18 Sarah kernel: 4.4.0-21-generic #37-ubuntu SMP x86_64 GNU/linux

NO backtrace information available. This is not a crash report. After rebooting
user gets an error "No boot disk found"

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

[dolphin] [Bug 371837] Dolphin General option "Executing scripts or desktop files" cannot be unchecked

[Don Nguyen]

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

--- Comment #3 from Don Nguyen  ---
The reason why you can't simply uncheck the box is because you need to specify
the behavior you want if you don't want the confirmation.  When you click on a
script, you will get the text, "What do you wish to do with this executable
file?", and you have the option to "Open" or "Execute".  In that same dialog
there is an option "Do not ask again".  If you check that box, and choose
"Open" or "Execute", it will no longer ask for confirmation, and always perform
the action that you choose - either "Open" or "Execute".  This will also turn
off the "Executing scripts or desktop files" setting.  The problem is if that
setting is on, and you turn it off, we don't know what you want to do with the
script - "Open" or "Execute".  If you don't want to the confirmation, you'll
somehow have to specify if you want to "Open" or "Execute".  I'm not sure
what's the best way to fix this.  The setting really should be "Always Execute,
Always Open, or Always Ask".

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

[choqok] [Bug 360790] Error on launch: Unknown host api.longurl.org: Host not found

[Mehrdad Momeny]

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

Mehrdad Momeny  changed:

   What|Removed |Added

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

--- Comment #4 from Mehrdad Momeny  ---
This has been fixed by removing the LongURL plugin. The service is dead and
Choqok is no longer relying on it.

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

[dolphin] [Bug 371837] Dolphin General option "Executing scripts or desktop files" cannot be unchecked

[Don Nguyen]

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

Don Nguyen  changed:

   What|Removed |Added

 CC||don78color...@gmail.com

--- Comment #2 from Don Nguyen  ---
The problem is in  ConfirmationsSettingsPage::applySettings()
It is only saving the setting if the setting is checked, but not doing anything
if it's unchecked.  Unlike it's neighboring settings, it's not being saved as a
simple on/off so I don't know how to deal with it.  I need to look into how
this setting is being used and find an appropriate value to set when the
checkbox is off.

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

[Touchpad-KCM] [Bug 346210] Touchpad KCM always asks to save changes

[Roman]

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

--- Comment #9 from Roman  ---
Thanks for the quick response. Yea, I was in fact already about to fix the
second problem you now also encountered and wanted to ask before I did this if
there is even another catch I should consider.

But so it seems that both problems are gone now.

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

[kontact] [Bug 372319] New: Move an email to an event

[Eric]

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

Bug ID: 372319
   Summary: Move an email to an event
   Product: kontact
   Version: 5.2.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eric.v...@msg4.us
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Creating an event in my calendar based on an email I just received
- Custom settings of the application:
Many email accounts

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd14fc0c7c0 (LWP 3145))]

Thread 30 (Thread 0x7fd076791700 (LWP 12733)):
#0  0x7fff6aecdb26 in clock_gettime ()
#1  0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd14d20d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd14d38eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd1453ab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fd1453abd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fd1453abf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fd14d38ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fd14d335d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fd14d15c32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fd14c85302d in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7fd08b7fe700 (LWP 11234)):
#0  0x7fff6aecdb26 in clock_gettime ()
#1  0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd14d20d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd14d38eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd1453ab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fd1453abd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fd1453abf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fd14d38ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fd14d335d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fd14d15c32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fd14c85302d in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7fd08bfff700 (LWP 11229)):
#0  0x7fff6aecdb26 in clock_gettime ()
#1  0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd14d20d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd14d38eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd1453ab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fd1453abd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fd1453abf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fd14d38ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fd14d335d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fd14d15c32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fd14c85302d in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7fd091687700 (LWP 11227)):
#0  0x7fff6aecdb26 in clock_gettime ()
#1  0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd14d20d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd14d38eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd1453ab4ad in g_main_context_prepare () at

[plasmashell] [Bug 372318] New: when I gparted USB device(Kingston 64GB,USB3.0)

[songjingcn]

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

Bug ID: 372318
   Summary: when I gparted USB device(Kingston 64GB,USB3.0)
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: songjin...@gmail.com
  Target Milestone: 1.0

Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7fd365d9b0c7 in raise () at /lib64/libc.so.6
#7  0x7fd365d9c478 in abort () at /lib64/libc.so.6
#8  0x7fd36682c7ce in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fd367c44b92 in  () at /usr/lib64/libQt5DBus.so.5
#10 0x7fd366a5b794 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7fd366a5c77f in QVariant::QVariant(int, void const*) () at
/usr/lib64/libQt5Core.so.5
#12 0x7fd366a277a2 in QMetaProperty::read(QObject const*) const () at
/usr/lib64/libQt5Core.so.5
#13 0x7fd366a48c0c in QObject::property(char const*) const () at
/usr/lib64/libQt5Core.so.5
#14 0x7fd367ee9964 in  () at /usr/lib64/libKF5Solid.so.5
#15 0x7fd367ee9b43 in  () at /usr/lib64/libKF5Solid.so.5
#16 0x7fd367ee4551 in  () at /usr/lib64/libKF5Solid.so.5
#17 0x7fd367efa959 in  () at /usr/lib64/libKF5Solid.so.5
#18 0x7fd367ef7ea5 in  () at /usr/lib64/libKF5Solid.so.5
#19 0x7fd367ee24f0 in  () at /usr/lib64/libKF5Solid.so.5
#20 0x7fd367eb0800 in
Solid::Device::asDeviceInterface(Solid::DeviceInterface::Type const&) const ()
at /usr/lib64/libKF5Solid.so.5
#21 0x00417466 in  ()
#22 0x004176eb in  ()
#23 0x7fd366a4973f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#24 0x7fd367eb0d52 in Solid::DeviceNotifier::deviceAdded(QString const&) ()
at /usr/lib64/libKF5Solid.so.5
#25 0x7fd367eb1eb6 in  () at /usr/lib64/libKF5Solid.so.5
#26 0x7fd366a49cc6 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#27 0x7fd367f092a2 in  () at /usr/lib64/libKF5Solid.so.5
#28 0x7fd367eddef2 in  () at /usr/lib64/libKF5Solid.so.5
#29 0x7fd367f0f045 in  () at /usr/lib64/libKF5Solid.so.5
#30 0x7fd366a49cc6 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#31 0x7fd367f08477 in  () at /usr/lib64/libKF5Solid.so.5
#32 0x7fd367f0f34b in  () at /usr/lib64/libKF5Solid.so.5
#33 0x7fd367f14393 in  () at /usr/lib64/libKF5Solid.so.5
#34 0x7fd367c21da4 in  () at /usr/lib64/libQt5DBus.so.5
#35 0x7fd366a4aac6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#36 0x7fd366a1a18d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#37 0x7fd366a19e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#38 0x7fd366a1c057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#39 0x7fd366a718f3 in  () at /usr/lib64/libQt5Core.so.5
#40 0x7fd362883c84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#41 0x7fd362883ed8 in  () at /usr/lib64/libglib-2.0.so.0
#42 0x7fd362883f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#43 0x7fd366a70d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#44 0x7fd366a17d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#45 0x7fd366a1f8f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#46 0x0040a832 in  ()
#47 0x7fd365d87b25 in __libc_start_main () at /lib64/libc.so.6
#48 0x0040a9a8 in _start ()

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

[plasmashell] [Bug 372317] New: Crash upon re-enabling display in 4k

[Con Kolivas]

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

Bug ID: 372317
   Summary: Crash upon re-enabling display in 4k
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: k...@kolivas.org
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.8.6-cktest+ x86_64
Distribution: Ubuntu 16.04.1 LTS

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

I am running a 4k monitor which is seen as two screens. A wine application had
resized one screen only (mistakenly) while trying to go fullscreen. Upon
killing the wine application I used the kde display configuration to re-enable
the screen at its correct resolution. This caused the crash even though it did
resize and enable the screen.

-- Backtrace:
Application: Plasma (plasmashell), 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 0x7f9a4e18d8c0 (LWP 1140))]

Thread 13 (Thread 0x7f9975768700 (LWP 2797)):
[KCrash Handler]
#6  0x7f990005 in  ()
#7  0x7f9a497b8171 in QOpenGLShaderProgram::setUniformValue(int, float)
(v=0x7f997576788c, count=1, location=, this=) at
opengl/qopenglfunctions.h:1833
#8  0x7f9a497b8171 in QOpenGLShaderProgram::setUniformValue(int, float)
(this=, location=, value=value@entry=0) at
opengl/qopenglshaderprogram.cpp:1934
#9  0x7f9a1d4b9ff9 in Plotter::render() (this=0x3995560) at
../../../../src/qmlcontrols/kquickcontrolsaddons/plotter.cpp:659
#10 0x7f9a491abbaf in QMetaObject::activate(QObject*, int, int, void**)
(a=0x7f9975767b00, r=0x3995560, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#11 0x7f9a491abbaf in QMetaObject::activate(QObject*, int, int, void**)
(sender=0x163fe10, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3698
#12 0x7f9a4c262ece in QQuickWindowPrivate::renderSceneGraph(QSize const&)
() at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7f9a4c2369c8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x7f9a4c23c08c in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x7f9a48f9c7be in QThreadPrivate::start(void*) (arg=0x3c5c050) at
thread/qthread_unix.cpp:331
#16 0x7f9a4808970a in start_thread (arg=0x7f9975768700) at
pthread_create.c:333
#17 0x7f9a488b282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f998f7ff700 (LWP 2796)):
#0  0x7f9a4808f3b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9a48f9da5b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x1e31240) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f9a48f9da5b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x4905bd0, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f9a4c23b92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f9a4c23c1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f9a48f9c7be in QThreadPrivate::start(void*) (arg=0x4905b50) at
thread/qthread_unix.cpp:331
#6  0x7f9a4808970a in start_thread (arg=0x7f998f7ff700) at
pthread_create.c:333
#7  0x7f9a488b282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f995f1d3700 (LWP 1419)):
#0  0x7f9a4808f3b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9a48f9da5b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x2ff7de0) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f9a48f9da5b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x4711100, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:208
#3  0x7f9a4c23b92e in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f9a4c23c1b3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f9a48f9c7be in QThreadPrivate::start(void*) (arg=0x4711080) at
thread/qthread_unix.cpp:331
#6  0x7f9a4808970a in start_thread (arg=0x7f995f1d3700) at
pthread_create.c:333
#7  0x7f9a488b282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f997664a700 (LWP 1161)):
#0  0x7f9a4808f3b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9a48f9da5b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x2c58c90) at
thread/qwaitcondition_unix.cpp:136
#2  0x7f9a48f9da5b in 

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Paul Sommer]

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

--- Comment #28 from Paul Sommer  ---
When I unset "apply colors to non-qt applications"? everything is fine (white
characters on black background).
But Comments 10, 12 and 13 sounds as if it was working correct with the Oxygen
theme without that workaround. Did I get this wrong?

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

[KScreen] [Bug 371643] Kscreen display configuration is lost on reboot

[bugzilla_noreply]

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

--- Comment #6 from patrickrif...@yandex.com ---
(kscreen doctor output had incorrect formatting when echoed to a text file.
Here is the output copy and pasted from Konsole)

Output: 65 VGA-1 enabled connected primary VGA Modes: 71:1280x1024@60!
72:1280x1024@75* 73:1152x864@75 74:1024x768@75 75:1024x768@60 76:832x624@75
77:800x600@75 78:800x600@60 79:640x480@75 80:640x480@60 81:720x400@70 Geometry:
1280,0 1280x1024
Output: 66 HDMI-1 enabled connected  HDMI Modes: 71:1280x1024@60!
72:1280x1024@75* 73:1152x864@75 74:1024x768@75 75:1024x768@60 76:832x624@75
77:800x600@75 78:800x600@60 79:640x480@75 80:640x480@60 81:720x400@70
82:1280x960@60 83:1024x768@70 84:800x600@72 85:800x600@56 86:640x480@73
87:640x480@67 Geometry: 0,0 1280x1024
Output: 67 DP-1 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0
Output: 68 HDMI-2 disabled disconnected  HDMI Modes: Geometry: 0,0 0x0
Output: 69 DP-2 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0

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

[KScreen] [Bug 371643] Kscreen display configuration is lost on reboot

[bugzilla_noreply]

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

--- Comment #5 from patrickrif...@yandex.com ---
Apologies, I should have made myself more clear. Upon rebooting my system, the
following configuration values are lost:
- Primary screen selection (where main panel resides)
- Display orientation
- Primary display wallpaper

However, it appears that since I have installed KDE Applications 16.08.3 the
issue has been resolved. I have tested my system on multiple reboots and my
display configuration is persisting.

I will attach the kscreen-doctor output of my last reboot. However, this is of
a reboot where the issue has not occured. If I do get a reboot where I can
replicate the issue, I will post the kscreen-doctor output again.

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

[kdeplasma-addons] [Bug 372316] When I drop into the widget a pic for share in Imgur, there is not answer of the widget.

[Víctor]

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

Víctor  changed:

   What|Removed |Added

 CC||vmorenoma...@gmail.com

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

[kdeplasma-addons] [Bug 372316] New: When I drop into the widget a pic for share in Imgur, there is not answer of the widget.

[Víctor]

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

Bug ID: 372316
   Summary: When I drop into the widget a pic for share in Imgur,
there is not answer of the widget.
   Product: kdeplasma-addons
   Version: 5.8.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: QuickShare
  Assignee: aleix...@kde.org
  Reporter: vmorenoma...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

When I drop a pic for share in imgur, the widget only show a loading animation
and not displays the link, as should be.

Someones the widget works :/

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Raman Gupta]

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

--- Comment #17 from Raman Gupta  ---
Here is another report that seems related to the virtualization mentioned in
comment #4, this time with VMWare:

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

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

[plasmashell] [Bug 361497] High memory usage of plasma shell when vmvare workstation is running

[Raman Gupta]

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

Raman Gupta  changed:

   What|Removed |Added

 CC||rocketra...@gmail.com

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

[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process

[Raman Gupta]

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

Raman Gupta  changed:

   What|Removed |Added

 CC||rocketra...@gmail.com

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

[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps

[Thomas Pfeiffer]

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

--- Comment #14 from Thomas Pfeiffer  ---
If technically possible, modifier-only shortcuts should not bypass keyboard
grabbing.
I would not consider them as equal to the likes of Ctrl-Alt-Fx. Those are "one
level above" the desktop as they cen be used to switch away from it, whereas
Meta for opening the start menu is a desktop feature.
Also, from a purely practical perspective, we don't want for example gamers to
have to physically remove their meta key because they press it by accident all
the time while playing shooters.

If it is not possible to prevent the meta key from triggering the menu opening
even when an application grabs the keyboard on X11, however, I would not roll
back the whole feature, under the assumption that removing the feature will
have an impact on more people than not blocking it when the keyboard is
grabbed.
As long as it is possible for users to manually disable it, that should be
okay.

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

[Akonadi] [Bug 372315] New: Unable to compact /var/mail/ mbox file

[bugzilla_noreply]

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

Bug ID: 372315
   Summary: Unable to compact /var/mail/ mbox file
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: MBox Resource
  Assignee: kdepim-b...@kde.org
  Reporter: ptitpierrecalim...@free.fr
  Target Milestone: ---

When I try to compact manually my mbox file.
The akonadiconsole just said : AgentBase(akonadi_mbox_resource_0): Échec
d'enregistrement du fichier « mbox » dans /var/mail/myname

And the log doesn't provides many lights :
akonadi_mbox_resource_0 (0x563214a5c880) 197 { Response: "FetchCollections"
Error Code: "0" Error Msg: "" ID: "15" Name: "Pierre Téchoueyres" Parent ID:
"0" Remote ID: "file:///var/mail/ptechoueyres" Remote Revision: "" Resource:
"akonadi_mbox_resource_0" Mimetypes: "(message/rfc822)" Statistics: { Count:
"-1" Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()"
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on
Demand: "false" Local Parts: "(ALL)" } Ancestors: { } Attributes:
"QMap((AccessRights, wcdW)(DeletedMboxItems,
245777,1160081,166839,860321,568683,993300,513082,1301955,1104521,519917,0,931466,23211,1099378,816148,112294,766422,58533,1031471,802,213783,801204,1271239,206178,324150,835808,1091775,383329,1291425,1164782,142330,1281439)(ENTITYDISPLAY,
("Pierre Téchoueyres" "message-rfc822" "" (" Display: "Undefined" Sync:
"Undefined" Index: "Undefined" Enabled: "true" Virtual: "false" Referenced:
"false" }
akonadi_mbox_resource_0 (0x563214a5c880) 197 { Response: "FetchCollections"
Error Code: "0" Error Msg: "" ID: "-1" Name: "" Parent ID: "-1" Remote ID: ""
Remote Revision: "" Resource: "" Mimetypes: "()" Statistics: { Count: "-1"
Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()"
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on
Demand: "false" Local Parts: "()" } Ancestors: { } Attributes: "QMap()"
Display: "Undefined" Sync: "Undefined" Index: "Undefined" Enabled: "true"
Virtual: "false" Referenced: "false" }
akonadi_mbox_resource_0 (0x563214a5c880) 198 { Command: "FetchCollections"
Collections: "RID (file:///var/mail/ptechoueyres)" Depth: "0" Resource: ""
Mimetypes: "()" Ancestors Depth: "0" Ancestors Attributes: "QSet()" Enabled:
"true" Sync: "false" Display: "false" Index: "false" Status: "false" }
akonadi_mbox_resource_0 (0x563214a5c880) 198 { Response: "FetchCollections"
Error Code: "0" Error Msg: "" ID: "15" Name: "Pierre Téchoueyres" Parent ID:
"0" Remote ID: "file:///var/mail/ptechoueyres" Remote Revision: "" Resource:
"akonadi_mbox_resource_0" Mimetypes: "(message/rfc822)" Statistics: { Count:
"-1" Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()"
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on
Demand: "false" Local Parts: "(ALL)" } Ancestors: { } Attributes:
"QMap((AccessRights, wcdW)(DeletedMboxItems,
245777,1160081,166839,860321,568683,993300,513082,1301955,1104521,519917,0,931466,23211,1099378,816148,112294,766422,58533,1031471,802,213783,801204,1271239,206178,324150,835808,1091775,383329,1291425,1164782,142330,1281439)(ENTITYDISPLAY,
("Pierre Téchoueyres" "message-rfc822" "" (" Display: "Undefined" Sync:
"Undefined" Index: "Undefined" Enabled: "true" Virtual: "false" Referenced:
"false" }
akonadi_mbox_resource_0 (0x563214a5c880) 198 { Response: "FetchCollections"
Error Code: "0" Error Msg: "" ID: "-1" Name: "" Parent ID: "-1" Remote ID: ""
Remote Revision: "" Resource: "" Mimetypes: "()" Statistics: { Count: "-1"
Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()"
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on
Demand: "false" Local Parts: "()" } Ancestors: { } Attributes: "QMap()"
Display: "Undefined" Sync: "Undefined" Index: "Undefined" Enabled: "true"
Virtual: "false" Referenced: "false" }
akonadi_mbox_resource_0 (0x563214a5c880) 199 { Command: "FetchCollections"
Collections: "UID " Depth: "2" Resource: "akonadi_mbox_resource_0" Mimetypes:
"()" Ancestors Depth: "2" Ancestors Attributes: "QSet()" Enabled: "false" Sync:
"false" Display: "false" Index: "false" Status: "false" }
akonadi_mbox_resource_0 (0x563214a5c880) 199 { Response: "FetchCollections"
Error Code: "0" Error Msg: "" ID: "15" Name: "Pierre Téchoueyres" Parent ID:
"0" Remote ID: "file:///var/mail/ptechoueyres" Remote Revision: "" Resource:
"akonadi_mbox_resource_0" Mimetypes: "(message/rfc822)" Statistics: { Count:
"-1" Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()"
Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on
Demand: "false" Local Parts: "(ALL)" } Ancestors: { { ID: "0" Remote ID: ""
Name: "" Attributes: "QMap()" } } Attributes: "QMap((AccessRights,

[digikam] [Bug 372314] I cannot choose the template predefined in the import window while renaming (F2)

[bugzilla_noreply]

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

piotergmo...@hotmail.com changed:

   What|Removed |Added

Summary|I cannot choose the |I cannot choose the
   |template defined in the |template predefined in the
   |import window while |import window while
   |renaming (F2)   |renaming (F2)

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

[digikam] [Bug 372314] New: I cannot choose the template defined in the import window while renaming (F2)

[bugzilla_noreply]

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

Bug ID: 372314
   Summary: I cannot choose the template defined in the import
window while renaming (F2)
   Product: digikam
   Version: 5.2.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: AdvancedRename
  Assignee: digikam-de...@kde.org
  Reporter: piotergmo...@hotmail.com
  Target Milestone: ---

I have this template defined in the import window: 
[date:-MM-dd_hh.mm.ss]{lower}{unique}.[ext]{lower}

When I rename the file, I want to use the same template and digikam almost
helps me with this: I can see (in the drop down list  the name of a template
widget) my template but it is ghosted and I cannot choose it, so in the end I
have to copy paste the template from the import menu. Bug or not?
P.

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

[kdeplasma-addons] [Bug 357222] Crash Plasma while I put an object

[melkor333]

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

--- Comment #5 from melkor333  ---

I had this bug and created Bug 369172.

After some Updates on my Manjaro Linux, I tried to add the widget again and the
crash occured on a later step.
I could add the Comic strip to the desktop, but when I pressed 'configure' ->
'Get new comic...' it crashed.

I created a new Bug with drkonqi, which can be found here:

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

Could it be that both crashes are related to each other, or are these complete
seperate bugs?

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

[plasmashell] [Bug 372313] New: Comic Strip 'Add Comic' Button crashes plasmashell

[melkor333]

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

Bug ID: 372313
   Summary: Comic Strip 'Add Comic' Button crashes plasmashell
   Product: plasmashell
   Version: 5.8.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sam...@ton-kunst.ch
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.4.30-1-MANJARO x86_64
Distribution: "Manjaro Linux"

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

On my Manjaro Linux (based on Arch):

1. Drag the comic strip widget from the widgets-area to the Desktop
2. click on 'configure' in the widget area
3. click on "Get new comics..."
 -> Plasmashell crashes (and instantly restarts)


I already had a bug described in https://bugs.kde.org/show_bug.cgi?id=357222
(My Bug Report has been marked as duplicate, Bug 369172).
After updating (with the official Manjaro updates), i tried it and I was able
to do the above steps.
The former bug describes a Crash right after the first step.

The crash can be reproduced every time.

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

Thread 9 (Thread 0x7f1c9ca95700 (LWP 4097)):
#0  0x7f1d70bd948d in poll () at /usr/lib/libc.so.6
#1  0x7f1d6bea1786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1d6bea189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f1d714fb72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f1d714a523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f1d712c80f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f1d7462b2d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f1d712ccd78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f1d703dc454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f1d70be27df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f1ca9a5f700 (LWP 1468)):
#0  0x7f1d70bd54ed in read () at /usr/lib/libc.so.6
#1  0x7f1d6bee5a10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f1d6bea1235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f1d6bea1724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f1d6bea189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f1d714fb72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f1d714a523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f1d712c80f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f1cabf8b0a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#9  0x7f1d712ccd78 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f1d703dc454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f1d70be27df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f1cbe976700 (LWP 1439)):
#0  0x7f1d6bee6db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f1d6bea0c95 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f1d6bea16ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f1d6bea189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f1d714fb72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f1d714a523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f1d712c80f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f1d751ca856 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7f1d712ccd78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f1d703dc454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f1d70be27df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f1d4dbbf700 (LWP 1408)):
#0  0x7f1d703e210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1d76c5aac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f1d76c5ab09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f1d703dc454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f1d70be27df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f1d4f86c700 (LWP 1380)):
#0  0x7f1d6be9e74b in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f1d6bea0c2b in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f1d6bea16ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f1d6bea189c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f1d714fb72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f1d714a523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f1d712c80f3 in QThread::exec() () at 

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

[Kusi]

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

Bug ID: 372312
   Summary: database upgrade v7 to v8 failed
   Product: digikam
   Version: 5.2.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Database-Mysql
  Assignee: digikam-de...@kde.org
  Reporter: k...@forum.titlis.org
  Target Milestone: ---

I cannot update the database version v7 (DK 4.14) to v8 (DK 5.2). I'm using
Opensuse Leap 42.2 with mariadb 10.0.27


$ digikam 
digikam.general: AlbumWatch use QFileSystemWatcher
QFileSystemWatcher::removePaths: list is empty
digikam.general: Database Parameters:
   Type: "QMYSQL"
   DB Core Name: "digikamdb"
   DB Thumbs Name:   "digikamthumbs"
   DB Face Name: "digikamfaces"
   Connect Options:  ""
   Host Name:"localhost"
   Host port:3306
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: "digikamuser"
   Password: "X"

digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  7
digikam.coredb: Core database: makeUpdates  7  to  8
digikam.dbengine: Failure executing query:
 "" 
Error messages: "QMYSQL: Unable to execute query" "Specified key was too long;
max key length is 767 bytes" 1071 2 
Bound values:  ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV8" ]
Statement [ "ALTER TABLE Albums\nADD
CONSTRAINT Albums_AlbumRoots FOREIGN KEY (albumRoot) REFERENCES AlbumRoots (id)
ON DELETE CASCADE ON UPDATE CASCADE,\n   
ADD UNIQUE (albumRoot, relativePath(255)),\n   
ENGINE InnoDB;" ]
digikam.coredb: Core database: schema update to V 8 failed!
digikam.coredb: Core database: cannot process schema initialization

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

[extra-cmake-modules] [Bug 372311] clang detection in FindPythonModuleGeneration.cmake only works in Debian/Ubuntu

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||steve...@gmail.com

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

[extra-cmake-modules] [Bug 372311] New: clang detection in FindPythonModuleGeneration.cmake only works in Debian/Ubuntu

[Antonio Rojas]

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

Bug ID: 372311
   Summary: clang detection in FindPythonModuleGeneration.cmake
only works in Debian/Ubuntu
   Product: extra-cmake-modules
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alex.me...@kde.org
  Reporter: aro...@archlinux.org
CC: ecm-bugs-n...@kde.org
  Target Milestone: ---

The clang detection in FindPythonModuleGeneration.cmake assumes that the clang
library is called libclang-x.y.so. This is only true in Debian/ubuntu, all
other major distros install the library as libclang.so.x.y. So the clang
library location needs to be manually specified in these distros.

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

[krita] [Bug 372310] New: Stylus side button for panning

[bugzilla_noreply]

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

Bug ID: 372310
   Summary: Stylus side button for panning
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: mad_cy...@hotmail.com
  Target Milestone: ---

Created attachment 102162
  --> https://bugs.kde.org/attachment.cgi?id=102162=edit
Sai Option

Problem:
I have my side button set up in my wacom settings to be Spacebar.
I go to the Canvas Input Settings and then under Pan Canvas set it to pan by
holding spacebar and then left clicking. Then when I try to use my keyboard
spacebar and then using my stylus to press down and move it works as intended
and pans.
But then when I use my side button registered to do the same thing the pan hand
icon comes up but I can't actually pan.

I did some looking in Paint tool sai since it works there and it turns out
there is a menu for the pen buttons where you can disable the side buttons and
if you leave it as default there is the exact same problem.
It seems like there are multiple signals being sent or something similar so
maybe the solution would be to have an option disable one of them. I included a
screenshot of the option in Sai, maybe that helps explain it better.

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

[konsole] [Bug 372250] readline's history search on up/down arrow keys visually messes up the edit line

[Egmont Koblinger]

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

--- Comment #5 from Egmont Koblinger  ---
It's not a bug in bash and not a workaround. It's documented in bash's manual
that you have to use these characters.

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

[krita] [Bug 372310] Stylus side button for panning

[bugzilla_noreply]

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

mad_cy...@hotmail.com changed:

   What|Removed |Added

   Severity|minor   |wishlist

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

[krita] [Bug 372310] Stylus side button for panning

[bugzilla_noreply]

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

mad_cy...@hotmail.com changed:

   What|Removed |Added

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

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

[konsole] [Bug 372250] readline's history search on up/down arrow keys visually messes up the edit line

[Diggory Hardy]

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

Diggory Hardy  changed:

   What|Removed |Added

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

--- Comment #4 from Diggory Hardy  ---
Yes, you're right. It's a bash bug really, and that's a sufficient workaround.

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

[systemsettings] [Bug 372309] New: Appearance -> Colors -> Edit Scheme (dialog breakup on vertical expand)

[David Rankin]

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

Bug ID: 372309
   Summary: Appearance -> Colors -> Edit Scheme (dialog breakup on
vertical expand)
   Product: systemsettings
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_colors
  Assignee: mwoehlke.fl...@gmail.com
  Reporter: drankina...@suddenlinkmail.com
CC: jpwhit...@kde.org
  Target Milestone: ---

Created attachment 102161
  --> https://bugs.kde.org/attachment.cgi?id=102161=edit
Snapshot showing 'Edit scheme' dialog breaking apart exposing blank dialog.

Version 5.8.3

When expanding the Appearance -> Colors -> Edit Scheme dialog vertically, the
dialog does not properly expand the 'Color set:' portion to maximize editing
the color scheme list of colors. Instead the 'Window text' widget and the
'Color set:' widgets separate and break apart wasting 1/3 to 1/2 of the 900px
screen with completely wasted space.

When maximizing the dialog vertically, the 'Color set:' widget should be the
only widget that expands maximizing the space available for editing the
color-scheme instead of just expanding the blank window behind the widgets.

Screenshot included:

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

[kmymoney4] [Bug 372254] Crash when importing CSV file

[allan]

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

--- Comment #3 from allan  ---
Totally unconnected, but I previously reported that I'd noticed the following -

"QObject::connect: No such signal
FormatsPage::statementReady(MyMoneyStatement&)
QObject::connect:  (sender name:   'FormatsPage')
QObject::connect:  (receiver name: 'csvimport')
KMyMoneyPlugin::KMMStatementInterface::import start
Updating account in MyMoneyStatementReader::startImport failed
Importing statement for ''
Importing statement for '' done
QObject::connect: No such signal
FormatsPage::statementReady(MyMoneyStatement&)
QObject::connect:  (sender name:   'FormatsPage')
QObject::connect:  (receiver name: 'csvimport')
KMyMoneyPlugin::KMMStatementInterface::import start"

A single line needed to be edited, which I've done in the code for this bug.
Do I need to raise a separate bug or add it to this one?

I can add the two fixes as an attachment here.

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

[digikam] [Bug 372308] buttons for rotate does not show very well

[dajomu]

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

--- Comment #1 from dajomu  ---
Created attachment 102160
  --> https://bugs.kde.org/attachment.cgi?id=102160=edit
screenshot of the affected area

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

[digikam] [Bug 372308] New: buttons for rotate does not show very well

[dajomu]

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

Bug ID: 372308
   Summary: buttons for rotate does not show very well
   Product: digikam
   Version: 5.3.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Preview
  Assignee: digikam-de...@kde.org
  Reporter: dajo...@gmail.com
  Target Milestone: ---

Buttons for rotating, show face tags, add face tags and show full screen does
not show very well on some photos. Using the breeze theme these buttons are
monochrome(?) and if the picture have the right color, the buttons are almost
invisible.

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

[digikam] [Bug 372307] New: buttons for rotate does not show very well

[dajomu]

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

Bug ID: 372307
   Summary: buttons for rotate does not show very well
   Product: digikam
   Version: 5.3.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Preview
  Assignee: digikam-de...@kde.org
  Reporter: dajo...@gmail.com
  Target Milestone: ---

Buttons for rotating, show face tags, add face tags and show full screen does
not show very well on some photos. Using the breeze theme these buttons are
monochrome(?) and if the picture have the right color, the buttons are almost
invisible.

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

[kate] [Bug 372306] New: Kate crashes when pressing "0" and "1" while holding alt key

[Marcus Behrendt]

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

Bug ID: 372306
   Summary: Kate crashes when pressing "0" and "1" while holding
alt key
   Product: kate
   Version: 16.08
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: marcus.behrendt...@gmail.com
  Target Milestone: ---

Created attachment 102159
  --> https://bugs.kde.org/attachment.cgi?id=102159=edit
GDB output

All is said in summary. This is reproducible on 2 computers.

I am using Archlinux packages that come without debug symbols. Nevertheless I
attached gdb output.

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

[valgrind] [Bug 371916] execution tree xtree concept

[Josef Weidendorfer]

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

--- Comment #19 from Josef Weidendorfer  ---
(In reply to Julian Seward from comment #18)
> +   Copyright (C) 2016-2016 Philippe Waroquiers
> 
> For m_xtree.c, if there is a lot of code in there which has been moved
> from massif and/or callgrind, and is not much changed, I think it
> would be diplomatic to add a line or two explaining that the original
> authors were Nick and/or Josef.

I assume the callgrind output code used the format spec, and no other code.
So no point to add me :-)

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

[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #5 from Maik Qualmann  ---
Thanks for the patch Mario. Delete to trash over right click on context menu
does not work here. The Item counter remains the same. Del key works. I'll look
at it tomorrow.

Maik

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

[kwin] [Bug 372305] New: kwin crash after disconnecting external monitor (including resolution change)

[Marc Schiffbauer]

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

Bug ID: 372305
   Summary: kwin crash after disconnecting external monitor
(including resolution change)
   Product: kwin
   Version: 5.8.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: msch...@gentoo.org
  Target Milestone: ---

Application: kwin_x11 (5.8.3)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.7.4-gentoo x86_64
Distribution: "Gentoo Base System release 2.3"

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

I plugged out my external monitor from my laptop. After that, kwin crashed

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

Thread 8 (Thread 0x7f951130e700 (LWP 3266)):
#0  0x7f95316bd01f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f952f156d9a in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x27a1f30) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x261b768,
mutex=mutex@entry=0x261b760, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f952a7f35f5 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x261b758) at scenegraph/qsgthreadedrenderloop.cpp:242
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x261b6e0) at
scenegraph/qsgthreadedrenderloop.cpp:690
#5  0x7f952a7f5a9a in QSGRenderThread::run (this=0x261b6e0) at
scenegraph/qsgthreadedrenderloop.cpp:719
#6  0x7f952f15672c in QThreadPrivate::start (arg=0x261b6e0) at
thread/qthread_unix.cpp:344
#7  0x7f95316b7444 in start_thread () from /lib64/libpthread.so.0
#8  0x7f95313fd92d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f9512dba700 (LWP 950)):
#0  0x7f95316bd01f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f952f156d9a in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x2854e70) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x28617c8,
mutex=mutex@entry=0x28617c0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f952a7f35f5 in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x28617b8) at scenegraph/qsgthreadedrenderloop.cpp:242
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x2861740) at
scenegraph/qsgthreadedrenderloop.cpp:690
#5  0x7f952a7f5a9a in QSGRenderThread::run (this=0x2861740) at
scenegraph/qsgthreadedrenderloop.cpp:719
#6  0x7f952f15672c in QThreadPrivate::start (arg=0x2861740) at
thread/qthread_unix.cpp:344
#7  0x7f95316b7444 in start_thread () from /lib64/libpthread.so.0
#8  0x7f95313fd92d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f94fdefb700 (LWP 949)):
#0  QTimerInfoList::timerWait (this=this@entry=0x7f94f8000980, tm=...) at
kernel/qtimerinfo_unix.cpp:413
#1  0x7f952f342829 in QEventDispatcherUNIX::processEvents
(this=0x7f94f80008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:480
#2  0x7f952f2f87ba in QEventLoop::exec (this=this@entry=0x7f94fdefad60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#3  0x7f952f1521a4 in QThread::exec (this=this@entry=0x274a5b0) at
thread/qthread.cpp:507
#4  0x7f952a31fed5 in QQmlThreadPrivate::run (this=0x274a5b0) at
qml/ftw/qqmlthread.cpp:147
#5  0x7f952f15672c in QThreadPrivate::start (arg=0x274a5b0) at
thread/qthread_unix.cpp:344
#6  0x7f95316b7444 in start_thread () from /lib64/libpthread.so.0
#7  0x7f95313fd92d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f94fc8d9700 (LWP 16915)):
#0  0x7f95316bd01f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f952e50ca94 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f952e5fb180 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f952e50cad9 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f95316b7444 in start_thread () from /lib64/libpthread.so.0
#4  0x7f95313fd92d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f951236f700 (LWP 16880)):
#0  0x7f95313f484d in poll () from /lib64/libc.so.6
#1  0x7f952f340f2a in poll (__timeout=-1, __nfds=1, __fds=0x7f950ac8)
at /usr/include/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f950ac8) at
kernel/qcore_unix.cpp:93
#3  qt_safe_poll (fds=0x7f950ac8, nfds=nfds@entry=1,
timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:112
#4  0x7f952f34258d in QEventDispatcherUNIX::processEvents 

[krusader] [Bug 350920] please revert removal of "minimize to tray"

[Stephen Anthony]

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

--- Comment #10 from Stephen Anthony  ---
I guess it's not really needed.  You're right that the description is exactly
what it does now.  But it could also be considered a regression, since the 4.x
version worked with the close button too.  I'm fine with it as-is.

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

[konsole] [Bug 372250] readline's history search on up/down arrow keys visually messes up the edit line

[Egmont Koblinger]

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

Egmont Koblinger  changed:

   What|Removed |Added

 CC||egm...@gmail.com

--- Comment #3 from Egmont Koblinger  ---
This is a typical symptom of control characters in your prompt not being
properly enclosed between \[ and \] (in PS1) or between 0x01 and 0x02 bytes (if
emitted via PROMPT_COMMAND).

Askubuntu and friends are full of this question, just one random example:
http://askubuntu.com/questions/251154/long-lines-overlap-in-bash-ps1-customized-prompt,
there's many more.

It's quite unlikely to be a problem with konsole.

(Just for the record, could you please try with a few other emulators, e.g.
xterm and gnome-terminal, and share the result with us?)

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

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Wulf]

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

--- Comment #27 from Wulf  ---
@Paul Sommer: did you really unset "apply colors to non-qt applications"?

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

[kwin] [Bug 372304] New: kwin_x11 crashes frequently on me when opening a window/application (Intel Skylake Graphics)

[bugzilla_noreply]

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

Bug ID: 372304
   Summary: kwin_x11 crashes frequently on me when opening a
window/application (Intel Skylake Graphics)
   Product: kwin
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dev...@t-online.de
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Kwin_x11 randomly crashes when just opening windows/programms, several times
per day.
- Unusual behavior I noticed:
As a result of the crashe(s), the open window(s) are not correctly rendered, I
mean the graphical glitches. Some parts of the window(s) like titelbars
are out of the screen...   
- Custom settings of the application:
I am not sure if related, but I use the 'Plastik' window decoration (Don't like
the breeze decoration), 'Breeze' as "Widget style" and the rest
(Color,Look and Feel, Desktop Theme) is "Breeze Dark".
A graphics driver is not installed (modesetting)
https://linux.die.net/man/4/modesetting and no other graphics settings are
set/changed (xorg,kernel parameters).
One more thing(not bug relevant) is that with same hardware, same OS/Apps, but
other DEs (mainly Xfce and Mate without the KDE apps),no crashes...

Now, I am quite sure there are other similar bug reports related to Kwin_x11
crashes, so what makes my report different/relevant..?  Well, I have
honestly no idea, all I know is that it's annoying with this frequent crashes
(on two machines, thinkpad L460 and E130) and hopefully it get fixed "soon". 
It wasn't actually intended to submit this bug report, because I know that it's
difficult to reproduce but "DrKonqi" said I should, so I did :)

The crash can be reproduced sometimes.

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

Thread 4 (Thread 0x7f8a2e82a700 (LWP 6011)):
#0  0x7ffe11b39b02 in clock_gettime ()
#1  0x7f8a664b86b6 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7f8a639ce1a1 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f8a63b553a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7f8a63b55955 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#5  0x7f8a63b54694 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f8a63b0123a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f8a639240f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f8a63928d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f8a5f74f454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f8a664ab7df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f8a2f82b700 (LWP 6010)):
#0  0x7ffe11b39b02 in clock_gettime ()
#1  0x7f8a664b86b6 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7f8a639ce1a1 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f8a63b553a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7f8a63b55955 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#5  0x7f8a63b54694 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f8a63b0123a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f8a639240f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f8a5e4aa2d5 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f8a63928d78 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f8a5f74f454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f8a664ab7df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f8a4a291700 (LWP 5997)):
#0  0x7ffe11b39b02 in clock_gettime ()
#1  0x7f8a664b86b6 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7f8a639ce1a1 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f8a63b553a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7f8a63b55955 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#5  0x7f8a63b54694 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f8a63b0123a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f8a639240f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f8a5d674e55 in  () at /usr/lib/libQt5DBus.so.5
#9  0x7f8a63928d78 in  () at /usr/lib/libQt5Core.so.5
#10 0x7f8a5f74f454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f8a664ab7df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f8a66a7f840 

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Paul Sommer]

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

Paul Sommer  changed:

   What|Removed |Added

 CC||n...@paul-sommer.de

--- Comment #26 from Paul Sommer  ---
For me tooltips aren't readable even when I choose Oxygen theme. The background
is a little bit darker then (kind of light beige), but still the white text is
almost unreadable.

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

[plasmashell] [Bug 372303] New: Plasma crash when connect to hidden wifi through usb adapter

[khrysRo]

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

Bug ID: 372303
   Summary: Plasma crash when connect to hidden wifi through usb
adapter
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bym...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
trying to connect to hidden wifi network
- Custom settings of the application:
hidden wifi, and throught an wifi usb adapter tp-link tl-wn725n

The crash can be reproduced sometimes.

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

Thread 8 (Thread 0x7f8e3fd60700 (LWP 2593)):
#0  0x7f8efd5b8bfd in poll () at /lib64/libc.so.6
#1  0x7f8ef9c95e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8ef9c95f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8efdee5d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f8efde8cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f8efdcae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f8e413accf7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7f8efdcb332f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f8efcdc20a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f8efd5c102d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f8e4aaa5700 (LWP 2587)):
#0  0x7f8ef9cd7d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f8ef9c958e9 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f8ef9c95df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f8ef9c95f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f8efdee5d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f8efde8cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f8efdcae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f8f01b5e282 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7f8efdcb332f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f8efcdc20a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f8efd5c102d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f8ed27b9700 (LWP 2585)):
#0  0x7f8efcdc603f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f8f0379186b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f8f03791899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f8efcdc20a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f8efd5c102d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f8ed3fff700 (LWP 2584)):
#0  0x7f8efd5cdc6e in clock_gettime () at /lib64/libc.so.6
#1  0x7f8efdd647d6 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f8efdee43b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#3  0x7f8efdee4945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f8efdee5b5e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f8ef9c954ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f8ef9c95d80 in  () at /usr/lib64/libglib-2.0.so.0
#7  0x7f8ef9c95f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#8  0x7f8efdee5d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#9  0x7f8efde8cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#10 0x7f8efdcae61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#11 0x7f8f00fc2e18 in  () at /usr/lib64/libQt5Qml.so.5
#12 0x7f8efdcb332f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f8efcdc20a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f8efd5c102d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f8ed992a700 (LWP 2583)):
#0  0x7f8efd5b4ccd in read () at /lib64/libc.so.6
#1  0x7f8ef9cd6b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f8ef9c95999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f8ef9c95df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f8ef9c95f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f8efdee5d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f8efde8cd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f8efdcae61a in QThread::exec() () at 

[neon] [Bug 372302] New: qttools5-private-dev 5.7.0 depends on qttools5-dev 5.5.1

[Kai Uwe Broulik]

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

Bug ID: 372302
   Summary: qttools5-private-dev 5.7.0 depends on qttools5-dev
5.5.1
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [unstable]
  Assignee: neon-b...@kde.org
  Reporter: k...@privat.broulik.de
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

I just tried to install qttools5-private-dev (5.7.0-0neon+16.04+build6) but it
depends on qttools5-dev (5.5.1-3build1) whereas neon ships qttools5-dev
(5.7.0-0neon+16.04+build6), so the packages are both Qt 5.7 packages but the
private one wants 5.5.1.

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

[frameworks-kdelibs4support] [Bug 370223] kdelibs4support 5.27.0 fails to compile with OpenSSL 1.1

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[ark] [Bug 372300] Ark can't open RAR file

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #2 from Elvis Angelaccio  ---
I just backported the bugfix on the 16.04 branch. The Kubuntu packagers are
supposed to update the Ark package in the next days (if they don't, open a bug
in the Kubuntu bugtracker).

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

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

[ark] [Bug 368786] Unable to open RAR files with shared-mime-info 1.7

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||jonay.sant...@gmail.com

--- Comment #4 from Elvis Angelaccio  ---
*** Bug 372300 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 372298] Multihead inoperative on second screen

[Jonathan E . Snow]

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

--- Comment #1 from Jonathan E. Snow  ---
deleting xorg.conf and letting it use xinerama mode works around the problem. 
Multihead is still broke. 

xorg.conf:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder63)  Tue Oct 20 21:00:15
PDT 2009

# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#
# **
# Refer to the xorg.conf(5x) man page for details about the format of 
# this file.
# **
# **
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **
#
# **
# Files section.  This allows default font and rgb paths to be set
# **
# **
# Server flags section.
# **
# **
# Input devices
# **
# **
# Core keyboard's InputDevice section
# **
#Section "InputDevice"
#Identifier "Keyboard1"
#Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
#Option "Protocol"  "Xqueue"
#Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#Option "Xleds"  "1 2 3"
#Option "LeftAlt" "Meta"
#Option "RightAlt""ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#Option "XkbModel""pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#Option "XkbModel""microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#Option "XkbLayout"   "de"
# or:
#Option "XkbLayout"   "de"
#Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#Option "XkbOptions"  "ctrl:swapcaps"
# These are the default XKB settings for Xorg
#Option "XkbModel""pc105"
#Option "XkbLayout"   "us"
#Option "XkbVariant"  ""
#Option "XkbOptions"  ""
#Option "XkbDisable"
#Option "XkbModel"  "pc104"
#Option "XkbLayout" "us"
#EndSection
# **
# Core Pointer's InputDevice section
# **
#Section "InputDevice"
## Identifier and driver
#Identifier "Mouse1"
#Driver "mouse"
#Option "Protocol""Auto"
#Option "Device"  "/dev/input/mouse0"
#Option "Buttons" "5"
#:wq
#Option "ZAxisMapping" "4 5"
# Mouse-speed setting for PS/2 mouse.
#Option "Resolution""256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
#Option "Protocol"  "Xqueue"
# 

[plasmashell] [Bug 372301] Plasmashell crash on suspend/resume

[Sergey]

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

Sergey  changed:

   What|Removed |Added

   Platform|Compiled Sources|Gentoo Packages

--- Comment #1 from Sergey  ---
It happens for few days probably. So quite recent bug somewhere.

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

[ark] [Bug 372300] Ark can't open RAR file

[Elvis Angelaccio]

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

--- Comment #1 from Elvis Angelaccio  ---
Git commit e05e5c4504428bd70d1a780904ef6e1a62482e93 by Elvis Angelaccio.
Committed on 10/11/2016 at 18:36.
Pushed by elvisangelaccio into branch 'Applications/16.04'.

Backport commit 9a9a851049cd904f08c9594cc6aacf696886404e

This fixes RAR support with Ark 16.04.3 and shared-mime-info >= 1.7
If you ship the combination above (e.g. Kubuntu 16.10 does), please
update your Ark package and include this commit.

CCMAIL: kde-distro-packag...@kde.org

M  +1-1plugins/clirarplugin/CMakeLists.txt
M  +3-2plugins/clirarplugin/kerfuffle_clirar.json
M  +1-1plugins/cliunarchiverplugin/CMakeLists.txt
M  +3-2plugins/cliunarchiverplugin/kerfuffle_cliunarchiver.json

http://commits.kde.org/ark/e05e5c4504428bd70d1a780904ef6e1a62482e93

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

[plasmashell] [Bug 372301] New: Plasmashell crash on suspend/resume

[Sergey]

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

Bug ID: 372301
   Summary: Plasmashell crash on suspend/resume
   Product: plasmashell
   Version: 5.8.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rion...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)
 (Compiled from sources)
Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-ck-r1 x86_64
Distribution: "Gentoo Base System release 2.3"

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

I closed lid of my laptop for few hours, opened again later.
Plasmashell was not running on open.
The last time it restarted automatically but I usually I have to
alt+f2+plasmashell to restart it.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f866acc2700 (LWP 12610)):
#0  0x7f872a545c30 in timerSourceCheckHelper(GTimerSource*) () from
/usr/lib64/libQt5Core.so.5
#1  0x7f8725a6ca11 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f8725a6cf80 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8725a6d0ec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f872a545d9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f872a4f5aaa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f872a354b94 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f866bb7fa57 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#8  0x7f872a35903c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f872940d434 in start_thread () from /lib64/libpthread.so.0
#10 0x7f8729c09ded in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f867c798700 (LWP 12608)):
#0  0x7f872a351ff9 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
#1  0x7f872a545b1f in postEventSourcePrepare(_GSource*, int*) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f8725a6c56d in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8725a6cf0b in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f8725a6d0ec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f872a545d9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f872a4f5aaa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f872a354b94 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f872d4c8626 in QQuickPixmapReader::run() () from
/usr/lib64/libQt5Quick.so.5
#9  0x7f872a35903c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f872940d434 in start_thread () from /lib64/libpthread.so.0
#11 0x7f8729c09ded in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f8707bde700 (LWP 12607)):
#0  0x7f8729412fef in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f872ed212f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQt5Script.so.5
#2  0x7f872ed21339 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /usr/lib64/libQt5Script.so.5
#3  0x7f872940d434 in start_thread () from /lib64/libpthread.so.0
#4  0x7f8729c09ded in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f8711a43700 (LWP 12606)):
#0  0x7f8729bfcd5d in read () from /lib64/libc.so.6
#1  0x7f8725ab02e0 in g_wakeup_acknowledge () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f8725a6cac4 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8725a6cf80 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f8725a6d0ec in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f872a545d9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f872a4f5aaa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f872a354b94 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f872cb462c5 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#9  0x7f872a35903c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f872940d434 in start_thread () from /lib64/libpthread.so.0
#11 0x7f8729c09ded in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f8713fff700 (LWP 12605)):
#0  0x7f8725ab1694 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f8725a6c560 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  

[KScreen] [Bug 372228] libkscreen-qt5: qt_message_fatal(): kscreen_backend_launcher

[Rex Dieter]

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

--- Comment #5 from Rex Dieter  ---
Is your hostname changing during or shortly after you login?  Could be due to
sddm issue:
https://github.com/sddm/sddm/issues/733
where xauth credentials get invalidated.

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

[kteatime] [Bug 369124] (Regression) Incorrect, outdated kteatime icon

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

 CC||andr...@stikonas.eu

--- Comment #1 from Andrius Štikonas  ---
Tomasz, I don't think kteatime is that well maintained, so you should probably
try to do the change yourself otherwise nobody will do it...

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

[valgrind] [Bug 371916] execution tree xtree concept

[Julian Seward]

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

--- Comment #18 from Julian Seward  ---
Some comments on the v3 patch:

Mostly it looks fine.  Below [1] some small comments.

Larger comments:

* I assume there are no regressions with correctness or performance
  with this, yes?  Could you do a self-host Memcheck run at some point?

* The large size of the patch concerns me a bit.  I would be happier
  if it could be split into two parts:

  (1) that creates m_xtree.c and refactors Massif to use it, but
  does not change the user-visible functionality at all.  So
  it is an implementation-only change, and

  (2) a patch that builds on (1), that supplies the new functionality.

  Is that possible, if it is not a lot of work?


[1] Small comments:



+typedef
+   struct { Addr a; const HChar* sym_name; PtrdiffT offset; }
+   Sym_Name_CacheEnt;

I prefer to have something more descriptive than just "a" for the
first field.  Since it is debug-info related, it would also be good to
clarify whether this is an SVMA or an AVMA or something else, per
comment at the top of m_debuginfo/debuginfo.c.  I suspect it's a SVMA,
in which case a good name would by "sym_svma".



+"--xtree-memory=none|allocs|full   profile heap memory in an xtree
[none]\n"
+"  and produces a report at the end of the
execution\n"
+"  none: no profiling, allocs: current
allocated\n"
+"  size/blocks, full: profile current and
cumulative\n"
+"  allocated size/blocks and freed size/blocks.\n"
+"--xtree-memory-file=   xtree memory report file
[xtmemory.kcg.%%p]\n"

This flag only has effect for tools that replace malloc, correct?  Is
it listed in the section "user options for Valgrind tools that replace
malloc:" ?



+   This file is part of Valgrind, a dynamic binary instrumentation
+   framework.
+
+   Copyright (C) 2016-2016 Philippe Waroquiers

For m_xtree.c, if there is a lot of code in there which has been moved
from massif and/or callgrind, and is not much changed, I think it
would be diplomatic to add a line or two explaining that the original
authors were Nick and/or Josef.  See the top of coregrind/m_wordfm.c for
an example.



 // growing such a block, but for consistency (it also simplifies things) we
 // ignore such reallocs as well.
+// XTREE??? why can't we just consider that a realloc of an ignored
+// alloc is just a new alloc (i.e. do not remove the old sz from the stats).

and again later.  The "XTREE???" is confusing -- I don't know what it
signifies.  Can you maybe write instead something like "PW Nov 2016,
xtree work:"?  I do that in comments from time to time.



Per previous comments in the bug re CamelCase vs snake_case, I really
have no problem mixing them.  I like to use camelcase, with a capital
first letter for type names, and snake case when function names get
long.  But no fixed rules.

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

[ark] [Bug 372300] New: Ark can't open RAR file

[Jonay]

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

Bug ID: 372300
   Summary: Ark can't open RAR file
   Product: ark
   Version: 16.04.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plugins
  Assignee: rthoms...@gmail.com
  Reporter: jonay.sant...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

I have installed the UNRAR package, but Ark seems to ignore it. I can't unrar
any .RAR file.

I'm using ARK 16.04.3, KDE Frameworks 5.26.0, and Qt 5.6.1.

Thanks in advance.

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

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr]

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

--- Comment #14 from Andreas Cord-Landwehr  ---
... and here the output after resumed from suspend-to-ram:

kscreen-console bug
kscreen-console(11252)/(default) main: START: Requesting Config
kscreen-console(11252)/(default) KScreen::BackendManager::startBackend: DBUS
signal sent
kscreen-console(11252)/(default) KScreen::BackendManager::requestBackend: SEND
startBackend for  ""
kscreen-console(11252)/(default) KScreen::BackendManager::onBackendRequestDone:
DBUS DONE
kscreen-console(11252)/(default) configReceived: Received config. Took 68
milliseconds

xrandr --verbose==
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (0x4b) normal (normal left inverted right
x axis y axis) 309mm x 173mm
Identifier: 0x42
Timestamp:  103923196
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4b) 141.000MHz -HSync -VSync *current +preferred
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz
  1920x1080 (0x4c) 138.500MHz +HSync -VSync 
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz 
v: height 1080 start 1083 end 1088 total    clock  59.93Hz  
  1680x1050 (0x4d) 146.250MHz -HSync +VSync 
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz 
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz  
  1680x1050 (0x4e) 119.000MHz +HSync -VSync 
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz 
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz  
  1600x1024 (0x4f) 103.125MHz +HSync +VSync 
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz 
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz  
  1400x1050 (0x50) 122.000MHz +HSync +VSync 
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz 
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz  
  1280x1024 (0x51) 108.000MHz +HSync +VSync 
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz 
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz  
  1440x900 (0x52) 106.500MHz -HSync +VSync  
h: width  1440 start 1520 end 1672 total 1904 skew0 clock  55.93KHz 
v: height  900 start  903 end  909 total  934   clock  59.89Hz  
  1280x960 (0x53) 108.000MHz +HSync +VSync  
h: width  1280 start 1376 end 1488 total 1800 skew0 clock  60.00KHz 
v: height  960 start  961 end  964 total 1000   clock  60.00Hz  
  1360x768 (0x54) 84.750MHz -HSync +VSync   
h: width  1360 start 1432 end 1568 total 1776 skew0 clock  47.72KHz 
v: height  768 start  771 end  781 total  798   clock  59.80Hz  
  1360x768 (0x55) 72.000MHz +HSync -VSync   
h: width  1360 start 1408 end 1440 total 1520 skew0 clock  47.37KHz
v: height  768 start  771 end  781 total  790   clock  59.96Hz
  1152x864 (0x56) 81.620MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock  53.70KHz
v: height  864 start  865 end  868 total  895   clock  60.00Hz
  1024x768 (0x57) 133.475MHz -HSync +VSync DoubleScan
h: width  1024 start 1100 end 1212 total 1400 skew0 clock  95.34KHz
v: height  768 start  768 end  770 total  794   clock  60.04Hz
  1024x768 (0x58) 

[kmail2] [Bug 372299] Kmail does not open.

[ObsoleteMan]

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

ObsoleteMan  changed:

   What|Removed |Added

 CC||msovi...@gmail.com

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

[Discover] [Bug 372277] Discover crashes when used to open rpm file

[Aleix Pol]

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

--- Comment #1 from Aleix Pol  ---
Please fill version and platform fields.

Also how do you open an rpm file?

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

[kmail2] [Bug 372299] New: Kmail does not open.

[ObsoleteMan]

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

Bug ID: 372299
   Summary: Kmail does not open.
   Product: kmail2
   Version: 4.14.1
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: msovi...@gmail.com
  Target Milestone: ---

Akonadi Server Self-Test Report
===

Test 1:  SUCCESS


Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server
configuration and was found on your system.

File content of '/home/michael/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-michael.22RIJb/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS


Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the
recommended setup for a secure system.

Test 3:  SUCCESS


MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server
'/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure
you have the necessary read and execution rights on the server executable. The
server executable is typically called 'mysqld'; its location varies depending
on the distribution.

Test 4:  SUCCESS


MySQL server is executable.
Details: MySQL server found: 161110 12:36:41 [Warning] Using unique option
prefix key_buffer instead of key_buffer_size is deprecated and will be removed
in a future release. Please use the full name instead.
/usr/sbin/mysqld  Ver 5.5.53-0+deb8u1 for debian-linux-gnu on x86_64 ((Debian))


Test 5:  SUCCESS


No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The
log can be found in '/home/michael/.local/share/akonadi/db_data/mysql.err'.

Test 6:  SUCCESS


MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is
readable at /etc/akonadi/mysql-global.conf.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp 
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#
sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of
data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for
debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM
information_schema.tables WHERE table_schema not in ("mysql",
"information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show
global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other
internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables
(default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin,
8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but
more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or

[KScreen] [Bug 364044] Second screen in docking station keeps black after suspend

[Andreas Cord-Landwehr]

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

--- Comment #13 from Andreas Cord-Landwehr  ---
Hi, the problem is still present with Plasma 5.8. Here the output with both
screens working:

$ kscreen-console bug
kscreen-console(10856)/(default) main: START: Requesting Config
kscreen-console(10856)/(default) KScreen::BackendManager::startBackend: DBUS
signal sent
kscreen-console(10856)/(default) KScreen::BackendManager::requestBackend: SEND
startBackend for  ""
kscreen-console(10856)/(default) KScreen::BackendManager::onBackendRequestDone:
DBUS DONE
kscreen-console(10856)/(default) configReceived: Received config. Took 66
milliseconds

xrandr --verbose==
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (0x4b) normal (normal left inverted right
x axis y axis) 309mm x 173mm
Identifier: 0x42
Timestamp:  103923196
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
000006af3d12
00160104951f11780287e5a456509e26
0d50540001010101010101010101
010101010101143780b8703824401010
3e0035ad1018000f
002000fe0041
554f0a20202020202020202000fe
004231343048414e30312e32200a00a3
scaling mode: Full aspect 
supported: None, Full, Center, Full aspect
Broadcast RGB: Automatic 
supported: Automatic, Full, Limited 16:235
audio: auto 
supported: force-dvi, off, auto, on
  1920x1080 (0x4b) 141.000MHz -HSync -VSync *current +preferred
h: width  1920 start 1936 end 1952 total 2104 skew0 clock  67.02KHz
v: height 1080 start 1083 end 1097 total 1116   clock  60.05Hz  
  1920x1080 (0x4c) 138.500MHz +HSync -VSync 
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  66.59KHz 
v: height 1080 start 1083 end 1088 total    clock  59.93Hz  
  1680x1050 (0x4d) 146.250MHz -HSync +VSync 
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz 
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz  
  1680x1050 (0x4e) 119.000MHz +HSync -VSync 
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz 
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz  
  1600x1024 (0x4f) 103.125MHz +HSync +VSync 
h: width  1600 start 1600 end 1656 total 1664 skew0 clock  61.97KHz 
v: height 1024 start 1024 end 1029 total 1030   clock  60.17Hz  
  1400x1050 (0x50) 122.000MHz +HSync +VSync 
h: width  1400 start 1488 end 1640 total 1880 skew0 clock  64.89KHz 
v: height 1050 start 1052 end 1064 total 1082   clock  59.98Hz  
  1280x1024 (0x51) 108.000MHz +HSync +VSync 
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz 
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz  
  1440x900 (0x52) 106.500MHz -HSync +VSync  
h: width  1440 start 1520 end 1672 total 1904 skew0 clock  55.93KHz 
v: height  900 start  903 end  909 total  934   clock  59.89Hz  
  1280x960 (0x53) 108.000MHz +HSync +VSync  
h: width  1280 start 1376 end 1488 total 1800 skew0 clock  60.00KHz 
v: height  960 start  961 end  964 total 1000   clock  60.00Hz  
  1360x768 (0x54) 84.750MHz -HSync +VSync   
h: width  1360 start 1432 end 1568 total 1776 skew0 clock  47.72KHz 
v: height  768 start  771 end  781 total  798   clock  59.80Hz  
  1360x768 (0x55) 72.000MHz +HSync -VSync   
h: width  1360 start 1408 end 1440 total 1520 skew0 clock  47.37KHz 
v: height  768 start  771 end  781 total  790   clock  59.96Hz
  1152x864 (0x56) 81.620MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock  53.70KHz
v: height  864 start  865 end  868 total  895   clock  60.00Hz
  1024x768 (0x57) 133.475MHz -HSync +VSync DoubleScan
h: width  1024 start 1100 end 1212 total 1400 skew0 clock  95.34KHz
v: height  768 start  768 end  770 total  794   

[plasmashell] [Bug 369450] Multiple monitor desktops & backgrounds are simply blank.

[Jonathan E . Snow]

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

Jonathan E. Snow  changed:

   What|Removed |Added

 CC||jes...@uh.edu

--- Comment #2 from Jonathan E. Snow  ---
Similar situation:
https://bugs.kde.org/show_bug.cgi?id=372298

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

[valgrind] [Bug 371916] execution tree xtree concept

[Josef Weidendorfer]

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

--- Comment #17 from Josef Weidendorfer  ---
(In reply to Philippe Waroquiers from comment #16)
> >  About the changes in the malloc
> >   wrappers, I think it would be better if the tool can register handlers,
> >   and these handlers then call e.g. VG_(XTMemory_Full_alloc).
> I guess this could be done, but I think this would be less practical
> than the current approach:  the malloc replacement is today
> calling a tool replacement function.

Ah, I see. Then that's fine with me.

> > About the XTree API, why do you need these add/sub variants?
> > Why not just have a function to get a pointer to the value to be updated?
> > Any reduction operation may be useful, such as min/max.
> Yes, any operation can be done in the add/sub : these functions
> get a pointer to the value being updated.

I just wondered if the xtree API could work without having to pass
add/sub_data_fn handlers to make it simpler. I see that the add
handler is used for calculating the totals in the callgrind output.
What about "reduce" instead of "add"? It's a reduction operation to
be used for propagating the value up the call chains. You could do
this before the callgrind output to get smaller files.
If callgrind_annotate/kcachegrind will be able at some point
to consume call chains, it has to be another format anyway.


> As a follow-up, I intend to work on a 'syscall xtree' which e.g. might
> capture min/max (or maybe an histogram) of values.

Yes, statistics are interesting: min/max/variance/average and histograms.
I always wanted to do that in callgrind...

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

[kmail2] [Bug 315568] kmail crash on startup

[ObsoleteMan]

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

ObsoleteMan  changed:

   What|Removed |Added

 CC||msovi...@gmail.com

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

[Discover] [Bug 372205] remove package dialog is meh

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/disc
   ||over/df6f7b1744b332b353a708
   ||6628296899f9f2eeed

--- Comment #2 from Aleix Pol  ---
Git commit df6f7b1744b332b353a7086628296899f9f2eeed by Aleix Pol.
Committed on 10/11/2016 at 17:34.
Pushed by apol into branch 'master'.

Improve error message for updates with removals

M  +1-1libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp

http://commits.kde.org/discover/df6f7b1744b332b353a7086628296899f9f2eeed

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

[plasmashell] [Bug 372298] New: Multihead inoperative on second screen

[Jonathan E . Snow]

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

Bug ID: 372298
   Summary: Multihead inoperative on second screen
   Product: plasmashell
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jes...@uh.edu
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

On KDE Plasma 5, multihead displays do not work with my hardware (nvidia). The
primary display (DVI-0) works, the secondary display (CRT-1) shows only a
background and unintentional artifacts from the primary display, such as cursor
artifacts. 

Similar to this bug: 
https://bugs.kde.org/show_bug.cgi?id=158850
But applies to Plasma 5.8.3 with qt 5.6.2

Reproducible: Always

Steps to Reproduce:
1.startx

Actual Results:  
2.KDE Plasma 5 starts on primary display, 
3. Secondary display shows only a desktop. Mouse can move between displays, but
app windows cannot be displayed, and there is no kpanel. 

Expected Results:  
3. Second display should show a desktop, kpanel, and be able to host
applicaiton windows.  

Nvidia settings detects displays correctly, as it did in KDE 4. 
DVI


XRandR shows the following: 

jesnow@Merckx ~ $ xrandr
Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected primary 1280x1024+0+0 (normal left inverted right x axis y
axis) 376mm x 301mm
   1024x768  75.03 +  70.0760.00  
   1600x1200 65.0060.00  
   1400x1050 74.7659.98  
   1280x1024 75.0260.02* 
   1280x960  60.00  
   1152x864  75.00  
   832x624   74.55  
   800x600   75.0072.1960.3256.25  
   700x525   74.7659.98  
   640x480   75.0072.8159.94  
   512x384   70.0760.00  
   400x300   72.19  
   320x240   72.8160.05  
HDMI-0 disconnected (normal left inverted right x axis y axis)

KDE system settings shows the same. 

jesnow@Merckx ~ $ emerge --info
Portage 2.3.0 (python 3.4.3-final-0, default/linux/x86/13.0/desktop/plasma,
gcc-4.9.3, glibc-2.22-r4, 4.4.26-gentoo i686)
=
System uname:
Linux-4.4.26-gentoo-i686-Intel-R-_Core-TM-_i7_CPU_860_@_2.80GHz-with-gentoo-2.2
KiB Mem:12461284 total,   4806628 free
KiB Swap:3905532 total,   3905280 free
Timestamp of repository gentoo: Tue, 08 Nov 2016 19:45:01 +
sh bash 4.3_p48
ld GNU ld (Gentoo 2.25.1 p1.1) 2.25.1
app-shells/bash:  4.3_p48::gentoo
dev-java/java-config: 2.2.0-r3::gentoo
dev-lang/perl:5.22.2::gentoo
dev-lang/python:  2.7.10-r1::gentoo, 3.4.3-r1::gentoo
dev-util/cmake:   3.5.2-r1::gentoo
dev-util/pkgconfig:   0.28-r2::gentoo
sys-apps/baselayout:  2.2::gentoo
sys-apps/openrc:  0.21.7::gentoo
sys-apps/sandbox: 2.10-r1::gentoo
sys-devel/autoconf:   2.13::gentoo, 2.69::gentoo
sys-devel/automake:   1.11.6-r1::gentoo, 1.14.1::gentoo, 1.15::gentoo
sys-devel/binutils:   2.25.1-r1::gentoo
sys-devel/gcc:4.9.3::gentoo
sys-devel/gcc-config: 1.7.3::gentoo
sys-devel/libtool:2.4.6::gentoo
sys-devel/make:   4.1-r1::gentoo
sys-kernel/linux-headers: 4.3::gentoo (virtual/os-headers)
sys-libs/glibc:   2.22-r4::gentoo
Repositories:

gentoo
location: /home/portage
sync-type: rsync
sync-uri: rsync://rsync.us.gentoo.org/gentoo-portage
priority: -1000

Merckx
location: /home/portage/local
masters: gentoo
priority: 0

ACCEPT_KEYWORDS="x86"
ACCEPT_LICENSE="* -@EULA googleearth AdobeFlash-11.x dlj-1.1
skype-4.0.0.7-copyright"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=core2 -msse4 -pipe -mcx16 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib/libreoffice/program/sofficerc /usr/share/config
/usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild
/etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -march=core2 -msse4 -pipe -mcx16 -fomit-frame-pointer"
DISTDIR="/home/portage/distfiles"
FCFLAGS="-O2 -march=i686 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks
ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs
protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs
unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -march=i686 -pipe"
GENTOO_MIRRORS="http://gentoo.cites.uiuc.edu/pub/gentoo/
http://gentoo.mirrors.easynews.com/linux/gentoo/
ftp://mirror.fslutd.org/linux/distributions/gentoo/;
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j10"
PKGDIR="/home/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times

[krita] [Bug 372198] Shortcuts reset to default

[eliotJ]

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

--- Comment #4 from eliotJ  ---
Today on the IRC (#krita channel):
"[12:52:50]  sigh, krita crashed and I lost all my hotkeys ~_~
[12:54:12]  and reassigning hotkeys without manually assigning
overlapping keys to something else still creates ambiguous hotkeys
[12:54:19]  I thought that was fixed o.O
[12:55:15]  and you still can't set any hotkey custom shortcut to
"none" as it defaults back to what it was
[12:55:24]  so my fill is now shift ctrl alt f
[12:57:01]  canvas input settings didn't reset, only keyboard
shortcuts o.O
[12:58:54]  oh I see, assigning a key to something that already
exists sets the previous hotkey to "none" but because you can't set anything to
"none" it just makes duplicate hotkeys
 I think with the shortcuts, the whole "none" is just not working
when it has to get assigned to a shortcut. Need to figure out how that works"

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

[plasmashell] [Bug 372297] New: Plasma says it crashes, but nothing really happend.

[Dominik Klementowski]

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

Bug ID: 372297
   Summary: Plasma says it crashes, but nothing really happend.
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: dominik...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.4.30-1-lts x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I closed laptop lid when external screen was connected with d-sub and then I
opened it back.

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

Thread 16 (Thread 0x7f6707fff700 (LWP 1162)):
#0  0x7f67f315f10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f67f404ac2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f673dcd31c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f673dcd7988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f673dcd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f673dcd51f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f67f4049d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f67f3159454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f67f395f7df in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f6724fca700 (LWP 1161)):
#0  0x7f67f315f10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f67f404ac2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f673dcd31c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f673dcd7988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f673dcd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f673dcd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f673dcd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7f673dcd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7f673dcd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7f673dcd51f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#16 0x7f67f4049d78 in  () at /usr/lib/libQt5Core.so.5
#17 0x7f67f3159454 in start_thread () at /usr/lib/libpthread.so.0
#18 0x7f67f395f7df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f67257cb700 (LWP 1160)):
#0  0x7f67f315f10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f67f404ac2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f673dcd31c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f673dcd7988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f673dcd79e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f673dcd2263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f673dcd51f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f67f4049d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f67f3159454 

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[Jan Wolter]

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

--- Comment #31 from Jan Wolter  ---
Created attachment 102158
  --> https://bugs.kde.org/attachment.cgi?id=102158=edit
Update Patch IgnoreDirectories

Hello Gilles,

yes there are progress.
The attached patch supports the requested feature: You are able to add
directories (separated by whitespaces in the text field) that you want to
ignore from your collection. The settings are stored in DbEngineParameters. All
directories that exactly match the configured directory name, will be ignored
from the photo collection.

But unfortunately, the configured directories gets ignored only after
restarting digikam.
When a user clicks the OK-Button of settings dialog, the DbEngineParameters are
updated correctly. But in the CollectionScanner CoreDbAccess().parameters()
delivers instead of the actual parameters, the parameters that were valid at
digikam startup.
Do you have, any hints to solve this?

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

[Spectacle] [Bug 372140] Tiny window on a HiDPI screen

[Roman Odaisky]

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

Roman Odaisky  changed:

   What|Removed |Added

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

--- Comment #2 from Roman Odaisky  ---
Git version works fine, thanks.

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

[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate

[Mario Frank]

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

--- Comment #4 from Mario Frank  ---
Created attachment 102157
  --> https://bugs.kde.org/attachment.cgi?id=102157=edit
Patch for the bug.

Tested this patch. Seems to work quite well. Please review it.

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

[krita] [Bug 372198] Shortcuts reset to default

[eliotJ]

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

--- Comment #3 from eliotJ  ---
Shortcuts being ambiguous... Yes, I also get this sometimes... Imho these
dataloss should be fixed before stable relase. This regression can broke a bit
Krita reputation if this will stay not fixed in stable relase :(

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

[Powerdevil] [Bug 353463] RFE: Make use of iio-sensor-proxy

[Stefan Brüns]

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

Stefan Brüns  changed:

   What|Removed |Added

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

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

[Spectacle] [Bug 372140] Tiny window on a HiDPI screen

[Peter Wu]

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

Peter Wu  changed:

   What|Removed |Added

   Assignee|m...@baloneygeek.com  |pe...@lekensteyn.nl
 CC||pe...@lekensteyn.nl

--- Comment #1 from Peter Wu  ---
Can you give more details, like the version of Spectacle, Qt and your
distribution?

Have you tried git master? There should be some fixes for HiDPI. Probably not
the window size, but maybe you are lucky.

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

[kwin] [Bug 372296] New: "Keep window thumbnails" set to "Always" doesn't work with shaded windows.

[Allan]

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

Bug ID: 372296
   Summary: "Keep window thumbnails" set to "Always" doesn't work
with shaded windows.
   Product: kwin
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: glx
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kdeb...@metalight.dk
  Target Milestone: ---

When hovering the icon-only task manager after shading a window, instead of the
window thumbnail, an icon is shown instead. Even though "Keep window
thumbnails" is set to "Always".

Minimizing instead of shading works as expected - thumbnail is shown in this
case.

So it is just for shaded windows that the setting does not work.

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

[Spectacle] [Bug 372270] Display pixel-width and height of selected region before taking a screenshot

[Peter Wu]

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

Peter Wu  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||pe...@lekensteyn.nl

--- Comment #1 from Peter Wu  ---
Already implemented, will be available in December :-)

(or you can build Spectacle from git master)

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

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

[Spectacle] [Bug 357080] Show area when capturing a rectangolar region

[Peter Wu]

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

Peter Wu  changed:

   What|Removed |Added

 CC||cher...@aip.de

--- Comment #4 from Peter Wu  ---
*** Bug 372270 has been marked as a duplicate of this bug. ***

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

[KScreen] [Bug 356864] Plasma cannot adapt to VM host window

[Sebastian Kügler]

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

--- Comment #31 from Sebastian Kügler  ---
Ok, cool. After some more fiddling, I'm getting the events now that I was
looking for. On it.

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

[plasmashell] [Bug 368384] [Feature Request] - Support for transparent panels

[Michail Vourlakos]

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

--- Comment #7 from Michail Vourlakos  ---
I have updated...

https://phabricator.kde.org/D3282
https://phabricator.kde.org/D3283

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

[krita] [Bug 372289] Crash when clicking in brush preset preview area

[bugzilla_noreply]

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

--- Comment #3 from jdre...@web.de ---
Great!

Looking forward for this version.
I already like krita 3.0.90 at lot more for painting than photoshop I used till
now.
Keep on working on this great software.
Best regards 
J

(In reply to Dmitry Kazakov from comment #2)
> Hi, jdreske!
> 
> Thank you for the report! I have just fixed that crash in the development
> version of Krita! Please wait for the next update with the fix :)

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