[gwenview] [Bug 402802] New: Gwenview temporary stops responding after opening an image via KDE Connect

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402802

Bug ID: 402802
   Summary: Gwenview temporary stops responding after opening an
image via KDE Connect
   Product: gwenview
   Version: 18.12.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: paninomaninod...@gmail.com
  Target Milestone: ---

SUMMARY
After opening any image from the phone remotely Gwewnview stop responding for
10 seconds.

At first I thought the problem was worse, but after testing more while filling
this "bug" I understood what happens.
What happens is that when you open a file in your phone (or in any folder I
believe) Gwenview scans the entire folder for more images to tell you if
there's more to see next. At first the navigation arrows appears darkened, and
they lighten up after Gnewnview finishes scanning the folder to tell you that
you can use the navigation option that it offers to see more images from that
folder, right?
If you interacts with the interface in any way the window will freezes and
prompts an error message telling that Gwenview stopped responding and if you
want to force close or wait. Because Gwenview was taking 10 whole seconds to
scan the folder from were I was opening the images I mistakenly thought it was
a bug and that I couldn't close it after opening the images on the phone.

Just a minor annoyance but I wonder if this can be improved.


STEPS TO REPRODUCE
1. Navigate the phone's file system using Dolphin
2. Open any image
3. 

OBSERVED RESULT
Gwenview temporary freezes

EXPECTED RESULT
Gwenview's interface is responsive

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION

Gwenview 18.12.0


At first I tho

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

[kdenlive] [Bug 402671] Combining the "Freeze" effect with others does not work

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402671

--- Comment #4 from kadls...@seznam.cz ---
Unfortunately, the nightly AppImage build (24a3010) crashes when creating a new
project (see the attachment 117256) or when trying to load the test case. It
also display the message "Could not create the video preview window. There is
something wrong with your Kdenlive install or your driver settings, please fix
it." during start up.

I have also built Kdenlive (version 19.03.70) with MLT (version 6.13.0). It
crashes during start up (see the attachment 117257), making it impossible to
try the test case.

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

[kdenlive] [Bug 402671] Combining the "Freeze" effect with others does not work

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402671

--- Comment #3 from kadls...@seznam.cz ---
Created attachment 117257
  --> https://bugs.kde.org/attachment.cgi?id=117257&action=edit
Backtrace of a crash during start up

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

[kdenlive] [Bug 402671] Combining the "Freeze" effect with others does not work

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402671

--- Comment #2 from kadls...@seznam.cz ---
Created attachment 117256
  --> https://bugs.kde.org/attachment.cgi?id=117256&action=edit
Backtrace of a crash when creating a new project

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

[kmymoney] [Bug 402801] New: Time to find another checking program as Tags is screwing up Kmymoney.

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402801

Bug ID: 402801
   Summary: Time to find another checking program as Tags is
screwing up Kmymoney.
   Product: kmymoney
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: deanmalb...@yahoo.com
  Target Milestone: ---

SUMMARY Kmymoney has more bugs in it than ever. 

1) Auto increment check number can not be turned off.  Constantly increments
the check number column regardless if you check the box or not.  Had to call
the account a savings account to get around this. 

2) Tags. I you make a typo in the tag box, it it automatically saved.
3) Once to pick a tag and out the cursor in the amount box, the dollar amount
shows up as a tag. You must double click in the dollar box for it to work. 
4) Tag box can't be disabled. Now the memo box is too small to paste in data. 
A real step backward. 

This new version is costing me much more time to input data and resulting is
more errors. 

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kontact] [Bug 402795] Kontact/Akregator crashes after opening link in New tab

2019-01-02 Thread Colin J Thomson
https://bugs.kde.org/show_bug.cgi?id=402795

Colin J Thomson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||colin.thom...@g6avk.co.uk
 Resolution|--- |DUPLICATE

--- Comment #1 from Colin J Thomson  ---
Probably related to this.

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

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

[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)

2019-01-02 Thread Colin J Thomson
https://bugs.kde.org/show_bug.cgi?id=371511

Colin J Thomson  changed:

   What|Removed |Added

 CC||st...@hotmail.com

--- Comment #24 from Colin J Thomson  ---
*** Bug 402795 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 388386] Time adjustment tool is misleading and potentially leads to data loss

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=388386

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

   What|Removed |Added

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

--- Comment #11 from caulier.gil...@gmail.com ---
yes, and it's already available in last official 6.0.0-beta3 released few days
ago...

Gilles Caulier

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

[digikam] [Bug 388386] Time adjustment tool is misleading and potentially leads to data loss

2019-01-02 Thread Jens
https://bugs.kde.org/show_bug.cgi?id=388386

--- Comment #10 from Jens  ---
Will this make it into 6.0-final?

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

[digikam] [Bug 402800] New: Main album view does not update when moving images between albums

2019-01-02 Thread Jens
https://bugs.kde.org/show_bug.cgi?id=402800

Bug ID: 402800
   Summary: Main album view does not update when moving images
between albums
   Product: digikam
   Version: 6.0.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Albums-MainView
  Assignee: digikam-bugs-n...@kde.org
  Reporter: jens-bugs.kde@spamfreemail.de
  Target Milestone: ---

SUMMARY
see $SUBJECT

STEPS TO REPRODUCE
1. Open an album that has sub-albums, so that the main view displays multiple
albums.
2. move an image from one of the sub-albums into another sub-album

OBSERVED RESULT
The image is moved, the count of images in the tree view (if enabled) is
updated, but the main view isn't updated to reflect the new position of the
moved image.
When deleting an image, the main view is updated as expected.

EXPECTED RESULT
The main view should be updated, while keeping the scrolling position and the
selected image(s) (if any) the same.
Optionally, there should be a way to automatically delete albums which become
empty due to a move or delete operation. Or an option "delete all empty albums"
(hotkey, button, etc).


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  KDE-Neon 18.04 with KDE 5.14.1

(available in About System)
KDE Frameworks 5.51.0
Qt 5.9.7 (kompiliert gegen 5.9.7)
Das xcb Fenstersystem

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

[okular] [Bug 402734] File > Export As... > Auto-open created file

2019-01-02 Thread Gregor Mi
https://bugs.kde.org/show_bug.cgi?id=402734

--- Comment #2 from Gregor Mi  ---
You are right, changing this by default would not be a good idea. This
auto-open feature should be optional, e.g. like here:
http://blog.gilbertconsulting.com/2010/02/how-to-control-pdf-after-exporting.html

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

[kstars] [Bug 402709] scheduler does not start a sequence when frames exist although repeat until terminated is selected

2019-01-02 Thread Wolfgang Reissenberger
https://bugs.kde.org/show_bug.cgi?id=402709

Wolfgang Reissenberger  changed:

   What|Removed |Added

   Assignee|mutla...@ikarustech.com |eric.dejouha...@gmail.com

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

[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist

2019-01-02 Thread Ardith Metz
https://bugs.kde.org/show_bug.cgi?id=397956

Ardith Metz  changed:

   What|Removed |Added

Version|18.08.0 |unspecified

--- Comment #6 from Ardith Metz  ---
I showed excerpt from ~/.config/katerc (without saying that it's from
~/.config/katerc because I assumed it's obvious at least for kate developers).

I also pointed to relevant gui option which will modify ~/.config/katerc.

If you want me to go for full nit, then here I am:

1. rm ~/.kateconfig
2. rm ~/.config/katerc
3. rm ~/kate_test
4. echo " " >kate_test
5. kate kate_test
6. Chose from toolbar: "Settings" -> "Open/Save" -> "General" -> "Remove
trailing spaces" -> "Never" -> "Apply" -> "Ok"
7. Click "Save" button (notice "Undo button is activated which means changes
are done in document)
8. Close kate
9. touch .kateconfig
10. rm ~/.config/katerc
11. rm kate_test
12. echo " " >kate_test
13. kate kate_test
14. Chose from toolbar: "Settings" -> "Open/Save" -> "General" -> "Remove
trailing spaces" -> "Never" -> "Apply" -> "Ok"
15. Click "Save" button from toolbar (notice "Undo button isn't activated which
means there aren't changes done in document)

I hope everything is clear now. Tested on:

Kde plasma:5.14.4
Kde frameworks: 5.53.0
Qt: 5.12.0
Kate: 18.12.0
Distro: Arch Linux

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

[digikam] [Bug 381625] Copying/Moving photograph files between albums does not give Overwrite/Rename/Cancel options if file with same name exists in the destination album.

2019-01-02 Thread aslam karachiwala
https://bugs.kde.org/show_bug.cgi?id=381625

--- Comment #21 from aslam karachiwala  ---
(In reply to caulier.gilles from comment #20)
> Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just
> released ?
> 
> https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/

Yes, I can reproduce this issue with
digikam-6.0.0-beta3-20181228T114626-x86-64.appimage.

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

[KScreen] [Bug 402607] Dynamic scren layout changes don't work properly in Plasma

2019-01-02 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=402607

David Edmundson  changed:

   What|Removed |Added

Product|plasmashell |KScreen
  Component|Multi-screen support|common
   Assignee|aleix...@kde.org|se...@kde.org

--- Comment #8 from David Edmundson  ---
Oh, you literally only have the one screen mirrored. Kscreen problem not a
plasmashell problem then. Moving.

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

[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop

2019-01-02 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=385920

--- Comment #23 from Patrick Silva  ---
Already reported in Qt bug tracker.
https://bugreports.qt.io/browse/QTBUG-67579

comment from a Qt dev...

Hi, sadly there isn't an official way to configure cursor size on Wayland
(yet). Most toolkits, including Qt, use the de-facto environment variable
XCURSOR_SIZE. Could you please check what it's set to on your system, and
upload the output of a Qt application when run with WAYLAND_DEBUG=1?

There is a proposal on the wayland-devel mailing list to add a protocol for
configuring cursor themes (and size) called xcursor-configuration. There's a
WIP patch for Qt here: https://codereview.qt-project.org/#/c/247935/ Note that
we can't merge it until the protocol has been merged into the wayland-protocols
repository, and kwin would also need to add support for it.

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

[kdeconnect] [Bug 402799] New: KDE connect Segmentation Fault.

2019-01-02 Thread Andy Great
https://bugs.kde.org/show_bug.cgi?id=402799

Bug ID: 402799
   Summary: KDE connect Segmentation Fault.
   Product: kdeconnect
   Version: 1.3.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: andythe_gr...@pm.me
  Target Milestone: ---

I update openSUSE Tumbleweed, after that I get crash report about kdeconnectd
every start up. I tried clicking on Restart but it crash immediately after and
display a same crash report over and over.

Operating System: openSUSE Tumbleweed 20181224
KDE Plasma Version: 5.14.4
Qt Version: 5.12.0
KDE Frameworks Version: 5.53.0
Kernel Version: 4.19.11-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 7.5 GiB of RAM



Application: kdeconnectd (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f573fd6a940 (LWP 7780))]

Thread 5 (Thread 0x7f572700 (LWP 7788)):
#0  0x7f57441c5739 in syscall () from /lib64/libc.so.6
#1  0x7f57446e8a24 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0,
val=, op=0, addr=) at thread/qfutex_p.h:105
#2  QtLinuxFutex::futexWait >
(expectedValue=, futex=...) at thread/qfutex_p.h:107
#3  futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593,
curValue=, u=...) at thread/qsemaphore.cpp:219
#4  futexSemaphoreTryAcquire (timeout=-1, n=n@entry=1, u=...) at
thread/qsemaphore.cpp:262
#5  QSemaphore::acquire (this=this@entry=0x7f57440cf440 <(anonymous
namespace)::Q_QGS_libProxyWrapper::innerFunction()::holder+32>, n=n@entry=1) at
thread/qsemaphore.cpp:326
#6  0x7f5744003b84 in QLibProxyWrapper::run (this=0x7f57440cf420
<(anonymous namespace)::Q_QGS_libProxyWrapper::innerFunction()::holder>) at
kernel/qnetworkproxy_libproxy.cpp:179
#7  0x7f57446e6702 in QThreadPrivate::start (arg=0x7f57440cf420 <(anonymous
namespace)::Q_QGS_libProxyWrapper::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
#8  0x7f5742a93554 in start_thread () from /lib64/libpthread.so.0
#9  0x7f57441caccf in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f5736b30700 (LWP 7783)):
#0  0x7f57441bbd34 in read () from /lib64/libc.so.6
#1  0x7f5741c1ea00 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f5741bd8a4b in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f5741bd8ef0 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f5741bd906c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f57448f088b in QEventDispatcherGlib::processEvents
(this=0x7f5728000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x7f574489b02b in QEventLoop::exec (this=this@entry=0x7f5736b2fc60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7f57446e53b6 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7f57446e6702 in QThreadPrivate::start (arg=0x5562995fdc10) at
thread/qthread_unix.cpp:361
#9  0x7f5742a93554 in start_thread () from /lib64/libpthread.so.0
#10 0x7f57441caccf in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f5737605700 (LWP 7782)):
#0  0x7f57441bbd34 in read () from /lib64/libc.so.6
#1  0x7f5741c1ea00 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f5741bd8a4b in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f5741bd8ef0 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f5741bd906c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f57448f088b in QEventDispatcherGlib::processEvents
(this=0x7f573b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x7f574489b02b in QEventLoop::exec (this=this@entry=0x7f5737604c30,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7f57446e53b6 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7f5743a75565 in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x7f57446e6702 in QThreadPrivate::start (arg=0x7f5743aefd80) at
thread/qthread_unix.cpp:361
#10 0x7f5742a93554 in start_thread () from /lib64/libpthread.so.0
#11 0x7f57441caccf in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f573d5de700 (LWP 7781)):
#0  0x7f57441c02c9 in poll () from /lib64/libc.so.6
#1  0x7f574154dcc7 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f574154f8ea in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f573e1e95da in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f57446e6702 in QThreadPrivate::start (arg=0x55629953d8b0) at
thread/qthread_unix.cpp:361
#5  0x7f5742a93554 in start_thread () from /lib64/libpthread.so.0
#6  0x7f57441caccf in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f573fd6a940 (LWP 7780)):
[KCrash Handler]
#6  0x0

kde-bugs-dist@kde.org

2019-01-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402376

--- Comment #7 from Nate Graham  ---
(In reply to Eike Hein from comment #5)
> > But dragging Task Manager buttons makes less sense because in the UI they 
> > represent open *instances* of windows or apps, not the *concept* of the app 
> > itself.
> 
> And that's what dragging them is used for by users, too (e.g. to move a
> window to a different virtual desktop on the pager).
Wow, I didn't even know you could do that! Perhaps we could only make the Task
Manager buttons for open windows draggable within the panel, but not outside of
it. And then there's the fact that with an IOTM, dragging an app icon to the
pager doesn't make sense since IOTM icons represent apps rather than open
windows.

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

[systemsettings] [Bug 402790] Systemsettings applications launching as standalone application

2019-01-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402790

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|INTENTIONAL |FIXED

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

[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop

2019-01-02 Thread Simone
https://bugs.kde.org/show_bug.cgi?id=385920

Simone  changed:

   What|Removed |Added

 CC||simone.tolo...@gmail.com

--- Comment #22 from Simone  ---
Still an issue on:
plasma-workspace-5.14.4-1.fc29

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

[valgrind] [Bug 208531] [PATCH]: FreeBSD support for valgrind

2019-01-02 Thread Yuri
https://bugs.kde.org/show_bug.cgi?id=208531

Yuri  changed:

   What|Removed |Added

 CC|y...@tsoft.com  |

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

[valgrind] [Bug 208531] [PATCH]: FreeBSD support for valgrind

2019-01-02 Thread Ed Maste
https://bugs.kde.org/show_bug.cgi?id=208531

--- Comment #30 from Ed Maste  ---
I believe the specific points raised in previous comments have been addressed.
On the mailing list Philippe Waroquiers reported that many files based on a
Linux version still have the old filename in header comments etc., will address
those soon.

Regtest results as of today:
 == 599 tests, 203 stderr failures, 68 stdout failures, 0 stderrB
failures, 0 stdoutB failures, 0 post failures ==

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

[valgrind] [Bug 208531] [PATCH]: FreeBSD support for valgrind

2019-01-02 Thread Ed Maste
https://bugs.kde.org/show_bug.cgi?id=208531

--- Comment #29 from Ed Maste  ---
(In reply to Bart Van Assche from comment #16)
> -check_PROGRAMS = clreq simwork threads
> +check_PROGRAMS = clreq simwork
> +
> +if !VGCONF_PLATFORMS_INCLUDE_X86_FREEBSD
> +check_PROGRAMS += threads
> +endif

This is no longer in the patchset. tsan_unittest is disabled on FreeBSD in the
patch though:

+if !VGCONF_OS_IS_FREEBSD
+check_PROGRAMS += tsan_unittest
 endif

> And why has the change below been made ? As far as I can see $(EGREP)
> doesn't occur anywhere.
> 
> --- //depot/vendor/valgrind/configure.in.orig
> +++ //depot/vendor/valgrind/configure.in
> @@ -39,6 +39,7 @@
>  # AC_SUBST([OBJCFLAGS])
>  #])
>  AC_PROG_RANLIB
> +AC_PROG_EGREP

Does it get used implicitly by AC_EGREP_CPP perhaps? I also see a ${EGREP} use
in setting xpg_present.

> And why has AC_PATH_PROG(SED, sed) been added ? AC_PROG_SED is already
> present in configure.in.

This one has been removed.

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

[krita] [Bug 401890] Krita doesn't open csv archives

2019-01-02 Thread Ian Giaroli
https://bugs.kde.org/show_bug.cgi?id=401890

--- Comment #50 from Ian Giaroli  ---
(In reply to Boudewijn Rempt from comment #49)
> Ah, no, that's wrong, I'm afraid. Our CSV plugin advertises it can import,
> but it cannot. So this really is a bug. Unfortunately, the original author
> has sort of disappeared...

Not disappeared, I just work in the night and was sleeping when the messages
were writting, but doesn't know anything about programming, so I discovered the
problem and report It.

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

[plasmashell] [Bug 402607] Dynamic scren layout changes don't work properly in Plasma

2019-01-02 Thread Andrej Podzimek
https://bugs.kde.org/show_bug.cgi?id=402607

Andrej Podzimek  changed:

   What|Removed |Added

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

--- Comment #7 from Andrej Podzimek  ---
Clearing the "needsinfo" flag.
Please let me know if there's any further information I can provide.

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

[plasmashell] [Bug 402607] Dynamic scren layout changes don't work properly in Plasma

2019-01-02 Thread Andrej Podzimek
https://bugs.kde.org/show_bug.cgi?id=402607

--- Comment #6 from Andrej Podzimek  ---
Created attachment 117255
  --> https://bugs.kde.org/attachment.cgi?id=117255&action=edit
Broken Plasma dual-head desktop after monitor hot-plug

Unplugging and replugging the (Thunderbolt dock with an) external monitor
causes this. As you can see, the laptop screen is placed correctly (on the
right) and the mouse cursor (as well as windows) can be dragged there just
fine, but Plasma doesn't draw anything on the right (laptop, primary) screen
and leaves it black. No panels, no wallpaper. The left screen (external
monitor) now has *two* Plasma panels overlapping each other, which is really
quite annoying with auto-hide panels.

Killing Plasma and starting plasmashell again restores law and order (see
before_unplug.png for what that looks like).

Sometimes Plasma crashes on its own and gets restarted automatically during
monitor hotplugging. In that case the screen layout turns out to be fine,
presumably, but one gets an ugly error message in desktop notifications. The
ration between the broken layout in this screenshot and a Plasma crash is
(rough guess) 20:1, so the crash is very rare (and I don't have any dumps from
that or whatnot).

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

[systemsettings] [Bug 396725] Configure desktop effects dialog:reading the effect names is impossible with fractional scaling

2019-01-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=396725

--- Comment #5 from Nate Graham  ---
Patch to fix this: https://phabricator.kde.org/D17928

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

[systemsettings] [Bug 402701] "Desktop effects" filtering checkboxes don't get checked

2019-01-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402701

--- Comment #3 from Nate Graham  ---
Here's the patch: https://phabricator.kde.org/D17928

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

[plasmashell] [Bug 402607] Dynamic scren layout changes don't work properly in Plasma

2019-01-02 Thread Andrej Podzimek
https://bugs.kde.org/show_bug.cgi?id=402607

--- Comment #5 from Andrej Podzimek  ---
Created attachment 117254
  --> https://bugs.kde.org/attachment.cgi?id=117254&action=edit
Normal Plasma single-head desktop

This occurs when the laptop either boots in single-head mode or the
(Thunderbolt dock with an) external monitor is unplugged. Everything looks /
works OK here, no duplicate overlapping control panels, no black screen,
windows are correctly relocated. Problems start after replugging the external
monitor (see after_replug.png).

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

[plasmashell] [Bug 402607] Dynamic scren layout changes don't work properly in Plasma

2019-01-02 Thread Andrej Podzimek
https://bugs.kde.org/show_bug.cgi?id=402607

--- Comment #4 from Andrej Podzimek  ---
Created attachment 117253
  --> https://bugs.kde.org/attachment.cgi?id=117253&action=edit
Expected Plasma dual-head desktop

This is what the dual-head desktop should look like. It looks this way after a
normal login in dual-head mode. Unplugging and re-plugging the (Thunderbolt
dock with an) external monitor requires a Plasma restart to get back to this
state; otherwise a broken layout is shown (see after_replug.png).

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

[valgrind] [Bug 208531] [PATCH]: FreeBSD support for valgrind

2019-01-02 Thread Ed Maste
https://bugs.kde.org/show_bug.cgi?id=208531

--- Comment #28 from Ed Maste  ---
Current work is in progress at https://github.com/freebsdfoundation/valgrind.
The most up-to-date branch is freebsd.rebase,
https://github.com/freebsdfoundation/valgrind/tree/freebsd.rebase.

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

[kmymoney] [Bug 402794] Automatic category assignment does not respect tax assignment

2019-01-02 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=402794

Thomas Baumgart  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kmy
   ||money/f838e3c0b7b3cd5543af3
   ||ce4a6119a9a41b2fcba
   Version Fixed In||5.0.3

--- Comment #1 from Thomas Baumgart  ---
Git commit f838e3c0b7b3cd5543af3ce4a6119a9a41b2fcba by Thomas Baumgart.
Committed on 02/01/2019 at 17:23.
Pushed by tbaumgart into branch '5.0'.

Automatically adjust tax split if possible

Importing transaction assigns categories based on previous transactions
found with the same payee or a preselected category. In case such a
historic transaction contains multiple splits then these splits are
copied but the amounts of the splits are not adjusted based on the value
of the imported transaction.

This change now adjusts in case the resulting transaction consists of an
asset/liability account, a taxable category and a tax category such that
the sum of all splits is zero based on the imported transaction.

This also fixes the "Copy splits" feature when used on a taxed
transaction.
FIXED-IN: 5.0.3

M  +10   -1kmymoney/converter/mymoneystatementreader.cpp
M  +53   -7kmymoney/mymoney/mymoneyfile.cpp
M  +15   -1kmymoney/mymoney/mymoneyfile.h
M  +4-0kmymoney/views/kgloballedgerview.cpp

https://commits.kde.org/kmymoney/f838e3c0b7b3cd5543af3ce4a6119a9a41b2fcba

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

[frameworks-kunitconversion] [Bug 402798] New: Add data units (bits, bytes, kilobits, kibibytes, etc)

2019-01-02 Thread Jonathan Rubenstein
https://bugs.kde.org/show_bug.cgi?id=402798

Bug ID: 402798
   Summary: Add data units (bits, bytes, kilobits, kibibytes, etc)
   Product: frameworks-kunitconversion
   Version: 5.53.0
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: jl...@kde.org
  Reporter: jrub...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY
KUnitConversion does not feature data storage units in the current source
tree[1] (f46927e). I think this is a useful feature to add.

STEPS TO REPRODUCE
1. Install the Unit Conversion addon for KRunner
2. Launch KRunner
3. Type "12 gigabytes in mebibytes" into the search bar

OBSERVED RESULT
No result

EXPECTED RESULT
A result of 11444.09 mebibytes


SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
Kernel Version: 4.19.0-1-amd64
OS Type: 64-bit
Processors: 4 × Intel Core Processor (Skylake, IBRS)
Memory: 5.4 GiB of RAM

ADDITIONAL INFORMATION
It's easy to substitute bits as grams for conversion, like kilobit to kilogram,
megabit to megagram, terabit to teragram, since both a bit and a gram equal 1.
Additionally, the prefixes kilo, mega, terra, ... yotta are used by both, and
mean the same thing. However, this does not help when trying to convert a bit
to a byte (which is 8 bits), or SI prefixes (exponents of 1000) to binary
prefixes like kibi, mebi, yobi (exponents of 1024).

The units I would expect to be added are bits (1), and bytes (8), with SI (1K =
1000) and binary (1Ki = 1024) permutations for each from kilo/kibi to
yotta/yobi.

Adding these units would be very useful, since while using a computer, users
deal with these types of units all the time.

NIST has some information about binary prefixes[2][3].

[1]
https://phabricator.kde.org/source/kunitconversion/browse/master/;f46927e9b196d78d117ce06516624094d33dd789
[2] https://physics.nist.gov/cuu/Units/binary.html
[3] (wayback machine since [2] is down temporarily due to the 2019 US
government shutdown)
https://web.archive.org/web/20181126092457/https://physics.nist.gov/cuu/Units/binary.html

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

[valgrind] [Bug 208531] [PATCH]: FreeBSD support for valgrind

2019-01-02 Thread Ed Maste
https://bugs.kde.org/show_bug.cgi?id=208531

Ed Maste  changed:

   What|Removed |Added

 CC||y...@tsoft.com

--- Comment #27 from Ed Maste  ---
*** Bug 368873 has been marked as a duplicate of this bug. ***

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

[valgrind] [Bug 368873] Please add FreeBSD to the supported OS list

2019-01-02 Thread Ed Maste
https://bugs.kde.org/show_bug.cgi?id=368873

--- Comment #3 from Ed Maste  ---
Close as duplicate against existing FreeBSD support ticket

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

[valgrind] [Bug 402781] Redo the cache used to process indirect branch targets

2019-01-02 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=402781

--- Comment #1 from Julian Seward  ---
Created attachment 117251
  --> https://bugs.kde.org/attachment.cgi?id=117251&action=edit
WIP patch

Contains all C-level changes, plus assembly changes for amd64-linux and
x86-linux only, and therefore works only on those platforms.

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

[plasmashell] [Bug 402607] Dynamic scren layout changes don't work properly in Plasma

2019-01-02 Thread Andrej Podzimek
https://bugs.kde.org/show_bug.cgi?id=402607

--- Comment #3 from Andrej Podzimek  ---
Created attachment 117252
  --> https://bugs.kde.org/attachment.cgi?id=117252&action=edit
xrandr -q with the laptop on Thunderbolt dock with a monitor

It's the same when the laptop boots with the Thunderbolt dock and when the dock
is unplugged and replugged.

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

[valgrind] [Bug 368873] Please add FreeBSD to the supported OS list

2019-01-02 Thread Ed Maste
https://bugs.kde.org/show_bug.cgi?id=368873

Ed Maste  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE
 CC||ema...@freebsd.org

--- Comment #2 from Ed Maste  ---


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

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

[plasmashell] [Bug 402607] Dynamic scren layout changes don't work properly in Plasma

2019-01-02 Thread Andrej Podzimek
https://bugs.kde.org/show_bug.cgi?id=402607

Andrej Podzimek  changed:

   What|Removed |Added

 CC||and...@podzimek.org

--- Comment #2 from Andrej Podzimek  ---
Created attachment 117250
  --> https://bugs.kde.org/attachment.cgi?id=117250&action=edit
xrandr -q with just the laptop

It's the same when the laptop boots without Thunderbolt and after Thunderbolt
gets unplugged.

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

[korganizer] [Bug 402797] New: all icons missing in korganizer gui

2019-01-02 Thread wpoet
https://bugs.kde.org/show_bug.cgi?id=402797

Bug ID: 402797
   Summary: all icons missing in korganizer gui
   Product: korganizer
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: w...@polzleitner.com
  Target Milestone: ---

Created attachment 117249
  --> https://bugs.kde.org/attachment.cgi?id=117249&action=edit
icons are missing, see the areas circled in red (not all indicated)

SUMMARY
korganizer does not have any icons in the gui (except the on for "scroll to
today")


STEPS TO REPRODUCE
1. open korganizer in Ubuntu 18.10
2. all icons are missing (see screenshot)
3. 

OBSERVED RESULT
the gui misses all icons

EXPECTED RESULT
should have icons

SOFTWARE/OS VERSIONS
Ubuntu 18.10
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
this is Ubuntu 18.10, GNOME 3, default korganizer installation using apt
KDE Frameworks 5.50.0
Qt 5.11.1 (built against 5.11.1)
The xcb windowing system

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

[bugs.kde.org] [Bug 381753] Internal Server Error when sorting by votes

2019-01-02 Thread Ben Cooksley
https://bugs.kde.org/show_bug.cgi?id=381753

Ben Cooksley  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED

--- Comment #3 from Ben Cooksley  ---
This bug was resolved when https://phabricator.kde.org/T9680 was reported.

The commit that fixed this was
http://commits.kde.org/websites/bugs-kde-org/e14ce68805a1cf332deab093839add4599158ff8

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

[ktorrent] [Bug 388966] Enabling "Search" plugin freezes KTorrent application

2019-01-02 Thread Muhamamd Furqan
https://bugs.kde.org/show_bug.cgi?id=388966

--- Comment #8 from Muhamamd Furqan  ---
Facing same issue
KDE Neon Latest version (5.14)

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

[kwin] [Bug 402689] KWin crashes with OpenGL compositing enabled when using dedicated GPU (radeon) in hybrid graphics notebook

2019-01-02 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=402689

Martin Flöser  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |---
 Status|NEEDSINFO   |REPORTED

--- Comment #10 from Martin Flöser  ---
Backtrace looks good now, so back to reported state

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

[ktorrent] [Bug 388966] Enabling "Search" plugin freezes KTorrent application

2019-01-02 Thread Muhamamd Furqan
https://bugs.kde.org/show_bug.cgi?id=388966

Muhamamd Furqan  changed:

   What|Removed |Added

 CC||mfurqan...@gmail.com

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

[kwin] [Bug 402689] KWin crashes with OpenGL compositing enabled when using dedicated GPU (radeon) in hybrid graphics notebook

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402689

jmlokosiew...@gmail.com changed:

   What|Removed |Added

 CC|jmlokosiew...@gmail.com |

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

[kwin] [Bug 402689] KWin crashes with OpenGL compositing enabled when using dedicated GPU (radeon) in hybrid graphics notebook

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402689

jmlokosiew...@gmail.com changed:

   What|Removed |Added

Version|5.14.4  |git master

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

[digikam] [Bug 384820] Allow matching library paths across different operating systems? [patch]

2019-01-02 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=384820

--- Comment #4 from Maik Qualmann  ---
Yes, the function has no problems with existing "old" entries. But I will
update the patch again.

Maik

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

[kalgebra] [Bug 402674] Wrong graph displayed with function

2019-01-02 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=402674

Aleix Pol  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #2 from Aleix Pol  ---
Please elaborate a bit further.

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

[korganizer] [Bug 402796] New: Part of the GUI on the left buttom is not readable

2019-01-02 Thread wpoet
https://bugs.kde.org/show_bug.cgi?id=402796

Bug ID: 402796
   Summary: Part of the GUI on the left buttom is not readable
   Product: korganizer
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: journalview
  Assignee: kdepim-b...@kde.org
  Reporter: w...@polzleitner.com
  Target Milestone: ---

Created attachment 117248
  --> https://bugs.kde.org/attachment.cgi?id=117248&action=edit
see the left buttom of the GUI marked in red. The text is not readable.

SUMMARY
Korganizer on Ubuntu 18.10 does not display the "Personal Calendar",
"Anniversaries & Birthdays", etc., in the left buttom of the Journal View
correctly. The line spacing seems to be at odds for the treeview, or whatever
control should be displayed. I cannot select my calendar (std.ics) file because
the display is not readable (see screenshot).


STEPS TO REPRODUCE
1. open korganizer
2. select Journal View
3. 

OBSERVED RESULT
The left buttom of the GUI is screwed up.


EXPECTED RESULT
It should be readable


SOFTWARE/OS VERSIONS
Ubuntu 18.10
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5.11.1 and 5.11.2 (none works).

ADDITIONAL INFORMATION
The About Korganizer-> Libraries shows this information:
KDE Frameworks 5.50.0
Qt 5.11.2 (built against 5.11.1)
The xcb windowing system

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

[kalgebra] [Bug 402674] Wrong graph displayed with function

2019-01-02 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=402674

--- Comment #1 from Aleix Pol  ---
Created attachment 117247
  --> https://bugs.kde.org/attachment.cgi?id=117247&action=edit
the plot

I'm not sure what you mean

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

[krita] [Bug 401890] Krita doesn't open csv archives

2019-01-02 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=401890

Boudewijn Rempt  changed:

   What|Removed |Added

   Severity|wishlist|normal
 CC||b...@valdyas.org

--- Comment #49 from Boudewijn Rempt  ---
Ah, no, that's wrong, I'm afraid. Our CSV plugin advertises it can import, but
it cannot. So this really is a bug. Unfortunately, the original author has sort
of disappeared...

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

[frameworks-kglobalaccel] [Bug 365255] inconsistent behavior with alt+7

2019-01-02 Thread Jurica Vukadin
https://bugs.kde.org/show_bug.cgi?id=365255

--- Comment #11 from Jurica Vukadin  ---
It seems the 'grave' keysym (mapped to the 3rd level of the '7' key on Croatian
layout) has something to do with this. Similarly, the 'asciitilde' keysym
prevents Alt+1 from working. If I remove or replace the keysyms, or move them
to the 1st or 2nd level, the shortcuts start working. I.e., for key 7 (AE07):

symbols[Group1]= [ 7,  slash, grave, dead_grave ] # default, doesn't work
symbols[Group1]= [ 7,  slash, dead_grave, grave ] # doesn't work
symbols[Group1]= [ 7,  grave, slash, dead_grave ] # works
symbols[Group1]= [ 7,  slash, 7, dead_grave ] # works
symbols[Group1]= [ 7,  slash ]# works

Can also be reproduced with the German layout:

setxkbmap de
# dump the layout
xkbcomp $DISPLAY de.xkb

# edit the entry for the 7 key in de.xkb, e.g.:
# -symbols[Group1]= [   7,   slash,  
braceleft,seveneighths ]
# +symbols[Group1]= [   7,   slash,   grave,   
seveneighths ]

# set the modified layout
xkbcomp de.xkb $DISPLAY

Alt+7 is busted now.

Also, it seems bugs #310881 and #398069 are the same as this one.

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

[kontact] [Bug 402795] New: Kontact/Akregator crashes after opening link in New tab

2019-01-02 Thread Steeven Hudon
https://bugs.kde.org/show_bug.cgi?id=402795

Bug ID: 402795
   Summary: Kontact/Akregator crashes after opening link in New
tab
   Product: kontact
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: st...@hotmail.com
  Target Milestone: ---

Application: kontact (5.10.0)

Qt Version: 5.12.0
Frameworks Version: 5.53.0
Operating System: Linux 4.14.91-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:  I clicked on an external link
in Kontact/Akregator, to be opened in a New Tab in the Akregator module of
Kontact.

- Custom settings of the application:  Configure Akregator > Browser > Left
mouse click = Open in Tab.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb0ace4eb00 (LWP 4628))]

Thread 32 (Thread 0x7faf62325700 (LWP 30913)):
#0  0x7fb0c1f6a12b in __lll_lock_wait_private () from /usr/lib/libc.so.6
#1  0x7fb0c1f6bf38 in __fprintf_chk () from /usr/lib/libc.so.6
#2  0x7fb0b42ae2f0 in event_logv_ () from /usr/lib/libevent-2.1.so.6
#3  0x7fb0b42ae4b7 in event_warn () from /usr/lib/libevent-2.1.so.6
#4  0x7fb0b42afee2 in ?? () from /usr/lib/libevent-2.1.so.6
#5  0x7fb0b42a5ac8 in event_base_loop () from /usr/lib/libevent-2.1.so.6
#6  0x7fb0ba7bce7d in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#7  0x7fb0ba75863b in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#8  0x7fb0ba78b608 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#9  0x7fb0ba7bc361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#10 0x7fb0c0daca9d in start_thread () from /usr/lib/libpthread.so.0
#11 0x7fb0c1f5cb23 in clone () from /usr/lib/libc.so.6

Thread 31 (Thread 0x7faf693f9700 (LWP 30902)):
#0  0x7fb0c0db2afc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fb0ba7b9379 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fb0ba7ba178 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fb0ba7ba20f in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fb0ba779318 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fb0ba77b4d7 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#6  0x7fb0ba77bb04 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#7  0x7fb0ba7bc361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#8  0x7fb0c0daca9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fb0c1f5cb23 in clone () from /usr/lib/libc.so.6

Thread 30 (Thread 0x7faf69bfa700 (LWP 30901)):
#0  0x7fb0c0db2ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fb0ba7b9447 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fb0ba7ba16a in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fb0ba7ba252 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fb0ba779301 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fb0ba77b4d7 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#6  0x7fb0ba77bac4 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#7  0x7fb0ba7bc361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#8  0x7fb0c0daca9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fb0c1f5cb23 in clone () from /usr/lib/libc.so.6

Thread 29 (Thread 0x7faf6a3fb700 (LWP 30900)):
#0  0x7fb0c0db2ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fb0ba7b9447 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fb0ba7ba16a in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fb0ba7ba252 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fb0ba779301 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fb0ba77b806 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#6  0x7fb0ba77bac4 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#7  0x7fb0ba7bc361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#8  0x7fb0c0daca9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fb0c1f5cb23 in clone () from /usr/lib/libc.so.6

Thread 28 (Thread 0x7faf96e02700 (LWP 30899)):
#0  0x7fb0c0db2ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fb0ba7b9447 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fb0ba7ba16a in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fb0ba7ba252 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fb0ba779301 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fb0ba77b806 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#6  0x7fb0ba77bac4 in ?? () from /usr/lib/libQt5WebEngineCore.so.5
#7  0x7fb0

[kstars] [Bug 402012] kstars crash when updated orbital elements for comet

2019-01-02 Thread claude
https://bugs.kde.org/show_bug.cgi?id=402012

claude  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from claude  ---
(In reply to Jasem Mutlaq from comment #1)
> Cannot reproduce. Can you retrigger it again? If yes, how?

02/01/2019
Thanks for you answer. The bug don't yet appears during the last month. Perhaps
an update on ubuntu has resolved the problem. Thanks and good luck !
Claude.

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

[kalgebra] [Bug 402404] I will add operation buttons like a squaret button for example

2019-01-02 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=402404

--- Comment #1 from Aleix Pol  ---
What's a squaret button?

Maybe you can draw what you mean and send me a picture?

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

[kalgebra] [Bug 402405] Allow removing an operation from the history

2019-01-02 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=402405

Aleix Pol  changed:

   What|Removed |Added

Summary|delete an operation |Allow removing an operation
   ||from the history

--- Comment #1 from Aleix Pol  ---
Could be useful. Maybe it would make sense that you give Cantor (another KDE
Edu application) a try and see if that's what you are looking for. It has a
KAlgebra backend with about the same features.

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

[krita] [Bug 402791] Color changes when selecting layers

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402791

--- Comment #8 from acc4commissi...@gmail.com ---
I should've said "after I select a new color, it happens once, again."... you
probebly get the point anyway. :)

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

[krita] [Bug 402791] Color changes when selecting layers

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402791

--- Comment #7 from acc4commissi...@gmail.com ---
+
It happens once every time I select a color. Once it changed, it stays the
same. And when I select a new color, it happens onece, again.

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

[krita] [Bug 402791] Color changes when selecting layers

2019-01-02 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=402791

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #6 from Boudewijn Rempt  ---
Thanks for the prompt reply!

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

[kmymoney] [Bug 402794] New: Automatic category assignment does not respect tax assignment

2019-01-02 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=402794

Bug ID: 402794
   Summary: Automatic category assignment does not respect tax
assignment
   Product: kmymoney
   Version: 5.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: kmymoney-de...@kde.org
  Reporter: tbaumg...@kde.org
  Target Milestone: ---

SUMMARY
Importing transaction assigns categories based on previous transactions found
with the same payee. In case such a historic transaction contains two splits (a
net income/expense and a tax split) then the splits are copied but the amounts
are not adjusted to the value of the imported transaction.

STEPS TO REPRODUCE
1. Create payee with and assign a tax transaction
2. Import a transaction from the same payee with a different amount
3. 

OBSERVED RESULT
Splits are setup to reflect the same income/expense and tax category but the
transaction is not balanced.

EXPECTED RESULT
Transaction is balanced.

ADDITIONAL INFORMATION
The copy split feature is also affected.

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

[krita] [Bug 402791] Color changes when selecting layers

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402791

--- Comment #5 from acc4commissi...@gmail.com ---
I added the file, but it happens with every new documents. Just in case.

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

[krita] [Bug 402791] Color changes when selecting layers

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402791

--- Comment #3 from acc4commissi...@gmail.com ---
Created attachment 117245
  --> https://bugs.kde.org/attachment.cgi?id=117245&action=edit
gif recording of the problem 2

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

[krita] [Bug 402791] Color changes when selecting layers

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402791

--- Comment #4 from acc4commissi...@gmail.com ---
Created attachment 117246
  --> https://bugs.kde.org/attachment.cgi?id=117246&action=edit
kra file

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

[dolphin] [Bug 402793] New: Sometimes Dolphin crashes on Wayland when I drag a file to the breadcrumb

2019-01-02 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=402793

Bug ID: 402793
   Summary: Sometimes Dolphin crashes on Wayland when I drag a
file to the breadcrumb
   Product: dolphin
   Version: 18.12.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bugsefor...@gmx.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

I tried to move a file to its parent folder by dragging it to the breadcrumb,
so Dolphin crashed.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.14.4
Qt Version: 5.12.0
KDE Frameworks Version: 5.53.0


Thread 5 (Thread 0x7f4203a55700 (LWP 3417)):
#0  0x7f420d4d87a4 in read () from /usr/lib/libc.so.6
#1  0x7f4208d27971 in read (__nbytes=, __buf=, 
__fd=, __fd=, __buf=, 
__nbytes=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x56516b94f0c0) at ../glib/glib/gwakeup.c:210
#3  0x7f4208d780b0 in g_main_context_check (
context=context@entry=0x7f41fc000bf0, max_priority=2147483647, 
fds=fds@entry=0x7f41fc003ce0, n_fds=n_fds@entry=1) at
../glib/glib/gmain.c:3698
#4  0x7f4208d794e6 in g_main_context_iterate (
context=context@entry=0x7f41fc000bf0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at
../glib/glib/gmain.c:3917
#5  0x7f4208d7962e in g_main_context_iteration (context=0x7f41fc000bf0, 
may_block=1) at ../glib/glib/gmain.c:3981
#6  0x7f420b5c95c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#7  0x7f420b57258c in
QEventLoop::exec(QFlags) ()
   from /usr/lib/libQt5Core.so.5
#8  0x7f420b3b65c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#9  0x7f420b83cba6 in ?? () from /usr/lib/libQt5DBus.so.5
#10 0x7f420b3b79cc in ?? () from /usr/lib/libQt5Core.so.5
#11 0x7f4209cb0a9d in start_thread () from /usr/lib/libpthread.so.0
#12 0x7f420d4e7b23 in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f41fbb7b700 (LWP 3419)):
#0  0x7f4208d77cc9 in g_source_iter_next (iter=iter@entry=0x7f41fbb7abd0,
source=source@entry=0x7f41fbb7abc8) at ../glib/glib/gmain.c:953
#1  0x7f4208d77ed2 in g_main_context_check
(context=context@entry=0x7f41fbf0, max_priority=2147483647,
fds=fds@entry=0x7f41f0004db0, n_fds=n_fds@entry=1) at ../glib/glib/gmain.c:944
#2  0x7f4208d794e6 in g_main_context_iterate
(context=context@entry=0x7f41fbf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:3917
#3  0x7f4208d7962e in g_main_context_iteration (context=0x7f41fbf0,
may_block=1) at ../glib/glib/gmain.c:3981
#4  0x7f420b5c95c4 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7f420b57258c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7f420b3b65c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7f420b3b79cc in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f4209cb0a9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f420d4e7b23 in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f4201736700 (LWP 3418)):
#0  0x7f4209cb6afc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4201d56c24 in cnd_wait (mtx=0x56516ba3aa38, cond=0x56516ba3aa60) at
../mesa-18.3.1/src/../include/c11/threads_posix.h:155
#2  util_queue_thread_func (input=input@entry=0x56516bbf0090) at
../mesa-18.3.1/src/util/u_queue.c:270
#3  0x7f4201d56948 in impl_thrd_routine (p=) at
../mesa-18.3.1/src/../include/c11/threads_posix.h:87
#4  0x7f4209cb0a9d in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f420d4e7b23 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f41ebfff700 (LWP 3486)):
#0  0x7f420d4dcc21 in poll () from /usr/lib/libc.so.6
#1  0x7f4209a71673 in ?? ()
#2  0x56516c826098 in ?? ()
#3  0x56516c825fc0 in ?? ()
#4  0x56516c825fc0 in ?? ()
#5  0x in ?? ()

Thread 1 (Thread 0x7f4204d15800 (LWP 3410)):
#0  0x7f420d423d7f in raise () from /usr/lib/libc.so.6
#1  0x7f420cd236cf in KCrash::defaultCrashHandler(int) () from
/usr/lib/libKF5Crash.so.5
#2  
#3  0x7f4204950481 in QtWaylandClient::QWaylandWindow::setVisible(bool) ()
from /usr/lib/libQt5WaylandClient.so.5
#4  0x7f42049f0ad5 in ?? () from
/usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so
#5  0x7f420b9e229c in QWindowPrivate::setVisible(bool) () from
/usr/lib/libQt5Gui.so.5
#6  0x7f420bffece9 in QWidgetPrivate::show_sys() () from
/usr/lib/libQt5Widgets.so.5
#7  0x7f420c008271 in QWidgetPrivate::show_helper() () from
/usr/lib/libQt5Widgets.so.5
#8  0x7f420c00b555 in QWidget::setVisible(bool) () from
/usr/lib/libQt5Widgets.so.5
#9  0x7f420c144742 in QMenu::popup(QPoint const&, QAction*) () 

[trojita] [Bug 402731] crash when sorting emails

2019-01-02 Thread Jan Kundrát
https://bugs.kde.org/show_bug.cgi?id=402731

Jan Kundrát  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Jan Kundrát  ---
We will need a backtrace with debugging symbols to understand the nature of
that crash.

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

[krita] [Bug 402791] Color changes when selecting layers

2019-01-02 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=402791

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
   Severity|major   |normal
 Status|REPORTED|NEEDSINFO

--- Comment #2 from Boudewijn Rempt  ---
Setting to needinfo

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

[krita] [Bug 402791] Color changes when selecting layers

2019-01-02 Thread Boudewijn Rempt
https://bugs.kde.org/show_bug.cgi?id=402791

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
I cannot reproduce this. Could you please provide a screen recording of the
entire Krita window, not just a small section, and the .kra file with which
this happens for you.

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

[systemsettings] [Bug 402790] Systemsettings applications launching as standalone application

2019-01-02 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=402790

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |INTENTIONAL
 CC||k...@davidedmundson.co.uk
 Status|REPORTED|RESOLVED

--- Comment #2 from David Edmundson  ---
There are two approaches to finding data. Searching and browsing.

If you've already searched, you don't need to browse. There's no point listing
anything when we can just show what's relevant.

You've not stated what problem changing this would fix.

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

[amarok] [Bug 402773] Current Track is missing, not showing anything.

2019-01-02 Thread hong
https://bugs.kde.org/show_bug.cgi?id=402773

--- Comment #4 from hong  ---
Created attachment 117244
  --> https://bugs.kde.org/attachment.cgi?id=117244&action=edit
picture of Current Track with recently played links

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

[kmail2] [Bug 402792] New: Can't accept invite without sending confirmation e-mail

2019-01-02 Thread davidblunkett
https://bugs.kde.org/show_bug.cgi?id=402792

Bug ID: 402792
   Summary: Can't accept invite without sending confirmation
e-mail
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: dav1dblunk...@hotmail.com
  Target Milestone: ---

ical invites cannot be accepted without replying!

If I get a cal invite I get the following options:
Accept:tentative:decline:counter proposal:delegate

All of these send replies back (without asking).  I see this as not useful and
leaking sensitive information without permission. As things stand I have to
"work offline", "accept" and delete the reply before it is sent as the 
way to extract the calender information without sending an unwanted reply.

To add insult to injury the original email (with the invitation) then gets
deleted (why?) 

Surely this can't be right? at the very least permission (do you want to
reply?) should be sought and a way to extract the calender information should
be offered.  Ideally the default behaviour should be settable so that I can
handle these requests without leaking sensitive information or spamming up the
world.

FWIW looks like this has been here before Ref: Bug 106595

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

[kaffeine] [Bug 402735] cant set NARRATION to eng

2019-01-02 Thread Mauro Carvalho Chehab
https://bugs.kde.org/show_bug.cgi?id=402735

--- Comment #3 from Mauro Carvalho Chehab  ---
(In reply to Mauro Carvalho Chehab from comment #1)
> There was a major redesign that fixed language selection on Kaffeine -
> needed on EU Countries where programs are received with multiple audio
> channels - each with one different language, but it doesn't take narration
> into account.
> 
> It should probably be easy to add support for it, but I need a stream that
> has both narration and non-narration audios, in order to use my RF
> generators to test it and see how the narration info is encoded.
> 
> Could you please record ~60 seconds of the full MPEG-TS affected by this bug
> and share it to me? You'll need to use the command line dvbv5-zap tool. See:
> 
> https://www.linuxtv.org/wiki/index.php/Dvbv5-
> zap#Recording_the_full_MPEG_stream_on_a_transponder
> 
> PS.: This is usually a big file. You'll need to store it at Google Drive (or
> similar) and send me a shared link. Feel free to send the link directly to
> my e-mail.

Ok, this bug happens also on channels with multiple audio PIDs. It was due to
an if () check that was misplaced.

I fixed it. You should be able to select a different audio channel now at the
channel edit window.

It would still be worth if you could later send me a 60 seconds of a channel
with narration, as I could try to improve the GUI in order for it to display a
different string for narration and try to select the non-narration PID by
default (if such information is somehow present at some descriptor at PMT
table).

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

[kaffeine] [Bug 402735] cant set NARRATION to eng

2019-01-02 Thread Mauro Carvalho Chehab
https://bugs.kde.org/show_bug.cgi?id=402735

Mauro Carvalho Chehab  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kaf
   ||feine/4bb4ad81dc03494d28c9a
   ||a5883faf8dcf6468ef5
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from Mauro Carvalho Chehab  ---
Git commit 4bb4ad81dc03494d28c9aa5883faf8dcf6468ef5 by Mauro Carvalho Chehab.
Committed on 02/01/2019 at 15:45.
Pushed by mauroc into branch 'master'.

dvbchanneldialog: fix audio channel selection

While Kaffeine is properly detecting the audio channels inside
a MPEG-TS stream, the selection dialog is disabled.

The problem is that Kaffeine's logic is to allow selecting the
audio channel only if there are more than one audio PID, but
the check is at the wrong place!

So, move it to be at the right place. While here, do the check
using the checkbox variable, instead of relying on something
else.

Signed-off-by: Mauro Carvalho Chehab 

M  +4-3src/dvb/dvbchanneldialog.cpp

https://commits.kde.org/kaffeine/4bb4ad81dc03494d28c9aa5883faf8dcf6468ef5

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

[bugs.kde.org] [Bug 381753] Internal Server Error when sorting by votes

2019-01-02 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=381753

Christophe Giboudeaux  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from Christophe Giboudeaux  ---
Seems to work now.

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

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-02 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=402789

Christophe Giboudeaux  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[bugs.kde.org] [Bug 399636] Integrate Phabricator and Bugzilla

2019-01-02 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=399636

Christophe Giboudeaux  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[bugs.kde.org] [Bug 375528] Less privileged users can move bugs, but default assignee is not (and cannot be) updated

2019-01-02 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=375528

--- Comment #2 from Christophe Giboudeaux  ---
Is this still valid ?

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

[bugs.kde.org] [Bug 374810] Request for own attachment deletion

2019-01-02 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=374810

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|ASSIGNED|RESOLVED

--- Comment #2 from Christophe Giboudeaux  ---
Let's assume this was fixed long ago.

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

[krita] [Bug 402791] New: Color changes when selecting layers

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402791

Bug ID: 402791
   Summary: Color changes when selecting layers
   Product: krita
   Version: 4.1.7
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Color Selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: acc4commissi...@gmail.com
  Target Milestone: ---

Created attachment 117243
  --> https://bugs.kde.org/attachment.cgi?id=117243&action=edit
gif recording of the problem

SUMMARY
Color changes when selecting layers. 

STEPS TO REPRODUCE
1. Select a color (You don't need to paint anything)
2. Select another layer. (including vector layers)

OBSERVED RESULT
Color changes.

EXPECTED RESULT
Color stays as the same.

SOFTWARE/OS VERSIONS
Windows: Windows 7
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
I thought it happened since the 4.1.7 update so I downgraded it to 4.1.5, but
it still happens.

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

[systemsettings] [Bug 402790] Systemsettings applications launching as standalone application

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402790

Claudius Ellsel  changed:

   What|Removed |Added

 CC||claudius.ell...@live.de

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

[systemsettings] [Bug 402790] Systemsettings applications launching as standalone application

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402790

--- Comment #1 from Claudius Ellsel  ---
Created attachment 117242
  --> https://bugs.kde.org/attachment.cgi?id=117242&action=edit
Standalone

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

[systemsettings] [Bug 402790] New: Systemsettings applications launching as standalone application

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402790

Bug ID: 402790
   Summary: Systemsettings applications launching as standalone
application
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: claudius.ell...@live.de
  Target Milestone: ---

Created attachment 117241
  --> https://bugs.kde.org/attachment.cgi?id=117241&action=edit
Systemsettings

As already written on https://phabricator.kde.org/T10247:

When using system settings it has a list with the different sections and
subsections. Example attached.

However when searching for a specific setting like the mouse setting from start
menu the application launches as standalone, see attachment.

Is there a reason for this behaviour?

>From UX perspective I had expected that the normal system settings page opens
(similar to GNOME and Windows).

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

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

2019-01-02 Thread mthw0
https://bugs.kde.org/show_bug.cgi?id=355540

mthw0  changed:

   What|Removed |Added

Version|5.8.4   |5.14.4
 CC||jari...@hotmail.com

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

[bugs.kde.org] [Bug 399636] Integrate Phabricator and Bugzilla

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=399636

Claudius Ellsel  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=402789

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

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789

Claudius Ellsel  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=399636

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

[bugs.kde.org] [Bug 402789] Switch to Gitlab for code and issue tracking

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789

Claudius Ellsel  changed:

   What|Removed |Added

 CC||claudius.ell...@live.de

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

[bugs.kde.org] [Bug 402789] New: Switch to Gitlab for code and issue tracking

2019-01-02 Thread Claudius Ellsel
https://bugs.kde.org/show_bug.cgi?id=402789

Bug ID: 402789
   Summary: Switch to Gitlab for code and issue tracking
   Product: bugs.kde.org
   Version: unspecified
  Platform: unspecified
OS: unspecified
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: product/component changes
  Assignee: sysad...@kde.org
  Reporter: claudius.ell...@live.de
CC: christo...@krop.fr
  Target Milestone: ---

>From my experience some projects recently switched to Gitlab like GNOME and
freedesktop. My question is, whether this might be also a good step for KDE.
This issue can therefore be used to discuss this topic.

Some arguments:

Pro:
- More intuitive to use
- Having issues and code on the same place

Con:
- Might be missing some features
- Requires some work (setup, migration)

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

[frameworks-kio] [Bug 401978] Opening link redirect to login page

2019-01-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=401978

Nate Graham  changed:

   What|Removed |Added

 CC||kdelibs-b...@kde.org
   Version Fixed In||5.54
 Resolution|WAITINGFORINFO  |FIXED
  Latest Commit||https://cgit.kde.org/kio.gi
   ||t/commit/?id=7bd7f38400b953
   ||a988a2cc942a518339e0b094a8
Version|17.12.3 |5.53.0
 Status|NEEDSINFO   |RESOLVED
   Assignee|konsole-de...@kde.org   |fa...@kde.org
  Component|general |general
Product|konsole |frameworks-kio

--- Comment #9 from Nate Graham  ---
Yep. Due to a bug I just fixed. :)

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

[latte-dock] [Bug 402776] The setting dialog disappears when switching between modes several times

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=402776

--- Comment #2 from tr...@yandex.com ---
Yes, it's more difficult to reproduce the bug on the latest git version.
More specifically, you have to repeat the switching action more times to
reproduce it, about < 15 times on my system.

1, When it happens, the previous switching action was always from Advanced:on
-> Advanced:off
with the debug output:
> [debug 21:55:42.859859] - SecDockConfigView deleting ...
> [warning 21:55:42.997997] - "" doesn't have any WindowType, assuming as 
> NET::Normal

2, If you pin the setting windows, the bug would never happen.

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

[konsole] [Bug 401978] Opening link redirect to login page

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=401978

--- Comment #8 from jb.ducha...@getinfinity.com ---
Hot damn! It works just fine now. 

Thanks for your help!

I'm 98% certain that I had clicked apply the first time I tried the setting,
but it wasn't checked. The default suggested application was firefox now ( it
was already installed, so that hasn't changed ). I selected it again and now it
works. I reloaded the settings to make sure it stuck this time.

Do you have any idea as to why it behaved like that? Just a curiousity on my
part.

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

[valgrind] [Bug 399584] Support macOS Mojave (10.14)

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399584

rowit...@yahoo.com changed:

   What|Removed |Added

 CC||rowit...@yahoo.com

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

[konsole] [Bug 401978] Opening link redirect to login page

2019-01-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=401978

--- Comment #7 from Nate Graham  ---
For 2, did you remember to click Apply? If so, does the problem happen if you
install Firefox and make it your default browser?

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

[konsole] [Bug 401978] Opening link redirect to login page

2019-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=401978

--- Comment #6 from jb.ducha...@getinfinity.com ---
1. Here is the result

x-scheme-handler/http=google-chrome.desktop
x-scheme-handler/https=google-chrome.desktop

2. No the problem remains

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

[krita] [Bug 402770] Selection tool (disappear content)

2019-01-02 Thread Vamdi
https://bugs.kde.org/show_bug.cgi?id=402770

--- Comment #2 from Vamdi  ---
Created attachment 117240
  --> https://bugs.kde.org/attachment.cgi?id=117240&action=edit
To show bug with selection tool

To show bug with selection tool

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

[frameworks-solid] [Bug 402096] Removing memory card causes device to disappear from the system.

2019-01-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402096

Nate Graham  changed:

   What|Removed |Added

  Latest Commit||https://cgit.kde.org/solid.
   ||git/commit/?id=6d260195cf75
   ||604d835235d2a1b02166ee8b514
   ||a
   Version Fixed In||5.54
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #13 from Nate Graham  ---
Fixed in
https://cgit.kde.org/solid.git/commit/?id=6d260195cf75604d835235d2a1b02166ee8b514a

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

[kate] [Bug 402788] New: KWrite crashed while searching

2019-01-02 Thread Alex Fiestas
https://bugs.kde.org/show_bug.cgi?id=402788

Bug ID: 402788
   Summary: KWrite crashed while searching
   Product: kate
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: afies...@kde.org
  Target Milestone: ---

Application: kwrite (19.03.70)
 (Compiled from sources)
Qt Version: 5.12.0
Frameworks Version: 5.54.0
Operating System: Linux 4.20.0-arch1-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was searching some text via Ctrl+F, it worked a few times and then crashed.

This has happend many times.

The crash can be reproduced every time.

-- Backtrace:
Application: KWrite (kwrite), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f94a1f97880 (LWP 3138))]

Thread 4 (Thread 0x7f94935ae700 (LWP 3143)):
#0  0x7f94a70b8afc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f94937ffc24 in ?? () from /usr/lib/dri/i965_dri.so
#2  0x7f94937ff948 in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7f94a70b2a9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f94a84f5b23 in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f949ae60700 (LWP 3142)):
#0  0x7f94a451b424 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0
#1  0x7f94a456d535 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f94a456d62e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f94a8bb886b in QEventDispatcherGlib::processEvents
(this=0x7f9494000b20, flags=...) at
/home/afiestas/Projects/qt5/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:424
#4  0x7f94a8b62c4b in QEventLoop::exec (this=this@entry=0x7f949ae5fcf0,
flags=..., flags@entry=...) at
../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:140
#5  0x7f94a89ac3f6 in QThread::exec (this=this@entry=0x7f94a8ea7d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../../../qtbase/src/corelib/global/qflags.h:120
#6  0x7f94a8e2d565 in QDBusConnectionManager::run (this=0x7f94a8ea7d80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/afiestas/Projects/qt5/qtbase/src/dbus/qdbusconnection.cpp:178
#7  0x7f94a89ad742 in QThreadPrivate::start (arg=0x7f94a8ea7d80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/home/afiestas/Projects/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:361
#8  0x7f94a70b2a9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f94a84f5b23 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f94a0b41700 (LWP 3141)):
#0  0x7f94a84eac21 in poll () from /usr/lib/libc.so.6
#1  0x7f94a4102630 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f94a41042db in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f94a191d4b8 in QXcbEventQueue::run (this=0x561546efbab0) at
/home/afiestas/Projects/qt5/qtbase/src/plugins/platforms/xcb/qxcbeventqueue.cpp:228
#4  0x7f94a89ad742 in QThreadPrivate::start (arg=0x561546efbab0) at
/home/afiestas/Projects/qt5/qtbase/src/corelib/thread/qthread_unix.cpp:361
#5  0x7f94a70b2a9d in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f94a84f5b23 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f94a1f97880 (LWP 3138)):
[KCrash Handler]
#6  0x7f94a90b10ac in QTextEngine::shape (this=0x5615478ed0c0,
item=item@entry=0) at
/home/afiestas/Projects/qt5/qtbase/src/gui/text/qtextengine.cpp:1982
#7  0x7f94a90c5e5b in QTextLine::xToCursor (this=0x7ffc9b666368,
_x=, cpos=QTextLine::CursorBetweenCharacters) at
/home/afiestas/Projects/qt5/qtbase/src/gui/text/qtextlayout.cpp:2885
#8  0x7f94aaae40c0 in KateRenderer::paintTextLine (this=0x56154728ce20,
paint=..., range=..., xStart=0, xEnd=1356, cursor=0x7ffc9b28, flags=...) at
/home/afiestas/Projects/kde5/source/ktexteditor/src/render/katerenderer.cpp:701
#9  0x7f94aab4fdfd in KateViewInternal::paintEvent (this=0x5615470cdb70,
e=0x7ffc9b666980) at
/home/afiestas/Projects/kde5/source/ktexteditor/src/view/kateviewinternal.cpp:3032
#10 0x7f94a9604d88 in QWidget::event (this=0x5615470cdb70,
event=0x7ffc9b666980) at
/home/afiestas/Projects/qt5/qtbase/src/widgets/kernel/qwidget.cpp:8935
#11 0x7f94a95c5601 in QApplicationPrivate::notify_helper
(this=this@entry=0x561546edc540, receiver=receiver@entry=0x5615470cdb70,
e=e@entry=0x7ffc9b666980) at
/home/afiestas/Projects/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3753
#12 0x7f94a95ccc40 in QApplication::notify (this=0x7ffc9b667770,
receiver=0x5615470cdb70, e=0x7ffc9b666980) at
/home/afiestas/Projects/qt5/qtbase/src/widgets/kernel/qapplication.cpp:3500
#13 0x7f94a8b63f79 in QCoreAppl

[kstars] [Bug 402386] ZWO ASI120MC-S camera crashes KStars 3.0

2019-01-02 Thread Jean-Claude
https://bugs.kde.org/show_bug.cgi?id=402386

--- Comment #6 from Jean-Claude  ---
This bug has also been reported in Bug 384171 - ZWO ASI120MC-S camera crashes
on MacOS

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

[kstars] [Bug 402386] ZWO ASI120MC-S camera crashes KStars 3.0

2019-01-02 Thread Jean-Claude
https://bugs.kde.org/show_bug.cgi?id=402386

--- Comment #5 from Jean-Claude  ---
The fact that :
1- the two cameras work well in TheSkyX
2- the bug doesn't appear each time
3- if I transfer the KStars app, the kstars folder and kstars prefs from one
Mac (where it doesn't crash) to another Mac, it crashes !
4- some versions of KStars don't crash while some others will crash (but it
changes)
That's a long time that I stopped programming but I would think at a bad
definition of the parameters of a record (in Pascal)
Sometimes the memory map is OK, sometimes not.

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

[krita] [Bug 401890] Krita doesn't open csv archives

2019-01-02 Thread Scott Petrovic
https://bugs.kde.org/show_bug.cgi?id=401890

Scott Petrovic  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 CC||scottpetro...@gmail.com

--- Comment #48 from Scott Petrovic  ---
I am changing this to a "wishlist" item since it would be a new feature to be
able to import TV Paint CSV files. Based off the documentation, the CSV file is
just a text file with a table of locations for animation frames and layers.
They are mapped to all the images in the "my.frames" folder. It is all zipped
up. This functionality could probably be written with a python plugin with some
of the new python API stuff that is added in Krita 4.2

reference:
https://www.tvpaint.com/doc/tvp11/index.php?id=lesson-import-export-handling-projects-export

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

[konsole] [Bug 401978] Opening link redirect to login page

2019-01-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=401978

--- Comment #5 from Nate Graham  ---
Two more questions for you:
1. What does `grep "x-scheme-handler/http" ~/.config/mimeapps.list` show?
2. Does the problem go away if you click on "In the following application" and
make sure "Google Chrome" is selected?

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

[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist

2019-01-02 Thread Lothar
https://bugs.kde.org/show_bug.cgi?id=397956

--- Comment #5 from Lothar  ---
In you initial post...
https://bugs.kde.org/show_bug.cgi?id=397956#c0
...did you not explicit mention ~/.config/katerc but often .kateconfig.

- Step 1. looks to me obsolete
- In 7. you create an empty file but you did not note before to ensure that 
  there is no such file
- Between 8. + 9. seems to be missed to start Kate again

Lastly I have only played around with my "Remove trailing spaces" setting, with 
and without to start Kate again, but couldn't observe the described damage.
Have also set "Keep extra spaces" from indention page as shown in your post.

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

  1   2   >