[plasmashell] [Bug 369156] black screen after /etc/init.d/xdm start

[Yu Tzu Wu via KDE Bugzilla]

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

--- Comment #3 from Yu Tzu Wu  ---
Where can I report a sddm bug?

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

[digikam] [Bug 369140] Tags don't appear at all

[Robinson Twins via KDE Bugzilla]

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

Robinson Twins  changed:

   What|Removed |Added

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

--- Comment #2 from Robinson Twins  ---
I decided that since I had upgraded DigiKam from 4.22 to 5.0 then to 5.1, the
problem was probably in the database. So I found the DigiKam database in my
Pictures folder and deleted it, then got Digikam to create a new database. Now
the tags work like they're supposed to.

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

[digikam] [Bug 338176] Face Recognition memory allocation crash application

[Peter via KDE Bugzilla]

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

--- Comment #80 from Peter  ---
In view of the deepening hassles, I gave up on digiKam 4.x. All versions that I
tried crashed out on memory overflow during face detection as well as on face
tagging as described above. 

So, installed Linux Mint 18 (which also came with a version 4 digiKam) and then
got digiKam 5.1 from philip5/extras. Now face tagging works without the memory
overflow, great! This is very exciting and I have high hopes that digiKam will
be a very useful tool for managing my photo collection (when I learn to drive
it properly).

Face detection by v5.1 works, mostly.  I've had a couple of crashes with face
detection, but I haven't worked out the circumstances. I haven't tried face
recognition, denoted as 'experimental'.

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

[digikam] [Bug 366769] Rename aborts after first rename of many

[via KDE Bugzilla]

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

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

   What|Removed |Added

   Version Fixed In||5.3.0

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

[konsole] [Bug 178320] Konsole split view: in both views same content

[Mathieu Jobin via KDE Bugzilla]

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

--- Comment #42 from Mathieu Jobin  ---
hey, we got something that work !


https://bitbucket.org/somekool/kde-start/branch/app_close

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

[Powerdevil] [Bug 369181] User session security vulnerability from screen lock being suppressed with power management

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

  Flags||Usability?
 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
Adding usability team.

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

[kio] [Bug 336397] Getting "Unknown error code 150" when opening USB connected Android device in MTP mode

[lbickley via KDE Bugzilla]

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

--- Comment #4 from lbickley  ---
btw: The default device is MTP: per either  (see directory
/usr/share/kde4/apps/solid/actions/ ):

Note: See "exec=..." in script below

File: solid_mtp.desktop
---
[Desktop Entry]
X-KDE-Solid-Predicate=PortableMediaPlayer.supportedProtocols == 'mtp'
Type=Service
Actions=open;

[Desktop Action open]
Exec=kioclient exec mtp:udi=%i/
Icon=system-file-manager
Name=Open with File Manager
Name[bs]=Otvori menadžerom datoteka
...

NOTE: I also tried with SAME or somewhat better results:

[Desktop Entry]
X-KDE-Solid-Predicate=PortableMediaPlayer.supportedProtocols == 'mtp'
Type=Service
Actions=open;

[Desktop Action open]
Exec=dolphin "mtp:/"
Icon=system-file-manager
Name=Open with File Manager
Name[bs]=Otvori menadžerom datoteka
...

Lyle

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #39 from Leslie Zhai  ---
Git commit ae0413daf1df44cb2c8c6e88a5b86180f1f52c3a by Leslie Zhai.
Committed on 22/09/2016 at 03:42.
Pushed by lesliezhai into branch 'multisession'.

Multisession implemented as Thomas suggested

Summary:
- validate file descriptor
- check for the ISO 9660 magic number
- convert the 4 bytes into a 32 bit number by interpreting them as
little-endian number
- A generic checker for GrowisofsWriter (growisofs) and IsoImager (mkisofs)

M  +1-0libk3b/projects/datacd/k3bdatajob.cpp
M  +41   -0libk3b/projects/datacd/k3bisoimager.cpp
M  +2-30   libk3b/projects/k3bgrowisofswriter.cpp

http://commits.kde.org/k3b/ae0413daf1df44cb2c8c6e88a5b86180f1f52c3a

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

[Powerdevil] [Bug 369181] New: User session security vulnerability from screen lock being suppressed with power management

[Boskote via KDE Bugzilla]

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

Bug ID: 369181
   Summary: User session security vulnerability from screen lock
being suppressed with power management
   Product: Powerdevil
   Version: 5.6.4
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: bosk...@riseup.net

The problem is that applications (in my experience it has only been browsers,
both firefox and chromium) request that power management be suppressed, which
overrides an automatic screen lock timeout configured through power management.
On its own this behaviour makes sense, but it can result in a silent failure of
the timed automatic screen locking, which is a significant vulnerability for
users who are depending on the auto screen lock for the security of their
session. 

This problem is exacerbated by poorly designed websites that get the browser to
request power management suppression for reasons that are not obvious to the
user (a background webRTC PeerConnection in chromium is the recent example I
saw).

I would expect that there would be an externally visible notification of when
this suppression of power management occurs, so that a user who is depending on
screen locking will be aware that it has been disabled. Alternatively, there
could also be a way of configuring power management to override the suppression
requests for users who value screen locking (and other power management
features) over the convenience of the automatic suppression. 

It is possible to click on the "Battery and Brightness" tab of the system tray
to see a message about suppression of power management, but there is no
externally visible notification when the suppression occurs. It is too tedious
to periodically click into this area to check if there is a suppression. 

It is also possible to configure a button or keyboard shortcut for quick screen
locking and do this manually just in case the automatic screen lock is being
suppressed. This is the workaround I am currently using, but it is basically
just a replacement for a timed screen lock that can't be trusted to work as
configured. 

Reproducible: Always

Steps to Reproduce:
1. Use power management to configure a short timeout on the screen lock
2. Open a poorly designed website in chromium or firefox that makes background
requests to suppress power management (some pages from http://www.laprensa.hn/
in chromium containing background webrtc peerconnections, for example). 
3. Get up and leave the computer with that tab open. See how long it takes for
someone to realize you left your session open and start digging around in your
stuff :p

Actual Results:  
The screen lock will not work because the power management is suppressed. 

Expected Results:  
Popped up a notification (or have the option to enable such a notification) as
soon as the power management is suppressed so that the offending website tab
could be closed, or the screen could be manually locked.

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

[kdenlive] [Bug 369180] New: git master - changing effects parameters doesn't affect preview render.

[Jesse via KDE Bugzilla]

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

Bug ID: 369180
   Summary: git master - changing effects parameters doesn't
affect preview render.
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

When I've preview rendered a zone, and make changes to an Effect parameter on a
clip IN that zone, the preview render bar shows red where it should. However,
when I click on Preview Render, it instantly goes green and uses the cached
render files -- it doesn't re-render the clip with the changed effects that I
made.

Reproducible: Always

Steps to Reproduce:
1. Preview render a zone in timeline with clips with effects on them.
2. Change some of the parameters to those clips.
3. Re-render same preview zone.

Actual Results:  
Kdenlive uses the already rendered cache files, instead of re-rendering the
video clips whose effects I made changes to. I can manually delete the cache,
but then I have to re-render everything.

Expected Results:  
When changes are made to an effect on a clip in the Timeline, Kdenlive
recognizes it and puts a red bar in the space where a new preview render is
needed (which it does). BUT, when I hit Start preview render, I would expect it
to re-render the clips that have had their effects parameters changed.

Bug discovered while using Kdenlive 16.11.70 git master build via
ppa:kdenlive/kdenlive-master Kubuntu 16.10, KDE Plasma 5.7.2 desktop
environment. 

KDE Frameworks 5.24.0
Qt 5.6.1

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

[kdenlive] [Bug 369180] git master - changing effects parameters doesn't affect preview render.

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

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

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

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

[Rhys Kidd via KDE Bugzilla]

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

--- Comment #4 from Rhys Kidd  ---
Preliminary support added in r15976.

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

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

[Rhys Kidd via KDE Bugzilla]

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

Rhys Kidd  changed:

   What|Removed |Added

 Attachment #101036|0   |1
is obsolete||

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

[kdeconnect] [Bug 369179] Reply function not working when receive a sms text

[via KDE Bugzilla]

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

--- Comment #1 from voncl...@gmail.com ---
found a typo - the app on the phone for kdeconnect is 1.4

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

[kdeconnect] [Bug 369179] New: Reply function not working when receive a sms text

[via KDE Bugzilla]

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

Bug ID: 369179
   Summary: Reply function not working when receive a sms text
   Product: kdeconnect
   Version: 1.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: voncl...@gmail.com

I will get a sms text, the notification popup will appear - the "Reply" button
appears however when I click it nothing happens.

The button disappears and I am unable to respond from the desktop.

Reproducible: Always

Steps to Reproduce:
1. send text message to self on phone
2. get notification on desktop with - reply prompt
3. click it - nothing happens

Actual Results:  
nothing, the button disappears and no textbox is given to respond

Expected Results:  
Once respond button is clicked in notification popup some way to communicate to
the message should be given.

I use Gentoo, I have set the use flag of telepathy to active in the package
use.
I run plasma 5 kde and the app on the phone for kde 5 is version 1.4

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

[yakuake] [Bug 369178] New: Yakuake does not properly scale to the width of a monitor if it's rotated 90 degrees

[via KDE Bugzilla]

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

Bug ID: 369178
   Summary: Yakuake does not properly scale to the width of a
monitor if it's rotated 90 degrees
   Product: yakuake
   Version: 3.0.2
  Platform: Gentoo Packages
   URL: http://imgur.com/a/vYJ5I
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: sted...@gmail.com

In KDE System Settings under Display and Monitor, you can set a monitor to be
rotated 90 degrees. When you rotate a monitor, the width of yakuake does not
take the proper width of the screen on the rotated monitor. I have width set to
90% for Yakuake, when on my horizontal monitor, it works perfectly fine. When
on the vertical monitor, it only takes up a small portion of the screen. If it
matters, I have it rotated 90 degrees counterclockwise.

Reproducible: Always

Steps to Reproduce:
1. Rotate a monitor 90 degrees counter clockwise, change settings in Display
Configuration to reflect the physical monitor changes
2. Open Yakuake on the rotated display

Actual Results:  
The Yakuake window does not take up 90% of the screen, more like a quarter of
it. 

Expected Results:  
The Yakuake window should take up 90% of the width of the screen.

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

[digikam] [Bug 366769] Rename aborts after first rename of many

[Geoff King via KDE Bugzilla]

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

Geoff King  changed:

   What|Removed |Added

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

--- Comment #8 from Geoff King  ---
Looks to be fixed now on 5.2.0 for Mac.  Thanks and please close.

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

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

[Carl Love via KDE Bugzilla]

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

Carl Love  changed:

   What|Removed |Added

 CC||c...@us.ibm.com

--- Comment #5 from Carl Love  ---
Created attachment 101221
  --> https://bugs.kde.org/attachment.cgi?id=101221=edit
fix for jm_int_isa_2_07.

The none/tests/ppc64/jm_int_isa_2_07.stdout.exp, by convention, should have the
big endian results.  The current file contains the little endian results.  By
convention, the little endian result files have "-LE" appended to the expected
output file name.  This patch fixes the output in the 
none/tests/ppc64/jm_int_isa_2_07.stdout.exp file.  

The results of the regression test on pre Power 8 processors and Power 8 LE
processors should not change.

Please test the patch and see if the regression test results are as expected on
your machine.

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

[plasmashell] [Bug 367664] Touchpad widget icon must reflect device status

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

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

[krita] [Bug 369177] New: filter applies to wrong layer and deletes when canceled

[Ayana via KDE Bugzilla]

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

Bug ID: 369177
   Summary: filter applies to wrong layer and deletes when
canceled
   Product: krita
   Version: 3.0.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Filters
  Assignee: krita-bugs-n...@kde.org
  Reporter: crazy4...@gmail.com

After adding another layer, I was going to add a filter, but when the menu for
the filters popped up, the mask was on the layer below. After canceling the
filter mask, it deletes the layer i was originally was going to add a filter
to.

Reproducible: Always

Steps to Reproduce:
1.draw something on one layer
2.add another or duplicate layer
3.covert second/duplicate layer to filter mask

Actual Results:  
It applies a mask to the layer below 

Expected Results:  
should have applied mask to the chosen layer

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

[plasmashell] [Bug 368936] Screen Lock happens after waking up from sleep

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Plasma 5.5 is really old and there have been changes in that area since.

If this is still a problem with >5.7 please reopen this bug report.

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

[plasmashell] [Bug 369173] OSD (on screen display) settings missing

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #2 from David Edmundson  ---
Those options never existed.  I just checked the OSD code logs, and it never
loaded anything from a config.

I'm not quite sure what you might be thinking of.

If you have any specific bugs regarding OSDs please reopen this with some extra
info as to what exactly is problematic.

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

[plasmashell] [Bug 369159] kickoff config dialog clips content

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 353015] Crash in Garbage collection after Plasma::DataEngine::connectSource

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #25 from David Edmundson  ---
Given I narrowed this down to the
applets/systemtray/plugin/protocols/dbussystemtray/dbussystemtrayprotocol.cpp:

and this has been rewritten since Plasma 5.5, I'm going to close this.

We've not got any duplicates newer than Plasma 5.4

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

[kdevelop] [Bug 369176] New: Crash when selecting one of the fixits

[Aleix Pol via KDE Bugzilla]

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

Bug ID: 369176
   Summary: Crash when selecting one of the fixits
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: aleix...@gmail.com

Application: kdevelop (5.0.1)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.27.0
Operating System: Linux 4.7.3-2-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
Used QDesktopService, it wasn't declared so I pressed the option to add it
automatically.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe31eacc840 (LWP 23563))]

Thread 14 (Thread 0x7fe2e572c700 (LWP 993)):
#0  0x7fe32db6b10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fe32d8498e4 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fe32d932f20 ) at
/home/apol/devel/frameworks/qt5/qtscript/src/3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7fe32d849929 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
/home/apol/devel/frameworks/qt5/qtscript/src/3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7fe32db65454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fe334f607df in clone () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7fe2b8d60700 (LWP 23739)):
#0  0x7fe334f5748d in poll () from /usr/lib/libc.so.6
#1  0x7fe328f97066 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fe328f9717c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fe335d824db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /home/apol/devel/kde5/lib/libQt5Core.so.5
#4  0x7fe335d2ef2a in
QEventLoop::exec(QFlags) () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#5  0x7fe335b61feb in QThread::exec() () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#6  0x7fe33300be34 in KDevelop::CompletionWorkerThread::run
(this=0x8a62bb0) at
/home/apol/devel/frameworks/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7fe335b66a29 in ?? () from /home/apol/devel/kde5/lib/libQt5Core.so.5
#8  0x7fe32db65454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fe334f607df in clone () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7fe2e49ab700 (LWP 23687)):
#0  0x7fe334f5748d in poll () from /usr/lib/libc.so.6
#1  0x7fe328f97066 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fe328f9717c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fe335d824db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /home/apol/devel/kde5/lib/libQt5Core.so.5
#4  0x7fe335d2ef2a in
QEventLoop::exec(QFlags) () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#5  0x7fe335b61feb in QThread::exec() () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#6  0x7fe335b66a29 in ?? () from /home/apol/devel/kde5/lib/libQt5Core.so.5
#7  0x7fe32db65454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7fe334f607df in clone () from /usr/lib/libc.so.6

Thread 11 (Thread 0x7fe2e5f2d700 (LWP 23647)):
#0  0x7fe32db6b10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fe335b677db in QWaitCondition::wait(QMutex*, unsigned long) () from
/home/apol/devel/kde5/lib/libQt5Core.so.5
#2  0x7fe331dae8df in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=0x2972670, th=0x7fe2d80013e0) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:594
#3  0x7fe331dae760 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x2972670,
th=0x7fe2d80013e0, threadWasBusy=false, suspendIfInactive=false,
justReturning=false) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:554
#4  0x7fe331db97e4 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x294a1f0, th=0x7fe2d80013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:66
#5  0x7fe331db9a32 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:61
#6  0x7fe331daea4f in ThreadWeaver::Weaver::applyForWork (this=0x2972670,
th=0x7fe2d80013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/weaver.cpp:568
#7  0x7fe331db996f in ThreadWeaver::WorkingHardState::applyForWork
(this=0x294a1f0, th=0x7fe2d80013e0, wasBusy=false) at
/home/apol/devel/frameworks/threadweaver/src/workinghardstate.cpp:73
#8  0x7fe331db9a32 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at

[plasmashell] [Bug 369160] Kickoff's tab reordering feature hides tabs invariably

[John Salatas via KDE Bugzilla]

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

--- Comment #2 from John Salatas  ---
this is not a solution, but can you try with a clean (new) profile? It seems
that it works in the live CD (unstable). 

Also, just noticed that some files were not created during the diff commit
(I'll fix it soon)

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

[plasmashell] [Bug 362417] Spacer in panels are very difficult to handle (move around and resize)

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from David Edmundson  ---
Seems fixed then. Note two more spacer changes were merged in Plasma/5.8

Please open a new report if there are any other issues with the spacer. Thanks.

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

[plasmashell] [Bug 360936] Flexible spacer does not resize

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---
Should be fixed by 8e1339887a01e078b04fb18ff575c16998447665 which is in
Plasma/5.8

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

[plasmashell] [Bug 369156] black screen after /etc/init.d/xdm start

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #2 from David Edmundson  ---
This is before plasma, so it's not a plasma bug.
Sorry.

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

[plasmashell] [Bug 368074] The height of the panel is not restored correctly.

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[plasmashell] [Bug 369102] Creating panel on second monitor leads to mouse freezing

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #3 from David Edmundson  ---
Then we've got nowhere to go from here.

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

[plasmashell] [Bug 369160] Kickoff's tab reordering feature hides tabs invariably

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
   Severity|major   |normal

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

[valgrind] [Bug 369175] jm_vec_isa_2_07 test crashes on ppc64

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Note that running the program itself (not under valgrind) seems fine.
It is only when ran under valgrind that it produces the SIGSEGV:

==28394== Process terminating with default action of signal 11 (SIGSEGV)
==28394==  Bad permissions for mapped region at address 0x3828C978
==28394==at 0x100016D4: test_bcdadd (test_isa_2_07_part1.c:710)
==28394==by 0x10001A2B: test_av_bcd (test_isa_2_07_part1.c:1419)
==28394==by 0x420646B: generic_start_main.isra.0 (in
/usr/lib64/libc-2.17.so)
==28394==by 0x4206693: (below main) (in /usr/lib64/libc-2.17.so)

static int PS_bit;
static void test_bcdadd (void)
{
   if (PS_bit)
  __asm__ __volatile__ ("bcdadd. %0, %1, %2, 1" : "=v" (vec_out): "v"
(vec_inA),"v" (vec_inB));
   else
=>  __asm__ __volatile__ ("bcdadd. %0, %1, %2, 0" : "=v" (vec_out): "v"
(vec_inA),"v" (vec_inB));
}

=> is line 710.

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

[valgrind] [Bug 369175] New: jm_vec_isa_2_07 test crashes on ppc64

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369175
   Summary: jm_vec_isa_2_07 test crashes on ppc64
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

none/tests/ppc64/jm_vec_isa_2_07.vgtest runs fine on ppc64le, but crashes on a
ppc64[be] setup:

gcc-4.8.5-11.el7.ppc64
binutils-2.25.1-22.base.el7.ppc64
glibc-2.17-157.el7.ppc64
glibc-2.17-157.el7.ppc
kernel-3.10.0-508.el7.ppc64

processor: 0
cpu: POWER8 (architected), altivec supported
clock: 3425.00MHz
revision: 2.1 (pvr 004b 0201)

timebase: 51200
platform: pSeries
model: IBM,8247-22L
machine: CHRP IBM,8247-22L

none/tests/ppc64/jm_vec_isa_2_07.stderr.diff says:

+Process terminating with default action of signal 11 (SIGSEGV)
+ Bad permissions for mapped region at address 0x
+   at 0x: test_bcdadd (test_isa_2_07_part1.c:710)
+   by 0x: test_av_bcd (test_isa_2_07_part1.c:1419)
+   by 0x: generic_start_main.isra.0 (in /...libc...)
+   by 0x: (below main)

Up to that point the stdout output looks like expected.

Reproducible: Always

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

[kdenlive] [Bug 369123] If a clip in timeline is grouped (video+audio) remove space don't work and this warning appear "cannot remove space in a track with a group."

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit d9d5d95a4565fbfbb890be20696fb424140943de by Jean-Baptiste Mardelle.
Committed on 21/09/2016 at 21:36.
Pushed by mardelle into branch 'master'.

Add new timeline action: Remove space from all tracks that works if there are
grouped clips

M  +2-1src/kdenliveui.rc
M  +8-0src/mainwindow.cpp
M  +1-0src/mainwindow.h
M  +56   -117  src/timeline/customtrackview.cpp
M  +5-6src/timeline/customtrackview.h
M  +3-12   src/timeline/spacerdialog.cpp
M  +25   -25   src/ui/spacerdialog_ui.ui

http://commits.kde.org/kdenlive/d9d5d95a4565fbfbb890be20696fb424140943de

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

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Sven Brauch via KDE Bugzilla]

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

--- Comment #3 from Sven Brauch  ---
Hmm, is that package written in Python?

Does pressing F5 change anything? Maybe the project wasn't reparsed.

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

[kdevelop] [Bug 368970] Python: autocompletion not available for library installed in virtualenv

[Gregor Mi via KDE Bugzilla]

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

--- Comment #2 from Gregor Mi  ---
I created a new Python project, added my source file and put 

/home/gregor/.virtualenvs/arcade/lib/python3.5/site-packages

(which contains an arcade folder with the py files) into Open Configuration...
> Include/Imports.

Now, `import arcade` is not underlined anymore but I still cannot navigate to
the source or get auto-completion for arcade types.

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

[kdeplasma-addons] [Bug 369172] Plasma crashes, as soon as a new Comic Strip Widget is added

[melkor333 via KDE Bugzilla]

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

melkor333  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from melkor333  ---
(In reply to David Edmundson from comment #3)
> It doesn't happen here.
> 
> Do you have a backtrace? (the icon in the system tray of a sad face should
> open a bug reoprt dialog)

Yes! There we go:

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

Thread 25 (Thread 0x7eff15a47700 (LWP 2191)):
#0  0x7f001a4bdf69 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0
#1  0x7f001a479801 in g_main_context_query () from
/usr/lib/libglib-2.0.so.0
#2  0x7f001a479fd8 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7f001a47a17c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7f001facf59b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7f001fa790da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7f001f89c0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7f0022bfe445 in ?? () from /usr/lib/libQt5Qml.so.5
#8  0x7f001f8a0d78 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7f001e9b0454 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f001f1b67df in clone () from /usr/lib/libc.so.6

Thread 24 (Thread 0x7eff167fc700 (LWP 2151)):
#0  0x7f001e9b610f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f001f8a1c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7eff696ed1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7eff696f1988 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7eff696ec263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7eff696f19e2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7eff696ec263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7eff696ef1f9 in ThreadWeaver::Thread::run() () from
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f001f8a0d78 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7f001e9b0454 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f001f1b67df in clone () from /usr/lib/libc.so.6

Thread 23 (Thread 0x7eff16ffd700 (LWP 2150)):
#0  0x7f001e9b610f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f001f8a1c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7eff696ed1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7eff696f1988 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7eff696ec263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7eff696f19e2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7eff696ec263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7eff696ef1f9 in ThreadWeaver::Thread::run() () from
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f001f8a0d78 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7f001e9b0454 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f001f1b67df in clone () from /usr/lib/libc.so.6

Thread 22 (Thread 0x7eff177fe700 (LWP 2149)):
#0  0x7f001e9b610f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f001f8a1c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7eff696ed1c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7eff696f1988 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7eff696ec263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7eff696f19e2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7eff696ec263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7eff696f19e2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7eff696ec263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7eff696f19e2 in ?? () from /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7eff696ec263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/libKF5ThreadWeaver.so.5
#11 

[plasmashell] [Bug 365240] kde.systemtray floods .xsession-errors with messages if Thunderbird is running

[Raman Gupta via KDE Bugzilla]

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

--- Comment #9 from Raman Gupta  ---
(In reply to Marco Martin from comment #8)
> is the systray icon done with
> https://addons.mozilla.org/it/thunderbird/addon/firetray/ ?

I guess you were asking the OP but FYI not in my case. Thunderbird not related
at all.

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

[Spectacle] [Bug 369174] New: Add image preview option for "Save As" dialog

[Shmerl via KDE Bugzilla]

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

Bug ID: 369174
   Summary: Add image preview option for "Save As" dialog
   Product: Spectacle
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: shm...@mykolab.com

Spectacle doesn't have preview option in the save as dialog, which for example
existed in Ksnapshot. It can be useful when overwriting some files with the
same name.

Reproducible: Always

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

[kdeplasma-addons] [Bug 369172] Plasma crashes, as soon as a new Comic Strip Widget is added

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO
 CC||k...@davidedmundson.co.uk

--- Comment #3 from David Edmundson  ---
It doesn't happen here.

Do you have a backtrace? (the icon in the system tray of a sad face should open
a bug reoprt dialog)

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

[kalarm] [Bug 367805] kalarm crashed editing an alarm

[David Jarvie via KDE Bugzilla]

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

--- Comment #2 from David Jarvie  ---
*** Bug 369113 has been marked as a duplicate of this bug. ***

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

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

[Philippe Waroquiers via KDE Bugzilla]

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

Philippe Waroquiers  changed:

   What|Removed |Added

 CC||philippe.waroquiers@skynet.
   ||be

--- Comment #14 from Philippe Waroquiers  ---
Quickly read the last version of the patch, sorry for entering in the game so
late

Some comments:

* Typo in the xml documentation:  alocator

* lines like below:  opening brace should be on the same line
+ if (MC_(is_mempool_block)(ch1))
+ {

* for detecting/reporting/asserting the overlap condition
   in case ch1_is_meta != ch2_is_meta, I am wondering if we should not check
   that the non meta block is (fully) inside the meta block.
   It looks to be an error if the non meta block is not fully inside the meta
block.

*  free_mallocs_in_mempool_block : this looks to be an algorithm that will be
O (n * m)   when n is the nr of malloc-ed blocks, and m is the nr of blocks
covered
by Start/End address. That might be very slow for big applications, that
allocates millions
of blocks, e.g. 1 million normal block, and one million blocks in meta
blocks
will take a lot of time to cleanup ?

Thanks

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

[kalarm] [Bug 369113] kalarm crashed editing a displayed alarm

[David Jarvie via KDE Bugzilla]

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

David Jarvie  changed:

   What|Removed |Added

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

--- Comment #1 from David Jarvie  ---
This seems to be a Qt bug. See bug 367805 for more information.

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

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

[kwin] [Bug 369068] Add tiling to KWin

[Piotr Dobrogost via KDE Bugzilla]

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

Piotr Dobrogost  changed:

   What|Removed |Added

 CC||p...@bugs.kde.dobrogost.net

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

[kdeplasma-addons] [Bug 369172] Plasma crashes, as soon as a new Comic Strip Widget is added

[Michał Dybczak via KDE Bugzilla]

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

Michał Dybczak  changed:

   What|Removed |Added

 CC||michal.dybc...@gmail.com

--- Comment #1 from Michał Dybczak  ---
I confirm, have this bug too.

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

[plasmashell] [Bug 369173] New: OSD (on screen display) settings missing

[via KDE Bugzilla]

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

Bug ID: 369173
   Summary: OSD (on screen display) settings missing
   Product: plasmashell
   Version: 5.7.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slartibar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

I am pretty sure i have already seen some settings for the configuration of the
OSD popups, like
- audio volume (using media keys)
- brightness (using hardware keys)
- mic on/off
etc.

There had been options for the size of the OSD and the time it was shown before
it faded away.
I was looking through (hopefully) all systemsettings entries and investigated
in every option to kcmshell4 and kcmshell5 but it's gone...

Am i missing something or has it disappeared in 5.7.x ?
Any hint would be appreciated :-)

Reproducible: Always

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

[marble] [Bug 368167] crash on startup in geoiface QMutex::lock [cause: digikamrc]

[Jens B . Benecke via KDE Bugzilla]

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

--- Comment #6 from Jens B. Benecke  ---
Marble with OSM map works perfectly.

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

[kdeplasma-addons] [Bug 369172] Plasma crashes, as soon as a new Comic Strip Widget is added

[Huw via KDE Bugzilla]

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

--- Comment #2 from Huw  ---
Confirmed (mine is the OpenSUSE system referenced in OP).  Exactly the same
behaviour, 100% reproducible.

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

[plasmashell] [Bug 369173] OSD (on screen display) settings missing

[via KDE Bugzilla]

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

--- Comment #1 from slartibar...@gmail.com ---
maybe helpful: the computer i was referring to (media/hardware keys) is a
lenovo laptop t420.
I am using the fn- keys or the special media keys of this machine for the
osd popups to appear.

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

[kdeplasma-addons] [Bug 369172] Plasma crashes, as soon as a new Comic Strip Widget is added

[Huw via KDE Bugzilla]

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

Huw  changed:

   What|Removed |Added

 CC||h...@synapticsilence.net

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

[kdeplasma-addons] [Bug 369172] New: Plasma crashes, as soon as a new Comic Strip Widget is added

[melkor333 via KDE Bugzilla]

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

Bug ID: 369172
   Summary: Plasma crashes, as soon as a new Comic Strip Widget is
added
   Product: kdeplasma-addons
   Version: 5.7.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Comic Applet
  Assignee: notm...@gmail.com
  Reporter: sam...@ton-kunst.ch

Whenever I try to add the Comic Strip Widget to my Desktop (or a Panel), plasma
workspace crashes and instantly restarts.

Testet on:

Platform: Manjaro Linux (built upon arch linux)
KDE Plasma Version: 5.7.5
KDE Frameworks Version: 5.26.0
QT Version: 5.7
Kernel Version: 4.4.21-1-MANJARO 64-bit

It has also been tested (not by me) on:
Platform: OpenSUSE Leap 42.1 (64-bit)
kde plasma Version: 5.5.5
QT Version:  5.5.1.

Reproducible: Always

Steps to Reproduce:
1. Right click on the desktop -> + Add Widgets...
2. Scroll down to the comic Strip widget (the icon is a big smiley)
3. Drag it to the one side of the desktop/into a panel

Actual Results:  
Plasma workspace crashes and restart instantly, The widget never appears

Expected Results:  
The Widget should be added to the Desktop/Panel and I should be able to chose a
comic.

This is the output of my journalctl about the crash:

Sep 21 20:07:59 Mario plasmashell[2755]: adding "org.kde.plasma.comic"
Sep 21 20:07:59 Mario plasmashell[2755]: QQuickItem::ungrabMouse(): Item is not
the mouse grabber.
Sep 21 20:07:59 Mario plasmashell[2755]: The file 
"/home/sam/.local/share/knewstuff3/comic.knsregistry"  could not be opened.
Sep 21 20:08:00 Mario kdeinit5[2653]: Service 
"org.kde.StatusNotifierHost-2755" unregistered
Sep 21 20:08:00 Mario konversation[3685]: org.kde.knotifications: env says KDE
is running but SNI unavailable -- check KDE_FULL_SESSION and
XDG_CURRENT_DESKTOP
Sep 21 20:08:00 Mario msm_kde_notifier[2806]: org.kde.knotifications: env says
KDE is running but SNI unavailable -- check KDE_FULL_SESSION and
XDG_CURRENT_DESKTOP
Sep 21 20:08:00 Mario octopi-notifier[2807]: org.kde.knotifications: env says
KDE is running but SNI unavailable -- check KDE_FULL_SESSION and
XDG_CURRENT_DESKTOP
Sep 21 20:08:00 Mario drkonqi[4768]: found lsb_release
Sep 21 20:08:00 Mario drkonqi[4768]: Using /proc to determine executable path
Sep 21 20:08:00 Mario drkonqi[4768]: Executable is: "/usr/bin/plasmashell"
Sep 21 20:08:00 Mario drkonqi[4768]: Executable exists: true
Sep 21 20:08:00 Mario drkonqi[4768]: Enabling drkonqi crash catching
Sep 21 20:08:00 Mario drkonqi[4768]: XSync seems available and ready
Sep 21 20:08:00 Mario drkonqi[4768]: XSync Inited
Sep 21 20:08:00 Mario drkonqi[4768]: Supported, init completed
Sep 21 20:08:00 Mario drkonqi[4768]: Created alarm 75497473
Sep 21 20:08:00 Mario kdeinit5[2653]: Registering
"org.kde.StatusNotifierItem-4768-1/StatusNotifierItem" to system tray
Sep 21 20:08:01 Mario plasmashell[4767]: No metadata file in the package,
expected it at: "/home/sam/Desktop/"
Sep 21 20:08:01 Mario plasmashell[4767]: No metadata file in the package,
expected it at: "/home/sam/Desktop/"
Sep 21 20:08:01 Mario plasmashell[4767]: No metadata file in the package,
expected it at: "/home/sam/Desktop/"
Sep 21 20:08:01 Mario plasmashell[4767]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:80:
TypeError: Cannot read property 'formFactor' of null
Sep 21 20:08:01 Mario plasmashell[4767]: libpng warning: iCCP: known incorrect
sRGB profile
Sep 21 20:08:01 Mario plasmashell[4767]: libpng warning: iCCP: known incorrect
sRGB profile
Sep 21 20:08:01 Mario plasmashell[4767]: libpng warning: iCCP: known incorrect
sRGB profile
Sep 21 20:08:01 Mario plasmashell[4767]: Could not resolve property :
radialGradient4782
Sep 21 20:08:01 Mario plasmashell[4767]: Could not resolve property :
radialGradient4857
Sep 21 20:08:01 Mario plasmashell[4767]: Could not resolve property :
radialGradient4883
Sep 21 20:08:01 Mario plasmashell[4767]: Could not resolve property :
radialGradient4885
Sep 21 20:08:01 Mario plasmashell[4767]: Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Sep 21 20:08:02 Mario plasmashell[4767]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:41:
TypeError: Cannot read property 'length' of unde
Sep 21 20:08:02 Mario plasmashell[4767]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/Tooltip.qml:43:
TypeError: Cannot read property 'timeFormat' of null
Sep 21 20:08:02 Mario plasmashell[4767]: Both point size and pixel size set.
Using pixel size.
Sep 21 20:08:02 Mario plasmashell[4767]: Both point size and pixel size set.
Using pixel size.
Sep 21 20:08:02 Mario plasmashell[4767]: Both point size and pixel size set.
Using pixel size.
Sep 21 20:08:02 Mario plasmashell[4767]: Both point size and pixel size set.
Using pixel 

[Oxygen] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #15 from Wolfgang Bauer  ---
(In reply to Wolfgang Bauer from comment #14)
> PS: in KDE4 those particular icons were taken from
> icons/plasma-networkmanagement2.svgz it seems, but this file is missing in
> Plasma5/plasma-framework.

Actually this file was part of plasma-nm itself in KDE4, but apparently it has
been decided to move the icons over to plasma-framework/network.svgz for
Plasma5.

It's here in git btw:
https://quickgit.kde.org/?p=plasma-nm.git=tree=8a0acc5aa3c0081d71c3c01bcf9de29acad51b78=c62c0cbf19f55d0598fc868563c22386c3db9355=applet%2Ficons

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

[dolphin] [Bug 361694] The search (Find) function in Dolphin is useless, doesn't return results as it should

[via KDE Bugzilla]

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

stu109...@mail.uni-kiel.de changed:

   What|Removed |Added

 CC||stu109...@mail.uni-kiel.de

--- Comment #8 from stu109...@mail.uni-kiel.de ---
I don't get it. Why was this baloo stuff  introduced in the first place? What
is the expected benefit?
Wouldn't it be way simpler (and more stable) to implement the dolphin search as
a fontend for the "find" command?
Something like "find . -iname *mysearchterm*" and the result is just displayed
by dolphin.

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

[frameworks-baloo] [Bug 369171] New: Crash durint reboot

[Vince Radice via KDE Bugzilla]

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

Bug ID: 369171
   Summary: Crash durint reboot
   Product: frameworks-baloo
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: pinak.ah...@gmail.com
  Reporter: vhrad...@cfl.rr.com

Application: baloo_file_extractor (5.26.0)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.3-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
rebooting pc
Received message baloo crashed unexpectedly.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3b8e7038c0 (LWP 1872))]

Thread 3 (Thread 0x7f3b71203700 (LWP 1927)):
#0  0x7f3b8b6943ed in poll () at /lib64/libc.so.6
#1  0x7f3b8a273a06 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f3b8a273b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f3b8c49924b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f3b8c4485ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f3b8c2a7343 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f3b8e81f559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f3b8c2ab99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f3b8abe95ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f3b8b69ff6d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f3b794a4700 (LWP 1874)):
#0  0x7f3b8b6943ed in poll () at /lib64/libc.so.6
#1  0x7f3b861f3f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f3b861f5b79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f3b7d7b6da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f3b8c2ab99a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f3b8abe95ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f3b8b69ff6d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f3b8e7038c0 (LWP 1872)):
[KCrash Handler]
#6  0x7f3b738a8a18 in Exiv2::ValueType::toLong(long) const ()
at /lib64/libexiv2.so.14
#7  0x7f3b7805523b in
KFileMetaData::Exiv2Extractor::add(KFileMetaData::ExtractionResult*,
Exiv2::ExifData const&, KFileMetaData::Property::Property, char const*,
QVariant::Type) () at
/usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
#8  0x7f3b78055a06 in
KFileMetaData::Exiv2Extractor::extract(KFileMetaData::ExtractionResult*) () at
/usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
#9  0x55a4280e9e0b in Baloo::App::index(Baloo::Transaction*, QString
const&, unsigned long long) ()
#10 0x55a4280ea2de in Baloo::App::processNextFile() ()
#11 0x7f3b8c47dd16 in QSingleShotTimer::timerEvent(QTimerEvent*) () at
/lib64/libQt5Core.so.5
#12 0x7f3b8c472b8b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#13 0x7f3b8ccdcc0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#14 0x7f3b8cce20ef in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#15 0x7f3b8c4497aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#16 0x7f3b8c4987ab in QTimerInfoList::activateTimers() () at
/lib64/libQt5Core.so.5
#17 0x7f3b8c498d39 in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#18 0x7f3b8a2736ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#19 0x7f3b8a273a70 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#20 0x7f3b8a273b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#21 0x7f3b8c49922f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#22 0x7f3b8c4485ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#23 0x7f3b8c45017c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#24 0x55a4280e920f in main ()

Reported using DrKonqi

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

[dolphin] [Bug 357762] Opening root folder in Dolphin hangs entire system (Macbook 8,1) indefinitely.

[via KDE Bugzilla]

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

stu109...@mail.uni-kiel.de changed:

   What|Removed |Added

 CC||stu109...@mail.uni-kiel.de

--- Comment #2 from stu109...@mail.uni-kiel.de ---
*** Bug 362414 has been marked as a duplicate of this bug. ***

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

[kio] [Bug 362414] Complete system crash when accessing the file system root in an application (e.g. Dolphin, Gewnview, Eclipse)

[via KDE Bugzilla]

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

stu109...@mail.uni-kiel.de changed:

   What|Removed |Added

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

--- Comment #2 from stu109...@mail.uni-kiel.de ---


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

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

[kio] [Bug 362414] Complete system crash when accessing the file system root in an application (e.g. Dolphin, Gewnview, Eclipse)

[via KDE Bugzilla]

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

--- Comment #1 from stu109...@mail.uni-kiel.de ---
Issue persists in LinuxMint 18 (Kubuntu 16.04)

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

[Oxygen] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #14 from Wolfgang Bauer  ---
PS: in KDE4 those particular icons were taken from
icons/plasma-networkmanagement2.svgz it seems, but this file is missing in
Plasma5/plasma-framework.

Just copying over that file doesn't help, but it should not be difficult to add
the missing icons from there to network.svgz I suppose...

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

[kio] [Bug 336397] Getting "Unknown error code 150" when opening USB connected Android device in MTP mode

[lbickley via KDE Bugzilla]

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

lbickley  changed:

   What|Removed |Added

 CC||lbick...@bickleywest.com

--- Comment #3 from lbickley  ---
This fails in the same manner with OpenSUSE Leap 42.1, KDE Plasma Version:
5.5.5, OS Type: 64-bit. - connecting to Samsung Galaxy S7 via USB.

Dolphin initially shows proper directories and files - but get a "150 error" on
any attempt to transfer files.

Can be duplicated easily. Connect Samsung Galaxy phone via USB to Linux
workstation. Use Dolphin as file manager to look at Samsung files. Attempt to
transfer file to desktop. After "150 error" occurs file access fails as well.

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

[krita] [Bug 369165] JJ: An option in the existing context menu to add the image as file layer when dragging an image in open document

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
   Keywords||junior-jobs
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
Summary|[Wishbug] An option in the  |JJ: An option in the
   |existing context menu to|existing context menu to
   |add the image as file layer |add the image as file layer
   |when dragging an image in   |when dragging an image in
   |open document   |open document

--- Comment #1 from Boudewijn Rempt  ---
Good point, and would be easy enough to do.

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

[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor

[Michael via KDE Bugzilla]

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

Michael  changed:

   What|Removed |Added

 CC||miga_m...@gmx.de

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

[Breeze] [Bug 363602] Symlinked SVG files fails to load under Windows

[Jasem Mutlaq via KDE Bugzilla]

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

Jasem Mutlaq  changed:

   What|Removed |Added

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

--- Comment #6 from Jasem Mutlaq  ---
This seems to have been fixed

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

[Breeze] [Bug 364981] Some breeze icons for KStars are inappropiate

[Jasem Mutlaq via KDE Bugzilla]

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

--- Comment #8 from Jasem Mutlaq  ---
Hello, any update on this? I realize you guys are busy, but if there this
cannot be done, then we will include our own icons in the resource file and
discard breeze icons.

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

[bugs.kde.org] [Bug 368988] "My Requests" menu always shows empty list

[Frédéric Sheedy via KDE Bugzilla]

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

Frédéric Sheedy  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Frédéric Sheedy  ---
Confirmed.

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

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #4 from Mark Wielaard  ---
The diffs are the same because the none/tests/ppc64/jm_int_isa_2_07.stdout.exp
and none/tests/ppc64/jm_int_isa_2_07.stdout.exp-LE expect files are the same.

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

[kactivitymanagerd] [Bug 369170] New: Cannot launch applications. Clicking on icon doesn't do anything. Then the desktop freezes

[Joffroy Urbain via KDE Bugzilla]

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

Bug ID: 369170
   Summary: Cannot launch applications. Clicking on icon doesn't
do anything. Then the desktop freezes
   Product: kactivitymanagerd
   Version: 5.7.95
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: urbain.joff...@gmail.com
CC: plasma-b...@kde.org

Tried to launch Dolphin and Digikam without success. Konsole seems to work.
Randomly the desktop freezes, no response from the mouse/keyboard.

dmesg gives this:
[  292.448030] kactivitymanage[2145]: segfault at 7f253e95ad10 ip
7f253e9743b1 sp 7ffe9db42bb8 error 4 in
libQt5Sql.so.5.6.1[7f253e95c000+47000]
[  292.517400] QDBusConnection[2954]: segfault at 7fe32e2be030 ip
7fe347fccd1f sp 7fe32fba79d0 error 4 in
libQt5Core.so.5.6.1[7fe347d11000+4c9000]
[  292.670764] QDBusConnection[2591]: segfault at 7f1cdede5260 ip
7f1d076ecd1f sp 7f1cee8bf9d0 error 4 in
libQt5Core.so.5.6.1[7f1d07431000+4c9000]
[  292.682442] QDBusConnection[2617]: segfault at 7ff3fbbadfc0 ip
7ff43b0e2d1f sp 7ff4173ef950 error 4 in
libQt5Core.so.5.6.1[7ff43ae27000+4c9000]


Reproducible: Always

Steps to Reproduce:
1. Click on icon
2. Application appears in taskbar
3. Application disappears from taskbar without showing a window

Actual Results:  
No window opens

Expected Results:  
Opening application

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

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #3 from Mark Wielaard  ---
Created attachment 101220
  --> https://bugs.kde.org/attachment.cgi?id=101220=edit
diff with LE expected output

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

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #2 from Mark Wielaard  ---
Created attachment 101219
  --> https://bugs.kde.org/attachment.cgi?id=101219=edit
diff with expected output

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

[valgrind] [Bug 369169] ppc64 fails jm_int_isa_2_07 test

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101218
  --> https://bugs.kde.org/attachment.cgi?id=101218=edit
test output

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

[valgrind] [Bug 369169] New: ppc64 fails jm_int_isa_2_07 test

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369169
   Summary: ppc64 fails jm_int_isa_2_07 test
   Product: valgrind
   Version: 3.12 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com

On ppc32 and ppc64le the jm_int_isa_2_07 test passes.
But on ppc64[be] ./none/tests/ppc64/jm_int_isa_2_07.stdout.out doesn't match
either the jm_int_isa_2_07.stdout.exp or jm_int_isa_2_07.stdout.exp-LE

This system has:
gcc-4.8.5-11.el7.ppc64
binutils-2.25.1-22.base.el7.ppc64
glibc-2.17-157.el7.ppc64
glibc-2.17-157.el7.ppc
kernel-3.10.0-508.el7.ppc64

processor   : 0
cpu : POWER8 (architected), altivec supported
clock   : 3425.00MHz
revision: 2.1 (pvr 004b 0201)

timebase: 51200
platform: pSeries
model   : IBM,8247-22L
machine : CHRP IBM,8247-22L

Reproducible: Always

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

[kdevelop] [Bug 369168] New: Clang Child Diagnostics can contain relative paths

[Milian Wolff via KDE Bugzilla]

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

Bug ID: 369168
   Summary: Clang Child Diagnostics can contain relative paths
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@milianw.de

Application: kdevelop (5.0.1)
 (Compiled from sources)
Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.7.2-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
I looked at an error in a template triggered by some other file that included a
header and tried to instantiate it incorrectly.

Clang created child diagnostics that referred to some files in the child
diagnostics with relative paths. Clicking on them in the problem view triggers
assertions.

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7febd9341840 (LWP 29285))]

Thread 15 (Thread 0x7feb24fab700 (LWP 31639)):
#0  0x7febc845010f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7febc9c29ac4 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7febc9c29b09 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7febc844a454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7febd193f7df in clone () from /usr/lib/libc.so.6

Thread 14 (Thread 0x7feb27fff700 (LWP 29369)):
#0  0x7febd19324ed in read () from /usr/lib/libc.so.6
#1  0x7febc5eaebc0 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7febc5e6bb36 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7febc5e6c004 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7febc5e6c17c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7febd277359b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#6  0x7febd271d0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#7  0x7febd25400f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x7febcfb45a64 in KDevelop::CompletionWorkerThread::run
(this=0x45c9c20) at
/home/milian/projects/kf5/src/extragear/kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:89
#9  0x7febd2544d78 in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7febc844a454 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7febd193f7df in clone () from /usr/lib/libc.so.6

Thread 13 (Thread 0x7feb62ffe700 (LWP 29330)):
#0  0x7febc5e6b553 in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#1  0x7febc5e6bf8b in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7febc5e6c17c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7febd277359b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7febd271d0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7febd25400f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7febd2544d78 in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7febc844a454 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7febd193f7df in clone () from /usr/lib/libc.so.6

Thread 12 (Thread 0x7feb7a868700 (LWP 29320)):
#0  0x7febc845010f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7febd2545c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7febce6157be in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=0x1db90c0, th=0x7feb74003450) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:594
#3  0x7febce6153d8 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=, th=0x80, threadWasBusy=, suspendIfInactive=, justReturning=) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:554
#4  0x7febce61a2c0 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1db9210, th=0x7feb74003450, wasBusy=false) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:66
#5  0x7febce61a4d0 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:61
#6  0x7febce61596e in ThreadWeaver::Weaver::applyForWork (this=, th=0x35e1, wasBusy=false) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/weaver.cpp:568
#7  0x7febce61a3ff in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1db9210, th=0x7feb74003450, wasBusy=false) at
/home/milian/projects/kf5/src/frameworks/threadweaver/src/workinghardstate.cpp:73
#8  0x7febce61a4d0 in non-virtual thunk to
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, 

[kdevelop] [Bug 369168] Clang Child Diagnostics can contain relative paths [ASSERT: "!inputUrl.isRelative()"]

[Milian Wolff via KDE Bugzilla]

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

Milian Wolff  changed:

   What|Removed |Added

   Priority|NOR |VHI
Summary|Clang Child Diagnostics can |Clang Child Diagnostics can
   |contain relative paths  |contain relative paths
   ||[ASSERT:
   ||"!inputUrl.isRelative()"]
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[plasmashell] [Bug 366732] Clicking active task doesn't minimize window when window housing delegate takes focus on mouse press (desktop, group popup)

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

Summary|Taskmanager minimize|Clicking active task
   |doesn't work when outside a |doesn't minimize window
   |panel   |when window housing
   ||delegate takes focus on
   ||mouse press (desktop, group
   ||popup)

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

[plasmashell] [Bug 366732] Clicking active task doesn't minimize window when window housing delegate takes focus on mouse press (desktop, group popup)

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 CC||cf...@kde.org

--- Comment #4 from Eike Hein  ---
*** Bug 368459 has been marked as a duplicate of this bug. ***

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

[bugs.kde.org] [Bug 335654] reported versions of several applications are not registered on bugs.kde.org

[Denis Kurz via KDE Bugzilla]

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

--- Comment #10 from Denis Kurz  ---
Since the PIM guys seem to be determined to stick to their internal version
numbers, can we agree for the moment on versions like "5.3.0 (KDE Applications
16.08.0)"? I learned in #kde-sysadmin that admins have the option to rename
existing versions. That would also be helpful for KOrganizer and Akonadi, for
example to rename KOrganizer "15.08.0" to "5.0 (KDE Applications 15.08.0)". If
we agree on this (interim?) solution, I would compile a list of version
translations for Akonadi and Korganizer, and a new list of requested versions.

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

[plasmashell] [Bug 368459] Group menu steals focus, cannot hide window

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Eike Hein  ---


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

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

[plasmashell] [Bug 369167] New: [Feature Request] - change app's icon from the icons-only app pop up menu

[Michail Vourlakos via KDE Bugzilla]

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

Bug ID: 369167
   Summary: [Feature Request] - change app's icon from the
icons-only app pop up menu
   Product: plasmashell
   Version: 5.7.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: mvourla...@gmail.com
CC: plasma-b...@kde.org

There is the following idea in the forums...

-
say you see Speedcrunch' launcher icon being ugly, knowing KDE you can go to
kmenuedit, guess which is its category or go through different ones to find its
entry and then change it. Alternatively you can replace the icon manually on
filesystem level. But from the usability or friendliness to newcomers
standpoint, it would be neat to just right click on an icons-only appicon (in
the taskmanager) and select "change icon"...
-

I found it very interesting...

Reproducible: Always

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

[plasmashell] [Bug 369166] Executable: plasmashell PID: 2122 Signal: Segmentation fault (11)

[Alain via KDE Bugzilla]

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

Alain  changed:

   What|Removed |Added

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

--- Comment #1 from Alain  ---
Solved issue by reinstalling NVIDIA proprietere drivers

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

[kdenlive] [Bug 369123] If a clip in timeline is grouped (video+audio) remove space don't work and this warning appear "cannot remove space in a track with a group."

[Doru via KDE Bugzilla]

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

--- Comment #1 from Doru  ---
Created attachment 101217
  --> https://bugs.kde.org/attachment.cgi?id=101217=edit
Screenshot with the space that can not be removed

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

[plasmashell] [Bug 369166] New: Executable: plasmashell PID: 2122 Signal: Segmentation fault (11)

[Alain via KDE Bugzilla]

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

Bug ID: 369166
   Summary: Executable: plasmashell PID: 2122 Signal: Segmentation
fault (11)
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: alai...@gmx.net
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Happens now every time, whenever I start the system: Yesterday it was all
normal.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f5a4edb7700 (LWP 2177)):
#0  0x7f5a655f7ccd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f5a61d19b60 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f5a4edb6bf0, __fd=) at /usr/include/bits/unistd.h:44
#2  0x7f5a61d19b60 in g_wakeup_acknowledge (wakeup=0x7f5a500015b0) at
gwakeup.c:210
#3  0x7f5a61cd8999 in g_main_context_check
(context=context@entry=0x7f5a48000990, max_priority=2147483647,
fds=fds@entry=0x7f5a48003070, n_fds=n_fds@entry=1) at gmain.c:3600
#4  0x7f5a61cd8df8 in g_main_context_iterate
(context=context@entry=0x7f5a48000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3805
#5  0x7f5a61cd8f7c in g_main_context_iteration (context=0x7f5a48000990,
may_block=1) at gmain.c:3869
#6  0x7f5a65f28d8b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f5a480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7f5a65ecfd53 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f5a4edb6df0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#8  0x7f5a65cf161a in QThread::exec() (this=this@entry=0x1f19440) at
thread/qthread.cpp:503
#9  0x7f5a69005e18 in QQmlThreadPrivate::run() (this=0x1f19440) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#10 0x7f5a65cf632f in QThreadPrivate::start(void*) (arg=0x1f19440) at
thread/qthread_unix.cpp:331
#11 0x7f5a64e050a4 in start_thread (arg=0x7f5a4edb7700) at
pthread_create.c:309
#12 0x7f5a6560402d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f5a55b28700 (LWP 2162)):
#0  0x7f5a655fbbfd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f5a6a54f422 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f5a55b27d00) at /usr/include/bits/poll2.h:46
#2  0x7f5a6a54f422 in _xcb_conn_wait (c=c@entry=0x1e35c20,
cond=cond@entry=0x1e35c60, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#3  0x7f5a6a55100f in xcb_wait_for_event (c=0x1e35c20) at xcb_in.c:693
#4  0x7f5a57c793c9 in QXcbEventReader::run() (this=0x1e41fd0) at
qxcbconnection.cpp:1229
#5  0x7f5a65cf632f in QThreadPrivate::start(void*) (arg=0x1e41fd0) at
thread/qthread_unix.cpp:331
#6  0x7f5a64e050a4 in start_thread (arg=0x7f5a55b28700) at
pthread_create.c:309
#7  0x7f5a6560402d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f5a6c0f67c0 (LWP 2159)):
[KCrash Handler]
#6  0x7f5a64e0e198 in __lll_unlock_elision () at
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
#7  0x7f5a64e0e198 in __lll_unlock_elision (lock=0x1e3bd20, private=0) at
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#8  0x7f5a6a7aa2d2 in _XError (dpy=dpy@entry=0x1e34860,
rep=rep@entry=0x7ffc6900bfc0) at XlibInt.c:1432
#9  0x7f5a6111f87f in MakeContextCurrent (resource=0, errorCode=0 '\000',
minorCode=26, dpy=0x1e34860) at glxcurrent.c:180
#10 0x7f5a6111f87f in MakeContextCurrent (dpy=0x1e34860, draw=60817417,
read=60817417, gc_user=0x20bf380) at glxcurrent.c:231
#11 0x7f5a54d0c2f0 in QGLXContext::init(QXcbScreen*,
QPlatformOpenGLContext*) (this=0x2029830, screen=,
share=) at qglxintegration.cpp:320
#12 0x7f5a54d0a7cb in
QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const
(this=, context=0x7ffc6900c1d0) at qxcbglxintegration.cpp:187
#13 0x7f5a57c7ac91 in
QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const
(this=, context=0x7ffc6900c1d0) at qxcbintegration.cpp:222
#14 0x7f5a66464c6d in QOpenGLContext::create()
(this=this@entry=0x7ffc6900c1d0) at kernel/qopenglcontext.cpp:594
#15 0x7f5a54d0d1ad in QGLXContext::queryDummyContext() () at
qglxintegration.cpp:661
#16 0x7f5a54d0d321 in QGLXContext::supportsThreading() () at
qglxintegration.cpp:692
#17 0x7f5a69c0ef63 in 

[plasmashell] [Bug 367952] Plasma crash while developing with Gambas

[Cristiano Guadagnino via KDE Bugzilla]

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

--- Comment #9 from Cristiano Guadagnino  ---
David, Gambas was recently updated to v3.9.1 and this release does not show the
reported behavior. I believe this means that the problem was in Gambas itself,
not in KDE.
I think the bug can be closed, if you agree.

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

[krita] [Bug 369165] New: [Wishbug] An option in the existing context menu to add the image as file layer when dragging an image in open document

[Raghavendra kamath via KDE Bugzilla]

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

Bug ID: 369165
   Summary: [Wishbug] An option in the existing context menu to
add the image as file layer when dragging an image in
open document
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: raghavendr.ra...@gmail.com

This is a wish bug request for adding an option in the existing context menu to
add the image as file layer when dragging an image in open document. When a
user drags an image in the document he is presented with a context menu showing
options such as
Insert as new layer
open in new document
etc. I request to add an entry to add the image to open document as a file
layer.

Reproducible: Always

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

[digikam] [Bug 368734] Moving a hierarchy of tags (a tag with subtags) doesn't work and can lead to losing the complete hierarchy

[Marcus Christopher via KDE Bugzilla]

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

--- Comment #10 from Marcus Christopher  ---
Thanks for your help.

Ok, so I removed literally *everything* (configuration files, databases etc.)
that had to do with digikam (version 5.1) and started with a fresh install.

- Started digikam.
- digikam asked me for the directory, where I keep me images. I chose a
directory that contained a few PNG files that have never been in contact with
any version of digikam before.
- I kept the rest of the options at their default, i.e. did not change
anything.
- Once digikam had started up, I immediately opened the Tag Manager.
- I created two top-level tags.
- I then created two subtags for one of the top-level tags.
- I closed digikam.
- I opened digikam again.
- I opened the Tag Manager again.
- I moved the top-level tag that contained the two subtags to under the other
top-level tag. digikam asked me, if I wanted to "move here". I clicked OK.
- I closed digikam.
- I opened digikam again.
- The changes are reverted! The top-level tag that I moved is back where it
was.

Can you reproduce this? Is there anything else that I can try?

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

[kdevelop] [Bug 369164] New: 5.0.1 "pauses" on startup

[OlafLostViking via KDE Bugzilla]

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

Bug ID: 369164
   Summary: 5.0.1 "pauses" on startup
   Product: kdevelop
   Version: git master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com

KDevelop 5.0.1 (not selectable in the dropdown above) shows a strange startup
behaviour. After starting it, the IDE window is created and correctly filled
with content of the last session.

But then it hangs for two or three seconds without updating the screen.
Resizing it via KWin breaks the window content until the next redraw. After
that it behaves snappy as expected.

It looks like the GUI thread runs, after initializing everything, some parser
job or so instead of sending it to the background. But that is speculation...

Anything I can do to give better feedback?

Reproducible: Always

Steps to Reproduce:
1. Start KDevelop.
2. See IDE drawing.
3. Wait some seconds until GUI becomes responsive.

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

[krita] [Bug 369163] New: Merging selected layers results into new layer with merged data instead of merging them into single layer

[Raghavendra kamath via KDE Bugzilla]

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

Bug ID: 369163
   Summary: Merging selected layers results into new layer with
merged data instead of merging them into single layer
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: raghavendr.ra...@gmail.com

This bug introduced in recent master, When a user selects multiple layers then
does merge layer either by menu or shortcut Ctrl + E . The merged pixels are
added to a new layer rather than merging them into one single layers . The
original layers are kept intact.

Reproducible: Always

Steps to Reproduce:
1.Open a document with multiple layers
2.select two or more layers and press ctrl + E

Actual Results:  
new layer is created with merged data without merging exisiting layer

Expected Results:  
merged data should be in one single layer and all other selected layer should
not be there.

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

[Oxygen] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #12 from Wolfgang Bauer  ---
(In reply to Dainius Masiliūnas from comment #11)
> If the icon is there in the icon theme, then it might be a Plasma or
> plasma-nm issue.

It's not in the icon theme either.
plasma-nm uses network-flightmode-on/network-flightmode-off and
network-wireless-on/network-wireless-off as icons for the two mentioned
buttons.
I can find neither of those in the breeze nor oxygen icon themes...

> The network.svgz file itself is provided by
> plasma-framework, hm.

Yes, this is part of the *desktop* theme.

Plasma's behavior is as follows according to my experience:
First, it tries to load the icon from network.svgz (in this case) from the
configured *desktop* theme.
If network.svgz does not exist, it uses network.svgz from the default *desktop*
theme (breeze) instead.
If network.svgz does exist but doesn't contain that specific icon, it tries to
load it from the *icon* theme instead.

So in this case, the icon should also be found if it was part of the icon
theme, but it isn't either.

The main problem is that the Air and Oxygen desktop themes haven't been
updated/adjusted to changes in other parts of Plasma (and plasma-nm), they are
incomplete.

network.svgz was missing completely from those themes for a while, which would
make it work.
IOW, if you delete network.svgz, the icon would show up, taken from breeze.

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

[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours

[J . O . Aho via KDE Bugzilla]

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

--- Comment #5 from J.O. Aho  ---
Created attachment 101216
  --> https://bugs.kde.org/attachment.cgi?id=101216=edit
The result of "thread apply all bt"

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

[plasmashell] [Bug 369099] When running multiple sessions at the same time, :1+ crashes after some hours

[J . O . Aho via KDE Bugzilla]

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

--- Comment #4 from J.O. Aho  ---
Created attachment 101215
  --> https://bugs.kde.org/attachment.cgi?id=101215=edit
The output generated while running plasma in gdb

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

[Oxygen] [Bug 368660] Wireless and aeroplane mode Oxygen icons missing in plasma-nm

[Wolfgang Bauer via KDE Bugzilla]

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

--- Comment #13 from Wolfgang Bauer  ---
(In reply to pinheiro from comment #10)
> http://wstaw.org/m/2016/09/21/plasma-desktopJi7326.png here

This looks like KDE4.
It worked there, yes.

But this bug report is about Plasma5.

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

[dolphin] [Bug 354301] Shift key toggles "delete" and "move to trash" entries the wrong order

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/dolp
   ||hin/3775ef19eaca057985b92cf
   ||a3716d3c3a1d22f0f
   Version Fixed In||16.08.2

--- Comment #5 from Elvis Angelaccio  ---
Git commit 3775ef19eaca057985b92cfa3716d3c3a1d22f0f by Elvis Angelaccio.
Committed on 21/09/2016 at 16:13.
Pushed by elvisangelaccio into branch 'Applications/16.08'.

Properly check Shift toggling in DolphinRemoveAction

Documentation of QGuiApplication::keyboardModifiers() says that "It should
be noted this may not reflect the actual keys held on the input device at
the time of calling but rather the modifiers as last reported in one of
the above events".

Since this method is called in DolphinContextMenu's keyPressEvent()
and keyReleaseEvent(), the first time that keyboardModifiers() is
called it doesn't report that shift has been pressed.

Replacing this method with queryKeyboardModifiers() does the job
because the latter doesn't care about the event queue.
FIXED-IN: 16.08.2
REVIEW: 128972

M  +1-1src/dolphinremoveaction.cpp

http://commits.kde.org/dolphin/3775ef19eaca057985b92cfa3716d3c3a1d22f0f

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

[kontact] [Bug 369162] New: Reading Email, Kontact Crashes

[Nathan Wolf via KDE Bugzilla]

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

Bug ID: 369162
   Summary: Reading Email, Kontact Crashes
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: future...@delorean.net

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
Selected within the email to show in HTML. A short pause and then Kontact
crashes. This happens every time.

The crash can be reproduced every time.

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

Thread 35 (Thread 0x7fe602c69700 (LWP 18326)):
#0  0x7fe75945f10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe659827353 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe659b5d971 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe759459454 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe75d5b43ff in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7fe60346a700 (LWP 18325)):
#0  0x7fe75945f10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe659826201 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe659b5d971 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe759459454 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe75d5b43ff in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7fe644180700 (LWP 18324)):
#0  0x7fe75945f10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe659b2cc4b in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe659b2cc89 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe759459454 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe75d5b43ff in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7fe64586d700 (LWP 18291)):
#0  0x7fff7fbaeb74 in clock_gettime ()
#1  0x7fe75d5c12a6 in clock_gettime () from /lib64/libc.so.6
#2  0x7fe75df68d96 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x7fe75e0e8639 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#4  0x7fe75e0e8be5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fe75e0e9f9e in ?? () from /usr/lib64/libQt5Core.so.5
#6  0x7fe758808569 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#7  0x7fe758808f3b in ?? () from /usr/lib64/libglib-2.0.so.0
#8  0x7fe75880912c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#9  0x7fe75e0eaaab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#10 0x7fe75e0926fa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#11 0x7fe75deb83c3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#12 0x7fe75debd2e8 in ?? () from /usr/lib64/libQt5Core.so.5
#13 0x7fe759459454 in start_thread () from /lib64/libpthread.so.0
#14 0x7fe75d5b43ff in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7fe646daa700 (LWP 18148)):
#0  0x7fe75d5a775d in read () from /lib64/libc.so.6
#1  0x7fe75884bc00 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fe758808ae6 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fe758808fb4 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7fe75880912c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7fe75e0eaaab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7fe75e0926fa in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7fe75deb83c3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7fe75debd2e8 in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7fe759459454 in start_thread () from /lib64/libpthread.so.0
#10 0x7fe75d5b43ff in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7fe649bd6700 (LWP 18126)):
#0  0x7fff7fbaeb74 in clock_gettime ()
#1  0x7fe75d5c12a6 in clock_gettime () from /lib64/libc.so.6
#2  0x7fe75df68d96 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x7fe75e0e8639 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#4  0x7fe75e0e8be5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fe75e0e9f9e in ?? () from /usr/lib64/libQt5Core.so.5
#6  0x7fe758808569 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#7  0x7fe758808f3b in ?? () from /usr/lib64/libglib-2.0.so.0
#8  0x7fe75880912c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#9  0x7fe75e0eaaab in

[bugs.kde.org] [Bug 369148] CA StartCom should not be trusted please use Let's Encrypt

[Boudhayan Gupta via KDE Bugzilla]

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

Boudhayan Gupta  changed:

   What|Removed |Added

 CC||m...@baloneygeek.com

--- Comment #6 from Boudhayan Gupta  ---
We're not going to throw our entire server infrastructure out of the window and
start afresh simply to accomodate a new CA. I've tried to implement LetsEncrypt
on our servers in the past (we've had this discussion internally way before you
thought you'd file a bug and we've actually tried testing it on live systems)
but the effort just isn't worth it.

Maybe as we move to immutable infrastructure in the future we will revisit this
topic of contention, but right now there are more pressing tasks that need to
be taken care of.

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

[krita] [Bug 369161] New: ext_qt (5.7) build fails with Xcode 8 + macOS Sierra

[Patrice Kouame via KDE Bugzilla]

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

Bug ID: 369161
   Summary: ext_qt (5.7) build fails with Xcode 8 + macOS Sierra
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: pkou...@mac.com

- Qt 5.7 and Xcode 8 no longer mix well
- this is a confirmed Qt bug. See (for example)
https://bugreports.qt.io/browse/QTBUG-55649?jql=text%20~%20%22xcode%208%22
among many reported issues.
- master krita/3rdparty/ext_qt on macOS pulls down opensource 5.7 to patch
- configure/build attempt will halt with:

Xcode not set up properly. You may need to confirm the license
   agreement by running /usr/bin/xcodebuild without arguments.

- misleading since it's not a licensing or xcode setup issue
- In fact, Qt attempts to validate your xcode installation using a now outdated
statement: "xcrun -find xcrun".  
- It should now use "xcrun -find xcodebuild" instead.

- I am researching Qt bug reports to surmize whether the fix is publically
available yet. Possibly qt 5.7.
- Not sure if latest macOS Sierra (Released) is a factor yet, but I register
many troublesome warnings which I am discussing with the Qt crew.

- meanwhile I have a tested patch ready, just in case...

Patrice

Reproducible: Always

Steps to Reproduce:
1. from 3rdparty extensions build directory
2. cmake --build . --config RelWithDebInfo --target ext_qt 
2.
3.

Actual Results:  
Xcode not set up properly. You may need to confirm the license
   agreement by running /usr/bin/xcodebuild without arguments.

make[3]: *** [ext_qt/ext_qt-prefix/src/ext_qt-stamp/ext_qt-configure] Error 2
make[2]: *** [ext_qt/CMakeFiles/ext_qt.dir/all] Error 2
make[1]: *** [ext_qt/CMakeFiles/ext_qt.dir/rule] Error 2
make: *** [ext_qt] Error 2


Expected Results:  
to build

Good news is : after a successfull rebuild, better macOS openGL compatibility
3.0.2 for krita 3.0.2 beta and beyond.

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

[krita] [Bug 369161] ext_qt (5.7) build fails with Xcode 8 + macOS Sierra

[Patrice Kouame via KDE Bugzilla]

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

--- Comment #1 from Patrice Kouame  ---
Created attachment 101212
  --> https://bugs.kde.org/attachment.cgi?id=101212=edit
patches defaults_pre.prf

in qtbase/mkspecs/features/mac

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

[krita] [Bug 369161] ext_qt (5.7) build fails with Xcode 8 + macOS Sierra

[Patrice Kouame via KDE Bugzilla]

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

--- Comment #4 from Patrice Kouame  ---
Created attachment 101214
  --> https://bugs.kde.org/attachment.cgi?id=101214=edit
cmake fix for invalid module qtenginio

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

[kdeconnect] [Bug 369098] Can't mount remote filesystem with some ssh_config options.

[Le Baron d'Merde via KDE Bugzilla]

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

--- Comment #5 from Le Baron d'Merde  ---
Patch applied, and working as expected. :-)

Thanks!

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

[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO

[Marvin Jens via KDE Bugzilla]

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

--- Comment #12 from Marvin Jens  ---
But since there seems to be a lot of magic happening at runtime with Qt and the
FileDialog, I am not even sure the problem is with kate itself (or its source
code). However, I have no clue how to dissect this issue. The mechanisms under
the hood are somewhat opaque to me. :(

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

[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO

[Marvin Jens via KDE Bugzilla]

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

--- Comment #11 from Marvin Jens  ---
Yes, I am also on 64Bit kubuntu. But my kate is from the backports repo, not
from source. Do you get the same plugins loaded as I do? Can I uninstall
kate/backports and compile it from source easily? Is there a howto somewhere? I
guess I'd need a lot of qt-dev and kde-dev packages, but I could try.

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

[krita] [Bug 369161] ext_qt (5.7) build fails with Xcode 8 + macOS Sierra

[Patrice Kouame via KDE Bugzilla]

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

--- Comment #5 from Patrice Kouame  ---
Geez hate not being able to edit/correct these (at least haven't found a way
how), but I meant 5.7.1 may fix this...still confirming

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