[krita] [Bug 382660] Flickering when drawing on large canvases

2017-07-24 Thread Andreas Resch
https://bugs.kde.org/show_bug.cgi?id=382660

Andreas Resch  changed:

   What|Removed |Added

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

--- Comment #2 from Andreas Resch  ---
Hello,

I've read that suggestion before, but it's no viable solution. If I turn it
off, the brush strokes get really slow and lag behind. I guess "Instant
Preview" was implemented for a reason. That's even worse than the flickering. I
actually prefer the flickering to the lagging.

So this isn't really a fix to the issue.

Cheers,
Andreas

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

[kwin] [Bug 376987] On screen display included in window layout

2017-07-24 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=376987

Martin Flöser  changed:

   What|Removed |Added

   Version Fixed In||5.10.4
  Latest Commit||https://commits.kde.org/kwi
   ||n/cf62ac8039a5821e52c6fc8e6
   ||a7d45a38f350dd2
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Martin Flöser  ---
Git commit cf62ac8039a5821e52c6fc8e6a7d45a38f350dd2 by Martin Flöser.
Committed on 22/07/2017 at 15:47.
Pushed by graesslin into branch 'Plasma/5.10'.

[effects] Exclude OSD windows from desktop grid

Summary:
FIXED-IN: 5.10.4

Test Plan: Compiles

Reviewers: #kwin, #plasma

Subscribers: plasma-devel, kwin

Tags: #kwin

Differential Revision: https://phabricator.kde.org/D6835

M  +1-1effects/desktopgrid/desktopgrid.cpp

https://commits.kde.org/kwin/cf62ac8039a5821e52c6fc8e6a7d45a38f350dd2

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

[plasmashell] [Bug 380432] Icons pinned to task manager have huge tooltip

2017-07-24 Thread Petr Nehez
https://bugs.kde.org/show_bug.cgi?id=380432

--- Comment #11 from Petr Nehez  ---
I can confirm that this is not happening anymore.

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

[plasmashell] [Bug 380432] Icons pinned to task manager have huge tooltip

2017-07-24 Thread Petr Nehez
https://bugs.kde.org/show_bug.cgi?id=380432

--- Comment #10 from Petr Nehez  ---
I can confirm that this is not happening anymore.

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

[kwin] [Bug 380106] KWin crashed after changing audio settings in VirtualBox

2017-07-24 Thread Petr Nehez
https://bugs.kde.org/show_bug.cgi?id=380106

Petr Nehez  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[kdenlive] [Bug 379954] Crashes when trying to add "Position and Zoom" effect to Color Clip in timeline [backtrage log included]

2017-07-24 Thread Jesse
https://bugs.kde.org/show_bug.cgi?id=379954

--- Comment #4 from Jesse  ---
Sounds good, thanks Farid!

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

[KScreen] [Bug 378881] Laptop screen doesn't wake up after disconnecting HDMI

2017-07-24 Thread Petr Nehez
https://bugs.kde.org/show_bug.cgi?id=378881

Petr Nehez  changed:

   What|Removed |Added

 CC||petr.ne...@gmail.com

--- Comment #1 from Petr Nehez  ---
This also happened to me few times but when I tried to reproduce it, I was not
successful.
Due to my main problem in bug 381515 I do have kscreen.log so when it occurs
again I will attach my kscreen.log here.

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

[kdenlive] [Bug 382451] downloaded wipes are not available

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=382451

farid  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||snd.no...@gmail.com
 Status|UNCONFIRMED |CONFIRMED

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

[krita] [Bug 382690] Bezier Curve Selection Tool doesn't work after making the first selection

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382690

--- Comment #1 from white.fox@gmail.com ---
(In reply to white.fox.331 from comment #0)
> For making the first selection, I need to press [Enter] to close it, because
> I can't do so by clicking on the starting point even when the circle is
> highlighted to red.
> 
> Afterwards, the tool doesn't work at all. I can't place new points to start
> another selection.

The version is 3.2.0-beta.2 (this version isn't on the list yet)

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

[kdenlive] [Bug 382577] No Render Profiles

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=382577

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from farid  ---
where did you get kdenlive from? see the website on how to download it for
mint, if that doesn't work test the appimage and let us know. closing this
issue as i suspect it is an installation problem and not a bug.

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

[krita] [Bug 382690] New: Bezier Curve Selection Tool doesn't work after making the first selection

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382690

Bug ID: 382690
   Summary: Bezier Curve Selection Tool doesn't work after making
the first selection
   Product: krita
   Version: 3.2.0-beta.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: white.fox@gmail.com
  Target Milestone: ---

For making the first selection, I need to press [Enter] to close it, because I
can't do so by clicking on the starting point even when the circle is
highlighted to red.

Afterwards, the tool doesn't work at all. I can't place new points to start
another selection.

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

[kdenlive] [Bug 379954] Crashes when trying to add "Position and Zoom" effect to Color Clip in timeline [backtrage log included]

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=379954

farid  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #3 from farid  ---
jesse i'm closing this, if you see it again just reopen it.

cheers

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

[kdenlive] [Bug 371730] "Loop Zone" playback in Project & Clip Monitors aren't working

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=371730

farid  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from farid  ---
This is fixed the only problem is the shortcut alt+space doesn't work... maybe
we could create a different one for it. closing.

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

[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions

2017-07-24 Thread Petr Nehez
https://bugs.kde.org/show_bug.cgi?id=381515

--- Comment #18 from Petr Nehez  ---
Created attachment 106851
  --> https://bugs.kde.org/attachment.cgi?id=106851=edit
kscreen-3

And in "kscreen-3" archive there are logs after resuming of my laptop (Eizo
1080p was connected before suspend), connecting Dell 1200p where 1080p was
activated and then restarting of the system.

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

[kdenlive] [Bug 379954] Crashes when trying to add "Position and Zoom" effect to Color Clip in timeline [backtrage log included]

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=379954

farid  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 379954] Crashes when trying to add "Position and Zoom" effect to Color Clip in timeline [backtrage log included]

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=379954

farid  changed:

   What|Removed |Added

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

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

[kdenlive] [Bug 379121] "Output destination" uses wrong dialog on GNOME, makes choosing destination impossible

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=379121

farid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||snd.no...@gmail.com
 Ever confirmed|0   |1

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

[kdenlive] [Bug 379209] crash when opening a project or creating a new project

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=379209

farid  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

--- Comment #1 from farid  ---
Could you please test with a newer version and report back? Also test the
appimage version to see if this is not a distro specific issue.

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

[kdenlive] [Bug 382689] New: Crash opening a project

2017-07-24 Thread farid
https://bugs.kde.org/show_bug.cgi?id=382689

Bug ID: 382689
   Summary: Crash opening a project
   Product: kdenlive
   Version: git-master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: snd.no...@gmail.com
  Target Milestone: ---

Title says it all.

Thread 19 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff9b7ff700 (LWP 27588)]
ProjectFolder::clip (id=..., this=)
at
/tmp/yaourt-tmp-farid/aur-kdenlive-git/src/kdenlive/src/bin/projectfolder.cpp:64
64 
/tmp/yaourt-tmp-farid/aur-kdenlive-git/src/kdenlive/src/bin/projectfolder.cpp:
Arquivo ou diretório não encontrado.
(gdb) thread apply all bt

Thread 19 (Thread 0x7fff9b7ff700 (LWP 27588)):
#0  0x559e1184 in ProjectFolder::clip(QString const&) (id=...,
this=)
at
/tmp/yaourt-tmp-farid/aur-kdenlive-git/src/kdenlive/src/bin/projectfolder.cpp:64
#1  0x559e1184 in ProjectFolder::clip(QString const&) (id=...,
this=)
at
/tmp/yaourt-tmp-farid/aur-kdenlive-git/src/kdenlive/src/bin/projectfolder.cpp:64
#2  0x559e1184 in ProjectFolder::clip(QString const&)
(this=0x58e170b0, id=...)
at
/tmp/yaourt-tmp-farid/aur-kdenlive-git/src/kdenlive/src/bin/projectfolder.cpp:64
#3  0x559be9c9 in Bin::slotCreateAudioThumbs() (this=0x56ad77c0)
at /tmp/yaourt-tmp-farid/aur-kdenlive-git/src/kdenlive/src/bin/bin.cpp:807
#4  0x55650c05 in QtConcurrent::RunFunctionTask::run()
(this=0x58bb9310)
at /usr/include/qt/QtConcurrent/qtconcurrentrunbase.h:136
#5  0x70e66341 in  () at /usr/lib/libQt5Core.so.5
#6  0x70e6a15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7fffee482049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7046bf0f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7fff92648700 (LWP 27580)):
#0  0x70461e9d in poll () at /usr/lib/libc.so.6
#1  0x7fffe7d34c09 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fffe7d34d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x710a8061 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7104bffb in
QEventLoop::exec(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x70e6540e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x70e6a15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7fffee482049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7046bf0f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7fff93049700 (LWP 27579)):
#0  0x7fffee4881ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x70e6b5ec in QWaitCondition::wait(QMutex*, unsigned long) ()
at /usr/lib/libQt5Core.so.5
#2  0x72751ae8 in  () at /usr/lib/libQt5Quick.so.5
---Type  to continue, or q  to quit---
#3  0x72751f4a in  () at /usr/lib/libQt5Quick.so.5
#4  0x70e6a15b in  () at /usr/lib/libQt5Core.so.5
#5  0x7fffee482049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7046bf0f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fff93fff700 (LWP 27578)):
#0  0x70461e9d in poll () at /usr/lib/libc.so.6
#1  0x7fffe7d34c09 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fffe7d34d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x710a8061 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7104bffb in
QEventLoop::exec(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x70e6540e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x70e6a15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7fffee482049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7046bf0f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fff98984700 (LWP 27577)):
#0  0x7fffee4881ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x70e6b5ec in QWaitCondition::wait(QMutex*, unsigned long) ()
at /usr/lib/libQt5Core.so.5
#2  0x72751ae8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x72751f4a in  () at /usr/lib/libQt5Quick.so.5
#4  0x70e6a15b in  () at /usr/lib/libQt5Core.so.5
#5  0x7fffee482049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7046bf0f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7fff9affe700 (LWP 27573)):
#0  0x70461e9d in poll () at /usr/lib/libc.so.6
#1  0x7fffe7d34c09 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fffe7d34d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x710a8061 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7104bffb in
QEventLoop::exec(QFlags) ()
---Type  to continue, or q  to quit---
at /usr/lib/libQt5Core.so.5
#5  0x70e6540e in 

[digikam] [Bug 382688] New: tag cannot be shown in photo's metadata

2017-07-24 Thread Kok Cze Jhin
https://bugs.kde.org/show_bug.cgi?id=382688

Bug ID: 382688
   Summary: tag cannot be shown in photo's metadata
   Product: digikam
   Version: 5.3.0
  Platform: Windows CE
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: mabel_czej...@yahoo.com
  Target Milestone: ---

The tag created through digikam software does not show metadata in windows
photo viewer's album.

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

[valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-24 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=382515

--- Comment #5 from Austin English  ---
Forgot to say, first line of mingw64's pdb is:
BSJB PDB V1.0

first character is \042

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

[digikam] [Bug 343458] A tool like pixelize (e.g. for my favourite images)

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=343458

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

   What|Removed |Added

Summary|a plugin like pixelize  |A tool like pixelize (e.g.
   |(e.g. for my favourite  |for my favourite images)
   |images) |

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

[digikam] [Bug 343458] a plugin like pixelize (e.g. for my favourite images)

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=343458

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

   What|Removed |Added

  Component|Wish For New Plugins|ImageEditor
Product|kipiplugins |digikam
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

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

[valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-24 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=382515

--- Comment #4 from Austin English  ---
(In reply to Philippe Waroquiers from comment #3)
> This find_pdb_header is searching for a specific character '\032'
> and the string "Microsoft C/C++"
> Is the pdb file containing the expected pdb header ?

No, it does not. These files were produced by mingw64. File considers them
data:
/home/austin/.wine/drive_c/windows/mono/mono-2.0/lib/mono/4.5/mscorlib.pdb:
   
 data

whereas real .pdb files from visual studio appear as:
./memory/mozalloc/mozalloc.pdb:   MSVC program database ver
7.00, 4096*95 bytes

it's produced by Mingw, not Microsoft. Whereas my real pdb's first line is:
Microsoft C/C++ MSF 7.00
DS

The first hex character is 0x4D, however (maybe I'm misunderstanding what
you're asking).

FYI, I uploaded the file here:
http://austinenglish.com/files/for_valgrind/mscorlib.pdb

the genuine pdb files I used are at
https://phoenixnap.dl.sourceforge.net/project/wine/Wine%20Gecko/2.36/wine_gecko-2.36-x86-dbg-msvc-pdb.tar.bz2

> I guess wine and/or microsoft-windows have objdump like utilities ?
> Or else just look with emacs this pdb and another working pdb, to
> see if the expected data is there ?
> 
> Would be good also to redo the tracing above adding something like
> --trace-symtab=yes --trace-symtab-patt=*mscorlib*

I'll get this in a bit or tomorrow.

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

[digikam] [Bug 338281] Add Sync to export

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=338281

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

   What|Removed |Added

  Component|Wish For New Plugins|Export
Product|kipiplugins |digikam
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

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

[digikam] [Bug 143978] Sync Plugin: New Synchronisation Framework to export files

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=143978

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

   What|Removed |Added

Version|0.2.0   |unspecified
  Component|Wish For New Plugins|Export
Summary|Sync Plugin: New|Sync Plugin: New
   |Syncronisation Framework|Synchronisation Framework
   |KIPI Plugin |to export files
Product|kipiplugins |digikam
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

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

[digikam] [Bug 269106] Digikam crashes if the currently uploading item is removed from the export list.

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=269106

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

   What|Removed |Added

  Component|BatchQueueManager   |Export

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

[digikam] [Bug 269106] Digikam crashes if the currently uploading item is removed from the export list.

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=269106

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

   What|Removed |Added

  Component|general |BatchQueueManager
Product|kipiplugins |digikam
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

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

[digikam] [Bug 233718] wish: add healer tool (from Gimp) to enable the user to remove spots easily

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=233718

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

   What|Removed |Added

Product|kipiplugins |digikam
  Component|general |ImageEditor
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

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

[plasmashell] [Bug 382687] plasmashell using high cpu when set to slideshow as wallpaper.

2017-07-24 Thread TOM Harrison
https://bugs.kde.org/show_bug.cgi?id=382687

--- Comment #1 from TOM Harrison  ---
Created attachment 106850
  --> https://bugs.kde.org/attachment.cgi?id=106850=edit
screenshot about high cpu usage

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

[digikam] [Bug 382576] DNG Image Converter crashed trying to convert a RAW image

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382576

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
 CC||caulier.gil...@gmail.com
  Component|general |BatchQueueManager-Tool-DngC
   ||onverter
Product|kipiplugins |digikam

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

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

2017-07-24 Thread TOM Harrison
https://bugs.kde.org/show_bug.cgi?id=381000

--- Comment #89 from TOM Harrison  ---
I report a new bug about that. sorry about bothering.

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

[digikam] [Bug 160228] configure does not check for libltdl installed

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=160228

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

   What|Removed |Added

Version|0.1.5   |unspecified
  Component|general |Import
Product|kipiplugins |digikam
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

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

[digikam] [Bug 109976] Header-file: missing forward-declaration in libkexif

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=109976

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

   What|Removed |Added

  Component|general |Metadata-Engine
Product|kipiplugins |digikam
 CC||caulier.gil...@gmail.com
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

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

[plasmashell] [Bug 382687] New: plasmashell using high cpu when set to slideshow as wallpaper.

2017-07-24 Thread TOM Harrison
https://bugs.kde.org/show_bug.cgi?id=382687

Bug ID: 382687
   Summary: plasmashell using high cpu when set to slideshow as
wallpaper.
   Product: plasmashell
   Version: 5.10.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: notm...@gmail.com
  Reporter: l12436...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 106849
  --> https://bugs.kde.org/attachment.cgi?id=106849=edit
callgrind analysis on machine that has such issue.

plasmashell using about one core on Intel Graphic Card machine. It will also
happened on AMD and nvidia graphic card, but the cpu usage is much lower.

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

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

2017-07-24 Thread TOM Harrison
https://bugs.kde.org/show_bug.cgi?id=381000

TOM Harrison  changed:

   What|Removed |Added

 Attachment #106848|0   |1
is obsolete||

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

[kate] [Bug 381997] Kate doesn't receive a lenghty text paste from Firefox

2017-07-24 Thread LordDan
https://bugs.kde.org/show_bug.cgi?id=381997

--- Comment #5 from LordDan  ---
I think that the bug might be in the code that makes that graphical text
preview at scrooling bar to the right. If kate opens a file with large text, no
problem. However, if kate receives a large text from paste command; it might
generate lots of cicles of rendering, letter by letter, consuming a lot of time
and cpu resources.
The solution might be this: do the rendering of the scrooling bar previewer
just in the end of paste task.

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

[kate] [Bug 381997] Kate doesn't receive a lenghty text paste from Firefox

2017-07-24 Thread LordDan
https://bugs.kde.org/show_bug.cgi?id=381997

--- Comment #4 from LordDan  ---
(In reply to Christoph Cullmann from comment #3)
> *** Bug 381329 has been marked as a duplicate of this bug. ***

I don't think so. This bug I reported is about an large incoming text copied
from another application (Firefox). Bug 381329 occurs in an inverse way: a text
being copied from kate to another app, LibreOffice; which is also weird.

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

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

2017-07-24 Thread TOM Harrison
https://bugs.kde.org/show_bug.cgi?id=381000

--- Comment #88 from TOM Harrison  ---
Created attachment 106848
  --> https://bugs.kde.org/attachment.cgi?id=106848=edit
callgrind analysis on machine that has such issue.

hope it will help.

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

[krunner] [Bug 365871] Crash when cancelling search

2017-07-24 Thread rindeal
https://bugs.kde.org/show_bug.cgi?id=365871

Jan Chren (rindeal)  changed:

   What|Removed |Added

 CC||dev.rindeal+bugs.kde.org@gm
   ||ail.com

--- Comment #2 from Jan Chren (rindeal)  ---
Just hit it with Krunner 5.35.0 and Qt 5.7.1

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

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

2017-07-24 Thread TOM Harrison
https://bugs.kde.org/show_bug.cgi?id=381000

--- Comment #87 from TOM Harrison  ---
Created attachment 106847
  --> https://bugs.kde.org/attachment.cgi?id=106847=edit
unfortunately still using almost single core on plasmashell

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

[dolphin] [Bug 382686] New: Dolphin crashed when I was working with multiple tabs

2017-07-24 Thread Enrique M . Roldan
https://bugs.kde.org/show_bug.cgi?id=382686

Bug ID: 382686
   Summary: Dolphin crashed when I was working with multiple tabs
   Product: dolphin
   Version: 17.04.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: enrique.rol...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (17.04.1)

Qt Version: 5.7.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.11-300.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"

-- Information about the crash:
- What I was doing when the application crashed:

I't crashed when I was working with multiple tabs.

- Custom settings of the application:

I have a link to Google Drive, and some other links to carpets.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f77b25880c0 (LWP 16576))]

Thread 3 (Thread 0x7f7784682700 (LWP 16579)):
#0  0x7f77ac02319d in read () at /lib64/libc.so.6
#1  0x7f77a4bd9170 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f77a4b95078 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f77a4b95510 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f77a4b9567c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f77ace48e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f77acdf960a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f77acc5199a in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f77acc55c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f77a992236d in start_thread () at /lib64/libpthread.so.0
#10 0x7f77ac033b8f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f779f95a700 (LWP 16577)):
#0  0x7f77ac027a9d in poll () at /lib64/libc.so.6
#1  0x7f77a4b95569 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f77a4b9567c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f77ace48e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f77acdf960a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f77acc5199a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f77ad05aa39 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f77acc55c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f77a992236d in start_thread () at /lib64/libpthread.so.0
#9  0x7f77ac033b8f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f77b25880c0 (LWP 16576)):
[KCrash Handler]
#6  0x7f77accaa0c3 in QHashData::nextNode(QHashData::Node*) () at
/lib64/libQt5Core.so.5
#7  0x7f77b31efb98 in KItemListView::slotSelectionChanged(KItemSet const&,
KItemSet const&) () at /lib64/libdolphinprivate.so.5
#8  0x7f77ace21b97 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#9  0x7f77b324a60a in KItemListSelectionManager::selectionChanged(KItemSet
const&, KItemSet const&) () at /lib64/libdolphinprivate.so.5
#10 0x7f77b31ea7e4 in KItemListSelectionManager::clearSelection() () at
/lib64/libdolphinprivate.so.5
#11 0x7f77b3508797 in FoldersPanel::updateCurrentItem(int) () at
/lib64/libkdeinit5_dolphin.so
#12 0x7f77b3508990 in FoldersPanel::loadTree(QUrl const&) () at
/lib64/libkdeinit5_dolphin.so
#13 0x7f77b3508b83 in FoldersPanel::urlChanged() () at
/lib64/libkdeinit5_dolphin.so
#14 0x7f77b350612e in Panel::setUrl(QUrl const&) () at
/lib64/libkdeinit5_dolphin.so
#15 0x7f77ace21b97 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#16 0x7f77b352ca55 in DolphinMainWindow::urlChanged(QUrl const&) () at
/lib64/libkdeinit5_dolphin.so
#17 0x7f77ace21b97 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#18 0x7f77b2b15345 in KUrlNavigator::urlChanged(QUrl const&) () at
/lib64/libKF5KIOFileWidgets.so.5
#19 0x7f77b2b1890a in KUrlNavigator::setLocationUrl(QUrl const&) () at
/lib64/libKF5KIOFileWidgets.so.5
#20 0x7f77b34dffac in DolphinViewContainer::setUrl(QUrl const&) () at
/lib64/libkdeinit5_dolphin.so
#21 0x7f77b34e00db in DolphinViewContainer::slotItemActivated(KFileItem
const&) () at /lib64/libkdeinit5_dolphin.so
#22 0x7f77ace21b97 in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#23 0x7f77b324b695 in DolphinView::itemActivated(KFileItem const&) () at
/lib64/libdolphinprivate.so.5
#24 0x7f77b32213e1 in DolphinView::slotItemActivated(int) () at
/lib64/libdolphinprivate.so.5
#25 0x7f77ace21b97 in 

[plasma-nm] [Bug 376664] Bridged connections are not visible in the applet

2017-07-24 Thread Jack Prom
https://bugs.kde.org/show_bug.cgi?id=376664

Jack Prom  changed:

   What|Removed |Added

 CC||j...@protohuman.net

--- Comment #16 from Jack Prom  ---
Created attachment 106846
  --> https://bugs.kde.org/attachment.cgi?id=106846=edit
bring back functionality

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

[plasma-nm] [Bug 376664] Bridged connections are not visible in the applet

2017-07-24 Thread Jack Prom
https://bugs.kde.org/show_bug.cgi?id=376664

--- Comment #17 from Jack Prom  ---
ok, have a look:

1. Gnome drops support cause "supported by Cockpit already"
2. You ask on kde-hardware-devel about dropping too. One persons says yes,
another no: 2:1 - in my opinion this isn't "we decided"!
3. you drop support cause of "gnome do so & not used on desktop anyway"
4. 9 people says, that you brick their setups! 9 people says, that she use it
on the desktop!

Your argument "not used on desktop anyway" is invalid, should we use cockpit in
future now, because gnome said so? I'm confused. Gnome is known for reducing
functionality with every release, KDE not. But not plasma-nm, you decided to
follow gnome way. I added patch from
https://forums.gentoo.org/viewtopic-t-1066054.html to bring back functionality,
so you have no work to bring back functionality! Please, don't ignore userbase
anymore.

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

[kdesrc-build] [Bug 353811] set-env no longer works

2017-07-24 Thread Michael Pyne
https://bugs.kde.org/show_bug.cgi?id=353811

Michael Pyne  changed:

   What|Removed |Added

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

--- Comment #8 from Michael Pyne  ---
I've taken a look again and still haven't been able to reproduce.

There was a bug with "options" blocks involving modules that weren't created
from a module-set, which I thought may have been potentially associated.  I
fixed that bug but that didn't seem to make a different in reproducing.

So for now I'm closing as WORKSFORME but if you experience again please reopen.

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

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

2017-07-24 Thread Scott Sloan
https://bugs.kde.org/show_bug.cgi?id=382624

--- Comment #2 from Scott Sloan  ---
I was unable reproduce it myself. Feel free to close and I'll create a new
issue if it happens again

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

[digikam] [Bug 382677] Rating groups by mouse only changes first item.[patch]

2017-07-24 Thread Simon
https://bugs.kde.org/show_bug.cgi?id=382677

Simon  changed:

   What|Removed |Added

Summary|Rating groups by mouse only |Rating groups by mouse only
   |changes first item. |changes first item.[patch]
   Severity|major   |normal

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

[digikam] [Bug 382677] Rating groups by mouse only changes first item.

2017-07-24 Thread Simon
https://bugs.kde.org/show_bug.cgi?id=382677

Simon  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||freisi...@gmail.com
   Assignee|digikam-de...@kde.org   |freisi...@gmail.com
 Ever confirmed|0   |1

--- Comment #1 from Simon  ---
Created attachment 106845
  --> https://bugs.kde.org/attachment.cgi?id=106845=edit
Considers grouping for rating applied via overlay

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

[tellico] [Bug 382680] 3.0.2 release build fails with cmake 3.9

2017-07-24 Thread rezso
https://bugs.kde.org/show_bug.cgi?id=382680

--- Comment #1 from rezso  ---
And the output of configuring, if this helps:

cmake
-DCMAKE_PREFIX_PATH=/usr/lib/qt5
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON
-DBUILD_TESTS=OFF
-DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_INSTALL_LIBDIR=/usr/lib
-- The C compiler identification is GNU 6.2.0
-- The CXX compiler identification is GNU 6.2.0
-- Check for working C compiler: /usr/lib/ccache/cc
-- Check for working C compiler: /usr/lib/ccache/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/lib/ccache/c++
-- Check for working CXX compiler: /usr/lib/ccache/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Deprecation Warning at CMakeLists.txt:11 (CMAKE_POLICY):
  The OLD behavior for policy CMP0028 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.


CMake Warning at /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:640 (message):
  KDE_INSTALL_BINDIR, KDE_INSTALL_LIBDIR and KDE_INSTALL_INCLUDEDIR should
  either all be absolute paths or all be relative paths.
Call Stack (most recent call first):
  CMakeLists.txt:31 (include)


-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Failed
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Could not set up the appstream test. appstreamcli is missing.
-- Looking for strlwr
-- Looking for strlwr - not found
-- Looking for strupr
-- Looking for strupr - not found
-- Found KF5Archive: /usr/lib/cmake/KF5Archive/KF5ArchiveConfig.cmake (found
version "5.36.0") 
-- Found KF5Codecs: /usr/lib/cmake/KF5Codecs/KF5CodecsConfig.cmake (found
version "5.36.0") 
-- Found KF5Config: /usr/lib/cmake/KF5Config/KF5ConfigConfig.cmake (found
version "5.36.0") 
-- Found KF5ConfigWidgets:
/usr/lib/cmake/KF5ConfigWidgets/KF5ConfigWidgetsConfig.cmake (found version
"5.36.0") 
-- Found KF5CoreAddons: /usr/lib/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake
(found version "5.36.0") 
-- Found KF5Crash: /usr/lib/cmake/KF5Crash/KF5CrashConfig.cmake (found version
"5.36.0") 
-- Found KF5DocTools: /usr/lib/cmake/KF5DocTools/KF5DocToolsConfig.cmake (found
version "5.36.0") 
-- Found KF5GuiAddons: /usr/lib/cmake/KF5GuiAddons/KF5GuiAddonsConfig.cmake
(found version "5.36.0") 
-- Found KF5IconThemes: /usr/lib/cmake/KF5IconThemes/KF5IconThemesConfig.cmake
(found version "5.36.0") 
-- Found KF5ItemModels: /usr/lib/cmake/KF5ItemModels/KF5ItemModelsConfig.cmake
(found version "5.36.0") 
-- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
-- Found PythonInterp: /usr/bin/python (found version "2.7.12") 
-- Found KF5I18n: /usr/lib/cmake/KF5I18n/KF5I18nConfig.cmake (found version
"5.36.0") 
-- Found KF5JobWidgets: /usr/lib/cmake/KF5JobWidgets/KF5JobWidgetsConfig.cmake
(found version "5.36.0") 
-- Found KF5KIO: /usr/lib/cmake/KF5KIO/KF5KIOConfig.cmake (found version
"5.36.0") 
-- Found KF5Solid: /usr/lib/cmake/KF5Solid/KF5SolidConfig.cmake (found version
"5.36.0") 
-- Found KF5Wallet: /usr/lib/cmake/KF5Wallet/KF5WalletConfig.cmake (found
version "5.36.0") 
-- Found KF5WidgetsAddons:
/usr/lib/cmake/KF5WidgetsAddons/KF5WidgetsAddonsConfig.cmake (found version
"5.36.0") 
-- Found KF5WindowSystem:
/usr/lib/cmake/KF5WindowSystem/KF5WindowSystemConfig.cmake (found version
"5.36.0") 
-- Found KF5XmlGui: /usr/lib/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found
version "5.36.0") 
-- Found KF5: success (found version "5.36.0") found components:  Archive
Codecs Config ConfigWidgets CoreAddons Crash DocTools GuiAddons IconThemes
ItemModels I18n JobWidgets KIO Solid Wallet WidgetsAddons WindowSystem XmlGui 
-- Found LibXml2: /usr/lib/libxml2.so (found version "2.9.4") 
-- Found LibXslt: /usr/lib/libxslt.so (found version "1.1.29") 
-- Checking for module 'qimageblitz>=5.0'
--   No package 'qimageblitz' found
-- Found taglib: -L/usr/lib -ltag
-- Taglib found: -L/usr/lib -ltag
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2") 
-- Checking for module 'yaz'
--   Found yaz, version 5.16.0
-- Found Yaz: /usr/include (Required is at least version "2.0") 
-- Found PopplerQt5: /usr/include/poppler/qt5  
-- Checking for module 'exempi-2.0'
--   Found exempi-2.0, version 2.2.1
-- Found Exempi: /usr/include/exempi-2.0 (Required is at least version "2.0") 
-- Could NOT find Btparse (missing: Btparse_INCLUDE_DIRS Btparse_LIBRARIES) 
-- Checking for module 'libdiscid'
--   Found libdiscid, version 0.6.1

[kexi] [Bug 348473] Kexi query parameters do not work in COLUMNS section

2017-07-24 Thread Jarosław Staniek
https://bugs.kde.org/show_bug.cgi?id=348473

--- Comment #3 from Jarosław Staniek  ---
Git commit 875de031fcfb785279c02f2e5c7d0d7555cb0cdb by Jaroslaw Staniek.
Committed on 24/07/2017 at 23:39.
Pushed by staniek into branch '3.0'.

Make Kexi query parameters also work in COLUMNS section

Port calligra.git's 5c0d3ee52fd:

Kexi query parameters do not work in COLUMNS section, e.g. this won't work
('invalid query' error appears):
SELECT [Param]

The parameters work only in the WHERE section, e.g. SELECT 123 WHERE [Param] =
1

Test Plan:
Test the query in the attached db
https://bugs.kde.org/show_bug.cgi?id=348473#c1

M  +4-4src/KDbNativeStatementBuilder.cpp
M  +12   -3src/KDbQuerySchema.cpp
M  +1-1src/KDbQuerySchemaParameter.h
M  +2-1src/parser/KDbParser_p.cpp

https://commits.kde.org/kdb/875de031fcfb785279c02f2e5c7d0d7555cb0cdb

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

[kmines] [Bug 382552] A cell with number (1) surrounded by 2 mines

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382552

waleed.lutf...@gmail.com changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #2 from waleed.lutf...@gmail.com ---
(In reply to Albert Astals Cid from comment #1)
> I don't see any 1 surrounded by two mines, which one do you mean?

Sorry Albert, my bad. Looking at the screenshot again, I belive I was mistaken.

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

[kmail2] [Bug 382659] KMail crashed on close

2017-07-24 Thread Allan Sandfeld
https://bugs.kde.org/show_bug.cgi?id=382659

Allan Sandfeld  changed:

   What|Removed |Added

 CC||k...@carewolf.com

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

[kmail2] [Bug 382659] KMail crashed on close

2017-07-24 Thread Allan Sandfeld
https://bugs.kde.org/show_bug.cgi?id=382659

--- Comment #1 from Allan Sandfeld  ---
Created attachment 106844
  --> https://bugs.kde.org/attachment.cgi?id=106844=edit
New crash information added by DrKonqi

kmail (5.5.90 rc) using Qt 5.9.1

- What I was doing when the application crashed:

Akonadi crashed after a system update of kde neon stable, and consistently
crashed on viewing the same folder. KMail would crash on existing with Akonadi
down.

-- Backtrace (Reduced):
#6  0x7fcb0ea7a80c in
KStatusNotifierItem::setStatus(KStatusNotifierItem::ItemStatus) () from
/usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#7  0x7fcb134747e9 in KMKernel::canQueryClose() () from
/usr/lib/x86_64-linux-gnu/libkmailprivate.so.5
#8  0x7fcb10cf5845 in KMainWindow::closeEvent(QCloseEvent*) () from
/usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#9  0x7fcb1255c6d8 in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7fcb1264e1cb in QMainWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

[kate] [Bug 369623] Kate Document dbus bindings missing

2017-07-24 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=369623

Christoph Cullmann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||cullm...@kde.org

--- Comment #2 from Christoph Cullmann  ---
Actually I would like to avoid having QDBus as dependency for the framework.

Exposing that to dbus might not be wanted by all applications embedding the
part, as this allows "unwanted" modifications of the document content without
any application control.

Actually, for your usecase, we always have swap files which will avoid any
data-loss, even on sudden system crashs.

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

[kde] [Bug 382632] Regression, Harald Sitter is missing a bowtie

2017-07-24 Thread Alex Fiestas
https://bugs.kde.org/show_bug.cgi?id=382632

--- Comment #3 from Alex Fiestas  ---
Created attachment 106843
  --> https://bugs.kde.org/attachment.cgi?id=106843=edit
With bowtie

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

[kate] [Bug 378085] Assertion failure in KateViewSpace during session shutdown

2017-07-24 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=378085

Christoph Cullmann  changed:

   What|Removed |Added

 CC||cullm...@kde.org

--- Comment #2 from Christoph Cullmann  ---
Hmm, document manager dies before all main windows.

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

[frameworks-ktexteditor] [Bug 370763] Error: Could not locate service type file kservicetypes5/ "kpart.desktop"

2017-07-24 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=370763

Christoph Cullmann  changed:

   What|Removed |Added

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

--- Comment #3 from Christoph Cullmann  ---
I just used the craft howto on mac.kde.org to rebuild, no problem with that
(and no need for patches).

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

[kate] [Bug 379008] Kate wiews painted blank grey when resuming session

2017-07-24 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=379008

Christoph Cullmann  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Cullmann  ---
Please retry with a current version, can't reproduce this.

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

[kate] [Bug 335855] code folding for python files misses some structures when body starts with empty lines

2017-07-24 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=335855

Christoph Cullmann  changed:

   What|Removed |Added

 CC||cullm...@kde.org

--- Comment #2 from Christoph Cullmann  ---
Valid bug, unfortunately ATM we only have one line look-ahead to 'know' if some
line should start a new folding section.

This means in these cases, that heuristic will fail, as the indentation level
is not increased (because empty lines are skipped for that).

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

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

2017-07-24 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=382570

--- Comment #20 from Luigi Toscano  ---
(In reply to Jack from comment #18)
> (In reply to Luigi Toscano from comment #17)
> > If you keep the left click button pushed, it opens the Bookmarks menu.
> 
> I find that odd, but it does work.  Clicking a menu item brings up it's menu
> almost immediately.  There is a notable delay (although still under a
> second) pushing on the toolbar button before the menu comes up.  Am I wrong
> to assume a simple click should work instead of needing an extended press?

>From what I know, it it expected. You should see a small icon with an arrow
pointing down in one of the corners. Anyway, not a KHelpCenter issue.

(In reply to svadkost from comment #19)
> (In reply to Luigi Toscano from comment #17)
> > If you keep the left click button pushed, it opens the Bookmarks menu.
> 
> Well, that's pretty strange way to do so. Maybe make it more
> straightforward? 

Same answer as before: that does not depend on KHelpCenter. If you use the
Oxygen theme for the widget, it is more clear that the widget is a button that
must be pushed. 

> And add something like in the okular - when you jump to a bookmark "add
> bookmark" is replaced by "remove bookmark", because there's no need to add
> more than one bookmark isn't there?
Maybe not straightforward, but...

> Also, i just found out that there's no way to delete bookmark folders, or i
> just don't see how.
... maybe enabling the link which opens KEditBookmarks should be enough.

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

[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner

2017-07-24 Thread Dominik Klementowski
https://bugs.kde.org/show_bug.cgi?id=381130

--- Comment #49 from Dominik Klementowski  ---
On Arch now with Plasma 5.10.4 packages this is not happening for me anymore.
Finally!

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

[kirigami] [Bug 382685] New: Android: pressing back with the global drawer open results in the application closing

2017-07-24 Thread Riccardo Iaconelli
https://bugs.kde.org/show_bug.cgi?id=382685

Bug ID: 382685
   Summary: Android: pressing back with the global drawer open
results in the application closing
   Product: kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: ricca...@kde.org
  Target Milestone: Not decided

Android: pressing back with the global drawer open results in the application
closing.

Expected behiavor: the drawer closes.

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

[ktorrent] [Bug 382684] New: After adding a torrent, ktorrent keeps crashing and became unusable

2017-07-24 Thread Dick Tracey
https://bugs.kde.org/show_bug.cgi?id=382684

Bug ID: 382684
   Summary: After adding a torrent, ktorrent keeps crashing and
became unusable
   Product: ktorrent
   Version: 5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: traceyd...@yandex.com
  Target Milestone: ---

After adding a few new torrents, ktorrent started crashing. It consistently
crashes after a second or so after I start it.

This is the output from valgrind with --track-origins=yes:

==7713== Thread 25 QThread:
==7713== Use of uninitialised value of size 8
==7713==at 0x9C4335C: QString::indexOf(QChar, int, Qt::CaseSensitivity)
const (in /usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x51A5F65: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51A6D93: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51A4507: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51A52A2: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x516787E: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x5163A23: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51629C9: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x5162550: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x5162588: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x9BBE15A: ??? (in /usr/lib/libQt5Core.so.5.9.1)
==7713==by 0xFC69048: start_thread (in /usr/lib/libpthread-2.25.so)
==7713==  Uninitialised value was created by a heap allocation
==7713==at 0x4C2E15F: realloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7713==by 0x9C19BC2: QListData::realloc_grow(int) (in
/usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x9C19C5F: QListData::append(int) (in
/usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x9BAD5C6: ??? (in /usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x9C4E5BD: QString::split(QString const&,
QString::SplitBehavior, Qt::CaseSensitivity) const (in
/usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x51A68B3: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51A4507: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51A52A2: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x516787E: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x5163A23: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51629C9: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x5162550: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713== 
==7713== Invalid read of size 4
==7713==at 0x9C4335C: QString::indexOf(QChar, int, Qt::CaseSensitivity)
const (in /usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x51A5F65: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51A6D93: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51A4507: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51A52A2: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x516787E: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x5163A23: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x51629C9: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x5162550: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x5162588: ??? (in /usr/lib/libktorrent.so.6.0.0)
==7713==by 0x9BBE15A: ??? (in /usr/lib/libQt5Core.so.5.9.1)
==7713==by 0xFC69048: start_thread (in /usr/lib/libpthread-2.25.so)
==7713==  Address 0x4 is not stack'd, malloc'd or (recently) free'd
==7713== 
KCrash: Application 'ktorrent' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
Mon Jul 24 17:57:26 2017: DHT: Got 1 potential peers for torrent 
Mon Jul 24 17:57:26 2017: Send error : Bad file descriptor
sock_file=/run/user/1000/kdeinit5__0
Mon Jul 24 17:57:27 2017: Qt Warning: QSocketNotifier: Invalid socket 17 and
type 'Read', disabling...
Warning: QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
==7713== Thread 4 utp::UTPServerTh:
==7713== Invalid read of size 2
==7713==at 0x9DFBF05: ??? (in /usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x121FA610: g_main_context_check (in
/usr/lib/libglib-2.0.so.0.5200.3)
==7713==by 0x121FABAF: ??? (in /usr/lib/libglib-2.0.so.0.5200.3)
==7713==by 0x121FAD1B: g_main_context_iteration (in
/usr/lib/libglib-2.0.so.0.5200.3)
==7713==by 0x9DFC060:
QEventDispatcherGlib::processEvents(QFlags) (in
/usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x9D9FFFA:
QEventLoop::exec(QFlags) (in
/usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x9BB940D: QThread::exec() (in /usr/lib/libQt5Core.so.5.9.1)
==7713==by 0x9BBE15A: ??? (in /usr/lib/libQt5Core.so.5.9.1)
==7713==by 0xFC69048: start_thread (in /usr/lib/libpthread-2.25.so)
==7713==by 0xABA5F0E: clone (in /usr/lib/libc-2.25.so)
==7713==  Address 0x2071c744 is 4 bytes inside a block of size 16 free'd
==7713==at 0x4C2D66B: operator delete(void*) (in

[plasmashell] [Bug 381130] Notifications are sometimes misplaced in the left upper corner

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=381130

--- Comment #48 from personaldesignertec...@gmail.com ---
Finally a bug fix, that solves fox X

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

[krita] [Bug 382660] Flickering when drawing on large canvases

2017-07-24 Thread wolthera
https://bugs.kde.org/show_bug.cgi?id=382660

wolthera  changed:

   What|Removed |Added

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

--- Comment #1 from wolthera  ---
That's instant preview.

You can turn it off: https://docs.krita.org/Instant_Preview

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

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

[krita] [Bug 361448] Brush strokes flicker when they finish rendering

2017-07-24 Thread wolthera
https://bugs.kde.org/show_bug.cgi?id=361448

wolthera  changed:

   What|Removed |Added

 CC||andr...@andreasresch.at

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

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

[krita] [Bug 382676] Cursor won't move when using XP-PEN Artist 22HD

2017-07-24 Thread wolthera
https://bugs.kde.org/show_bug.cgi?id=382676

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
This sadly sounds like a problem with the xppen drivers. We have seen the same
issues with the huion, ugee and yiynova drivers, all of which have been fixed
by updating the drivers.

So I'd recommend trying to update the tablet drivers or sending a message to
xp-pen if they could see if there's a fix.

We'll keep the report open, but there's very little we can do from here, I'm
afraid.

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

[kstars] [Bug 334039] kstars crash when try to make observing list

2017-07-24 Thread Jasem Mutlaq
https://bugs.kde.org/show_bug.cgi?id=334039

Jasem Mutlaq  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |UNMAINTAINED

--- Comment #3 from Jasem Mutlaq  ---
v2.2 of KStars is not maintained, please update to a newer version.

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

[frameworks-ktexteditor] [Bug 339627] vi input mode: Kate 3.14.1 (kubuntu 4.14.1 backport) crashes when saving files

2017-07-24 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=339627

Christoph Cullmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kte
   ||xteditor/900337e6864beb09e0
   ||eaed935de5ed89398363b8
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Christoph Cullmann  ---
Git commit 900337e6864beb09e0eaed935de5ed89398363b8 by Christoph Cullmann.
Committed on 24/07/2017 at 21:32.
Pushed by cullmann into branch 'master'.

perhaps avoid stringbuild crash

M  +1-1src/vimode/commandrangeexpressionparser.cpp

https://commits.kde.org/ktexteditor/900337e6864beb09e0eaed935de5ed89398363b8

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

[bugs.kde.org] [Bug 382683] New: Please add an item 'Manjaro' to the 'Platform' menu

2017-07-24 Thread Winfried Kusgoerd
https://bugs.kde.org/show_bug.cgi?id=382683

Bug ID: 382683
   Summary: Please add an item 'Manjaro' to the 'Platform' menu
   Product: bugs.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: database
  Assignee: sysad...@kde.org
  Reporter: w-kusgo...@t-online.de
CC: she...@kde.org
  Target Milestone: ---

Contra: Is that strictly necessary? The menu is already overcrowded.

Pro: Yes it is. Have a look at the page hit ranking at distrowatch.com :
 Manjaro is at number four among all linux distros.

Contra: But isn't it just a temporal phenomenon?

Pro: No, it isn't. Manjaro is at number three as to the 12 month average.
 It has a competent core team and an engaged and constantly growing
 community.
 The core team also works as one of the main contributors at the project
 calamares, the highly customizable and distribution-independent installer.

Contra: But it's an arch derivat and arch already is in the menu.

Pro: It is an arch derivat but unlike arch manjaro releases several different
 precisely preconfigured BINARY and TESTED desktop editions, three 
 core editions and several further community editions.
 They all run reliably out of the box (life and/or after installation).

 The KDE edition is one of the three core editions (and besides Neon
 one of the most popular and stable KDE-based distributions that 
 actually exist.)

 So if a Manjaro user/developer files a bug for a (binary!) KDE package
this
 is comparable to other binary distributions and has a higher significance
 than a bug filed for a self-compiled arch package (unknown compiling
 options ...). Therefore it's worth making a distinction between them.

(Additionally one can take into account to add another menu 'Branch' with
contains the entries 'stable', 'testing' and 'unstable' in order to
get the Platform-menu more clearly arranged.)

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

[kmail2] [Bug 382651] KMail reminds me of attachments to make when hitting the reply button

2017-07-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=382651

--- Comment #7 from Laurent Montel  ---
Ok thanks
it seems to be a bug when you reply as html.

I will investigate it.

Thanks

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

[plasmashell] [Bug 382682] New: Crash when copying to USB drive

2017-07-24 Thread PSK
https://bugs.kde.org/show_bug.cgi?id=382682

Bug ID: 382682
   Summary: Crash when copying to USB drive
   Product: plasmashell
   Version: 5.10.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: patr...@kyne.us
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.3)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.8-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Copying a file via Konquerer to USB drive.
I opened the System Tray icon to monitor the copy operation.
KDE Crashed.

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

Thread 17 (Thread 0x7fcd5097e700 (LWP 9023)):
#0  0x7fce3f3cf5dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fce4020304b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fce43f6a9e8 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fce43f6ae1a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fce40201d2e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fce3f3c94d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fce3fb0fb2f in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fcd51305700 (LWP 7663)):
#0  0x7fce3f3cf5dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fce4020304b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fce43f6a9e8 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fce43f6ae1a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fce40201d2e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fce3f3c94d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fce3fb0fb2f in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7fcd51c6c700 (LWP 7187)):
#0  0x7fce3f3cf5dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fce4020304b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fce43f6a9e8 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fce43f6ae1a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fce40201d2e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fce3f3c94d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fce3fb0fb2f in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7fcd529fd700 (LWP 6324)):
#0  0x7fce3f3cf5dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fce4020304b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fce43f6a9e8 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fce43f6ae1a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fce40201d2e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fce3f3c94d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fce3fb0fb2f in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fcd533fe700 (LWP 3999)):
#0  0x7fce3f3cf5dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fce4020304b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fce43f6a9e8 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fce43f6ae1a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fce40201d2e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fce3f3c94d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fce3fb0fb2f in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fcd53fff700 (LWP 3665)):
#0  0x7fce3f3cf5dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fce4020304b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fce43f6a9e8 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fce43f6ae1a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fce40201d2e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fce3f3c94d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fce3fb0fb2f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fcd6a94f700 (LWP 3664)):
#0  0x7fce3f3cf5dd in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fce4020304b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fce43f6a9e8 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7fce43f6ae1a in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fce40201d2e in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fce3f3c94d7 in start_thread () at /lib64/libpthread.so.0
#6  0x7fce3fb0fb2f in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fcd6a14e700 (LWP 2877)):
[KCrash Handler]
#6  0x56046b1200f0 in  ()
#7  0x7fce4335fe7f in 

[plasmashell] [Bug 382668] Fragment shader in UserDelegate.qml is not GLSL/ES compatible, missing precision specifier

2017-07-24 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=382668

David Edmundson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||k...@davidedmundson.co.uk
 Ever confirmed|0   |1

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

[kstars] [Bug 334039] kstars crash when try to make observing list

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=334039

--- Comment #2 from denis.ci...@gmail.com ---
Created attachment 106842
  --> https://bugs.kde.org/attachment.cgi?id=106842=edit
New crash information added by DrKonqi

kstars (2.2.0) on KDE Platform 4.14.30 using Qt 4.8.6

- What I was doing when the application crashed:

Creating an observation list. Everytime on final validation.

-- Backtrace (Reduced):
#5  0x006558e7 in ObsListWizard::applyFilters(bool) ()
[...]
#7  0x7f52dbed8f50 in KDialog::slotButtonClicked(int) () from
/lib64/libkdeui.so.5
[...]
#10 0x7f52db29808e in QSignalMapper::mapped(int) () from
/lib64/libQtCore.so.4
#11 0x7f52db298196 in QSignalMapper::map(QObject*) () from
/lib64/libQtCore.so.4
[...]
#13 0x7f52dac62e92 in QAbstractButton::clicked(bool) () from
/lib64/libQtGui.so.4

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

[kstars] [Bug 334039] kstars crash when try to make observing list

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=334039

denis.ci...@gmail.com changed:

   What|Removed |Added

 CC||denis.ci...@gmail.com

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

[dragonplayer] [Bug 382681] New: Crash playing a larger quicktime movie

2017-07-24 Thread rainer
https://bugs.kde.org/show_bug.cgi?id=382681

Bug ID: 382681
   Summary: Crash playing a larger quicktime movie
   Product: dragonplayer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: kdeb...@munin-soft.de
CC: myr...@kde.org
  Target Milestone: ---

Application: dragon (17.04.2)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.8-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I played a larger (>700MB) quicktime movie. The crash happened when the movie
finished playing. I think the crash is not specific to this particular one (as
I have a series of four movies and occasional crashes with some of them, but
maybe they have something (problematic?) in common, as they were created by the
samemobile device (AFAIK).

-- Backtrace:
Application: Dragon Player (dragon), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5bc2f29d80 (LWP 16963))]

Thread 3 (Thread 0x7f5ba54a2700 (LWP 16965)):
#0  0x7f5bb930618b in g_main_context_prepare
(context=context@entry=0x7f5ba9b0, priority=priority@entry=0x7f5ba54a1b70)
at gmain.c:3514
#1  0x7f5bb9306c4b in g_main_context_iterate
(context=context@entry=0x7f5ba9b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3952
#2  0x7f5bb9306e2c in g_main_context_iteration (context=0x7f5ba9b0,
may_block=1) at gmain.c:4033
#3  0x7f5bbee486ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5bbedf135a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5bbec2131a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f5bbf2cba45 in QDBusConnectionManager::run() () at
/usr/lib64/libQt5DBus.so.5
#7  0x7f5bbec25d2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f5bbb9584d7 in start_thread (arg=0x7f5ba54a2700) at
pthread_create.c:456
#9  0x7f5bbe221b2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 2 (Thread 0x7f5bace49700 (LWP 16964)):
#0  0x7f5bbe21818d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5bbb51d387 in poll (__timeout=-1, __nfds=1, __fds=0x7f5bace48bc8)
at /usr/include/bits/poll2.h:46
#2  0x7f5bbb51d387 in _xcb_conn_wait (c=c@entry=0x55cad3320ee0,
cond=cond@entry=0x55cad3320f20, vector=vector@entry=0x0, count=count@entry=0x0)
at xcb_conn.c:479
#3  0x7f5bbb51f16a in xcb_wait_for_event (c=0x55cad3320ee0) at xcb_in.c:693
#4  0x7f5baf9ef449 in QXcbEventReader::run() () at
/usr/lib64/libQt5XcbQpa.so.5
#5  0x7f5bbec25d2e in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f5bbb9584d7 in start_thread (arg=0x7f5bace49700) at
pthread_create.c:456
#7  0x7f5bbe221b2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 1 (Thread 0x7f5bc2f29d80 (LWP 16963)):
[KCrash Handler]
#6  0x7f5bbe168a90 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7f5bbe16a0f6 in __GI_abort () at abort.c:78
#8  0x7f5bb6ff3339 in  () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so
#9  0x7f5bb6ff3d3f in pa_fdsem_after_poll () at
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#10 0x7f5bb700b74d in  () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so
#11 0x7f5bbaeb7fb0 in  () at /usr/lib64/libpulse-mainloop-glib.so.0
#12 0x7f5bb9306b67 in g_main_dispatch (context=0x7f5ba8001710) at
gmain.c:3234
#13 0x7f5bb9306b67 in g_main_context_dispatch
(context=context@entry=0x7f5ba8001710) at gmain.c:3899
#14 0x7f5bb9306d98 in g_main_context_iterate
(context=context@entry=0x7f5ba8001710, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3972
#15 0x7f5bb9306e2c in g_main_context_iteration (context=0x7f5ba8001710,
may_block=1) at gmain.c:4033
#16 0x7f5bbee4868f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#17 0x7f5bbedf135a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#18 0x7f5bbedf9be4 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#19 0x55cad172bcae in main(int, char**) (argc=,
argv=) at /usr/src/debug/dragon-17.04.2/src/app/main.cpp:91

Reported using DrKonqi

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

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

2017-07-24 Thread svadkost
https://bugs.kde.org/show_bug.cgi?id=382570

--- Comment #19 from svadkost  ---
(In reply to Luigi Toscano from comment #17)
> If you keep the left click button pushed, it opens the Bookmarks menu.

Well, that's pretty strange way to do so. Maybe make it more straightforward? 

And add something like in the okular - when you jump to a bookmark "add
bookmark" is replaced by "remove bookmark", because there's no need to add more
than one bookmark isn't there?

Also, i just found out that there's no way to delete bookmark folders, or i
just don't see how.

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

[plasma-integration] [Bug 374913] Open does use directory for currently open file with sftp://

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=374913

--- Comment #6 from pyrk...@go2.pl ---
Bug fix https://codereview.qt-project.org/#/c/182661/2 is still unreviewed
because of coding style issues. Because it is serious issue for KDE, please
resubmit it with required changes. Thanks.

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

[kdevelop] [Bug 382652] Navigate to breakpoint not working

2017-07-24 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=382652

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.1.2
  Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde
   |vplatform/6c6329f2373e43ca6 |vplatform/b4770057b79a02f77
   |a9aa4886c4e7c1d0e75975e |cc5d0500ac6edc5837a2103

--- Comment #2 from Kevin Funk  ---
Git commit b4770057b79a02f77cc5d0500ac6edc5837a2103 by Kevin Funk, on behalf of
Sven Brauch.
Committed on 24/07/2017 at 20:43.
Pushed by kfunk into branch '5.1'.

make breakpoint "location" non-editable in item model

fixes

Clicking the location is the more useful behaviour than editing
the line number by hand. I don't see why you would want to do that.

(cherry picked from commit 6c6329f2373e43ca6a9aa4886c4e7c1d0e75975e)

M  +1-2debugger/breakpoint/breakpointmodel.cpp

https://commits.kde.org/kdevplatform/b4770057b79a02f77cc5d0500ac6edc5837a2103

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

[kdevelop] [Bug 382652] Navigate to breakpoint not working

2017-07-24 Thread Kevin Funk
https://bugs.kde.org/show_bug.cgi?id=382652

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.1.2

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

[tellico] [Bug 382680] New: 3.0.2 release build fails with cmake 3.9

2017-07-24 Thread rezso
https://bugs.kde.org/show_bug.cgi?id=382680

Bug ID: 382680
   Summary: 3.0.2 release build fails with cmake 3.9
   Product: tellico
   Version: 3.0.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ro...@periapsis.org
  Reporter: re...@rezso.net
  Target Milestone: ---

I can compile the 3.0.2 release with cmake 3.7.2, but compiling with cmake 3.9
fails:

-- Configuring done
CMake Error: The inter-target dependency graph contains the following strongly
connected component (cycle):
  "core" of type STATIC_LIBRARY
depends on "images" (weak)
depends on "utils" (weak)
depends on "core_autogen" (strong)
  "core_autogen" of type UTILITY
depends on "images" (strong)
depends on "utils" (strong)
  "images" of type STATIC_LIBRARY
depends on "core" (weak)
depends on "utils" (weak)
depends on "images_autogen" (strong)
  "images_autogen" of type UTILITY
depends on "core" (strong)
depends on "utils" (strong)
  "utils" of type STATIC_LIBRARY
depends on "images" (weak)
depends on "core" (weak)
depends on "utils_autogen" (strong)
  "utils_autogen" of type UTILITY
depends on "images" (strong)
At least one of these targets is not a STATIC_LIBRARY.  Cyclic dependencies are
allowed only among static libraries.

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

[dolphin] [Bug 382669] Image preview on a webdav folder

2017-07-24 Thread Elvis Angelaccio
https://bugs.kde.org/show_bug.cgi?id=382669

--- Comment #1 from Elvis Angelaccio  ---
Previews of remote files are disabled by default, you can enable them in
Settings -> General -> Previews.

Maybe nowadays this could be reconsidered though. Or maybe the Preview action
should have a tooltip explaining why the previews are not working on remote
folders.

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

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

2017-07-24 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=382570

Jack  changed:

   What|Removed |Added

 CC|ostroffjh@users.sourceforge |
   |.net|

--- Comment #18 from Jack  ---
(In reply to Luigi Toscano from comment #17)
> If you keep the left click button pushed, it opens the Bookmarks menu.

I find that odd, but it does work.  Clicking a menu item brings up it's menu
almost immediately.  There is a notable delay (although still under a second)
pushing on the toolbar button before the menu comes up.  Am I wrong to assume a
simple click should work instead of needing an extended press?

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

[krita] [Bug 382633] Crash while using Text Editor

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382633

--- Comment #2 from gibon...@gmail.com ---
Nope. It doesn't crash with krita-3.2.0-beta.2-x86_64.appimage.

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

[plasmashell] [Bug 382668] Fragment shader in UserDelegate.qml is not GLSL/ES compatible, missing precision specifier

2017-07-24 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=382668

Martin Flöser  changed:

   What|Removed |Added

Product|plasma-integration  |plasmashell
  Component|general |Look & Feel package
   Assignee|mgraess...@kde.org  |plasma-b...@kde.org
 CC||plasma-b...@kde.org
   Target Milestone|--- |1.0

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

[kde] [Bug 382632] Regression, Harald Sitter is missing a bowtie

2017-07-24 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=382632

--- Comment #2 from Aleix Pol  ---
Created attachment 106841
  --> https://bugs.kde.org/attachment.cgi?id=106841=edit
No bowtie

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

[kde] [Bug 382632] Regression, Harald Sitter is missing a bowtie

2017-07-24 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=382632

Aleix Pol  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||aleix...@kde.org

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

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

2017-07-24 Thread ocumo
https://bugs.kde.org/show_bug.cgi?id=382628

--- Comment #4 from ocumo  ---
I have created the bug report and workaround in the gmic community site, as
suggested by Boudewijn.

It's been assigned the number 87.

Here is the link:

https://github.com/dtschump/gmic-community/issues/87

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

[kwin] [Bug 382050] MinimizeAll script / Minimize Windows widget affects all activities

2017-07-24 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=382050

--- Comment #5 from Martin Flöser  ---
Totally honest answer: we don't have the resources to implement user wishes.

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

[kate] [Bug 382679] New: Non-greedy regular expressions are not supported

2017-07-24 Thread Victor Porton
https://bugs.kde.org/show_bug.cgi?id=382679

Bug ID: 382679
   Summary: Non-greedy regular expressions are not supported
   Product: kate
   Version: 16.08
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: search
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: por...@narod.ru
  Target Milestone: ---

Kate seems not to support non-greedy mode (available for example in Perl by
appending a question sign to a part of an expression) of regular expressions,
as in the following example of a regular expression:

%%(.*?)%%

Please add support for such expressions.

Kate 16.08.3.

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

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

2017-07-24 Thread ocumo
https://bugs.kde.org/show_bug.cgi?id=382628

--- Comment #3 from ocumo  ---
(In reply to Boudewijn Rempt from comment #2)

--
Hi Boudewijn,
Thank you for having a look and for good suggestion. I'll do.

I was not sure to what extent this bug would be better owned by you guys as
direct "consumer" and "co-implementers"/partners of the new feature from what I
understood in the announcement of 3.2-, since it is an actual button in Krita
(and a newly announced, important one) that doesn't work.

Obviously I gladly will report (copy) this on the gmic forum as you suggest; I
appreciate that no one exactly loves taking ownership of problems that might be
a bigger percentage (even all) of responsibility of others. I've done that
professionally for long time. But Krita's site says: "We’re still working with
them to create binary builds...", which implies partnership, strongly
suggesting that somehow this bug does relate to all the good people working
hard to produce a nice 3.2 final product (though it doesn't imply that they are
necessarily the "causers").

Please don't get me wrong: I'll report this wherever you tell me it's the best
place to help devs to get their goals done, for the benefit of everybody. But
still it should also exists here.

Please just let me observe -with appreciation- that Krita's users should be
aware or notified in the first place, that this bug affects Krita, no matter
who's technically the final owner. As users of Krita, (exactly as say, our own
car) we interact with Krita and when one of its major features is broken, we
immediately see a bug in Krita. 

We (users) don't ought to know who's the one taking care of environmental
variables, dependencies, or what not in a plugin partnership. Same with our own
car. We don't know who should be inquired about a failing pump, other than the
car's manufacturer. That's regardless of whether the issue is caused by the guy
who installed it in the car, or a pump manufacturer's mistake, or a supplier of
a sub-assembly of that third party (so, a fourth party), etc. But: my car is
broken. I'd complain to the car's vendor, period. Who wouldn't?  (Disclaimer:
this example is for mere illustration, as a metaphor: it's NOT a comparison by
any means! you guys are NOT a rich corporation that gets good money for their
products Most people won't give you any money at all for Krita.)

It's in that spirit that I decided to report in the first place (but not the
last one!) here. That said:

Thank you, again, for all you do to provide us with such an incredible and ever
improving, formidable software called Krita!

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

[kdenlive] [Bug 382678] 3 point balance does not work on a track

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382678

stuart.rowla...@yahoo.co.uk changed:

   What|Removed |Added

   Severity|normal  |minor

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

[kdenlive] [Bug 382678] 3 point balance does not work on a track

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382678

stuart.rowla...@yahoo.co.uk changed:

   What|Removed |Added

   Severity|minor   |normal
Version|unspecified |17.04.1

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

[kdenlive] [Bug 382678] New: 3 point balance does not work on a track

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382678

Bug ID: 382678
   Summary: 3 point balance does not work on a track
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: stuart.rowla...@yahoo.co.uk
  Target Milestone: ---

3 point balance works on a clip, but if applied to a track the ink drop fails
to appear and the effect is disabled.

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

[digikam] [Bug 382677] New: Rating groups by mouse only changes first item.

2017-07-24 Thread Alexander
https://bugs.kde.org/show_bug.cgi?id=382677

Bug ID: 382677
   Summary: Rating groups by mouse only changes first item.
   Product: digikam
   Version: 5.6.0
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: alexander.nofamilyn...@gmx.net
  Target Milestone: ---

If you group items and you have metadata group edit enabled rating a group only
works if you use the shortcuts (ctrl 0-5). If you use the mouse to change the
stars of a group only the first item in the group gets rated.

This is serious imo because you will get metadata inconsistency if you use your
mouse to change a rating.

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

[krita] [Bug 382676] New: Cursor won't move when using XP-PEN Artist 22HD

2017-07-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=382676

Bug ID: 382676
   Summary: Cursor won't move when using XP-PEN Artist 22HD
   Product: krita
   Version: 3.1.4
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: olivias...@comic.com
  Target Milestone: ---

Created attachment 106840
  --> https://bugs.kde.org/attachment.cgi?id=106840=edit
An example of the constant lines interrupting the drawing process

When trying to use the program, the cursor will not move with my stylus pen. I
can draw, but when I do it creates lines all through the drawing connecting all
the points the cursor has been.

I.E. The cursor is frozen in the top right corner, and I try to draw in the
centre. It will then draw a line from where the cursor was frozen, to wherever
I begin drawing next.

I can still use the program, but have to spend copious amounts of time when I'm
finished drawing to erase all the lines that this problem creates, making the
usage of this program very frustrating.

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

[plasmashell] [Bug 382675] New: Plasma (plasmashell), signal: Illegal instruction - QHashData::shared_null () at /usr/lib64/libQt5Core.so.5

2017-07-24 Thread Don Curtis
https://bugs.kde.org/show_bug.cgi?id=382675

Bug ID: 382675
   Summary: Plasma (plasmashell), signal: Illegal instruction -
QHashData::shared_null () at
/usr/lib64/libQt5Core.so.5
   Product: plasmashell
   Version: 5.8.6
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugrprt21...@online.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.74-18.20-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:

Locking the KDE session by means of the Application Menu -- Shortcut key was
not used.

-- Backtrace:
Application: Plasma (plasmashell), signal: Illegal instruction
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3c91016900 (LWP 21715))]

Thread 18 (Thread 0x7f3b8dffb700 (LWP 32340)):
#0  0x7f3c89cd00bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3c8abd365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f3bcde0842f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f3bcde0bdea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7f3bcde09a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7f3c8abd29e9 in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f3c89ccb744 in start_thread () at /lib64/libpthread.so.0
#18 0x7f3c8a4d4aad in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f3b8e7fc700 (LWP 32339)):
#0  0x7f3c89cd00bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3c8abd365b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f3bcde0842f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f3bcde0bdea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f3bcde0be32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f3bcde0645b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7f3bcde09a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7f3c8abd29e9 in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f3c89ccb744 in start_thread () at /lib64/libpthread.so.0
#18 0x7f3c8a4d4aad in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f3b8effd700 (LWP 32338)):
#0  

[digikam] [Bug 365684] Tags Manager : Crash when deleting a tag from the list of tags

2017-07-24 Thread Olli Lupton
https://bugs.kde.org/show_bug.cgi?id=365684

Olli Lupton  changed:

   What|Removed |Added

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

--- Comment #26 from Olli Lupton  ---
Apologies for not following up with this.

I am now on 3.6.0 and no longer see this bug.

Since I could reproduce it I had to rebuild my library from scratch, so it's
not clear whether the newer digikam version actually fixed the problem, or if
was due to funny state of the database.

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

[kate] [Bug 382674] Wrong arrow key navigation in a file with Hebrew text

2017-07-24 Thread Victor Porton
https://bugs.kde.org/show_bug.cgi?id=382674

--- Comment #1 from Victor Porton  ---
Created attachment 106839
  --> https://bugs.kde.org/attachment.cgi?id=106839=edit
The file which triggers the error

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

[kate] [Bug 382674] New: Wrong arrow key navigation in a file with Hebrew text

2017-07-24 Thread Victor Porton
https://bugs.kde.org/show_bug.cgi?id=382674

Bug ID: 382674
   Summary: Wrong arrow key navigation in a file with Hebrew text
   Product: kate
   Version: 16.08
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: por...@narod.ru
  Target Milestone: ---

Open the attached file error.txt.

With mouse put the cursor at the rightmost position at the second line of the
file.

Press arrow key Right a few times. This causes the cursor jump to the rightmost
position of the first line and back.

It is not logical that the cursor is moved by the same arrow key in different
directions.

I think, the bug is related to Hebrew characters in the fie.

Kate 16.08.3.

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

  1   2   3   4   >