[kget] [Bug 386413] New: KGet Crashes upon Start

[Jdgozilla]

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

Bug ID: 386413
   Summary: KGet Crashes upon Start
   Product: kget
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: jdogzi...@hotmail.com
  Target Milestone: ---

Application: kget (2.14.34)
KDE Platform Version: 4.14.34
Qt Version: 4.8.7
Operating System: Linux 4.13.0-16-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
- What I was doing when the application crashed: I was trying to start kget so
that I could copy a link from firefox and download it through kget.  I tried
starting it multiple times and it crashed every time.  I have recently updated
to Kubuntu 17.10

The crash can be reproduced every time.

-- Backtrace:
Application: KGet (kget), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x55ef902701a4 in  ()
#7  0x55ef90270b65 in  ()
#8  0x7f28dc991f70 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f28dc20cf8f in QHeaderView::sectionCountChanged(int, int) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x7f28dc210c36 in QHeaderView::initializeSections(int, int) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x7f28dc212c5d in QHeaderView::initializeSections() () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x7f28dc216ad2 in QHeaderView::setModel(QAbstractItemModel*) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x7f28dc249d9f in QTreeView::setModel(QAbstractItemModel*) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x55ef902703b0 in  ()
#15 0x55ef90275dc2 in  ()
#16 0x55ef902e56a1 in  ()
#17 0x55ef902e6b9d in  ()
#18 0x7f28ddc0514e in  () at /usr/lib/libkdeui.so.5
#19 0x7f28ddc051fd in  () at /usr/lib/libkdeui.so.5
#20 0x7f28ddc05451 in  () at /usr/lib/libkdeui.so.5
#21 0x7f28dcd09fc5 in  () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#22 0x7f28dcd0b5ab in  () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#23 0x7f28dcd0c23d in  () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#24 0x7f28dcd0c43b in  () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#25 0x7f28dc997d11 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x7f28dbcc87ef in QApplication::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#27 0x7f28dbcc303c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#28 0x7f28dbcc9f76 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#29 0x7f28ddbfe04a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkdeui.so.5
#30 0x7f28dc97d8ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#31 0x7f28dc981366 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#32 0x7f28dc9ae09e in  () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x7f28d7741fb7 in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x7f28d77421f0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x7f28d774227c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x7f28dc9ae20e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#37 0x7f28dbd70666 in  () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#38 0x7f28dc97c12f in
QEventLoop::processEvents(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#39 0x7f28dc97c495 in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#40 0x7f28c5323972 in  () at /usr/lib/kde4/kget_metalinkfactory.so
#41 0x7f28c530caa5 in  () at /usr/lib/kde4/kget_metalinkfactory.so
#42 0x7f28dec73140 in KGet::createTransfers(QList
const&) () at /usr/lib/libkgetcore.so.4
#43 0x7f28dec74833 in KGet::addTransfers(QList const&, QString
const&) () at /usr/lib/libkgetcore.so.4
#44 0x7f28dec8cf14 in TransferGroup::load(QDomElement const&) () at
/usr/lib/libkgetcore.so.4
#45 0x7f28dec70e99 in KGet::load(QString) () at /usr/lib/libkgetcore.so.4
#46 0x55ef902e45d2 in  ()
#47 0x55ef902e575e in  ()
#48 0x55ef902e6b9d in  ()
#49 0x7f28ddc0514e in  () at /usr/lib/libkdeui.so.5
#50 0x7f28ddc051fd in  () at /usr/lib/libkdeui.so.5
#51 0x7f28ddc05451 in  () at /usr/lib/libkdeui.so.5
#52 0x7f28dcd09fc5 in  () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#53 0x7f28dcd0b51c in  () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#54 0x7f28dcd0c23d in  () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#55 

[krita] [Bug 386412] New: menu items not showing

[Brendan]

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

Bug ID: 386412
   Summary: menu items not showing
   Product: krita
   Version: 4.0 pre-alpha
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bunf2...@apps.opensourcelaw.biz
  Target Milestone: ---

Created attachment 108660
  --> https://bugs.kde.org/attachment.cgi?id=108660=edit
Some menus from Krita showing blank entries.

When I run ./krita-4.0.0-pre-alpha-x86_64.appimage on my system (OpenSuSE leap
42.3), many menu items are blank. The whole of the scripting submenu does not
show at all. 

Blank menu items seem to be connected to their associated code when clicked. 

Sample screenshot attached.

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

[digikam] [Bug 382818] Rotating a picture ends in crash

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||5.8.0

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

[Discover] [Bug 385997] Only 2 elements on the home page (on Neon)

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
Still, Dolphin is a weird choice. 99.9% of Discover users are going to have it
already installed, no? How about Kate or some of the KDE games or educational
offerings?

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

[plasma-nm] [Bug 379756] KCM in SySe asks for Apply after opening

[Dr . Chapatin]

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

--- Comment #13 from Dr. Chapatin  ---
fixing typos...

wi-fi is selected by default only when is connected.
if a wi-fi connection is available but ethernet is active, ethernet is selected
by default instead wi-fi.
And if ethernet is selected by default, apply/discard dialog does not appear.

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

[kwin] [Bug 386411] New: Application specific task switcher not working properly

[Raul Laasner]

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

Bug ID: 386411
   Summary: Application specific task switcher not working
properly
   Product: kwin
   Version: 5.11.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: raullaas...@gmail.com
  Target Milestone: ---

Created attachment 108659
  --> https://bugs.kde.org/attachment.cgi?id=108659=edit
Screenshot of task switcher in action

Application specific task switcher, by default bound to Alt+`, does not work
for certain applications. In the attachment, I have two Dolphin windows open, I
press Alt+`, but the task switcher only register one of the Dolphins. This is
not the case with GTK applications. For instance, I can have two instances of
Firefox open, and Alt+` works fine. Also, Alt+Tab works without problems no
matter which windows are open. It is specifically Alt+` on KDE applications
that seems to have a bug.

I'm using Arch Linux and this issue emerged after an update at around Oct 11.

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

[valgrind] [Bug 386318] valgrind.org/info/tools.html is missing SGCheck

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

   Assignee|jsew...@acm.org |iv...@ivosh.net

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

[valgrind] [Bug 386318] valgrind.org/info/tools.html is missing SGCheck

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

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

--- Comment #3 from Ivo Raisr  ---
Committed in revision 531.

Thank you for the patch.

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

[okular] [Bug 382725] Okular crashes when rotating view in multi-page pdf document

[Ian Borg]

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

Ian Borg  changed:

   What|Removed |Added

 CC||bor...@gmail.com

--- Comment #9 from Ian Borg  ---
I can confirm this bug on a current OpenSUSE Leap 42.3 system. 

However, it only happens when I launch the program from the main Application
Launcher in the lower left hand corner. When I open a multi page doc and rotate
right or left the Okular window just closes, with no other dialog at all.
When I run the program under gdb, it does not crash when rotating. 
It does, however lock up after a while, usually when scrolling through pages
using the navigation bar set to thumbnails. 
gdb shows an error in the trace output close to where the program is started,
plus a segfault where it locks up. I'm including them in case they have
anything to do with the rotation issue, I have no idea:

1. error when okular is started or re-started:

(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/bin/okular 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea9c3700 (LWP 19398)]
[New Thread 0x7fffe6115700 (LWP 19399)]
Detaching after fork from child process 19402.
Detaching after fork from child process 19403.
[New Thread 0x7fffccbf2700 (LWP 19405)]
[New Thread 0x7fffc83f1700 (LWP 19406)]
[Thread 0x7fffc83f1700 (LWP 19406) exited]
[Thread 0x7fffccbf2700 (LWP 19405) exited]
QXcbConnection: XCB error: 3 (BadWindow), sequence: 4859, resource id:
36951301, major code: 40 (TranslateCoords), minor code: 0
[New Thread 0x7fffccbf2700 (LWP 19408)]
[New Thread 0x7fffc83f1700 (LWP 19409)]



2: Segfault once the pgm locks up:

...etc etc
[Thread 0x7fffb6b69700 (LWP 19640) exited]
[New Thread 0x7fffb6b69700 (LWP 19641)]
[Thread 0x7fffb6b69700 (LWP 19641) exited]
[New Thread 0x7fffb6b69700 (LWP 19642)]
[Thread 0x7fffb6b69700 (LWP 19642) exited]

Thread 72 "Queue(0x12e7190" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc83f1700 (LWP 19475)]
0x7566d8b0 in vtable for QPaintDevice () from /usr/lib64/libQt5Gui.so.5
(gdb)

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

[dolphin] [Bug 386410] New: Tokens in visual location bar should be draggable

[Nate Graham]

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

Bug ID: 386410
   Summary: Tokens in visual location bar should be draggable
   Product: dolphin
   Version: 17.08.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: bars: location
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

When Dolphin's location bar is in edit mode, there is a draggable folder icon
on the left. But there's no equivalent when the bar is in visual mode. The
tokens should themselves be draggable!

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

[Falkon] [Bug 386409] New: Add option to middle click in empty area of tab bar to reopen closed tab

[Kishore Gopalakrishnan]

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

Bug ID: 386409
   Summary: Add option to middle click in empty area of tab bar to
reopen closed tab
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: kishor...@gmail.com
  Target Milestone: ---

It would be nice to have an option in the preferences to allow to reopen the
last closed tab by middle clicking in the empty area of the tab bar. Right now,
the behaviour is to open an empty tab, which I feel is a bit redundant, since
there is already an easily accessible new tab button.

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

[kdevelop] [Bug 386407] Incomplete type marked by semantic analysis in C++ code, but includes are correct and builds

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de
  Component|Analyzer: Cppcheck  |Language Support: CPP
   ||(Clang-based)

--- Comment #1 from Sven Brauch  ---
More things look off here, apparently it doesn't find the Qt includes. Did you
open the project with the CMake project manager ...?

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

[kio-extras] [Bug 385708] kio-smb reports internal error instead of asking for login credentials with libsmbclient 4.7

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kio
   ||-extras/a36b797913a844dbb26
   ||d5dc1542b3ce304f5f445

--- Comment #12 from Nate Graham  ---
Git commit a36b797913a844dbb26d5dc1542b3ce304f5f445 by Nathaniel Graham, on
behalf of Michal Malý.
Committed on 01/11/2017 at 00:21.
Pushed by ngraham into branch 'master'.

Workaround incorrectly returned EEXIST instead of EPERM regression introduced
by libsmbclient 4.7

Summary:
There appears to be an issue with libsmbclient 4.7 that returns nonsensical
EEXIST error code when a user has not authenticated themselves to access
password-protected shares. This patch attempts to work around the issue by
treating EEXIST as another case of "invalid login credentials". The workaround
tries to detect broken versions of libsmbclient and enables itself only when
such a version is found.

See https://bugzilla.samba.org/show_bug.cgi?id=13050 for upstream bug report.

Reviewers: ngraham, davidedmundson, elvisangelaccio, #frameworks

Reviewed By: ngraham, davidedmundson

Subscribers: cfeck, rdieter, graesslin, z3ntu

Differential Revision: https://phabricator.kde.org/D8387

M  +29   -1smb/kio_smb.cpp
M  +3-0smb/kio_smb.h
M  +6-1smb/kio_smb_browse.cpp

https://commits.kde.org/kio-extras/a36b797913a844dbb26d5dc1542b3ce304f5f445

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

[digikam] [Bug 382818] Rotating a picture ends in crash

[Markus Kempf]

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

Markus Kempf  changed:

   What|Removed |Added

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

--- Comment #14 from Markus Kempf  ---
I updated to ubuntu 17.10 and installed digikam 5.6.0 - and it works.
So the problem seems solved.

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

[gwenview] [Bug 386405] Gwenview fullscreen comparison feature broken for more than 6 pictures

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 CC||rk...@lab12.net
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Henrik Fehlauer  ---
Thanks for reporting. Actually, this feature is not that "little known", so
somebody else already found some issues before you did… Can easily be found by
searching bugzilla for "gwenview more than 6", BTW.

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

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

[gwenview] [Bug 349402] Selecting more than 6 images to view causes strange behavior

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 CC||ma...@free.fr

--- Comment #2 from Henrik Fehlauer  ---
*** Bug 386405 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 386341] launching mpv causes kwin crash

[Shitikanth]

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

--- Comment #2 from Shitikanth  ---
(In reply to Martin Flöser from comment #1)
> Please provide the backtrace of the crash.

I was trying to follow the instructions to create a backtrace of the crash here

https://community.kde.org/Bugsquad/Basic_Guide_about_Crash_Reporting

and I installed the debug package for kwin but I don't see any KDE crash
handler dialog even when I reproduce the crash. 

Is there some other way I can get the backtrace?

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

[okular] [Bug 386408] New: Text color printed incorrectly

[SP]

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

Bug ID: 386408
   Summary: Text color printed incorrectly
   Product: okular
   Version: 1.0.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: scp.stj...@gmail.com
  Target Milestone: ---

I am printing to a Canon Pro 9000 MkII.  When I print with Okular v.1.0.3 the
text color is wrong - eg; blue is printed as green and black appears to be
grey.  If I use Evince the text color prints correctly - even though I am using
KDE Plasma and not Gnome.  If I use other programs such as Linux Draw - the
text colors print correctly.  

Other relevant info:
KDE Frameworks 5.38.0
Qt 5.7.1 (built against 5.7.1)
CUPS+Gutenprint v5.2.12 (color)

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

[plasmashell] [Bug 381442] SVG starter icons not displayed in application menus/launchers

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||rk...@lab12.net

--- Comment #8 from Henrik Fehlauer  ---
Can confirm. For an incomplete list of similar issues, see
https://phabricator.kde.org/D5109#162592.

@Sefa: As a workaround, edit the desktop file and remove the filename extension
from the icon's name. With this, I was able to see your example SVG in the
application dashboard.

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

[kdevelop] [Bug 386407] New: Incomplete type marked by semantic analysis in C++ code, but includes are correct and builds

[Sandro Knauß]

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

Bug ID: 386407
   Summary: Incomplete type marked by semantic analysis in C++
code, but includes are correct and builds
   Product: kdevelop
   Version: 5.1.80
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Analyzer: Cppcheck
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: skna...@kde.org
  Target Milestone: ---

Created attachment 108658
  --> https://bugs.kde.org/attachment.cgi?id=108658=edit
Sementic Analysis of messagepart.cpp

I try to scan kde/pim/messagelib for the semantic analysis - in detail
mimetreeparser/src/messagepart.cpp compiles correctly with gcc/make, but the
semantic analysis, tells me that MessagePart is incomplete in messagepart.cpp.
But messagepart.h is as first imported with the complete class. The later
import of objecttreeparser.h has correctly only a forward class declaration.

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

[valgrind] [Bug 376257] helgrind history full speed up using a cached stack

[Philippe Waroquiers]

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

--- Comment #6 from Philippe Waroquiers  ---
Ivo, thanks for looking at the patch.
I will fix this weird character (just a typo).

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

[frameworks-kio] [Bug 386406] New: Doubly encoded URL sent to proxy

[Andreas Schwab]

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

Bug ID: 386406
   Summary: Doubly encoded URL sent to proxy
   Product: frameworks-kio
   Version: 5.32.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: sch...@linux-m68k.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

When using a proxy HTTPProtocol::formatRequestUri returns a doubly encoded URL.
 This is because since Qt 5.2 (commit 1de1470189) the QUrl setters use
DecodedMode instead of TolerantMode by default, which causes all '%' to be
encoded as '%25'.  Thus a space in a URL is encoded as '%2520':
QUrl::path(QUrl::FullyEncoded) encodes ' ' into '%20' and QUrl::setPath encodes
it into '%2520'.

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

[gwenview] [Bug 386405] Gwenview fullscreen comparison feature broken for more than 6 pictures

[Mahendra Tallur]

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

Mahendra Tallur  changed:

   What|Removed |Added

 CC||ma...@free.fr

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

[gwenview] [Bug 386405] New: Gwenview fullscreen comparison feature broken for more than 6 pictures

[Mahendra Tallur]

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

Bug ID: 386405
   Summary: Gwenview fullscreen comparison feature broken for more
than 6 pictures
   Product: gwenview
   Version: 17.08.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: ma...@free.fr
  Target Milestone: ---

Hi ! 

[Intro]

Gwenview has a very nice (and little known) feature for comparing several
pictures. When in fullscreen mode, hover the mouse over the top bar, then mark
several pictures by clicking on the "+" sign. 

It enables to display several pictures at a time on the screen, in a mosaic
(then you can unselect some or put some to the trashcan).

[Bug]

When selecting MORE THAN SIX (6) pictures, the additional ones are either
hidden or more rarely displayed in fullscreen over the 6 first pictures that
are correctly displayed in a mosaic. When deselecting one, a random behaviour
occurs (the former 7th picture is displayed in fullscreen for instance, above
the mosaic, instead of becoming the 6th picture of the mosaic).

|Expected behaviour]

The 7th, 8th etc. pictures should either also be in the mosaic, or there should
be an explicit limit (impossibility to select more than 6 pictures).

[My setup]

KDE Neon, regular edition, all up to date, Gwenview 17.08.2.

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

[digikam] [Bug 386402] Not all page sizes for selected printer can be selected

[JohnR]

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

JohnR  changed:

   What|Removed |Added

 CC||raynerbee...@gmail.com

--- Comment #1 from JohnR  ---
Okay it then gets a bit weird.  I tried changing the default paper size for the
printer, it still came up with A4.  I tried printing using a different paper
size to see if it remembered what had last been printed, still A4 next time I
went to print.  Remembering an old bug I changed the photo printer to be the
default printer (I have 2 printers attached).  The default paper size had now
changed, not to the correct default paper but to the first paper type in the
list, I could then only select one of the last 6 paper types in the list and
was unable to re-select the first!  Obviously if using a printer that is not
the default printer on the system it is looking at the default printer to
determine the default paper type, quite what happens after that is anyone's
guess.

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

[Discover] [Bug 386404] Plasma-discover lists packages already intalled

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[Discover] [Bug 386404] Plasma-discover lists packages already intalled

[bugzilla_noreply]

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

emele...@gmail.com changed:

   What|Removed |Added

 CC||emele...@gmail.com

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

[Discover] [Bug 386404] New: Plasma-discover lists packages already intalled

[bugzilla_noreply]

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

Bug ID: 386404
   Summary: Plasma-discover lists packages already intalled
   Product: Discover
   Version: 5.10.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: emele...@gmail.com
  Target Milestone: ---

Plasma-discover eports 3000+packages to be updated while the system is up to
date per command-line dnf

Steps to Reproduce:
1.Open a KDE session
2.wait for discover to look for packages

Actual results:
3000+ packages to be updated (all installed packages)

Expected results:
No packages to be updated

Additional info:
I can't disable plasma-discover. This is a portable computer that runs
frequently on my phone's 4G mobile connection, and I really would like discover
to stop looking for packages. It eats up my bandwidth and data plan.

I have unchecked the apper monitor in the settings->startup and
shutdown->background services and have unsuccessfully tried to 
systemctl stop packagekit; systemctl disable packagekit


As an additional input, I tried to update the packages through discover, even
knowing that they are already at their last version. plasma-discover complains
and (a) refuses to update an already updated package, and (b) fails to remove
that package from the list, keeping it flagged for update.

So, again, please, is there a way to clean the discover database (some
equivalent to dnf clean all)? 

Thanks

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

[klickety] [Bug 386403] New: Klickety is not listed at https://www.kde.org/applications/games/

[shevegen]

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

Bug ID: 386403
   Summary: Klickety is not listed at
https://www.kde.org/applications/games/
   Product: klickety
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: shuizhuyuan...@hotmail.com
  Reporter: sheve...@gmail.com
CC: kde-games-b...@kde.org
  Target Milestone: ---

https://www.kde.org/applications/games/

Klickety is not listed there.

Could it be added please?

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

[digikam] [Bug 386402] New: Not all page sizes for selected printer can be selected

[JohnR]

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

Bug ID: 386402
   Summary: Not all page sizes for selected printer can be
selected
   Product: digikam
   Version: 5.6.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Export-PrintCreator
  Assignee: digikam-bugs-n...@kde.org
  Reporter: raynerbee...@gmail.com
  Target Milestone: ---

The problem is the same with Digikam (Image Print & Print Assistant) +
Showfoto.

Select Item
   Print Images
   Printer properties
   Page size
 Correctly picks up the page sizes for the printer, in my case HP Photosmart
D7360.

This printer has 51 different paper types!  Default is A4.
I can select any paper type that is within 10 before the default or 5 after. 
Selecting any other paper type is ignored and left as the last one selected
within the range.

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

[kwin] [Bug 376104] Quick tile window to any screen edge or corner de-maximizes the window without tiling as a first action since plasma 5.9.0

[Andrew]

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

Andrew  changed:

   What|Removed |Added

 CC||andrewnguyen...@gmail.com

--- Comment #26 from Andrew  ---
I have a similar issue with kwin 5.10.5 on Debian Testing Linux. I have quick
tile shortcuts assigned to Meta+Up/Down/Left/Right and whenever I attempt to
quick-tile a maximized window via shortcut, it de-maximizes before I am able to
quick tile it. If I activate the shortcut a second time, the window tiles as
expected.

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

[plasmashell] [Bug 384888] Mouse wheel scrolling is incredibly slow

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #3 from David Edmundson  ---
https://bugreports.qt.io/browse/QTBUG-59261

There is a workaround in one of our QQC2 implementations, but we can't use that
everywhere.

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

[plasmashell] [Bug 361311] mouse wheel only scrolls about one line, no matter how the settings in systemsettins5 are.

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
https://bugreports.qt.io/browse/QTBUG-59261

There is a workaround in one of our QQC2 implementations, but we can't use that
everywhere.

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

[amarok] [Bug 195368] Spreadsheet-like collection browser (at least for local collections)

[Alexandre Bonneau]

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

Alexandre Bonneau  changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #7 from Alexandre Bonneau  ---
Stop with this emotional rollercoaster!
Almost 10 years in waiting, please do not give us false hope ;)

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

[k3b] [Bug 386401] New: "Continue Multisession Project" don't work

[sebastian]

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

Bug ID: 386401
   Summary: "Continue Multisession Project" don't work
   Product: k3b
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: rikudou__sen...@outlook.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

I am working on "Kubuntu 17.O4LTS" With "K3B ver 17.04.0" and my problem is:

I) I burn a DVD+R with "start multisession" option

II) With my previous DVD+R
1) I choose "More actions..."
2) I choose "Continue Multisession Project"
3) The sessions list appears 
4) I choose the last session then I press "OK"

=>Result: nothing happens

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

[ktorrent] [Bug 386400] New: KTorrent crash while closing application

[steffko]

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

Bug ID: 386400
   Summary: KTorrent crash while closing application
   Product: ktorrent
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: s...@gmx.de
  Target Milestone: ---

Application: ktorrent (5.1.0)

Qt Version: 5.9.2
Frameworks Version: 5.39.0
Operating System: Linux 4.13.9-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

Closing KTorrent with Ctrl+Q results in crash. The goal is achieved, but not as
intended.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb925575900 (LWP 1672))]

Thread 6 (Thread 0x7fb8e753d700 (LWP 11004)):
#0  0x7fb91f7267e8 in __GI___libc_read (fd=fd@entry=64,
buf=buf@entry=0x7fb8e753caee, nbytes=nbytes@entry=10) at
../sysdeps/unix/sysv/linux/read.c:26
#1  0x7fb914a82751 in read (__nbytes=10, __buf=0x7fb8e753caee, __fd=64) at
/usr/include/bits/unistd.h:44
#2  pa_read (fd=64, buf=buf@entry=0x7fb8e753caee, count=count@entry=10,
type=type@entry=0x55dc9cbaafa8) at pulsecore/core-util.c:434
#3  0x7fb9174bfdde in clear_wakeup (m=) at
pulse/mainloop.c:781
#4  pa_mainloop_prepare (m=m@entry=0x55dc9cbaaed0, timeout=-1) at
pulse/mainloop.c:789
#5  0x7fb9174c0850 in pa_mainloop_iterate (m=0x55dc9cbaaed0,
block=, retval=0x0) at pulse/mainloop.c:923
#6  0x7fb9174c0910 in pa_mainloop_run (m=0x55dc9cbaaed0,
retval=retval@entry=0x0) at pulse/mainloop.c:944
#7  0x7fb9174ce779 in thread (userdata=0x55dc9cae60d0) at
pulse/thread-mainloop.c:100
#8  0x7fb914ab1438 in internal_thread_func (userdata=0x55dc9d141a20) at
pulsecore/thread-posix.c:81
#9  0x7fb91b3fe558 in start_thread (arg=0x7fb8e753d700) at
pthread_create.c:465
#10 0x7fb91f73543f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fb8e5b34700 (LWP 1695)):
#0  0x7fb91b40482d in futex_wait_cancelable (private=,
expected=0, futex_word=0x7fb9080068c4) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7fb908006870,
cond=0x7fb908006898) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7fb908006898, mutex=0x7fb908006870) at
pthread_cond_wait.c:655
#3  0x7fb920393f2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#4  0x7fb924db2b33 in net::ReverseResolverThread::run (this=0x55dc9cb81dd0)
at /usr/src/debug/libktorrent-2.1/src/net/reverseresolver.cpp:124
#5  0x7fb920392c0e in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#6  0x7fb91b3fe558 in start_thread (arg=0x7fb8e5b34700) at
pthread_create.c:465
#7  0x7fb91f73543f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fb8f093e700 (LWP 1678)):
#0  0x7fb91b40482d in futex_wait_cancelable (private=,
expected=0, futex_word=0x55dc9c888c04) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55dc9c888bb0,
cond=0x55dc9c888bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55dc9c888bd8, mutex=0x55dc9c888bb0) at
pthread_cond_wait.c:655
#3  0x7fb920393f2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#4  0x7fb92038cd8b in QSemaphore::acquire(int) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fb922737974 in QLibProxyWrapper::run() () from
/usr/lib64/libQt5Network.so.5
#6  0x7fb920392c0e in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7fb91b3fe558 in start_thread (arg=0x7fb8f093e700) at
pthread_create.c:465
#8  0x7fb91f73543f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fb906be4700 (LWP 1676)):
#0  0x7fb9190546f9 in g_mutex_lock (mutex=mutex@entry=0x7fb8f4000be0) at
gthread-posix.c:1336
#1  0x7fb91900e4f5 in g_main_context_prepare
(context=context@entry=0x7fb8f4000be0, priority=priority@entry=0x7fb906be3ba0)
at gmain.c:3384
#2  0x7fb91900f07b in g_main_context_iterate
(context=context@entry=0x7fb8f4000be0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3866
#3  0x7fb91900f25c in g_main_context_iteration (context=0x7fb8f4000be0,
may_block=1) at gmain.c:3947
#4  0x7fb9205b625b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7fb92055e73a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7fb92038e1fa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7fb920392c0e in QThreadPrivate::start(void*) () from

[plasmashell] [Bug 385814] KDE apps icons removed from the favorites list are back when plasma session is restarted

[bugzilla_noreply]

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

ale2.ran...@gmail.com changed:

   What|Removed |Added

 CC||ale2.ran...@gmail.com

--- Comment #5 from ale2.ran...@gmail.com ---
I have the same issue, Kate and Dolphin keep coming back.
I'm running Arch with Plasma 5.11.2

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

[dolphin] [Bug 386399] New: Dolphin Fechou

[Frédney Ramllo Moronari]

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

Bug ID: 386399
   Summary: Dolphin Fechou
   Product: dolphin
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: moron...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.8.0-53-generic x86_64
Distribution: Linux Mint 18.2 Sonya

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

Ao copiar arquivos de uma partição NTFS para uma unidade externa USB.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f745e2478c0 (LWP 9816))]

Thread 3 (Thread 0x7f744347f700 (LWP 9818)):
#0  __GI___clock_gettime (clock_id=1, tp=0x7f744347ea30) at
../sysdeps/unix/clock_gettime.c:134
#1  0x7f74587e36c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f745895ef09 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f745895f475 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f745896085e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f745404791d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f74540482bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f745404849c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f745896137b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f7458909ffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f74587329e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f745e332515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x7f7458737808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f7454bd46ba in start_thread (arg=0x7f744347f700) at
pthread_create.c:333
#14 0x7f745dc563dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f7449079700 (LWP 9817)):
#0  0x7f745dc4a70d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7451f9bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f7451f9d8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f744bc01d29 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f7458737808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f7454bd46ba in start_thread (arg=0x7f7449079700) at
pthread_create.c:333
#6  0x7f745dc563dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f745e2478c0 (LWP 9816)):
[KCrash Handler]
#6  0x7f7459288180 in QWidget::setParent(QWidget*, QFlags)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x7f74592887de in QWidgetPrivate::init(QWidget*,
QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7f7459443603 in QDialog::QDialog(QWidget*, QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7f745aaf3cb0 in KMessageBox::messageBox(QWidget*,
KMessageBox::DialogType, QString const&, QString const&, KGuiItem const&,
KGuiItem const&, KGuiItem const&, QString const&, QFlags)
() from /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5
#10 0x7f745c233cac in KDialogJobUiDelegate::Private::next() () from
/usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#11 0x7f7458939719 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f7459241afc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f7459247036 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f745890c2a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f745890e16a in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f7458960f53 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f7454048197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f74540483f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f745404849c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f745896135f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f7458909ffa 

[valgrind] [Bug 386397] valgrind truncates powerpc timebase to 32-bits

[Carl Love]

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

Carl Love  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[valgrind] [Bug 386397] valgrind truncates powerpc timebase to 32-bits

[Carl Love]

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

Carl Love  changed:

   What|Removed |Added

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

--- Comment #2 from Carl Love  ---
Patch committed.

commit 6a55b1e82ccda3f0d663d2cc89eb543ae2d096bf
Author: Carl Love 
Date:   Tue Oct 31 13:45:28 2017 -0500

Fix access to time base register to return 64-bits.

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

[kdenlive] [Bug 386395] kdenlive crashes on launch with missing OpenGL profile

[bugzilla_noreply]

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

krzysio.ku...@wp.pl changed:

   What|Removed |Added

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

--- Comment #1 from krzysio.ku...@wp.pl ---
I forgot I installed new graphics drivers early today, sorry for the invalid
report.

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

[valgrind] [Bug 386397] valgrind truncates powerpc timebase to 32-bits

[Carl Love]

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

--- Comment #1 from Carl Love  ---
Created attachment 108657
  --> https://bugs.kde.org/attachment.cgi?id=108657=edit
Fix for reading the time base register

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

[kdenlive] [Bug 386398] Export Project - Feature Request

[Ceda EI]

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

Ceda EI  changed:

   What|Removed |Added

 CC||ceda...@protonmail.com

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

[kdenlive] [Bug 386398] New: Export Project - Feature Request

[Ceda EI]

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

Bug ID: 386398
   Summary: Export Project - Feature Request
   Product: kdenlive
   Version: unspecified
  Platform: unspecified
OS: unspecified
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: ceda...@protonmail.com
  Target Milestone: ---

Sharing projects between PCs is often a problem. It requires manually creating
a lot of directories especially when the files are not in ~ (e.g. another
partition of HDD). To solve the problem an export feature could be implemented
in the following way.

Export copies all the videos, images and audios, the project's .kdenlive file
and an additional file that tells what was the actual path of the
video/image/audio and packs them into a zip.

Import from zip asks for a location to store the project files. After the
location is set, the zip is extracted to that location. Further based on the
additional file, Kdenlive edits the project's .kdenlive file with the new
absolute paths to the extracted video/image/audio files.

Is this implementable?

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

[digikam] [Bug 386396] Eliminate useless and misleading libpng terminal message

[Elle Stone]

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

--- Comment #1 from Elle Stone  ---
Hmm, digiKam terminal output just printed a useless libpng warning that I've
never seen before:

digikam.dimg: "/hdd/edit/edit/archiveprints/20080416 pond leaves/586-587.png" 
: PNG file identified
libpng warning: iCCP: profile 'ICC profile': 0h: PCS illuminant is not D50

The profile in question is an old Kodak Romm profile directly from the old
Kodak website. Apparently libpng is now checking profile illuminant values, and
complaining about the following discrepancy (using iccToXml to print out the
profile contents:

What is in the old Kodak profile:

  

What is in most profile's illuminant field (until iccMAX comes along and makes
it OK to use other illuminants):

  

This libpg warning is useless. Users won't know what to do with it. The profile
is fine just as it is. Yes, the D50 illuminant values are slightly off from
what is normally found in V2 and V4 ICC profiles. No, this small difference
won't make a bit of practical difference to the user, especially in a V4 CMM
such as LCMS2 provides. All this warning does is confuse the user (if they see
it) and waste processing time to detect and print.

AFAIK no other file format prints such warnings. As the warnings are about
things that make no difference whatsoever to users, it would be good to disable
the libpng warnings to keep them from being printed to the terminal, where they
might confuse users. In fact they do confuse users, as a search on the internet
will quickly show.

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

[kdenlive] [Bug 386395] kdenlive crashes on launch with missing OpenGL profile

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
Version|unspecified |git-master
Product|kde |kdenlive
   Assignee|unassigned-b...@kde.org |vpi...@kde.org
  Component|general |Installation

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

[gwenview] [Bug 386329] Some SVGs are black

[Sefa Eyeoglu]

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

Sefa Eyeoglu  changed:

   What|Removed |Added

URL||https://bugreports.qt.io/br
   ||owse/QTBUG-58326

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

[gwenview] [Bug 386329] Some SVGs are black

[Sefa Eyeoglu]

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

--- Comment #2 from Sefa Eyeoglu  ---
Okay. Nice to know. :D Wish you a nice evening

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

[valgrind] [Bug 386397] New: valgrind truncates powerpc timebase to 32-bits

[Carl Love]

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

Bug ID: 386397
   Summary: valgrind truncates powerpc timebase to 32-bits
   Product: valgrind
   Version: 3.14 SVN
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: c...@us.ibm.com
  Target Milestone: ---

---Problem Description---
Valgrind is incorrectly modeling the PowerPC timebase register as 32-bit. 
Should be 64-bit.  

---uname output---
Linux c650f07p23 4.11.0-42.el7a.ppc64le #1 SMP Mon Oct 9 12:00:22 EDT 2017
ppc64le ppc64le ppc64le GNU/Linux

Machine Type = 8335-GTC 

---Debugger---
A debugger is not configured

---Steps to Reproduce---
 Compile the following example using "gcc -o tb tb.c" and execute.  Without
Valgrind, program will display timebase as 64-bit values.  With Valgrind,
timebase will be limited to 32-bit values and the 2nd timebase printf may
appear to be lesser than the first timebase printf.

#include 
#include 

int main(int argc, char** argv)
{
uint64_t tb = __ppc_get_timebase();
printf("timebase = %lx\n", tb);
sleep(15);
tb = __ppc_get_timebase();
printf("timebase = %lx\n", tb);

return 0;
}


Contact Information = Tom Gooding / tgood...@us.ibm.com 

Userspace tool common name: valgrind 

The userspace tool has the following bit modes: 64-bit 

Userspace rpm: valgrind-3.12.0-9.el7_4.ppc64le 

Userspace tool obtained from project website:  na 

*Additional Instructions for Tom Gooding / tgood...@us.ibm.com:
-Attach ltrace and strace of userspace application.

[reply] [-]
Internal Only
Comment 1 Thomas M. Gooding 2017-10-30 22:48:33 CDT

output:

bash-4.2$ ./tb
timebase = 3be626e90262
timebase = 3be7f0ad4167




bash-4.2$ valgrind ./tb
==89099== Memcheck, a memory error detector
==89099== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==89099== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==89099== Command: ./tb
==89099== 
timebase = 8ab00ec0
timebase = 552cacc9
==89099== 
==89099== HEAP SUMMARY:
==89099== in use at exit: 0 bytes in 0 blocks
==89099==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==89099== 
==89099== All heap blocks were freed -- no leaks are possible
==89099== 
==89099== For counts of detected and suppressed errors, rerun with: -v
==89099== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)


Issue reported by  Thomas M. Gooding

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

[digikam] [Bug 386396] New: Eliminate useless and misleading libpng terminal message

[Elle Stone]

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

Bug ID: 386396
   Summary: Eliminate useless and misleading libpng terminal
message
   Product: digikam
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: FilesIO-PNG
  Assignee: digikam-bugs-n...@kde.org
  Reporter: e...@ninedegreesbelow.com
  Target Milestone: ---

Upon creating a new database, and probably every time digikam is run, the
following lines are printed to the terminal:

digikam.dimg: "/usr/share/digikam/data/sample-aix.png"  : PNG file identified
digikam.metaengine: Loading image history  ""
digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => 
QDateTime(2010-07-27 06:40:05.000 EDT Qt::TimeSpec(LocalTime))
libpng warning: iCCP: known incorrect sRGB profile

For unfathomable reasons, libpng searches for and flags certain sRGB profiles
as problematic. Once such profile is an sRGB profile that is commonly found on
Windows computers and consequently also in images downloaded from the internet.
There is absolutely nothing wrong with this profile and probably nothing with
other profiles that libpng flags. But the error messages cause consternation
for users.

This GIMP bug report has a patch that shows how to eliminate this misleading
libpng "known incorrect sRGB profile" terminal message: Deal with libpng error
gracefully when exporting an image with the color profile "sRGB IEC61966-2.1":
https://bugzilla.gnome.org/show_bug.cgi?id=765850#c3

The GIMP bug report references an imagemagick forum discussion on the topic.
Quoting from the GIMP bug report:

#Begin quote: 
The attached patch suppresses these libpng terminal warnings. It just adds this
option: png_set_option(pp, PNG_SKIP_sRGB_CHECK_PROFILE, PNG_OPTION_ON);

But maybe I should have added all of this as per the third-from-last post
#if defined(PNG_SKIP_sRGB_CHECK_PROFILE) && \
defined(PNG_SET_OPTION_SUPPORTED)
   png_set_option(png, PNG_SKIP_sRGB_CHECK_PROFILE,
   PNG_OPTION_ON);
#endif
This option to suppress the libpng known incorrect sRGB profile warning is
available starting with libpng 1.6.11, which was released back in 2014.

#End quote.

Of course the patch attached to the GIMP bug report
(https://bug765850.bugzilla-attachments.gnome.org/attachment.cgi?id=334241)
won't work with digiKam. But the relevant code changes to disable the png
warnings are hopefully easy to port over to digiKam.

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

[kde] [Bug 386395] New: kdenlive crashes on launch with missing OpenGL profile

[bugzilla_noreply]

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

Bug ID: 386395
   Summary: kdenlive crashes on launch with missing OpenGL profile
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: krzysio.ku...@wp.pl
  Target Milestone: ---

Application: kdenlive (17.11.70)
 (Compiled from sources)
Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.0-16-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
- Custom settings of the application:
Built with Release build type and "-flto". 
Built from commit 09d696b9c5bce7659ac6be5ed3f6fe359fb034f5

The crash can be reproduced every time.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcd27cac900 (LWP 17153))]

Thread 8 (Thread 0x7fccd943d700 (LWP 17161)):
#0  0x7fcd1e470072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55f724e36660) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fcd1e470072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55f724e36610, cond=0x55f724e36638) at pthread_cond_wait.c:502
#2  0x7fcd1e470072 in __pthread_cond_wait (cond=0x55f724e36638,
mutex=0x55f724e36610) at pthread_cond_wait.c:655
#3  0x7fcd206736cb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fcd2066bd6b in QSemaphore::acquire(int) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x55f7227749e4 in onThreadCreate(mlt_properties_s*, GLWidget*,
RenderThread**, int*, void* (*)(void*), void*) ()
#6  0x7fcd2695794e in mlt_events_fire (self=self@entry=0x55f725ab4220,
id=id@entry=0x7fcd269694a4 "consumer-thread-create") at mlt_events.c:216
#7  0x7fcd26961304 in mlt_thread_create (function=0x7fcd2695fee0
, self=0x55f725ab4220) at mlt_consumer.c:1783
#8  0x7fcd26961304 in consumer_read_ahead_start (self=0x55f725ab4220) at
mlt_consumer.c:1128
#9  0x7fcd26961304 in mlt_consumer_rt_frame
(self=self@entry=0x55f725ab4220) at mlt_consumer.c:1566
#10 0x7fcce4e9ac13 in consumer_thread (arg=0x55f725ab4220) at
consumer_sdl_audio.c:528
#11 0x7fcd1e4697fc in start_thread (arg=0x7fccd943d700) at
pthread_create.c:465
#12 0x7fcd27846b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7fcce0059700 (LWP 17160)):
#0  0x7fcd1e473afd in __lll_lock_wait () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7fcd1e46c21a in __GI___pthread_mutex_lock (mutex=0x7fcd19f57930) at
../nptl/pthread_mutex_lock.c:115
#2  0x7fcd19cd36fc in  () at /usr/lib/nvidia-387/libGL.so.1
#3  0x7fcd19cd8631 in  () at /usr/lib/nvidia-387/libGL.so.1
#4  0x7fcd19cd8b48 in  () at /usr/lib/nvidia-387/libGL.so.1
#5  0x7fcd15392102 in  () at
/usr/lib/nvidia-387/tls/libnvidia-tls.so.387.22
#6  0x7fcd10e2be41 in pa_read () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
#7  0x7fcd185d39fe in pa_mainloop_prepare () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#8  0x7fcd185d4470 in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#9  0x7fcd185d4530 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#10 0x7fccedd776ef in  () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0
#11 0x7fccedd3b75c in  () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0
#12 0x7fccedd91999 in  () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0
#13 0x7fcd1e4697fc in start_thread (arg=0x7fcce0059700) at
pthread_create.c:465
#14 0x7fcd27846b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fccdb7fe700 (LWP 17158)):
#0  0x7fcd18aad5b9 in g_mutex_lock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fcd18a67cf6 in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fcd18a681f0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fcd18a6827c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fcd208a849b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fcd2084de3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fcd2066d3ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fcd2231ef45 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fcd2067229d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fcd1e4697fc in start_thread (arg=0x7fccdb7fe700) at
pthread_create.c:465
#10 0x7fcd27846b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fccdbfff700 (LWP 17157)):
#0  0x7fcd1e47064b in 

[frameworks-ktexteditor] [Bug 386394] New: Crash in auto-indenter

[Matthew Woehlke]

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

Bug ID: 386394
   Summary: Crash in auto-indenter
   Product: frameworks-ktexteditor
   Version: 5.38.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: mwoehlke.fl...@gmail.com
  Target Milestone: ---

I'm experiencing a reproducible crash when trying to edit a Javascript file.
GDB and the bug reporting wizard are having problems generating a stack trace.
Valgrind reports:

==4284== Invalid read of size 8
==4284==at 0x35816C79: ???
==4284==by 0xA387305: ??? (in /usr/lib64/libQt5Qml.so.5.7.1)
==4284==by 0xA3EF7D6:
QV4::Runtime::callActivationProperty(QV4::ExecutionEngine*, int,
QV4::CallData*) (in /usr/lib64/libQt5Qml.so.5.7.1)
==4284==by 0x2F6CA9F1: ???
==4284==by 0xA387305: ??? (in /usr/lib64/libQt5Qml.so.5.7.1)
==4284==by 0xA3EF7D6:
QV4::Runtime::callActivationProperty(QV4::ExecutionEngine*, int,
QV4::CallData*) (in /usr/lib64/libQt5Qml.so.5.7.1)
==4284==by 0x2F6C9DA0: ???
==4284==by 0xA387305: ??? (in /usr/lib64/libQt5Qml.so.5.7.1)
==4284==by 0xA2ED235: QJSValue::call(QList const&) (in
/usr/lib64/libQt5Qml.so.5.7.1)
==4284==by 0x4F67E2D:
KateIndentScript::indent(KTextEditor::ViewPrivate*, KTextEditor::Cursor const&,
QChar, int) (kateindentscript.cpp:75)
==4284==by 0x50258BD:
KateAutoIndent::scriptIndent(KTextEditor::ViewPrivate*, KTextEditor::Cursor
const&, QChar) (kateautoindent.cpp:278)
==4284==by 0x5026935:
KateAutoIndent::userTypedChar(KTextEditor::ViewPrivate*, KTextEditor::Cursor
const&, QChar) (kateautoindent.cpp:453)
==4284==  Address 0xb5bd04d8 is not stack'd, malloc'd or (recently) free'd

To reproduce:

- Open
https://raw.githubusercontent.com/Kitware/vaui/84ba21ecce5fb64388b1510b50c8cbb8c9bda3e1/web_external/Viewer/ImageViewerWidgetWrapper/VauiGeoJSImageViewer.js
- Move the caret to the end of line 36 (`var pendingNext = false;`)
- Press enter

Curiously, if I paste the file contents into an empty document and set HL to
'javascript', no crash...

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

[gwenview] [Bug 386329] Some SVGs are black

[Henrik Fehlauer]

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

Henrik Fehlauer  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||rk...@lab12.net

--- Comment #1 from Henrik Fehlauer  ---
Hi Sefa, thanks for reporting and your enthusiasm for KDE's software. I can
confirm your observation. Unfortunately, "svgviewer" from the examples
contained in Qt's SVG module shows the same behaviour. As we just use Qt for
rendering SVGs, this means we cannot do anything for you from Gwenview's side
(except someone would provide a patch to change our SVG renderer to something
better).

Digging a bit deeper, the issue boils down to how the opacity is specified in
the SVG. In http://doc.qt.io/qt-5/svgrendering.html it is mentioned that only
SVG Tiny 1.2 is supported by Qt, which your SVG is not. However, there is a
trick to get SVGs not conforming to this spec to work: You can add
type="text/css" to the style element of your SVG, then Gwenview is able to
render it fine for me.

This problem has already been reported in
https://bugreports.qt.io/browse/QTBUG-58326, which is still unresolved. I added
a comment over there, but to get things going an actual patch against the Qt
SVG module would be needed.

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

[plasma-nm] [Bug 386342] Hidden wi-fi network is duplicated in kcm

[Dr . Chapatin]

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

--- Comment #9 from Dr. Chapatin  ---
Created attachment 108656
  --> https://bugs.kde.org/attachment.cgi?id=108656=edit
plasma-nm debug

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

[plasma-nm] [Bug 386342] Hidden wi-fi network is duplicated in kcm

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 Attachment #108644|0   |1
is obsolete||
 Attachment #108645|0   |1
is obsolete||

--- Comment #8 from Dr. Chapatin  ---
Created attachment 108655
  --> https://bugs.kde.org/attachment.cgi?id=108655=edit
d-bus monitor

New steps to reproduce

open "connections" in system settings
create a new wi-fi network,
enter a connection name,
in "wi-fi" tab check "hidden network" and enter your network SSiD,
click "wi-fi security" tab, select "ask for this password every time",
click "save" button
click on wi-fi icon in system tray and active your just created wi-fi
connection
when the connection is stabilished, a second wi-fi connection appears in menu
of the wi-fi icon from system tray:
first connection name is the name that you entered in "connection name" field
second connection name is your hidden wi-fi network SSiD

tested on neon user edition, plasma 5.11.2
hidden AP name: 56Kbps
connection name: provider7

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

[dolphin] [Bug 386379] Scrolling is faster comparing with other softwares

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
BTW, I really appreciate your bugs. You find a lot of annoying thousand-cuts
issues that are easy to fix. :) Keep 'em coming!

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

[dolphin] [Bug 386379] Scrolling is faster comparing with other softwares

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #3 from Nate Graham  ---
Hmm, in that case maybe Dolphin is to blame here. I'll investigate. Thanks for
following up.

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

[dolphin] [Bug 386379] Scrolling is faster comparing with other softwares

[Dr . Chapatin]

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

--- Comment #2 from Dr. Chapatin  ---
Scrolling looks the same in okular, kate and gwenview, dolphin is faster.
What do you think Nate?

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

[valgrind] [Bug 320546] valgrind exits with "Assertion 'in_rx' failed" for /system/lib/libva-android.so on Android 4.0.4

[Petar Jovanovic]

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

Petar Jovanovic  changed:

   What|Removed |Added

 CC||mips3...@gmail.com

--- Comment #2 from Petar Jovanovic  ---
There is a patch [1] on the master branch that fixes an issue that looks
similar to this one.
Can you try to build Valgrind ToT and test it with your application?

[1]
https://sourceware.org/git/?p=valgrind.git;a=commit;h=0eea388934a228231843d8c13cfd99bb170074f1

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

[kwin] [Bug 386393] No virtual keyboard when used without Xwayland

[Bhushan Shah]

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

Bhushan Shah  changed:

   What|Removed |Added

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

--- Comment #1 from Bhushan Shah  ---
Uhhmm PEBKAC... Somehow I managed to disable keyboard through SNI.

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

[systemsettings] [Bug 386392] Global Shortcuts Crash

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

  Component|general |kcm_keys
Product|kde |systemsettings
   Assignee|unassigned-b...@kde.org |k...@michael-jansen.biz
 CC||pointedst...@zoho.com
Version|unspecified |5.11.2

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

[akregator] [Bug 386348] XML format not recognized

[Kim Lilliestierna]

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

--- Comment #2 from Kim Lilliestierna  ---
Created attachment 108654
  --> https://bugs.kde.org/attachment.cgi?id=108654=edit
dent xml rss

aquired by curl http://www.webtoons.com/en/sf/dents/rss?title_no=671 > dents

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

[kwin] [Bug 386393] New: No virtual keyboard when used without Xwayland

[Bhushan Shah]

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

Bug ID: 386393
   Summary: No virtual keyboard when used without Xwayland
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: virtual-keyboard
  Assignee: kwin-bugs-n...@kde.org
  Reporter: bhus...@gmail.com
  Target Milestone: ---

So I started kwin without Xwayland on phone, and I can no longer start
Qtvirtualkeyboard.

Starting kwin with Xwayland, virtual keyboard works again

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

[dolphin] [Bug 386379] Scrolling is faster comparing with other softwares

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Nate Graham  ---
All of these programs use different scroll methods, which explains the
discrepancy.

Dolphin uses the KDE/Qt standard speed, which should be tweakable in the Input
Devices System Settings module.

Firefox has its own scroll speed which is controlled by a hidden setting in
about:config:  "mousewheel.min_line_scroll_amount"

LibreOffice likewise uses its own internal scroll speed setting and I don't
think you can change it. I think there are bugs about this on their own bug
tracker.

If Okular's speed is different, I think that may be worth a bug, asking it to
respect the systemwide default setting like Dolphin does.

Please file bugs against those other products.

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

[kmail2] [Bug 386238] Kmail crashes on start

[Ferry]

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

--- Comment #2 from Ferry  ---
OK I managed to work around this in the following way:
- I went into ~ferry/.local/share/kmail2/autosave
- removed the file there

Started kmail, problem gone.

May I suggest that if kmail is repeatedly trying to recover an open e-mail that
it should give up on that and clear the autosave folder?

Unfortunately I really deleted the file, so we can't use it here now to
reproduce the problem.

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

[kdenlive] [Bug 375206] Kdenlive-16.12.1-2-x86_64.AppImage aborts with 'failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id"'

[Lutz Vieweg]

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

--- Comment #3 from Lutz Vieweg  ---
(In reply to Vincent PINON from comment #2)
> Is the bug fixed with the recent 17.08 images?

No, the symptom still occurs with kdenlive-17.08.2-x86_64.AppImage - and the
same work-around I mentioned above (which is only possible to create as "root")
is still possible.

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

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

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #7 from Allen Winter  ---
this bug has been fixed. but I don't think the fixed version will be released
until 2018.  Laurent do you know which version will have the fix?

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

[kmail2] [Bug 386238] Kmail crashes on start

[Ferry]

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

Ferry  changed:

   What|Removed |Added

 CC||ft...@telfort.nl

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

[kmail2] [Bug 386238] Kmail crashes on start

[Ferry]

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

--- Comment #1 from Ferry  ---
I just upgraded to kubuntu backport ppa:
~$ kmail -v
kmail2 5.5.3

Still kontact (and kmail) crash on each start. I think it tries to recover an
e-mail and then crashes again and again. How do I stop this?

Starting from command line now shows:

~$ kontact
[3491:3510:1031/170506.962118:ERROR:nss_util.cc(808)] After loading Root Certs,
loaded==false: NSS error code: -8018
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
sonnet.plugins.hspell: HSpellDict::HSpellDict: Init failed
sonnet.core: Missing trigrams for languages: QSet("es_VE", "es_AR", "fr_LU",
"es_BO", "es_PY", "en_AU", "es_CL", "es_NI", "fr_MC", "es_PE", "nl_BE",
"es_CO", "de_BE", "fr_CA", "fr_CH", "es_CU", "de_CH", "es_CR", "es_PR",
"fr_BE", "en_CA", "es_UY", "es_PA", "es_EC", "de_AT", "sv_FI", "es_GT",
"de_LU", "es_DO", "es_HN", "es_MX", "es_SV", "en_GB")
org.kde.pim.webengineviewer:  It's not necessary to check database now
KXMLGUI file found at deprecated location
("/home/ferry/.local/share/kontact/kontactsummary_part.rc") -- please use
${KXMLGUI_INSTALL_DIR} to install this file instead.
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.webengineviewer: Database already initialized. It's a bug in code
if you call it twice.
"Tag 'a' is not defined in message {<__kuit_internal_top__>Voor meer informatie
over het gebruikt van Akregator, kij...}."
"Tag 'a' is not defined in message {<__kuit_internal_top__>Voor meer informatie
over het gebruikt van Akregator, kij...}."
*** KMail got signal 11 (Exiting)
*** Dead letters dumped.
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
[1:1:0100/00.525574:ERROR:broker_posix.cc(41)] Invalid node channel message
QSocketNotifier: Invalid socket 71 and type 'Read', disabling...
QSocketNotifier: Invalid socket 89 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kontact path = /usr/bin pid = 3491
KCrash: Arguments: /usr/bin/kontact 
Segmentatiefout (geheugendump gemaakt)

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

[kde] [Bug 386392] New: Global Shortcuts Crash

[bugzilla_noreply]

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

Bug ID: 386392
   Summary: Global Shortcuts Crash
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: m46sr...@posteo.de
  Target Milestone: ---

Application: kcmshell5 (5.11.2)

Qt Version: 5.9.2
Frameworks Version: 5.39.0
Operating System: Linux 4.13.10-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I edited the custom shortcuts for tiling the current window.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5e01c37800 (LWP 1457))]

Thread 4 (Thread 0x7f5db9699700 (LWP 1564)):
#0  0x7f5e015b4c49 in syscall () at /usr/lib/libc.so.6
#1  0x7f5df9268f2f in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0
#2  0x7f5df925b393 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f5df925b55e in g_async_queue_timeout_pop () at
/usr/lib/libglib-2.0.so.0
#4  0x7f5df9230041 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f5df92351eb in  () at /usr/lib/libglib-2.0.so.0
#6  0x7f5dfb75908a in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f5e015ba24f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f5de59ba700 (LWP 1459)):
#0  0x7f5e015afd4b in poll () at /usr/lib/libc.so.6
#1  0x7f5df9240ed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f5df9240fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5dfea17cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5dfe9bb48b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5dfe7d427e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5dfee33376 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f5dfe7d8fcb in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5dfb75908a in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f5e015ba24f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f5deeb68700 (LWP 1458)):
#0  0x7f5e015afd4b in poll () at /usr/lib/libc.so.6
#1  0x7f5dfbb7f8e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f5dfbb81679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f5df170385a in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f5dfe7d8fcb in  () at /usr/lib/libQt5Core.so.5
#5  0x7f5dfb75908a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f5e015ba24f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f5e01c37800 (LWP 1457)):
[KCrash Handler]
#5  0x7f5dffaa0ed7 in QLabel::text() const () at
/usr/lib/libQt5Widgets.so.5
#6  0x7f5dfdf00797 in  () at /usr/lib/libKF5XmlGui.so.5
#7  0x7f5dfe9ecd3f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#8  0x7f5df8855505 in KGlobalAccel::globalShortcutChanged(QAction*,
QKeySequence const&) () at /usr/lib/libKF5GlobalAccel.so.5
#9  0x7f5df8858694 in  () at /usr/lib/libKF5GlobalAccel.so.5
#10 0x7f5dfe9ecc16 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#11 0x7f5df8864557 in  () at /usr/lib/libKF5GlobalAccel.so.5
#12 0x7f5df88665c6 in  () at /usr/lib/libKF5GlobalAccel.so.5
#13 0x7f5dfee3eabd in  () at /usr/lib/libQt5DBus.so.5
#14 0x7f5dfe9ed662 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#15 0x7f5dff964f2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#16 0x7f5dff96ca06 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#17 0x7f5dfe9bd060 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#18 0x7f5dfe9bf8b6 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#19 0x7f5dfea186e4 in  () at /usr/lib/libQt5Core.so.5
#20 0x7f5df923f270 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#21 0x7f5df9240f69 in  () at /usr/lib/libglib-2.0.so.0
#22 0x7f5df9240fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#23 0x7f5dfea17cd1 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#24 0x7f5dfe9bb48b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#25 0x7f5dfe9c44d8 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#26 0x7f5e018834a6 in kdemain () at /usr/lib/libkdeinit5_kcmshell5.so
#27 0x7f5e014e4f6a in __libc_start_main () at /usr/lib/libc.so.6
#28 0x5634d426877a in _start ()

Reported using DrKonqi

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

[kate] [Bug 386391] New: Kate: code highlighting java: Binary Literals not supported

[bugzilla_noreply]

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

Bug ID: 386391
   Summary: Kate: code highlighting java: Binary Literals not
supported
   Product: kate
   Version: 16.04
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: h...@gmx.at
  Target Milestone: ---

Java has Binary Literals
(https://docs.oracle.com/javase/8/docs/technotes/guides/language/binary-literals.html),
but the highlighting doesn't work)

Example:
int x = 0b011;

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

[Baloo] [Bug 365122] repeatable crash of baloo_file because of corrupted Database

[Malick]

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

--- Comment #3 from Malick  ---
Created attachment 108653
  --> https://bugs.kde.org/attachment.cgi?id=108653=edit
New crash information added by DrKonqi

baloo_file (0.1) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:

I launch Bleachbit app to clean my system. After that, I restarted my laptop.

-- Backtrace (Reduced):
#5  std::vector
>::operator= (this=this@entry=0x13f4b00, __x=) at /usr/include/c++/4.8/bits/vector.tcc:161
#6  0x7f1257c29c7c in Xapian::Database::Database (this=0x13f4af8,
other=...) at ../api/omdatabase.cc:82
#7  0x7f1257c33dfa in Xapian::Enquire::Internal::Internal (this=0x13f4af0,
db_=..., errorhandler_=0x0) at ../api/omenquire.cc:621
#8  0x7f1257c33fae in Xapian::Enquire::Enquire (this=0x7ffd84113e80,
databases=..., errorhandler=0x0) at ../api/omenquire.cc:874
#9  0x004174d3 in Baloo::FileIndexingQueue::fillQueue (this=0x13ee7c0)
at ../../../src/file/fileindexingqueue.cpp:56

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

[Baloo] [Bug 365122] repeatable crash of baloo_file because of corrupted Database

[Malick]

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

Malick  changed:

   What|Removed |Added

 CC||sow.mal...@gmail.com

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

[amarok] [Bug 195368] Spreadsheet-like collection browser (at least for local collections)

[Myriam Schweingruber]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Status|CONFIRMED   |UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #6 from Myriam Schweingruber  ---
We do not confirm wishlist items.

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

[krita] [Bug 386389] some blending modes does no work while editing brushes

[Boudewijn Rempt]

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

--- Comment #3 from Boudewijn Rempt  ---
It's actually possible to erase the white pixels in the scratchpad.

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

[kmail2] [Bug 354822] Opening link in mail directs user to received location header instead of link

[Martin van Es]

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

--- Comment #4 from Martin van Es  ---
Still bug is still present in plasma 5.11.2

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

[kwin] [Bug 384402] KWin compositing performance anomaly

[Steffen Coenen]

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

Steffen Coenen  changed:

   What|Removed |Added

 CC||tarding...@googlemail.com

--- Comment #9 from Steffen Coenen  ---
This sounds like it may be a duplicate of this bug:
https://bugs.kde.org/show_bug.cgi?id=344433

Maybe try out if setting KWIN_TRIPLE_BUFFER=0 helps.

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

[systemsettings] [Bug 347870] Default Applications > Web Browser "in an application based on the contents of the URL" is confusing and undocumented

[Martin van Es]

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

--- Comment #3 from Martin van Es  ---
I just hit my head again against the problem reported in comment
https://bugs.kde.org/show_bug.cgi?id=347870#c2
Please remove content inspection option from default browser, it's broken by
design!

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

[krita] [Bug 386389] some blending modes does no work while editing brushes

[wolthera]

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

--- Comment #2 from wolthera  ---
yes, this is because the scratchpad is not transparent but filled with white
pixels. This will require a rethinking of how the scratchpad works.

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

[krita] [Bug 386389] some blending modes does no work while editing brushes

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
That's because those blending modes need something to blend with, so you'd need
to create a background that alles the blending mode to act.

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

[kontact] [Bug 386390] New: Crashes every few minutes at many clicks

[bugzilla_noreply]

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

Bug ID: 386390
   Summary: Crashes every few minutes at many clicks
   Product: kontact
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: pi...@gmx.de
  Target Milestone: ---

Since Kubuntu 17.10 my Kontact/Kmail crashes a LOT of times. When using the
menu bar or clicking an an email or clicking in the tree of mails. I would say
I have seldomly 10 clicks in a row without crashing.

I wanted to install backtrace packages but they are not available. Can you give
some advice how to help out with deeper debug symbols to find this really
anoying bug?

Thanks
Andreas

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

[krita] [Bug 386389] New: some blending modes does no work while editing brushes

[bugzilla_noreply]

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

Bug ID: 386389
   Summary: some blending modes does no work while editing brushes
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: gordie.lachance+...@gmail.com
  Target Milestone: ---

I can't test my brush when editing it and switching to some modes, including
the "greater" blending mode.

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

[kio-extras] [Bug 385708] kio-smb reports internal error instead of asking for login credentials with libsmbclient 4.7

[Bruno Friedmann]

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

--- Comment #11 from Bruno Friedmann  ---
(In reply to Bruno Friedmann from comment #10)
> Also seen on openSUSE Tumbleweed as samba 4.7.0 has been incorporated

Reported on openSUSE as https://bugzilla.opensuse.org/show_bug.cgi?id=1065868
Hope some samba people from there can help

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

[kio-extras] [Bug 385708] kio-smb reports internal error instead of asking for login credentials with libsmbclient 4.7

[Bruno Friedmann]

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

Bruno Friedmann  changed:

   What|Removed |Added

 CC||br...@ioda-net.ch

--- Comment #10 from Bruno Friedmann  ---
Also seen on openSUSE Tumbleweed as samba 4.7.0 has been incorporated

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

[kontact] [Bug 386386] Summary locks up kontact until its done it job

[BingMyBong]

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

--- Comment #2 from BingMyBong  ---
Seems like akonadi_ical_resource running between 40-50% all the time its
"locked up" - its also reporting it taking 1.5GB memory usage

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

[kdevelop] [Bug 386388] kdevelop crash when opening a project containing javascript files

[Urmet Saar]

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

--- Comment #1 from Urmet Saar  ---
Created attachment 108652
  --> https://bugs.kde.org/attachment.cgi?id=108652=edit
example crashing project

Attached a project tarball. Containing only one 9-line javascript file. It
alone has been able to crash kdevelop without failure.

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

[kdevelop] [Bug 386388] New: kdevelop crash when opening a project containing javascript files

[Urmet Saar]

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

Bug ID: 386388
   Summary: kdevelop crash when opening a project containing
javascript files
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: urmet.s...@gmail.com
  Target Milestone: ---

Created attachment 108651
  --> https://bugs.kde.org/attachment.cgi?id=108651=edit
stack trace

After commit 9ec89cdc6a1f6ef2548d318f97a908d17a2440b0 kdevelop crashes after
opening a project containing some javascript files.

Reverting that specific commit gets rid of the crashes and seems to have no bad
side effects.

Attached is a stack trace.

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

[ktorrent] [Bug 386387] New: KTorrent crashes when closed

[Max Sydorenko]

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

Bug ID: 386387
   Summary: KTorrent crashes when closed
   Product: ktorrent
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: maxim.starga...@gmail.com
  Target Milestone: ---

Application: ktorrent (5.1.0)

Qt Version: 5.9.2
Frameworks Version: 5.39.0
Operating System: Linux 4.13.11-pf x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I closed application with Ctrl+Q command
It crashed. Nothing else abnormal was observed prior to crash.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f07491110c0 (LWP 1002))]

Thread 3 (Thread 0x7f072a147700 (LWP 1029)):
#0  0x7f073c44a664 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f073c422ec8 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f073c422fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f07440f8cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f074409c48b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f0743eb527e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f0743eb9fcb in  () at /usr/lib/libQt5Core.so.5
#7  0x7f073eaba08a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f074326324f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f072bb59700 (LWP 1008)):
#0  0x7f07432703df in __libc_enable_asynccancel () at /usr/lib/libc.so.6
#1  0x7f0743258d36 in poll () at /usr/lib/libc.so.6
#2  0x7f073c422ed3 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f073c422fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f07440f8cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f074409c48b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f0743eb527e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f07454d3376 in  () at /usr/lib/libQt5DBus.so.5
#8  0x7f0743eb9fcb in  () at /usr/lib/libQt5Core.so.5
#9  0x7f073eaba08a in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f074326324f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f07491110c0 (LWP 1002)):
[KCrash Handler]
#5  0x7f07440e008d in QVariant::QVariant(QString const&) () at
/usr/lib/libQt5Core.so.5
#6  0x56450a9fc10d in  ()
#7  0x56450a9fea7d in  ()
#8  0x7f0745037381 in
QStyledItemDelegate::initStyleOption(QStyleOptionViewItem*, QModelIndex const&)
const () at /usr/lib/libQt5Widgets.so.5
#9  0x7f0745036857 in QStyledItemDelegate::sizeHint(QStyleOptionViewItem
const&, QModelIndex const&) const () at /usr/lib/libQt5Widgets.so.5
#10 0x56450aa05145 in  ()
#11 0x7f074507b8f6 in QTreeView::indexRowSizeHint(QModelIndex const&) const
() at /usr/lib/libQt5Widgets.so.5
#12 0x7f074507c28f in QTreeViewPrivate::layout(int, bool, bool) () at
/usr/lib/libQt5Widgets.so.5
#13 0x7f07450844e0 in QTreeView::doItemsLayout() () at
/usr/lib/libQt5Widgets.so.5
#14 0x7f074507eb06 in QTreeViewPrivate::updateScrollBars() () at
/usr/lib/libQt5Widgets.so.5
#15 0x7f074508609e in QTreeView::updateGeometries() () at
/usr/lib/libQt5Widgets.so.5
#16 0x7f0745013ff9 in  () at /usr/lib/libQt5Widgets.so.5
#17 0x7f07440cdc16 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#18 0x7f074502a17b in QHeaderView::viewportEvent(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#19 0x7f074409dd2c in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/usr/lib/libQt5Core.so.5
#20 0x7f0744dbbf08 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x7f0744dc3a06 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#22 0x7f074409e060 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#23 0x7f0744df6ace in QWidgetPrivate::hideChildren(bool) () at
/usr/lib/libQt5Widgets.so.5
#24 0x7f0744df6ab4 in QWidgetPrivate::hideChildren(bool) () at
/usr/lib/libQt5Widgets.so.5
#25 0x7f0744df6ab4 in QWidgetPrivate::hideChildren(bool) () at
/usr/lib/libQt5Widgets.so.5
#26 0x7f0744df6ab4 in QWidgetPrivate::hideChildren(bool) () at
/usr/lib/libQt5Widgets.so.5
#27 0x7f0744df6ab4 in QWidgetPrivate::hideChildren(bool) () at
/usr/lib/libQt5Widgets.so.5
#28 0x7f0744df6ab4 in QWidgetPrivate::hideChildren(bool) () at
/usr/lib/libQt5Widgets.so.5
#29 0x7f0744df6ab4 in QWidgetPrivate::hideChildren(bool) () at
/usr/lib/libQt5Widgets.so.5
#30 0x7f0744df6ab4 

[LabPlot2] [Bug 379104] creating a plot or a fit must be improved

[bugzilla_noreply]

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

--- Comment #6 from uwesto...@web.de ---
> The improvements are part of the next release, 2.5

These are great news! I will test the new features thoroughly as soon as I can
get a Windows build of 2.5. nevertheless I think it would be better to leave
bugs open that are not fixed in the current release. If for example a user of
LP 2.4 encounters the same or a similar problem he will find the existing open
bug and won't open a new one.

For LyX (www.lyx.org/trac) we do this and mark bugs fixed for the next release
as "fixed in branch". I guess the KDE bugtracker allows such a keyword or tag
as well. Once LP 2.5 is available you can easily close al tagged bugs as fixed.

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

[kwin] [Bug 386370] kwin randomly crashes when switching desktops

[Jesse]

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

--- Comment #2 from Jesse  ---
How can I do that in this case? When it crashes, it doesn't popup that usual
error dialog.

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

[kontact] [Bug 386386] Summary locks up kontact until its done it job

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #1 from Allen Winter  ---
I can see how my fix for bug 384284 could possibly be causing this.

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

[kate] [Bug 377538] Create a new file from selection

[Christoph Cullmann]

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

--- Comment #6 from Christoph Cullmann  ---
Sorry, the link to the ticket was just ment for Lex ;=)
Just ignore that.

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

[plasmashell] [Bug 386381] Plasma utilizing 100% CPU (1 core) after upgrade to 17.10

[Petr Nehez]

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

Petr Nehez  changed:

   What|Removed |Added

Summary|Plasma frozen after upgrade |Plasma utilizing 100% CPU
   |to 17.10|(1 core) after upgrade to
   ||17.10

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

[kontact] [Bug 386386] New: Summary locks up kontact until its done it job

[BingMyBong]

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

Bug ID: 386386
   Summary: Summary locks up kontact until its done it job
   Product: kontact
   Version: 5.6.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: summary
  Assignee: kdepim-b...@kde.org
  Reporter: bingmyb...@btinternet.com
  Target Milestone: ---

Since the fix to bug 384284, if you open kontact on the Summary, you cannot go
to any other task like mail or calendar until its displayed the summary
details.  The summary details used to be displayed virtually immediately on
opening so you could jump to another task immediately. Its taking as long as it
did when it was displaying a whole years worth of upcoming dates. (see bug
384284)

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

[plasmashell] [Bug 386381] Plasma frozen after upgrade to 17.10

[Petr Nehez]

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

--- Comment #4 from Petr Nehez  ---
OK, I understand it is not specifically Plasma's code, but would it be possible
to disable all plasmoids while doing an upgrade?

This would avoid such problems.
For less experienced users this would mean full reinstall only...

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

[plasmashell] [Bug 386381] Plasma frozen after upgrade to 17.10

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from David Edmundson  ---
>When I deleted the folder 
>"/home/petr/.local/share/plasma/plasmoids/com.github.zren.batterytime/" and 
>restarted system, plasmashell started correctly.

Sounds like they're stuck in a layout loop. 
But not Plasma code, so I can't do anything.

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

[xdg-desktop-portal-kde] [Bug 386385] New: ctrl-q on client doesn't close portal dialogs

[Harald Sitter]

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

Bug ID: 386385
   Summary: ctrl-q on client doesn't close portal dialogs
   Product: xdg-desktop-portal-kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: sit...@kde.org
  Target Milestone: ---

- start a portal'd kate
- ctrl-o
- then ctrl-q the kate (leave the dialog open)

result: dialog stays open even though the kate instances that started it is now
gone

expected: dialog disappears when kate gets closed

possible solution: since a client requesting a portal method must have some
dbus address, the portal can listen for the address getting unregistered on the
bus at which point the portal should also discard all pending dialogs to do
with the client

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

[plasmashell] [Bug 386381] Plasma frozen after upgrade to 17.10

[Petr Nehez]

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

Petr Nehez  changed:

   What|Removed |Added

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

--- Comment #2 from Petr Nehez  ---
OK, I have written it in a bad way.
Plasmashell was utilizing 1 core on 100% and doing a lot of IO writes.
That line was the only thing I have found out by executing 
* "lsof | grep plasmashe" 
* "sudo strace -p  -v"
and checking what was being written.

And that line was the only thing that was being written.

When I deleted the folder
"/home/petr/.local/share/plasma/plasmoids/com.github.zren.batterytime/" and
restarted system, plasmashell started correctly.

I deleted the folder after logging in and pressing of Ctrl+Alt+F1 and logging
in again in terminal.

Now I have no idea how you want from me to debug it after fixing of the issue.
My computers was not usable after upgrade until I deleted that folder.

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

[plasma-nm] [Bug 386360] "ok/close" buttons in dialog to confirm connection deletion need to use more appropriate terms

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/pla
   ||sma-nm/e7b1b68eacc453d89c5d
   ||31a60a7627c21effeabc
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Nate Graham  ---
Git commit e7b1b68eacc453d89c5d31a60a7627c21effeabc by Nathaniel Graham.
Committed on 31/10/2017 at 12:51.
Pushed by ngraham into branch 'master'.

Use standard Ok/Cancel buttons for the connection removal dialog

Summary:

Change the Close button to a Cancel button in the KCM's connection removal
dialog.

Test Plan:
Tested in KDE Neon. The dialog now has Ok/Cancel buttons:

{F5459178}

Reviewers: #plasma, jgrulich

Reviewed By: jgrulich

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D8562

M  +1-1kcm/qml/main.qml

https://commits.kde.org/plasma-nm/e7b1b68eacc453d89c5d31a60a7627c21effeabc

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

[frameworks-baloo] [Bug 386261] Show "Downloaded From" by default in Dolphin

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/bal
   ||oo-widgets/16e77619ee73a612
   ||9f732ae2e8ab32baaa089b29
 Resolution|--- |FIXED

--- Comment #2 from Nate Graham  ---
Git commit 16e77619ee73a6129f732ae2e8ab32baaa089b29 by Nathaniel Graham.
Committed on 31/10/2017 at 12:49.
Pushed by ngraham into branch 'master'.

Display "Downloaded From" by default, if file supports it

Summary:

By default, show "Downloaded From" information from files' extended attributes,
if present. No change for files without the xattr.

Test Plan:
Tested in KDE Neon. Blew away dolphinrc and baloofileinformationrc, deployed
the baloo-widgets change, rebuilt dolphin, downloaded a file using Chromium
(which writes the user.xdg.origin.url xattr), opened Dolphin, navigated to the
file, selected it, and turned on the Information panel. Downloaded From was
visible. It was (correctly) not visible for any other file that lacked the
user.xdg.origin.url xattr.

{F5453057}

Reviewers: #dolphin, #frameworks, broulik, dfaure, markg, vhanda

Reviewed By: markg, vhanda

Subscribers: vhanda

Tags: #dolphin

Differential Revision: https://phabricator.kde.org/D8527

M  +1-2src/metadatafilter.cpp

https://commits.kde.org/baloo-widgets/16e77619ee73a6129f732ae2e8ab32baaa089b29

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