[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[Maik Qualmann]

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

--- Comment #30 from Maik Qualmann  ---
Are you already authorized in Ubuntu 16.04? If so, does it work if you change
your account and log back into the browser?

Maik

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

[clazy] [Bug 389006] Asserts are triggered in debug build

[bugzilla_noreply]

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

--- Comment #5 from ivan.donchevs...@qt.io ---
Created attachment 109902
  --> https://bugs.kde.org/attachment.cgi?id=109902=edit
Patch that fixes asserts by adding extra checks

I've added extra checks which prevent described assets.

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

[clazy] [Bug 389006] Asserts are triggered in debug build

[bugzilla_noreply]

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

--- Comment #4 from ivan.donchevs...@qt.io ---
I've rechecked. The initial assert happens even with level0. Another one with
Loc.isMacroID() happens only starting with level1

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

[krita] [Bug 389037] [Crash] Krita crashed when draging and dropping transparency mask (random)

[Raghavendra kamath]

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

--- Comment #1 from Raghavendra kamath  ---
I can reproduce this reliably now,

You have to repeatedly hold ctrl drag and drop the transparency mask on layers
one by one.

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

[kdeplasma-addons] [Bug 378342] Input Method Panel doesn't seem to work

[Eike Hein]

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

--- Comment #14 from Eike Hein  ---
ibus-ui-gtk3 doesn't integrate well with Plasma. It also only supports ibus and
doesn't support fcitx.

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

[kleopatra] [Bug 389008] Failed to Find

[Andre Heinecke]

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

Andre Heinecke  changed:

   What|Removed |Added

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

--- Comment #1 from Andre Heinecke  ---
Hi,

If Kleopatra can't find it it really means that GnuPG (the crypto backend)
reported this error.

Please try to use the command line (cmd.exe) and do
 gpg --decrypt 

I'm 90% sure that this will fail too. Maybe it gives you a better indication of
the problem. You can add --verbose to the command to get more output.

If you still think that gnupg should be able to decrypt your files then please
report an issue to GnuPG in dev.gnupg.org

Thanks and best Regards,
Andre

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

[krita] [Bug 389037] New: [Crash] Krita crashed when draging and dropping transparency mask (random)

[Raghavendra kamath]

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

Bug ID: 389037
   Summary: [Crash] Krita crashed when draging and dropping
transparency mask (random)
   Product: krita
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: raghavendr.ra...@gmail.com
  Target Milestone: ---

Application: krita (4.0.0-beta1 (git 26f6401))

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was dragging and dropping transperancy mask while holding control to
duplicate it  from one layer to another. 

I tried to reproduce this but couldn't do it reliably although i have
encountered this twice or thrice.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fafc4d79dc0 (LWP 21090))]

Thread 6 (Thread 0x7faf7a4dc700 (LWP 21107)):
#0  0x7fafb93f43d8 in read () from /usr/lib/libc.so.6
#1  0x7fafb4e9e801 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fafb4e58afc in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7fafb4e58fc6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7fafb4e5913e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7fafba2a66b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#6  0x7fafba24882b in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#7  0x7fafba05878e in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x7fafa70cebcb in ?? () from /usr/lib/libQt5Quick.so.5
#9  0x7fafba05db2d in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7fafb81d908c in start_thread () from /usr/lib/libpthread.so.0
#11 0x7fafb9402e1f in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7faf7bbe5700 (LWP 21106)):
#0  0x7fafb93f891b in poll () from /usr/lib/libc.so.6
#1  0x7fafb4e59023 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fafb4e5913e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fafba2a66b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fafba24882b in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fafba05878e in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fafa6c80a19 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fafba05db2d in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fafb81d908c in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fafb9402e1f in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7faf8bd65700 (LWP 21105)):
#0  0x7fafb81df39d in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fafba05f00c in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7fafbb3e9b76 in ?? () from /usr/lib/libQt5Widgets.so.5
#3  0x7fafba05db2d in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fafb81d908c in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fafb9402e1f in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7faf8b564700 (LWP 21104)):
#0  0x7fafb93d0b10 in nanosleep () from /usr/lib/libc.so.6
#1  0x7fafba2a5fff in ?? () from /usr/lib/libQt5Core.so.5
#2  0x7fafc311973a in KisTileDataSwapper::run (this=0x7fafc360ade0
<_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at
/run/media/raghu/Data/krita-build/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:97
#3  0x7fafba05db2d in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7fafb81d908c in start_thread () from /usr/lib/libpthread.so.0
#5  0x7fafb9402e1f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fafa11e7700 (LWP 21092)):
#0  0x7fafb93f891b in poll () from /usr/lib/libc.so.6
#1  0x7fafb4e59023 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fafb4e5913e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fafba2a66b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fafba24882b in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fafba05878e in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fafbda8d416 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7fafba05db2d in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fafb81d908c in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fafb9402e1f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fafc4d79dc0 (LWP 21090)):
[KCrash Handler]
#5  KisProcessingApplicator::applyCommand (this=this@entry=0x0,
command=command@entry=0x7faf1c0ac8d0,

[clazy] [Bug 389006] Asserts are triggered in debug build

[bugzilla_noreply]

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

ivan.donchevs...@qt.io changed:

   What|Removed |Added

Summary|Assert is triggered while   |Asserts are triggered in
   |level2 is selected  |debug build

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

[skrooge] [Bug 388955] Splitting Currency and Amount into separate columns

[bugzilla_noreply]

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

--- Comment #5 from dterr...@yahoo.com ---
Yes, the raw columns would be useful for me, with a separate column for the
currency code.

Somehow there seem to be extra characters in the non-raw columns with currency
values that do not show up under linux LibreOffice, but that turn into strange
symbols (�贈) under windows.

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

[okular] [Bug 351408] printing BROKEN - pdf files from publishers

[Michael Weghorn]

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

Michael Weghorn  changed:

   What|Removed |Added

 CC||m.wegh...@posteo.de

--- Comment #1 from Michael Weghorn  ---
@Amnon:

The given Dropbox URL does not work any more which makes it impossible to
reproduce the issue.

Does the problem still exist for you with current Okular versions?
If so, can yo please provide the files needed to reproduce this once again?

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

[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget

[Sebastian]

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

Sebastian  changed:

   What|Removed |Added

 CC||unr...@unterderbruecke.de

--- Comment #28 from Sebastian  ---
I can still confirm that this Bug exsists on actual KDE Neon. Changing to
slideshow increases CPU-Usage immediatley, going back to single image und
restart plasmashell solves the problem.

The same happends on Archlinux.

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

[KBibTeX] [Bug 388892] Formatting error when saving file ( switching " and } )

[Arnout Boelens]

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

--- Comment #2 from Arnout Boelens  ---
Created attachment 109901
  --> https://bugs.kde.org/attachment.cgi?id=109901=edit
Test bib file

I think I found a way to reproduce the problem.

* Open the attached test.bib file in kbibtex
* Edit element
* Remove the brackets around title
* Click OK
* Press control W
* Click save

When opening the file in a text editor the title now reads:

"{The dynamics ... fluid sheets"},

instead of:

"{The dynamics ... fluid sheets}",

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

[Discover] [Bug 389036] New: After installing a Flatpak version of an app, trying to launch the PackageKit version from Discover opens the Flatpak one instead

[Nate Graham]

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

Bug ID: 389036
   Summary: After installing a Flatpak version of an app, trying
to launch the PackageKit version from Discover opens
the Flatpak one instead
   Product: Discover
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

[Discover with the PackageKit, Snap, and Flatpak backends built from source in
KDE Neon]

1. Add Flathub as a Flatpak source
2. Install the Flathub version of Kdenlive
3. Switch sources and install the PackageKit version of Kdenlive
4. Click the Launch button to launch the PackageKit version of Kdenlive

Expected results:
- The PackageKit version opens

Actual results:
- The Flatpak version opens

Reproducibility:
Happens with other apps (also tried gedit), and with other Flatpak sources
(e.g. kdeapps). If a Flatpak version of a de-duplicated app is installed,
attempting to launch PackageKit version from Discover instead launches the
Flatpak version.

I can still launch the PackageKit version using Kicker/Kickoff, so it's not a
total disaster, but still, not a great thing considering that people will
probably launch apps from Discover fairly frequently after switching or
installing new versions.

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

[plasmashell] [Bug 389035] New: When multiple copies of an app are installed from different sources (e.g. distro package version and Flatpak version), make each version clear

[Nate Graham]

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

Bug ID: 389035
   Summary: When multiple copies of an app are installed from
different sources (e.g. distro package version and
Flatpak version), make each version clear
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: pointedst...@zoho.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 109900
  --> https://bugs.kde.org/attachment.cgi?id=109900=edit
Two copies of the same app, each one from a different source

See attached screenshot. I used Discover to install one copy of gedit from KDE
Neon's packaging, and another from Flathub. Kickoff doesn't offer any
distinction between the two, so it just looks weird and confusing, and I can't
tell which version is going to open when I click on one of the two entries.

Perhaps we could mark each with its version and source to help differentiate
them, e.g:
- gedit 3.18 (KDE Neon)
- gedit 3.26 (Flathub)

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

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[David Mattatall]

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

--- Comment #11 from David Mattatall  ---
Hi it's a 100% reproducible.

Just give me the steps and I'd be happy to follow (I can even build with
symbols if you need me too). I think gentoo allows that with a flag.

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

[krita] [Bug 389034] New: Incorrect behavior when painting beyond the top or left borders of the canvas

[Nicholas LaPointe]

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

Bug ID: 389034
   Summary: Incorrect behavior when painting beyond the top or
left borders of the canvas
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: nicholaslapoin...@gmail.com
  Target Milestone: ---

Created attachment 109899
  --> https://bugs.kde.org/attachment.cgi?id=109899=edit
Example image

Painting beyond the top or left borders of the canvas appears to produce a
dashed version of what was drawn, with a 128px spacing.
This seems to have broken at or around the time that multithreaded brushes were
added.

In the attached image, I drew lines that started on the canvas and ended
outside of it, then moved the layer down and to the right.

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

[digikam] [Bug 389031] Scanning collection for faces causes produces lots of OpenCV errors

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|Faces-Detection |Faces-Recognition

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

[krita] [Bug 384774] Using a custom Shortcut Scheme causes menus and buttons to be invisible

[Nicholas LaPointe]

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

Nicholas LaPointe  changed:

   What|Removed |Added

 CC||nicholaslapoin...@gmail.com

--- Comment #4 from Nicholas LaPointe  ---
*** Bug 387260 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 387260] Custom shortcuts are not loaded

[Nicholas LaPointe]

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

Nicholas LaPointe  changed:

   What|Removed |Added

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

--- Comment #4 from Nicholas LaPointe  ---


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

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

[krita] [Bug 388903] JJ: show pixel grid option is initialized the wrong way around

[Nicholas LaPointe]

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

Nicholas LaPointe  changed:

   What|Removed |Added

 CC||nicholaslapoin...@gmail.com

--- Comment #2 from Nicholas LaPointe  ---
I was going to try fixing this, but it worked for me (I tested git 2ab0991 on
one computer and krita-4.0.0-beta.1-x86_64.appimage on another).

That said, there are two circumstances where I can get this to occur:
* When OpenGL is disabled. (The pixel grid requires OpenGL, but the "Show Pixel
Grid" can still be enabled when OpenGL is disabled.)
* When toggling the "Show Pixel Grid" option and switching documents in certain
ways (see bug 389033; although the steps to have the grid disabled and the
checkbox enabled are a little different).

I'm going to assume that the second one doesn't apply here, but the first seems
like it might be a reasonable cause. Could you check if OpenGL is disabled for
me?

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

[plasmashell] [Bug 388765] Plasma crashes after hiding an icon in 'Status and Notifications'

[Brandon Watkins]

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

Brandon Watkins  changed:

   What|Removed |Added

 CC||bwa...@gmail.com

--- Comment #1 from Brandon Watkins  ---
I'm seeing the same behavior here. If I show/hide tray icons, plasma always
immediately crashes after clicking 'OK' to save the changes.

KDE 5.11.5
Manjaro Linux

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

[kwin] [Bug 374867] Impossible to reach screen edge if mouse cursor is moving fast

[Andreas Eckstein]

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

Andreas Eckstein  changed:

   What|Removed |Added

 CC||andreas.eckst...@gmx.net

--- Comment #9 from Andreas Eckstein  ---
I'm seeing this bug too, with the latest-and-greatest installed.

Software setup:
kde-frameworks 5.42
kde-plasma 5.11.95
libinput 1.9.4 (but also with 1.8.3)

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

[krita] [Bug 389033] New: "Show Pixel Grid" checkbox state can desync with multiple documents/views

[Nicholas LaPointe]

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

Bug ID: 389033
   Summary: "Show Pixel Grid" checkbox state can desync with
multiple documents/views
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: nicholaslapoin...@gmail.com
  Target Milestone: ---

The "checked" state of the "Show Pixel Grid" checkbox inside of the "View" menu
can be inaccurate when it is toggled in multiple documents or views.

(Steps assume that the pixel grid is already enabled, which it is by default)
1. Create two documents
2. Disable the pixel grid in one document
3. Switch documents. The pixel grid in this document will still be enabled, but
the checkbox is now unchecked.

I'd expect that the state of the checkbox would match the status of the pixel
grid on the view (versus the other alternative of the checkbox affecting all
views).

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

[frameworks-kxmlgui] [Bug 382358] Under Windows KDE Application configuration files must be stored in %APPDATA% not in %LOCALAPPDATA%

[Thomas Debesse]

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

--- Comment #6 from Thomas Debesse  ---
A quick lookup reveals many stuff in the whole kde tree uses
`QStandardPaths::DataLocation` (which returns `%LocalAppData%` as
`QStandardPaths::AppLocalDataLocation` does) or even
`QStandardPaths::GenericDataLocation` that does exactly the same (and some code
also uses %LocalAppData% directly) instead of `QStandardPaths::DataLocation`
that returns %AppData% (added in Qt 5.4) which is the only viable option.

As read there:
https://doc-snapshots.qt.io/qt5-dev/qstandardpaths.html

> QStandardPaths::DataLocation
> Returns the same value as AppLocalDataLocation. This enumeration value is 
> deprecated. Using AppDataLocation is preferable since on Windows, the roaming 
> path is recommended.

> QStandardPaths::AppDataLocation
> Returns a directory location where persistent application data can be stored. 
> This is an application-specific directory. To obtain a path to store data to 
> be shared with other applications, use QStandardPaths::GenericDataLocation. 
> The returned path is never empty. On the Windows operating system, this 
> returns the roaming path. This enum value was added in Qt 5.4.

I would said that on Windows using `AppDataLocation` is not only recommended
but required since other options (DataLocation, GenericDataLocation,
AppLocalDataLocation) return a directory designed to be local to a disposable
computer and to not be part of the user's profile. This directory is made to be
not be shared among multiple computers, to not be backed up and to be wiped
out. It's a bit like writing user's configuration in /temp: it's definitely not
a place to save user's configuration.

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

[frameworks-kxmlgui] [Bug 382358] Under Windows KDE Application configuration files must be stored in %APPDATA% not in %LOCALAPPDATA%

[Thomas Debesse]

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

--- Comment #5 from Thomas Debesse  ---
I confirm that bug also affects Krita, it's obiously a bug in a common
component!

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

[Discover] [Bug 389032] Discover crashed when pressing PageDown button

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[Discover] [Bug 386015] Discover crashes in QGuiApplicationPrivate::sendQWindowEventToQPlatformWindow() while searching

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||yu...@protonmail.com

--- Comment #4 from Aleix Pol  ---
*** Bug 389032 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 388504] Discover crashes prior to completing update process

[Aleix Pol]

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

--- Comment #5 from Aleix Pol  ---
A Discover crash cannot render the system unbootable, PackageKit will continue
working on the background (check with pkcon and pkmon).

Did you really compile it from sources?

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

[bindings] [Bug 388980] heaps of missing and broken libraries for TortoiseHg

[Scott Kitterman]

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

--- Comment #3 from Scott Kitterman  ---
OK.  That's nothing to do with pykde though, so you should either consult with
one of the relevant upstreams or with the Neon developers.

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

[bindings] [Bug 388980] heaps of missing and broken libraries for TortoiseHg

[Eddie]

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

--- Comment #2 from Eddie  ---
Thank you for a quick response.

I have successfully recompiled qscintilla2, however, Im still not being able to
build the python binding and run `TortoiseHg`.

First error:
It is asking to make sure I have `sip` available in PATH.

Upon trying to fix that up:
`sudo apt-get install sip-dev`

and tring again
`python configure.py`

it gives the following error:
`Error: Unable to create the C++ code.`

`python configure-old.py` doesn't work either.

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

[plasmashell] [Bug 389003] Date and time is not shown into calendar-clock widget if no Region is selected.

[Alejandro]

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

--- Comment #4 from Alejandro  ---
2 screenshots attached:

   * digital clock and calendar widges

   * no region (UTC) time.

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

[plasmashell] [Bug 389003] Date and time is not shown into calendar-clock widget if no Region is selected.

[Alejandro]

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

--- Comment #3 from Alejandro  ---
Created attachment 109898
  --> https://bugs.kde.org/attachment.cgi?id=109898=edit
no region selected in preferences (UTC)

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

[plasmashell] [Bug 389003] Date and time is not shown into calendar-clock widget if no Region is selected.

[Alejandro]

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

--- Comment #2 from Alejandro  ---
Created attachment 109897
  --> https://bugs.kde.org/attachment.cgi?id=109897=edit
digital clock widged

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

[kmymoney] [Bug 388700] Investment Transaction imported as buy, when change to reinvest dividend get missing assignment error

[Joe Byers]

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

--- Comment #2 from Joe Byers  ---
On 01/15/2018 03:40 PM, Ralf Habacker wrote:
> https://bugs.kde.org/show_bug.cgi?id=388700
>
> Ralf Habacker  changed:
>
> What|Removed |Added
> 
>   CC||ralf.habac...@freenet.de
>
> --- Comment #1 from Ralf Habacker  ---
> Just to be sure - I
>
> 1. created an investment account named invest
> 2. In the wizard I enabled creating of a security account which has been named
> 'invest (billing)'
> 3. I imported the appended qfx file into account 'invest'
> 4. Then I opened the ledger of  account 'invest' and saw 4 transactions
> 5. I double clicked on the second transaction (having note 'dividends', which 
> I
> think you are refering to) and changed the activity to 'Reinvest Dividend'
>
> Then I saw that I cannot save this transaction - can you confirm or are I am
> doing something different ?
>
Ralf,


1-4is what I did.  5 is new.  Did you enter the income category for 
dividend income or interest income, if not, then it will not save.

Joe

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

[dolphin] [Bug 388611] log polluted w/ 'Empty filename passed to function'

[Henrik Fehlauer]

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

--- Comment #12 from Henrik Fehlauer  ---
> Even after yesterdays update it is still [...] 5.41.0

Oops, in my comment I meant 5.41, not 5.42 – sorry for the confusion.

>> Let me know if you need help with that.
> Yes I do, definitely!

Great, I'll try to post a follow-along how I arrived at the Plasma fix and what
you need to install for that on Tumbleweed. Until that is done, you could read
a bit on Wikipedia and Stackoverflow about gdb, breakpoints and the difference
between a coredump and a backtrace, because I'll probably not be able to
explain all of those in detail in a comment on Bugzilla ;)

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

[Discover] [Bug 389032] New: Discover crashed when pressing PageDown button

[bugzilla_noreply]

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

Bug ID: 389032
   Summary: Discover crashed when pressing PageDown button
   Product: Discover
   Version: 5.10.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: yu...@protonmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.0-25-generic x86_64
Distribution: Ubuntu 17.10

-- Information about the crash:
- What I was doing when the application crashed:
Using PageDown button to browse list of applications in Discover Software
Center

The crash does not seem to be reproducible.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6f32200900 (LWP 3313))]

Thread 17 (Thread 0x7f6ede7fa700 (LWP 5093)):
#0  0x7f6f2d8e6ffd in __GI___libc_read (fd=51, buf=0x7f6ede7f9a90,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f6f268dd073 in  () at
/usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111
#2  0x7f6f2818a280 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f28145c4b in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6f28146110 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f6f2814627c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f6f2e22d49b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6f2e1d2e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f6f2dff23ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f6f2dff729d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f6f2a10a7fc in start_thread (arg=0x7f6ede7fa700) at
pthread_create.c:465
#11 0x7f6f2d8f7b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f6ed2130700 (LWP 5051)):
#0  0x7f6f2d8eb901 in __GI___poll (fds=0x7f6ec0002de0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f6f28146169 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6f2814627c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f2e22d49b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6f2e1d2e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6f2dff23ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6f2dff729d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6f2a10a7fc in start_thread (arg=0x7f6ed2130700) at
pthread_create.c:465
#8  0x7f6f2d8f7b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f6ed2931700 (LWP 5047)):
#0  0x7f6f2d8eb901 in __GI___poll (fds=0x7f6ebc0029e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f6f28146169 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6f2814627c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f2e22d49b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6f2e1d2e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6f2dff23ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6f2dff729d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6f2a10a7fc in start_thread (arg=0x7f6ed2931700) at
pthread_create.c:465
#8  0x7f6f2d8f7b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f6edc92b700 (LWP 5043)):
#0  0x7f6f28143036 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f6f281455db in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6f2814609b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f2814627c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6f2e22d49b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6f2e1d2e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6f2dff23ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6f2dff729d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f6f2a10a7fc in start_thread (arg=0x7f6edc92b700) at
pthread_create.c:465
#9  0x7f6f2d8f7b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7f6edd12c700 (LWP 5027)):
#0  0x7f6f2814579f in 

[kblackbox] [Bug 363660] Grid visibility is poor

[Albert Astals Cid]

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

--- Comment #9 from Albert Astals Cid  ---
As you see I commited your patch, i've also made two small follow up commits,
please comment if you disagree 

https://cgit.kde.org/kblackbox.git/commit/?id=1b137d305d3c898ae292ebb761f7dcb505c7c9a6
https://cgit.kde.org/kblackbox.git/commit/?id=9b100d33a36e79c92a19fdd612b4d371e5705a0f

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

[kblackbox] [Bug 363660] Grid visibility is poor

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kbl
   ||ackbox/cb6d38cadfc1225e164f
   ||596ce73bef4d35a8

--- Comment #8 from Albert Astals Cid  ---
Git commit cb6d38cadfc1225e164f596ce73bef4d35a8 by Albert Astals Cid, on
behalf of Kevin Price.
Committed on 15/01/2018 at 23:10.
Pushed by aacid into branch 'master'.

Added an option under the settings menu to enable a cursor under the mouse

Contains some tweaks by Albert Astals Cid (whitespaces et al)

M  +2-0kbbgraphicsitemball.cpp
M  +16   -1kbbgraphicsitemblackbox.cpp
M  +11   -4kbbgraphicsitemblackbox.h
M  +1-2kbbgraphicsitemcursor.h
M  +1-1kbblevelconfigurationpreview.cpp
M  +8-1kbbmainwindow.cpp
M  +1-1kbbmainwindow.h
M  +23   -2kbbscalablegraphicwidget.cpp
M  +4-0kbbscalablegraphicwidget.h
M  +4-1kblackboxui.rc

https://commits.kde.org/kblackbox/cb6d38cadfc1225e164f596ce73bef4d35a8

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

[digikam] [Bug 377072] Cannot read video metadata

[Nick Anderson]

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

Nick Anderson  changed:

   What|Removed |Added

 CC||nick+kde-bug-tracker@cmdln.
   ||org

--- Comment #2 from Nick Anderson  ---
(In reply to caulier.gilles from comment #1)
> Metadata from video is supported through Exiv2 shared library.
> 
> The Exiv2 0.25, the last stable have serious problems with video files. This
> feature is optional in Exiv2 and certainly disabled at compilation time by
> packager.
> 
> Next 0.26 (not yet released) will be better so far, and we use it in digiKam
> bundle as ApppImage for Linux. You can try 5.5.0 pre release with Exiv2 0.26
> here :
> 
> https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
> 
> Note : depending of video format, some files cannot be read by Exiv2 yet.
> Look in Exiv2 web site for details.
> 
> Gilles Caulier

With the 5.8.0 appimage should we expect video metadata and editing to work? I 
get errors about the file being of an unknown image type.


#+BEGIN_EXAMPLE
digikam.metaengine: Cannot load metadata from file   (Error # 11 :
VID_20160814_002328.mp4: The file contains data of an unknown image type
#END+EXAMPLE

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

[okular] [Bug 388854] Okular uses a very large amount of RAM for caching

[Nate Graham]

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

--- Comment #11 from Nate Graham  ---
Yes, I opened Okular with the document and left it open for a few hours. I
didn't observe any memory leak; usage was static. So I assumed that the
reporter was referring to memory consumed by actually using Okular.

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

[okular] [Bug 388854] Okular uses a very large amount of RAM for caching

[Albert Astals Cid]

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

--- Comment #10 from Albert Astals Cid  ---
(In reply to Albert Astals Cid from comment #9)
> Question since you changed the subject of the bug, have you verified that
> there is actually no memory bug?

memory bug -> memory leak

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

[okular] [Bug 388854] Okular uses a very large amount of RAM for caching

[Albert Astals Cid]

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

--- Comment #9 from Albert Astals Cid  ---
Question since you changed the subject of the bug, have you verified that there
is actually no memory bug?

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

[clazy] [Bug 388979] Allow to add classes to UnusedNonTrivialVariable::isInterestingType

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED
  Latest Commit||https://commits.kde.org/cla
   ||zy/3e2edaa8f7048b25f6a2b501
   ||c794043409eff524

--- Comment #2 from Sergio Martins  ---
Git commit 3e2edaa8f7048b25f6a2b501c794043409eff524 by Sergio Martins.
Committed on 15/01/2018 at 23:03.
Pushed by smartins into branch 'master'.

unused-non-trivial-variable: Add user blacklist and whitelist

You can now use CLAZY_UNUSED_NON_TRIVIAL_VARIABLE_WHITELIST to
set a comma separated list of user types which you want to warn on.

Conversly, if you disabled the whitelist via export
CLAZY_EXTRA_OPTIONS=unused-non-trivial-variable-no-whitelist
then you'll want a blacklist, that's the env variable
CLAZY_UNUSED_NON_TRIVIAL_VARIABLE_BLACKLIST, which also
accepts comma separated list.

M  +5-1src/checks/level0/README-unused-non-trivial-variable.md
M  +25   -1src/checks/level0/unused-non-trivial-variable.cpp
M  +2-0src/checks/level0/unused-non-trivial-variable.h
M  +5-2tests/unused-non-trivial-variable/config.json
M  +12   -1tests/unused-non-trivial-variable/main.cpp
M  +1-0tests/unused-non-trivial-variable/main.cpp.expected
M  +11   -0tests/unused-non-trivial-variable/no-whitelist.cpp

https://commits.kde.org/clazy/3e2edaa8f7048b25f6a2b501c794043409eff524

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

[kblackbox] [Bug 363660] Grid visibility is poor

[bugzilla_noreply]

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

--- Comment #7 from key...@gmail.com ---
Kevin Price.

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

[okular] [Bug 388854] Okular uses a very large amount of RAM for caching

[Nate Graham]

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

--- Comment #8 from Nate Graham  ---
If you don't see any problems with Okular's memory usage, then go ahead and
close the bug. No reason to leave it open if we don't intend to make any
changes.

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

[okular] [Bug 388854] Okular uses a very large amount of RAM for caching

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|CONFIRMED   |UNCONFIRMED

--- Comment #7 from Albert Astals Cid  ---
I don't agree this is a bug, so i'm removing the confirmed flag.

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

[okular] [Bug 388854] Okular uses a very large amount of RAM for caching

[Albert Astals Cid]

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

--- Comment #6 from Albert Astals Cid  ---
(In reply to Nate Graham from comment #5)
> Yes, but is the amount reasonable?

You have it available, do you prefer the memory to lay around being unused?

> 1.17 Gb RAM / 257 pages = 4.5 Mb per page, for a document that's only 3.2 Mb
> on disk. This PDF is mostly text and a few graphics.

First, what does it matter how much it takes on disk regarding to what the
actual representation will be? https://en.wikipedia.org/wiki/Zip_bomb

And second, we're caching the rendered pixmap, so yeah the file size matters
nothing against what file rendering caching will occupy.


> When I perform the same procedure in Evince, it tops out at 93 Mb and
> doesn't feel any slower. So Okular is using 11 times as much RAM for its
> caching, but doesn't seem notably faster.

Sure, but the page may have taken 3 minutes to render, do you really want to
add  code that decides whether to cache the rendered pixmap depending on how
much it took to render?

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

[skrooge] [Bug 388955] Splitting Currency and Amount into separate columns

[Stephane MANKOWSKI]

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

--- Comment #4 from Stephane MANKOWSKI  ---
Created attachment 109895
  --> https://bugs.kde.org/attachment.cgi?id=109895=edit
Result of copy paste

Hi,

I did a small correction to copy/paste the displayed values AND the raw values.
As you can see, this could be interesting for dates and values.

Do you think this could help you?
Regards.

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

[skrooge] [Bug 388955] Splitting Currency and Amount into separate columns

[Stephane MANKOWSKI]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[digikam] [Bug 389031] New: Scanning collection for faces causes produces lots of OpenCV errors

[Nick Anderson]

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

Bug ID: 389031
   Summary: Scanning collection for faces causes produces lots of
OpenCV errors
   Product: digikam
   Version: 5.8.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Detection
  Assignee: digikam-bugs-n...@kde.org
  Reporter: nick+kde-bug-trac...@cmdln.org
  Target Milestone: ---

Using the 5.8.0 appimage on Ubuntu 17.10 I get lots of OpenCV Errors when
scanning my collection for faces.

#+BEGIN_EXAMPLE
OpenCV Error: Bad argument (This LBPH model is not computed yet. Did you call
the train method?) in predict, file
/b/dktemp/digikam-v5.8.0/core/libs/facesengine/recognition-opencv-lbph/facerec_borrowed.cpp,
line 383
digikam.facesengine: cv::Exception:
/b/dktemp/digikam-v5.8.0/core/libs/facesengine/recognition-opencv-lbph/facerec_borrowed.cpp:383:
error: (-5) This LBPH model is not computed yet. Did you call the train method?
in function predict
#+END_EXAMPLE

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

[clazy] [Bug 388979] Allow to add classes to UnusedNonTrivialVariable::isInterestingType

[Sergio Martins]

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

--- Comment #1 from Sergio Martins  ---
Git commit e847520dcf734c384aa6607317133faa1d73eb86 by Sergio Martins.
Committed on 15/01/2018 at 22:42.
Pushed by smartins into branch 'master'.

unused-non-trivial-variable: Add option to disable the whitelist

Meaning it will warn for any unused non-trivial variable. This will
cause false-positives, such as RAII types, but still useful to run at least
once
on your code.

Do use it:
export CLAZY_EXTRA_OPTIONS=unused-non-trivial-variable-no-whitelist

Next will implement blacklist/whitelist support from env-variable

M  +4-0src/checks/level0/README-unused-non-trivial-variable.md
M  +31   -0src/checks/level0/unused-non-trivial-variable.cpp
M  +1-0src/checks/level0/unused-non-trivial-variable.h
M  +4-0tests/unused-non-trivial-variable/config.json
A  +62   -0tests/unused-non-trivial-variable/no-whitelist.cpp [License:
UNKNOWN]  *
A  +7-0tests/unused-non-trivial-variable/no-whitelist.cpp.expected

The files marked with a * at the end have a non valid license. Please read:
https://community.kde.org/Policies/Licensing_Policy and use the headers which
are listed at that page.


https://commits.kde.org/clazy/e847520dcf734c384aa6607317133faa1d73eb86

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

[clazy] [Bug 388979] Allow to add classes to UnusedNonTrivialVariable::isInterestingType

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |smart...@kde.org
 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1
   Severity|normal  |wishlist

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

[okular] [Bug 388854] Okular uses a very large amount of RAM for caching

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|A very big volume of RAM|Okular uses a very large
   ||amount of RAM for caching

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

[okular] [Bug 388854] A very big volume of RAM

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
Yes, but is the amount reasonable?

1.17 Gb RAM / 257 pages = 4.5 Mb per page, for a document that's only 3.2 Mb on
disk. This PDF is mostly text and a few graphics.

When I perform the same procedure in Evince, it tops out at 93 Mb and doesn't
feel any slower. So Okular is using 11 times as much RAM for its caching, but
doesn't seem notably faster.

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

[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[bugzilla_noreply]

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

--- Comment #29 from steffen.he...@gmail.com ---
I checked ssl version. Output looks similar for Unbuntu 16.04.3 and 17.04:

(Ubuntu 17.04) 
$ openssl version -a
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
platform: debian-amd64
options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx) 
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -g -O2
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack
-Wall -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM
-DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM
-DGHASH_ASM -DECP_NISTZ256_ASM
OPENSSLDIR: "/usr/lib/ssl"

(Ubuntu 16.04.3)
$ openssl version -a
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
platform: debian-amd64
options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) blowfish(idx)
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -g -O2
-fdebug-prefix-map=/build/openssl-w1gRN6/openssl-1.0.2g=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack
-Wall -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM
-DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM
-DGHASH_ASM -DECP_NISTZ256_ASM
OPENSSLDIR: "/usr/lib/ssl"

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

[kmymoney] [Bug 388906] KDE Language Settings window not showing

[bugzilla_noreply]

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

--- Comment #3 from trustno12...@gmail.com ---
The problem is that the GUI is in english by default. I try to change it to
other language, so I go to the menu Settings, I press "KDE Language Settings"
and nothing happens. No new windos or dialog. Nothing. So I can't change the
language because the language windows is not showing.
However, looking for a way to log the issues, I've found another option to
change languange in "Help" menu, "Switch Application". That one works ok, shows
a dialog with a list of language. If I select Spanish and reopen the
applicaiton, it is in Spanish.

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

[okular] [Bug 388854] A very big volume of RAM

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #4 from Albert Astals Cid  ---
Nate, how is this a bug?

There's 200 rendered pages to cache, so yes obviously okular uses memory.

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

[user-manager] [Bug 389030] New: Updating user password should also update KWallet password, or at least prompt to

[Nate Graham]

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

Bug ID: 389030
   Summary: Updating user password should also update KWallet
password, or at least prompt to
   Product: user-manager
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: kcontrol module
  Assignee: j...@jriddell.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

When you update your user password using the user-manager KCM, your KWallet
password isn't updated. So the next time KWallet asks for a password, you'll
repeatedly enter your new password in frustration before yuo figure out what
happened and try the old one.

It would be really nice if user-manager either updated your KWallet password
for you when you changed your user password, or else prompted you to do it or
something like that.

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

[digikam] [Bug 388345] AppImage MySQL connection issues

[Nick Anderson]

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

Nick Anderson  changed:

   What|Removed |Added

 CC||nick+kde-bug-tracker@cmdln.
   ||org

--- Comment #5 from Nick Anderson  ---
(In reply to Maik Qualmann from comment #1)
> In the AppImage localhost does not work as a server address. Use 127.0.0.1
> in the digiKam settings and you can connect to your local server.
> 
> Maik

Thanks. This worked for me.

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

[krita] [Bug 389025] invisible menu items

[Scott Petrovic]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
have you tried clearing your kritarc file. This is a settings file that is
shared between multiple Krita versions. There is something in the 3.x version
that is messing up 4.0

https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration

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

[kexi] [Bug 389029] Crash when table view containing combo boxes is re-used

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[kexi] [Bug 389029] Crash when table view containing combo boxes is re-used

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kex
   ||i/d98f53f12f0dec3660089b6e8
   ||b633ba62527e83b
   Version Fixed In||3.1.0

--- Comment #1 from Jarosław Staniek  ---
Git commit d98f53f12f0dec3660089b6e8b633ba62527e83b by Jaroslaw Staniek.
Committed on 15/01/2018 at 22:06.
Pushed by staniek into branch 'master'.

Fix possible crash when table view containing combo boxes is re-used
FIXED-IN:3.1.0

M  +2-5src/widget/dataviewcommon/kexidataawareobjectiface.cpp

https://commits.kde.org/kexi/d98f53f12f0dec3660089b6e8b633ba62527e83b

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

[digikam] [Bug 388977] Error during upgrading core database schema from v8 to v9

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Attachment #109887|0   |1
is obsolete||

--- Comment #4 from Maik Qualmann  ---
Created attachment 109894
  --> https://bugs.kde.org/attachment.cgi?id=109894=edit
dbconfig.xml

Small updated dbconfig.xml.

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

[gwenview] [Bug 388982] Main image view does not automatically refresh on file changes

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
What kind of modification? A rename, or an image edit (e.g. crop/resize)?

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

[kexi] [Bug 389029] Crash when table view containing combo boxes is re-used

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

   Severity|normal  |crash
 Ever confirmed|0   |1
   Target Milestone|--- |3.1
   Assignee|kexi-b...@kde.org   |stan...@kde.org
 Status|UNCONFIRMED |ASSIGNED

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

[kexi] [Bug 389029] New: Crash when table view containing combo boxes is re-used

[Jarosław Staniek]

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

Bug ID: 389029
   Summary: Crash when table view containing combo boxes is
re-used
   Product: kexi
   Version: 3.1 Alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tables
  Assignee: kexi-b...@kde.org
  Reporter: stan...@kde.org
CC: a...@piggz.co.uk, in...@fables.co.za
  Target Milestone: ---

Possible crash when table view containing combo boxes is re-used.

To reproduce:
- design a table with combo boxes referencing detail tables, e.g. 2 columns
- go to data view, add one record
- go to the designer and change the design by e.g. renaming one column
- go back to data view and try to add one record using the last combo box
- effect: crash because capacity of the new record's data is insufficient

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

[plasmashell] [Bug 389028] New: KDE randomly locks up

[bugzilla_noreply]

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

Bug ID: 389028
   Summary: KDE randomly locks up
   Product: plasmashell
   Version: 5.8.8
  Platform: Mint (Debian based)
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: bk...@gnu.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

This has gone on for a while through some revisions of KDE, so now I am
reporting it. It happens at random times, the only consistency is that browsers
are running Java script.

Symptoms:
* mouse works
* audio will continue until the buffered data are exhausted
* Nothing else apparently operates
* reboot hot keys do not work. Not even the power button signal to reboot.
(Hold it long enough and power gets pulled, but I'm trying to trigger an "init
6" or "init 0".)
* ssh does work and "init 4" followed by "init 5" will successfully restart the
desktop. Unfortunately, SSH is considered a security hole and it is a laborious
task to figure out how to re-enable it with each OS update.

In the end, I press "reset". There is a left over glitch in that the task bar
will not auto-hide and changing its setting does no good. After several
reboots, the task bar will go back to auto-hiding.



I would be more than happy to help diagnose the problem. I am willing to
re-enable ssh and ssh in to try to determine what is causing KDE to hang up.
Just tell me what you need me to do.  Thank you.

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

[krita] [Bug 388989] Configuration window too large in Hi-DPI mode

[bugzilla_noreply]

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

--- Comment #3 from gst...@zoho.com ---
(In reply to Alvin Wong from comment #2)
> Unfortunately, there is a limitation in Qt (the framework that Krita uses)
> that setting the scaling to 150% in Windows will cause the GUI to be scaled
> at 2x (rounded up to integer). There is an upstream task on making it
> better, so let's hope it gets to the next LTS release.
> https://bugreports.qt.io/browse/QTBUG-53022
> 
> The configuration window has been shrunken down on 4.0 beta 1, so it should
> be a bit better.
> 
> ---
> 
> There is an obscure way of overriding the scaling behaviour (ref:
> https://doc.qt.io/qt-5.9/highdpi.html#high-dpi-support-in-qt) by setting the
> environment variable `QT_SCALE_FACTOR` to `1.5`. If you haven't already
> tried it after reading the previous sentence, I suggest you don't touch it
> at all. (P.S. If you set the system-wide environment variable, it will
> affect other applications that use Qt, so I don't recommend changing that.)
> 
> (I did have the thoughts of adding an easily-accessible option for setting
> it or `QT_SCREEN_SCALE_FACTORS` from within Krita, but I fear it would cause
> confusion.)

Thank you for responding in such a timely manner!
I am very happy to hear that this is being worked on, as Krita otherwise works
flawlessly I'll stick to the stable release for now, attaching the Type Cover
whenever I need to make configuration changes is not so much of a burden.
2x scaling is otherwise just fine, so making the configuration window smaller
should do the trick.

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

[Breeze] [Bug 388984] regression: breeze icons 5.41.0 uncompilable

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kexi] [Bug 334584] Kexi crash in Table Designer when changing data type

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
 CC||stan...@kde.org

--- Comment #9 from Jarosław Staniek  ---
99% of chances that it's fixed in todays 3.1.0 Alpha (git) or even before. 

When you have chance to test the new version feel free to reopen this report if
needed or report other bugs.

Thanks.

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

[KScreen] [Bug 389016] [Wayland] Setting Primary Display thru the KScreen KCM does not save

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
Summary|Setting Primary Display |[Wayland] Setting Primary
   |thru the KScreen KCM does   |Display thru the KScreen
   |not save|KCM does not save

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

[kexi] [Bug 343897] Crash after changing of a query design after renaming tables

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from Jarosław Staniek  ---
99% of chances that it's fixed in todays 3.1.0 Alpha (git) or even before.
Currently KEXI requests closing dependent windows, so that also would include
closing the query design.

When you have chance to test the new version feel free to reopen this report if
needed or report other bugs.

Thanks.

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

[dolphin] [Bug 388887] View is slow to refresh when creating a file

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kexi] [Bug 365914] Crash when try to change the type of a field and then add data

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 CC||stan...@kde.org
   Version Fixed In||3.1.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Jarosław Staniek  ---
99% of chances that it's fixed in todays 3.1.0 Alpha (git) or even before. 

When you have chance to test the new version feel free to reopen this report if
needed or report other bugs.

Thanks.

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

[kexi] [Bug 371892] Kexi crashed when renaming a table

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #6 from Jarosław Staniek  ---
99% of chances that it's fixed in todays 3.1.0 Alpha (git) or even before. 

When you have chance to test the new version feel free to reopen this report if
needed or report other bugs.

Thanks.

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

[kexi] [Bug 371892] Kexi crashed when renaming a table

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

   Version Fixed In||3.1.0

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

[kblackbox] [Bug 363660] Grid visibility is poor

[Albert Astals Cid]

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

--- Comment #6 from Albert Astals Cid  ---
Can i have your full name for proper authorship attribution?

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

[kio-extras] [Bug 388922] Clicking arrow beside samba share expands them all on top level

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
Product|dolphin |kio-extras
  Component|panels: folders |default
   Assignee|dolphin-bugs-n...@kde.org   |plasma-b...@kde.org

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

[kdeconnect] [Bug 389010] devices cannot see eachother

[dSP]

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

--- Comment #1 from dSP  ---
possible duplicates:
#373327 (almost no information)
#359149 

359149 suggest that it doesn't work, if the network interface has a link-local
address (ipv6 beginning with fe80:). 

apparently[1] the link-local address is required when using ipv6 so I am trying
to disable ipv6 for my WLAN. 
Only way i found so far is to globally disable ipv6 through uncommenting the
appropriate line in /etc/modprobe.d/aliases.conf
will reboot to see the change and report on the outcome

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

[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[bugzilla_noreply]

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

--- Comment #28 from caulier.gil...@gmail.com ---
Well the solution is to not copy the ssl version from CentoS6 into the AppImage
bundle and let's the system wide library alone. A line to add somewhere here :

https://cgit.kde.org/digikam-software-compilation.git/tree/project/bundles/appimage/04-build-appimage.sh#n264

Gilles

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

[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[Maik Qualmann]

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

--- Comment #27 from Maik Qualmann  ---
My theory is that Google recognizes 2 different versions of SSL and therefore
rejects it. Once natively from the browser login to start the authorization and
once from the AppImage. As I said, just one theory, because one Ubuntu goes,
the other not.

Maik

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

[Discover] [Bug 388916] Install button doesn't disable or become something else during installation of Snap app

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Nate Graham  ---
Sorry, I hadn't realized that the work was done on the 5.12 branch, and I was
still building from master. I can confirm that the button works properly now.
Sorry for the noise!

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

[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[bugzilla_noreply]

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

--- Comment #26 from caulier.gil...@gmail.com ---
After a full update of Centos6, nothing has changed about the Openssl version
installed.

Gilles Caulier

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

[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[bugzilla_noreply]

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

--- Comment #25 from caulier.gil...@gmail.com ---
On Centos6, openSSL is at 1.0.1e-57.

Gilles Caulier

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

[kblackbox] [Bug 363660] Grid visibility is poor

[Albert Astals Cid]

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

--- Comment #5 from Albert Astals Cid  ---
As said i'm not really a kblackbox player, so can't give a hard answer, but
from looking at it i think we can at least enable it by default and if someone
really dislikes it, they can go an disable it.

I'll give a quick review to the patch and commit it if i don't think anything
wrong.

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

[ark] [Bug 388423] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem

[David Tonhofer]

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

--- Comment #3 from David Tonhofer  ---
It works if I deselect the "P7zip" plugin.

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

[ark] [Bug 388423] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem

[David Tonhofer]

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

--- Comment #2 from David Tonhofer  ---
Created attachment 109893
  --> https://bugs.kde.org/attachment.cgi?id=109893=edit
Plugins selected

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

[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[bugzilla_noreply]

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

--- Comment #24 from caulier.gil...@gmail.com ---
Probably the openssl from Centos6 is not updated since a while to build
AppImage.

As 5.8.0 is out, i will rebuild the whole Centos6 VM from scratch and update
all as well before to recompile all Qt5/KF5/DK.

Gilles Caulier

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

[okular] [Bug 388854] A very big volume of RAM

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1

--- Comment #3 from Nate Graham  ---
I can reproduce using Okular 1.1.3 and poppler 0.57.0. As I use the arrow key
to scroll all the way to the end of the document and back three times, Okular's
memory usage rapidly rises, topping out at 1.17 Gb.

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

[frameworks-kio] [Bug 388991] KDE Connect 1.2 segfaults/crashes.

[Albert Astals Cid]

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

--- Comment #10 from Albert Astals Cid  ---
David how reproducible is this for you?

Any chance you could get us a crash with more debug information?

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

[Breeze] [Bug 388810] "Tile windows by dragging them to the side of the screen" puts window borders off the screen edge

[Nate Graham]

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

--- Comment #10 from Nate Graham  ---
https://phabricator.kde.org/D9900

No strong feelings either, but I figured I'd open it up for discussion anyway
to see what folks think.

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

[KBibTeX] [Bug 387638] kbibtex for kde5 crashes at start in fc27

[Amaro]

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

--- Comment #7 from Amaro  ---
Hello Thomas

Thanks for the patch, it worked and compiled well with qoauth-qt5-devel and 

cmake -DKDE_INSTALL_QTPLUGINDIR:PATH=`qtpaths --plugin-dir`
-DCMAKE_INSTALL_PREFIX:PATH=`kf5-config --prefix` -DCMAKE_BUILD_TYPE=debug
../kbibtex


Best regards

Amaro

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

[kwin] [Bug 388969] Active Screen Corners and Edges - toggle checkbox and schortcut

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #3 from Martin Flöser  ---
Please leave the state of the wish. Reopening won't change anything.

Fact is: any X application has the possibility to ensure that it gets all mouse
events, be it through locking (as I mentioned in comment #1) or through
grabbing. If it does that the screen edges won't activate.

If the game play requires mouse interaction in each part of the window it needs
to ensure it. We are not going to add further config options or global
shortcuts to workaround application shortcomings.

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

[kmymoney] [Bug 388700] Investment Transaction imported as buy, when change to reinvest dividend get missing assignment error

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

 CC||ralf.habac...@freenet.de

--- Comment #1 from Ralf Habacker  ---
Just to be sure - I 

1. created an investment account named invest
2. In the wizard I enabled creating of a security account which has been named
'invest (billing)'
3. I imported the appended qfx file into account 'invest'
4. Then I opened the ledger of  account 'invest' and saw 4 transactions 
5. I double clicked on the second transaction (having note 'dividends', which I
think you are refering to) and changed the activity to 'Reinvest Dividend'

Then I saw that I cannot save this transaction - can you confirm or are I am
doing something different ?

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

[plasmashell] [Bug 389027] New: plasma crash while s2ream and resume

[Toralf Förster]

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

Bug ID: 389027
   Summary: plasma crash while s2ream and resume
   Product: plasmashell
   Version: 5.10.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: toralf.foers...@gmx.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)
 (Compiled from sources)
Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.14.13 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
I logged in into a resumed system (s2ram).
Then I saw the icon  in the systray

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

Thread 16 (Thread 0x7f91ceffd700 (LWP 14306)):
#0  0x7f922d4e8cf2 in futex_wait_cancelable (private=,
expected=0, futex_word=0x558e84930f44) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x558e84930ef0,
cond=0x558e84930f18) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x558e84930f18, mutex=0x558e84930ef0) at
pthread_cond_wait.c:655
#3  0x7f922e6ea1aa in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x558e84930ef0) at
thread/qwaitcondition_unix.cpp:143
#4  QWaitCondition::wait (this=, mutex=0x558e8414c840,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#5  0x7f91f9d138f0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f91f9d1a0a7 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f91f9d1284c in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f91f9d1a102 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f91f9d1284c in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f91f9d163a9 in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f922e6e99d0 in QThreadPrivate::start (arg=0x7f91dc003190) at
thread/qthread_unix.cpp:368
#12 0x7f922d4e19d3 in start_thread (arg=0x7f91ceffd700) at
pthread_create.c:456
#13 0x7f922df4caef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 15 (Thread 0x7f91cf7fe700 (LWP 14305)):
#0  0x7f922d4e8cf2 in futex_wait_cancelable (private=,
expected=0, futex_word=0x558e84930f44) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x558e84930ef0,
cond=0x558e84930f18) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x558e84930f18, mutex=0x558e84930ef0) at
pthread_cond_wait.c:655
#3  0x7f922e6ea1aa in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x558e84930ef0) at
thread/qwaitcondition_unix.cpp:143
#4  QWaitCondition::wait (this=, mutex=0x558e8414c840,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#5  0x7f91f9d138f0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f91f9d1a0a7 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f91f9d1284c in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f91f9d1a102 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f91f9d1284c in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f91f9d163a9 in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f922e6e99d0 in QThreadPrivate::start (arg=0x7f91d80033f0) at
thread/qthread_unix.cpp:368
#12 0x7f922d4e19d3 in start_thread (arg=0x7f91cf7fe700) at
pthread_create.c:456
#13 0x7f922df4caef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 14 (Thread 0x7f91d7fff700 (LWP 14304)):
#0  0x7f922d4e8cf2 in futex_wait_cancelable (private=,
expected=0, futex_word=0x558e84930f44) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x558e84930ef0,
cond=0x558e84930f18) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x558e84930f18, mutex=0x558e84930ef0) at
pthread_cond_wait.c:655
#3  0x7f922e6ea1aa in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x558e84930ef0) at
thread/qwaitcondition_unix.cpp:143
#4  QWaitCondition::wait (this=, mutex=0x558e8414c840,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#5  0x7f91f9d138f0 in

[plasmashell] [Bug 389026] New: Crashing when changing view mode

[bugzilla_noreply]

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

Bug ID: 389026
   Summary: Crashing when changing view mode
   Product: plasmashell
   Version: 5.11.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: idw.wis...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.5)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed: Had 2 tabs open with different
PDFs. They started in single page mode. I changed one to facing pages, when I
switched to the other PDF, the program freezes, crashes then reopens the
documents in facing pages

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

Thread 17 (Thread 0x7fcc8d7fa700 (LWP 5533)):
#0  0x7fcd7adf939d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fcd7bc3f00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fccb71ee42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fccb71f3479 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fccb71f34d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fccb71f0c83 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fcd7bc3db2d in  () at /usr/lib/libQt5Core.so.5
#9  0x7fcd7adf308c in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fcd7b545e1f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7fcc8dffb700 (LWP 5532)):
#0  0x7fcd7adf939d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fcd7bc3f00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fccb71ee42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fccb71f3479 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fccb71f34d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fccb71f34d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fccb71f34d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7fccb71f0c83 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#12 0x7fcd7bc3db2d in  () at /usr/lib/libQt5Core.so.5
#13 0x7fcd7adf308c in start_thread () at /usr/lib/libpthread.so.0
#14 0x7fcd7b545e1f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7fcc8e7fc700 (LWP 5531)):
#0  0x7fcd7adf939d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fcd7bc3f00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fccb71ee42f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fccb71f3479 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fccb71f34d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fccb71f34d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fccb71f34d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7fccb71ed924 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7fccb71f34d2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7fccb71ed924 in

[kmymoney] [Bug 388906] KDE Language Settings window not showing

[Ralf Habacker]

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

--- Comment #2 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #1)
> I you can see this dialog and you cannot select any language except spanish
> - this is a known bug in a library used by kmymoney.
To the more specific - you can select any language, but after restarting
kmymoney the gui language has not been changed ?

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

[KScreen] [Bug 389016] Setting Primary Display thru the KScreen KCM does not save

[Mike]

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

--- Comment #1 from Mike  ---
Just had a chance to check the X session and primary display is saving properly
there.  

So, under the X session, primary display is saved by the KCM, under Wayland
session, it is not.

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

[kipiplugins] [Bug 385363] Digikam crashes when authorizing access to Google photo

[Maik Qualmann]

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

--- Comment #23 from Maik Qualmann  ---
This problem only occurs with the AppImage. I have a theory. Which SSL version
use Ubuntu 17.04 4.10.0-42 generic and which Ubuntu 16.04.03 4.10.0-42 generic?

Maik

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

[kmymoney] [Bug 388906] KDE Language Settings window not showing

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||ralf.habac...@freenet.de

--- Comment #1 from Ralf Habacker  ---
You want to say kmymoney 4.8.1 is always uses a spanish gui, regardless what
you choosed in the language dialog ?

I rechecked this with 4.8.1.1 32 bit on a german translated Windows 10 and saw
the language dialog - you are sure, that did not see it ? 

I you can see this dialog and you cannot select any language except spanish -
this is a known bug in a library used by kmymoney.

If not please reopen this bug.

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

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