date:20170614

[kate] [Bug 380861] >> Replace checked << cause a freeze/crash

2017-06-14 Thread Kåre Särs

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

--- Comment #5 from Kåre Särs  ---
I have a patch for disabling the buttons during a search and I am working on
indicating what file is currently being replaced in (or updating it every x ms)

Only problem is finding time to finish it ;)

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

[skrooge] [Bug 381168] Change tab order of properties editor

2017-06-14 Thread Stephane MANKOWSKI

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

   Assignee|guillaume.deb...@gmail.com  |steph...@mankowski.fr
 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1

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

[krita] [Bug 381189] New: Beizer curves do not properly save as previewed on the editor

2017-06-14 Thread bugzilla_noreply

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

Bug ID: 381189
   Summary: Beizer curves do not properly save as previewed on the
editor
   Product: krita
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Vector Objects and Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: commando...@gmail.com
  Target Milestone: ---

When creating a vector bezier curve on a vector layer and saving it as a Krita
file and reopening the file, the bezier curve is slightly transformed compared
to the original line. It also reverted the vector cap style on the bezier curve
to the default. Exporting the image to an image format before reopening the
file keeps what is seen in the editor preview. Exporting the image to an image
format after reopening the file keeps the slightly transformed bezier curve.
This is preventing me from effectively using vector layers because I cannot
rely on saving the vectors to a Krita file.

Krita versions: I know it happens from 3.1.1 to 3.1.4. Have not tested other
versions.
OS/Specs:
Windows 10 Pro 64-bit v1703 (creator's update)
Intel Core i5-6600K @ 3.50 GHz
ATI AMD Radeon R9 390 8GB

Settings:
Hi-DPI support: Disabled
OpenGL: Enabled
Enable curve anti-aliasing: Enabled
Disable vector optimizations: Enabled

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

[krita] [Bug 381189] Beizer curves do not properly save as previewed on the editor

2017-06-14 Thread bugzilla_noreply

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

commando...@gmail.com changed:

   What|Removed |Added

Version|unspecified |3.1.4

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

[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced

2017-06-14 Thread bugzilla_noreply

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

--- Comment #10 from tro...@free.fr ---
(In reply to Pranav Sharma from comment #9)
> I am on KDE neon, x11, and I am getting this bug as well. Some times the
> notification is in the correct position, but then the next ones are in the
> top left corner. Only observer after kde frameworks 5.35.

I get this as well on X11 since Frameworks 5.35, but it might be a different
issue.

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

[plasmashell] [Bug 379213] Global Menu suggestion

2017-06-14 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

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

--- Comment #2 from Kai Uwe Broulik  ---
Thanks for your suggestions. However, please only file one issue/wish per
ticket, also first check whether it has already been reported. I'm pretty sure
all three have been reported somewhere already.

You might want to try the "Yet Another Window Control" (or something like this)
plasmoid on the KDE Store which should at least give you the application name 
and controls.

> 1. Be able to show Global Menu only if current window is maximized else menu 
> will be on default position (in window)

This is not possible unfortunately. Qt exports the menu once it finds a global
menu service. It cannot change this at runtime and the architecture of Qt would
require significant re-engineering effort to make this possible. 

This is also the reason we have no "HUD" yet (e.g. the app menu searchable
through KRunner) as that would require exporting the menu but then you'd lose
it in the window if you don't want to use global menu.

In a nutshell, I'm aware of all three issues and like your suggestions but
they're not a super high priority right now, sorry.

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

[kde] [Bug 374808] Dependency on QtWebEngine might make KDE non-(free/libre)

2017-06-14 Thread Florian Bruhin

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

Florian Bruhin  changed:

   What|Removed |Added

 CC||kde@the-compiler.org

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

[krita] [Bug 381190] New: Crash when clicking on "Color Space Browser" in "New" dialog

2017-06-14 Thread Elias Probst

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

Bug ID: 381190
   Summary: Crash when clicking on "Color Space Browser" in "New"
dialog
   Product: krita
   Version: 3.1.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: m...@eliasprobst.eu
  Target Milestone: ---

Application: krita (3.1.2)
 (Compiled from sources)
Qt Version: 5.7.1
Frameworks Version: 5.35.0
Operating System: Linux 4.10.1-gentoo x86_64
Distribution: "Gentoo Base System release 2.3"

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

- Start Krita
- Open "New" dialog
- Click on "Color Space Browser"
- Krita crashes

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f583b332800 (LWP 19059))]

Thread 6 (Thread 0x7f5827218700 (LWP 19060)):
#0  0x7f5838899e6d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f583712a8f2 in poll (__timeout=-1, __nfds=1, __fds=0x7f5827217cc0)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x21ccbc0, cond=cond@entry=0x21ccc00,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_conn.c:479
#3  0x7f583712c6df in xcb_wait_for_event (c=0x21ccbc0) at
/var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_in.c:693
#4  0x7f582956c2a9 in QXcbEventReader::run (this=0x21d7290) at
qxcbconnection.cpp:1343
#5  0x7f583921052c in QThreadPrivate::start (arg=0x21d7290) at
thread/qthread_unix.cpp:368
#6  0x7f5833773454 in start_thread (arg=0x7f5827218700) at
pthread_create.c:333
#7  0x7f58388a2f4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f581a8c6700 (LWP 19061)):
#0  0x7f5838899e6d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5831edc6fc in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f5814018e00, timeout=-1, context=0x7f5814000990) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f5814000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3924
#3  0x7f5831edc80c in g_main_context_iteration (context=0x7f5814000990,
may_block=may_block@entry=1) at
/var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990
#4  0x7f58393f36ab in QEventDispatcherGlib::processEvents
(this=0x7f58140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f58393a538a in QEventLoop::exec (this=this@entry=0x7f581a8c5d90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f583920c2e4 in QThread::exec (this=this@entry=0x7f583b4387c0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#7  0x7f583b3c4835 in QDBusConnectionManager::run (this=0x7f583b4387c0
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x7f583921052c in QThreadPrivate::start (arg=0x7f583b4387c0 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#9  0x7f5833773454 in start_thread (arg=0x7f581a8c6700) at
pthread_create.c:333
#10 0x7f58388a2f4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f57f3b9d700 (LWP 19066)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5839210b9a in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x86a5e70) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x869f7e8,
mutex=mutex@entry=0x869f7e0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f583920af7b in QSemaphore::acquire (this=this@entry=0x7f583710db50
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+16>,
n=n@entry=1) at thread/qsemaphore.cpp:143
#4  0x7f5836c2a50e in KisTileDataPooler::waitForWork (this=0x7f583710db40
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
/var/tmp/portage/media-gfx/krita-3.1.2-r2/work/krita-3.1.2.1/libs/image/tiles3/kis_tile_data_pooler.cc:165
#5  0x7f5836c2af12 in KisTileDataPooler::run (this=0x7f583710db40
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
/var/tmp/portage/media-gfx/krita-3.1.2-r2/work/krita-3.1.2.1/libs/image/tiles3/kis_tile_data_pooler.cc:187
#6  0x7f583921052c in QThreadPrivate::start (arg=0x7f583710db40 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#7  0x7f583

[kmail2] [Bug 381191] New: Suppressed folders are coming back

2017-06-14 Thread Michel

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

Bug ID: 381191
   Summary: Suppressed folders are coming back
   Product: kmail2
   Version: 5.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: dubois.mic...@gmail.com
  Target Milestone: ---

Hi, 


I suppressed some folder and they 're coming back after a stop/start of kmail
through kontact. 
I emptied them in putting the mails in the trash and the folders 're coming
back empty

Thank for your support.

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

[krita] [Bug 381190] Crash when clicking on "Color Space Browser" in "New" dialog

2017-06-14 Thread Boudewijn Rempt

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||b...@valdyas.org
 Ever confirmed|0   |1

--- Comment #1 from Boudewijn Rempt  ---
Hi Elias,

I guess I know why this is... You've probably built Krita without openexr. Let
me try to find a way to fix this.

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

[kmail2] [Bug 381192] New: The searches don't work

2017-06-14 Thread Michel

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

Bug ID: 381192
   Summary: The searches don't work
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: dubois.mic...@gmail.com
  Target Milestone: ---

Hi, 

I'm trying some search in kmail. The search still empty. The folder of the
search has been created but the search result still empty like the folder of
search.

Thank for your support.

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

[krita] [Bug 381190] Crash when clicking on "Color Space Browser" in "New" dialog

2017-06-14 Thread Boudewijn Rempt

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kri
   ||ta/ea1647b76e3a783fd3cdc650
   ||1353c38b881bb5c6
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Boudewijn Rempt  ---
Git commit ea1647b76e3a783fd3cdc6501353c38b881bb5c6 by Boudewijn Rempt.
Committed on 14/06/2017 at 07:56.
Pushed by rempt into branch 'master'.

Don't crash on TCXYY calculations if Krita was built without openexr

We cannot use F16 colorspaces unless we know krita has been built
with openexr, so use F32 instead, which is always present.

A  +4625 -0krita/data/symbols/pepper_carrot_speech_bubbles_backup.svg
M  +2-2libs/pigment/KoColorSpace.cpp

https://commits.kde.org/krita/ea1647b76e3a783fd3cdc6501353c38b881bb5c6

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

[krita] [Bug 381190] Crash when clicking on "Color Space Browser" in "New" dialog

2017-06-14 Thread Boudewijn Rempt

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/ea1647b76e3a783fd3cdc650 |ta/8bb19c8b0c1756a24a63d741
   |1353c38b881bb5c6|256d7294fcfcecec

--- Comment #3 from Boudewijn Rempt  ---
Git commit 8bb19c8b0c1756a24a63d741256d7294fcfcecec by Boudewijn Rempt.
Committed on 14/06/2017 at 07:56.
Pushed by rempt into branch 'krita/3.2'.

Don't crash on TCXYY calculations if Krita was built without openexr

We cannot use F16 colorspaces unless we know krita has been built
with openexr, so use F32 instead, which is always present.

M  +7-7libs/pigment/KoColorSpace.cpp

https://commits.kde.org/krita/8bb19c8b0c1756a24a63d741256d7294fcfcecec

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

[digikam] [Bug 381193] New: Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread Andrea Malfagia

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

Bug ID: 381193
   Summary: Digikam crashes after uploading photos from smartphone
via USB
   Product: digikam
   Version: 5.2.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: andrea.malfa...@poste.it
  Target Milestone: ---

Application: digikam (5.2.0)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.70-18.9-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
Whenever it ends to upload a selection of pictures from my Samsung Galaxy A5,
Digikam crashes with a segmentation fault. The problem has never occurred
before I upgraded my OS to openSUSE Leap 42.2

The crash can be reproduced every time.

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

Thread 18 (Thread 0x7f343589a700 (LWP 8521)):
#0  0x7f34b6e6f7b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f34b6e2def6 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f34b6e2e388 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f34b6e2e42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f34c05f932b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f34c05a6fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f34c3056eda in  () at /usr/lib64/libdigikamcore.so.5.2.0
#7  0x7f34c03e381e in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f34c03e69e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f34bc1e1744 in start_thread () at /lib64/libpthread.so.0
#10 0x7f34bfaddd3d in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f33dbfff700 (LWP 8520)):
#0  0x7f34bfad549d in poll () at /lib64/libc.so.6
#1  0x7f34b6e2e314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f34b6e2e42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f34c05f932b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f34c05a6fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f34c3056eda in  () at /usr/lib64/libdigikamcore.so.5.2.0
#6  0x7f34c03e381e in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f34c03e69e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f34bc1e1744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f34bfaddd3d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f33d1ffb700 (LWP 8519)):
[KCrash Handler]
#6  0x7f34ba30a3ee in  () at /usr/lib64/libjpeg.so.8
#7  0x7f34c3008d45 in  () at /usr/lib64/libdigikamcore.so.5.2.0
#8  0x7f34c3002c0b in
Digikam::JPEGUtils::JpegRotator::performJpegTransform(Digikam::MetaEngineRotation::TransformationAction,
QString const&, QString const&) () at /usr/lib64/libdigikamcore.so.5.2.0
#9  0x7f34c3006169 in
Digikam::JPEGUtils::JpegRotator::exifTransform(Digikam::MetaEngineRotation
const&) () at /usr/lib64/libdigikamcore.so.5.2.0
#10 0x7f34c3007b37 in
Digikam::JPEGUtils::JpegRotator::exifTransform(Digikam::MetaEngineRotation::TransformationAction)
() at /usr/lib64/libdigikamcore.so.5.2.0
#11 0x7f34c3ed8578 in  () at /usr/lib64/libdigikamgui.so.5.2.0
#12 0x7f34c3eda7f6 in  () at /usr/lib64/libdigikamgui.so.5.2.0
#13 0x7f34c05d4166 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#14 0x7f34c12afe3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#15 0x7f34c12b449a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#16 0x7f34c05a8fc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#17 0x7f34c05aadaa in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#18 0x7f34c05f9c83 in  () at /usr/lib64/libQt5Core.so.5
#19 0x7f34b6e2e134 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#20 0x7f34b6e2e388 in  () at /usr/lib64/libglib-2.0.so.0
#21 0x7f34b6e2e42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#22 0x7f34c05f930c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#23 0x7f34c05a6fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#24 0x7f34c3056eda in  () at /usr/lib64/libdigikamcore.so.5.2.0
#25 0x7f34c03e381e in  () at /usr/lib64/libQt5Core.so.5
#26 0x7f34c03e69e9 in  () at /usr/lib64/libQt5Core.so.5
#27 0x7f34bc1e1744 in start_thread () at /lib64/libpthread.so.0
#28 0x7f34bfaddd3d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f33d17fa700 (LWP 8518

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread bugzilla_noreply

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
It crash in libjpeg while JPEG lossless rotation.

2 possibilities :

- your JPEG files are corrupted
- your libjpeg depend of device acceleration which can be problematic.

The AppImage Linux bundles of 5.6.0 use a cleaned libjpeg (no hardware
support). Try with this version to see if problem disappear. The bundle is here
:

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread bugzilla_noreply

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

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

   What|Removed |Added

  Component|general |Import-PostProcessing

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

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread Andrea Malfagia

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

--- Comment #2 from Andrea Malfagia  ---
(In reply to caulier.gilles from comment #1)
> It crash in libjpeg while JPEG lossless rotation.
> 
> 2 possibilities :
> 
> - your JPEG files are corrupted
> - your libjpeg depend of device acceleration which can be problematic.
> 
> The AppImage Linux bundles of 5.6.0 use a cleaned libjpeg (no hardware
> support). Try with this version to see if problem disappear.

The first possibility of course is out of question, so I am going to try Your
suggestion. News to follow as soon as I am done with it, meanwhile thanks in
advance for Your help.

Andrea Malfagia

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

[kmail2] [Bug 381194] New: KMail not detecting HTML mails

2017-06-14 Thread bugzilla_noreply

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

Bug ID: 381194
   Summary: KMail not detecting HTML mails
   Product: kmail2
   Version: Git (master)
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: johan.claudebreunin...@gmail.com
  Target Milestone: ---

KMail is not always showing the security warning to display HTML messages even
the mail is in the HTML format.

The side bar considers the mail as "raw text" even if it is HTML. 

Workaround: select "Prefer HTML over raw text" in Security settings.

KMail 5.5.2

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

[kmail2] [Bug 381194] KMail not detecting HTML mails

2017-06-14 Thread bugzilla_noreply

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

johan.claudebreunin...@gmail.com changed:

   What|Removed |Added

 CC||johan.claudebreuninger@gmai
   ||l.com

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

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread Andrea Malfagia

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

--- Comment #3 from Andrea Malfagia  ---
(In reply to caulier.gilles from comment #1)

> The AppImage Linux bundles of 5.6.0 use a cleaned libjpeg (no hardware
> support). Try with this version to see if problem disappear. The bundle is
> here :
> 
> https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Mmm... unable to try it: after chmod'ing the file, I launch it from a console
window as normal user, saying 'no' to its request to integrate into the system,
but it crashes reporting the following info:

digikam.dbengine: Loading SQL code from config file
"/tmp/.mount_lbQAzD/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  8
digikam.coredb: Core database: makeUpdates  8  to  8
digikam.database: Creating new Location  "//Immagini"  uuid 
"volumeid:?uuid=e58d799f-350f-4f3b-966d-1a51e265eefd"
digikam.database: location for  "/home/malfa/Immagini"  is available  true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  12525010944
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.general: Switch to widget style:  ""
/tmp/.mount_lbQAzD/AppRun: riga 73: 10732 Errore di segmentazione (core dump
creato) digikam.wrapper $@

(I replaced my real username with )

Maybe I am misusing it?

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

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread bugzilla_noreply

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

--- Comment #4 from caulier.gil...@gmail.com ---
I'm curious. it do not crash here.

Run the bundle with "debug" arguments to see where it crash in application.

Gilles Caulier

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

[kmail2] [Bug 381192] The searches don't work

2017-06-14 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

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

--- Comment #1 from Laurent Montel  ---
5.1.3 is very old.
We fixed a lot of bugs in new version
see 5.5.x.
Regards

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

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread Andrea Malfagia

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

--- Comment #5 from Andrea Malfagia  ---
(In reply to caulier.gilles from comment #4)

> Run the bundle with "debug" arguments to see where it crash in application.

Not sure if this is the right way to provide info or should I somehow send an
attachment, anyway here is the output:

./digikam-5.6.0-01-x86-64.appimage debug


-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (GDB; openSUSE Leap 42.2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...done.
Catchpoint 1 (throw)
Starting program: /tmp/.mount_0mrfuL/usr/bin/digikam 
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libspeex.so.1
Try: zypper install -C
"debuginfo(build-id)=85c7557bade689f2a5109482efad8980d3d948ac"
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/liblcms2.so.2
Try: zypper install -C
"debuginfo(build-id)=ab54400a4129c25f69840acbd87a7e6e853ad8d5"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libgomp.so.1
Try: zypper install -C
"debuginfo(build-id)=a27b5f0e1a8e1bc0d98926e6e7336f0d0d17c2bf"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libXext.so.6
Try: zypper install -C
"debuginfo(build-id)=e269a5a1c9f02085d7cd11f8ede0e87f4aa5f265"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libexslt.so.0
Try: zypper install -C
"debuginfo(build-id)=e872b897b755d1f146ba15f86570e27299106bd2"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libxslt.so.1
Try: zypper install -C
"debuginfo(build-id)=2c2c33a9d51d2068ef6674489e7cffb61776ef17"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libxml2.so.2
Try: zypper install -C
"debuginfo(build-id)=4612da142a0ed2e070482534e6a5b086639b5a52"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libGLU.so.1
Try: zypper install -C
"debuginfo(build-id)=8568525eeaf35aeb364bc70d5cfcac12a9bc9199"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/liblzma.so.0
Try: zypper install -C
"debuginfo(build-id)=2f1f98636d83908f9157858bcc7b44a6a6784385"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libgcrypt.so.11
Try: zypper install -C
"debuginfo(build-id)=57781f018acbd399e29ed7b9c4e265a9c301"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libswresample.so.1
Try: zypper install -C
"debuginfo(build-id)=dac89d297bb6ff3aaeeb41af3943501e8864d385"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libavresample.so.2
Try: zypper install -C
"debuginfo(build-id)=0d3b65f4c0e7270d2da8e5605ac649eed4cff7a6"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libavdevice.so.56
Try: zypper install -C
"debuginfo(build-id)=ac00e8e9ccb05dad95bf0b1def4e30ac61bfef08"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libavfilter.so.5
Try: zypper install -C
"debuginfo(build-id)=ad00758ac0580aba838311de8a1b8ecee8ea019f"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libavcodec.so.56
Try: zypper install -C
"debuginfo(build-id)=50ae05c0ad74f47f96172fd04d1a8f120a2d8c13"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libavformat.so.56
Try: zypper install -C
"debuginfo(build-id)=0352346bfde4ff1eef7635bbbfd010e0afba766e"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libswscale.so.3
Try: zypper install -C
"debuginfo(build-id)=43cfa7e67922a11b496d969e4c201331bdd634fc"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libavutil.so.54
Try: zypper install -C
"debuginfo(build-id)=c102cc8f73e83e693b6d489a3d4fbcadebfba0e7"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libsqlite3.so.0
Try: zypper install -C
"debuginfo(build-id)=0e42624ae755ada258f06a9c5fe23480c7068ce1"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libXrender.so.1
Try: zypper install -C
"debuginfo(build-id)=771256bb92a7dfe45aa4203e92c5fdcf9a8bf6e3"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libicui18n.so.42
Try: zypper install -C
"debuginfo(build-id)=488accd4122387506f60edcbb166542e5ad442dc"
Missing separate debuginfo for /tmp/.mount_0mrfuL/usr/lib/libicuuc.so.42
Try: zypper install -C
"debuginfo(build-id)=b3ce

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread bugzilla_noreply

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

--- Comment #6 from caulier.gil...@gmail.com ---
This is really strange. It crash in libc. This is the only component from the
system that we use in the bundle. libc is not integrated in the bundle.

Did you have anither Linux system avaiable to test. I suspect a dysfunction
from your openSuse (perhaps a wrong update).

Gilles Caulier

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

[krita] [Bug 381189] Bezier curves do not properly save as previewed on the editor

2017-06-14 Thread Boudewijn Rempt

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|Beizer curves do not|Bezier curves do not
   |properly save as previewed  |properly save as previewed
   |on the editor   |on the editor
 CC||b...@valdyas.org

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

[krita] [Bug 381189] Bezier curves do not properly save as previewed on the editor

2017-06-14 Thread Boudewijn Rempt

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

Boudewijn Rempt  changed:

   What|Removed |Added

   Platform|Other   |MS Windows

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

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

2017-06-14 Thread Andrea Malfagia

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

--- Comment #7 from Andrea Malfagia  ---
(In reply to caulier.gilles from comment #6)
> This is really strange. It crash in libc. This is the only component from
> the system that we use in the bundle. libc is not integrated in the bundle.
> 
> Did you have anither Linux system avaiable to test. I suspect a dysfunction
> from your openSuse (perhaps a wrong update).

*GASP!* Unfortunately not, I have only this openSUSE on my notebook. What kind
of checks could I perform on this library? The current versions comes from
glibc v. 2.22-4.6.3 distribution-specific package :-/

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

[skrooge] [Bug 381168] Change tab order of properties editor

2017-06-14 Thread Stephane MANKOWSKI

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/skr
   ||ooge/4f181df968109113c1d2eb
   ||e88bc37586cb6f262f
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #1 from Stephane MANKOWSKI  ---
Git commit 4f181df968109113c1d2ebe88bc37586cb6f262f by Stephane Mankowski.
Committed on 14/06/2017 at 10:10.
Pushed by smankowski into branch 'master'.

Change tab order of properties editor

M  +1-0CHANGELOG
M  +2-2   
plugins/generic/skg_properties/skgpropertiesplugindockwidget_base.ui

https://commits.kde.org/skrooge/4f181df968109113c1d2ebe88bc37586cb6f262f

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

[plasmashell] [Bug 381195] New: Plasma crash after volume up/down

2017-06-14 Thread Kubilay KOCABALKAN

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

Bug ID: 381195
   Summary: Plasma crash after volume up/down
   Product: plasmashell
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: hkubil...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.4-1-ARCH x86_64
Distribution: "Arch Linux"

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

When i was conneting bluetooth headset and plasma crash after volume up or
down,

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

Thread 12 (Thread 0x7efcc3d37700 (LWP 6621)):
#0  0x7efdcc13ca44 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7efdcc0f7128 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7efdcc0f7b2b in  () at /usr/lib/libglib-2.0.so.0
#3  0x7efdcc0f7d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7efdd1e64e9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7efdd1e0b21a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7efdd1c2d40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7efdd4d9c645 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7efdd1c31cbd in  () at /usr/lib/libQt5Core.so.5
#9  0x7efdd0dfa297 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7efdd154625f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7efcc21a8700 (LWP 6599)):
#0  0x7efdd153c2bd in poll () at /usr/lib/libc.so.6
#1  0x7efdcc0f7bf9 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7efdcc0f7d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7efdd1e64e9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7efdd1e0b21a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7efdd1c2d40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7efdd4d9c645 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7efdd1c31cbd in  () at /usr/lib/libQt5Core.so.5
#8  0x7efdd0dfa297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7efdd154625f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7efce6a56700 (LWP 6593)):
#0  0x7efdd153802d in read () at /usr/lib/libc.so.6
#1  0x7efdc5853f51 in pa_read () at
/usr/lib/pulseaudio/libpulsecommon-10.0.so
#2  0x7efdc5ee430e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0
#3  0x7efdc5ee4d80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7efdc5ee4e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7efdc5ef2e29 in  () at /usr/lib/libpulse.so.0
#6  0x7efdc5882fe8 in  () at /usr/lib/pulseaudio/libpulsecommon-10.0.so
#7  0x7efdd0dfa297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7efdd154625f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7efd1aace700 (LWP 1550)):
#0  0x7efdcc13ca29 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7efdcc0f6a80 in g_main_context_acquire () at
/usr/lib/libglib-2.0.so.0
#2  0x7efdcc0f7ab5 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7efdcc0f7d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7efdd1e64e9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7efdd1e0b21a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7efdd1c2d40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7efce9b5b427 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#8  0x7efdd1c31cbd in  () at /usr/lib/libQt5Core.so.5
#9  0x7efdd0dfa297 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7efdd154625f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7efcf77f8700 (LWP 1514)):
#0  0x7efdd153c2bd in poll () at /usr/lib/libc.so.6
#1  0x7efdcc0f7bf9 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7efdcc0f7d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7efdd1e64e9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7efdd1e0b21a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7efdd1c2d40a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7efdd1c31cbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7efdd0dfa297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7efdd154625f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7efda7dea700 (LWP 1268)):
#0  0x7efdd0e0039d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#

[Breeze] [Bug 381196] New: Make notification popup have rounded corners

2017-06-14 Thread Michael D

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

Bug ID: 381196
   Summary: Make notification popup have rounded corners
   Product: Breeze
   Version: 5.10.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: nortex...@gmail.com
  Target Milestone: ---

This is just a wish for an aesthetic improvement, but given that the window
decoration, buttons, and similar elements all have rounded corners, the
squared-off notification pop-ups look out of place (and uglier, to my eye).
Would be nice to round them as much as e.g. the window decorations.

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

[kmail2] [Bug 380933] Find messages results in no results

2017-06-14 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||mon...@kde.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Laurent Montel  ---
Please test in last version 5.2.x is very old. Last version is 5.5.2

Thanks

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

[frameworks-baloo] [Bug 364042] balooctl status and balooshow always report "Baloo Index could not be opened"

2017-06-14 Thread Nick Cross

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

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[kmail2] [Bug 380297] Recipients counter miscounts number of message recipients

2017-06-14 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
I confirm it.
I will fix it soon.

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

[frameworks-baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays

2017-06-14 Thread Nick Cross

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

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar

2017-06-14 Thread David Faure

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

--- Comment #17 from David Faure  ---
Alex6: please remain constructive, I'm offering to spend some of my *free* time
recreating the most needed features. Nobody destroyed anything intentionally,
the old sidebar was based on Qt3Support which doesn't exist in Qt5, so it had
to be rewritten no matter what, with the Qt5 port. I'm just offering to take a
step back and think about the best new way to offer these features, rather than
just blindly recreating the old sidebar "as is".

David Rosenstrauch: if the folder tree was the only feature you're missing,
Dolphin would do the job, right?

avlas: thanks, that's useful feedback.

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

[plasmashell] [Bug 381197] New: Plasma shell stops updating the panel

2017-06-14 Thread Paul de Vrieze

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

Bug ID: 381197
   Summary: Plasma shell stops updating the panel
   Product: plasmashell
   Version: 5.10.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: paul.devri...@gmail.com
  Target Milestone: 1.0

For the last number of major releases plasma shell "randomly" stops updating
the state of its plasmoids in the panel (the clock stops, load viewer (if
enabled) stops, the task list doesn't update). The system is still responsive
to user input, so clicking on an application in the task section of the panel
does open (or bring forward) a window, but not the correct window. The alt-tab
task switcher works correctly and lists all windows.

Manually killing/restarting plasmashell fixes the problem temporarily, but it
comes up again soon. The issue is much more likely to occur on high system
load, even when system monitor is not included. It looks like some sort of race
condition.

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

[ksysguard] [Bug 381198] New: show combined memory usage when in tree view for e.g. Google chrome

2017-06-14 Thread Pascal d'Hermilly

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

Bug ID: 381198
   Summary: show combined memory usage when in tree view for e.g.
Google chrome
   Product: ksysguard
   Version: 5.10.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: pas...@dhermilly.dk
  Target Milestone: ---

It would be nice too see how much memory for example Google Chrome uses.
right now it's not possible due to being spread on many processes.

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

[kwin] [Bug 380476] Kwin draws 1px overlay on the left screen border

2017-06-14 Thread bugzilla_noreply

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

--- Comment #16 from gr...@sub.red ---
(In reply to Christoph Feck from comment #10)
> According to bug 380492, it is possible to workaround this by disabling the
> left-edge touchscreen action.

Thanks, can confirm it does help.

Bad defaults then

(In reply to Martin Flöser from comment #14)
> Technically this is not a regression. This behavior has been present for as
> long as screenedges exist and hardly any bug got reported for it. As soon as
> one has a screenedge configured for an edge it takes away one pixel.

kwin should differentiate between pointer and touch input, also IMHO the
default should not take away one screen edge from every user when the vast
majority doesn't even have a touchscreen.

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

[Breeze] [Bug 381196] Make notification popup have rounded corners

2017-06-14 Thread Kai Uwe Broulik

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de
 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Kai Uwe Broulik  ---
The corners, at least the shadow, is slightly rounded, no? Feel free to use a
different Plasma theme, there are plenty of options to download from the
internet.

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

[dolphin] [Bug 381187] Please add Miller Columns back to Dolphin

2017-06-14 Thread Christoph Feck

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

--- Comment #1 from Christoph Feck  ---
Already reported as bug 377825, bug 336563, bug 335479, bug 333744.

Somehow I feel we should keep one of them open to get people to understand that
the code that was removed cannot just be added back.

The new view infrastructure is just not capable of column views, and without a
major rewrite, which I estimate to be bigger than any GSoC student would be
able to handle as a project, they cannot come back.

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

[kmail2] [Bug 380297] Recipients counter miscounts number of message recipients

2017-06-14 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.5.3
  Latest Commit||https://commits.kde.org/mes
   ||sagelib/a6536bca179aa8052de
   ||973e5563de04f9dc07581

--- Comment #2 from Laurent Montel  ---
Git commit a6536bca179aa8052de973e5563de04f9dc07581 by Montel Laurent.
Committed on 14/06/2017 at 11:56.
Pushed by mlaurent into branch 'Applications/17.04'.

Fix Bug 380297 - Recipients counter miscounts number of message recipients

FIXED-IN: 5.5.3

M  +1-0messagecomposer/src/recipient/recipientline.cpp
M  +11   -5messagecomposer/src/recipient/recipientseditor.cpp

https://commits.kde.org/messagelib/a6536bca179aa8052de973e5563de04f9dc07581

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

[kmail2] [Bug 379467] Display "Date:" header in sender's local timezone

2017-06-14 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
which is your kmail version ?

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

[okular] [Bug 186531] [JJ] Trim Margin doesn't work if paper color was set

2017-06-14 Thread Nikolaos Kakouros

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

--- Comment #22 from Nikolaos Kakouros  ---
Yes, you are right. After changing the page color setting I had to restart to
trigger the bug.

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

[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner

2017-06-14 Thread Nishant Elkunchwar

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

Nishant Elkunchwar  changed:

   What|Removed |Added

 CC||nishant.elkunch...@gmail.co
   ||m

--- Comment #5 from Nishant Elkunchwar  ---
Facing this issue as well since updating to KDE frameworks 5.35. I am on KDE
neon user edition (non-LTS).

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

[kmail2] [Bug 378985] KMail 5.4.3: Save all attachements -> no attachments found

2017-06-14 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Can we have a test case ?

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

[kmail2] [Bug 378439] KMail - search is "one-shot" only

2017-06-14 Thread Laurent Montel

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

Laurent Montel  changed:

   What|Removed |Added

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

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

[kmail2] [Bug 380855] kmail crashes with signal 11 on logout

2017-06-14 Thread bugzilla_noreply

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

johan.claudebreunin...@gmail.com changed:

   What|Removed |Added

 CC||johan.claudebreuninger@gmai
   ||l.com

--- Comment #3 from johan.claudebreunin...@gmail.com ---
I can confirm this bug.

KMail 5.5.2

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

[Powerdevil] [Bug 381199] New: Broken brightness control with kernel module (ex. nvidia-bl)

2017-06-14 Thread bugzilla_noreply

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

Bug ID: 381199
   Summary: Broken brightness control with kernel module (ex.
nvidia-bl)
   Product: Powerdevil
   Version: 5.10.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: vsnrain@gmail.com
  Target Milestone: ---

Overview:
Since 5.10, it is no longer possible to adjust brightness on my system, which
requires special kernel module for brightness to work. I tried to look at what
caused this, and found that in following commit 
https://cgit.kde.org/powerdevil.git/commit/?id=86c3548d103ff5966366788220796de629be9230
Was attempt to add feature that powerdevil will control only brightness of
active device. Part of relevant code is following:

/daemon/backends/upower/backlighthelper.cpp
bool BacklightHelper::isRawBacklightEnabled(const QString &interface)
{
QFile file(BACKLIGHT_SYSFS_PATH + interface + "/device/enabled");

if (!file.open(QIODevice::ReadOnly | QIODevice::Text)) {
return false;
}

QByteArray buffer = file.readLine().trimmed();
if (buffer == "enabled") {
return true;
   }

return false;
}

As you can see, it was implemented by skipping all brightness devices which in
BACKLIGHT_SYSFS_PATH + interface + "/device/enabled" does not return "enabled".
The problem is, there is no property "device/enabled" in my nvidia_backlight
device:

ls -la /sys/class/backlight/nvidia_backlight/  
total 0
drwxr-xr-x 3 root root0 Jun  2 22:50 .
drwxr-xr-x 3 root root0 Jun  2 22:50 ..
-r--r--r-- 1 root root 4096 Jun  2 23:02 actual_brightness
-rw-r--r-- 1 root root 4096 Jun  2 23:02 bl_power
-rw-r--r-- 1 root root 4096 Jun  2 22:54 brightness
-r--r--r-- 1 root root 4096 Jun  2 22:50 max_brightness
drwxr-xr-x 2 root root0 Jun  2 23:02 power
lrwxrwxrwx 1 root root0 Jun  2 22:50 subsystem ->
../../../../class/backlight
-r--r--r-- 1 root root 4096 Jun  2 22:50 type
-rw-r--r-- 1 root root 4096 Jun  2 22:50 uevent

so powerdevil tries to open this file, fails, and always skips this brightness
device. I recompiled powerdevil with "return true" in mentioned function, and
brightness control works again, so it seems that problem in indeed in this
part.

Steps to Reproduce:
use kernel module for brightness device, tested on Nvidia GF 9400M with
nvidia-bl kernel module.

Actual Results:
powerdevil always skips brightness device, because it cannot open file
/sys/class/backlight/nvidia_backlight/device/enabled, which does not exist.

Expected Results:
register and control brightness device.

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

[kinfocenter] [Bug 381200] New: KInfoCenter crashes on exit after viewing Energy Information

2017-06-14 Thread Shashwat

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

Bug ID: 381200
   Summary: KInfoCenter crashes on exit after viewing Energy
Information
   Product: kinfocenter
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: hubn...@gmail.com
  Reporter: shashtheas...@gmail.com
  Target Milestone: ---

Application: kinfocenter (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-80-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Viewed the energy information in KInfoCenter and then exited the app. While I
was viewing the energy information, the graphs seemed to be incorrectly
displayed.

-- Backtrace:
Application: KDE Info Center (kinfocenter), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f281bcda900 (LWP 3056))]

Thread 14 (Thread 0x7f26a106f700 (LWP 3107)):
#0  0x7f2818f0569d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2812178f55 in ?? () from
/usr/lib/nvidia-340/tls/libnvidia-tls.so.340.102
#2  0x7f2815bf86f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2815bb4e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2815bb5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f2815bb549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f28198367eb in QEventDispatcherGlib::processEvents
(this=0x7f26940fd010, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7f28197ddb4a in QEventLoop::exec (this=this@entry=0x7f26a106eca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7f28195fa834 in QThread::exec (this=this@entry=0x2d8a110) at
thread/qthread.cpp:503
#9  0x7f28186dd3c5 in QQmlThreadPrivate::run (this=0x2d8a110) at
qml/ftw/qqmlthread.cpp:141
#10 0x7f28195ff7be in QThreadPrivate::start (arg=0x2d8a110) at
thread/qthread_unix.cpp:331
#11 0x7f28165f56ba in start_thread (arg=0x7f26a106f700) at
pthread_create.c:333
#12 0x7f2818f1582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f26a1d89700 (LWP 3106)):
#0  __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65
#1  0x7f2818f09b52 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f2815bb538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2815bb549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f28198367eb in QEventDispatcherGlib::processEvents
(this=0x7f269c003660, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f28197ddb4a in QEventLoop::exec (this=this@entry=0x7f26a1d88ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f28195fa834 in QThread::exec (this=this@entry=0x27f4d90) at
thread/qthread.cpp:503
#7  0x7f28186dd3c5 in QQmlThreadPrivate::run (this=0x27f4d90) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f28195ff7be in QThreadPrivate::start (arg=0x27f4d90) at
thread/qthread_unix.cpp:331
#9  0x7f28165f56ba in start_thread (arg=0x7f26a1d89700) at
pthread_create.c:333
#10 0x7f2818f1582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f26aa6ca700 (LWP 3076)):
#0  0x7f2818f09b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2815bb538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2815bb549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f28198367eb in QEventDispatcherGlib::processEvents
(this=0x7f26a4102f80, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f28197ddb4a in QEventLoop::exec (this=this@entry=0x7f26aa6c9ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f28195fa834 in QThread::exec (this=this@entry=0x26ff5b0) at
thread/qthread.cpp:503
#6  0x7f28186dd3c5 in QQmlThreadPrivate::run (this=0x26ff5b0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f28195ff7be in QThreadPrivate::start (arg=0x26ff5b0) at
thread/qthread_unix.cpp:331
#8  0x7f28165f56ba in start_thread (arg=0x7f26aa6ca700) at
pthread_create.c:333
#9  0x7f2818f1582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f27ebdf9700 (LWP 3074)):
#0  0x7f2818f0569d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2812178f55 in ?? () from
/usr/lib/nvidia-340/tls/libnvidia-tls.so.340.102
#2  0x7f2815bf86f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2815bb4e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2815bb5330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f2815bb549c in g_m

[Powerdevil] [Bug 381199] Broken brightness control with kernel module (ex. nvidia-bl)

2017-06-14 Thread Bhushan Shah

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

Bhushan Shah  changed:

   What|Removed |Added

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

--- Comment #1 from Bhushan Shah  ---
though This is done only for raw backlight type devices..

What is the backlight type for your device?

cat /sys/class/backlight/nvidia_backlight/type

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

[Powerdevil] [Bug 381199] Broken brightness control with kernel module (ex. nvidia-bl)

2017-06-14 Thread bugzilla_noreply

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

--- Comment #2 from vsnrain@gmail.com ---
it returns "raw"

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

[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar

2017-06-14 Thread avlas

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

--- Comment #18 from avlas  ---
(In reply to David Faure from comment #17)
> Alex6: please remain constructive, I'm offering to spend some of my *free*
> time recreating the most needed features. Nobody destroyed anything
> intentionally, the old sidebar was based on Qt3Support which doesn't exist
> in Qt5, so it had to be rewritten no matter what, with the Qt5 port. I'm
> just offering to take a step back and think about the best new way to offer
> these features, rather than just blindly recreating the old sidebar "as is".
> 
> David Rosenstrauch: if the folder tree was the only feature you're missing,
> Dolphin would do the job, right?
> 
> avlas: thanks, that's useful feedback.

Thanks to you for willing to port the sidebar in the best way possible to Qt5.
It's very much appreciated :)

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

[kmail2] [Bug 379467] Display "Date:" header in sender's local timezone

2017-06-14 Thread Juri Vitali

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

--- Comment #2 from Juri Vitali  ---
I'm using the latest version on Arch Linux repositories. Currently it is at
5.5.2, but it was the same on previous versions too.

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

[plasmashell] [Bug 381201] New: plasma crashed after search any programm

2017-06-14 Thread bugzilla_noreply

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

Bug ID: 381201
   Summary: plasma crashed after search any programm
   Product: plasmashell
   Version: 5.10.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: hess2...@ukr.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.1)

Qt Version: 5.7.1
Frameworks Version: 5.35.0
Operating System: Linux 4.10.0-22-generic x86_64
Distribution: Ubuntu Artful Aardvark (development branch)

-- Information about the crash:
When I type the name of the program in the start -> search, the plasma is
cashed

The crash can be reproduced every time.

-- 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 0x7fc0b25298c0 (LWP 1658))]

Thread 20 (Thread 0x7fbf96ffd700 (LWP 3241)):
[KCrash Handler]
#6  0x7fc0ac154c0a in __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:301
#7  0x7fbfc0188564 in  () at
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x7fbfc01730ce in  () at
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x7fbfc0173191 in Baloo::PostingDB::iter(QByteArray const&) () at
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x7fbfc017dbba in
Baloo::Transaction::postingIterator(Baloo::EngineQuery const&) const () at
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x7fbfc05d5640 in  () at /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#12 0x7fbfc05d58ba in  () at /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#13 0x7fbfc05d69a7 in  () at /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#14 0x7fbfc05c4fd6 in Baloo::Query::exec() () at
/usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#15 0x7fbfc07e64de in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#16 0x7fbfc07e73c9 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#17 0x7fbff1072538 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5
#18 0x7fbff0596bf8 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#19 0x7fbff0595630 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#20 0x7fbff05951d0 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#21 0x7fc0ac802c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7fc0ab6a36da in start_thread (arg=0x7fbf96ffd700) at
pthread_create.c:456
#23 0x7fc0ac10d17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 19 (Thread 0x7fbf977fe700 (LWP 3240)):
#0  0x7fc0ab6a9510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc0ac803b4b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fbff0593240 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7fbff0597478 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fbff05923bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fbff05974d2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fbff05923bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fbff0595289 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fc0ac802c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fc0ab6a36da in start_thread (arg=0x7fbf977fe700) at
pthread_create.c:456
#10 0x7fc0ac10d17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 18 (Thread 0x7fbf97fff700 (LWP 3239)):
#0  0x7fc0ab6a9510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc0ac803b4b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fbff0593240 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7fbff0597478 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fbf

[plasmashell] [Bug 381202] New: Plasma crashed on Opensuse 42.2 when wine is setuping GOG Game

2017-06-14 Thread KMN

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

Bug ID: 381202
   Summary: Plasma crashed on Opensuse 42.2 when wine is setuping
GOG Game
   Product: plasmashell
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kino1...@mail.ru
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

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

-- Information about the crash:
- What I was doing when the application crashed:
I was setuping King's Bounty - Warriors of the North fropm the GOG with Wine
2.10.

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

Thread 8 (Thread 0x7f72eb7ec700 (LWP 20339)):
#0  0x7f73ac07c7d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f73ac03ad99 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f73ac03b2a8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f73ac03b42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f73b028032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f73b022dfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f73b0068f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f72ecc148f7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#8  0x7f73b006d9e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f73af17c744 in start_thread () at /lib64/libpthread.so.0
#10 0x7f73af97bd3d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f72fe51b700 (LWP 20211)):
#0  0x7f73ac03a903 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f73ac03b230 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f73ac03b42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f73b028032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f73b022dfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f73b0068f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f73b3ef8632 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7f73b006d9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f73af17c744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f73af97bd3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f7394c08700 (LWP 20159)):
#0  0x7f73af1810bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f73b5b3f93b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f73b5b3f969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f73af17c744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f73af97bd3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f7396a17700 (LWP 20154)):
#0  0x7f73ac07c7d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f73ac03ad4b in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f73ac03b2a8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f73ac03b42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f73b028032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f73b022dfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f73b0068f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f73b33759c8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f73b006d9e9 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f73af17c744 in start_thread () at /lib64/libpthread.so.0
#10 0x7f73af97bd3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f7397fff700 (LWP 20079)):
#0  0x7f73af96f51d in read () at /lib64/libc.so.6
#1  0x7f73ac07b670 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f73ac03ae49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f73ac03b2a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f73ac03b42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f73b028032b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f73b022dfdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f73b0068f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f73b33759c8 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f73b006d9e9 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f73af17c744 in start_thread () at /lib64/libpthread.so.0
#11 0x7f73af97bd3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f739df4c700 (LWP 20074)):
#0  0x7f73af97349d in poll () at /lib64/libc.s

[calligrawords] [Bug 380228] Calligra Word Crash with large file

2017-06-14 Thread Dag Andersen

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

Dag Andersen  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Dag Andersen  ---
Reported as QTBUG-61416.

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

[Powerdevil] [Bug 381114] Can't control brightness

2017-06-14 Thread Bhushan Shah

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

Bhushan Shah  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/pow
   ||erdevil/97f3900049aa657be5f
   ||4c124c9f992120f124944

--- Comment #6 from Bhushan Shah  ---
Git commit 97f3900049aa657be5f4c124c9f992120f124944 by Bhushan Shah.
Committed on 14/06/2017 at 12:55.
Pushed by bshah into branch 'master'.

Revert "skip the disabled backlight device"

This reverts commits 86c3548d103ff5966366788220796de629be9230 and
5c0d35ca6caf7bb0a0e9897a1a868e8406f3b112.

Not all raw interfaces have device/enabled under the backlight sysfs
interface. Some examples are nvidia-bl and acpi_video0, they are raw
interfaces but doesn't have device/enabled properties.

Overall we can just return true even if file doesn't exist but then this
code serves no purpose.
Related: bug 381199

Ackd-by: Kai Uwe Broulik 
CCMAIL: AceLan Kao 

M  +1-19   daemon/backends/upower/backlighthelper.cpp
M  +0-5daemon/backends/upower/backlighthelper.h

https://commits.kde.org/powerdevil/97f3900049aa657be5f4c124c9f992120f124944

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

[Powerdevil] [Bug 381199] Broken brightness control with kernel module (ex. nvidia-bl)

2017-06-14 Thread Bhushan Shah

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

Bhushan Shah  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/pow
   ||erdevil/97f3900049aa657be5f
   ||4c124c9f992120f124944

--- Comment #3 from Bhushan Shah  ---
Git commit 97f3900049aa657be5f4c124c9f992120f124944 by Bhushan Shah.
Committed on 14/06/2017 at 12:55.
Pushed by bshah into branch 'master'.

Revert "skip the disabled backlight device"

This reverts commits 86c3548d103ff5966366788220796de629be9230 and
5c0d35ca6caf7bb0a0e9897a1a868e8406f3b112.

Not all raw interfaces have device/enabled under the backlight sysfs
interface. Some examples are nvidia-bl and acpi_video0, they are raw
interfaces but doesn't have device/enabled properties.

Overall we can just return true even if file doesn't exist but then this
code serves no purpose.
Related: bug 381114

Ackd-by: Kai Uwe Broulik 
CCMAIL: AceLan Kao 

M  +1-19   daemon/backends/upower/backlighthelper.cpp
M  +0-5daemon/backends/upower/backlighthelper.h

https://commits.kde.org/powerdevil/97f3900049aa657be5f4c124c9f992120f124944

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

[kmail2] [Bug 378985] KMail 5.4.3: Save all attachements -> no attachments found

2017-06-14 Thread Axel Braun

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

--- Comment #2 from Axel Braun  ---
I will send you a PM

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

[Powerdevil] [Bug 381114] Can't control brightness

2017-06-14 Thread Bhushan Shah

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

Bhushan Shah  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/pow |https://commits.kde.org/pow
   |erdevil/97f3900049aa657be5f |erdevil/5c57cf64b5e5c880b1a
   |4c124c9f992120f124944   |5f3a0177293f6958e1b9a

--- Comment #7 from Bhushan Shah  ---
Git commit 5c57cf64b5e5c880b1a5f3a0177293f6958e1b9a by Bhushan Shah.
Committed on 14/06/2017 at 13:04.
Pushed by bshah into branch 'Plasma/5.10'.

Revert "skip the disabled backlight device"

This reverts commits 86c3548d103ff5966366788220796de629be9230 and
5c0d35ca6caf7bb0a0e9897a1a868e8406f3b112.

Not all raw interfaces have device/enabled under the backlight sysfs
interface. Some examples are nvidia-bl and acpi_video0, they are raw
interfaces but doesn't have device/enabled properties.

Overall we can just return true even if file doesn't exist but then this
code serves no purpose.
Related: bug 381199

Ackd-by: Kai Uwe Broulik 
CCMAIL: AceLan Kao 

M  +1-19   daemon/backends/upower/backlighthelper.cpp
M  +0-5daemon/backends/upower/backlighthelper.h

https://commits.kde.org/powerdevil/5c57cf64b5e5c880b1a5f3a0177293f6958e1b9a

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

[Powerdevil] [Bug 381199] Broken brightness control with kernel module (ex. nvidia-bl)

2017-06-14 Thread Bhushan Shah

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

Bhushan Shah  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/pow |https://commits.kde.org/pow
   |erdevil/97f3900049aa657be5f |erdevil/5c57cf64b5e5c880b1a
   |4c124c9f992120f124944   |5f3a0177293f6958e1b9a

--- Comment #4 from Bhushan Shah  ---
Git commit 5c57cf64b5e5c880b1a5f3a0177293f6958e1b9a by Bhushan Shah.
Committed on 14/06/2017 at 13:04.
Pushed by bshah into branch 'Plasma/5.10'.

Revert "skip the disabled backlight device"

This reverts commits 86c3548d103ff5966366788220796de629be9230 and
5c0d35ca6caf7bb0a0e9897a1a868e8406f3b112.

Not all raw interfaces have device/enabled under the backlight sysfs
interface. Some examples are nvidia-bl and acpi_video0, they are raw
interfaces but doesn't have device/enabled properties.

Overall we can just return true even if file doesn't exist but then this
code serves no purpose.
Related: bug 381114

Ackd-by: Kai Uwe Broulik 
CCMAIL: AceLan Kao 

M  +1-19   daemon/backends/upower/backlighthelper.cpp
M  +0-5daemon/backends/upower/backlighthelper.h

https://commits.kde.org/powerdevil/5c57cf64b5e5c880b1a5f3a0177293f6958e1b9a

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

[kalarm] [Bug 351253] KAlarm does not go to system tray and closing the window ends its process.

2017-06-14 Thread rusconi

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

--- Comment #7 from rusconi  ---
Version 2.11.7-5ak
This bug seems to not show up anymore. For me, you can close it.
Thank you for this useful program.

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

[konsole] [Bug 351242] cannot type accented characters like é à è

2017-06-14 Thread rusconi

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

--- Comment #1 from rusconi  ---
Version 16.12.0

For me this bug seems to have gone away. 
You can close it.
Thank you for this useful program.

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

[Breeze] [Bug 381196] Make notification popup have rounded corners

2017-06-14 Thread Michael D

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

--- Comment #2 from Michael D  ---
Maybe, but certainly not as rounded as the default window border, window
decoration, and buttons. Might be worth doing a user poll to see what is
aesthetically preferred.

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

[kdevelop] [Bug 381203] New: Kdevelop crashes when editing Python Code

2017-06-14 Thread Jonathan Verner

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

Bug ID: 381203
   Summary: Kdevelop crashes when editing Python Code
   Product: kdevelop
   Version: 5.1.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: jonathan.ver...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.1.1)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.4.0-79-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
Editing Python Code sometimes leads to crashes, however, I was not able to
reliably reproduce the crash. It seems to happen randomly.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb7a402c900 (LWP 8429))]

Thread 13 (Thread 0x7fb74139b700 (LWP 8665)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb7b3ab06f4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fb7b3ab0739 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fb7bada16ba in start_thread (arg=0x7fb74139b700) at
pthread_create.c:333
#4  0x7fb7c0dfc82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fb7437fe700 (LWP 8583)):
#0  0x7fb7c0df0b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb7b89dd38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb7b89dd49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb7c171075b in QEventDispatcherGlib::processEvents
(this=0x7fb7345172a0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb7c16bb0ba in QEventLoop::exec (this=this@entry=0x7fb7437fdcc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fb7c14eaf64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fb7c14efb48 in QThreadPrivate::start (arg=0x7fb7b3dde6b8
) at
thread/qthread_unix.cpp:368
#7  0x7fb7bada16ba in start_thread (arg=0x7fb7437fe700) at
pthread_create.c:333
#8  0x7fb7c0dfc82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fb7524b5700 (LWP 8499)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb7c14f09fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x25c9df0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x2642dd0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fb7b66ca07f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fb7b66ce078 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fb7b66c926d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fb7b66ce0d2 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fb7b66c926d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fb7b66cbbf0 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fb7c14efb48 in QThreadPrivate::start (arg=0x7fb784003cb0) at
thread/qthread_unix.cpp:368
#10 0x7fb7bada16ba in start_thread (arg=0x7fb7524b5700) at
pthread_create.c:333
#11 0x7fb7c0dfc82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fb7534d1700 (LWP 8498)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb7c14f09fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x25c9df0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x2642dd0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fb7b66ca07f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fb7b66ce078 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fb7b66c926d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fb7b66cbbf0 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fb7c14efb48 in QThreadPrivate::start (arg=0x7fb75c308fe0) at
thread/qthread_unix.cpp:368
#8  0x7fb7bada16ba in start_thread (arg=0x7fb7534d1700) at
pthread_c

[Discover] [Bug 379943] Text in updater section is pale when using a dark theme

2017-06-14 Thread Christoph Feck

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

--- Comment #4 from Christoph Feck  ---
Maxim, could you please share your color and theme settings files? These would
be .config/kdeglobals and .config/plasmarc. It is possible that you are mixing
dark and light themes.

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

[Discover] [Bug 375913] Kde "Discover" crashing

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 CC||kde-b...@ssr.host.ru

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

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

[Discover] [Bug 380425] Discover app crash on update attempt

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[Discover] [Bug 380483] sudoers using pam to block root

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Christoph Feck  ---
Unless we get more information, we have to assume it has been resolved with
help from your distribution provider.

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

[dolphin] [Bug 379336] Folder icon text label multi line behavior

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #9 from Christoph Feck  ---
To further investigate this issue, KDE developers need the information
requested in comment #7. Please add a text comment, graphical mockups or
sketches.

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

[dolphin] [Bug 379389] Dolphin freezes during large transfers over NFS

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Christoph Feck  ---
Thanks for the update; closing.

I suggest to investigate which method was used to mount the share and report
this issue to developers of these tools.

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

[kde] [Bug 380361] KDE (Qt) apps stop processing keyboard events

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
  Component|general |general
   Assignee|fa...@kde.org   |unassigned-b...@kde.org
Product|frameworks-kded |kde
Version|5.33.0  |unspecified

--- Comment #1 from Christoph Feck  ---
Do you have some input method helpers installed, such as IBus or Fcitx? If this
also happens with Qt applications that do not use KDE components, then I doubt
there is anything KDE developers can do to resolve this issue.

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

[kwin] [Bug 378710] OpenGL visual glitches for task switcher, desktop grid and window tiling.

2017-06-14 Thread Szymon Łągiewka

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

--- Comment #2 from Szymon Łągiewka  ---
I made a quick video that shows all of the issues in one take.
https://youtu.be/tZqx2mgY1Bc

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

[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

2017-06-14 Thread Ryokun

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

--- Comment #27 from Ryokun  ---
Hello,

Just for your interest I encountered the bug in another form : when you try to
"file/export..." a file as jpeg, if you click the save button on the files
panel THEN click CANCEL on the jpeg settings panel, Krita randomly freezes the
same way as when you really try to export the file. I could reproduce it
multiple times as JPEG, never as PNG (strangely !) but this bug is much less
frequent than the one when you effectively try to save the file (i'd say it
occurs maybe 1 time on 15 !), so maybe it can happen for PNG too...

I also tried to launch Krita from the terminal to see the logs but nothing
showed when the bug occured.

Hope you found something on your side because this bug is really strange (and
really annoying too !)

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

[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

2017-06-14 Thread Ryokun

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

--- Comment #28 from Ryokun  ---
(Oh and I forget : this happened on the 3.1.4 version on Krita)

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

[krita] [Bug 381204] New: Extract foreground [interactive] result in offest layers with G'mic 0.1.7 in Krita 3.1.4

2017-06-14 Thread Camille Bissuel

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

Bug ID: 381204
   Summary: Extract foreground [interactive] result in offest
layers with G'mic 0.1.7 in Krita 3.1.4
   Product: krita
   Version: 3.1.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: G'Mic for Krita
  Assignee: krita-bugs-n...@kde.org
  Reporter: welc...@nylnook.com
  Target Milestone: ---

Created attachment 106094
  --> https://bugs.kde.org/attachment.cgi?id=106094&action=edit
Extract foreground [interactive] offest 1

This may be solved with Gmic 2, but for some pictures (including this one:
https://commons.wikimedia.org/wiki/Earth#/media/File:BlueMarble-2001-2002.jpg),
using the extract foreground [interactive] filter of G'mic in Krita may result
in offest layers.

Using the background dots (red ones) instead of the foreground dots (green
ones) for the foreground usually workaround the issue.

Please see the attached screenshots for a clearer explanation ;)

Depending on the ratio of the picture, the bug seem to occur or not. It doesn't
occur in Gimp.

Initially reported here :
https://github.com/dtschump/gmic-community/issues/82#issuecomment-308412717

Tested on Antergos Linux 64 bits

Thanks !

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

[plasmashell] [Bug 381160] Battery plasmoid does not show a notification that an application is inhibiting screenlock when it uses xdg-screensaver to do so

2017-06-14 Thread Kai Uwe Broulik

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

--- Comment #1 from Kai Uwe Broulik  ---
When I run xdg-screensaver from console I can see it telling
org.freedesktop.ScreenSaver on DBus which in turn tells PowerDevil.  Then it
immediately uninhibits because the application (xdg-screensaver) that requested
the inhibition quit.

powerdevil: Scheduling inhibition from ":1.10" "0x5a5" with cookie 1 and
reason "xdg-screensaver"
powerdevil: Releasing inhibition with cookie  1

I don't actually have mpv installed here, so I don't know if this behavior
applies to it at all. I just don't understand why the inhibition still holds
after it, screen locker also uninhibits in this case. Are you sure the
inhibition is applied? Perhaps it's doing another thing (simulate user
activity) repeatedly.

In any case the "appName" which is ":1.10" with reason "xdg-screensaver" is
just plain wrong and perhaps that causes the issue of it not showing up,
":1.10" is not a valid application name after all.

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

[kwayland-integration] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

 CC||mvourla...@gmail.com

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

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

[frameworks-kwayland] [Bug 380828] [possible crash] - exiting an application using kwayland

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[konversation] [Bug 381066] Konversation crashes with a segmentation fault

2017-06-14 Thread wintonian

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

wintonian  changed:

   What|Removed |Added

 CC||bugzi...@wintonian.org.uk

--- Comment #3 from wintonian  ---
Same issues as the original reporter with the same servers open. However I am
using Fedora 25 and have more rooms open.

I updated to ver. konversation.x86_64 1.7.2-1.fc25 and the issue remains.

/var/log/messages keeps reporting the following at about the same time as the
crash:

QXcbConnection: XCB error: 3 (BadWindow), sequence: 60229, resource id:
50331711, major code: 18 (ChangeProperty), minor code: 0


Backtrace

Application: Konversation (konversation), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f88d5899940 (LWP 4904))]

Thread 4 (Thread 0x7f88c35ef700 (LWP 4908)):
#0  0x7f88e14f9f3d in poll () from /lib64/libc.so.6
#1  0x7f88da934166 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f88da93427c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f88e23006eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f88e22b168a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f88e210e5e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f88e21129ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f88e00f773a in start_thread () from /lib64/libpthread.so.0
#8  0x7f88e1505e7f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f88c8fe4700 (LWP 4907)):
#0  0x7f88da979894 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7f88da933690 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7f88da93408b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f88da93427c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f88e23006eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f88e22b168a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f88e210e5e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f88e250dfb9 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#8  0x7f88e21129ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7f88e00f773a in start_thread () from /lib64/libpthread.so.0
#10 0x7f88e1505e7f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f88cafc1700 (LWP 4906)):
#0  0x7f88e14f9f3d in poll () from /lib64/libc.so.6
#1  0x7f88de4e1d10 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7f88de4e3aa9 in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7f88cec12d69 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7f88e21129ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7f88e00f773a in start_thread () from /lib64/libpthread.so.0
#6  0x7f88e1505e7f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f88d5899940 (LWP 4904)):
[KCrash Handler]
#6  0x7f88e218c8af in QString::operator=(QString const&) () from
/lib64/libQt5Core.so.5
#7  0x5615693195a7 in InputFilter::parseClientCommand(QString const&,
QString const&, QStringList&, QHash) ()
#8  0x561569324968 in InputFilter::parseLine(QString const&) ()
#9  0x5615692d0554 in Server::processIncomingData() ()
#10 0x561569437fc9 in Server::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) ()
#11 0x7f88e22d9721 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#12 0x7f88e22e5c08 in QTimer::timerEvent(QTimerEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7f88e22da79b in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#14 0x7f88e2b7eecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#15 0x7f88e2b86671 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#16 0x7f88e22b26fa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7f88e22ffceb in QTimerInfoList::activateTimers() () from
/lib64/libQt5Core.so.5
#18 0x7f88e2300241 in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5Core.so.5
#19 0x7f88da933e52 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7f88da9341d0 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#21 0x7f88da93427c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7f88e23006cf in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7f88e22b168a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x7f88e22b918c in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#25 0x561569263767 in main ()

-- 
You are receiving

[krita] [Bug 381204] Extract foreground [interactive] result in offest layers with G'mic 0.1.7 in Krita 3.1.4

2017-06-14 Thread Camille Bissuel

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

--- Comment #1 from Camille Bissuel  ---
Created attachment 106095
  --> https://bugs.kde.org/attachment.cgi?id=106095&action=edit
Extract foreground [interactive] offest 2

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

[krita] [Bug 381204] Extract foreground [interactive] result in offset layers with G'mic 0.1.7 in Krita 3.1.4

2017-06-14 Thread Camille Bissuel

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

Camille Bissuel  changed:

   What|Removed |Added

Summary|Extract foreground  |Extract foreground
   |[interactive] result in |[interactive] result in
   |offest layers with G'mic|offset layers with G'mic
   |0.1.7 in Krita 3.1.4|0.1.7 in Krita 3.1.4

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

[partitionmanager] [Bug 375394] application crash if started without root permission

2017-06-14 Thread Andrius Štikonas

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

Andrius Štikonas  changed:

   What|Removed |Added

   Version Fixed In||3.1.0

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

[krita] [Bug 381204] Extract foreground [interactive] result in offset layers with G'mic 0.1.7 in Krita 3.1.4

2017-06-14 Thread Camille Bissuel

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

--- Comment #2 from Camille Bissuel  ---
Created attachment 106096
  --> https://bugs.kde.org/attachment.cgi?id=106096&action=edit
Extract foreground [interactive] offset 3

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

[kwin] [Bug 381205] New: Toggle presents windows shortcut does not toggle 'off'

2017-06-14 Thread Mike Lui

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

Bug ID: 381205
   Summary: Toggle presents windows shortcut does not toggle 'off'
   Product: kwin
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mike.d@gmail.com
  Target Milestone: ---

Global shortcuts has "Toggle Present Windows (Current desktop)' set to a key.

In KDE 5.9, when that key was hit once, it would explode the view of all
windows.
When that key was hit again, it would jump back to the previous view

In KDE 5.10.1 (and now in 5.10.2), when that key is hit once, it explodes the
view of all windows.
When that key is hit again, nothing happens. The only way to 'unset' the
exploded view is to click a blank area of the desktop, or a window.

This does not match the concept of 'toggle', IMO. The behavior in 5.9 was more
in line with what is expected.

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

[frameworks-plasma] [Bug 380280] Crash when using webengine type in plasma

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #3 from Christoph Feck  ---
I remember we had to add patches to Konqueror and KDEPIM applications to not
crash with QtWebEngine. It is possible that 'plasmoidviewer' needs a similar
patch.

Relevant part of backtrace from comment #2:

Thread 1 (Thread 0x7f2f11ae68c0 (LWP 6677)):
[KCrash Handler]
#6  0x7f2f0d0776f0 in QOpenGLContext::shareGroup() const () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x7f2f0d077719 in QOpenGLContext::areSharing(QOpenGLContext*,
QOpenGLContext*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#8  0x7f2e59f134e8 in
QtWebEngineCore::DelegatedFrameNode::DelegatedFrameNode() (this=0x41bdc40) at
/workspace/build/src/core/delegated_frame_node.cpp:427
#9  0x7f2e59f36145 in
QtWebEngineCore::RenderWidgetHostViewQt::updatePaintNode(QSGNode*)
(this=0x4201020, oldNode=) at
/workspace/build/src/core/render_widget_host_view_qt.cpp:749
#10 0x7f2f0fb78720 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*)
(this=this@entry=0x1354210, item=item@entry=0x4232460) at
items/qquickwindow.cpp:3121
#11 0x7f2f0fb78f8b in QQuickWindowPrivate::updateDirtyNodes()
(this=this@entry=0x1354210) at items/qquickwindow.cpp:2866
#12 0x7f2f0fb7a020 in QQuickWindowPrivate::syncSceneGraph()
(this=this@entry=0x1354210) at items/qquickwindow.cpp:419
#13 0x7f2f0fb46978 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*)
(this=0x132f200, window=0x1152bb0) at scenegraph/qsgrenderloop.cpp:391
#14 0x7f2f0fb83f67 in QQuickWindow::event(QEvent*) (this=0x1152bb0,
e=0x7ffc76a7b900) at items/qquickwindow.cpp:1527

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

[frameworks-plasma] [Bug 380280] Crash when using webengine type in plasma

2017-06-14 Thread Christoph Feck

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

--- Comment #4 from Christoph Feck  ---
See e.g.
https://cgit.kde.org/konqueror.git/commit/?id=c5b71a8301e615c3e4d7fb023e815b3c8aab1adc

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

[kmail2] [Bug 381181] akonadiserver is launched every time kmail starts via SSH X-Forwarding.

2017-06-14 Thread Rex Dieter

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[kmail2] [Bug 381181] akonadiserver is launched every time kmail starts via SSH X-Forwarding.

2017-06-14 Thread Steven Haigh

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

--- Comment #2 from Steven Haigh  ---
I should mention that I connect to my laptop via:

I connect to my laptop via:
$ ssh -C -Y username@

Then launch kmail via:
$ dbus-launch kmail

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

[kate] [Bug 380861] >> Replace checked << cause a freeze/crash

2017-06-14 Thread Matthias

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

--- Comment #6 from Matthias  ---
So, the buttons are an issue for the crash, when they are enabled?

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

[kate] [Bug 380861] >> Replace checked << cause a freeze/crash

2017-06-14 Thread Matthias

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

--- Comment #7 from Matthias  ---
I am willing to test this patch. :)

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

[plasmashell] [Bug 378010] Generic High CPU Usage Rendering

2017-06-14 Thread Steven Haigh

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

Steven Haigh  changed:

   What|Removed |Added

 CC||net...@crc.id.au

--- Comment #30 from Steven Haigh  ---
I wonder if my report from re kwin_x11 belongs here too?

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

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

[plasmashell] [Bug 380863] Cannot autostart synology cloudstation server at login

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #3 from Christoph Feck  ---
Thanks for the update; closing.

If synology-cloud-station-drive fails again, please report this issue directly
to synology-cloud-station-drive developers.

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

[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

2017-06-14 Thread Boudewijn Rempt

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

--- Comment #29 from Boudewijn Rempt  ---
I haven't :-(


But there are now builds of master ready to test, and in master all the saving
code has been rewritten:
https://download.kde.org/unstable/krita/4.0.0-prealpha/krita-4.0.0-prealpha.dmg
-- i wonder if there is a difference.

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

[systemsettings] [Bug 380842] Under Plasma on Wayland, Specifically Settings > Desktop Behavior has wild graphics behavior

2017-06-14 Thread Christoph Feck

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
This is probably a duplicate of bug https://bugreports.qt.io/browse/QTBUG-59017

Please add a comment if Qt 5.9.1 does not resolve this issue.

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

[plasmashell] [Bug 381155] Wayland - Plasma slow startup and messed up multimonitor configuration

2017-06-14 Thread CDK

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

--- Comment #1 from CDK  ---
Additional information: The font scaling is also broken.

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

[kdeconnect] [Bug 373967] Android File System not Mounted and Pairing is no longer persistent.

2017-06-14 Thread Luzius Auer

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

Luzius Auer  changed:

   What|Removed |Added

 CC||luz...@geosystem.ch

--- Comment #10 from Luzius Auer  ---
Still same problem though I tried all methods described here.
I'm using Krusader (instead of Dolphin) as default file manager and a Huawei P9
phone under Android 6.0
Very sad for an otherwise promising solution to access the Android file system
from KDE. Why is the status marked RESOLVED FIXED. I strongly disagree.
Still hoping
regards Luzius

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

[knetwalk] [Bug 381206] New: Knetwalk starts up but the content of the screen is not visible (black screen)

2017-06-14 Thread HERVE MOENS

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

Bug ID: 381206
   Summary: Knetwalk starts up but the content of the screen is
not visible (black screen)
   Product: knetwalk
   Version: 3.3.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ashwin_raj...@hotmail.com
  Reporter: herve.mo...@skynet.be
CC: kde-games-b...@kde.org
  Target Milestone: ---

Starting program: /usr/bin/knetwalk 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe3e7e700 (LWP 18048)]
[New Thread 0x7fffdbfff700 (LWP 18049)]
[New Thread 0x7fffdadee700 (LWP 18050)]
[New Thread 0x7fffd940d700 (LWP 18051)]
[Thread 0x7fffd940d700 (LWP 18051) exited]
[New Thread 0x7fffd940d700 (LWP 18053)]
[Thread 0x7fffd940d700 (LWP 18053) exited]
[New Thread 0x7fffd940d700 (LWP 18054)]
[New Thread 0x7fffe0207700 (LWP 18055)]
Module 'org.kde.games.core' does not contain a module identifier directive - it
cannot be protected from external registrations.
games.ui: KStandardGameAction::create(  1 = game_new ,
KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
games.ui: KStandardGameAction::create(  7 = game_pause ,
KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
games.ui: KStandardGameAction::create(  25 = move_solve ,
KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
games.ui: KStandardGameAction::create(  8 = game_highscores ,
KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
games.ui: KStandardGameAction::create(  11 = game_quit ,
KActionCollection(0x8f3e20, name = "KXMLGUIClient-KActionCollection")  )
[New Thread 0x7fffb8c17700 (LWP 18056)]
[New Thread 0x7fffb08e5700 (LWP 18057)]
[New Thread 0x7fffaf454700 (LWP 18058)]
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
QQuickWidget cannot be used as a native child widget. Consider setting
Qt::AA_DontCreateNativeWidgetSiblings
[Thread 0x7fffdadee700 (LWP 18050) exited]
[Thread 0x7fffaf454700 (LWP 18058) exited]
[Thread 0x7fffe3e7e700 (LWP 18048) exited]
[Thread 0x7fffb08e5700 (LWP 18057) exited]
[Thread 0x7fffb8c17700 (LWP 18056) exited]
[Thread 0x7fffe0207700 (LWP 18055) exited]
[Thread 0x7fffd940d700 (LWP 18054) exited]
[Thread 0x7fffdbfff700 (LWP 18049) exited]
[Inferior 1 (process 18043) exited normally]
(gdb)

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

[plasmashell] [Bug 380411] Plasmashell hangs waiting for audio

2017-06-14 Thread Christoph Feck

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

--- Comment #2 from Christoph Feck  ---
If you can provide the information requested in comment #1, please add it.

You can interrupt gdb while plasmashell hangs to get the backtrace. Without
this information, we have to assume that it is some upstream component that
blocks.

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

[systemsettings] [Bug 381207] New: Allow the use of a solid color as the background instead of a wallpaper

2017-06-14 Thread KDE Neon user

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

Bug ID: 381207
   Summary: Allow the use of a solid color as the background
instead of a wallpaper
   Product: systemsettings
   Version: 5.10.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_sddm
  Assignee: k...@davidedmundson.co.uk
  Reporter: emailm...@protonmail.com
  Target Milestone: ---

Currently, we can only select images or themes. It'd be nice to be able to set
a solid color too.

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

1 2 3 4 5 >

1 - 100 of 434 matches

Mail list logo