date:20180621

[kdenlive] [Bug 394888] 2018-05-31 refactoring timeline branch does not build.

2018-06-21 Thread Evert Vorster

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

--- Comment #8 from Evert Vorster  ---
Getting further, it now fails at 74%. :)

I'll try the make -k, it's not something I have done before. 

Here is the error now:

[ 74%] Building CXX object
src/CMakeFiles/kdenliveLib.dir/titler/titlewidget.cpp.o
/var/tmp/yaourt-tmp-evert/aur-kdenlive-testing-git/src/kdenlive/src/titler/titlewidget.cpp:
In constructor ‘TitleWidget::TitleWidget(const QUrl&, const Timecode&, const
QString&, Monitor*, QWidget*)’:
/var/tmp/yaourt-tmp-evert/aur-kdenlive-testing-git/src/kdenlive/src/titler/titlewidget.cpp:95:45:
error: invalid use of incomplete type ‘class QButtonGroup’
 auto *colorGroup = new QButtonGroup(this);
 ^
In file included from /usr/include/qt/QtWidgets/qtoolbutton.h:45

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

[umbrello] [Bug 395672] Java import fails to identify "String..." parameter as "String[]"

2018-06-21 Thread Ralf Habacker

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

Ralf Habacker  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 CC||ralf.habac...@freenet.de
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Ralf Habacker  ---
The message indicates that the Java parser has tried to create a class in the
current namespace and found an existing class called 'String'.

Since this can be a problem with the Java parser in Umbrello, it would be nice
to get a Java test file or, if you are using publicly available Java code, a
link to reproduce the problem with an umbrello debug image.

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

[krita] [Bug 395674] the timeline lag

2018-06-21 Thread Boudewijn Rempt

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---
I'm sorry, but this isn't a bug report. A bug report states a problem clearly
in terms that make it easy to reproduce the issue. It also adds relevant
information, like hardware, os version, image file specification. And finally,
a bug report should use the latest version of Krita, which right now is 4.0.4,
not an older version. There just isn't anything we can do with reports like
this.

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

[okular] [Bug 395660] okular cannot preserve annotations in some pdf files.

2018-06-21 Thread Oliver Sander

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

Oliver Sander  changed:

   What|Removed |Added

 CC||oliver.san...@tu-dresden.de

--- Comment #2 from Oliver Sander  ---
Hi Iuri,

okular 0.24.2 is quite old.  There are reasons to believe that new versions
handle these annotations better.  Could you please try that first?

Thanks,
Oliver

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

[frameworks-baloo] [Bug 387672] Baloo File Extraction Error

2018-06-21 Thread EDes

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

EDes  changed:

   What|Removed |Added

 CC||mailin...@wanadoo.fr

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

[frameworks-baloo] [Bug 387672] Baloo File Extraction Error

2018-06-21 Thread EDes

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

--- Comment #19 from EDes  ---
Created attachment 113479
  --> https://bugs.kde.org/attachment.cgi?id=113479&action=edit
New crash information added by DrKonqi

baloo_file_extractor (5.47.0) using Qt 5.9.4

- What I was doing when the application crashed:
Just starting fedora 27, kernel 4.16.15-200

-- Backtrace (Reduced):
#8  0x7f288a39fbf2 in mdb_assert_fail.constprop () from
/lib64/liblmdb.so.0.0.0
#9  0x7f288a394b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0
#10 0x7f288a395dab in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0
#11 0x7f288a396039 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0
#12 0x7f288a397c64 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0

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

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

2018-06-21 Thread bugzilla_noreply

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.

[krita] [Bug 395679] New: The pressure sensitivity with my wacom tablet is not working.

2018-06-21 Thread bugzilla_noreply

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

Bug ID: 395679
   Summary: The pressure sensitivity with my wacom tablet is not
working.
   Product: krita
   Version: 4.0.4
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Shortcuts and Canvas Input Settings
  Assignee: krita-bugs-n...@kde.org
  Reporter: xyziteprogram...@gmail.com
  Target Milestone: ---

Created attachment 113480
  --> https://bugs.kde.org/attachment.cgi?id=113480&action=edit
debug file

The pressure sensitivity with my wacom tablet is not working. Everything I
tried has failed such as clearing preferences for wacom, uninstalling then
reinstalling the driver, uninstalling krita, clearing preferences for krita by
removing files from appdata, changing USB ports, removing the tablet then
putting it back in, and restarting the computer.

Info
-windows 10
-wacom intuos draw (old version)
-a very bad laptop

Also in the wacom settings it does sense the pressure and when I use SAI the
pressure sensitivity did work. I also tried gimp but that didn't work either.
Probably because I don't know how to use it.

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

[krita] [Bug 395679] The pressure sensitivity with my wacom tablet is not working.

2018-06-21 Thread Boudewijn Rempt

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|Shortcuts and Canvas Input  |tablet support
   |Settings|
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Okay, Krita cannot find the driver for your tablet, so it is only getting mouse
events. We've been getting a lot of these reports recently, but it all boils
down to Windows 10 updates and Wacom driver updates breaking things... It's not
something we can fix in Krita, it's a system issue.

You don't mention whether you have tried to enable the windows pointer api in
Krita's tablet settings. Does that make a difference?

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

[krita] [Bug 395679] The pressure sensitivity with my wacom tablet is not working.

2018-06-21 Thread bugzilla_noreply

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

--- Comment #2 from xyziteprogram...@gmail.com ---
(In reply to Boudewijn Rempt from comment #1)
> Okay, Krita cannot find the driver for your tablet, so it is only getting
> mouse events. We've been getting a lot of these reports recently, but it all
> boils down to Windows 10 updates and Wacom driver updates breaking things...
> It's not something we can fix in Krita, it's a system issue.
> 
> You don't mention whether you have tried to enable the windows pointer api
> in Krita's tablet settings. Does that make a difference?
Yea i did try it and it didn't work. Also i forgot to mention that sometimes a
portion of the canvas will sense pressure if the offset is wrong.

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

[plasmashell] [Bug 395661] Dragging PDF file to google drive(Chromium) Crashes plasma shell

2018-06-21 Thread now-im

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

--- Comment #1 from now-im  ---
Same thing happened when I tried to dram an ISO to deepin boot maker. However,
total crash no backtrace.

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

[dolphin] [Bug 395553] Can not 'move' files to an NTFS partition in Kubuntu

2018-06-21 Thread bugzilla_noreply

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

--- Comment #2 from notlost.justlookingaro...@gmail.com ---
Hi Elvis.

It is reproducable and i've love to help solve this, but i have no idea how
to install debug symbols, so you'll have to talk me through it.

On Mon, 18 Jun 2018, 22:26 Elvis Angelaccio, 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=395553
>
> Elvis Angelaccio  changed:
>
>What|Removed |Added
>
> 
>  Status|UNCONFIRMED |RESOLVED
>  Resolution|--- |DUPLICATE
>
> --- Comment #1 from Elvis Angelaccio  ---
> Thanks for the detailed report. We are already tracking this issue in
> #368287.
>
> If you can reproduce the crash, please install debug symbols for kio and
> kcoreaddons and then post a new backtrace. Thanks!
>
> *** This bug has been marked as a duplicate of bug 368287 ***
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kdenlive] [Bug 375691] Crash on most "deshake" values for "rx" / "ry"

2018-06-21 Thread Martin Riethmayer

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

Martin Riethmayer  changed:

   What|Removed |Added

Version|16.08.2 |18.04.0
   Platform|openSUSE RPMs   |Neon Packages

--- Comment #2 from Martin Riethmayer  ---
Still crashing in Kdenlive 17.11.80 on KDE Neon User:

KDE Plasma 5.12.2
KDE FW: 5.48.0
Qt: 5.11.0
Kernel: 4.13.0


Also crashing in Kdenliv 18.03.70 on KDE Neon Git unstable as of today:

KDE Plasma 5.13.80
KDE FW: 5.48.0
Qt: 5.11.0
Kernel: 4.13.0

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

[krita] [Bug 395679] The pressure sensitivity with my wacom tablet is not working.

2018-06-21 Thread Boudewijn Rempt

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

--- Comment #3 from Boudewijn Rempt  ---
Hm. I've actually been able to recreate a setup that shows these problems. I'm
contacting Wacom again, because it still isn't a bug in krita, but a problem
with windows 10 updates breaking the wacom driver.

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

[Spectacle] [Bug 394499] No Visible Guidelines Show for Rectangular Region Grab

2018-06-21 Thread David Allen

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

--- Comment #8 from David Allen  ---
On 06/20/2018 06:15 PM, Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=394499
> 
> --- Comment #7 from Christoph Feck  ---
> If you can provide the information requested in comment #6, please add it.

[root@proteus ~]# lspci -k | grep -EA3 'VGA|3D|Display'
02:00.0 VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 
GT] (rev a1)
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device 1270
 Kernel driver in use: nouveau
 Kernel modules: nouveau

Spectacle Libraries:

KDE Frameworks 5.47.0
Qt 5.10.1 (built against 5.10.1)
The xcb windowing system

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

[frameworks-baloo] [Bug 392663] Default search doesn't show results for files that are clearly there

2018-06-21 Thread Michael D

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

Michael D  changed:

   What|Removed |Added

 CC||nortex...@gmail.com

--- Comment #1 from Michael D  ---
I have the same issue. After a few weeks on a fresh install of Manjaro, dolphin
stopped returning *any* CTRL+F search results. Rebooting did not help. I had to
disable baloo, delete the index database from ~/.local/share/baloo, kill any
baloo processes, re-enable baloo again and then reindex my entire drive. After
that, dolphin started returning search results.

Not sure how to reproduce it either. The index was there and didn't look
corrupt and I hadn't changed any of the baloo configuration settings.

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

[akregator] [Bug 395680] New: Akregator won't start...

2018-06-21 Thread PK

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

Bug ID: 395680
   Summary: Akregator won't start...
   Product: akregator
   Version: 5.8.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: akregator konqueror plugin
  Assignee: kdepim-b...@kde.org
  Reporter: pieterkristen...@gmail.com
  Target Milestone: ---

When I try to start akonadi it crashes immediately. And so does Korganizer btw.
Strange thing is that they both are ok when running inside Kontact.
I installed akonadi in the running live-distribution (neon user 14-06-2018) and
it also crashes at startup.
I tried this on another computer (eight years younger/also intel based) with
the same result: akregator crashes when it starts.

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

[okular] [Bug 395660] okular cannot preserve annotations in some pdf files.

2018-06-21 Thread Albert Astals Cid

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #3 from Albert Astals Cid  ---
It does fail on current version, would need someone to investigate why,
probably a poppler issue

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

[Akonadi] [Bug 394279] /usr/bin/akonadi_indexing_agent coredumps twice

2018-06-21 Thread kts

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

kts  changed:

   What|Removed |Added

Version|unspecified |5.8.2

--- Comment #2 from kts  ---
It's kmail 18.04.2.
It's still crashing.
Give some attention.

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

[systemsettings] [Bug 395681] New: libinput pointer kcm has no neutral setting, overrides system defaults

2018-06-21 Thread bugzilla_noreply

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

Bug ID: 395681
Summary: libinput pointer kcm has no neutral setting, overrides
system defaults
Product: systemsettings
Version: 5.13.1
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: kcm_mouse
Assignee: unassigned-b...@kde.org
Reporter: gr...@sub.red
CC: unassigned-b...@kde.org
Target Milestone: ---

The new kcm for libinput mouse handling has a slider to set the libinput
acceleration factor which has 10 stops, and therefore lacks a centered/neutral
position.

It is currently not possible to disable mouse acceleration with libinput via
the UI. Many users prefer a 1:1 mapping, and disable acceleration entirely.

A current workaround is to manually change ~/.config/kcminputrc and setting the
value to 0.0 and never touch the kcm slider again.

I'd suggest to make it 11 stops, so we'll have 5 negative, a neutral and 5
positive settings, or add a convenience switch to disable acceleration entirely
(set flat profile and neutral factor).

Please note that the leftmost setting results in strong deceleration (for the
flat profile and for slow speeds in the adaptive profile as well) and not in
disabling acceleration. The value given to libinput is not the speed or
acceleration factor, but a parameter within [-1,1] that will affect the actual
factor. See libinput docs[1] and especially The flat pointer acceleration
profile[2] for further info. libinput has chosen bad terminology here and that
should not be transferred to a DE's UI settings for usability reasons. You are
not setting the "acceleration" with that slider but a parameter that affects
the acceleration. And for the flat profile, it doesn't even actually affect
acceleration but speed.

IMHO, it should also not override the system-wide settings set in
/etc/X11/xorg.conf.d/, at least not initially on installing/upgrading Plasma.
It's ok to override the settings, if the user tweaks the actual kcm manually.
Two reasons:
- there are Plasma users which have used libinput on X long before the kcm was
updated
- there are users which have several DEs installed, either due to pragmatism
(some things work better here or there) or because they like to try new things
at times

Those will most likely set their preferences globally. Now when a user has done
that, then upgrades plasma to 5.13 or usually uses Gnome and wants to try
plasma, he'll be left confused with weird mouse behaviour. That also includes
things like inverse scrolling, middle-click emulation, ... and not only the
acceleration factor (which would be bad enough).

[1]:
https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html
[2]:
https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html#ptraccel-profile-flat

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

[valgrind] [Bug 395682] New: Reading debug info

2018-06-21 Thread Дилян Палаузов

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

Bug ID: 395682
   Summary: Reading debug info
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: dilyan.palau...@aegee.org
  Target Milestone: ---

Created attachment 113482
  --> https://bugs.kde.org/attachment.cgi?id=113482&action=edit
The produced binary

I have this program:
  #include 
  int main() {
printf("a\n");
int i = 7 /0;
printf("b\n");
  }
which I compile with "gcc -g t.c -o t"

Running `valgrind -v  --memcheck:track-origins=yes --read-var-info=yes
--memcheck:show-leak-kinds=all --vgdb=no t` I expect to see the line where
there are problems, but it prints:

==24781== Memcheck, a memory error detector
==24781== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==24781== Using Valgrind-3.14.0.GIT-90daa486e8-20180620X and LibVEX; rerun with
-h for copyright info
==24781== Command: t
==24781== 
--24781-- Valgrind options:
--24781---v
--24781----memcheck:track-origins=yes
--24781----read-var-info=yes
--24781----memcheck:show-leak-kinds=all
--24781----vgdb=no
--24781-- Contents of /proc/version:
--24781--   Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc
version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08)
--24781-- 
--24781-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-sse3
--24781-- Page sizes: currently 4096, max supported 4096
--24781-- Valgrind library directory: /usr/local/lib/valgrind
--24781-- Reading syms from /home/me/t
--24781-- ELF section outside all mapped regions
--24781-- Reading syms from /lib/x86_64-linux-gnu/ld-2.19.so
--24781--   Considering /lib/x86_64-linux-gnu/ld-2.19.so ..
--24781--   .. CRC mismatch (computed c067370a wanted 8c45d3ea)
--24781--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.19.so ..
--24781--   .. CRC is valid
--24781-- warning: addVar: unknown size (buf)
--24781-- warning: addVar: unknown size (buf)
--24781-- warning: addVar: unknown size (buf)
--24781-- warning: addVar: unknown size (loadcmds)
--24781-- warning: addVar: unknown size (loadcmds)
--24781-- warning: addVar: unknown size (loadcmds)
--24781-- warning: addVar: unknown size (loadcmds)
--24781-- warning: addVar: unknown size (loadcmds)
--24781-- warning: addVar: unknown size (loadcmds)
--24781-- warning: addVar: unknown size (loadcmds)
--24781-- Reading syms from /usr/local/lib/valgrind/memcheck-amd64-linux
--24781--object doesn't have a symbol table
--24781--object doesn't have a dynamic symbol table
--24781-- Scheduler: using generic scheduler lock implementation.
--24781-- Reading suppressions file: /usr/local/lib/valgrind/default.supp
--24781-- REDIR: 0x4017b50 (ld-linux-x86-64.so.2:strlen) redirected to
0x581df42e (???)
--24781-- REDIR: 0x4017900 (ld-linux-x86-64.so.2:index) redirected to
0x581df448 (???)
--24781-- Reading syms from
/usr/local/lib/valgrind/vgpreload_core-amd64-linux.so
--24781--object doesn't have a symbol table
--24781-- Reading syms from
/usr/local/lib/valgrind/vgpreload_memcheck-amd64-linux.so
--24781--object doesn't have a symbol table
==24781== WARNING: new redirection conflicts with existing -- ignoring it
--24781-- old: 0x04017b50 (strlen  ) R-> (.0) 0x581df42e
???
--24781-- new: 0x04017b50 (strlen  ) R-> (2007.0) 0x0402d490
strlen
--24781-- REDIR: 0x4017b20 (ld-linux-x86-64.so.2:strcmp) redirected to
0x402ed40 (strcmp)
--24781-- REDIR: 0x4018850 (ld-linux-x86-64.so.2:mempcpy) redirected to
0x4037390 (mempcpy)
--24781-- Reading syms from /lib/x86_64-linux-gnu/libc-2.19.so
--24781--   Considering /lib/x86_64-linux-gnu/libc-2.19.so ..
--24781--   .. CRC mismatch (computed 8b555f82 wanted cd9b3228)
--24781--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.19.so ..
--24781--   .. CRC is valid
--24781-- REDIR: 0x4aa8dc0 (libc.so.6:strcasecmp) redirected to 0x4023720
(_vgnU_ifunc_wrapper)
--24781-- REDIR: 0x4aab0b0 (libc.so.6:strncasecmp) redirected to 0x4023720
(_vgnU_ifunc_wrapper)
--24781-- REDIR: 0x4aa8590 (libc.so.6:memcpy@GLIBC_2.2.5) redirected to
0x4023720 (_vgnU_ifunc_wrapper)
--24781-- REDIR: 0x4aa6910 (libc.so.6:rindex) redirected to 0x402ce10 (rindex)
--24781-- REDIR: 0x4aa4c10 (libc.so.6:strlen) redirected to 0x402d3d0 (strlen)
==24781== 
==24781== Process terminating with default action of signal 8 (SIGFPE)
==24781==  Integer divide by zero at address 0x10090584FE
==24781==at 0x401149: ??? (in /home/me/t)
==24781==by 0x4A44B44: (below main) (libc-start.c:287)
a
--24781-- REDIR: 0x4a9f600 (libc.so.6:free) redirected to 0x402afd0 (free)
==24781== 
==24781== HEAP SUMMARY:
==24781== in use at exit: 0 bytes in 0 blocks
==24781==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==24781== 
==24781== All

[krita] [Bug 394376] Unable to export or save-as png, gif, or jpg on 4.1.0-pre-alpha nightly build (git 65e24ca)

2018-06-21 Thread Sebastian

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

--- Comment #20 from Sebastian  ---
(In reply to Alvin Wong from comment #19)
> (In reply to Sebastian from comment #18)
> > (In reply to Boudewijn Rempt from comment #17)
> > > New build:
> > > https://www.dropbox.com/s/sf6q3aiw0g7a1ru/krita-qtbug394376-2.zip?dl=0
> > 
> > Can confirm it to be working with this build.
> 
> Can you make a Process Monitor capture?

Sadly, don't have time for that right now. It just worked for me to save a new
krita file to dropbox (saving existing ones was working for me already). And
export it as .png to dropbox as a new file.

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

[tellico] [Bug 394343] Saving a CD does sometimes deselect it in the list instead of keeping it selected

2018-06-21 Thread Bruno Cornec

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

--- Comment #4 from Bruno Cornec  ---
Created attachment 113483
  --> https://bugs.kde.org/attachment.cgi?id=113483&action=edit
Video showing the issue

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

[krita] [Bug 394510] Clone layer with animation has grave visual bugs and does not work well

2018-06-21 Thread Dmitry Kazakov

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://commits.kde.org/kri
   ||ta/b52918c1a2c7aff72889c5f2
   ||6d9d67de57b50fcd
 Resolution|--- |FIXED

--- Comment #1 from Dmitry Kazakov  ---
Git commit b52918c1a2c7aff72889c5f26d9d67de57b50fcd by Dmitry Kazakov.
Committed on 21/06/2018 at 10:04.
Pushed by dkazakov into branch 'master'.

Correctly invalidate frames when moving a Clone Layer

When moving a clone layer we should also reset all the frames, because
it doesn't have any animation channels.

M  +3-8libs/image/kis_image_animation_interface.cpp
M  +52   -8libs/image/kis_time_range.cpp
M  +2-0libs/image/kis_time_range.h

https://commits.kde.org/krita/b52918c1a2c7aff72889c5f26d9d67de57b50fcd

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

[Akonadi] [Bug 392092] akonadi_control crash on first start

2018-06-21 Thread PK

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

--- Comment #12 from PK  ---
I installed a package called mariadb-server and it seems as if things are
better now.

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

[kaddressbook] [Bug 395683] New: Entry for security-aware messengers

2018-06-21 Thread Thomas Rother

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

Bug ID: 395683
   Summary: Entry for security-aware messengers
   Product: kaddressbook
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: t.rot...@netzwissen.de
CC: to...@kde.org
  Target Milestone: ---

Created attachment 113484
  --> https://bugs.kde.org/attachment.cgi?id=113484&action=edit
Messaging entry in Kontact

The pulldown menu of KAdressbook/Kontact should also offer entries for
security-aware messengers so that people can add these contact data.Proposed
messengers are
a) Signal >> Mobile phone number
b) Threema >> "Threema ID", 8-digit alphanumeric string
c) Telegram >> Username, alphanumeric string, length ?

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

[okular] [Bug 395684] New: Segfault after closing "file not found" dialog after reboot

2018-06-21 Thread Dennis

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

Bug ID: 395684
   Summary: Segfault after closing "file not found" dialog after
reboot
   Product: okular
   Version: 1.4.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: m...@dennis-irrgang.com
  Target Milestone: ---

Application: okular (1.4.2)

Qt Version: 5.11.0
Frameworks Version: 5.46.0
Operating System: Linux 4.17.1-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I zypper dup'd my system and did a reboot. A file was not found (I had moved it
to a different folder after opening the file and forgot about that) after
booting and KDE recreated the session. I closed the dialog and that's when
Okular crashed.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f569785a180 (LWP 3747))]

Thread 2 (Thread 0x7f567bdbf700 (LWP 3775)):
#0  0x7f568df3cb44 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f568def6790 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f568def71fb in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f568def73ec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f5693e8f90b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f5674000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f5693e3f9fb in
QEventLoop::exec(QFlags) (this=0x7f567bdbed90,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7f5693c9e356 in QThread::exec() (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7f56942e0f45 in QDBusConnectionManager::run() (this=0x7f5694556d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x7f5693ca793c in QThreadPrivate::start(void*) (arg=0x7f5694556d60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:367
#9  0x7f5690512554 in start_thread () at /lib64/libpthread.so.0
#10 0x7f569358cfdf in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f569785a180 (LWP 3747)):
[KCrash Handler]
#6  0x7f5695c6a7e0 in  () at /usr/lib64/libKF5ConfigCore.so.5
#7  0x7f5695c7f1f3 in KConfigGroup::readEntry(char const*, QVariant const&)
const () at /usr/lib64/libKF5ConfigCore.so.5
#8  0x5561fd4d07c3 in KConfigGroup::readEntry(char const*, int const&)
const (defaultValue=@0x7ffdaad7edac: 0, key=0x5561fd4d8a4c "ActiveTab",
this=0x7ffdaad7ee60) at /usr/include/qt5/QtCore/qvariant.h:518
#9  0x5561fd4d07c3 in Shell::readProperties(KConfigGroup const&)
(this=0x5561ff239c70, group=...) at
/usr/src/debug/okular-18.04.2-1.1.x86_64/shell/shell.cpp:392
#10 0x7f56969a8b78 in KMainWindow::readPropertiesInternal(KConfig*, int) ()
at /usr/lib64/libKF5XmlGui.so.5
#11 0x7f56969a8bc2 in KMainWindow::restore(int, bool) () at
/usr/lib64/libKF5XmlGui.so.5
#12 0x5561fd4cbcd3 in kRestoreMainWindows() () at
/usr/include/qt5/QtCore/qarraydata.h:255
#13 0x5561fd4c9353 in main(int, char**) (argc=,
argv=) at
/usr/src/debug/okular-18.04.2-1.1.x86_64/shell/main.cpp:66

Reported using DrKonqi

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

[Discover] [Bug 394558] Looking for updates is hanging forever

2018-06-21 Thread Lastique

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

--- Comment #6 from Lastique  ---
Created attachment 113485
  --> https://bugs.kde.org/attachment.cgi?id=113485&action=edit
pkmon log

I've attached pkmon log taken while Discover starts. All log records were
written when Discover started. When I clicked on "Checking for Updates" no
additional activity happened in the log. I currently have no outstanding
updates.

BTW, for completeness, I also don't have the Snap backend installed.

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

[frameworks-kio] [Bug 280571] Ctrl+Click in the Location Bar should open in a new tab

2018-06-21 Thread Dr . Chapatin

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

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

[plasmashell] [Bug 395685] New: KDE desktop environment crashed when searching in start menu

2018-06-21 Thread bugzilla_noreply

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

Bug ID: 395685
   Summary: KDE desktop environment crashed when searching in
start menu
   Product: plasmashell
   Version: 5.12.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: northern.sno...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.5)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.17.2 x86_64
Distribution: Ubuntu 18.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I typed "start" in the search bar after I opened the start menu. Crash happens
when I input the last "t". In such cases, I noticed the first result was always
Google Chrome, which is wierd.

The crash can be reproduced sometimes.

-- Backtrace:
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 0x7f9fd0456800 (LWP 1144))]

Thread 16 (Thread 0x7f9ed3fff700 (LWP 1393)):
#0  0x7f9fc92b49f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55894dbb3130) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f9fc92b49f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55894dbb30e0, cond=0x55894dbb3108) at pthread_cond_wait.c:502
#2  0x7f9fc92b49f3 in __pthread_cond_wait (cond=0x55894dbb3108,
mutex=0x55894dbb30e0) at pthread_cond_wait.c:655
#3  0x7f9fca13359b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9f0ec63ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f9f0ec67ba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f9f0ec62c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f9f0ec67c02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f9f0ec62c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f9f0ec67c02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f9f0ec62c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f9f0ec65a6b in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7f9fca13216d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f9fc92ae6db in start_thread (arg=0x7f9ed3fff700) at
pthread_create.c:463
#14 0x7f9fc9a2888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f9ee8b27700 (LWP 1392)):
#0  0x7f9fc92b49f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55894dbb3130) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f9fc92b49f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55894dbb30e0, cond=0x55894dbb3108) at pthread_cond_wait.c:502
#2  0x7f9fc92b49f3 in __pthread_cond_wait (cond=0x55894dbb3108,
mutex=0x55894dbb30e0) at pthread_cond_wait.c:655
#3  0x7f9fca13359b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9f0ec63ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f9f0ec67ba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f9f0ec62c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f9f0ec65a6b in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f9fca13216d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f9fc92ae6db in start_thread (arg=0x7f9ee8b27700) at
pthread_create.c:463
#10 0x7f9fc9a2888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f9ee9328700 (LWP 1391)):
#0  0x7f9fc92b49f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55894dbb3130) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f9fc92b49f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55894dbb30e0, cond=0x55894dbb3108) at pthread_cond_wait.c:502
#2  0x7f9fc92b49f3 in __pthread_cond_wait (cond=0x55894dbb3108,
mutex=0x55894dbb30e0) at pthread_cond_wait.c:655
#3  0x7f9fca13359b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9f0ec63ad5 in
ThreadWeaver::Weaver::ta

[kdiff3] [Bug 395686] New: Kdiff3 doesn't start in wayland when using the default run command

2018-06-21 Thread Michael D

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

Bug ID: 395686
   Summary: Kdiff3 doesn't start in wayland when using the default
run command
   Product: kdiff3
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: reeves...@gmail.com
  Reporter: nortex...@gmail.com
  Target Milestone: ---

The default run command for kdiff3, which I can no longer tell you because
wayland somehow wiped my clipboard, won't start kdiff3 in a wayland session. It
runs just fine with just "kdiff3".

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

[krita] [Bug 395598] Cannot use CJK input method in input boxes on popup UI elements.

2018-06-21 Thread Eike Hein

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

Eike Hein  changed:

   What|Removed |Added

 CC||h...@kde.org

--- Comment #5 from Eike Hein  ---
I have an automatic daily Bugzilla search set up for "Korean" because I tend to
work on text input issues across KDE (I live in Seoul and type Korean
frequently).

I am super busy currently, but I'll try to take a look at this soon.

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

[krita] [Bug 395598] Cannot use CJK input method in input boxes on popup UI elements.

2018-06-21 Thread Eike Hein

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

--- Comment #6 from Eike Hein  ---
Oh wait, this is Windows-specific? Then I might not be able to help, I only
know Linux well :(.

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

[kmail2] [Bug 395687] New: Mails from Apple Mail are shown without attachment

2018-06-21 Thread naraesk

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

Bug ID: 395687
   Summary: Mails from Apple Mail are shown without attachment
   Product: kmail2
   Version: 5.8.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: m...@naraesk.eu
  Target Milestone: ---

I recieved several mails send by Apple Mail with attachment (*.odt and *.pdf).
In the webmailer they look fine, but Kmail shows no attchment for these mails.

The mail code contains something like

Content-Type: multipart/alternative;
boundary="Apple-Mail=_682EBA32-6E79-4481-A723-AD4C4F5EB65B"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))

and

--Apple-Mail=_3F105A33-15E5-44DE-A56B-168A0F6FB591
Content-Disposition: attachment;
filename=XXX.odt
Content-Type: application/vnd.oasis.opendocument.text;
x-unix-mode=0644;
name="XXX.odt"
Content-Transfer-Encoding: base64

For all other mails I have no problems with attached files. But all mails with
missing attachment have this Apple Mail lines included.

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

[kmail2] [Bug 395687] Mails from Apple Mail are shown without attachment

2018-06-21 Thread naraesk

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

naraesk  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

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

[Falkon] [Bug 395688] New: Middle click paste URL

2018-06-21 Thread Jonathan Riddell

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

Bug ID: 395688
   Summary: Middle click paste URL
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: j...@jriddell.org
  Target Milestone: ---

A wish from me, old versions of Opera let you middle click anywhere in the page
and it would 'paste' the selection clipboard as a URL and load that page.  It's
a very slick way of opening a page.

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

[valgrind] [Bug 385412] s390x: new non-vector z13 instructions not implemented

2018-06-21 Thread Andreas Arnez

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

--- Comment #11 from Andreas Arnez  ---
(In reply to Vadim Barkov from comment #10)
> Andreas,
> 
> I fixed the PPNO implementation so the tests are memcheck clean. I think
> it's ready to merge. 

Thanks!

> Julian,
> Could you review and merge it?

Julian, can we merge this now?

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

[konsole] [Bug 395689] New: konsole ignores .NET color change methods

2018-06-21 Thread bugzilla_noreply

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

Bug ID: 395689
   Summary: konsole ignores .NET color change methods
   Product: konsole
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: eg...@protonmail.com
  Target Milestone: ---

OVERVIEW
=

I am writing a console application in C# using the .NET framework.  This
includes two properties, Console.ForegroundColor and Console.BackgroundColor,
which set the output colors for the foreground and background, respectively. 
However, konsole ignores them completely.


STEPS TO REPRODUCE
===

Using System;

namespace test_program {

   class Program {

  static void Main(string[] args) {

 Console.ForegroundColor = ConsoleColor.Red;  // ConsoleColor is an
enum, where Red = 12
 Console.WriteLine("this text should be red");

  }

   }

}

EXPECTED RESULTS
==

The text in the WriteLine method outputs in red.


ACTUAL RESULTS
===

The text output is in the default color for text (regardless of theme).


ADDITIONAL INFORMATION
===

Konsole version is 18.04.2
Plasma-shell version is 5.13.1

The example C# code above works as expected on other terminal emulators (have
tried it on xterm and urxvt).  Konsole is in 256 color mode, and things like ls
--color=auto also work properly.  So does escaping an ANSI code, e.g.:

> echo -e "\e[0;31mSome red text\e[0m"


Documentation
--

ForegroundColor:
https://msdn.microsoft.com/en-us/library/system.console.foregroundcolor.aspx
BackgroundColor:
https://msdn.microsoft.com/en-us/library/system.console.backgroundcolor.aspx
ConsoleColor (enum):
https://docs.microsoft.com/en-us/dotnet/api/system.consolecolor?view=netframework-4.7.1

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

[konsole] [Bug 395689] konsole ignores .NET color change methods

2018-06-21 Thread bugzilla_noreply

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

eg...@protonmail.com changed:

   What|Removed |Added

Version|unspecified |18.04.2

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

1 2 3 >

1 - 100 of 237 matches

Mail list logo