[kwin] [Bug 377413] New: Kwin crash from time to time

2017-03-09 Thread Alessandro
https://bugs.kde.org/show_bug.cgi?id=377413

Bug ID: 377413
   Summary: Kwin crash from time to time
   Product: kwin
   Version: 5.9.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: alessandro.sturni...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.9.3)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.4.49-16-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed: Sometimes kwin crash after
login, but more frequently it crash during normal usage.
I've 3d effects on, and nvidia proprietary driver installed.

The crash can be reproduced sometimes.

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

Thread 5 (Thread 0x7f06912c7700 (LWP 3413)):
#0  0x7f06c668e0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f06c2a73b1b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f06c2a73b49 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f06c6689734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f06c63c7d3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f06a0bdc700 (LWP 3408)):
#0  0x7f06c668e458 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f06a0e94e44 in  () at /usr/lib64/libGLX_nvidia.so.0
#2  0x7f0692fd5394 in  () at /usr/lib64/libnvidia-glcore.so.378.13
#3  0x7f06a0e9412c in  () at /usr/lib64/libGLX_nvidia.so.0
#4  0x7f06c6689734 in start_thread () at /lib64/libpthread.so.0
#5  0x7f06c63c7d3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f06a1922700 (LWP 3406)):
#0  0x7f06c63bf55f in ppoll () at /lib64/libc.so.6
#1  0x7f06c3ae68b1 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f06c3ae7e7f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f06c3a9a6ab in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f06c38e29aa in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f06c38e7019 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f06c6689734 in start_thread () at /lib64/libpthread.so.0
#7  0x7f06c63c7d3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f06b10ad700 (LWP 3302)):
#0  0x7f06c6690d1d in read () at /lib64/libpthread.so.0
#1  0x7f06bafa3670 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f06baf62e49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f06baf632a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f06baf6342c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f06c3aea88c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f06c3a9a6ab in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f06c38e29aa in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f06bd61fd15 in  () at /usr/lib64/libQt5DBus.so.5
#9  0x7f06c38e7019 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f06c6689734 in start_thread () at /lib64/libpthread.so.0
#11 0x7f06c63c7d3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f06c6c41940 (LWP 3298)):
[KCrash Handler]
#6  0x7f06c63128d7 in raise () at /lib64/libc.so.6
#7  0x7f06c6313caa in abort () at /lib64/libc.so.6
#8  0x7f06c38d26fe in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f06c38e1be4 in QThread::~QThread() () at /usr/lib64/libQt5Core.so.5
#10 0x7f06c38e1c39 in QThread::~QThread() () at /usr/lib64/libQt5Core.so.5
#11 0x7f06c3ac2f65 in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#12 0x7f06c3acc41e in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#13 0x7f06a39b6bc9 in KWin::X11StandalonePlatform::~X11StandalonePlatform()
() at /usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#14 0x7f06c3ac2f65 in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#15 0x7f06c3acc41e in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#16 0x7f06c3a9dcee in QCoreApplication::~QCoreApplication() () at
/usr/lib64/libQt5Core.so.5
#17 0x7f06c3fe7b37 in QGuiApplication::~QGuiApplication() () at
/usr/lib64/libQt5Gui.so.5
#18 0x7f06c474fe0a in QApplication::~QApplication() () at
/usr/lib64/libQt5Widgets.so.5
#19 0x7f06c68a5949 in  () at /usr/lib64/libkdeinit5_kwin_x11.so
#20 0x7f06c68a78ef in kdemain () at /usr/lib64/libkdeinit5_kwin_x11.so
#21 0x7f06c62fe6e5 in __libc_start_main () at /lib64/libc.so.6
#22 0x00400809 in _start ()

Reported using DrKonqi

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

[frameworks-kdoctools] [Bug 377406] Fails to build on windows with linker error

2017-03-09 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=377406

--- Comment #2 from Luigi Toscano  ---
Created attachment 104468
  --> https://bugs.kde.org/attachment.cgi?id=104468&action=edit
Do not link the same functions both directly and through the library meinproc5

Unless... can you please try the attached patch? It still compiles locally
(tested on Debian), so it may work, if I read the error correctly.

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

[konsole] [Bug 377414] New: Bookmark should also store tab name

2017-03-09 Thread Ovidiu-Florin BOGDAN
https://bugs.kde.org/show_bug.cgi?id=377414

Bug ID: 377414
   Summary: Bookmark should also store tab name
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: bookmark
  Assignee: konsole-de...@kde.org
  Reporter: ovidiu@gmail.com
  Target Milestone: ---

Tab names are an important part of differentiating tabs.

IMO a bookmark here, should also hold the tab name.

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

[krita] [Bug 377415] New: Random Animated brush always starts with the same frame

2017-03-09 Thread Nathan Lovato
https://bugs.kde.org/show_bug.cgi?id=377415

Bug ID: 377415
   Summary: Random Animated brush always starts with the same
frame
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: nathan.lovato@gmail.com
  Target Milestone: ---

Created attachment 104469
  --> https://bugs.kde.org/attachment.cgi?id=104469&action=edit
Example stamp vs brush stroke

When used, any brushstroke made with an animated brush tip set to random mode
will always start with the first frame of the brush tip.

When you use the brush as a stamp, it makes it so you can't benefit from the
randomness. Also, if your preset has a large spacing, even with multiple
brushstrokes, the repetition soon becomes visible.

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

[trojita] [Bug 377416] New: Got FETCH that is out of bounds

2017-03-09 Thread kavol
https://bugs.kde.org/show_bug.cgi?id=377416

Bug ID: 377416
   Summary: Got FETCH that is out of bounds
   Product: trojita
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: IMAP
  Assignee: trojita-b...@kde.org
  Reporter: ka...@seznam.cz
  Target Milestone: ---

I just got IMAP protocol error -

UnknownMessageIndex: Got FETCH that is out of bounds -- got 1079 messages FETCH
1080 ( FLAGS "\Recent" MODSEQ "4228166" UID "1507554")

please see https://bugzilla.redhat.com/show_bug.cgi?id=1424991 for log, I don't
see how to make the attachment private here (jkt is already on CC, just tell me
if someone else needs access)

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

[trojita] [Bug 377382] Unable to log in -- IMAP alert

2017-03-09 Thread Pali Rohár
https://bugs.kde.org/show_bug.cgi?id=377382

--- Comment #11 from Pali Rohár  ---
On Thursday 09 March 2017 07:24:37 Thomas Lübking wrote:
> https://bugs.kde.org/show_bug.cgi?id=377382
> 
> --- Comment #10 from Thomas Lübking  ---
> Evolution has OAUTH2 support - it's not exaclty proprietary (that wouldn't 
> make
> sense) but it's certainly far from unobjected, see
> https://en.wikipedia.org/wiki/OAuth#Controversy

OAUTH2 RFC does not specify exact steps for implementation and specially
how to exchange and generate tokens. That RFC is too vague for such
things, but show examples...

Basically we can say that for usage of OAUTH2 you need proprietary
extension + try to interpret vague RFC specification for OAUTH2.

And IIRC more vendors needs different client implementation of OAUTH2...

> Leaving the complexity concerns aside, there's certainly usecase for such
> system, but it's not "your MUA wants to log into your IMAP server" but more
> like "webservice foo wants to use your google drive" which you can then
> individually permit and revoke that permission w/o having to expose (and thus
> later change) your credentials.
> 
> Also I frankly wonder how google secures the OAUTH2 access of MUAs -
> "something™" will have to open a 2nd channel to google and have it ask for
> confirmation.

>From my understanding of OAUTH2: this protocol is not designed for open
source MUAs, but for servers which must not disclose their parts of
authentication/token material. Or for closed source application which
must contains data which must not be disclosed to user.

If you want to use your own application (which is fully under your
control) for OAUTH2, then you send just plain text token in protocol
(e.g. IMAP) to server (which is equivalent of user+password). And via
other channel (HTTP) you need to request for such token.

Google's implementation: On Google console website you need to register
your application. You will receive public and private tokens for your
application. Application tokens then will be used for requesting user
tokens (via web page! with user input). This token is IIRC with infinite
validity but Google can revoke it at any time. And with this (your
private) token you can request via HTTP REST API for time-limited
authentication token, which is then used in application protocol for
login (e.g. in IMAP). Note that for requesting authentication token you
just need to know your private user token and public application. So
once your private user token will be stolen anybody can login to your
account (if know application).

Which means private application token must be kept secret and to
correctly use OAUTH2 either application must be closed-source and had
obfuscated private application token in binary (and it cannot leak!) or
every user generates your own application token (this is only one
solution how to properly implement OAUTH2 for open source application).
Server needs to have ability to revoke application token at any time.

> If "someone" is your local client that opens a browser with a google link, I
> could imagine this is easily broken (by the local client never opening a
> visible webpage and just clicking "ok" for the user...) - so the client would
> have to tell the user "please log into your google account and allow me"

This is used for requesting user tokens and caller needs to know private
application token. In case whole service is running on server, then user
does not see private application token, it is exchanged between Google
server and service server.

And if correctly implemented, this step is needed only once. From
requested token you can request (now without application private parts)
time-limited access token which then you will use in IMAP (or other
protocol) for authentication.

Basically server can track for which protocols is application token (and
derived tokens) applicable.

If you think more about it you should realise that it is too
complicated, hard to properly implement and it has zero benefits for
desktop applications (comparing to plain text user+password auth).

Security throw obscurity and obfuscating plain text auth in user's
applications binaries does not work. And you can perfectly implement
time-limited protocol specified access via user+passwords also on server
without need for such thing like OAUTH2.

So I see absolutely no reason why desktop email client should implement
such thing like OAUTH2. It does not bring any security (comparing to
plain text), plain text token can be stolen in same way as plain text
passwords and proper implementation needs for user to generate
application tokens via some Google console service.

If you want to use more secure authentication then look for
SCRAM-SHA-256 which does not send any plain text information via (IMAP)
application protocol. And not for OAUTH2.

PS: Probably I used another terminology as specified in OAUTH2, I just
wanted to show how such complicated thing is working to answer Thomas's
questions.

-- 
You are r

[kdevelop] [Bug 375854] Git commit not working.

2017-03-09 Thread Nikolai
https://bugs.kde.org/show_bug.cgi?id=375854

Nikolai  changed:

   What|Removed |Added

Version|5.0.3   |5.0.4

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

[digikam] [Bug 377292] Improve GPS Correlator UI

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377292

--- Comment #9 from caulier.gil...@gmail.com ---
Git commit 2865e9325e73ff5ad408f197eb4576c583c2cf6f by Gilles Caulier, on
behalf of Wolfgang Scheffner.
Committed on 09/03/2017 at 09:17.
Pushed by cgilles into branch 'master'.

Apply patches #19, 20, 21 about geolocation editor handbook description
Note : Screenshots for this section have been alreay commited previously. Only
docbook files changes are included in this commit.

M  +4-2digikam/index.docbook
M  +186  -87   digikam/tool-geolocationeditor.docbook
M  +4-0digikam/using-mainwindow-intro.docbook
M  +5-2digikam/using-mainwindow-mapview.docbook
M  +19   -24   digikam/using-sidebar-maps.docbook
M  +2-12   showfoto/index.docbook

https://commits.kde.org/digikam-doc/2865e9325e73ff5ad408f197eb4576c583c2cf6f

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

[trojita] [Bug 377416] Got FETCH that is out of bounds

2017-03-09 Thread Jan Kundrát
https://bugs.kde.org/show_bug.cgi?id=377416

--- Comment #1 from Jan Kundrát  ---
I don't see any attachment at
https://bugzilla.redhat.com/show_bug.cgi?id=1424991 . I'm logged in as
j...@flaska.net.

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

[dolphin] [Bug 377269] dolphin hangs after opening a file

2017-03-09 Thread Ingo Ebel
https://bugs.kde.org/show_bug.cgi?id=377269

--- Comment #2 from Ingo Ebel  ---
Strange.
The moment i start the degugger. Dolphin is not usable anymore. I tried it 2
times. So can't klick on anything. And the output not helping:

Attaching to process 7633
[New LWP 7635]
[New LWP 7641]
[New LWP 7712]
[New LWP 7713]
[New LWP 7714]
[New LWP 7715]
[New LWP 7716]
[New LWP 7754]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x7f3d22d3b48d in poll () from /usr/lib/libc.so.6
(gdb) 

Any suggestions?

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

[trojita] [Bug 377416] Got FETCH that is out of bounds

2017-03-09 Thread kavol
https://bugs.kde.org/show_bug.cgi?id=377416

--- Comment #2 from kavol  ---
(In reply to Jan Kundrát from comment #1)
> I don't see any attachment at
> https://bugzilla.redhat.com/show_bug.cgi?id=1424991 . I'm logged in as
> j...@flaska.net.

hm, looks like I got the permissions logic wrong :-(

can I send it to you via email?

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

[dolphin] [Bug 377269] dolphin hangs after opening a file

2017-03-09 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=377269

--- Comment #3 from Elvis Angelaccio  ---
@Ingo that's fine, just press CTRL+C from gdb and then type 'bt'

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

[dolphin] [Bug 377269] dolphin hangs after opening a file

2017-03-09 Thread Ingo Ebel
https://bugs.kde.org/show_bug.cgi?id=377269

--- Comment #4 from Ingo Ebel  ---
Ok.
Thats still not much output :(


(gdb) Quit
(gdb) bt
#0  0x7f3d22d3b48d in poll () from /usr/lib/libc.so.6
#1  0x7f3d15c987a6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f3d15c988bc in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f3d1ceec04f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f3d1ce9589a in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f3d1ce9dde4 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#6  0x7f3d23058177 in kdemain () from /usr/lib/libkdeinit5_dolphin.so
#7  0x7f3d22c7c291 in __libc_start_main () from /usr/lib/libc.so.6
#8  0x0040065a in _start ()

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

[dolphin] [Bug 377411] Created Items Are Not Selected In Parent Folder

2017-03-09 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=377411

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
Hi, can you please provide a patch and submit it at
https://phabricator.kde.org/differential/diff/create/ ?

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

[Akonadi] [Bug 377394] Uploading a mail in a remote IMAP folder does not show progress status in Kmail

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377394

orontob...@gmail.com changed:

   What|Removed |Added

 CC||orontob...@gmail.com

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

[dolphin] [Bug 377410] Option "Open archives as folder" mounts read-only

2017-03-09 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=377410

Elvis Angelaccio  changed:

   What|Removed |Added

   Severity|minor   |wishlist
 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
Hi, Dolphin uses kio slaves to access archives, and they don't currently
provide read-write support (see for example
https://bugs.kde.org/show_bug.cgi?id=77127).

That said, integration with archivemount is something that could be considered.

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

[plasmashell] [Bug 372384] Memory leak in plasmashell

2017-03-09 Thread evkogan
https://bugs.kde.org/show_bug.cgi?id=372384

evkogan  changed:

   What|Removed |Added

 CC||koga...@mail.ru

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

[amarok] [Bug 335605] Change playback speed

2017-03-09 Thread Rami Lehti
https://bugs.kde.org/show_bug.cgi?id=335605

Rami Lehti  changed:

   What|Removed |Added

 CC||ram...@ipi.fi

--- Comment #4 from Rami Lehti  ---
(In reply to Myriam Schweingruber from comment #1)
> Why, what for? Could you specify a valid use case?

Also when listening to podcasts with Amarok it is useful sometimes useful to
speed up the playback.

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

[plasmashell] [Bug 372384] Memory leak in plasmashell

2017-03-09 Thread evkogan
https://bugs.kde.org/show_bug.cgi?id=372384

--- Comment #10 from evkogan  ---
I have same problem.
openSUSE Leap 42.2
plasma5-workspace 5.8.3
plasma-framework: 5.26.0
Qt; 5.6.1
Video: Intel Graphics 530

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

[digikam] [Bug 366247] Digikam writes metadata to some files only not every one

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=366247

--- Comment #14 from wildcowboy  ---
I just found out that this bug still exists.
I have been sorting pictures using Geeqie and noticed that some pictures I
facetagged in digiKam do not have keywords. Sure enough when I opened same
images in digiKam the People tag showed up in the Tags tree but not in Edit
Metadata menu (Ctrl-Shift-M)
Latest 5.5 appimage on Linux Mint 18.1

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

[okular] [Bug 376845] Okular ignores default view setting

2017-03-09 Thread Germano Massullo
https://bugs.kde.org/show_bug.cgi?id=376845

Germano Massullo  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Germano Massullo  ---
I did not know about that

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

[krita] [Bug 376597] Text created using Multiline text tool disappears when reopening .kra file and cuases Krita to crash

2017-03-09 Thread wolthera
https://bugs.kde.org/show_bug.cgi?id=376597

--- Comment #4 from wolthera  ---
Well, we actually wanted to see the file because we wanted to look inside
whether the text is saved at all :P

You can try this yourself by...

1. Making a copy of the kra file.
2. Renaming the extension to ZIP
3. Opening the zip file.
4. Looking for the ODG file that represents the vector layer.(it should be
somewhere in layers)
5. Extracting and uploading that ODG file.

Still, thank you very much for the crash. Even if it doesn't always happen with
the text-tool, that it sometimes crashes can still be related. This can happen
when you computer is trying to multi-task. Sometimes it can then get a little
confused because it finishes one task before the other, so it might be we need
to write some code to help resolve this type of confusion.

We're hoping to rewrite the text-tool coming months, so crash reports like
these can help us make it stabler. I am still a little worried about it not
saving though, so I hope you can find whether there's an ODG file inside the
kra.

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

[krita] [Bug 376597] Text created using Multiline text tool disappears when reopening .kra file and cuases Krita to crash

2017-03-09 Thread wolthera
https://bugs.kde.org/show_bug.cgi?id=376597

wolthera  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #5 from wolthera  ---
Oh yeah, setting this as confirmed as there's a backtrace.

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

[digikam] [Bug 377417] New: Item - Open & Item - Open with Default Application not working for video files

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377417

Bug ID: 377417
   Summary: Item - Open & Item - Open with Default Application not
working for video files
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: AlbumsView
  Assignee: digikam-de...@kde.org
  Reporter: aegor...@gmail.com
  Target Milestone: ---

Terminal output:
VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
[00605148] core libvlc: Running vlc with the default interface. Use
'cvlc' to use vlc without interface.
This application failed to start because it could not find or load the Qt
platform plugin "xcb"
in "".

Reinstalling the application may fix this problem.
Latest AppImage

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

[digikam] [Bug 377417] Item - Open & Item - Open with Default Application not working for video files

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377417

--- Comment #1 from wildcowboy  ---
It does work for images though

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

[digikam] [Bug 377418] New: Crash on saving metadata. Latest AppImage 5.5

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377418

Bug ID: 377418
   Summary: Crash on saving metadata. Latest AppImage 5.5
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: aegor...@gmail.com
  Target Milestone: ---

digikam.metaengine: Metadata for file "20161218_172327.jpg" written to file.
[New Thread 0x7fff17fff700 (LWP 21566)]
[Switching to Thread 0x7fff15924700 (LWP 21565)]

Thread 231 "Thread (pooled)" hit Catchpoint 1 (exception thrown),
0x7fffee10b8bd in __cxa_throw () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0x7fffee10b8bd in __cxa_throw ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x75e8054d in VerifyXPathRoot (expandedXPath=0x7fff15922420, 
propName=0x7fff20064548 "hierarchicalSubject", 
schemaURI=0x7fff2007f588 "http://ns.adobe.com/lightroom/1.0/";)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPCore_Impl.cpp:173
#2  ExpandXPath (
schemaNS=schemaNS@entry=0x7fff2007f588
"http://ns.adobe.com/lightroom/1.0/";, propPath=propPath@entry=0x7fff20034ef8
"hierarchicalSubject", 
expandedXPath=expandedXPath@entry=0x7fff15922420)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPCore_Impl.cpp:688
#3  0x75e88166 in XMPMeta::SetProperty (this=this@entry=
0x7fff200852f0, 
schemaNS=schemaNS@entry=0x7fff2007f588
"http://ns.adobe.com/lightroom/1.0/";, propName=propName@entry=0x7fff20034ef8
"hierarchicalSubject", 
propValue=propValue@entry=0x0, options=options@entry=512)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/XMPMeta-GetSet.cpp:460
#4  0x75e756fa in WXMPMeta_SetProperty_1 (xmpRef=0x7fff200852f0, 
schemaNS=0x7fff2007f588 "http://ns.adobe.com/lightroom/1.0/";, 
propName=0x7fff20034ef8 "hierarchicalSubject", propValue=0x0, options=512, 
---Type  to continue, or q  to quit---
wResult=0x7fff159224e0)
at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/src/WXMPMeta.cpp:529
#5  0x75e63428 in TXMPMeta::SetProperty (
this=this@entry=0x7fff15922900, schemaNS=, 
propName=, propValue=propValue@entry=0x0, 
options=options@entry=512)
at
/b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/xmpsdk/include/client-glue/TXMPMeta.incl_cpp:421
#6  0x75e6025e in Exiv2::XmpParser::encode (
xmpPacket="

http://www.w3.org/1999/02/22-rdf-syntax-ns#\";>
 to continue, or q  to quit---
this=0x7fff20077a60, finfo=...)
at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine_p.cpp:192
#11 0x767f0b59 in Digikam::MetaEngine::save (this=0x7fff15923650, 
imageFilePath=...)
at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine.cpp:419
#12 0x767f16a1 in Digikam::MetaEngine::applyChanges (
this=this@entry=0x7fff15923650)
at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine.cpp:449
#13 0x7682d119 in Digikam::DMetadata::applyChanges (
this=this@entry=0x7fff15923650)
at /b/dktemp/digikam-master/core/libs/dmetadata/dmetadata.cpp:116
#14 0x77779062 in Digikam::MetadataHub::writeToMetadata (
this=this@entry=0x7fff159236e0, info=..., writeMode=writeMode@entry=..., 
ignoreLazySync=ignoreLazySync@entry=false, settings=...)
at /b/dktemp/digikam-master/core/libs/fileactionmanager/metadatahub.cpp:263
#15 0x77783bdd in Digikam::FileActionMngrFileWorker::writeMetadata (
this=0xba9e40, infos=..., flags=128)
at
/b/dktemp/digikam-master/core/libs/fileactionmanager/fileworkeriface.cpp:131
#16 0x77786d9e in Digikam::FileWorkerInterface::qt_static_metacall (
_o=0xba9e40, _c=, _id=, _a=)
at
/b/dktemp/digikam-master/build/core/libs/fileactionmanager/moc_fileworkeriface.cpp:103
---Type  to continue, or q  to quit---
#17 0x0031e04b0e6a in QObject::event(QEvent*) ()
   from /tmp/.mount_9GSMRx/usr/lib/libQt5Core.so.5
#18 0x7fffef3978fc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /tmp/.mount_9GSMRx/usr/lib/libQt5Widgets.so.5
#19 0x7fffef39e808 in QApplication::notify(QObject*, QEvent*) ()
   from /tmp/.mount_9GSMRx/usr/lib/libQt5Widgets.so.5
#20 0x0031e04880f0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /tmp/.mount_9GSMRx/usr/lib/libQt5Core.so.5
#21 0x0031e048a03b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /tmp/.mount_9GSMRx/usr/lib/libQt5Core.so.5
#22 0x0031e04d5993 in ?? () from /tmp/.mount_9GSMRx/usr/lib/libQt5Core.so.5
#23 0x7fffecc58197 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fffecc583f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fffecc5849c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x0031e04d5d87 in

[digikam] [Bug 377418] Crash on saving metadata. Latest AppImage 5.5

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377418

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
It's clear. It crash in Exiv2, XMP parser class, and finaly in Adobe XMP SDK.
Probably something from your image in XMP metadata is not well interpreted by
Exiv2.

Reprot this problem as UPSTREAM to Exiv2 team with the image file for
investiguation (20161218_172327.jpg)

Gilles Caulier

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

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-09 Thread Kestutis
https://bugs.kde.org/show_bug.cgi?id=375536

Kestutis  changed:

   What|Removed |Added

 CC||kestuti...@gmail.com

--- Comment #3 from Kestutis  ---
Same here, except my keyboard layout is IE. 
I had SDDM , and thought that bug was SDDM related, therefore switched to
Lightdm.
Even after "apt-get purge sddm" I found plenty lefover files.And my lockscreen
is still old SDDm theme. But what I do, is start a new session (after failed
login), where I get lightdm themed screenlock, then after typing password I'm
brought back to old session.
Other way is from tty1 issue :
loginctl unlock-sessions

Its Debian Stretch, amd64, intel graphic.
I'm noob , but I wish I could help here, and if any logs would help, please let
me know. 
Thanks

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

[plasma-nm] [Bug 377345] Network Manager Import VPN Crashes With Wayland

2017-03-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377345

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |5.8.4
Product|kde |plasma-nm
   Assignee|unassigned-b...@kde.org |jgrul...@redhat.com
  Component|general |editor

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

[kdelibs] [Bug 377350] KDE Chrash directly after Login via rdp

2017-03-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377350

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[KScreen] [Bug 357253] xrdp - Crash after logon

2017-03-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=357253

Christoph Feck  changed:

   What|Removed |Added

 CC||rabenh...@gmail.com

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

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

[kget] [Bug 332191] Kget crash after server authenticate cancel

2017-03-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=332191

Christoph Feck  changed:

   What|Removed |Added

 CC||fhj52.i...@gmail.com

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

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

[kget] [Bug 377288] kget crashes

2017-03-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377288

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[kleopatra] [Bug 377403] The GPGME library returned an unexpected error at gpafiledecryptop.c:534

2017-03-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377403

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Reported as bug 377402.

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

[Akonadi] [Bug 377399] kontact loses imap connections constantly

2017-03-09 Thread Steve
https://bugs.kde.org/show_bug.cgi?id=377399

Steve  changed:

   What|Removed |Added

Summary|kontact loses imap  |kontact loses imap
   |connections constatntly |connections constantly

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

[partitionmanager] [Bug 377232] Allow to backup the entire disk

2017-03-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=377232

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[Akonadi] [Bug 377399] kontact loses imap connections constantly

2017-03-09 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=377399

Rex Dieter  changed:

   What|Removed |Added

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

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

[Akonadi] [Bug 377393] /usr/bin/akonadiserver crashes

2017-03-09 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=377393

Rex Dieter  changed:

   What|Removed |Added

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

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

[kontact] [Bug 377395] Kontact is crashing during start up

2017-03-09 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=377395

Rex Dieter  changed:

   What|Removed |Added

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

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

[kontact] [Bug 377395] Kontact is crashing during start up

2017-03-09 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=377395

--- Comment #1 from Rex Dieter  ---
This one looks to be crashing down in QtWebEngine for some reason,

Thread 13 (Thread 0x7fe6627fc700 (LWP 6031)):
[KCrash Handler]
#6  0x7fe6a9b5db3e in
QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*,
base::Callback const&, GURL*) () at /lib64/libQt5WebEngineCore.so.5
#7  0x7fe6aa451210 in
net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*,
base::Callback const&, GURL*) () at /lib64/libQt5WebEngineCore.so.5
#8  0x7fe6aa415800 in net::URLRequest::Start() () at
/lib64/libQt5WebEngineCore.so.5

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

[valgrind] [Bug 144362] Uninitialized parameters to malloc not warned about.

2017-03-09 Thread Vladimir Marko
https://bugs.kde.org/show_bug.cgi?id=144362

Vladimir Marko  changed:

   What|Removed |Added

 CC||swe...@gmail.com

--- Comment #2 from Vladimir Marko  ---
Similarly, uninitialized parameters to

  VALGRIND_MAKE_MEM_NOACCESS()
  VALGRIND_MAKE_MEM_UNDEFINED()
  VALGRIND_MAKE_MEM_DEFINED()

should be reported. See

 
https://android-review.googlesource.com/#/c/307010/14..15/runtime/base/arena_allocator.cc

where it took a long time (and some luck) to track down the uninitialized value
being passed to VALGRIND_MAKE_MEM_NOACCESS().

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

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

2017-03-09 Thread zephyrus00jp
https://bugs.kde.org/show_bug.cgi?id=377006

--- Comment #8 from zephyrus00jp  ---
Created attachment 104470
  --> https://bugs.kde.org/attachment.cgi?id=104470&action=edit
A log of valgrind experiencing SIGSEGV under 4.9.x kernel: with full vlgrind
options

This log is obtained by running
valgrind under a wrapper called run-valgrind (of my creation).
This wrapper runs valgrind with suitable parameters to monitor thunderbird
binary as follows.

valgrind --trace-children=yes --fair-sched=yes --smc-check=all-non-file
--gen-suppressions=all --vex-iropt-register-updates=allregs-at-mem-access
--child-silent-after-fork=yes
--trace-children-skip=/usr/bin/hg,/bin/rm,*/bin/certutil,*/bin/pk12util,*/bin/ssltunnel,*/bin/uname,*/bin/which,*/bin/ps,*/bin/grep,*/bin/java
--num-transtab-sectors=24 --tool=memcheck --freelist-vol=5
--redzone-size=128 --px-default=allregs-at-mem-access
--px-file-backed=unwindregs-at-mem-access --malloc-fill=0xA5 --free-fill=0xC3
--num-callers=50 --suppressions=$HOME/Dropbox/myown.sup
--show-mismatched-frees=no --show-possibly-lost=no --read-inline-info=yes
--trace-syscalls=yes /NREF-COMM-CENTRAL/objdir-tb3/dist/bin/thunderbird-bin


The process IDs that appear are:
pid 28538: the binary wrapper run-valgrind

pid 28539: from the wrapper valgrind is executed by calling system() library
call.
[pid 28539] execve("/bin/sh", ["sh", "-c", "valgrind --trace-children=yes
--"...], [/* 65 vars */]) = 0

pid 28540: from the spawned shell valgrind is run
[pid 28540] execve("/usr/local/bin/valgrind", ["valgrind",
"--trace-children=yes", "--fair-sched=yes", "--smc-check=all-non-file",
"--gen-suppressions=all", "--vex-iropt-register-updates=all"...,
"--child-silent-after-fork=yes", "--trace-children-skip=/usr/bin/h"...,
"--num-transtab-sectors=24", "--tool=memcheck", "--freelist-vol=5",
"--redzone-size=128", "--px-default=allregs-at-mem-acce"...,
"--px-file-backed=unwindregs-at-m"..., "--malloc-fill=0xA5",
"--free-fill=0xC3", "--num-callers=50", "--suppressions=/home/ishikawa/Dr"...,
"--show-mismatched-frees=no", "--show-possibly-lost=no",
"--read-inline-info=yes", "--trace-syscalls=yes",
"/NREF-COMM-CENTRAL/objdir-tb3/di"...], [/* 65 vars */] 

Near the end of the log, we see the following two lines:

[pid 28540] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
si_addr=0xffeffa1fc} ---
[pid 28540] +++ killed by SIGSEGV +++

So it is pid 28540 that gets killed by SIGSEGV: pid 28540 is for
/usr/local/bin/valgrind thus invoked.

There are two PCs which I cannot easily access all the time.
Sorry for slightly different file layout on two PCs.

TIA

PS: I am trying to create a valgrind-enabled thunderbird binary on mozilla's
compilation farm. But I have hit some unexpected difficulties for now.
(The particular CPU farm does NOT have valgrind headers. Ugh.)
I am trying to have it installed. Stay tuned.

The series of patches AND parameters that I use to create comm-central
thunderbird is captured in a few shell scripts, but they are rather complex and
need customization: I am not quire sure if I can simply post the shell script
and people to modify it to their environment. I may not be available for
consultation always. So I thought creating a binary on a shared computer is
much better.

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

[rsibreak] [Bug 377419] New: End of short/long break notifies all the time

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=377419

Bug ID: 377419
   Summary: End of short/long break notifies all the time
   Product: rsibreak
   Version: 0.12.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: aa...@kde.org
  Reporter: promike1...@gmail.com
  Target Milestone: ---

Notifications 'end of short/long breaks' notify even when they are not needed.
Tiny breaks are currently set to 20 seconds. I set a sound to end of short
break, but it was irritating since it played the sound in every 20 seconds.
I think that what the 'when the short timer has been reset' is for, and it does
the job well. End of short/long break should notify only when there was a
break.

I think at this very moment the timers reset and end of breaks are do the very
same.

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

[valgrind] [Bug 377420] New: Valgrind is missing an armv7 instruction

2017-03-09 Thread Alberto Ruiz
https://bugs.kde.org/show_bug.cgi?id=377420

Bug ID: 377420
   Summary: Valgrind is missing an armv7 instruction
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: ar...@gnome.org
  Target Milestone: ---

disInstr(arm): unhandled instruction: 0xEC510F1E
 cond=14(0xE) 27:20=197(0xC5) 4:4=1 3:0=14(0xE)
==13274== valgrind: Unrecognised instruction at address 0x507b468.
==13274==at 0x507B468: _armv7_tick (armv4cpuid.S:94)
==13274== Your program just tried to execute an instruction that Valgrind
==13274== did not recognise.  There are two possible reasons for this.
==13274== 1. Your program has a bug and erroneously jumped to a non-code
==13274==location.  If you are running Memcheck and you just saw a
==13274==warning about a bad jump, it's probably your program's fault.
==13274== 2. The instruction is legitimate but Valgrind doesn't handle it,
==13274==i.e. it's Valgrind's fault.  If you think this is the case or
==13274==you are not sure, please let us know and we'll try to fix it.
==13274== Either way, Valgrind will now raise a SIGILL signal which will
==13274== probably kill your program.

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

[valgrind] [Bug 377420] Valgrind is missing an armv7 instruction

2017-03-09 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=377420

Peter Maydell  changed:

   What|Removed |Added

 CC||peter.mayd...@linaro.org

--- Comment #1 from Peter Maydell  ---
Looks like the same as bug 344082 to me (insn is reading CNTVCT).

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

[valgrind] [Bug 377420] Valgrind is missing an armv7 instruction

2017-03-09 Thread Peter Maydell
https://bugs.kde.org/show_bug.cgi?id=377420

--- Comment #2 from Peter Maydell  ---
Doh, I meant bug 344802...

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

[valgrind] [Bug 377420] Valgrind is missing an armv7 instruction

2017-03-09 Thread Alberto Ruiz
https://bugs.kde.org/show_bug.cgi?id=377420

--- Comment #3 from Alberto Ruiz  ---
(In reply to Peter Maydell from comment #1)
> Looks like the same as bug 344082 to me (insn is reading CNTVCT).

That bug seems unrelated to valgrind.

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

[valgrind] [Bug 377420] Valgrind is missing an armv7 instruction

2017-03-09 Thread Alberto Ruiz
https://bugs.kde.org/show_bug.cgi?id=377420

--- Comment #4 from Alberto Ruiz  ---
(In reply to Peter Maydell from comment #2)
> Doh, I meant bug 344802...

that makes more sense now :D

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

[ark] [Bug 377421] New: Ark claims to delete file from APK while it didn't

2017-03-09 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=377421

Bug ID: 377421
   Summary: Ark claims to delete file from APK while it didn't
   Product: ark
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: k...@privat.broulik.de
CC: rthoms...@gmail.com
  Target Milestone: ---

When manually deleting files from a .apk file (I know this breaks signing and
what not but I wanted to test something) it asks whether I'm really sure and
then removes the file from the list.

However, it didn't actually delete the file and on re-opening the file the next
time it's there again (also file size didn't change). If I just rename the file
from .apk to .zip it works just fine.

Wild guess: could it be that the zip cmdline tool it uses in the background
refuses because it doesn't have a "zip" file extension? In any case it should
not lie to me by showing the file being succesfully deleted. ;)

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

[digikam] [Bug 377422] New: Main window got stuck in Full Screen mode

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=377422

Bug ID: 377422
   Summary: Main window got stuck in Full Screen mode
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: AlbumsView
  Assignee: digikam-de...@kde.org
  Reporter: aegor...@gmail.com
  Target Milestone: ---

Light Table is fine (Ctrl+L)
Here is what happens when I press Exit Full Screen / Full Screen:
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN ON fullscreen
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN OFF fullscreen
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN ON fullscreen
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN OFF fullscreen
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN ON fullscreen
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN OFF fullscreen
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN ON fullscreen
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN OFF fullscreen
digikam.general: Stacked View Mode :  0
digikam.widgets: TURN ON fullscreen
digikam.general: Stacked View Mode :  0
...
Linux Mint 18.1 Cinnamon

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

[kwin] [Bug 377336] Weird behaviour of mouse cursor in games

2017-03-09 Thread Aleksey Samoilov
https://bugs.kde.org/show_bug.cgi?id=377336

--- Comment #5 from Aleksey Samoilov  ---
Update: after last updates from KDE Neon repo, Xonotic works fine in window and
fullscreen mode. OpenArena works fine in window mode to, but in fullscreen
still have an this issue. And in order to navigate in game menu (for example to
normal quit) you have to press and hold the "Esc" button (when appear "Pointer
motion confined to the current window"). It's annoying.

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

[marble] [Bug 377423] New: marble: legend panel: text colour fixed to black

2017-03-09 Thread Thomas Posch
https://bugs.kde.org/show_bug.cgi?id=377423

Bug ID: 377423
   Summary: marble: legend panel: text colour fixed to black
   Product: marble
   Version: 2.1 (KDE Applications 16.12)
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: bugs.kde@online.posch.name
  Target Milestone: ---

In the legend panel the text colour does not follow the theme.
This leads to poor readability.

Steps to reproduce:
  * Choose Breeze Dark theme.
  * Open marble.
  * Try to read legend.

Note: To show the legend panel, check Settings->Panels->Legend.

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

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-09 Thread Kestutis
https://bugs.kde.org/show_bug.cgi?id=375536

--- Comment #4 from Kestutis  ---
ok, so I manage to find some logs related to this:

/var/log/auth.log
9 14:13:12 DebianStretchPC unix_chkpwd[6242]: check pass; user unknown
Mar  9 14:13:12 DebianStretchPC unix_chkpwd[6243]: check pass; user unknown
Mar  9 14:13:12 DebianStretchPC unix_chkpwd[6243]: password check failed for
user (kiesha)
Mar  9 14:13:12 DebianStretchPC kcheckpass[6241]: pam_unix(kde:auth):
authentication failure; logname= uid=1000 euid=1000 tty=:0 ruser= rhost= 
user=kiesha
Mar  9 14:13:12 DebianStretchPC kcheckpass[6241]: Authentication failure for
kiesha (invoked by uid 1000)
Mar  9 14:13:18 DebianStretchPC lightdm: pam_unix(lightdm-greeter:session):
session opened for user lightdm by (uid=0)
Mar  9 14:13:18 DebianStretchPC systemd-logind[494]: New session c10 of user
lightdm.
Mar  9 14:13:27 DebianStretchPC lightdm: pam_unix(lightdm-greeter:session):
session closed for user lightdm
Mar  9 14:13:30 DebianStretchPC sudo:   kiesha : TTY=pts/1 ; PWD=/home/kiesha ;
USER=root ; COMMAND=/usr/bin/tail -n 70 /var/log/auth.log
Mar  9 14:13:30 DebianStretchPC sudo: pam_unix(sudo:session): session opened
for user root by kiesha(uid=0)

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

[kdevelop] [Bug 373996] Crash when try to delete file from "Save as..." dialog

2017-03-09 Thread Pilzschaf
https://bugs.kde.org/show_bug.cgi?id=373996

Pilzschaf  changed:

   What|Removed |Added

 CC||pilzsc...@t-online.de

--- Comment #4 from Pilzschaf  ---
Also works for me. Can't reproduce crash

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

[plasmashell] [Bug 372384] Memory leak in plasmashell

2017-03-09 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=372384

--- Comment #11 from David Edmundson  ---
Thanks for doing that heapprofile output, it would be ideal, except for the
fact you can't profile on one machine and profile on another. It tries to
resolve symbols that simply won't match :S 

The valgrind output had one useful piece:
=== 39,846,072 bytes in 8 blocks are possibly lost in loss record 77,372 of
77,372
====at 0x4C2CB3F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
====by 0x22EBAC48: ??? (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.28)
====by 0x245CA6D6: ??? (in
/usr/lib/nvidia-370/libnvidia-glcore.so.370.28)
====by 0x245B7A9C: ??? (in
/usr/lib/nvidia-370/libnvidia-glcore.so.370.28)
====by 0x24691AA3: ??? (in
/usr/lib/nvidia-370/libnvidia-glcore.so.370.28)
====by 0x246933EA: ??? (in
/usr/lib/nvidia-370/libnvidia-glcore.so.370.28)
====by 0x2431B1B8: ??? (in
/usr/lib/nvidia-370/libnvidia-glcore.so.370.28)
====by 0x243250A7: ??? (in
/usr/lib/nvidia-370/libnvidia-glcore.so.370.28)
====by 0x2432910C: ??? (in
/usr/lib/nvidia-370/libnvidia-glcore.so.370.28)
====by 0x24342B86: ??? (in
/usr/lib/nvidia-370/libnvidia-glcore.so.370.28)
====by 0x6A464B3: glTexImage2D (qopenglfunctions.h:995)
====by 0x6A464B3: QSGAtlasTexture::Atlas::bind(QSGTexture::Filtering)
(qsgatlastexture.cpp:347)
====by 0x6A49B42:
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState
const&, QSGMaterial*, QSGMaterial*) (qsgtexturematerial.cpp:99)
====by 0x6A30101:
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
(qsgbatchrenderer.cpp:2260)
====by 0x6A31644: QSGBatchRenderer::Renderer::renderBatches()
(qsgbatchrenderer.cpp:2503)
====by 0x6A36EA4: QSGBatchRenderer::Renderer::render()
(qsgbatchrenderer.cpp:2697)
====by 0x6A428FE: QSGRenderer::renderScene(QSGBindable const&)
(qsgrenderer.cpp:217)
====by 0x6A4319A: QSGRenderer::renderScene(unsigned int)
(qsgrenderer.cpp:177)
====by 0x6A5355D: QSGRenderContext::renderNextFrame(QSGRenderer*,
unsigned int) (qsgcontext.cpp:555)
====by 0x6A9A92D: QQuickWindowPrivate::renderSceneGraph(QSize const&)
(qquickwindow.cpp:424)
====by 0x6A6C72E: QSGRenderThread::syncAndRender()
(qsgthreadedrenderloop.cpp:623)
====by 0x6A71CAB: QSGRenderThread::run()
(qsgthreadedrenderloop.cpp:704)
====by 0x9AE8C67: QThreadPrivate::start(void*) (qthread_unix.cpp:341)
====by 0xAB76709: start_thread (pthread


Which implies either we're leaking a QSGTexture somewhere. 
Or Qt isn't cleaning up properly.
Or Nvidia isn't.

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

[plasmashell] [Bug 372384] Memory leak in plasmashell

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=372384

988a...@mail.ru changed:

   What|Removed |Added

 CC|988a...@mail.ru |

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

[libkface] [Bug 358910] OpenCV 3.1 support for libkface

2017-03-09 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=358910

Rex Dieter  changed:

   What|Removed |Added

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

--- Comment #3 from Rex Dieter  ---
I can confirm libkface-16.12 works with opencv 3.1 since the referenced
reviewboard was committed

Submitted with commit ec6e82328cac37c9d59b49245b18c3f0abee4d8f by Andreas
Sturmlechner on behalf of Xuetian Weng to branch master.



(same cannot be said of opencv 3.2, but I'll file a separate bug tracking that

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

[kdevelop] [Bug 377424] New: v5.0.80-223-g20ab513d78 regressions

2017-03-09 Thread RJVB
https://bugs.kde.org/show_bug.cgi?id=377424

Bug ID: 377424
   Summary: v5.0.80-223-g20ab513d78 regressions
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: rjvber...@gmail.com
  Target Milestone: ---

Please ignore if already known:

KDevelop v5.0.80-223-g20ab513d78 introduces a number of regressions, possibly
related, among which at least

- the code parser raises multiple false alarms, apparently due in part to not
finding header files that were found before
- spurious warnings from the new cmake server feature. For example:

unhandled message
QJsonObject({"supportedProtocolVersions":[{"isExperimental":true,"major":1,"minor":0}],"type":"hello"})
error!! QJsonObject({"cookie":"","errorMessage":"Failed to activate protocol
version: \"CMAKE_HOME_DIRECTORY\" is set but incompatible with configured
source directory value.","inReplyTo":"handshake","type":"error"})
kdevelop.projectmanagers.cmake: couldn't load json successfully "purpose"
kdevelop.projectmanagers.cmake: couldn't load json successfully "purpose"
unhandled message
QJsonObject({"supportedProtocolVersions":[{"isExperimental":true,"major":1,"minor":0}],"type":"hello"})
error!! QJsonObject({"cookie":"","errorMessage":"Failed to activate protocol
version: \"CMAKE_HOME_DIRECTORY\" is set but incompatible with configured
source directory value.","inReplyTo":"handshake","type":"error"})
kdevelop.projectmanagers.cmake: couldn't load json successfully "kf5-kdevelop-5
(MP)"
kdevelop.projectmanagers.cmake: couldn't load json successfully "kf5-kdevelop-5
(MP)"
kdevelop.projectmanagers.cmake: cmake server socket error:
QLocalSocket::ServerNotFoundError "/tmp/kdevelopcmake-.W18688"
unhandled message
QJsonObject({"supportedProtocolVersions":[{"isExperimental":true,"major":1,"minor":0}],"type":"hello"})
error!! QJsonObject({"cookie":"","errorMessage":"Failed to activate protocol
version: \"CMAKE_HOME_DIRECTORY\" is set but incompatible with configured
source directory value.","inReplyTo":"handshake","type":"error"})
kdevelop.projectmanagers.cmake: couldn't load json successfully
"kf5-kdevplatform-5 (MP)"
kdevelop.projectmanagers.cmake: couldn't load json successfully
"kf5-kdevplatform-5 (MP)"
Reusing existing ksycoca
Recreating ksycoca file
("/home/bertin/.cache/ksycoca5_en-GB_mAClIZ0r_bjiwdrSoxoVtRb9pr8=", version
303)
Still in the time dict (i.e. deleted files) ("apps")
Saving
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
unhandled message
QJsonObject({"supportedProtocolVersions":[{"isExperimental":true,"major":1,"minor":0}],"type":"hello"})
error!! QJsonObject({"cookie":"","errorMessage":"Failed to activate protocol
version: \"CMAKE_HOME_DIRECTORY\" is set but incompatible with configured
source directory value.","inReplyTo":"handshake","type":"error"})
kdevelop.projectmanagers.cmake: couldn't load json successfully "kf5-kdevelop-5
(MP)"
kdevelop.projectmanagers.cmake: couldn't load json successfully "kf5-kdevelop-5
(MP)"
QWidget::insertAction: Attempt to insert null action
qrc:/JobDialog.qml:67: TypeError: Cannot read property 'Layout' of null
qrc:/JobDialog.qml:66: TypeError: Cannot read property 'Layout' of null
Cannot initialize model with data QJsonObject() . missing: QJsonValue(string,
"urls")
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
kdevplatform.plugins.git: couldn't find the git root for
QUrl("file:///opt/local/portia-site-ports")
kdevelop.projectmanagers.cmake: cmake server error:
QProcess::ProcessError(Crashed) "/tmp/kdevelopcmake-.f18688" "" ""
kdevelop.projectmanagers.cmake: cmake server error:
QProcess::ProcessError(Crashed) "/tmp/kdevelopcmake-.W18688" "" ""
kdevelop.projectmanagers.cmake: cmake server error:
QProcess::ProcessError(Crashed) "/tmp/kdevelopcmake-.J18688" "" ""
kdevelop.projectmanagers.cmake: cmake server error:
QProcess::ProcessError(Crashed) "/tmp/kdevelopcmake-.q18688" "" ""
register count: 0, destroy count 0: 

I have qtlogging.ini set up to show me all qCWarning output (and more severe)
but I wouldn't expect to see warnings about cmake server failures if I didn't
intend to use such a server and thus never set one up.

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

[libkface] [Bug 377425] New: libkface FTBFS against opencv-3.2.0

2017-03-09 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=377425

Bug ID: 377425
   Summary: libkface FTBFS against opencv-3.2.0
   Product: libkface
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: kde-imag...@kde.org
  Reporter: rdie...@math.unl.edu
  Target Milestone: ---

Created attachment 104471
  --> https://bugs.kde.org/attachment.cgi?id=104471&action=edit
error output of 'make -k'

Latest libkface (both 16.12.3 and master branch
be78bce9dc5124896e6e50f45f5575c175adf454 ), fail to build against recent OpenCV
3.2.0 release.

Attached is the output of 'make -k' (on fedora 25)

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

[libkface] [Bug 377425] libkface FTBFS against opencv-3.2.0

2017-03-09 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=377425

Rex Dieter  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Rex Dieter  ---
marking confirmed, fails on newer fedora releases too (where we first noticed
it)

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

[kdenlive] [Bug 371062] audio on some clips does not match playhead position - only plays later audio, never earlier

2017-03-09 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=371062

--- Comment #2 from S. Christian Collins  ---
Created attachment 104472
  --> https://bugs.kde.org/attachment.cgi?id=104472&action=edit
video showing the bug

I can repro this 100% using Kdenlive 16.12.2 with MLT 6.5.0 (appimage). Video
attached.

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

[kdenlive] [Bug 371849] audio file sounds "clicky" when on project timeline; affects rendered file

2017-03-09 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=371849

--- Comment #10 from S. Christian Collins  ---

I can repro this 100% using Kdenlive 16.12.2 with MLT 6.5.0 (appimage).

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

[kdenlive] [Bug 371849] audio file sounds "clicky" when on project timeline; affects rendered file

2017-03-09 Thread S . Christian Collins
https://bugs.kde.org/show_bug.cgi?id=371849

--- Comment #11 from S. Christian Collins  ---
(In reply to S. Christian Collins from comment #10)
> I can repro this 100% using Kdenlive 16.12.2 with MLT 6.5.0 (appimage).

Just realized my comment might have been a bit unclear. I can reproduce the bug
every time is what I should have said.

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

[digikam] [Bug 376952] AppImage Video playback issues - no sound

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376952

--- Comment #16 from caulier.gil...@gmail.com ---
I fixed the problem using current QtAv implementation in digiKam AppImage. I
just recompiled quickly the 64 bits bundle for testing without translations.

The audio from video is played well now under Linux.

Please test and give me a feedback. File is at usual place :

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

PS : i will recompile a complete bundle with translations later today, if time
permit, else tomorrow.

Gilles Caulier

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

[kwin] [Bug 377413] Kwin crash from time to time

2017-03-09 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=377413

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is lacking debug symbols. If you are able to 
reproduce please install the debug packages provided by your 
distribution (please ask the distribution support channel on how to 
install them) and attach a new backtrace.

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

[digikam] [Bug 376952] AppImage Video playback issues - no sound

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=376952

--- Comment #17 from wildcowboy  ---
AppImage isn't working for me now.
---
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (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 digikam...done.
Catchpoint 1 (throw)
Starting program: /tmp/.mount_q8UWsJ/usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2ef8700 (LWP 5582)]
digikam.widgets: Breeze icons ressource file found
digikam.general: AlbumWatch use QFileSystemWatcher
[New Thread 0x7fffe167d700 (LWP 5583)]
[New Thread 0x7fffe0e7c700 (LWP 5584)]
digikam.general: Database Parameters:
   Type: "QSQLITE"
   DB Core Name: "/media/data/FamilyPictures/digikam4.db"
   DB Thumbs Name:   "/media/data/FamilyPictures/thumbnails-digikam.db"
   DB Face Name: "/media/data/FamilyPictures/recognition.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

[New Thread 0x7fffd3fff700 (LWP 5585)]
[Thread 0x7fffd3fff700 (LWP 5585) exited]
digikam.dbengine: Loading SQL code from config file
"/tmp/.mount_q8UWsJ/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  8
digikam.coredb: Core database: makeUpdates  8  to  8
digikam.database: Creating new Location  "/FamilyPictures"  uuid 
"volumeid:?uuid=e0deb5d0deb59eea"
digikam.database: location for  "/media/data/FamilyPictures"  is available 
true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  8244797440
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.general: Switch to widget style:  "Fusion"
digikam.dimg: ("/usr/share/color/icc", "/home/andrey/.local/share/icc")
[New Thread 0x7fffd3fff700 (LWP 5586)]
digikam.general: Camera XML data: 
"/home/andrey/.local/share/digikam/cameras.xml"
[New Thread 0x7fffd1610700 (LWP 5587)]
[New Thread 0x7fffd0e0f700 (LWP 5588)]
[New Thread 0x7fffc3fff700 (LWP 5589)]
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: Face database: have a structure version  "2"
digikam.facesengine: Face database ready for use
[New Thread 0x7fffc37fe700 (LWP 5590)]
[New Thread 0x7fffc2ffd700 (LWP 5591)]
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
[New Thread 0x7fffc27fc700 (LWP 5592)]
[New Thread 0x7fffc1ffb700 (LWP 5593)]
[New Thread 0x7fffc17fa700 (LWP 5594)]
[New Thread 0x7fffc0ff9700 (LWP 5595)]
[New Thread 0x7fffa3fff700 (LWP 5596)]
digikam.facesengine: Face database ready for use
[New Thread 0x7fffa37fe700 (LWP 5597)]
[New Thread 0x7fffa2ffd700 (LWP 5598)]
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
[New Thread 0x7fffa27fc700 (LWP 5599)]
[New Thread 0x7fffa1ffb700 (LWP 5604)]
[New Thread 0x7fffa17fa700 (LWP 5605)]
[New Thread 0x7fffa0ff9700 (LWP 5606)]
digikam.geoiface: "setting backend marble"
QtAV 1.11.0(Mar  9 2017, 09:49:02)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai University->S3 Graphics->Deepin, Shanghai, ChinaCopyright (C)
2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
capi::version: 0.6.0
ALSA lib conf.c:3750:(snd_config_update_r) Cannot access file
././/share/alsa/alsa.conf
ALSA lib control.c:954:(snd_ctl_open_noupdate) Inv

[digikam] [Bug 376952] AppImage Video playback issues - no sound

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=376952

--- Comment #18 from wildcowboy  ---
(In reply to caulier.gilles from comment #16)
> I fixed the problem using current QtAv implementation in digiKam AppImage. I
> just recompiled quickly the 64 bits bundle for testing without translations.
> 
> The audio from video is played well now under Linux.
Gilles.

Do you have a chance to put the previous version back to the GDrive?
I overwrote mine 
> 
> Please test and give me a feedback. File is at usual place :
> 
> https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
> 
> PS : i will recompile a complete bundle with translations later today, if
> time permit, else tomorrow.
> 
> Gilles Caulier

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

[valgrind] [Bug 144362] Uninitialized parameters to malloc not warned about.

2017-03-09 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=144362

Philippe Waroquiers  changed:

   What|Removed |Added

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

--- Comment #3 from Philippe Waroquiers  ---
(In reply to Vladimir Marko from comment #2)
Thanks for reporting the problem.
Note that in revision r13361, the bug of false negative for undefined malloc
args was fixed, and this bug should have been related to the commit, and
closed.
I guess it should be better to file a new bug related to the checking
of the valgrind client requests arguments.

> Similarly, uninitialized parar13361meters to
> 
>   VALGRIND_MAKE_MEM_NOACCESS()
>   VALGRIND_MAKE_MEM_UNDEFINED()
>   VALGRIND_MAKE_MEM_DEFINED()
> 
> should be reported. See
> 
>  
> https://android-review.googlesource.com/#/c/307010/14..15/runtime/base/
> arena_allocator.cc
> 
> where it took a long time (and some luck) to track down the uninitialized
> value being passed to VALGRIND_MAKE_MEM_NOACCESS().

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

[plasmashell] [Bug 377210] Drag files from Dolphin to another programs causes plasma crash under Wayland

2017-03-09 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=377210

Marco Martin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE
 CC||notm...@gmail.com

--- Comment #1 from Marco Martin  ---
needs full debug symbols installed to be useful

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

[KDb] [Bug 303030] Predicate does not build (probably because it assumes gcc < 4.7)

2017-03-09 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=303030

Jarosław Staniek  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[trojita] [Bug 360091] MessageWidget should reset when the current message disappears

2017-03-09 Thread Adam Chasen
https://bugs.kde.org/show_bug.cgi?id=360091

Adam Chasen  changed:

   What|Removed |Added

 CC||a...@chasen.name

--- Comment #2 from Adam Chasen  ---
This behavior is unintuitive. If you need access to a message which is no
longer in the "active folder list" then it would make sense to require
navigation to the location of that message (i.e. trash).

This state also prevents the next/previous actions (shortcuts and menu items)
from functioning.

The question is, what to you do if you don't display the message anymore? Does
the MessageWidget collapse? Does it show the next message? If it shows the
message, do you mark that message as read?

My desired behavior is to show the next message and give me an option of
marking it as read (but not automatically marking it as read).

Minimum requirement: Still allow next/previous message actions to function.

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

[plasmashell] [Bug 377426] New: Plasma (plasmashell), signal: Segmentation fault

2017-03-09 Thread Don Curtis
https://bugs.kde.org/show_bug.cgi?id=377426

Bug ID: 377426
   Summary: Plasma (plasmashell), signal: Segmentation fault
   Product: plasmashell
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugrprt21...@online.de
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
Ejecting a removable device -- the DVD player which had a DVD film in it.
The DVD Player is the Fluendo product.

The crash does not seem to be reproducible.

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

Thread 10 (Thread 0x7f82ba03c700 (LWP 26163)):
#0  0x7f839ffd73f0 in QMutex::lock() (this=this@entry=0x5b28b68) at
thread/qmutex.cpp:217
#1  0x7f83a01f1255 in postEventSourcePrepare(GSource*, gint*) (m=0x5b28b68,
this=) at ../../src/corelib/thread/qmutex.h:128
#2  0x7f83a01f1255 in postEventSourcePrepare(GSource*, gint*)
(this=0x5b28b40) at ../../src/corelib/thread/qthread_p.h:246
#3  0x7f83a01f1255 in postEventSourcePrepare(GSource*, gint*)
(s=0x7f8294003c00, timeout=0x7f82ba03baf4) at
kernel/qeventdispatcher_glib.cpp:253
#4  0x7f839bf5295d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f839bf53230 in  () at /usr/lib64/libglib-2.0.so.0
#6  0x7f839bf5342c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f83a01f132b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f8294007970, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#8  0x7f83a019efdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f82ba03bcb0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#9  0x7f839ffd9f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#10 0x7f83a330b9c8 in  () at /usr/lib64/libQt5Qml.so.5
#11 0x7f839ffde9e9 in QThreadPrivate::start(void*) (arg=0x663ec60) at
thread/qthread_unix.cpp:341
#12 0x7f839f0d7734 in start_thread () at /lib64/libpthread.so.0
#13 0x7f839f8e0d3d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f82db43e700 (LWP 2342)):
#0  0x7f839f8d849d in poll () at /lib64/libc.so.6
#1  0x7f839bf53314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f839bf5342c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f83a01f132b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f82d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f83a019efdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f82db43dc90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7f839ffd9f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7f82dc8908f7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7f839ffde9e9 in QThreadPrivate::start(void*) (arg=0x42a9160) at
thread/qthread_unix.cpp:341
#8  0x7f839f0d7734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f839f8e0d3d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f82e677e700 (LWP 2333)):
#0  0x7f839f8d849d in poll () at /lib64/libc.so.6
#1  0x7f839bf53314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f839bf5342c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f83a01f132b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f82e8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f83a019efdb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f82e677dc70, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#5  0x7f839ffd9f1a in QThread::exec() (this=) at
thread/qthread.cpp:500
#6  0x7f83a3e92632 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7f839ffde9e9 in QThreadPrivate::start(void*) (arg=0x30320a0) at
thread/qthread_unix.cpp:341
#8  0x7f839f0d7734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f839f8e0d3d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f82efc56700 (LWP 2268)):
#0  0x7f839f0dc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f837acf1533 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7f837acf0d57 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7f839f0d7734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f839f8e0d3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f837bfff700 (LWP 2243)):
#0  0x7f839f0dc0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f83a58e293b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f83a58e2969 in  () at /usr/li

[trojita] [Bug 321387] Option for switching to next message after deleting one

2017-03-09 Thread Adam Chasen
https://bugs.kde.org/show_bug.cgi?id=321387

Adam Chasen  changed:

   What|Removed |Added

 CC||a...@chasen.name

--- Comment #1 from Adam Chasen  ---
duplicates #360091

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

[plasmashell] [Bug 377298] plasma5 crash after detaching secondary screen

2017-03-09 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=377298

Marco Martin  changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #1 from Marco Martin  ---
line numbers don't seem to correspond exactly with the 5.8.3 tag, btw, the
crash is probably at line 1792 if (m_desktopViewforId.value(id)->containment()
== containment && containment->activity() ==
m_activityController->currentActivity()) {

like screenForContainment was called before the deleted desktopview was removed
fro mthe pool

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

[plasmashell] [Bug 377426] Plasma (plasmashell), signal: Segmentation fault

2017-03-09 Thread Kai Uwe Broulik
https://bugs.kde.org/show_bug.cgi?id=377426

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #1 from Kai Uwe Broulik  ---
Interesting that similar crashes even happened in 4.x times where there was no
QML in the backtrace, cf. Bug 360366 and Bug 346725

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

[valgrind] [Bug 376956] Memcheck crashes on access(NULL, F_OK) done by Free Pascal application

2017-03-09 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=376956

Philippe Waroquiers  changed:

   What|Removed |Added

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

--- Comment #1 from Philippe Waroquiers  ---
There should be no difference of behaviour between Pascal runtime calling
access and a C application calling access.

Can you run your small C application under memheck with
   --trace-syscalls=yes
and give the relevant trace portion for the 'access' syscalls ?

Then similarly run the pascal application.
Thanks


On my side, running the below C code gives as trace:
  SYSCALL[6688,1](21) sys_access ( 0x400614(/dev/null), 0 )[sync] -->
Success(0x0) 
  SYSCALL[6688,1](21) sys_access ( 0x0((null)), 0 )==6688== Syscall param
access(pathname) points to unaddressable byte(s)
  ==6688==at 0x4F0EC57: access (syscall-template.S:81)
  ==6688==by 0x400578: main (sys_access.c:6)
  access /dev/null 0
  access NULL -1
which seems all ok to me.

#include 
#include 
main()
{
   printf("access /dev/null %d\n", access("/dev/null", 0));
   printf("access NULL %d\n", access(NULL, 0));
}

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

[dolphin] [Bug 377172] Dolphin unable to read open copy move files with some unicode characters

2017-03-09 Thread Nathan Shearer
https://bugs.kde.org/show_bug.cgi?id=377172

--- Comment #6 from Nathan Shearer  ---
I've reported this bug upstream at https://bugreports.qt.io/browse/QTBUG-59402
and referenced this bug along with bug 165044 and
https://marc.info/?l=kde-core-devel&m=122025063320264&w=2

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

[plasmashell] [Bug 377298] plasma5 crash after detaching secondary screen

2017-03-09 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=377298

--- Comment #2 from Marco Martin  ---
in the notifications applet, 
connect(KWindowSystem::self(), &KWindowSystem::workAreaChanged,
this, &NotificationsApplet::onScreenChanges);

seems to trigger onScreenChanges, then
containment()->corona()->availableScreenRect(containment()->screen()); in the
middle of the way between view deletion and removal from the list

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

[dolphin] [Bug 377411] Created Items Are Not Selected In Parent Folder

2017-03-09 Thread Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=377411

--- Comment #2 from Tsu Jan  ---
There's no registration button at
https://phabricator.kde.org/differential/diff/create/ (for now?)

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

[dolphin] [Bug 377411] Created Items Are Not Selected In Parent Folder

2017-03-09 Thread Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=377411

--- Comment #3 from Tsu Jan  ---
BTW, this is a just workaround; why that double slash, in the first place?

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

[KScreen] [Bug 377237] Screen configuration changes after reboot

2017-03-09 Thread Bartosz Krzeszewski
https://bugs.kde.org/show_bug.cgi?id=377237

--- Comment #1 from Bartosz Krzeszewski  ---
I have found solution to this problem. I had "KEkran 2" turned off in
background services. Something changed after 5.9.3 KDE update that I had to
turn on so it didn't split my screens. I don't have split screens configuration
anywhere except my second user account so I don't understand why in version
5.9.3 it is taken from that other user account even when I don't have screen
services turned on.

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

[valgrind] [Bug 377427] New: PPC64, lxv instruction failing on odd destination register

2017-03-09 Thread Carl Love
https://bugs.kde.org/show_bug.cgi?id=377427

Bug ID: 377427
   Summary: PPC64, lxv instruction failing on odd destination
register
   Product: valgrind
   Version: 3.10 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: c...@us.ibm.com
  Target Milestone: ---

The lxv instruction is failing on a Valgrind test of the register number being
odd.  This Valgrind test only applies to load/store functions that work on a
register pair.  This is not the case for the lxv instruction.

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

[ark] [Bug 377421] Ark claims to delete file from APK while it didn't

2017-03-09 Thread Ragnar Thomsen
https://bugs.kde.org/show_bug.cgi?id=377421

--- Comment #1 from Ragnar Thomsen  ---
I can't reproduce with a random apk archive from the internet. Tried with both
cli7z and clizip plugins.

Can you set:
QT_LOGGING_RULES=ark.*.debug=true
and then reproduce the problem and attach console output?

Does it happen with all apk archives? If not, can you provide a link to the
affected archive or upload it (if small)?

What is your version of Ark?

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

[digikam] [Bug 376952] AppImage Video playback issues - no sound

2017-03-09 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=376952

--- Comment #19 from Maik Qualmann  ---
AppImage works here under openSUSE with sound. OpenAl is found as audio
backend. Wildcowboy please look where in your system is the alsa.conf file is
located (/usr/share/alsa/alsa.conf).

Maik

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

[plasmashell] [Bug 377210] Drag files from Dolphin to another programs causes plasma crash under Wayland

2017-03-09 Thread Dr . Chapatin
https://bugs.kde.org/show_bug.cgi?id=377210

--- Comment #2 from Dr. Chapatin  ---
I dont know enable debug symbols on Arch. Sorry.

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

[plasmashell] [Bug 377298] plasma5 crash after detaching secondary screen

2017-03-09 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=377298

--- Comment #3 from Marco Martin  ---
possible solution: https://phabricator.kde.org/D4991

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

[plasmashell] [Bug 377301] Plasma crushing

2017-03-09 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=377301

Marco Martin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE
 CC||notm...@gmail.com

--- Comment #1 from Marco Martin  ---
can you install debug packages for plasma-workspace and plasma-framework?
the backtrace doesn't say that much at the moment

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

[frameworks-baloo] [Bug 377311] a panel crash

2017-03-09 Thread Marco Martin
https://bugs.kde.org/show_bug.cgi?id=377311

Marco Martin  changed:

   What|Removed |Added

Version|5.7.4   |5.26.0
Product|plasmashell |frameworks-baloo
  Component|general |general
   Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com
 CC||notm...@gmail.com
   Target Milestone|1.0 |---

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

[kscreenlocker] [Bug 377428] New: Indicate if Num Lock is active.

2017-03-09 Thread OlafLostViking
https://bugs.kde.org/show_bug.cgi?id=377428

Bug ID: 377428
   Summary: Indicate if Num Lock is active.
   Product: kscreenlocker
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: breeze-theme
  Assignee: plasma-b...@kde.org
  Reporter: olaf.the.lost.vik...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

(my current version is 5.9.3, which isn't selectable above)

My TKL keyboard as well as my notebook keyboard map certain "normal" keys to
number keys if Num Lock is active. Indicating this on the lockscreen just like
with Caps Lock could be helpful.

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

[digikam] [Bug 375651] Update 5.4.0 on Windows : no sound with all my videos

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375651

--- Comment #26 from caulier.gil...@gmail.com ---
I try to fix the problem using current QtAv implementation in digiKam Windows
installer. I just recompiled quickly the 32 bits bundle for testing.

Please test and give me a feedback. File is at usual place :

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

Gilles Caulier

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

[frameworks-kio] [Bug 372411] MTP flickers with android

2017-03-09 Thread Olivier Churlaud
https://bugs.kde.org/show_bug.cgi?id=372411

--- Comment #1 from Olivier Churlaud  ---
Some debug showed that the problem is due to energy: if I connect the phone to
the computer through a powered hub, it works correctly. (However it works fine
even without the hub on Ubuntu with gnome)

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

[kde-windows] [Bug 234732] okular cannot open djvu files

2017-03-09 Thread swdseth
https://bugs.kde.org/show_bug.cgi?id=234732

swds...@gmail.com  changed:

   What|Removed |Added

 CC||swds...@gmail.com

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

[dolphin] [Bug 377411] Created Items Are Not Selected In Parent Folder

2017-03-09 Thread Tsu Jan
https://bugs.kde.org/show_bug.cgi?id=377411

--- Comment #4 from Tsu Jan  ---
Added the patch at https://git.reviewboard.kde.org/r/130001/

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

[plasmashell] [Bug 377429] New: Plasman crashes when I pressed win button on keyboard

2017-03-09 Thread Sergey
https://bugs.kde.org/show_bug.cgi?id=377429

Bug ID: 377429
   Summary: Plasman crashes when I pressed win button on keyboard
   Product: plasmashell
   Version: 5.9.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: greengogo...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.3)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.13-1-lts x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I installed plasma. Booted it using sddm and pressd win button. 
The mistake no longer showed up.

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

Thread 6 (Thread 0x7fe335b9f700 (LWP 819)):
#0  0x7fe3df234e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fe3df1eec80 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fe3df1ef6cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fe3df1ef8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fe3e4cf506b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fe3e4c9e89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fe3e4ac0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fe3e87adfd6 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7fe3e4ac56d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fe3e43da7df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fe3b6d3a700 (LWP 818)):
#0  0x7fe3e399610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fe3ea4a2234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fe3ea4a2279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fe3e43da7df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fe3c15f5700 (LWP 817)):
#0  0x7fe3df234e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7fe3df1ef79a in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe3df1ef8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe3e4cf506b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe3e4c9e89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe3e4ac0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe3e7bfa025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fe3e4ac56d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe3e43da7df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fe3d0822700 (LWP 816)):
#0  0x7fe3df1ec79e in  () at /usr/lib/libglib-2.0.so.0
#1  0x7fe3df1eec2b in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fe3df1ef6cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fe3df1ef8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fe3e4cf506b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fe3e4c9e89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fe3e4ac0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fe3e7bfa025 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7fe3e4ac56d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fe3e43da7df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fe3d226a700 (LWP 775)):
#0  0x7fe3e43d148d in poll () at /usr/lib/libc.so.6
#1  0x7fe3df1ef7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe3df1ef8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe3e4cf506b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe3e4c9e89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe3e4ac0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe3e510a125 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7fe3e4ac56d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fe3e43da7df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fe3ead34800 (LWP 695)):
[KCrash Handler]
#6  0x7fe3e8858d16 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib/libQt5Quick.so.5
#7  0x7fe3e8858dea in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
at /usr/lib/libQt5Quick.so.5
#8  0x7fe3e8858dea in QQuickItemPrivate::setEffec

[kwin] [Bug 376155] "Quick tile window to the left/right" de-maximizes the window without tiling as a first action since plasma 5.9.0

2017-03-09 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376155

mowalle@gmail.com changed:

   What|Removed |Added

 CC||mowalle@gmail.com

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

[dolphin] [Bug 377430] Checksums SHA512

2017-03-09 Thread Dennis Gesker
https://bugs.kde.org/show_bug.cgi?id=377430

Dennis Gesker  changed:

   What|Removed |Added

 CC||den...@gesker.com

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

[dolphin] [Bug 377430] New: Checksums SHA512

2017-03-09 Thread Dennis Gesker
https://bugs.kde.org/show_bug.cgi?id=377430

Bug ID: 377430
   Summary: Checksums SHA512
   Product: dolphin
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: panels: information
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: den...@gesker.com
  Target Milestone: ---

Please add SHA512 to the Checksums tab of the File Properties window
BTW, thanks for Dolphin. It's awesome.

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

[frameworks-kio] [Bug 377430] Checksums SHA512

2017-03-09 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=377430

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org,
   ||kdelibs-b...@kde.org
Product|dolphin |frameworks-kio
  Component|panels: information |general
   Assignee|dolphin-bugs-n...@kde.org   |fa...@kde.org
Version|unspecified |5.31.0

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

[digikam] [Bug 376952] AppImage Video playback issues - no sound

2017-03-09 Thread wildcowboy
https://bugs.kde.org/show_bug.cgi?id=376952

--- Comment #20 from wildcowboy  ---
(In reply to Maik Qualmann from comment #19)
> AppImage works here under openSUSE with sound. OpenAl is found as audio
> backend. Wildcowboy please look where in your system is the alsa.conf file
> is located (/usr/share/alsa/alsa.conf).
> 
> Maik

/usr/share/alsa

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

[frameworks-kwallet] [Bug 377122] kwallet cannot ask for GPG password on wayland

2017-03-09 Thread Guo Yunhe
https://bugs.kde.org/show_bug.cgi?id=377122

Guo Yunhe (郭云鹤)  changed:

   What|Removed |Added

 CC||guoyunhebr...@gmail.com

--- Comment #1 from Guo Yunhe (郭云鹤)  ---
Same issue here. When enter desktop, kwalletd keeps popping up a warning saying
cannot open wallet with GPG.

openSUSE Tumbleweed 20170308 64bit
Plasma 5.9.2
Frameworks 5.31.0
Qt 5.7.1
Wayland 
Kernel 4.10.1

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

  1   2   3   4   >