date:20180113

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

Bug ID: 388947
   Summary: Brushes work for a while, then randomly stopped.
   Product: krita
   Version: 3.3.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush Engine/Bristle
  Assignee: krita-bugs-n...@kde.org
  Reporter: artgrub...@gmail.com
  Target Milestone: ---

Created attachment 109855
  --> https://bugs.kde.org/attachment.cgi?id=109855=edit
Comp. & Krita specs.

I have been working on a drawing for a while, and suddenly I stopped being able
to make marks on my piece. It only affects the one canvas, if I open a new one
the problem fixes itself. This is inconvenient when trying to produce art. As
you can see below, I do not have OpenGL enabled.

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

[plasma-pa] [Bug 388766] Looks ugly with dark themes

2018-01-13 Thread David Rosca

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

--- Comment #2 from David Rosca  ---
https://phabricator.kde.org/D9784
https://phabricator.kde.org/D9785

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

[plasmashell] [Bug 388946] Creating new files dialog is minimized by defualt

2018-01-13 Thread Eike Hein

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

--- Comment #1 from Eike Hein  ---
The Task Manager doesn't minimize any windows. We need to assign this ticket
somewhere else.

Where do you open this dialog from?

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

[plasmashell] [Bug 388946] New: Creating new files dialog is minimized by defualt

2018-01-13 Thread RaitaroH

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

Bug ID: 388946
   Summary: Creating new files dialog is minimized by defualt
   Product: plasmashell
   Version: 5.11.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: raitarohik...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 109854
  --> https://bugs.kde.org/attachment.cgi?id=109854=edit
The rule.

When I try to create a new file, or a new folder (it can happen in other
applications I am sure), the filename/foldername dialog that appears in the
task manager is minimized EVERY TIME. It also is orange. At first I thought
that it didn't appear but it was just minimized.

I managed to fix the problem by adding the window rule you can see in the
description.

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

[digikam] [Bug 388898] Convert Tiff to PNG fails

2018-01-13 Thread Maik Qualmann

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

--- Comment #15 from Maik Qualmann  ---
Saving as PNG in the image editor also fails because the color management is
disabled. So we do not seem to use color management in BQM.

Maik

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

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-13 Thread Martin Flöser

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

--- Comment #20 from Martin Flöser  ---
yeah, that all makes sense. Fullscreenshot is taken in a different way, thus
the request problem is not hit.

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

[dolphin] [Bug 388945] New: Kmail send as attachment service menu doesn't work

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

Bug ID: 388945
   Summary: Kmail send as attachment service menu doesn't work
   Product: dolphin
   Version: 17.12.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: guptaprashant...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Using the dolphin service menu to send file as attachment doesn't work if kmail
is not running. Tried running 'kmail --attach ' from the terminal
throws a segfault if kmail isn't running.

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

[Discover] [Bug 387041] "Reason" and "Change Log" are identical

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

--- Comment #8 from Nate Graham  ---
I've submitted a patch based on advice and comments from PackageKit developers.
Basically, the ChangeLog field is the raw data used to synthesize the Updates
and UpdateText fields. So if we show those, we don't need to also show the text
in the ChangeLog field.

https://phabricator.kde.org/D9850

...At least, this is true in Debian-based distros. It would be great to get
some testing in a few non-Debian-based distros to make sure it doesn't regress
anything for anybody.

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

[Discover] [Bug 387041] "Reason" and "Change Log" are identical

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

Nate Graham  changed:

   What|Removed |Added

Summary|"Reason" and "Change Log"   |"Reason" and "Change Log"
   |are frequently identical|are identical

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

[Discover] [Bug 388944] New: Use Generic Icon for Missing App Icons

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

Bug ID: 388944
   Summary: Use Generic Icon for Missing App Icons
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: anditosan1...@gmail.com
  Target Milestone: ---

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

In the Application Addons results list, there are many applications that don't
have an icon to represent them. Instead Discover shows a white square. My
suggestion is to use a generic breeze icon that represents applications to
replace those images missing.

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

[kuser] [Bug 388943] New: Keep Consistent Shape to Represent User

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

Bug ID: 388943
   Summary: Keep Consistent Shape to Represent User
   Product: kuser
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: gyu...@freemail.hu
  Reporter: anditosan1...@gmail.com
  Target Milestone: ---

We have a couple of ways that we show a user's picture that would look better
and more consistent if they were all the same.

Kickoff shows the user in a square when you use an image instead of an avatar.
Kscreenlock uses the same image in a circle (because of the theme we use) and
in system settings the representation is in a square.

I am in favor of making all of these shapes circular. They are more inviting.

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

[Discover] [Bug 388942] New: Opening Review Scrolls Vertically Past Content

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

Bug ID: 388942
   Summary: Opening Review Scrolls Vertically Past Content
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: anditosan1...@gmail.com
  Target Milestone: ---

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

The review screen needs to stop at the bottom of its size and not go past all
the way up.

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

[Discover] [Bug 388941] New: Strange Visual Effect with Search Bar

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

Bug ID: 388941
   Summary: Strange Visual Effect with Search Bar
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: anditosan1...@gmail.com
  Target Milestone: ---

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

The search bar appears to have issues at the corners when placed against the
blue background on the main screen in Discover.

Do you see the white dots at each corner?

Expected behavior:

Search bar looks rounded at the corners without white dots completing the
square

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

[Discover] [Bug 385040] Discover crashes in QQuickItem::isVisible() when attempting to go to home page

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

Nate Graham  changed:

   What|Removed |Added

 CC||ado...@xaker.ru

--- Comment #7 from Nate Graham  ---
*** Bug 388879 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 388879] Discover crashes when typing filter in drawer while in submenu

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---


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

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

[dolphin] [Bug 388555] renamed file reclaims focus

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

--- Comment #6 from Nate Graham  ---
Thanks to Andreas, we have a potential patch that fixes the issue:
https://phabricator.kde.org/D9711

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

[dolphin] [Bug 388888] Renaming a file shouldn’t change focus if manually changed

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---


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

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

[dolphin] [Bug 388555] renamed file reclaims focus

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

Nate Graham  changed:

   What|Removed |Added

 CC||pe...@hack-libre.org

--- Comment #5 from Nate Graham  ---
*** Bug 38 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 387630] Discover Plasma Addons Possible Memory Leak

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

Nate Graham  changed:

   What|Removed |Added

 CC||lei...@leinir.dk
  Component|discover|KNewStuff Backend

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

[Discover] [Bug 387630] Discover Plasma Addons Possible Memory Leak

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

Nate Graham  changed:

   What|Removed |Added

 CC||trial...@protonmail.com

--- Comment #3 from Nate Graham  ---
*** Bug 388911 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 388911] Massive leaks when opening Plasma extensions->Wallpapers

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---


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

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

[Discover] [Bug 387805] Multiple additional sort options based on popularity, ratings, and quality

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

--- Comment #3 from Nate Graham  ---
Yes, exactly. That would basically be the current contents of the Home screen
(which I am hoping to rename to "Featured Apps":
https://phabricator.kde.org/D9868)

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

[Discover] [Bug 387805] Multiple additional sort options based on popularity, ratings, and quality

2018-01-13 Thread Jasem Mutlaq

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

Jasem Mutlaq  changed:

   What|Removed |Added

 CC||mutla...@ikarustech.com

--- Comment #2 from Jasem Mutlaq  ---
Lovely idea. I presume #1 is the same thing as "Editors Pick", correct?

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

[gwenview] [Bug 385242] Custom shortcut ESC can ostensibly be set, but will not work

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

--- Comment #1 from andydecle...@gmail.com ---
No change as far as 17.12.1. I am disappointed that the unrelated fix that
introduced this bug was accepted, as I quit gwenview more often than I crop.

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

[Falkon] [Bug 388940] New: Option to add spacers and/or separators to the toolbar

2018-01-13 Thread Kishore Gopalakrishnan

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

Bug ID: 388940
   Summary: Option to add spacers and/or separators to the toolbar
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: kishor...@gmail.com
  Target Milestone: ---

When we click right click on the toolbar and click 'configure toolbar', we get
a list of items to add / remove from the toolbar. Separators and/or spacers
would be a good addition to this list, in order to allow better organisation of
the toolbar items.

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

[plasmashell] [Bug 388939] plasmashell 5.11.5 segfaults every couple of minutes

2018-01-13 Thread Phr33d0m

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

--- Comment #1 from Denis M. (Phr33d0m)  ---
Here's additional information running plasmashell through gdb manually:

(gdb) bt full
#0  0x in  ()
#1  0x71d45b29 in QMetaObject::cast(QObject const*) const () at
/usr/lib/libQt5Core.so.5
#2  0x75302f70 in  () at /usr/lib/libKF5XmlGui.so.5
#3  0x71d3bd5c in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#4  0x72d40e7a in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#5  0x72d48816 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#6  0x71d3c1e0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#7  0x71d3ee46 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#8  0x71d990a4 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fffebcf8e98 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#10 0x7fffebcf90e1 in  () at /usr/lib/libglib-2.0.so.0
#11 0x7fffebcf916e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#12 0x71d98691 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#13 0x7fffe3f6d282 in  () at /usr/lib/libQt5XcbQpa.so.5
#14 0x71d3a82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#15 0x71d43b18 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#16 0x5556f8d8 in  ()
#17 0x71382f4a in __libc_start_main () at /usr/lib/libc.so.6
#18 0x5556fc9a in _start ()

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

[plasmashell] [Bug 388939] New: plasmashell 5.11.5 segfaults every couple of minutes

2018-01-13 Thread Phr33d0m

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

Bug ID: 388939
   Summary: plasmashell 5.11.5 segfaults every couple of minutes
   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: g...@politeia.in
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: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
It does not matter if I'm working with my computer or watching it accross the
hall. It just crashes every couple of minutes with a segfault.

The crash can be reproduced every time.

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

Thread 13 (Thread 0x7ffefbdef700 (LWP 1698)):
#0  0x70d0b39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x71b5100c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x759929ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x75992e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x71b4fb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x70d0508c in start_thread () at /usr/lib/libpthread.so.0
#6  0x71457e1f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fff1497e700 (LWP 1697)):
#0  0x70d0b39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x71b5100c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x759929ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x75992e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x71b4fb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x70d0508c in start_thread () at /usr/lib/libpthread.so.0
#6  0x71457e1f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fff1566c700 (LWP 1602)):
#0  0x70d0b39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x71b5100c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x759929ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x75992e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x71b4fb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x70d0508c in start_thread () at /usr/lib/libpthread.so.0
#6  0x71457e1f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7fff1733a700 (LWP 1586)):
#0  0x70d0b39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x71b5100c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x759929ca in  () at /usr/lib/libQt5Quick.so.5
#3  0x75992e54 in  () at /usr/lib/libQt5Quick.so.5
#4  0x71b4fb2d in  () at /usr/lib/libQt5Core.so.5
#5  0x70d0508c in start_thread () at /usr/lib/libpthread.so.0
#6  0x71457e1f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fff1dd78700 (LWP 1562)):
#0  0x71d98283 in  () at /usr/lib/libQt5Core.so.5
#1  0x7fffebcf8579 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fffebcf8f7e in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fffebcf916e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x71d986b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x71d3a82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x71b4a78e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x71b4fb2d in  () at /usr/lib/libQt5Core.so.5
#8  0x70d0508c in start_thread () at /usr/lib/libpthread.so.0
#9  0x71457e1f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fff305a5700 (LWP 1359)):
#0  0x77ffa969 in  ()
#1  0x77ffac20 in clock_gettime ()
#2  0x714656e6 in clock_gettime () at /usr/lib/libc.so.6
#3  0x71d97fa2 in  () at /usr/lib/libQt5Core.so.5
#4  0x71d9673a in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#5  0x71d96d16 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#6  0x71d983ff in  () at /usr/lib/libQt5Core.so.5
#7  0x7fffebcf8579 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#8  0x7fffebcf8f7e in  () at /usr/lib/libglib-2.0.so.0
#9  0x7fffebcf916e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#10 0x71d986b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#11 0x71d3a82b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#12

[digikam] [Bug 388936] User Selectable Thumbnail Format

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

--- Comment #3 from caulier.gil...@gmail.com ---
>One use case that I can think of (and am currently working on, as a personal 
>project), >is that the I'd like to be able to use my Digikam database on other 
>platforms (say my >Android phone, or via HTTP), so I have been working on a 
>PHP frontend of sorts. 

I recommend to take a look to the new database sharing feature introduced with
5.8.0 based on DLNA/UPNP. you have plenty of application under Android that
permit to read digiKam database without to reinvent the wheel. DLNA and UPNP
are standardized and sound adapted for your use.

Gilles Caulier

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

[digikam] [Bug 388936] User Selectable Thumbnail Format

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

--- Comment #2 from aer...@aerysl.net ---
(In reply to caulier.gilles from comment #1)
> Can you give me a very good reason to provide a way to change the database
> image format in thumbnail database ?
> 
> - PGF is used because it use wavelets compression to optimize space,
> quality, speed.
> - the other format support provided in digiKam core for thumbs database is
> present for testing only. It's a legacy of test done many years ago when we
> choose the right one.
> - there is currently no mechanism to detect the thumb format stored in DB.
> including this king of control will slow down the thumb extraction, and we
> won't to complex this task.
> 
> For me PGF is prefect and there is no reason to changes it. The only
> possible way to change the format id to use a new compression which provide
> a better optimisation than PGF. Perhaps HEIF, WepP, or JPEGXR, but none
> provide an easy to use through a small library under Linux as PGF. There are
> also patents problem in background...
> 
> Gilles Caulier

One use case that I can think of (and am currently working on, as a personal
project), is that the I'd like to be able to use my Digikam database on other
platforms (say my Android phone, or via HTTP), so I have been working on a PHP
frontend of sorts. As such I have done local builds with JPEG thumbnails
(simply changing the previously mentioned line, and regenerating all my
thumbnails), so I can directly serve the thumbnails in the database extremely
quickly. I imagine others may find this useful, but it is a pretty niche case.

I definitely agree with PGF being a great format for use within Digikam, but
unfortunately I could not find many other libraries to interface with them.

I'm using the MySQL (MariaDB) backend, but it appears to me the "type" field in
the "Thumbnails" table corresponds with the type - and have had success using
JPEG based thumbnails. However, I am completely ignorant of how performant this
is, and any other considerations involved, and my observations may be
completely incorrect.

Thanks

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

[krita] [Bug 388938] Segmentation fault by moving text on a duplicated layer (Krita_4.0.0-beta1.1)

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

--- Comment #1 from mvowada  ---
Created attachment 109850
  --> https://bugs.kde.org/attachment.cgi?id=109850=edit
(GDB report)

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

[krita] [Bug 388938] Segmentation fault by moving text on a duplicated layer (Krita_4.0.0-beta1.1)

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

mvowada  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[krita] [Bug 388938] New: Segmentation fault by moving text on a duplicated layer (Krita_4.0.0-beta1.1)

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

Bug ID: 388938
   Summary: Segmentation fault by moving text on a duplicated
layer (Krita_4.0.0-beta1.1)
   Product: krita
   Version: 4.0.0-beta.1
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: freebo...@tiscali.it
  Target Milestone: ---

Created attachment 109849
  --> https://bugs.kde.org/attachment.cgi?id=109849=edit
(Video example)

(Ubuntu 14.04 - Krita 4.0.0-beta1.1.appimage)

I'm getting a Segmentation fault by moving text on a duplicated layer (see
video). Steps:

1) create text
2) duplicate the layer
3) using the "Select Shapes Tool" try to move the text on the duplicated
layer

Actual Results: crash
Expected Results: just move the layer

-- 
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%

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

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

   What|Removed |Added

Version|5.6.0   |unspecified

-- 
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%

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

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

   What|Removed |Added

Product|digikam |frameworks-kxmlgui
   Assignee|digikam-bugs-n...@kde.org   |kdelibs-b...@kde.org
  Component|Setup-ConfigFiles   |general
Summary|Windows: configuration must |Under Windows KDE
   |be stored in %APPDATA% not  |Application configuration
   |in %LOCALAPPDATA%   |files must be stored in
   ||%APPDATA% not in
   ||%LOCALAPPDATA%

--- Comment #4 from caulier.gil...@gmail.com ---
It's a bug in common component from KDE library : KF5::KXMLGUI our KConfig, i'm
not 100% sure. I forward to KDE core team for analyze.

Gilles Caulier

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

[digikam] [Bug 388936] User Selectable Thumbnail Format

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Can you give me a very good reason to provide a way to change the database
image format in thumbnail database ?

- PGF is used because it use wavelets compression to optimize space, quality,
speed.
- the other format support provided in digiKam core for thumbs database is
present for testing only. It's a legacy of test done many years ago when we
choose the right one.
- there is currently no mechanism to detect the thumb format stored in DB.
including this king of control will slow down the thumb extraction, and we
won't to complex this task.

For me PGF is prefect and there is no reason to changes it. The only possible
way to change the format id to use a new compression which provide a better
optimisation than PGF. Perhaps HEIF, WepP, or JPEGXR, but none provide an easy
to use through a small library under Linux as PGF. There are also patents
problem in background...

Gilles Caulier

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

[digikam] [Bug 388898] Convert Tiff to PNG fails

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

--- Comment #14 from caulier.gil...@gmail.com ---
Philipe, cab you confirm that you can covert this TIFF to PNG under Image
editor ?

Gilles Caulize

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

[digikam] [Bug 388898] Convert Tiff to PNG fails

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

--- Comment #13 from caulier.gil...@gmail.com ---
Maik, is right. Your ICC color profile break the libpng in background while
integrating it to the dedicated PNG chunk.

But the question is : why BQM has a problem to run conversion from tiff to png,
and editor no ?

Gilles Caulier

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

[kwin] [Bug 388889] Kwin crash when I open Kdevelop or Ark

2018-01-13 Thread Vincent Girès

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

--- Comment #2 from Vincent Girès  ---
Sorry, I made a mistake, it was a plasmashell bug related, I reported it here:
https://bugs.kde.org/show_bug.cgi?id=388937

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

[plasmashell] [Bug 388937] plasmashell crash when I open Kdevelop or Ark

2018-01-13 Thread Vincent Girès

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

Vincent Girès  changed:

   What|Removed |Added

   Platform|Other   |Neon Packages

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

[plasmashell] [Bug 388937] New: plasmashell crash when I open Kdevelop or Ark

2018-01-13 Thread Vincent Girès

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

Bug ID: 388937
   Summary: plasmashell crash when I open Kdevelop or Ark
   Product: plasmashell
   Version: 5.11.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: vincent.gi...@gmail.com
  Target Milestone: 1.0

plasmashell crash with some KDE application (Ark and Kdevelop, maybe other?)
since updates from the last days.
It starts again with "kstart plasmashell".

Here is the plasmashell-20180113-122033.kcrash.txt that was generated:

Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f823c5998c0 (LWP 1434))]

Thread 18 (Thread 0x7f813b7fe700 (LWP 2670)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f823636965b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f8174d4380f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f8174d478e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f8174d429ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f8174d47942 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f8174d429ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f8174d47942 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f8174d429ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f8174d45460 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f8236368709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f823520f6ba in start_thread (arg=0x7f813b7fe700) at
pthread_create.c:333
#12 0x7f8235c773dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7f813bfff700 (LWP 2669)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f823636965b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f8174d4380f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f8174d478e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f8174d429ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f8174d47942 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f8174d429ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f8174d45460 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f8236368709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f823520f6ba in start_thread (arg=0x7f813bfff700) at
pthread_create.c:333
#10 0x7f8235c773dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f8148b72700 (LWP 2668)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f823636965b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f8174d4380f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f8174d478e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f8174d429ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f8174d47942 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f8174d429ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f8174d47942 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f8174d429ed in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f8174d45460 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f8236

[digikam] [Bug 388936] New: User Selectable Thumbnail Format

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

Bug ID: 388936
Summary: User Selectable Thumbnail Format
Product: digikam
Version: unspecified
Platform: Other
OS: All
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: Database-Thumbs
Assignee: digikam-bugs-n...@kde.org
Reporter: aer...@aerysl.net
Target Milestone: ---

Currently behind the scenes Digikam supports a number of different
filetypes(https://cgit.kde.org/digikam.git/tree/libs/database/thumbsdb/thumbsdb.h?id=adbe3e2c132c4ffbf17bdffc2e14aaa91868ca18)
for the thumbnails to be stored within the database. However, while the
pipeline has the required code for all the types, the hardcoded default is PGF
(https://cgit.kde.org/digikam.git/tree/libs/threadimageio/thumbnailcreator.cpp?id=adbe3e2c132c4ffbf17bdffc2e14aaa91868ca18
- line 737). I propose that the thumbnail type be user selecteble. I imagine
this could be done in one of many ways, three of which I describe:

1. As an setting in the digikamrc config file. This would likely require less
work, but to maintain a consistent thumbnail type would require all Digikam
clients accessing the same database to have the same setting in the config.

2. Add the type as a setting in the Setting table of the database. This would
allow all clients accessing the database to use the same type, allowing a
homogenous thumbnail database of user configurable type.

3. A much less elegant solution would be to add a compile-time option to set
the dbInfo.type variable.

I'm not terribly familiar with the coding of Digikam, but if a Contributer
thinks option 1 is the way to go I should be able to make a patch to submit.

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

[digikam] [Bug 388936] User Selectable Thumbnail Format

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

aer...@aerysl.net changed:

   What|Removed |Added

 CC||aer...@aerysl.net

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

[kmymoney] [Bug 388935] New: Unable to import investment account transaction with .csv

2018-01-13 Thread wgking99

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

Bug ID: 388935
   Summary: Unable to import investment account transaction with
.csv
   Product: kmymoney
   Version: 4.8.1
  Platform: Mint (Debian based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: wgkin...@yahoo.com
  Target Milestone: ---

Created attachment 109848
  --> https://bugs.kde.org/attachment.cgi?id=109848=edit
1 line test file for investment transaction import

When trying to import investment transactions from brokerage as .csv file,
import fails after mapping fields with popup "The values in the columns you
have selected do not match any expected investment type", and all other types
from the drop down menu are grayed out. It even fails after modifying .csv file
to use sample type in the Merrill Lynch template in the csvimporterrc file.
Since option to reassign type are all grayed out (another issue?), the only
option is to abort the import. 

The proper action in the sample case would be to recognize "dividend" as a
valid brokerage transaction and deposit the amount in the "brokerage" account
of the corresponding investment account. The error occurs before  the
investment account is selected. The csvimporterrc template is the default M-L
one with the columns mapped as follows:
[BankProfiles]
BankNames=Merril Lynch,Schwab
PriorInvProfile=Merril Lynch

[MainWindow]
Height=174
Width=866

[Profiles-Merril Lynch]
AmountCol=7
BrokerageParam=Bill Payment,Check,dividend,interest,qualified div,foreign tax
paid,adr mgmt fee
BuyParam=buy
DateCol=1
DateFormat=2
DecimalSymbol=0
DetailCol=9
DivXParam=Dividend
Encoding=0
FeeCol=6
FieldDelimiter=0
FileType=Invest
Filter=
IntIncParam=Interest,Income
InvDirectory=~/
MemoCol=2
PayeeCol=3
PriceCol=5
PriceFraction=2
ProfileName=Merril Lynch
QuantityCol=4
ReinvdivParam=reinvest,Reinv,Re-inv,ReInv
RemoveParam=Remove
SecurityName=-1
SellParam=Sell,Repurchase
ShrsinParam=Add,Stock Dividend,Divd Reinv,Transfer In,Re-Registration
In,Journal Entry
StartLine=0
SymbolCol=8
TrailerLines=0

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

[plasmashell] [Bug 388934] New: KDE Application Launcher is Crashing Plasma

2018-01-13 Thread jmdkde

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

Bug ID: 388934
   Summary: KDE Application Launcher is Crashing Plasma
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: dupre...@gmail.com
  Target Milestone: 1.0

Created attachment 109847
  --> https://bugs.kde.org/attachment.cgi?id=109847=edit
ksmserver (ksmserver), signal: Segmentation fault

seems like
* https://bugs.kde.org/show_bug.cgi?id=388477
* https://bugs.kde.org/show_bug.cgi?id=387562

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

[frameworks-kactivities-stats] [Bug 387562] plasmashell crash after click on Application Launcher

2018-01-13 Thread jmdkde

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

jmdkde  changed:

   What|Removed |Added

 CC||dupre...@gmail.com

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

[plasmashell] [Bug 388901] Plasmashell segfaulting regularly

2018-01-13 Thread Antonio Rojas

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org

--- Comment #4 from Antonio Rojas  ---
As a workaround, remove the updates applet

Backtrace with debug symbols:
#0  0x71d36b97 in QMetaObject::cast(QObject const*) const
(this=0x7340e380 , obj=obj@entry=0x7fffdc016150)
at kernel/qmetaobject.cpp:366
#1  0x71d36bd6 in QMetaObject::cast(QObject*) const (this=, obj=obj@entry=0x7fffdc016150) at kernel/qmetaobject.cpp:355
#2  0x752f9f70 in qobject_cast(QObject*)
(object=0x7fffdc016150) at /usr/include/qt/QtCore/qobject.h:514
#3  0x752f9f70 in KActionConflictDetector::eventFilter(QObject*,
QEvent*) (this=0x558872c0, watched=0x7fffdc016150, event=0x59afa410)
at /build/kxmlgui/src/kxmlgui-5.42.0/src/kactionconflictdetector.cpp:44
#4  0x71d2cdcc in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
(this=this@entry=0x558237f0, receiver=receiver@entry=0x7fffdc016150,
event=event@entry=0x59afa410) at kernel/qcoreapplication.cpp:1152
#5  0x72d37f0a in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x558237f0, receiver=receiver@entry=0x7fffdc016150,
e=e@entry=0x59afa410) at kernel/qapplication.cpp:3707
#6  0x72d3f8a6 in QApplication::notify(QObject*, QEvent*)
(this=0x7fffe480, receiver=0x7fffdc016150, e=0x59afa410)
at kernel/qapplication.cpp:3491
#7  0x71d2d250 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x7fffdc016150, event=event@entry=0x59afa410)
at kernel/qcoreapplication.cpp:1044
#8  0x71d2feb6 in QCoreApplication::sendEvent(QObject*, QEvent*)
(event=0x59afa410, receiver=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#9  0x71d2feb6 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x55818fe0) at kernel/qcoreapplication.cpp:1719
#10 0x71d3044a in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=receiver@entry=0x0, event_type=event_type@entry=0)
at kernel/qcoreapplication.cpp:1573
#11 0x71d8a114 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55887020) at kernel/qeventdispatcher_glib.cpp:276
#12 0x7fffe9f3be68 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#13 0x7fffe9f3c0b1 in  () at /usr/lib/libglib-2.0.so.0
#14 0x7fffe9f3c13e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#15 0x71d89701 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55887650, flags=...)
at kernel/qeventdispatcher_glib.cpp:423
#16 0x7fffe3d55a52 in
QPAEventDispatcherGlib::processEvents(QFlags)
(this=0x55887650, flags=...)
at qeventdispatcher_glib.cpp:69
#17 0x71d2b89b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fffe380, flags=..., flags@entry=...)
at kernel/qeventloop.cpp:212
#18 0x71d34b88 in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1332
#19 0x5556f8d8 in  ()
#20 0x71371f4a in __libc_start_main () at /usr/lib/libc.so.6
#21 0x5556fc9a in _start ()

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

[klines] [Bug 388923] KLines is missing metadata

2018-01-13 Thread Albert Astals Cid

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
https://phabricator.kde.org/D9864

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

[plasmashell] [Bug 388920] Plasmashell coredump

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

jlhyo...@bigpond.com changed:

   What|Removed |Added

 CC||jlhyo...@bigpond.com

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

[plasmashell] [Bug 388901] Plasmashell segfaulting regularly

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

jlhyo...@bigpond.com changed:

   What|Removed |Added

 CC||jlhyo...@bigpond.com

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

[Discover] [Bug 388734] All Snap apps list size as "0 B"

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

Nate Graham  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #2 from Nate Graham  ---
Verified, thanks!

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

[Discover] [Bug 388933] Add subcategories for Multimedia category (e.g. Audio players, Video players, Utilities & Converters, etc)

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[Discover] [Bug 388933] New: Add subcategories for Multimedia category (e.g. Audio players, Video players, Utilities & Converters, etc)

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

Bug ID: 388933
   Summary: Add subcategories for Multimedia category (e.g. Audio
players, Video players, Utilities & Converters, etc)
   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: ---

The "Multimedia" category is gigantic, and encompasses so many different kinds
of apps that it's almost impossible to find anything there by browsing.

Because of the huge diversity of Multimedia apps, I propose adding
sub-categories:
- Audiobooks
- Audio Editors
- Audio Players
- Camera & Screenshots
- CD & DVD
- Video Editors
- Video Players
- Utilities & Converters

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

[kontact] [Bug 388932] New: Kontact segfaults at restart of the program with dataloss

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

Bug ID: 388932
   Summary: Kontact segfaults at restart of the program with
dataloss
   Product: kontact
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: staka...@freenet.de
  Target Milestone: ---

Application: kontact (5.5.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.104-39-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
When I open kontakt for a second time after having closed it the program
segafaults at start. Or when the system was unattended on another user for some
time and I come back to the one with kontakt active, try to check for mail.
This will hang. When shutting down the application Kontact segfaults. When
opening it again, then mail previously marked as read appear as unread, some
mails that where not there or were deleted reappear. akonadi fsck complains
about missing RID. (no RID or no RID and dirty). Konqui pops up but is not able
to create a backtrace. I started the program under gdb and was able to recover
the following:

-- Backtrace:
(gdb) thread apply all backtrace

Thread 33 (Thread 0x7fffc0db2700 (LWP 7747)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fffe816e9b2 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fffe817c3f6 in base::PosixDynamicThreadPool::WaitForTask() () from
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fffe817c5e6 in base::(anonymous
namespace)::WorkerThread::ThreadMain() () from
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fffe817631e in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7096a744 in start_thread (arg=0x7fffc0db2700) at
pthread_create.c:334
#6  0x749c9aad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 32 (Thread 0x7ffecf070700 (LWP 7745)):
#0  0x749c120d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffefd2d314 in g_main_context_poll (priority=2147483647, n_fds=3,
fds=0x7ffec0005a70, timeout=-1, context=0x7ffec00050b0) at gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7ffec00050b0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3835
#3  0x7fffefd2d42c in g_main_context_iteration (context=0x7ffec00050b0,
may_block=1) at gmain.c:3901
#4  0x754e518c in QEventDispatcherGlib::processEvents
(this=0x7ffec0004390, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#5  0x75492bfb in QEventLoop::exec (this=this@entry=0x7ffecf06fe50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:206
#6  0x752cdf5a in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x752d2a29 in QThreadPrivate::start (arg=0x1478cb0) at
thread/qthread_unix.cpp:365
#8  0x7096a744 in start_thread (arg=0x7ffecf070700) at
pthread_create.c:334
#9  0x749c9aad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 30 (Thread 0x7ffeb9ac3700 (LWP 5995)):
#0  0x749c120d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffefd2d314 in g_main_context_poll (priority=2147483647, n_fds=2,
fds=0x7ffeac003220, timeout=-1, context=0x7ffeac000990) at gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7ffeac000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3835
#3  0x7fffefd2d42c in g_main_context_iteration (context=0x7ffeac000990,
may_block=1) at gmain.c:3901
#4  0x754e518c in QEventDispatcherGlib::processEvents
(this=0x7ffeac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#5  0x75492bfb in QEventLoop::exec (this=this@entry=0x7ffeb9ac2e50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:206
#6  0x752cdf5a in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x752d2a29 in QThreadPrivate::start (arg=0x12ef860) at
thread/qthread_unix.cpp:365
#8  0x7096a744 in start_thread (arg=0x7ffeb9ac3700) at
pthread_create.c:334
#9  0x749c9aad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 29 (Thread 0x7ffeba2c4700 (LWP 5993)):
#0  0x749c120d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffefd2d314 in g_main_context_poll (priority=2147483647, n_fds=3,
fds=0x7ffeb4002e20, timeout=-1, context=0x7ffeb4000990) at gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7ffeb4000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3835
#3  0x7fffefd2d42c in g_main_context_iteration (context=0x7ffeb4000990,
may_block=1) at gmain.c:3901
#4  0x754e518c in QEventDispatcherGlib::processEvents

[plasmashell] [Bug 388749] Don't appear new thumbnails on first tooltips seance

2018-01-13 Thread Roman Gilg

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

--- Comment #4 from Roman Gilg  ---
Yes, this is a problem with the group / proxy / model behind it. In short my
believe is that a backend model change does not update the QML code reliable.

But this is a fragile area because there are other problems with it:
https://phabricator.kde.org/D7768

When I wrote the new tooltips I hacked around this problem after not being able
to write a proper solution for it for quite some time. I'm lacking the
understanding of the backend / proxy code in this regard.

If Eike has time at some point in the future we should try to tackle this
problem together.

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

[krita] [Bug 388931] softproof mode is always on

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
I cannot reproduce the first on KDE Neon 16.04, there must be something more
going on here.

And I have the opposite with the store softproofing toggle, I cannot turn it
on.

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

[calligracommon] [Bug 388930] Image cropping UI broken

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

sebpe  changed:

   What|Removed |Added

 CC||se...@mailbox.org

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

[krita] [Bug 388931] New: softproof mode is always on

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

Bug ID: 388931
   Summary: softproof mode is always on
   Product: krita
   Version: 4.0.0-beta.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Color models
  Assignee: krita-bugs-n...@kde.org
  Reporter: razvan...@yahoo.com
  Target Milestone: ---

View > Soft Proofing has no influence, if softproofing is changed in Image >
Properties dialog, that color mode is turned on no matter the View toggle. Also
can't switch off 'store softproofing configuration in the image', when you
toggle it off and press OK, if you open the image properties panel again, it's
still on.

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

[calligracommon] [Bug 388930] Image cropping UI broken

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

--- Comment #2 from sebpe  ---
Created attachment 109846
  --> https://bugs.kde.org/attachment.cgi?id=109846=edit
gray shape covering parts of the image cropping preview

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

[calligracommon] [Bug 388930] Image cropping UI broken

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

--- Comment #1 from sebpe  ---
Attachment description should be "gray shape covering the image cropping
preview at the bottom right"

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

[calligracommon] [Bug 388930] New: Image cropping UI broken

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

Bug ID: 388930
   Summary: Image cropping UI broken
   Product: calligracommon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: flake-picture
  Assignee: calligra-bugs-n...@kde.org
  Reporter: se...@mailbox.org
  Target Milestone: ---

Created attachment 109845
  --> https://bugs.kde.org/attachment.cgi?id=109845=edit
gray shape covering the image cropping preview at the bottom left

The Image Cropping UI on the "Picture editing" Tab of the general docker shows
some opaque grey shape instead of the the cropping borders.
Until the Top, Bottom, Left and Right cropping borders are not set to some
larger value using the spin boxes above, the shape will cover the entire image
preview.
Setting the cropping with the mouse still works but you have to spot the
handles blindly.

Steps to reproduce:
 - open an empty document in words
 - insert an image
 - go to the "Picture editing" tab
 - change the values of the Top, Bottom, Left and Right spin boxes

I can always reproduce this within words, sheets, stage and karbon using arch
(recent git-master) and (K)ubuntu (3.0.1).

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

[krita] [Bug 388929] New: Weird crash while drawing. [GDB backtrace]

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

Bug ID: 388929
   Summary: Weird crash while drawing. [GDB backtrace]
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com
  Target Milestone: ---

I was drawing with the "Basic_Chisel_Smooth", which is a pixel brush. Even
weirder, it is a pixel brush that does NOT have any of the airbrush features
turned on.

I had GDB turned on.

I have no idea what happened. I am therefore afraid it might be a race
condition with multi-threaded brushes.

KDE Neon based on Ubuntu 16.04, with Intuos 3, build from master.


Thread 183 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffb3fff700 (LWP 25080)]
0x75315b14 in QMapDataBase::rotateLeft(QMapNodeBase*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) thread apply all backtrace

Thread 183 (Thread 0x7fffb3fff700 (LWP 25080)):
#0  0x75315b14 in QMapDataBase::rotateLeft(QMapNodeBase*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x75315cec in QMapDataBase::rebalance(QMapNodeBase*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x75316254 in QMapDataBase::createNode(int, int, QMapNodeBase*,
bool) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fffd0c9ea55 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/styles/breeze.so
#4  0x7fffd0c83ce2 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/styles/breeze.so
#5  0x7fffd0cc2f54 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/styles/breeze.so
#6  0x7622657e in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x761e6b9c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x761ee5a7 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x77859ab7 in KisApplication::notify (this=,
receiver=0x7fffa409a940, 
event=0x7fffb3ffe410) at
/home/wolthera/krita/src/libs/ui/KisApplication.cpp:600
#10 0x75489df8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x76221ae9 in QWidget::ensurePolished() const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7622554c in QWidget::setVisible(bool) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
---Type  to continue, or q  to quit---
#13 0x7fffc4675fbe in KisAirbrushWidget::KisAirbrushWidget
(canIgnoreSpacing=true, parent=0x0, 
this=0x7fffa4056fb0)
at
/home/wolthera/krita/src/plugins/paintops/libpaintop/kis_airbrush_option.cpp:46
#14 KisAirbrushOption::KisAirbrushOption (this=0x7fffa40433d8,
enabled=, 
canIgnoreSpacing=)
at
/home/wolthera/krita/src/plugins/paintops/libpaintop/kis_airbrush_option.cpp:68
#15 0x7fffc41e0ef6 in KisBrushOp::KisBrushOp (this=0x7fffa40432c0,
settings=..., painter=
0xeb398d0, node=..., image=...)
at
/home/wolthera/krita/src/plugins/paintops/defaultpaintops/brush/kis_brushop.cpp:67
#16 0x7fffc41dca2b in KisSimplePaintOpFactory::createOp (this=,
settings=..., painter=0xeb398d0, node=..., image=...)
at
/home/wolthera/krita/src/plugins/paintops/libpaintop/kis_simple_paintop_factory.h:94
#17 0x72572a20 in KisPaintOpRegistry::paintOp (
this=this@entry=0x72a47940 <(anonymous
namespace)::Q_QGS_s_registryInstance::innerFunction()::holder>, id=...,
settings=..., painter=painter@entry=0xeb398d0, node=..., image=...)
at
/home/wolthera/krita/src/libs/image/brushengine/kis_paintop_registry.cc:104
#18 0x72572cca in KisPaintOpRegistry::paintOp (
this=0x72a47940 <(anonymous
namespace)::Q_QGS_s_registryInstance::innerFunction()::holder>, 
preset=..., painter=painter@entry=0xeb398d0, node=..., image=...)
at
/home/wolthera/krita/src/libs/image/brushengine/kis_paintop_registry.cc:120
#19 0x72556125 in KisPainter::setPaintOpPreset
(this=this@entry=0xeb398d0, preset=..., 
node=..., image=...) at
/home/wolthera/krita/src/libs/image/kis_painter.cc:2627
#20 0x77730b35 in KisResourcesSnapshot::setupPainter (this=0xeb3dd80, 
painter=painter@entry=0xeb398d0)
---Type  to continue, or q  to quit---
at /home/wolthera/krita/src/libs/ui/tool/kis_resources_snapshot.cpp:207
#21 0x777393ca in KisPainterBasedStrokeStrategy::initPainters
(this=this@entry=0xeb3a400, 
targetDevice=..., maskingDevice=..., selection=..., 
hasIndirectPainting=hasIndirectPainting@entry=true,
indirectPaintingCompositeOp=...)
at

[marble] [Bug 388928] New: MSVCP120.dll was not found

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

Bug ID: 388928
   Summary: MSVCP120.dll was not found
   Product: marble
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: jrd...@optusnet.com.au
  Target Milestone: ---

The code execution cannot proceed because MSVCP120.dll was not found.
Reinstalling the program may fix this problem.

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

[frameworks-kactivities-stats] [Bug 387562] plasmashell crash after click on Application Launcher

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

tux+kde...@warnetd.org changed:

   What|Removed |Added

 CC||tux+kde...@warnetd.org

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

[plasmashell] [Bug 388477] Plasma crashes when activating the Application Launcher

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

tux+kde...@warnetd.org changed:

   What|Removed |Added

 CC||tux+kde...@warnetd.org

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

[digikam] [Bug 388898] Convert Tiff to PNG fails

2018-01-13 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #12 from Maik Qualmann  ---
I see this error message in BQM:

digikam.dimg: Saving to 
"/daten/Bilder/Zugang/xx/BatchTool-fltmRu-2b5179bd.digikamtempfile.png"  with
format:  "PNG"
libpng error: known incorrect sRGB profile
digikam.dimg.png: Internal libPNG error during writing file. Process aborted!

And this in the image editor (but saved as PNG):

libpng warning: iCCP: profile 'ICC PROFILE': 58070020h: exceeds application
limits
libpng warning: iCCP: CRC error


Maik

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

[plasmashell] [Bug 388886] plasmashell crashed when trying to unminimize konsole

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

galla...@gmx.net changed:

   What|Removed |Added

 CC||galla...@gmx.net

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

[plasmashell] [Bug 388920] Plasmashell coredump

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

galla...@gmx.net changed:

   What|Removed |Added

 CC||galla...@gmx.net

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

[plasmashell] [Bug 388901] Plasmashell segfaulting regularly

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

galla...@gmx.net changed:

   What|Removed |Added

 CC||galla...@gmx.net

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

[plasmashell] [Bug 388902] Segfault while searching apps

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

galla...@gmx.net changed:

   What|Removed |Added

 CC||galla...@gmx.net

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

[krita] [Bug 388927] save incremental * crashes program if not use regular save beforehand

2018-01-13 Thread Boudewijn Rempt

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||b...@valdyas.org
 Ever confirmed|0   |1

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

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-13 Thread Altguard

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

--- Comment #19 from Altguard  ---
In addition, taking a full screen screenshot of both monitors at once does not
cause any issues - only the window screenshot.

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

[krita] [Bug 388927] New: save incremental * crashes program if not use regular save beforehand

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

Bug ID: 388927
   Summary: save incremental * crashes program if not use regular
save beforehand
   Product: krita
   Version: 4.0.0-beta.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: razvan...@yahoo.com
  Target Milestone: ---

On linux, Ubuntu 17.04 at least, both Save Incremental Version & Backup gives
an error if I don't save the file beforehand (the regular way with CTLR + S).

Save Incremental Version & Backup give the same error:
ASSERT (krita): "job.isValid()" in file
/krita-4.0.0.51/libs/ui/KisDocument.cpp, line 689
Aborted (core dumped)

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

[Discover] [Bug 388917] Can't browse through PackageKit source; page says "Sorry, nothing found..."

2018-01-13 Thread Aleix Pol

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

Aleix Pol  changed:

   What|Removed |Added

  Component|discover|PackageKit

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

[clazy] [Bug 388925] Segmentation fault in OldStyleConnect::fixits() calling Expr::getBestDynamicClassType()

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

--- Comment #3 from Tom Isaacson  ---
I can open the .crash file using apport-retrace:
(gdb) bt
#0  0x7fe406a22240 in getInterestingTagDecl(clang::TagDecl*) () from
/home/tom/Documents/clazy/lib/ClangLazy.so
#1  0x7fe406247685 in OldStyleConnect::fixits (this=0x643fea0,
classification=12, call=0x7f3) at
/home/big/Documents/BitBucket/clazy/src/checks/level2/oldstyleconnect.cpp:450
#2  0x7fe406245915 in OldStyleConnect::VisitStmt (this=0x643fea0,
s=0x7f3) at
/home/big/Documents/BitBucket/clazy/src/checks/level2/oldstyleconnect.cpp:215
#3  0x7fe406270a1e in ClazyASTConsumer::VisitStmt (this=0x43b1380,
stm=0x7f3) at /home/big/Documents/BitBucket/clazy/src/Clazy.cpp:139
#4  0x7fe4062d503a in
clang::RecursiveASTVisitor::WalkUpFromStmt (this=0x43b1380,
S=0x7f3) at /usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:320
#5  0x7fe4062d51f2 in
clang::RecursiveASTVisitor::WalkUpFromExpr (this=0x43b1380,
S=0x7f3) at /usr/lib/llvm-3.8/include/clang/AST/StmtNodes.inc:115
#6  0x7fe4062ce228 in
clang::RecursiveASTVisitor::WalkUpFromCallExpr
(this=0x43b1380, S=0x7f3) at
/usr/lib/llvm-3.8/include/clang/AST/StmtNodes.inc:311
#7  0x7fe4062b9581 in
clang::RecursiveASTVisitor::TraverseCallExpr (this=0x43b1380,
S=0x7f3, Queue=0x7ffeb1a1e430)
at /usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:2195
#8  0x7fe4062a5f41 in
clang::RecursiveASTVisitor::dataTraverseNode (this=0x43b1380,
S=0x7f3, Queue=0x7ffeb1a1e430) at
/usr/lib/llvm-3.8/include/clang/AST/StmtNodes.inc:311
#9  0x7fe406290be0 in
clang::RecursiveASTVisitor::TraverseStmt (this=0x43b1380,
S=0x7f300d8, Queue=0x0) at
/usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:560
#10 0x7fe406293f92 in
clang::RecursiveASTVisitor::TraverseFunctionHelper
(this=0x43b1380, D=0x7f2d330) at
/usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:1795
#11 0x7fe406289c81 in
clang::RecursiveASTVisitor::TraverseCXXMethodDecl
(this=0x43b1380, D=0x7f2d330) at
/usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:1806
#12 0x7fe4062828c2 in
clang::RecursiveASTVisitor::TraverseDecl (this=0x43b1380,
D=0x7f2d330) at /usr/lib/llvm-3.8/include/clang/AST/DeclNodes.inc:367
#13 0x7fe40628fe7e in
clang::RecursiveASTVisitor::TraverseDeclContextHelper
(this=0x43b1380, DC=0x4366d00) at
/usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:1231
#14 0x7fe40628aa4f in
clang::RecursiveASTVisitor::TraverseTranslationUnitDecl
(this=0x43b1380, D=0x4366ce0) at
/usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:1321
#15 0x7fe406282c25 in
clang::RecursiveASTVisitor::TraverseDecl (this=0x43b1380,
D=0x4366ce0) at /usr/lib/llvm-3.8/include/clang/AST/DeclNodes.inc:491
#16 0x7fe406270ab7 in ClazyASTConsumer::HandleTranslationUnit
(this=0x43b1380, ctx=...) at
/home/big/Documents/BitBucket/clazy/src/Clazy.cpp:151
#17 0x7fe406a7376a in clang::ParseAST(clang::Sema&, bool, bool) () from
/home/tom/Documents/clazy/lib/ClangLazy.so
#18 0x7fe40632ecce in clang::FrontendAction::Execute() () from
/home/tom/Documents/clazy/lib/ClangLazy.so
#19 0x7fe406351656 in
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) () from
/home/tom/Documents/clazy/lib/ClangLazy.so
#20 0x004e3916 in
clang::tooling::FrontendActionFactory::runInvocation(clang::CompilerInvocation*,
clang::FileManager*, std::shared_ptr,
clang::DiagnosticConsumer*)
()
#21 0x004dee10 in clang::tooling::ToolInvocation::runInvocation(char
const*, clang::driver::Compilation*, clang::CompilerInvocation*,
std::shared_ptr) ()
#22 0x004e17b9 in clang::tooling::ToolInvocation::run() ()
#23 0x004e27c5 in
clang::tooling::ClangTool::run(clang::tooling::ToolAction*) ()
#24 0x004ae1c7 in main (argc=41, argv=0x7ffeb1a1f7e8) at
/home/big/Documents/BitBucket/clazy/src/ClazyStandaloneMain.cpp:103

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

[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server

2018-01-13 Thread George L . Emigh

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

--- Comment #10 from George L. Emigh  ---
After the most recent update kmail2 5.7.1 still broken for large emails here.

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

[krita] [Bug 388336] It is possible to select shapes on a locked vector layer.

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

wolthera  changed:

   What|Removed |Added

 CC||freebo...@tiscali.it

--- Comment #1 from wolthera  ---
*** Bug 388926 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 388926] Vector "layer lock" doesn't prevent from moving / scaling objects and from editing text (Krita 4.0.0-beta1.1)

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

wolthera  changed:

   What|Removed |Added

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

--- Comment #1 from wolthera  ---


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

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

[krita] [Bug 388926] Vector "layer lock" doesn't prevent from moving / scaling objects and from editing text (Krita 4.0.0-beta1.1)

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

mvowada  changed:

   What|Removed |Added

Summary|Vector "layers lock"|Vector "layer lock" doesn't
   |doesn't prevent from moving |prevent from moving /
   |/ scaling objects and from  |scaling objects and from
   |editing text (Krita |editing text (Krita
   |4.0.0-beta1.1)  |4.0.0-beta1.1)

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

[krita] [Bug 388926] New: Vector "layers lock" doesn't prevent from moving / scaling objects and from editing text (Krita 4.0.0-beta1.1)

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

Bug ID: 388926
   Summary: Vector "layers lock" doesn't prevent from moving /
scaling objects and from editing text (Krita
4.0.0-beta1.1)
   Product: krita
   Version: 4.0.0-beta.1
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Layers/Vector
  Assignee: krita-bugs-n...@kde.org
  Reporter: freebo...@tiscali.it
  Target Milestone: ---

(Ubuntu 14.04 - Krita 4.0.0-beta1.1.appimage)

Vector "layers lock" doesn't prevent from moving and scaling objects and from
editing text. Steps:

1) enable the layer lock on a vector layer with objects and text
2) using the "Select Shapes Tool" try to move / scale the objects or edit
text

Actual Results: vector layer lock does not prevent from moving / scaling vector
objects and from editing text
Expected Results: when the vector layer lock is enabled do not allow the moving
/ scaling of the objects and the editing of text

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

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-13 Thread Altguard

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

--- Comment #18 from Altguard  ---
That just gave me an idea I didn't consider before - resizing the windows. As
it turns out, this isn't just Chromium - after trying multiple applications at
different window sizes, it looks like taking a screenshot of *any* application
past a certain window size causes the crash, and shrinking the chromium window
down allows me to take a screenshot without issues. I always have Chromium
windows open at a larger size than everything else, so I never caught on until
now. My apologies.

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

[plasma-pa] [Bug 388766] Looks ugly with dark themes

2018-01-13 Thread Anton Hristov

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

Anton Hristov  changed:

   What|Removed |Added

 CC||antonhristov0...@gmail.com

--- Comment #1 from Anton Hristov  ---
Hi,

I am a long-time KDE user who wants to get involved in the development and
solve this bug. Would this be a good 'first-bug' to start with? Can someone
please provide a bit more information on what needs to be done?

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

[clazy] [Bug 388925] Segmentation fault in OldStyleConnect::fixits() calling Expr::getBestDynamicClassType()

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

--- Comment #2 from Tom Isaacson  ---
No. I've turned them on - my command line is:
export CLAZY_FIXIT=fix-old-style-connect && find . -name "*cpp" -print | xargs
/usr/bin/clazy-standalone -extra-arg=-Wno-unknown-warning-option
-extra-arg=-fms-extensions -extra-arg=-Wno-inconsistent-missing-override -p
build/compile_commands.json -checks=old-style-connect

Stacktrace:
 #0  0x7f7fcac23240 in getInterestingTagDecl(clang::TagDecl*) () from
/home/tom/Documents/clazy/lib/ClangLazy.so
 No symbol table info available.
 #1  0x7f7fca448685 in OldStyleConnect::fixits (this=0x52543f0,
classification=12, call=0x7c322d0) at
/home/big/Documents/BitBucket/clazy/src/checks/level2/oldstyleconnect.cpp:450
 expr = 0x7c31200
 record = 0x0
 s = {ID = 4125}
 lastRecordDecl = 0x26d2298
 arg = 0x7c31200
 __for_range = 
 __for_begin = { >> =
{> = {> = {}, }, I = 0x7c322f8}, }
 __for_end = { >> =
{> = {> = {}, }, I = 0x7c32310}, }
 fixits = std::vector of length 0, capacity 0
 macroNum = 0
 implicitCallee = ""
 macroName = ""
 senderMethod = 0x0
 #2  0x7f7fca446915 in OldStyleConnect::VisitStmt (this=0x52543f0,
s=0x7c322d0) at
/home/big/Documents/BitBucket/clazy/src/checks/level2/oldstyleconnect.cpp:215
 call = 0x7c322d0
 function = 0x1fd74f0
 classification = 12
 #3  0x7f7fca471a1e in ClazyASTConsumer::VisitStmt (this=0x39662f0,
stm=0x7c322d0) at /home/big/Documents/BitBucket/clazy/src/Clazy.cpp:139
 check = 0x52543f0
 __for_range = std::vector of length 1, capacity 1 = {0x52543f0}
 __for_begin = 
 __for_end = 
 parentMap = 0x78c61f0
 isFromIgnorableInclude = false
 #4  0x7f7fca4d603a in
clang::RecursiveASTVisitor::WalkUpFromStmt (this=0x39662f0,
S=0x7c322d0) at /usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:320
 No locals.
 #5  0x7f7fca4d61f2 in
clang::RecursiveASTVisitor::WalkUpFromExpr (this=0x39662f0,
S=0x7c322d0) at /usr/lib/llvm-3.8/include/clang/AST/StmtNodes.inc:115
 No locals.
 #6  0x7f7fca4cf228 in
clang::RecursiveASTVisitor::WalkUpFromCallExpr
(this=0x39662f0, S=0x7c322d0) at
/usr/lib/llvm-3.8/include/clang/AST/StmtNodes.inc:311
 No locals.
 #7  0x7f7fca4ba581 in
clang::RecursiveASTVisitor::TraverseCallExpr (this=0x39662f0,
S=0x7c322d0, Queue=0x7ffd5832cc90) at
/usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:2195
 No locals.
 #8  0x7f7fca4a6f41 in
clang::RecursiveASTVisitor::dataTraverseNode (this=0x39662f0,
S=0x7c322d0, Queue=0x7ffd5832cc90) at
/usr/lib/llvm-3.8/include/clang/AST/StmtNodes.inc:311
 No locals.
 #9  0x7f7fca491be0 in
clang::RecursiveASTVisitor::TraverseStmt (this=0x39662f0,
S=0x7c323a8, Queue=0x0) at
/usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:560
 CurrS = 0x7c322d0
 N = 0
 LocalQueue = {> =
{> =
{> =
{ = {BeginX = 0x7ffd5832cca8, EndX = 0x7ffd5832cca8,
CapacityX = 0x7ffd5832cce8}, FirstEl = {> =
{buffer = "\320\"\303\a\000\000\000"}, }}, },
}, Storage = {InlineElts = {{>
= {buffer = "\360\366\302\a\000\000\000"}, },
{> = {buffer = "\031#\263\312\177\177\000"},
}, {> = {buffer =
"\000\000\000\000\000\000\000"}, },
{> = {buffer = "{J\262\312\177\177\000"}, }, {> = {buffer =
"\350\365\302\a\000\000\000"}, }, {> = {buffer = "\300\315\062X\375\177\000"}, },
{> = {buffer = "\220 \261\003\000\000\000"},

 #10 0x7f7fca494f92 in
clang::RecursiveASTVisitor::TraverseFunctionHelper
(this=0x39662f0, D=0x7c2f600) at
/usr/lib/llvm-3.8/include/clang/AST/RecursiveASTVisitor.h:1795
 No locals.
 #11 0x7f7fca48ac81 in

[kdenlive] [Bug 388696] Render to webm crash with AVStream error

2018-01-13 Thread Ovidiu-Florin BOGDAN

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

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

--- Comment #6 from Ovidiu-Florin BOGDAN  ---
(In reply to Jean-Baptiste Mardelle from comment #5)
> Can you please check if this is not a duplicate of issue #388503
> https://bugs.kde.org/show_bug.cgi?id=388503
> 
> (replace vorbis with libvorbis for the audio codec)

Yes, it is a duplicate of that bug after all for the rendering part. I haven't
figured out the stuttering of the project monitor playback yet.

Thank you for your help.

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

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

[kdenlive] [Bug 388503] Changing "acodec=vorbis" to "acodec=libvorbis" fixes a SIGSEGV

2018-01-13 Thread Ovidiu-Florin BOGDAN

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

Ovidiu-Florin BOGDAN  changed:

   What|Removed |Added

 CC||ovidiu@gmail.com

--- Comment #2 from Ovidiu-Florin BOGDAN  ---
*** Bug 388696 has been marked as a duplicate of this bug. ***

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

[clazy] [Bug 388925] Segmentation fault in OldStyleConnect::fixits() calling Expr::getBestDynamicClassType()

2018-01-13 Thread Sergio Martins

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

Sergio Martins  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |smart...@kde.org

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

[clazy] [Bug 388925] Segmentation fault in OldStyleConnect::fixits() calling Expr::getBestDynamicClassType()

2018-01-13 Thread Sergio Martins

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

--- Comment #1 from Sergio Martins  ---
So it doesn't crash if you disable fixits ? Fixits should be disabled by
default already though, unless you enabled them.

Can you share the backtrace ?

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

[frameworks-solid] [Bug 270808] KDE should spin-down external hard disks when 'safely removed'

2018-01-13 Thread Michael Heidelbach

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

--- Comment #50 from Michael Heidelbach  ---
@Davide
Click Device manager icon in toolbar
Click 'actions for ...' for a mounted partition.

You should see something like 'Eject' or 'Auswerfen'
Click that and you disk should power down.

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

[clazy] [Bug 388925] New: Segmentation fault in Expr::getBestDynamicClassTypeExpr()

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

Bug ID: 388925
   Summary: Segmentation fault in
Expr::getBestDynamicClassTypeExpr()
   Product: clazy
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: tom.isaac...@navico.com
CC: smart...@kde.org
  Target Milestone: ---

I'm running clazy-standalone on my codebase and it keeps crashing. The stack
showed me it was crashing while calling Expr::getBestDynamicClassType() from
OldStyleConnect::fixits() and I was able to confirm this by adding debug
output.

I'm wondering if this is
https://www.mail-archive.com/llvm-bugs@lists.llvm.org/msg16745.html so I tried
recompiling clazy with clang 6.0 but I'm having trouble. I've built the clang
source myself but there doesn't seem to be a way to override FindClang.cmake
with my build directory rather than Ubuntu's default clang 3.8 install. Do I
have to edit the cmake build myself?

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

[clazy] [Bug 388925] Segmentation fault in OldStyleConnect::fixits() calling Expr::getBestDynamicClassType()

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

Tom Isaacson  changed:

   What|Removed |Added

Summary|Segmentation fault in   |Segmentation fault in
   |Expr::getBestDynamicClassTy |OldStyleConnect::fixits()
   |peExpr()|calling
   ||Expr::getBestDynamicClassTy
   ||pe()

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

[krdc] [Bug 281071] Request to add support for Terminal Server Gateway Support

2018-01-13 Thread Ondrej

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

--- Comment #8 from Ondrej  ---
(In reply to Andrea Scarpino from comment #7)
> (In reply to Ondrej from comment #6)
> > freerdp fully supports RD Gateway. It would be nice to have it in KRDC as
> > well...
> 
> I sent a patch for this: https://phabricator.kde.org/D9854

Great news! I hope it will be merged soon.

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

[valgrind] [Bug 388895] LibVEX_FrontEnd assertion failure: `0 == sizeof(VexGuestX86State) % LibVEX_GUEST_STATE_ALIGN'

2018-01-13 Thread Ivo Raisr

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

Ivo Raisr  changed:

   What|Removed |Added

 CC||iv...@ivosh.net

--- Comment #3 from Ivo Raisr  ---
SVN is a past thing. Valgrind lives in GIT now:
http://valgrind.org/downloads/repository.html

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

[korganizer] [Bug 273978] Calendars are randomly unselected & colors reset to random values

2018-01-13 Thread Olivier Churlaud

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

--- Comment #19 from Olivier Churlaud  ---
Since Application 17.12.0, both bugs are corrected.

I think this should be closed. 

see https://bugs.kde.org/show_bug.cgi?id=328862,
https://cgit.kde.org/korganizer.git/commit/?id=9aeb0331b6ee44c38ae6ccad8ec0d8e04b2409db
for details

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

[Discover] [Bug 383393] Discover does not install snap packages

2018-01-13 Thread Aleix Pol

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

Aleix Pol  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #2 from Aleix Pol  ---
I can reproduce on neon.
I cannot reproduce on ArchLinux (with master libsnapd-glib) or in kubuntu.

I suggest updating the version of the library in neon to the latest stable.

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

[Discover] [Bug 388734] All Snap apps list size as "0 B"

2018-01-13 Thread Aleix Pol

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

Aleix Pol  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dis
   ||cover/7bef4c75352e51ab98f3a
   ||a2b6bdc657587580aa1
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Aleix Pol  ---
Git commit 7bef4c75352e51ab98f3aa2b6bdc657587580aa1 by Aleix Pol.
Committed on 13/01/2018 at 19:23.
Pushed by apol into branch 'master'.

Improve displayed size

If it's not installed show the download size

M  +1-1libdiscover/backends/SnapBackend/SnapResource.cpp

https://commits.kde.org/discover/7bef4c75352e51ab98f3aa2b6bdc657587580aa1

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

[digikam] [Bug 388898] Convert Tiff to PNG fails

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

--- Comment #11 from caulier.gil...@gmail.com ---
I tried to convert this TIFF file to PNG using native digiKam 5.8.0 installed
on computer. The problem still reproducible. So it's not a packaging problem
with AppImage bundle. The problem is really in BQM implementation.

Gilles Caulier

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

[digikam] [Bug 388898] Convert Tiff to PNG fails

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

--- Comment #10 from caulier.gil...@gmail.com ---
Just to be sure, i tried to convert the TIFF to JPEG into BQM. All work fine as
expected. So the problem is only with PNG converter. Very strange...

Gilles Caulier

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

[digikam] [Bug 388898] Convert Tiff to PNG fails

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

--- Comment #9 from caulier.gil...@gmail.com ---
The dysfunction is fully reproducible here with BQM from 5.8.0 AppImage. So the
problem is localized in BQM files manager or something like that.

Gilles Caulier

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

[digikam] [Bug 388898] Convert Tiff to PNG fails

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

--- Comment #8 from caulier.gil...@gmail.com ---
I can convert the TIFF file to PNG with 5.8.0 Appimage into Image Editor. No
problem here with libpng in fact, included in the bundle.

Gilles Caulier

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

[digikam] [Bug 388898] Convert Tiff to PNG fails