[digikam] [Bug 376898] Crash when scanning photo containing exif with empty Jis comment (Digikam::MetaEngine::getExifComment, QTextCodec::toUnicode) [patch]

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376898

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

   What|Removed |Added

Summary|Crash when scanning photo   |Crash when scanning photo
   |containing exif with empty  |containing exif with empty
   |Jis comment |Jis comment
   |(Digikam::MetaEngine::getEx |(Digikam::MetaEngine::getEx
   |ifComment,  |ifComment,
   |QTextCodec::toUnicode)  |QTextCodec::toUnicode)
   ||[patch]
 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Can you share an image with this kind of Exif::Jis comment ?

Gilles Caulier

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

[digikam] [Bug 376891] Digikam becomes unusable with many Metatags

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376891

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Where digiKam waste time at startup ? Can you investigate using kcallgrind tool
? This will indicate which code will be called a lots of time in this
situation...

Gilles Caulier

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

[digikam] [Bug 376898] Crash when scanning photo containing exif with empty Jis comment (Digikam::MetaEngine::getExifComment, QTextCodec::toUnicode) [patch]

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376898

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

   What|Removed |Added

   Version Fixed In||5.5.0
  Latest Commit||https://commits.kde.org/dig
   ||ikam/4cc8880fa70a943d8b1978
   ||b7987b3a47bd586e8d
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from caulier.gil...@gmail.com ---
Git commit 4cc8880fa70a943d8b1978b7987b3a47bd586e8d by Gilles Caulier.
Committed on 25/02/2017 at 08:55.
Pushed by cgilles into branch 'master'.

apply patch from max...@smoothware.net to prevent crash when Exif::Jis comment
is badly encoded with empty string.
Fix coding style and polish
FIXED-IN: 5.5.0

M  +57   -35   libs/dmetadata/metaengine_p.cpp
M  +15   -15   libs/dmetadata/metaengine_p.h

https://commits.kde.org/digikam/4cc8880fa70a943d8b1978b7987b3a47bd586e8d

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

[Discover] [Bug 376910] New: Scrolling does not follow system settings

2017-02-25 Thread Sascha Zenglein
https://bugs.kde.org/show_bug.cgi?id=376910

Bug ID: 376910
   Summary: Scrolling does not follow system settings
   Product: Discover
   Version: 5.9.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: sascha.zengl...@yahoo.de
  Target Milestone: ---

Using Discover with a touchpad is not working as expected. Every scrolling
input accelerates the page without regard to whether the fingers are lifted or
not. 

It also does not follow the system scroll speed which leads to much too fast
scroll speeds and coasting even when coasting is disabled.


I don't know if this bug should be filed against Discover or Kirigami, but it's
a bit annoying for an Application that wants to be convergent.

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

[krunner] [Bug 173668] KDE must show Ksysguard main window with Ctrl+Esc

2017-02-25 Thread Mariusz Libera
https://bugs.kde.org/show_bug.cgi?id=173668

Mariusz Libera  changed:

   What|Removed |Added

 CC||mariusz.lib...@gmail.com

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

[digikam] [Bug 376891] Digikam becomes unusable with many Metatags

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376891

--- Comment #2 from bzru...@protonmail.ch ---
Created attachment 104212
  --> https://bugs.kde.org/attachment.cgi?id=104212&action=edit
Valgrind log

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

[digikam] [Bug 376891] Digikam becomes unusable with many Metatags

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376891

--- Comment #3 from bzru...@protonmail.ch ---
(In reply to caulier.gilles from comment #1)
> Where digiKam waste time at startup ? Can you investigate using kcallgrind
> tool ? This will indicate which code will be called a lots of time in this
> situation...
> 
> Gilles Caulier

Hi Gilles,

Digikam starts within a minute or two, so that is no problem for me as I
usually will start it once a day. The problem comes up when I try to
add/edit/delete a tag, Digikam will freeze for a whole minute until done.

I just installed valgrind and started digikam like this:
valgrind --tool=callgrind digikam

I get lots of segment overflows like :
==5290== brk segment overflow in thread #1: can't grow to 0x4a38000

and I am waiting now 20 minutes for Digikam to start up ;)

I found some info on stackoverflow:

http://stackoverflow.com/questions/35129135/valgrind-reporting-a-segment-overflow

still not sure if that is a problem at all. However, seems I can't even get
Digikam to start up running valgrind. I killed the process and attaching the
output till here, maybe it's already usefull for debugging.

Thanks!

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

[kdeconnect] [Bug 376911] New: no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

Bug ID: 376911
   Summary: no devices
   Product: kdeconnect
   Version: 1.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: ykmssg-...@yahoo.co.uk
  Target Milestone: ---

Fresh install with Fedora workstation from iso. (am thinking this may be where
it's hit the fan? as I copied and pasted from another machine, almost identical
in hardware, using the package manager list and giving/transferring it to dnf
on the problem install, to cut time down to the minimum).
Anyways, nothing shows when refreshing the gui and when run from terminal
nothing is indicating anything wrong. Have installed using source and still
nothing showing in terms of devices connected.
My 'droids don't see the machine or other Fedora installs. Ive reinstalled the
program, maybe I need to reinstall my OS? (not much chance in the latter hozay)

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

[kdenlive] [Bug 376912] New: Crashed: Kdenlive was updating thumbnails and I closed it

2017-02-25 Thread Nikita Melnichenko
https://bugs.kde.org/show_bug.cgi?id=376912

Bug ID: 376912
   Summary: Crashed: Kdenlive was updating thumbnails and I closed
it
   Product: kdenlive
   Version: 16.12.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: nikita+...@melnichenko.name
  Target Milestone: ---

Application: kdenlive (16.12.2), MLT 6.4.1

Qt Version: 5.6.2
Frameworks Version: 5.29.0
Operating System: Linux 4.1.35-gentoo-c1 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
Kdenlive was updating the bin (video thumbnails / audio snapshots) and I closed
the application.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f031c21a740 (LWP 22055))]

Thread 35 (Thread 0x7f030a35a700 (LWP 22056)):
#0  0x7f0315b6b80d in poll () from /lib64/libc.so.6
#1  0x7f03109198f2 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7f031091b6df in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f030cef3549 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f0316523d4c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f0314027494 in start_thread () from /lib64/libpthread.so.0
#6  0x7f0315b7490d in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7f0301da6700 (LWP 22057)):
#0  0x7f0310dac650 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f0310dad0a8 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f0310dad28c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f031671705c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f03166c8a2a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f031651f564 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f031c2c4235 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7f0316523d4c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f0314027494 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0315b7490d in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f02e17e9700 (LWP 22058)):
#0  0x7f0315b6b80d in poll () from /lib64/libc.so.6
#1  0x7f0310dad17c in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f0310dad28c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f031671705c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f03166c8a2a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f031651f564 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f031724c8f5 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#7  0x7f0316523d4c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f0314027494 in start_thread () from /lib64/libpthread.so.0
#9  0x7f0315b7490d in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f02db7fe700 (LWP 22060)):
#0  0x7f0310dad120 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f0310dad28c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f031671705c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#3  0x7f03166c8a2a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f031651f564 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#5  0x7f031724c8f5 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#6  0x7f0316523d4c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f0314027494 in start_thread () from /lib64/libpthread.so.0
#8  0x7f0315b7490d in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f02d93ff700 (LWP 22067)):
#0  0x7f031402d13f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f03165243ba in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f031aaa8805 in QSGRenderThread::processEventsAndWaitForMore() ()
from /usr/lib64/libQt5Quick.so.5
#3  0x7f031aaa8bea in QSGRenderThread::run() () from
/usr/lib64/libQt5Quick.so.5
#4  0x7f0316523d4c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f0314027494 in start_thread () from /lib64/libpthread.so.0
#6  0x7f0315b7490d in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f02d8afe700 (LWP 22068)):
#0  0x7f0315b6b80d in poll () from /lib64/libc.so.6
#1  0x7f0310dad17c in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x

[krita] [Bug 342105] [HUION] Cannot right click with the Pen of Huion H610 Pro

2017-02-25 Thread algomaax
https://bugs.kde.org/show_bug.cgi?id=342105

algomaax  changed:

   What|Removed |Added

 CC||alfr...@gomez-gutierrez.de

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

[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond

2017-02-25 Thread Dartmouth
https://bugs.kde.org/show_bug.cgi?id=343383

Dartmouth  changed:

   What|Removed |Added

 CC||lolmanlolz.l...@gmail.com

--- Comment #25 from Dartmouth  ---
I have the same problem under openSUSE Leap 42.2 (and also had it with Leap
42.1)
Whatever mouse button I configure for mouse gestures is unusable for anything
else. 

plasmashell version 5.8.3
systemsettings version 5.8.2
KDE Frameworks 5.26.0

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

[kaffeine] [Bug 376882] DVB-S: FE_SET_PROPERTY: Invalid argument

2017-02-25 Thread Mauro Carvalho Chehab
https://bugs.kde.org/show_bug.cgi?id=376882

--- Comment #5 from Mauro Carvalho Chehab  ---
(In reply to Mauro Carvalho Chehab from comment #4)

> Could you please test with this patch applied on libdvbv5, the issue is
> fixed?

Btw, just added a patch on Kaffeine to allow finer control over its debug
messages. With the upstream version, it is now possible to enable only the
debug messages related to DVB device settings and libdvbv5 logs, with:

QT_LOGGING_RULES="kaffeine.dev.debug=true" kaffeine

So, if just upgrading libdvbv5 doesn't solve, please send me the logs with the
above command (Kaffeine should be compiled against its git tree).

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

[plasmashell] [Bug 359601] "Windows can cover" does not seem to work for me

2017-02-25 Thread Gunter Ohrner
https://bugs.kde.org/show_bug.cgi?id=359601

Gunter Ohrner  changed:

   What|Removed |Added

Version|5.5.4   |5.9.2
   Platform|Kubuntu Packages|Neon Packages

--- Comment #13 from Gunter Ohrner  ---
Still experiencing this with Plasma 5.9.2 KDE Neon packages - any news on this
issue?

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

[kmail2] [Bug 343186] Timeout trying to get lock on start of kmail

2017-02-25 Thread m . eik michalke
https://bugs.kde.org/show_bug.cgi?id=343186

m.eik michalke  changed:

   What|Removed |Added

 CC||m...@reaktanz.de

--- Comment #4 from m.eik michalke  ---
now, this bites me, again (KF5 16.04.3 packages from kubuntu backports, plasma
5.8.5): when i log in to my account, after a while i get the infamous "fatal
error: timeout trying to get lock", informing me that kmail will be terminated,
while i can actually see it in the background soon after, loading folders and
fetching mails.

ever since the upgrade to KF5, it literally takes like ages until the session
has finally started. i didn't really change anything, except of course
replacing the plasma widgets. but compared to KDE4, KF5 now needs at least
twice the time to even show a background image and the control bar, which seems
like it's slow enough for kmail to crash on me. it happens almost every day.

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

[kaffeine] [Bug 376882] DVB-S: FE_SET_PROPERTY: Invalid argument

2017-02-25 Thread Michael Zapf
https://bugs.kde.org/show_bug.cgi?id=376882

--- Comment #6 from Michael Zapf  ---
Give me a few days to check ...

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

[digikam] [Bug 365669] Face Recognition improvement suggestion

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365669

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

   What|Removed |Added

 CC||1127553...@qq.com

--- Comment #1 from caulier.gil...@gmail.com ---
*** Bug 376901 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 376901] [GSOC2017]Face Recognition Algorithm Improvements

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376901

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Please continue the discussion in bug #365669. No need to open a new file in
bugzilla

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

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

[digikam] [Bug 365669] Face Recognition improvement suggestion

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365669

--- Comment #2 from caulier.gil...@gmail.com ---
The face recognition is based on a dedicated algorithm plugged in faceEngine
class from digiKam core.

A new one can be add without to introduce a dysfunction. In GUI we can make it
selectable.

This is the goal of GSoC 2017 idea :

https://community.kde.org/GSoC/2017/Ideas#Project_4_:_digiKam_Face_Management_improvements

Gilles Caulier

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

[digikam] [Bug 365669] Face Recognition improvement suggestion

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365669

--- Comment #3 from caulier.gil...@gmail.com ---
This file is also an entry  to process in GSoC 2017 :

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

Gilles Caulier

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

[digikam] [Bug 365669] Face Recognition improvement suggestion

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365669

--- Comment #4 from caulier.gil...@gmail.com ---
Another one entry to process while GSoC 2017 :

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

Gilles Caulier

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

[digikam] [Bug 365669] Face Recognition improvement suggestion

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=365669

--- Comment #5 from caulier.gil...@gmail.com ---
Yingjie Liu,

Please review enties from bugzilla that i start to list in this file for GSoC
2017. Create a private proposal in Google Doc and share with me in private. I
will forward to other developers.

Gilles Caulier

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

[digikam] [Bug 376913] New: can't create a new album in picasa/googlephoto

2017-02-25 Thread Philippe ROUBACH
https://bugs.kde.org/show_bug.cgi?id=376913

Bug ID: 376913
   Summary: can't create a new album in picasa/googlephoto
   Product: digikam
   Version: 5.4.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Export
  Assignee: digikam-de...@kde.org
  Reporter: philippe.roub...@free.fr
  Target Milestone: ---

Created attachment 104213
  --> https://bugs.kde.org/attachment.cgi?id=104213&action=edit
error creating an album

opensuse 42.2 x86_64
digikam 5.4.0

KDE Frameworks 5.26.0
Qt 5.6.1 (built against 5.6.1)
The xcb windowing system

i want to export photos to google photo
i fill the template
then
ok
then
i get an error . see the capture

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

[Discover] [Bug 376914] New: no programs

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376914

Bug ID: 376914
   Summary: no programs
   Product: Discover
   Version: 5.6.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: irr...@citromail.hu
  Target Milestone: ---

When i run Discover Software Center i can not see or search any programs.

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

[digikam] [Bug 374248] importing photo, bad file selector

2017-02-25 Thread Philippe ROUBACH
https://bugs.kde.org/show_bug.cgi?id=374248

--- Comment #14 from Philippe ROUBACH  ---
there is no more problem in my case with digikam 5.4.0

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

[partitionmanager] [Bug 376895] Partition Manager crashes when run without root

2017-02-25 Thread Alexander Schlarb
https://bugs.kde.org/show_bug.cgi?id=376895

--- Comment #2 from Alexander Schlarb  ---
No problem! Thanks for the reply!

I can't remember ever setting up an LVM-based partition layout through… Or is
it the LVM-integration module/code that causes this?

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

[partitionmanager] [Bug 376895] Partition Manager crashes when run without root

2017-02-25 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=376895

--- Comment #3 from Andrius Štikonas  ---
(In reply to Alexander Schlarb from comment #2)
> No problem! Thanks for the reply!
> 
> I can't remember ever setting up an LVM-based partition layout through… Or
> is it the LVM-integration module/code that causes this?

I'm actually not sure. It's just that backtrace contains FS::lvm2_pv::getPVs,
so crash must happen in that function.

That function in kpmcore/src/fs/lvm2_pv.cpp loops over QList& devices.
I guess it crashes if there are no devices. Feell free to play around yourself
if you have time :), should be quite easy to fix, probably one "if". If not
I'll look at it at some point later, but these days I'm quite busy... Writing
my PhD thesis.

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #1 from ykmssg-...@yahoo.co.uk ---
Created attachment 104214
  --> https://bugs.kde.org/attachment.cgi?id=104214&action=edit
gui with no devices

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #2 from ykmssg-...@yahoo.co.uk ---
ports are open for the program 
2 other Fedora25 machines don't see it and 5 Android devices also have no
connection with it even adding the IP address produces nothing

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

[amarok] [Bug 376906] kgraphicswebview.h: No such file or directory

2017-02-25 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=376906

Myriam Schweingruber  changed:

   What|Removed |Added

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

--- Comment #1 from Myriam Schweingruber  ---
Please report this to your distribution, we didn't change anything on our side
in that regard.
Missing dependencies need to be addressed by the distributions.

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

[kipiplugins] [Bug 376913] can't create a new album in picasa/googlephoto

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376913

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|Export  |GoogleServices
   Assignee|digikam-de...@kde.org   |kde-imag...@kde.org
Product|digikam |kipiplugins

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

[digikam] [Bug 374248] importing photo, bad file selector

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=374248

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

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.5.0

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

[kipiplugins] [Bug 376913] can't create a new album in picasa/googlephoto

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376913

--- Comment #1 from caulier.gil...@gmail.com ---
Google API has changed again... to a new version... Thanks Google. code from
plugin need to be ported...

Gilles Caulier

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #3 from Albert Vaca  ---
Maybe the kdeconnect config from your old distro doesn't work on the new one.
Go to ~/.config and rename kdeconnect to something else. Log out and log in
again so the config is recreated and let me know if it solves the problem.

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #4 from ykmssg-...@yahoo.co.uk ---
Created attachment 104215
  --> https://bugs.kde.org/attachment.cgi?id=104215&action=edit
rename

after rename and re-login 
this showing in logs; recurring 

Feb 20 13:05:02 localhost.localdomain /usr/libexec/gdm-x-session[1362]: Fail
set label TypeError: menuitem is null

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #5 from ykmssg-...@yahoo.co.uk ---
no change to the program being visible!!

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

[kdenlive] [Bug 376915] New: Adding speed effect to Slideshow clip shrinks it to 0 on the timeline

2017-02-25 Thread Francesco
https://bugs.kde.org/show_bug.cgi?id=376915

Bug ID: 376915
   Summary: Adding speed effect to Slideshow clip shrinks it to 0
on the timeline
   Product: kdenlive
   Version: 16.12.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: francesco.cimore...@gmail.com
  Target Milestone: ---

Created attachment 104216
  --> https://bugs.kde.org/attachment.cgi?id=104216&action=edit
Screencast of the bug

Hello. I am trying to create a timelapse.

To do this I add a slideshow clip based on ~1500 pictures.

After adding the clip to the timeline, I am trying to speed it up.

Whenever I select a speed different from 100% the clip shrinks to 0. I still
tried rendering the video but the speed effect is not applied.

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

[neon] [Bug 376793] Dependencies not met for winehq-devel in Neon User non LTS

2017-02-25 Thread Alex
https://bugs.kde.org/show_bug.cgi?id=376793

--- Comment #1 from Alex  ---
Created attachment 104217
  --> https://bugs.kde.org/attachment.cgi?id=104217&action=edit
Console log from Neon LTS to compare.

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #6 from Albert Vaca  ---
In that case I'm not sure what the error can be. Try running the kdeconnectd
binary on a terminal and see what the output looks like. The location of the
binary changes depending on the distribution (eg: on Arch it's in
/usr/lib/libexec/kdeconnectd). Also make sure to "killall kdeconnectd" before
running it, as if it detects another instance is running it just terminates
without doing anything.

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

[partitionmanager] [Bug 376895] Partition Manager crashes when run without root

2017-02-25 Thread Alexander Schlarb
https://bugs.kde.org/show_bug.cgi?id=376895

--- Comment #4 from Alexander Schlarb  ---
Thanks for the hint, I wouldn't have taken up this little bug squashing
exercise otherwise! :-)

As you expected there are only some very minor changes required, they just
happen to be in the `libparted` backend, not in the LVM code itself. I like how
easy it is to follow the structure of your code btw! Not gonna make me friends
with C/C++ but it definitely makes things a lot more pleasant this way!

Anyway, the code for review is here:
https://git.reviewboard.kde.org/r/129968/

Have a nice weekend and thanks for KPM! It has become such an awesome tool to
use!

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

[partitionmanager] [Bug 376895] Partition Manager crashes when run without root

2017-02-25 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=376895

--- Comment #5 from Andrius Štikonas  ---
Thanks, a lot! I'll commit it...

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

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

2017-02-25 Thread Andrius Štikonas
https://bugs.kde.org/show_bug.cgi?id=375394

Andrius Štikonas  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kpm
   ||core/427e37a047898dad0ab8c5
   ||4aea33473f7854e150

--- Comment #4 from Andrius Štikonas  ---
Git commit 427e37a047898dad0ab8c54aea33473f7854e150 by Andrius Štikonas, on
behalf of Alexander Schlarb.
Committed on 25/02/2017 at 13:45.
Pushed by stikonas into branch 'master'.

Prevent the libparted backend from exposing "null devices"

REVIEW: 129968

M  +4-1src/plugins/libparted/libpartedbackend.cpp

https://commits.kde.org/kpmcore/427e37a047898dad0ab8c54aea33473f7854e150

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

[kipiplugins] [Bug 376913] can't create a new album in picasa/googlephoto

2017-02-25 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=376913

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
I have already spent time on this problem. Nothing can be ported. The required
functions are no longer available in the Google Picasa API. The available LR
plugin is also affected. Read this threads as example:

https://developers.google.com/picasa-web/forum

Thanks Google for it!

Maik

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #7 from ykmssg-...@yahoo.co.uk ---
Created attachment 104218
  --> https://bugs.kde.org/attachment.cgi?id=104218&action=edit
log from login

Is the polkit the problem

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

[kdevelop] [Bug 326041] Invalid problem reported about "use of deleted function"

2017-02-25 Thread Lahoucine ENASSIRI
https://bugs.kde.org/show_bug.cgi?id=326041

Lahoucine ENASSIRI  changed:

   What|Removed |Added

 CC||lahouc02-...@gmx.fr

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #8 from ykmssg-...@yahoo.co.uk ---
I have looked at the logs upon login using 2 machines and the/this bad 1 is
showing the auto start service with the url omitting my home directory which
DOES SHOW on the good machine

i.e. "/etc/xdg/autostart
instead of ~/.config/autostart/*
and polkit Registered
(trying to login... sorry on my other laptop, much easier when this program
works)

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #9 from ykmssg-...@yahoo.co.uk ---
Created attachment 104219
  --> https://bugs.kde.org/attachment.cgi?id=104219&action=edit
kdeconnect working machine log

shows the polkit registering on a good machine, so if thisis the problem, how
do I fix it?

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

[Breeze] [Bug 376916] New: Breeze GTK theme severely broken in Thunderbird

2017-02-25 Thread Janek Bevendorff
https://bugs.kde.org/show_bug.cgi?id=376916

Bug ID: 376916
   Summary: Breeze GTK theme severely broken in Thunderbird
   Product: Breeze
   Version: 5.9.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: scionicspec...@gmail.com
  Reporter: k...@jbev.net
  Target Milestone: ---

Created attachment 104220
  --> https://bugs.kde.org/attachment.cgi?id=104220&action=edit
Compose window

With the latest update to 5.9.2, my Thunderbird started looking terrible.
I got solid black lines as widget separators and my conversations (Thunderbird
Conversations plugin) got an ugly gray background with a white rectangle
instead of a fully white background.

I attached screenshots to depict better what I mean.


Everything worked fine in 5.9.0 (and probably 5.9.1). Native GTK applications
look fine. Firefox seems to work as well, but Thunderbird looks terrible.

Using Plasma 5.9.2 on Arch Linux.

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

[Breeze] [Bug 376916] Breeze GTK theme severely broken in Thunderbird

2017-02-25 Thread Janek Bevendorff
https://bugs.kde.org/show_bug.cgi?id=376916

--- Comment #1 from Janek Bevendorff  ---
Created attachment 104221
  --> https://bugs.kde.org/attachment.cgi?id=104221&action=edit
Conversation, note the gray background around the white rectangle, the reply
and forward buttons also used to have white background

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

[ksysguard] [Bug 376917] New: ksysguard SensorDisplay.cpp compile problem

2017-02-25 Thread Vladislav Dembskiy
https://bugs.kde.org/show_bug.cgi?id=376917

Bug ID: 376917
   Summary: ksysguard  SensorDisplay.cpp compile problem
   Product: ksysguard
   Version: 5.9.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: v.dembs...@gmail.com
  Target Milestone: ---

During compilation of ksysguard-5.9.2 I have got very strange error:
In file included from
/sources/KDE/PLASMA/ksysguard-5.9.2/gui/SensorDisplayLib/SensorDisplay.cpp:41:0:
/sources/KDE/PLASMA/ksysguard-5.9.2/gui/SensorDisplayLib/SensorDisplay.h:47:1:
error: expected class-name before ‘{’ token
 {

My gcc is version 6.3.0 And I did successful compilation of full set of
frameworks and part of Plasma modules which do not depend on ksysguard.

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #10 from ykmssg-...@yahoo.co.uk ---

localhost ~]$ /usr/libexec/kdeconnectd



nothing

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

[digikam] [Bug 376918] New: Ambiguous Shortcuts

2017-02-25 Thread Ric
https://bugs.kde.org/show_bug.cgi?id=376918

Bug ID: 376918
   Summary: Ambiguous Shortcuts
   Product: digikam
   Version: 5.4.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: setup
  Assignee: digikam-de...@kde.org
  Reporter: fhj52.i...@gmail.com
  Target Milestone: ---

Started charge for phone, got a popup in KDE plasma 5.9.2 for 'what to do' and
decided to see if Digikam works.
It does! (I'm so glad - luv digikam!)
However it popped-up a message:
"
Ambiguous Shortcuts
There are two actions (Select Locked Items, Toggle Lock) that want to use the
same shortcut (Ctrl+L). This is most probably a bug. Please report it in
bugs.kde.org
"

The configurable Settings/Shortcuts has neither of those items. 
It does have General/"Place onto Light Table" as Ctrl+L.

So not sure what the real problem is here. 
Nevertheless, I looked for this error in bugs list and did not find it so it is
reported as requested.

[system info]
System:Kernel: 4.9.12-1-MANJARO x86_64 (64 bit gcc: 6.3.1)
   Desktop: KDE Plasma 5.9.2 (Qt 5.8.0) Distro: Manjaro Linux
Machine:   Mobo: Supermicro model: X8DTH BIOS: AMI v: 2.1b date: 05/04/12
CPU(s):2 Quad core Intel Xeon X5687s (-HT-MCP-SMP-) cache: 24576 KB
Graphics:  Card: NVIDIA GP106 [GeForce GTX 1060 6GB] bus-ID: 84:00.0

[digikam info]
Name: digikam
Version : 5.4.0-2
Depends On  : liblqr  libkipi  lensfun  opencv  akonadi-contacts 
knotifyconfig  libksane  kfilemetadata
  qtav  marble  threadweaver  kcalcore
Optional Deps   : kipi-plugins: export to various online services [installed]
  qt5-imageformats: support for additional image formats (WEBP,
TIFF) [installed]
Packager: Antonio Rojas 
Build Date  : Sun 29 Jan 2017 03:50:14 PM CST

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

[kdepim] [Bug 376919] New: WebEngine-dependent scrollbars do not fit with KDE style (applies to Kmail, Akregator, Konqueror, maybe others)

2017-02-25 Thread avlas
https://bugs.kde.org/show_bug.cgi?id=376919

Bug ID: 376919
   Summary: WebEngine-dependent scrollbars do not fit with KDE
style (applies to Kmail, Akregator, Konqueror, maybe
others)
   Product: kdepim
   Version: 5.4.*
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: messageviewer
  Assignee: kdepim-b...@kde.org
  Reporter: jsar...@gmail.com
  Target Milestone: ---

Scrollbars in Kmail, Akregator and Konqueror look out of place (different from
KDE breeze, or any other style chosen in KDE neon).

This is well known and it's due to QtWebEngine.

I thought to be the same in Qupzilla (also based on QtWebEngine), but actually
it's not. Qupzilla uses QtWebEngine as well but has perfectly integrated
scrollbars in KDE.

This must be then sth doable as well for KDE applications using WebEngine,
perhaps you can even borrow the code from Qupzilla source code (?)

(Btw, sorry if this wasn't the proper package to associated the bug with)

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

[Breeze] [Bug 376916] Breeze GTK theme severely broken in Thunderbird

2017-02-25 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=376916

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org

--- Comment #2 from Antonio Rojas  ---
This has nothing to do with the 5.9.2 update, this is because thunderbird is
now compiled with gtk3 instead of gtk2

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

[Breeze] [Bug 376916] Breeze GTK theme severely broken in Thunderbird

2017-02-25 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=376916

Antonio Rojas  changed:

   What|Removed |Added

 CC|aro...@archlinux.org|

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #11 from Albert Vaca  ---
killall kdeconnectd; /usr/libexec/kdeconnectd

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

[konsole] [Bug 376920] New: WishList: Toggling notification support

2017-02-25 Thread Looserof7
https://bugs.kde.org/show_bug.cgi?id=376920

Bug ID: 376920
   Summary: WishList: Toggling notification support
   Product: konsole
   Version: 16.12.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: looser...@gmail.com
  Target Milestone: ---

Os: Manjaro

WishList: A small icon to toggle notifications for currently running process on
that particular terminal.

There were times when update or something similar to download through a
command-line programs, compilation takes some-what long time, rather than
peeking into to terminal each and every-time, to see whether it is completed or
not, I think it would be better to have icon which would allow us to toggle
notifications feature.

consider an update process which is currently being executed, if I turn-on
notification feature for this particular process, then I would get notified by
notification after that particular process is completed.

Another request: This may-be beyond scope:-
To get a notification while some process is asking for some input.
Ex:- while installing any package from Aur, It would ask for password, after
compilation is finished, to install that particular package, It would be better
to get notified during such cases because compilation of certain packages take
really long time, no-body knows how long, and when yaourt asks for password, It
would wait for around 10 to 20 minutes for password and then terminate.
If forgot about that particular process then we need to compile it again.

Thank you.

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #12 from ykmssg-...@yahoo.co.uk ---
did that

and not a sausage

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

[plasmashell] [Bug 376501] Initial loading screen uses wrong resolution on one monitor if monitors have different resolutions

2017-02-25 Thread Chris
https://bugs.kde.org/show_bug.cgi?id=376501

Chris  changed:

   What|Removed |Added

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

--- Comment #1 from Chris  ---
This seems to be fixed now. Nice! My SDDM issues are almost all resolved too, I
wonder if that's related.

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

[konsole] [Bug 376920] WishList: Toggling notification support

2017-02-25 Thread Looserof7
https://bugs.kde.org/show_bug.cgi?id=376920

Looserof7  changed:

   What|Removed |Added

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

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

[Breeze] [Bug 376916] Breeze GTK theme severely broken in Thunderbird

2017-02-25 Thread Janek Bevendorff
https://bugs.kde.org/show_bug.cgi?id=376916

--- Comment #3 from Janek Bevendorff  ---
Possible that it got updated as well. Wasn't exactly sure what caused the
problem. It's still an issue, though.

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #13 from Albert Vaca  ---
Then something is really broken with your system. You should at least see
"kdeconnect.core: KdeConnect daemon starting". Make sure your kdeconnectd is
actually dead, before starting the new one!

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #14 from ykmssg-...@yahoo.co.uk ---
I'll remove a some packages with the bunch of deps and see if anything changes,
I've started with removing polkit and doing a kernel update @tm so if anything
changes there'll be a report on here.
Thanks for your speedy reply, oh yes all kdeconnectd was killed before
executing

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

[kolourpaint] [Bug 376921] New: Crash when closing the Application

2017-02-25 Thread Tobias Endres
https://bugs.kde.org/show_bug.cgi?id=376921

Bug ID: 376921
   Summary: Crash when closing the Application
   Product: kolourpaint
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kolourpaint-supp...@lists.sourceforge.net
  Reporter: endr4...@gmail.com
  Target Milestone: ---

Application: kolourpaint (16.12.2)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.11-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I had an unsaved image opened and closed the application by clicking teh small
X in the corner

The crash can be reproduced every time.

-- Backtrace:
Application: KolourPaint (kolourpaint), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f11e5ab0840 (LWP 8459))]

Thread 5 (Thread 0x7f11ba971700 (LWP 8474)):
#0  0x7f11dc864f1c in __lll_lock_wait () at /usr/lib/libpthread.so.0
#1  0x7f11dc85ebb6 in pthread_mutex_lock () at /usr/lib/libpthread.so.0
#2  0x7f11e59c2255 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#3  0x7f11e1096a7d in do_dlopen () at /usr/lib/libc.so.6
#4  0x7f11e59be3a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#5  0x7f11e1096b0f in dlerror_run () at /usr/lib/libc.so.6
#6  0x7f11e1096b82 in __libc_dlopen_mode () at /usr/lib/libc.so.6
#7  0x7f11dc86660b in pthread_cancel_init () at /usr/lib/libpthread.so.0
#8  0x7f11dc8667f4 in _Unwind_ForcedUnwind () at /usr/lib/libpthread.so.0
#9  0x7f11dc864d20 in __pthread_unwind () at /usr/lib/libpthread.so.0
#10 0x7f11dc85d565 in  () at /usr/lib/libpthread.so.0
#11 0x7f11e106ce0b in  () at /usr/lib/libc.so.6
#12 0x7f11ba975460 in  () at /usr/lib/libspeechd.so.2
#13 0x7f11dc85c454 in start_thread () at /usr/lib/libpthread.so.0
#14 0x7f11e10607df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f11bca15700 (LWP 8462)):
#0  0x7f11dc86210f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f11c4b2dc5b in  () at /usr/lib/xorg/modules/dri/r600_dri.so
#2  0x7f11c4b2dab7 in  () at /usr/lib/xorg/modules/dri/r600_dri.so
#3  0x7f11dc85c454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f11e10607df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f11c6f21700 (LWP 8461)):
#0  0x7f11e105748d in poll () at /usr/lib/libc.so.6
#1  0x7f11da2ea7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f11da2ea8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f11e1c7f06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f11e1c2889a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f11e1a4aa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f11dd743125 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f11e1a4f6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f11dc85c454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f11e10607df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f11cda12700 (LWP 8460)):
#0  0x7f11e105748d in poll () at /usr/lib/libc.so.6
#1  0x7f11d7adc8e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f11d7ade679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f11cf73b239 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f11e1a4f6d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f11dc85c454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f11e10607df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f11e5ab0840 (LWP 8459)):
[KCrash Handler]
#6  0x7f11abfbfb94 in  () at /usr/lib/libQtGui.so.4
#7  0x7f11e59be4fa in call_init.part () at /lib64/ld-linux-x86-64.so.2
#8  0x7f11e59be60b in _dl_init () at /lib64/ld-linux-x86-64.so.2
#9  0x7f11e59c2b38 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#10 0x7f11e59be3a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#11 0x7f11e59c22d9 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#12 0x7f11daa24ee9 in  () at /usr/lib/libdl.so.2
#13 0x7f11e59be3a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#14 0x7f11daa25521 in  () at /usr/lib/libdl.so.2
#15 0x7f11daa24f82 in dlopen () at /usr/lib/libdl.so.2
#16 0x7f11b9ab2b20 in  () at /usr/lib/libvlccore.so.8
#17 0x7f11b9a96e2b in  () at /usr/lib/libvlccore.so.8
#18 0x7f11b9a97158 in  () at /usr/lib/libvlccore.so.8
#19 0x7f11b9a970b4 in  () at /usr/lib/libvlccore.so.8
#20 0x7f11b9a97634 in  () at /usr/lib/libvlccore.so.8
#21 0x7f11b9a97c3a in  () at /usr/lib/libvlccore.so.8
#22 0x7f11b9a1deb1 in libvlc_InternalInit () at /usr/lib/libvlccore.so.8
#23 0x7f11b97eecee in libvlc_new () at /usr/lib/libvlc.so.5
#24 0x7f11b9d

[dolphin] [Bug 376922] New: Don't show new Service Menus in KDE Store

2017-02-25 Thread Alex L
https://bugs.kde.org/show_bug.cgi?id=376922

Bug ID: 376922
   Summary: Don't show new Service Menus in KDE Store
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: alexlon...@gmail.com
  Target Milestone: ---

The Dolphin dialog to download additional Service Menus from KDE Store show
only old products. It seems to me it only show products that were in KDE Look.
When KDE Store was launcher some Service Menu were uploaded but Dolphin doesn't
show them.

Step to reproduce:
* Go to store.kde.org and check the recently added Service Menus
* Go to Dolphin settings > Services > Download new services and check the newer
ones are not displayed

Expected result:
* Newer Service Menus in KDE Store should be displayed in Dolphin's dialog

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #15 from ykmssg-...@yahoo.co.uk ---
when I say nothing happened within the terminal command, the kdeconnectd did
start again but there was no change to the program

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

[Akonadi] [Bug 376923] New: Akonadi crashes on restart when KMail hangs on "Retrieving folder content" (POP accounts). Akonadi also creates many dupplicates.

2017-02-25 Thread Frits Spieker
https://bugs.kde.org/show_bug.cgi?id=376923

Bug ID: 376923
   Summary: Akonadi crashes on restart when KMail hangs on
"Retrieving folder content" (POP accounts). Akonadi
also creates many dupplicates.
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: s.pa...@spiekerbros.com
  Target Milestone: ---

Application: akonadiserver (5.4.2)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.11-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
When KMail hangs on "Retrieving Folder content" it sometimes helps to restart
akonadi. However, since last update this does not help anymore; akonadi just
crashes on the restart. Also, many duplicates and duplicates of duplicates are
being created upon filtering. 
- Unusual behavior I noticed:

The crash can be reproduced sometimes.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f63648868c0 (LWP 6998))]

Thread 35 (Thread 0x7f62b4ff9700 (LWP 7192)):
#0  0x7f635f24af64 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f635f20588a in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f635f2059ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f636312418b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f63630cdaea in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f6361422454 in start_thread () from /lib64/libpthread.so.0
#8  0x7f63625f637f in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7f62b57fa700 (LWP 7189)):
#0  0x7f63625ed66d in poll () from /lib64/libc.so.6
#1  0x7f635f205896 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f635f2059ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f636312418b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f63630cdaea in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f6361422454 in start_thread () from /lib64/libpthread.so.0
#8  0x7f63625f637f in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f62b5ffb700 (LWP 7184)):
#0  0x7f63625ed66d in poll () from /lib64/libc.so.6
#1  0x7f635f205896 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f635f2059ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f636312418b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f63630cdaea in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f6361422454 in start_thread () from /lib64/libpthread.so.0
#8  0x7f63625f637f in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f62b67fc700 (LWP 7180)):
#0  0x7f635f24af64 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f635f204d70 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f635f2057bb in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f635f2059ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f636312418b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f63630cdaea in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f6362efb813 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f6362f004c8 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f6361422454 in start_thread () from /lib64/libpthread.so.0
#9  0x7f63625f637f in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f62b77fe700 (LWP 7176)):
[KCrash Handler]
#6  0x7f63625415af in raise () from /lib64/libc.so.6
#7  0x7f63625429aa in abort () from /lib64/libc.so.6
#8  0x7f6362b5b69d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib64/libstdc++.so.6
#9  0x7f6362b59676 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x7f6362b596c1 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x7f6362b598d8 in __cxa_throw () from /usr/lib64/libstdc++.so.6
#12 0x7f6363fdfc02 in Akonadi::Protocol::DataStream::operator<<  (this=, val=) at
/usr/src/debug/akonadi-16.12.2/src/p

[systemsettings] [Bug 376924] New: Crashed while using system settings

2017-02-25 Thread John
https://bugs.kde.org/show_bug.cgi?id=376924

Bug ID: 376924
   Summary: Crashed while using system settings
   Product: systemsettings
   Version: 5.8.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jkd...@zoho.com
  Target Milestone: ---

Application: systemsettings5 (5.8.5)
 (Compiled from sources)
Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.6-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:
I was using system settings, clicking on different options.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc8bea87900 (LWP 1987))]

Thread 8 (Thread 0x7fc86f6cb700 (LWP 2098)):
#0  0x7fc8b386b879 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7fc8b3825bd6 in g_main_context_check () from /lib64/libglib-2.0.so.0
#2  0x7fc8b3826104 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7fc8b382627c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7fc8bb8386eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7fc8bb7e968a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7fc8bb6465e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7fc8ba1f24e5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#8  0x7fc8bb64a9ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7fc8b7aab6ca in start_thread () from /lib64/libpthread.so.0
#10 0x7fc8baa33f7f in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7fc876d53700 (LWP 2096)):
#0  0x7fc8b382320f in g_source_iter_next () from /lib64/libglib-2.0.so.0
#1  0x7fc8b382563b in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7fc8b382608b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7fc8b382627c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7fc8bb8386eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7fc8bb7e968a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7fc8bb6465e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7fc8ba1f24e5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#8  0x7fc8bb64a9ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7fc8b7aab6ca in start_thread () from /lib64/libpthread.so.0
#10 0x7fc8baa33f7f in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fc882383700 (LWP 2092)):
#0  0x7fc8b386b894 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7fc8b3826286 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#2  0x7fc8bb8386eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7fc8bb7e968a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7fc8bb6465e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7fc8ba1f24e5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#6  0x7fc8bb64a9ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fc8b7aab6ca in start_thread () from /lib64/libpthread.so.0
#8  0x7fc8baa33f7f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fc88d16b700 (LWP 2079)):
#0  0x7fc8b386b894 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7fc8b3825bc1 in g_main_context_check () from /lib64/libglib-2.0.so.0
#2  0x7fc8b3826104 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7fc8b382627c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7fc8bb8386eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7fc8bb7e968a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7fc8bb6465e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7fc8ba1f24e5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#8  0x7fc8bb64a9ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7fc8b7aab6ca in start_thread () from /lib64/libpthread.so.0
#10 0x7fc8baa33f7f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fc890733700 (LWP 1991)):
#0  0x7fc8b7ab1460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc8985f1c4b in util_queue_thread_func () from
/usr/lib64/dri/r600_dri.so
#2  0x7fc8985f1aa7 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so
#3  0x7fc8b7aab6ca in start_thread () from /lib64/libpthread.so.0
#4  0x7fc8baa33f7f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fc89b68370

[kipiplugins] [Bug 376913] can't create a new album in picasa/googlephoto

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376913

--- Comment #3 from caulier.gil...@gmail.com ---
Maik, 

I suppose that it's the expected way about PICASA, as GPhoto replace it step by
step.

Is GPhoto and GDrive are also affected by these changes ?

Gilles Caulier

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

[frameworks-kpackage] [Bug 376847] since kpackage 5.29->5.31 upgrade, plasma crashes (custom lookandfeel, mismatched metadata.json ?)

2017-02-25 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=376847

Rex Dieter  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DOWNSTREAM  |---
 Ever confirmed|0   |1

--- Comment #6 from Rex Dieter  ---
Re-opening, other users downstream are experiencing similar symptoms during
testing,
https://bugzilla.redhat.com/show_bug.cgi?id=1426846

will see about getting details if it's the same as me or something different.

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

[kdenlive] [Bug 376925] New: wenn ich mit mit dem curser von einem clip zum nächsten springe stürzt kdenlive immer ab

2017-02-25 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=376925

Bug ID: 376925
   Summary: wenn ich mit mit dem curser von einem clip zum
nächsten springe stürzt kdenlive immer ab
   Product: kdenlive
   Version: 16.12.2
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: texasrange...@web.de
  Target Milestone: ---

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kdenlive...Reading symbols from
/usr/lib/debug/.build-id/e4/6d5556b45ac35ab0a9ba4d028c87871b2e863c.debug...done.
done.
Attaching to program: /usr/bin/kdenlive, process 4192
ptrace: Kein passender Prozess gefunden.
(gdb)

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

[gwenview] [Bug 376926] New: Slideshow does not stop when going back to overview

2017-02-25 Thread Martin Ueding
https://bugs.kde.org/show_bug.cgi?id=376926

Bug ID: 376926
   Summary: Slideshow does not stop when going back to overview
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: von.kde@martin-ueding.de
CC: myr...@kde.org
  Target Milestone: ---

I file this bug here, I have the impression that it did not get forwarded from
Fedora (https://bugzilla.redhat.com/show_bug.cgi?id=1405442).



Description of problem:

The slideshow in Gwenview does not stop when one leaves the image and goes
back to the overview with the ESC key.


Version-Release number of selected component (if applicable):

gwenview 16.08.2 1.fc25

How reproducible:

Always

Steps to Reproduce:

1. Go into full screen mode
2. Start a slideshow in some directory
3. Press ESC to go back to the overview
4. Wait a few seconds

Actual results:

After a couple of seconds, the selection of the image in the overview
jumps, the slideshow seems to be still active.

When opening another image, the slideshow will also continue and keep
jumping.

At least when changing the directory, the slideshow stops.

Expected results:

Slideshow should stop when pressing ESC.

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

[kdenlive] [Bug 376925] wenn ich mit mit dem curser von einem clip zum nächsten springe stürzt kdenlive immer ab

2017-02-25 Thread Rico
https://bugs.kde.org/show_bug.cgi?id=376925

--- Comment #1 from Rico  ---
im übrigen nutze ich Linux Mint 18.1 KDE
und hier zusätzliche informationen vom letzten Absturz:

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

Thread 27 (Thread 0x7fcbb3fff700 (LWP 4787)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbb3fff700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fcbc0ff7700 (LWP 4786)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc0ff7700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7fcbc17f8700 (LWP 4785)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc17f8700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 24 (Thread 0x7fcbc1ff9700 (LWP 4784)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc1ff9700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 23 (Thread 0x7fcbc27fa700 (LWP 4783)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc4b8a18ae in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc27fa700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7fcbc2ffb700 (LWP 4777)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fcc3715595d in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so
#2  0x7fcc6d39c6ba in start_thread (arg=0x7fcbc2ffb700) at
pthread_create.c:333
#3  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fcc20e73700 (LWP 4776)):
#0  0x7fcc6ea9ac21 in __GI_ppoll (fds=0x7fcc0c6ecc70, nfds=3,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x7fcc69aebebd in pa_mainloop_poll () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7fcc69aec4ae in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7fcc3cca6feb in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#4  0x7fcc3cc79920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#5  0x7fcc3cc830b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#6  0x7fcc3ccc2f59 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#7  0x7fcc6d39c6ba in start_thread (arg=0x7fcc20e73700) at
pthread_create.c:333
#8  0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7fcbc37fc700 (LWP 4775)):
[KCrash Handler]
#6  0x7fcc3ec1c9f4 in MltInput::set_pixel_data(unsigned char const*) ()
from /usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#7  0x7fcc3ec1609d in ?? () from
/usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#8  0x7fcc3ec1588d in ?? () from
/usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#9  0x7fcc3ec167da in ?? () from
/usr/lib/x86_64-linux-gnu/mlt/libmltopengl.so
#10 0x7fcc744269c8 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#11 0x7fcc7443ca99 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#12 0x7fcc74426977 in mlt_frame_get_image () from
/usr/lib/x86_64-linux-gnu/libmlt.so.6
#13 0x7fcc7443a110 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6
#14 0x00736a0d in RenderThread::run (this=0x7fcc0c007b90) at
/build/kdenlive-SJVwLm/kdenlive-16.12.1/src/monitor/glwidget.cpp:1268
#15 0x7fcc6f4a1808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fcc6d39c6ba in start_thread (arg=0x7fcbc37fc700) at
pthread_create.c:333
#17 0x7fcc6eaa682d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7fcc03bfd700 (LWP 4774)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_con

[kipiplugins] [Bug 376913] can't create a new album in picasa/googlephoto

2017-02-25 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=376913

--- Comment #4 from Maik Qualmann  ---
The API for GPhoto is the same for Picasa. There is only the API which now has
fewer functions. GDrive is not affected.

Available functions are:
- list albums
- list images
- upload new images / videos to existing albums

Removed functions are:
- create albums
- comments, tags are ignored, except GEO information
- updating a image removed
- delete a image removed

Maik

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

[kaffeine] [Bug 371579] Kaffeine 2.0.5 unresponsive on certain DVB-S channels

2017-02-25 Thread Stefan Huebner
https://bugs.kde.org/show_bug.cgi?id=371579

--- Comment #5 from Stefan Huebner  ---
Great news. Thank you, Mauro.

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

[kipiplugins] [Bug 376913] can't create a new album in picasa/googlephoto

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376913

--- Comment #5 from caulier.gil...@gmail.com ---
Incredible...

Do you know why Google drop these functions ? It's an error, or new ones will
replace in the future ?

Or Google is in silent mode ?

Gilles

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

[krita] [Bug 376927] New: in the timeline, drag&drop a frame between two layer make it move on the canvas

2017-02-25 Thread z-uo
https://bugs.kde.org/show_bug.cgi?id=376927

Bug ID: 376927
   Summary: in the timeline, drag&drop a frame between two layer
make it move on the canvas
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: nicolas.boug...@z-uo.com
  Target Milestone: ---

Only if the frame as been created by a selection

Here are the steps:
In the timeline, create a frame, draw something on it (check show in timeline)
select some of the drawing, ctrl c and ctrl v create a new layer (check show in
timeline) and right clic, copy frame
Create a third layer (check show in timeline), take the frame you just created,
drag and drop it in the blank layer 

The result is the content of the frame move on the canvas to go in the top left
corner

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #16 from Albert Vaca  ---
What was the output? Any message that looks like an error?

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #17 from ykmssg-...@yahoo.co.uk ---
'blank' on the problem machine 
and just icon missing with the good 1

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

[digikam] [Bug 376928] New: Changes on mimetypes are applied after restart

2017-02-25 Thread Jan Wolter
https://bugs.kde.org/show_bug.cgi?id=376928

Bug ID: 376928
   Summary: Changes on mimetypes are applied after restart
   Product: digikam
   Version: 5.5.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: setup
  Assignee: digikam-de...@kde.org
  Reporter: onl...@wolter.re
  Target Milestone: ---

Created attachment 104222
  --> https://bugs.kde.org/attachment.cgi?id=104222&action=edit
Patch

Changes on mimetypes (Settings -> Views -> Mime Types) are applied only after
restarting digikam. The attached patch fixes that in a way that the changes are
directly applied (by scanning the collection) after confirming the dialog.

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread Albert Vaca
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #18 from Albert Vaca  ---
It should print something on the console where you execute it.

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

[digikam] [Bug 376928] Changes on mimetypes are applied after restart [patch]

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376928

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|Changes on mimetypes are|Changes on mimetypes are
   |applied after restart   |applied after restart
   ||[patch]

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #19 from ykmssg-...@yahoo.co.uk ---
(In reply to Albert Vaca from comment #18)
> It should print something on the console where you execute it.

nope
(nothing on my working desktop aswell)

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

[dolphin] [Bug 376922] Don't show new Service Menus in KDE Store

2017-02-25 Thread Rog131
https://bugs.kde.org/show_bug.cgi?id=376922

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #1 from Rog131  ---
When executing the Dolphin from the terminal the output tells:

'org.kde.knewstuff.core: Redirected to 
"https://distribute.kde.org/khotnewstuff/servicemenu/downloads/...'

The servicemenus at there are really old - at many cases obsolete.

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #20 from ykmssg-...@yahoo.co.uk ---
the cursor is just wedged to the left and blank

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

[dolphin] [Bug 376922] Don't show new Service Menus in KDE Store

2017-02-25 Thread Rog131
https://bugs.kde.org/show_bug.cgi?id=376922

--- Comment #2 from Rog131  ---
... and the Dolphin (16.12.2) is still using the KDE4 file paths - bug:
https://bugs.kde.org/show_bug.cgi?id=371907

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

[kuser] [Bug 374505] KUser crashed when was starting

2017-02-25 Thread m3johan
https://bugs.kde.org/show_bug.cgi?id=374505

m3johan  changed:

   What|Removed |Added

 CC||m3jo...@gmail.com

--- Comment #7 from m3johan  ---
I have the exact same error. Does not work with kdesu.
Same backtrace as in first post.

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

[frameworks-kpackage] [Bug 376847] since kpackage 5.29->5.31 upgrade, plasma crashes (custom lookandfeel, mismatched metadata.json ?)

2017-02-25 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=376847

Rex Dieter  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #7 from Rex Dieter  ---
closing->downstream again, fedora's updates system pushd plasma-5.8.6 out to
the repos without the requisite kf5-5.31.0 along with it.

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

[kdevplatform] [Bug 376849] clipped error text in toolviews

2017-02-25 Thread Simon Andric
https://bugs.kde.org/show_bug.cgi?id=376849

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[okular] [Bug 334733] Okular txt backend chokes on unicode text

2017-02-25 Thread Simon Andric
https://bugs.kde.org/show_bug.cgi?id=334733

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[Breeze] [Bug 376929] New: Basket icon is missing in Breeze

2017-02-25 Thread smihael
https://bugs.kde.org/show_bug.cgi?id=376929

Bug ID: 376929
   Summary: Basket icon is missing in Breeze
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: smih...@gmail.com
CC: kain...@gmail.com
  Target Milestone: ---

Icon for Basket Notepads is missing in the Breeze icon theme.

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

[kmail2] [Bug 376565] Automatic spell checking is not working

2017-02-25 Thread avlas
https://bugs.kde.org/show_bug.cgi?id=376565

--- Comment #2 from avlas  ---
I found the root issue. It is due to the font that is being used.

The same happens in other applications such as Kate. The reason why this didn't
seem to happen is because I use a monospace font in Kate where the bug didn't
happen (Hack 10), but it emerge as soon as I changed it to the font of my
system (Cabin 11).


This bug has been reported against Kate/Kwrite/etc before and it seems to be
tagged as fixed:

https://bugs.kde.org/show_bug.cgi?id=335988
https://bugs.kde.org/show_bug.cgi?id=343313
https://bugs.kde.org/show_bug.cgi?id=366291
https://bugs.kde.org/show_bug.cgi?id=335079

However this is not fixed at all in my system (up-to-date KDE neon User Edition
5.9). It might be a regression...

Reading more carefully to https://bugs.kde.org/show_bug.cgi?id=335079 it seems
the fix only works in a subset of fonts, perhaps this is enough for Kate as
people tend to use monospace fonts (my included) but it's far from ideal for
the rest of KDE apps that rely on spellchecking (Kate, Choqok, Konqueror...)

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

[digikam] [Bug 376930] New: Cannot write metadata to TIFF files

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376930

Bug ID: 376930
   Summary: Cannot write metadata to TIFF files
   Product: digikam
   Version: 5.4.0
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata-Engine
  Assignee: digikam-de...@kde.org
  Reporter: sharpknig...@gmail.com
  Target Milestone: ---

When trying to write metadata to a TIFF file, the metadata is not actually
written and an error with Exiv2 occurs in the console window.

One possible way to reproduce:
1) In the thumbnails view, select an image.
2) Click on "Item", followed by "Write Metadata to Image".

This happened using the AppImage bundle of version 5.4.0.

Console output resulting from executing reproduce steps (note that I replaced
the file path and name with a placeholder):
digikam.general: Using  2  CPU core to run threads
digikam.general: Action Thread run  1  new jobs
digikam.metaengine: ""  ==> Title:  QMap(("x-default",
CaptionValues::caption: "Test title", CaptionValues::author: "",
CaptionValues::date: QDateTime( Qt::TimeSpec(LocalTime)) ) ) 
digikam.metaengine: ""  ==> Comment:  QMap()
digikam.metaengine: ""  ==> Pick Label:  0
digikam.metaengine: ""  ==> Color Label:  0
digikam.metaengine: ""  ==> Rating: +++ 4
digikam.general: Writting tags
digikam.general: Delete all keywords
digikam.metaengine: xmlACDSee ""
digikam.metaengine: ""  ==> Read Iptc Keywords:  ()
digikam.metaengine: ""  ==> New Iptc Keywords:  ()
digikam.metaengine: MetaEngine::metadataWritingMode 0
digikam.metaengine: Will write Metadata to file ""
digikam.metaengine: wroteComment:  false
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Cannot save metadata using Exiv2   (Error # 2 :  : Call to `mmap' failed: Invalid argument (errno = 22)
digikam.metaengine: Metadata for file "" written to file.
digikam.general: One job is done
digikam.general: List of Pending Jobs is empty
digikam.general: Event is dispatched to KDE desktop notifier
digikam.general: Cancel Main Thread
digikam.general: Cancel Main Thread

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

[digikam] [Bug 376930] Cannot write metadata to TIFF files

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376930

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from caulier.gil...@gmail.com ---
The mmap problem is an internal error from Exiv2. Report this problem as
Upstream to Exiv2 bugzilla with relevant TIFF file attached to reproduce the
problem.

Gilles Caulier

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

[gwenview] [Bug 376931] New: Volume set to 100% when deleting a file

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376931

Bug ID: 376931
   Summary: Volume set to 100% when deleting a file
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: repor...@mailinator.com
CC: myr...@kde.org
  Target Milestone: ---

Gwenview always sets system volume to 100% when showing a confirmation dialog
for  deletion of a file, or for unsaved changes to pictures when closing the
app.

org.kde.gwenview 16.08.3
OS: Debian GNU/Linux 9.0 (stretch) - actual
Output device: Built-in Audio Analog Stereo
Backend: Phonon VLC

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

[kolourpaint] [Bug 376921] Crash when closing the Application

2017-02-25 Thread Martin Koller
https://bugs.kde.org/show_bug.cgi?id=376921

Martin Koller  changed:

   What|Removed |Added

 CC||kol...@aon.at
 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Martin Koller  ---
What I see is that it seems to be related to a Notification, sent via
KNotification and obviously using the VLC multimedia backend.
The stack does not show why it crashes (debug symbols missing), but the crash
has nothing to do directly with kolourpaint.

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

[plasmashell] [Bug 376866] Can't write anything into plasma dialogues, can into KDE apps.

2017-02-25 Thread Tom Kijas
https://bugs.kde.org/show_bug.cgi?id=376866

--- Comment #4 from Tom Kijas  ---
Sure, here it is.

tomas@Ubuntu-Tomas:~$ env
XDG_VTNR=7
PAM_KWALLET5_LOGIN=/tmp/kwallet5_tomas.socket
SSH_AGENT_PID=1723
XDG_SESSION_ID=2
CLUTTER_IM_MODULE=xim
SHELL=/bin/bash
TERM=xterm-256color
KONSOLE_DBUS_SERVICE=:1.97
QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
KONSOLE_PROFILE_NAME=Výchozí
GS_LIB=/home/tomas/.fonts
WINDOWID=12582918
SHELL_SESSION_ID=65aae2a1e8e84f61bbbdefeb209d5bd2
QSG_RENDER_LOOP=
KDE_FULL_SESSION=true
XDG_SESSION_CLASS=user
USER=tomas
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
XCURSOR_SIZE=0
QT_ACCESSIBILITY=1
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
QT_AUTO_SCREEN_SCALE_FACTOR=0
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
SSH_AUTH_SOCK=/tmp/ssh-k4TxWQTn7Jej/agent.1670
DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path
SESSION_MANAGER=local/Ubuntu-Tomas:@/tmp/.ICE-unix/2007,unix/Ubuntu-Tomas:/tmp/.ICE-unix/2007
XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg
DESKTOP_SESSION=/usr/share/xsessions/plasma
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
QT_IM_MODULE=ibus
PWD=/home/tomas
XDG_SESSION_TYPE=x11
XMODIFIERS=@im=ibus
KONSOLE_DBUS_WINDOW=/Windows/1
LANG=cs_CZ.UTF-8
KDE_SESSION_UID=1000
MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path
KONSOLE_DBUS_SESSION=/Sessions/1
HOME=/home/tomas
SHLVL=1
XDG_SEAT=seat0
COLORFGBG=15;0
LANGUAGE=
KDE_SESSION_VERSION=5
XCURSOR_THEME=Breeze_Snow
LOGNAME=tomas
XDG_SESSION_DESKTOP=KDE
QT4_IM_MODULE=xim
XDG_DATA_DIRS=/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-nZC1saBh08,guid=5b09848b0fcc42b698f6803058b15273
LESSOPEN=| /usr/bin/lesspipe %s
DISPLAY=:0
XDG_RUNTIME_DIR=/run/user/1000
PROFILEHOME=
XDG_CURRENT_DESKTOP=KDE
GTK_IM_MODULE=xim
LESSCLOSE=/usr/bin/lesspipe %s %s
XAUTHORITY=/home/tomas/.Xauthority
QMLSCENE_DEVICE=
COLORTERM=truecolor
_=/usr/bin/env
tomas@Ubuntu-Tomas:~$ 

BTW I deleted ~/.local and ~/.cache and ~/.kde folders and after some hiccups
it worked for a day... then, after reboot, the problem is the same.

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

[kio-extras] [Bug 376867] sftp connect issue "Failed to resolve hostname = (Name or service not known)"

2017-02-25 Thread Vadim
https://bugs.kde.org/show_bug.cgi?id=376867

Vadim  changed:

   What|Removed |Added

 CC||vadims.zen...@gmail.com

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

[kio-extras] [Bug 376867] sftp connect issue "Failed to resolve hostname = (Name or service not known)"

2017-02-25 Thread Vadim
https://bugs.kde.org/show_bug.cgi?id=376867

Vadim  changed:

   What|Removed |Added

 CC|vadims.zen...@gmail.com |

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #21 from ykmssg-...@yahoo.co.uk ---
Created attachment 104223
  --> https://bugs.kde.org/attachment.cgi?id=104223&action=edit
caught after polkit reinstall and deps with KDE apps

After removing polkit and reinstalling all the essential deps back again after
a few reboots, first there was a component crash in the top right of screen but
no indication of which (shall have to crawl through the journalctl (shall see
if I can see anything) did a couple of logins after reinstalling KDE and apps
('cause polkit requires loads of deps) kdecrashed + other.
This was noticed on my initial install (lots of crashes, like the snapshot) but
didn't catch it with screenshot

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

[kdeconnect] [Bug 376911] no devices

2017-02-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376911

--- Comment #22 from ykmssg-...@yahoo.co.uk ---
As you would guess! no change in the kdeconnect💣

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

  1   2   >