date:20170723

[digikam] [Bug 381222] Digikam crash on fuzzy search

2017-07-23 Thread bugzilla_noreply

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

--- Comment #3 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 379959] Could not start database initializer

2017-07-23 Thread bugzilla_noreply

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

--- Comment #3 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 379984] ASSERT failure in Q_GLOBAL_STATIC: "The global static was used after being destroyed", file /usr/include/qt5/QtCore/qglobalstatic.h, line 138

2017-07-23 Thread bugzilla_noreply

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

--- Comment #2 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 376256] Crach when trying to go to "Metadata" tab in the image editor

2017-07-23 Thread bugzilla_noreply

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

--- Comment #6 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start

2017-07-23 Thread bugzilla_noreply

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

--- Comment #4 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 370029] black and white low resolution print only

2017-07-23 Thread bugzilla_noreply

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

--- Comment #5 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 374165] Tag Change in Menu Person search crashes

2017-07-23 Thread bugzilla_noreply

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

--- Comment #4 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 373638] Digikam doesn't show any files.

2017-07-23 Thread bugzilla_noreply

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

--- Comment #5 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 368468] digiKam hanging at start up with a collection that has >100000 sub folders

2017-07-23 Thread bugzilla_noreply

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

--- Comment #12 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

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

2017-07-23 Thread bugzilla_noreply

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

--- Comment #29 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 379261] Crash on attempting camera import

2017-07-23 Thread bugzilla_noreply

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

--- Comment #3 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 377517] digikam editor crash

2017-07-23 Thread bugzilla_noreply

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

--- Comment #4 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

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

2017-07-23 Thread bugzilla_noreply

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

--- Comment #10 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[digikam] [Bug 376401] Crash with MariaDB-Database

2017-07-23 Thread bugzilla_noreply

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

--- Comment #7 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[krita] [Bug 382628] New: G'Mic fails to start because could not find Qt platform plugin "xcb" - Krita v3.2.0-beta.2

2017-07-23 Thread ocumo

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

Bug ID: 382628
   Summary: G'Mic fails to start because could not find Qt
platform plugin "xcb" - Krita v3.2.0-beta.2
   Product: krita
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: G'Mic for Krita
  Assignee: krita-bugs-n...@kde.org
  Reporter: kxk-ocumoatbugs...@lugosys.com
  Target Milestone: ---

G'Mic won't start and no information or visible reaction is shown on Krita's
GUI when 'Start GMic-Qt' is selected in the Filter menu.

When launching Krita on the console, this error is logged exactly when the
'Start GMic-Qt' button is pressed:

stateChanged QProcess::ProcessState(Starting)
stateChanged QProcess::ProcessState(Running)
Plugin started true QProcess::ProcessState(Running)
gmic-qt: socket Key: "{5e393e6a-8442-4d77-ba98-1cf48f9c929f}"
This application failed to start because it could not find or load the Qt
platform plugin "xcb"
in "".

Reinstalling the application may fix this problem.
stateChanged QProcess::ProcessState(NotRunning)
pluginFinished 6 QProcess::ExitStatus(CrashExit)


My system: Kubuntu 16.04; Krita 3.2.0-beta.2 (running the appimage from
/opt/krita/); G'Mic v2.02


Steps to reproduce: 

1. Download the G'Mic plug-in for Krita in
http://gmic.eu/files/prerelease_linux/gmic_krita_qt_linux64.zip, and unzip the
files and "place it somewhere you can find it."
2. "Go to Settings → Configure Krita → G'Mic plugin and set G'MIC to the
filepath there; then restart Krita." (Quoted from Krita documentation).
3. Go to Krita's menu: Filter -> Start GMic-Qt, and when asked, enter the
location of the gmic_krita_qt file that was unzipped earlier. Alternatively, go
to Settings -> Configure Krita -> G'Mic-Qt Integration and enter (or browse to)
the gmic_krita_qt file path and click OK.
4. Restart Krita (don't know if it's necessary, but won't make a difference).
5. Open an image file, and select Filter -> 'Start GMic-Qt'.
At this point, nothing visible will happen in Krita's GUI. But if you have
launched Krita from the console, then you will see the aforementioned error
message.

Expected behaviour: G'Mic should launch when the 'Start GMic-Qt' button is
pressed.

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

[digikam] [Bug 367979] Crashes when scanning directories on network drive

2017-07-23 Thread bugzilla_noreply

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

--- Comment #4 from caulier.gil...@gmail.com ---
New digiKam 5.7.0 are built with current implementation as pre-release bundles:

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

Problem still reproducible ?

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

[amarok] [Bug 382454] amarock automatic playlist generator tagmatch does not work

2017-07-23 Thread bugzilla_noreply

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

p...@free.fr changed:

   What|Removed |Added

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

--- Comment #6 from p...@free.fr ---
I confirm it works OK with latest git

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

[phonon-backend-vlc] [Bug 371507] libvlc loads Qt4 plugin in a Qt5 application [ArchLinux]

2017-07-23 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||bjoern...@googlemail.com

--- Comment #33 from Elvis Angelaccio  ---
*** Bug 382617 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 382617] Dolphin crashes on play audio file

2017-07-23 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #1 from Elvis Angelaccio  ---
Please uninstall infinality or patched cairo.

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

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

[plasmashell] [Bug 360212] Icon positions in folder view of the desktop are often scrambled after reboot or logout

2017-07-23 Thread Florian Röhrer

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

--- Comment #8 from Florian Röhrer  ---
still not fixed! Is anybody working on this? My first report of the bug was
more than one year ago!

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

[plasmashell] [Bug 382601] Ark notification should say "canceled" instead "finished" when the user cancels the extraction

2017-07-23 Thread Kai Uwe Broulik

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

--- Comment #2 from Kai Uwe Broulik  ---
It does.
https://cgit.kde.org/plasma-workspace.git/tree/applets/notifications/package/contents/ui/Jobs.qml#n63

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

[plasmashell] [Bug 382601] Ark notification should say "canceled" instead "finished" when the user cancels the extraction

2017-07-23 Thread Elvis Angelaccio

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

Elvis Angelaccio  changed:

   What|Removed |Added

   Assignee|elvis.angelac...@kde.org|k...@privat.broulik.de
 CC||plasma-b...@kde.org
  Component|general |Notifications
Product|ark |plasmashell
   Target Milestone|--- |1.0
Version|17.04.3 |5.10.4

--- Comment #1 from Elvis Angelaccio  ---
The "Finished" string comes from Plasma. The applet should probably check
whether the KJob finished with an error.

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

[ark] [Bug 382609] sorting by date does not work

2017-07-23 Thread Elvis Angelaccio

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

--- Comment #1 from Elvis Angelaccio  ---
Seems to work here. Can you attach a screenshot showing what's wrong?

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

[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized

2017-07-23 Thread John Reiser

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

--- Comment #10 from John Reiser  ---
(In reply to John Reiser from comment #8)

> The underlying principle is that it can be useful to view "a bit is
> initialized" as equivalent to "the cardinality of the set of possible values
> is 1, not 2."

Expanding: if int 'a' is initialized and int 'x' is not, then consider the
code:
/* memcheck should complain about the comparison because x is uninit */
if (x == a) {
/* Now x is known to have only 1 value (namely, the value of 'a'),
 * so 'x' has become initialized.  So memcheck should no longer
complain
 * about 'x' in this True branch of the 'if'.
 */
g(x);  /* arbitrary code that does not change 'x' */
}
else {
x = 42;  /* Initialize 'x' */
}
/* Here the fan-out of if-else has re-converged, and 'x' is known to be
 * initialized at the end of all (both) branches, so 'x' is has become
initialized.
 */
so the initialization status of 'x' has been changed by a Read-and-Compare (to
an initialized value, with result Equal), and not by a Write.  The converging
of all branches to the same point, with 'x' initialized at the end of each
branch, "solidifies" the initialization going forward.  Even more fortuitously,
the detailed analysis is necessary only in the unlikely case when there are
some Uninit bits, so can be done by a closed subroutine in the infrequent
branch.

In the extreme case where the bit width of 'x' is 1, then comparing to any
initialized bit makes 'x' initialized, even without the balancing branch.  If
the result of the comparison is Equal then by the same reasoning as before, and
if NotEqual then that means Equal to the complement *bit*, whose set of all
possible values also has cardinality 1.

> It also applies to <, <=, >=, > when there are enough Valid bits that are
> contiguous with the MostSignificantBit, and the operands satisfy the
> relation when restricted to those contiguous bits.

The case of <= and >= is only for the '<' or '>' result implying non-equality
(unless the whole words are valid.)

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

[valgrind] [Bug 381553] VEX register allocator v3

2017-07-23 Thread Ivo Raisr

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

--- Comment #35 from Ivo Raisr  ---
The final set of patches implementing new VEX register allocator version 3
for AMD64 and X86 architectures.
All regression tests pass successfully, Firefox runs ok.

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

2017-07-23 Thread Thomas Baag

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

--- Comment #80 from Thomas Baag  ---
Created attachment 106803
  --> https://bugs.kde.org/attachment.cgi?id=106803=edit
plasmashell output with qt5-declarative 5.9.1-3 patched with 106799

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

[valgrind] [Bug 381553] VEX register allocator v3

2017-07-23 Thread Ivo Raisr

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

Ivo Raisr  changed:

   What|Removed |Added

 Attachment #106688|0   |1
is obsolete||

--- Comment #34 from Ivo Raisr  ---
Created attachment 106802
  --> https://bugs.kde.org/attachment.cgi?id=106802=edit
patch 009 - VEX part

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

[valgrind] [Bug 381553] VEX register allocator v3

2017-07-23 Thread Ivo Raisr

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

Ivo Raisr  changed:

   What|Removed |Added

 Attachment #106687|0   |1
is obsolete||

--- Comment #33 from Ivo Raisr  ---
Created attachment 106801
  --> https://bugs.kde.org/attachment.cgi?id=106801=edit
patch 009 - Valgrind part

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

[khelpcenter] [Bug 382570] No option to delete bookmarks

2017-07-23 Thread svadkost

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

--- Comment #6 from svadkost  ---
(In reply to Luigi Toscano from comment #5)
> (In reply to svadkost from comment #4)
> > Where exactly i should right click? 
> > I can add and see bookmarks only in menubar. Toolbar button do nothing. 
> 
> If you right-click on the bookmark, the context menu shows the option to
> delete the bookmark.

Like i said, i can see bookmarks only through menubar, and there is no way to
right-click in menubar.

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

[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized

2017-07-23 Thread John Reiser

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

--- Comment #9 from John Reiser  ---
(In reply to John Reiser from comment #8)

> The underlying principle is that it can be useful to view "a bit is
> initialized" as equivalent to "the cardinality of the set of possible values
> is 1, not 2."

Expanding: if 'a' is initialized and 'x' is not, then

> 
> It also applies to <, <=, >=, > when there are enough Valid bits that are
> contiguous with the MostSignificantBit, and the operands satisfy the
> relation when restricted to those contiguous bits.

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

[plasmashell] [Bug 382067] Thumbnails for grouped tasks become invisible / inaccessible after a certain number of tasks are in that group

2017-07-23 Thread bugzilla_noreply

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

christian.her...@astro.su.se changed:

   What|Removed |Added

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

--- Comment #6 from christian.her...@astro.su.se ---
I do not use a mouse with a scroll wheel.  I use a touchpad, where the scroll
wheel is emulated by touching the right margin.  I can not scroll the thumbnail
gallery with this.

As this bug is clearly present for me, and "WORKSFORME" was assigned by someone
who only "thinks it scrolls", I reopen as UNCONFIRMED.

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

[kinfocenter] [Bug 382627] New: Wrong OpenGL version shown

2017-07-23 Thread Fabian Vogt

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

Bug ID: 382627
   Summary: Wrong OpenGL version shown
   Product: kinfocenter
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: OpenGL
  Assignee: hubn...@gmail.com
  Reporter: fab...@ritter-vogt.de
  Target Milestone: ---

The OpenGL KCM only shows the version of the compatibility profile, which is
3.0. It should instead show the version of the core profile, which can be >
3.0.

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

[kdevelop] [Bug 382626] New: Crash in KDevelop::FunctionDeclaration::additionalIdentity() [Git Master]

2017-07-23 Thread Andreas Cord-Landwehr

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

Bug ID: 382626
   Summary: Crash in
KDevelop::FunctionDeclaration::additionalIdentity()
[Git Master]
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: cordlandw...@kde.org
  Target Milestone: ---

Created attachment 106800
  --> https://bugs.kde.org/attachment.cgi?id=106800=edit
Backtrace

Application: kdevelop (5.1.40)
 (Compiled from sources)
Qt Version: 5.8.0
Frameworks Version: 5.36.0
Operating System: Linux 4.9.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
- What I was doing when the application crashed:
Directly after startup during initial re-parsing of my project, the appended
crash happened. (full report as attachment)

KDevelop & KDevPlatform and plugins were just cleanly rebuilt from sources.

Thread 12 (Thread 0x7fcd98daa700 (LWP 25828)):
[KCrash Handler]
#6  0x7fce04e05efb in KDevelop::FunctionDeclaration::additionalIdentity()
const (this=0x55dd56429a80) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/duchain/functiondeclaration.cpp:88
#7  0x7fce04dd111d in KDevelop::Declaration::id(bool) const
(this=0x55dd56429a80, forceDirect=false) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/duchain/declaration.cpp:542
#8  0x7fce04db1c4a in
KDevelop::TopDUContext::indexForUsedDeclaration(KDevelop::Declaration*, bool)
(this=0x55dd5636f450, declaration=0x55dd56429a80, create=true) at
/opt/kde/src/extragear/kdevelop/kdevplatform/language/duchain/topducontext.cpp:1109
#9  0x7fcdbd6ac267 in (anonymous
namespace)::Visitor::Visitor(CXTranslationUnit, CXFile, IncludeFileContexts
const&, bool) (this=0x7fcd98da9200, tu=0x7fcd6a36d8a0, file=0x7fcd5846d1a0,
includes=..., update=true) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/duchain/builder.cpp:1425
#10 0x7fcdbd6accfa in Builder::visit(CXTranslationUnitImpl*, void*,
QHash const&, bool)
(tu=0x7fcd6a36d8a0, file=0x7fcd5846d1a0, includes=..., update=true) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/duchain/builder.cpp:1515
#11 0x7fcdbd705933 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=0x7fcd5846d1a0, imports=..., session=...,
features=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x55dd52313b60, abortFunction=...) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/duchain/clanghelpers.cpp:189
#12 0x7fcdbd70516a in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features,
QHash&, ClangIndex*,
std::function const&) (file=0x7fcd688cd7e0, imports=..., session=...,
features=KDevelop::TopDUContext::AllDeclarationsContextsAndUses,
includedFiles=..., index=0x55dd52313b60, abortFunction=...) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/duchain/clanghelpers.cpp:121
#13 0x7fcdbd99c418 in
ClangParseJob::run(QSharedPointer,
ThreadWeaver::Thread*) (this=0x55dd560bd410) at
/opt/kde/src/extragear/kdevelop/kdevelop/languages/clang/clangparsejob.cpp:322
#14 0x7fce03e01e60 in
ThreadWeaver::IdDecorator::run(QSharedPointer,
ThreadWeaver::Thread*) (this=0x55dd560bce80, self=..., thread=0x7fcd940013e0)
at /opt/kde/src/frameworks/threadweaver/src/iddecorator.cpp:69
#15 0x7fce03e02b46 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) (this=0x7fce0401e6b0
, job=..., thread=0x7fcd940013e0) at
/opt/kde/src/frameworks/threadweaver/src/executor.cpp:52
#16 0x7fce03e01a55 in
ThreadWeaver::Private::DefaultExecutor::execute(QSharedPointer
const&, ThreadWeaver::Thread*) (this=0x7fce0401e6b0
, job=..., thread=0x7fcd940013e0) at
/opt/kde/src/frameworks/threadweaver/src/job_p.cpp:70
#17 0x7fce03e02d8e in
ThreadWeaver::ExecuteWrapper::executeWrapped(QSharedPointer
const&, ThreadWeaver::Thread*) (this=0x55dd560bcac8, job=...,
thread=0x7fcd940013e0) at
/opt/kde/src/frameworks/threadweaver/src/executewrapper.cpp:64
#18 0x7fce03e019c1 in
ThreadWeaver::Private::DebugExecuteWrapper::execute(QSharedPointer
const&, ThreadWeaver::Thread*) (this=0x55dd560bcac8, job=...,
th=0x7fcd940013e0) at /opt/kde/src/frameworks/threadweaver/src/job_p.cpp:58
#19 0x7fce03e02d8e in
ThreadWeaver::ExecuteWrapper::executeWrapped(QSharedPointer
const&, ThreadWeaver::Thread*) (this=0x55dd560bcaf0, job=...,
thread=0x7fcd940013e0) at
/opt/kde/src/frameworks/threadweaver/src/executewrapper.cpp:64
#20 0x7fce03e02d19

[systemsettings] [Bug 350688] Mouse acceleration setting has no effect with libinput

2017-07-23 Thread Yevgeny Kosarzhevsky

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

Yevgeny Kosarzhevsky  changed:

   What|Removed |Added

 CC||phao...@gmail.com

--- Comment #12 from Yevgeny Kosarzhevsky  ---
Hey,

I have the same problem in systemsettings version 5.8.7.
Acceleration settings have no effect

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

2017-07-23 Thread Thomas Baag

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

--- Comment #79 from Thomas Baag  ---
As this bug report made me aware of high (single thread) CPU usage of
plasmashell I now can confirm this part of the bug. CPU usage is substantially
higher with desktop slideshow enabled (~30%) than normal (1%-5%) when this bug
happens.

It's harder to trigger than the memory leak bug. I had to have both screens set
to slideshow. Setting picture to change every second helps a lot with
triggering it. Still looks like some race condition.

With help of GALLIUM_HUD I found redraws go up a lot when the bug strikes.
Climbing up to 330 redraws per second as shown here http://imgur.com/a/Y45SQ.

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

2017-07-23 Thread David Edmundson

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

--- Comment #78 from David Edmundson  ---
Created attachment 106799
  --> https://bugs.kde.org/attachment.cgi?id=106799=edit
Add debug in QtDeclarative QSGGuiThreadRenderLoop

Can someone run with this on QtDeclarative and attach the output please.

It won't fix anything, it just adds debug.
It only changes one of the render loops, but I think the relevant one.

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

[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention

2017-07-23 Thread Martin Flöser

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

--- Comment #26 from Martin Flöser  ---
@Thomas: there simply is no usability problem here. This feature exists for >
10 years (which also means I did not design or implement it) and works with the
constraints for the same time. This must have been broken with Kicker as well
(yes I talk of KDE 3 here). This is the first bug report for this problem. To
me it means it is not a problem which users will hit likely.

This means it also doesn't make sense to invest time into it. Sorry, but we
have more important things to fix. Lots of them.

I can offer some solutions:
1) remove focus stealing prevention HIGH and EXTREME. Reasoning: we are not
able to make it work in a Plasma session and don't have the expertise to
maintain it
2) We remove the GUI setting and make it an advanced option
3) We show a warning that this breaks Plasma panels if selected

If I would have to pick one I would go for 3 as we do that in other places as
well.

For example if you want to use "Focus Under Mouse" it says that Alt+Tab cannot
work. Or the Compositor settings show a warning when selecting any of the
"dangerous" settings.

Please note that I marked the bug as WORKSFORME before we had misbehaving in
this bug report. There is no punishment going on.

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

[k3b] [Bug 377105] Disc space/time bar is broken

2017-07-23 Thread Leslie Zhai

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

--- Comment #12 from Leslie Zhai  ---
I only fixed the vertical issue, but I have no idea about Horizontal, could you
give me some hint? The green bar is too short for the Horizontal text, it
doesn't like vertical, I can ask for more space for vertical text.

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

[plasmashell] [Bug 382625] Crash after coming back from suspension

2017-07-23 Thread Antonio Chirizzi

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

--- Comment #1 from Antonio Chirizzi  ---
[Continuing previous comment, sent incomplete by mistake]
... in the last 14 days... 
But this time (it is the 3rd in 6 days) I was able to send the info cause
finally the "login" button was available!!!)

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

2017-07-23 Thread Thomas Baag

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

--- Comment #77 from Thomas Baag  ---
Comment 60 fixed the memory leak problem I described in bug 382602.

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

[plasmashell] [Bug 382580] Plasma crashes when searching in application launcher

2017-07-23 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---


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

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

[plasmashell] [Bug 382625] New: Crash after coming back from suspension

2017-07-23 Thread Antonio Chirizzi

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

Bug ID: 382625
   Summary: Crash after coming back from suspension
   Product: plasmashell
   Version: 5.8.7
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: antonio.chiri...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.7)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.4.0-83-generic x86_64
Distribution: Linux Mint 18.1 Serena

-- Information about the crash:
The system was suspended. The crash happens many times when coming back from
suspension, even though no major prolems are noticed: the message that it
crashed is available on the toolbar though.
Please note this is a Lenovo P50 with the nvidia graphics card. I have had so
many problems trying to make it work with 2 additional 4K monitors that I
really want KDE to work properly.
In this case the laptop was on the battery, and no monitor has been attached in
the last

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

Thread 23 (Thread 0x7f837e7ba700 (LWP 23195)):
#0  0x7f84a1b2570d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f849e85738c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f83701cc8e0, timeout=, context=0x7135730) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135
#2  0x7f849e85738c in g_main_context_iterate (context=0x7135730,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835
#3  0x7f849e857712 in g_main_loop_run (loop=0x6aa4500) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4034
#4  0x7f83c4bda9d6 in gdbus_shared_thread_func (user_data=0x65af370) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./gio/gdbusprivate.c:246
#5  0x7f849e87dbb5 in g_thread_proxy (data=0x6cfd8a0) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gthread.c:780
#6  0x7f84a13076ba in start_thread (arg=0x7f837e7ba700) at
pthread_create.c:333
#7  0x7f84a1b313dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7f837d3af700 (LWP 23194)):
#0  0x7f849e857372 in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f8374155d50, timeout=, context=0x63ee100) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4134
#1  0x7f849e857372 in g_main_context_iterate
(context=context@entry=0x63ee100, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835
#2  0x7f849e85749c in g_main_context_iteration (context=0x63ee100,
may_block=may_block@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#3  0x7f849e8574d9 in glib_worker_main (data=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:5672
#4  0x7f849e87dbb5 in g_thread_proxy (data=0x6cfd850) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gthread.c:780
#5  0x7f84a13076ba in start_thread (arg=0x7f837d3af700) at
pthread_create.c:333
#6  0x7f84a1b313dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7f837700 (LWP 22520)):
#0  0x7f84a244b4cd in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f84a244cafc in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f849e85691d in g_main_context_prepare
(context=context@entry=0x7f8378001c00, priority=priority@entry=0x7f837fffebc0)
at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3442
#3  0x7f849e8572bb in g_main_context_iterate
(context=context@entry=0x7f8378001c00, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3820
#4  0x7f849e85749c in g_main_context_iteration (context=0x7f8378001c00,
may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#5  0x7f84a244d37b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f84a23f5ffa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f84a221e9e4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f84a2223808 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f84a13076ba in start_thread (arg=0x7f837700) at
pthread_create.c:333
#10 0x7f84a1b313dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7f83911fd700 (LWP 4552)):
#0  0x7f84a130d360 in pthread_cond_wait@@GLIBC_2.3.2 () at

[plasmashell] [Bug 369430] QQmlDelegateModel::_q_itemsChanged - kickoff version

2017-07-23 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

 CC||anohigisa...@gmail.com

--- Comment #22 from David Edmundson  ---
*** Bug 382580 has been marked as a duplicate of this bug. ***

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

[kdevelop] [Bug 382624] New: Crash when creating a new C++ Class

2017-07-23 Thread Scott Sloan

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

Bug ID: 382624
   Summary: Crash when creating a new C++ Class
   Product: kdevelop
   Version: 5.1.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: scottsl...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.1.1)

Qt Version: 5.7.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.10-300.fc26.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
1.) Created a new Empty Project
2.) Right clicked on the Project to create a new C++ Class
3.) Selected just the constructor to generate
4.) Crashed

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0e9d5c4e00 (LWP 3367))]

Thread 21 (Thread 0x7f0e24e78700 (LWP 3583)):
#0  0x7f0eb017481b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0eb863b3fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f0eb4c35985 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f0eb4c398f8 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f0eb4c34b4d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f0eb4c3783b in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f0eb863ac9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f0eb016e36d in start_thread () at /lib64/libpthread.so.0
#8  0x7f0eb7a22b8f in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f0e25679700 (LWP 3582)):
#0  0x7f0eb017481b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0eb863b3fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f0eb4c35985 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f0eb4c398f8 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f0eb4c34b4d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f0eb4c3783b in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f0eb863ac9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f0eb016e36d in start_thread () at /lib64/libpthread.so.0
#8  0x7f0eb7a22b8f in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f0e0f3b7700 (LWP 3581)):
#0  0x7f0eb017481b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0eb863b3fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f0eb4c35985 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f0eb4c398f8 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f0eb4c34b4d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f0eb4c3783b in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f0eb863ac9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f0eb016e36d in start_thread () at /lib64/libpthread.so.0
#8  0x7f0eb7a22b8f in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f0e44a18700 (LWP 3580)):
#0  0x7f0eb017481b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0eb863b3fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f0eb4c35985 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f0eb4c398f8 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f0eb4c34b4d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f0eb4c3783b in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f0eb863ac9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f0eb016e36d in start_thread () at /lib64/libpthread.so.0
#8  0x7f0eb7a22b8f in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f0e0d1a6700 (LWP 3579)):
#0  0x7f0eb017481b in

[dolphin] [Bug 378824] Dolphin displays a "Loop device" for each Snap application installed.

2017-07-23 Thread Dr . Chapatin

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

--- Comment #2 from Dr. Chapatin  ---
I can confirm on Arch and neon dev unstable.

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

[plasmashell] [Bug 382602] Video memory leak with desktop configured to slideshow

2017-07-23 Thread Thomas Baag

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

--- Comment #3 from Thomas Baag  ---
qt5-declarative package from Antonio Rojas linked in bug 381000 seems to have
fixed the issue for me. Thanks a lot.

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

[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized

2017-07-23 Thread John Reiser

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

--- Comment #8 from John Reiser  ---
(In reply to Julian Seward from comment #5)
>  What's the underlying insight
> here?  In particular, why is it the case that knowing the two operands are
> equal allows us to mark the operands as more defined than they were
> originally?
> 
> Is this specific to == and !=, or is it more general?

The underlying principle is that it can be useful to view "a bit is
initialized" as equivalent to "the cardinality of the set of possible values is
1, not 2."

It also applies to <, <=, >=, > when there are enough Valid bits that are
contiguous with the MostSignificantBit, and the operands satisfy the relation
when restricted to those contiguous bits.

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

[valgrind] [Bug 381326] recognize re-convergent fanout before complaining about Uninitialized

2017-07-23 Thread John Reiser

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

--- Comment #7 from John Reiser  ---
(In reply to Julian Seward from comment #6)
> In particular I am trying to figure out if this can somehow be used to avoid
> the problems shown at
> https://bugs.llvm.org//show_bug.cgi?id=12319
> and
> https://github.com/rust-lang/rust/issues/11710

The 0x4560123 case (https://bugs.llvm.org//show_bug.cgi?id=12319#c2) is not
related.  Instead, it is "not-equal in any bit position where both operands
have valid bits, implies not-equal for the whole word."

As *presented*, the main Description for "  if (!h(, ) || a == 42 || b ==
33)",  namely https://bugs.llvm.org//show_bug.cgi?id=12319#c0 , is a bug in
gcc.  The code for h() is not shown, so it and its post-conditions are
*unknown*.  Therefore gcc must evaluate the if-expression according to the
rules of C, namely left-to-right; but gcc evaluated the a==42 before the
!result_of_h().  Besides, the dcache has latency, so it would be 1 to 3 cycles
faster (and 3 bytes larger) to fetch 'a' first:
call h
mov 4(%rsp),%ecx  // overlap cache latency; result might be unused
testb %al,%al; je .LBB0_3
cmpl $42,%ecx; je .LBB0_3

The 'rust' case
https://github.com/rust-lang/rust/issues/11710#issuecomment-33315140 is
similarly muddled by imprecise presentation.  "LLVM is allowed to generate
undefined reads if it can not change the program behavior."  memcheck does not
complain about the Read, but about the Compare.

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

[frameworks-solid] [Bug 318068] KDE mounts devices as root instead of as user

2017-07-23 Thread Arthur Țițeică

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

--- Comment #12 from Arthur Țițeică  ---
Polkit will misbehave with /proc mounted with hidepid=2 option.

I've been recently been bitten by this, maybe it helps.

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

[kexi] [Bug 125843] Add support for importing native SQLite 3 databases

2017-07-23 Thread Jarosław Staniek

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

--- Comment #13 from Jarosław Staniek  ---
A word from maintainer. SQLite is the most used db engine in the world and we
do support it since 2004. At the time it was not easy/possible to work without
metadata, now it is doable at least for people that know what they are doing,
e.g. those that have existing database files and need to work with them without
creating new ones.

Importing will be always "catching the rabbit" challenge, therefore there is a
mid-term ultimate plan: wish #380088 "Support opening native databases without
importing" for Kexi 4.

Especially importing within the same engine often seems to be overhead and can
frustrate users. Our aim is perfect convenience not exiting e.g. in the world
or spreadsheets.

Extra: C++ developers would get a tool for working with existing databases via
the KDb framework (https://community.kde.org/KDb) which is the pillar of Kexi.

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

[krita] [Bug 382623] New: Can not apply changed language

2017-07-23 Thread bugzilla_noreply

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

Bug ID: 382623
   Summary: Can not apply changed language
   Product: krita
   Version: 3.1.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: leeheech...@gmail.com
  Target Milestone: ---

Hi,thanks for watching this issue.
I'm using krita 3.1.4 and installed via ubuntu snap.

But i have a problem. I can't switch program language.
And here is a log below.
krita appimage works fine.

lee@lee-Lemur:~$ krita
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (ko_KR.UTF-8)
Qt: Session management error: None of the authentication protocols specified
are supported
XmbTextListToTextProperty result code -2
OpenGL Info
  Vendor:  Intel Open Source Technology Center
  Renderer:  "Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) "
  Version:  3.0 Mesa 12.0.6
  Shading language:  1.30
  Requested format:  QSurfaceFormat(version 3.0, options QFlags(0x4),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  2)
  Current format:QSurfaceFormat(version 3.0, options QFlags(0x4),
depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  0)
 Version: 3 . 0
 Supports deprecated functions true
krita has opengl true
Setting XDG_DATA_DIRS
"/snap/krita/22/usr/bin/../share:/home/lee/snap/krita/22/.local-3.1.4/share:/snap/krita/22/usr/share:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/home/lee/snap/anbox/common/app-data"
Available translations QSet("en_GB", "hne", "ne", "ar", "nb", "it", "sv", "nl",
"gl", "fy", "ug", "ca@valencia", "ru", "lv", "pl", "he", "is", "da", "de",
"ja", "zh_CN", "xh", "mr", "fr", "el", "be", "cy", "oc", "ca", "et", "kk",
"ms", "mai", "zh_TW", "tr", "wa", "hu", "sk", "es", "ro", "tg", "ast", "hi",
"uz@cyrillic", "km", "ga", "se", "ta", "ia", "vi", "pt", "th", "pa", "bs",
"bg", "uk", "en_US", "fa", "uz", "eu", "mk", "nn", "eo", "nds", "sq", "fi",
"br", "pt_BR", "hr", "af", "cs", "ko", "sl", "lt")
Available domain translations QSet("en_GB", "hne", "ne", "ar", "nb", "it",
"sv", "nl", "gl", "fy", "ug", "ca@valencia", "ru", "lv", "pl", "he", "is",
"da", "de", "ja", "zh_CN", "xh", "mr", "fr", "el", "be", "cy", "oc", "ca",
"et", "kk", "ms", "mai", "zh_TW", "tr", "wa", "hu", "sk", "es", "ro", "tg",
"ast", "hi", "uz@cyrillic", "km", "ga", "se", "ta", "ia", "vi", "pt", "th",
"pa", "bs", "bg", "uk", "en_US", "fa", "uz", "eu", "mk", "nn", "eo", "nds",
"sq", "fi", "br", "pt_BR", "hr", "af", "cs", "ko", "sl", "lt")
Override language: "en_US"
Qt ui languages ("en", "en-US", "en-Latn-US")
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2
XmbTextListToTextProperty result code -2

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

[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention

2017-07-23 Thread Thomas Pfeiffer

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 CC||thomas.pfeif...@kde.org

--- Comment #25 from Thomas Pfeiffer  ---
>From a purely technical perspective, Martin is right: This is not a technical
bug, because it works exactly as he has designed it.

However, that does not keep it from being a massive usability problem. 
Sure, from a technical perspective, a popup from an application launcher is a
new window, but not from a user's perspective.
>From a user perspective, it's really just "I click this button, and then that
button spawns a popup as a natural reaction to my click". The popup is an
extension to the button, not a separate window that just happens to be spawned
by the button.

If a user has an expectation towards the system but the system behaves
differently, then from a user perspective it's broken. Users don't care about
what is technically correct, and they should not have to.

Martin, you say that focus-stealing prevention is an advanced feature. You are
certainly right, but I am very certain that there are lots of users out there
who are advanced enough to want to use focus-stealing prevention, but not
advanced enough to understand why that keeps the launcher popup from opening.
The latter knowledge is extremely advanced, as it requires in-depth knowledge
of window management.

So yes, it WORKSFORYOU, but only because you have knowledge that the vast
majority of users - including those who are advanced enough to want to use
focus-stealing prevention - don't have.

>From a social perspective: I don't approve of people reopening bugs that the
maintainer has closed (unless new information has emerged, which was not the
case here), and I do not approve of sarcasm in bug reports either.

On the other hand, I do not approve of punishing all users with refusal to fix
a usability problem because a few users behaved inappropriately in a bug
report, either. I do not think this is fair towards the other users who have
never misbehaved but would be stuck with a usability problem, anyway.

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

[k3b] [Bug 382622] Do not show progress percentage in main window

2017-07-23 Thread Dr . Chapatin

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

Dr. Chapatin  changed:

   What|Removed |Added

Summary|Do not show percentage  |Do not show progress
   |progress in main window |percentage in main window

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

[k3b] [Bug 382622] New: Do not show percentage progress in main window

2017-07-23 Thread Dr . Chapatin

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

Bug ID: 382622
   Summary: Do not show percentage progress in main window
   Product: k3b
   Version: 17.04.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: GUI/Usability
  Assignee: k...@kde.org
  Reporter: yy...@gmx.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

Created attachment 106798
  --> https://bugs.kde.org/attachment.cgi?id=106798=edit
screenshot

Both window title bars from main and burn/copy progress window show the
progress percentage (see my screenshot). I think the percentage from main
window is redundant and unnecessary. Show this informtation only in progress
window is enough.

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

[frameworks-syntax-highlighting] [Bug 370459] Could you add ats mode for kate?

2017-07-23 Thread Dominik Haumann

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

--- Comment #3 from Dominik Haumann  ---
As testcase, just attach some example script here in this bug report.

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

[kate] [Bug 372068] Kate 3.13.3 randomly switches keyboard layout

2017-07-23 Thread Christoph Cullmann

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

Christoph Cullmann  changed:

   What|Removed |Added

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

--- Comment #4 from Christoph Cullmann  ---
Sorry, can not reproduce.
If you have some way to do so with a current release, please report how we can
do so.
Thanks!

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

[frameworks-syntax-highlighting] [Bug 371973] kate/kwrite highlights php mime_content_type as depricated

2017-07-23 Thread Dominik Haumann

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/syn
   ||tax-highlighting/e1f59eaa6d
   ||b27674d6c8492cb7bf7f325e121
   ||603
 Resolution|--- |FIXED
   Version Fixed In||5.37

--- Comment #1 from Dominik Haumann  ---
Git commit e1f59eaa6db27674d6c8492cb7bf7f325e121603 by Dominik Haumann.
Committed on 23/07/2017 at 14:07.
Pushed by dhaumann into branch 'master'.

PHP: Remove mime_content_type() from list of deprecated functions

Ths was a mistake by PHP, see https://bugs.php.net/bug.php?id=71367

FIXED-IN: 5.37

M  +2-2data/syntax/php.xml

https://commits.kde.org/syntax-highlighting/e1f59eaa6db27674d6c8492cb7bf7f325e121603

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

[kate] [Bug 369467] Cant use Open/Save as dialog on wayland

2017-07-23 Thread Christoph Cullmann

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

Christoph Cullmann  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Cullmann  ---
We use the native dialogs via QFileDialog, if that keeps to be an issue, please
report that upstream to Qt.

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

[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention

2017-07-23 Thread Sebastian Kügler

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

--- Comment #24 from Sebastian Kügler  ---
I'm aware that a solution to this problem means marking these windows in some
way, not a biggie in my opinion, but maybe the most straightforward fix is to
mark these windows as belonging to the shell and then allowing them to steal
focus?

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

[frameworks-syntax-highlighting] [Bug 373002] Single line comment in Less begins a new region

2017-07-23 Thread Dominik Haumann

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
Already fixed, see https://phabricator.kde.org/D4296 since KDE Frameworks 5.32.

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

[frameworks-syntax-highlighting] [Bug 374573] XML syntax: XBEL bookmarks are not highlighted by default

2017-07-23 Thread Dominik Haumann

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.37
  Latest Commit||https://commits.kde.org/syn
   ||tax-highlighting/9425e1b610
   ||1676d9064fd389391e36b13f204
   ||95f
 Resolution|--- |FIXED

--- Comment #1 from Dominik Haumann  ---
Git commit 9425e1b6101676d9064fd389391e36b13f20495f by Dominik Haumann.
Committed on 23/07/2017 at 13:58.
Pushed by dhaumann into branch 'master'.

XML: Add XBEL extension/mimetype to xml highlighting

FIXED-IN: 5.37

M  +1-1data/syntax/xml.xml

https://commits.kde.org/syntax-highlighting/9425e1b6101676d9064fd389391e36b13f20495f

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

[marble] [Bug 382612] KDE-Marble crash on exit

2017-07-23 Thread Dennis Nienhüser

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

Dennis Nienhüser  changed:

   What|Removed |Added

 CC||nienhue...@kde.org

--- Comment #1 from Dennis Nienhüser  ---
Does it also crash when satellites are not shown?

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

[kate] [Bug 382254] crash-on-exit in the katesnippets plugin

2017-07-23 Thread Christoph Cullmann

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

Christoph Cullmann  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kat
   ||e/5233308e83f2cfb8619db2a26
   ||148521b458fac46
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christoph Cullmann  ---
Git commit 5233308e83f2cfb8619db2a26148521b458fac46 by Christoph Cullmann.
Committed on 23/07/2017 at 13:51.
Pushed by cullmann into branch 'master'.

fix crash if no gui factory around

M  +6-3addons/snippets/katesnippets.cpp

https://commits.kde.org/kate/5233308e83f2cfb8619db2a26148521b458fac46

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

[frameworks-syntax-highlighting] [Bug 375245] Bash Syntax highlighting/color for option

2017-07-23 Thread Dominik Haumann

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

Dominik Haumann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.37
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/syn
   ||tax-highlighting/12c6df3b6d
   ||958ac87a2a678b24b8e84c624e0
   ||1e7

--- Comment #2 from Dominik Haumann  ---
Git commit 12c6df3b6d958ac87a2a678b24b8e84c624e01e7 by Dominik Haumann.
Committed on 23/07/2017 at 13:49.
Pushed by dhaumann into branch 'master'.

Bash: Fix incorrect highlighting for command options

FIXED-IN: 5.37

M  +6-0autotests/html/test.bash.html
M  +6-0autotests/input/test.bash
M  +3-2data/syntax/bash.xml

https://commits.kde.org/syntax-highlighting/12c6df3b6d958ac87a2a678b24b8e84c624e01e7

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

[kmymoney4] [Bug 382621] New: Date column is not wide enough to show DD/MM/YYYY

2017-07-23 Thread Eion MacDonald

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

Bug ID: 382621
   Summary: Date column is not wide enough to show DD/MM/
   Product: kmymoney4
   Version: 4.8.0
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: eion...@btinternet.com
  Target Milestone: ---

Created attachment 106797
  --> https://bugs.kde.org/attachment.cgi?id=106797=edit
View of date column width JPG

I have used KMyMoney on Windows 10 and on OpenSUSE Linux. In both set ups the
date column in ledgers is too narrow. It shows e.g. 23/06/2 instead of
23/06/2017.  How to widen the date column in all ledgers?

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

[okular] [Bug 314755] "Color options" from "Print Dialog -> Properties -> Advanced" override "Color options" from "Print Dialog -> Options -> Options"

2017-07-23 Thread Luigi Toscano

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

--- Comment #5 from Luigi Toscano  ---
(In reply to Eric L. from comment #3)
> This issue does still exist in okular-16.08.3-1.fc25.x86_64 respectively:
> 

That version is still based on kdelibs4, so of course no changes.
The first Frameworks version of Okular is 1.0, part of KDE Applications 16.12.

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

[kate] [Bug 382469] kate closed unexpectedly in debian stretch

2017-07-23 Thread Christoph Cullmann

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

Christoph Cullmann  changed:

   What|Removed |Added

 CC||cullm...@kde.org
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Christoph Cullmann  ---
Hi, would need some way to reproduce.
Can you reproduce that with some more recent Kate/Frameworks version?

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

[kate] [Bug 381433] Kate crashes when opening

2017-07-23 Thread Christoph Cullmann

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

Christoph Cullmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kat
   ||e/34e61eda173a3e2db5b8d4f0b
   ||a86c3b2eb05f5df
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Christoph Cullmann  ---
Git commit 34e61eda173a3e2db5b8d4f0ba86c3b2eb05f5df by Christoph Cullmann.
Committed on 23/07/2017 at 13:31.
Pushed by cullmann into branch 'master'.

fix crash during load of view manager state
export only visible splitter parts
avoid cleanups during loading

M  +33   -50   kate/kateviewmanager.cpp
M  +1-2kate/kateviewmanager.h

https://commits.kde.org/kate/34e61eda173a3e2db5b8d4f0ba86c3b2eb05f5df

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

[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts

2017-07-23 Thread Yogesh Marwaha

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

Yogesh Marwaha  changed:

   What|Removed |Added

 CC||yogeshm@gmail.com

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

[k3b] [Bug 377105] Disc space/time bar is broken

2017-07-23 Thread Dr . Chapatin

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

--- Comment #11 from Dr. Chapatin  ---
Created attachment 106796
  --> https://bugs.kde.org/attachment.cgi?id=106796=edit
screenshot from neon unstable

Thin bug is still present.

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

[frameworks-syntax-highlighting] [Bug 379298] Syntax highliting not working properly for perl when using heredoc

2017-07-23 Thread Dominik Haumann

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/syn
   ||tax-highlighting/2f8a2406fc
   ||925583d7a1c548f99675e181573
   ||3c7
   Version Fixed In||5.37

--- Comment #1 from Dominik Haumann  ---
Git commit 2f8a2406fc925583d7a1c548f99675e1815733c7 by Dominik Haumann.
Committed on 23/07/2017 at 13:09.
Pushed by dhaumann into branch 'master'.

Perl: Fix heredoc highlighting with leading spaces in the delimiter

FIXED-IN: 5.37

M  +4-0autotests/folding/highlight.pl.fold
M  +11   -0autotests/html/highlight.pl.html
M  +11   -0autotests/input/highlight.pl
M  +4-0autotests/reference/highlight.pl.ref
M  +4-4data/syntax/perl.xml

https://commits.kde.org/syntax-highlighting/2f8a2406fc925583d7a1c548f99675e1815733c7

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

[frameworks-baloo] [Bug 382610] unknown crash

2017-07-23 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 382602] Video memory leak with desktop configured to slideshow

2017-07-23 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #2 from David Edmundson  ---
thanks, please follow linked report.

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

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

[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow

2017-07-23 Thread David Edmundson

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

David Edmundson  changed:

   What|Removed |Added

 CC||tho...@b2ag.de

--- Comment #76 from David Edmundson  ---
*** Bug 382602 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 315376] Digikam Crash on Startup with active X11 color profile

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DOWNSTREAM  |FIXED

--- Comment #8 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 324780] Crash on startup

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

 Resolution|UPSTREAM|FIXED
   Version Fixed In||5.7.0

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[amarok] [Bug 382620] mp3 stream not working

2017-07-23 Thread bugzilla_noreply

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

p...@free.fr changed:

   What|Removed |Added

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

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

[amarok] [Bug 382620] mp3 stream not working

2017-07-23 Thread bugzilla_noreply

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

--- Comment #1 from p...@free.fr ---
after erasing all my old amarok config files in .kde  now it works.

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

[digikam] [Bug 318762] Digicam crash

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318987] Digikam crashes at startup

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||5.7.0

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318842] digiKam crash in color management

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

Summary|digikam |digiKam crash in color
   ||management
 Resolution|DUPLICATE   |FIXED
   Version Fixed In||5.7.0

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318730] digiKam crashes.

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||5.7.0

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318859] Digikam crashes on start

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||5.7.0

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318989] digikam crash

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 319144] digikam crashes

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 326347] Absturz bei Start

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 320357] Crash de Digikam

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #3 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318848] Crash on startup the application

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #3 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 319674] Digikam crashed

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||5.7.0

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318744] Digikam stop immediatly when I try to open it

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

Summary|Digikam stp immediatly when |Digikam stop immediatly
   |I try to open it|when I try to open it
 Resolution|DUPLICATE   |FIXED
   Version Fixed In||5.7.0

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318861] Digikam crashes on startup

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[systemsettings] [Bug 379930] kcm_keyboard kills ibus daemon, entirely breaking the keyboard

2017-07-23 Thread Evgeny Brazgin

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

Evgeny Brazgin  changed:

   What|Removed |Added

 CC||k...@xapienz.ru

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

[digikam] [Bug 319166] Digikam crashes on 64bit version

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[digikam] [Bug 318991] Digikam crash at startup

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we use drop lcms version 1.x in favor of lcms version 2.x.
This problem will not reproducible.

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

[frameworks-kio] [Bug 382459] Exec lines in service files must not have any path prefix on Windows

2017-07-23 Thread Ralf Habacker

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

--- Comment #6 from Ralf Habacker  ---
(In reply to Christophe Giboudeaux from comment #5)
> @something@somedir without any separator is not intuitive. I'd really prefer
> having something to replace the configure_file macro instead.

You are thinking about something like
https://build.opensuse.org/package/view_file/home:rhabacker:branches:windows:mingw:win32:KF536/mingw32-kwallet/0002-Win32-fix-for-installing-kwalletd-dbus-service.patch?expand=1
?

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

[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention

2017-07-23 Thread Nate Graham

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

--- Comment #23 from Nate Graham  ---
For me, Kickoff works just fine with Focus Follows Mouse as well as Focus
Strictly Under Mouse.

I agree with Sebastian. We are arguing over technical details that it is
unreasonable to expect users to understand, or care about. We should find a way
to make this work rather than come up with reasons to justify why it doesn't.

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

[digikam] [Bug 339309] digikam crashed when closing

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

  Component|general |Metadata-Engine

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

[digikam] [Bug 206381] crash of app when closing app

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

  Component|general |Database-Files
   Version Fixed In||5.7.0
 Resolution|DUPLICATE   |FIXED

--- Comment #4 from caulier.gil...@gmail.com ---
Since digiKam 5.0.0, we drop KIO slave in favor of a multi-threaded interface
to query the database. This problem will not reproducible.

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

[digikam] [Bug 273133] crash when move files from harddisc folder to digikam

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

  Component|general |Thumbnails

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

[digikam] [Bug 290889] always crash

2017-07-23 Thread bugzilla_noreply

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

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

   What|Removed |Added

  Component|general |ImageEditor

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

< 1 2 3 4 5 6 >

101 - 200 of 536 matches

Mail list logo