[plasmashell] [Bug 374162] Add an option to sort programs chronologically in task bar, when grouping

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |NEEDSINFO

--- Comment #2 from Eike Hein  ---
Setting to NEEDSINFO.

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

[plasmashell] [Bug 374162] Add an option to sort programs chronologically in task bar, when grouping

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

   Severity|normal  |wishlist

--- Comment #1 from Eike Hein  ---
Actually not entirely sure I follow, why can't you set sorting to manual and
enable grouping and inline grouping?

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

[plasmashell] [Bug 360219] Right Click opens files

[Eike Hein]

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

--- Comment #38 from Eike Hein  ---
Patch seems fine, please commit Kai.

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

[plasmashell] [Bug 373544] Task manager: no text on small items

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Eike Hein  ---
Ok, so I think there's something more to consider here, namely vertical panels.
With the current value of 7, with most common vertical panel widths, the text
label will currently be collapsed, leaving only the icons. If I lower the value
to 3, many common vertical panel widths will end up with (very little) text
shown. On the face of it this makes sense, since wanting text labels is a
reason to use the regular Task Manager over the Icons-only version, and people
who don't want text could just use Icons-only. However for historical reasons,
there's more difference between the two applets than that ... the ITM has
slightly different default options and slightly different (less) settings
available, as it's our "this satisfies your dock cravings" applet.

Basically, if I lower this value to 3 as the only change, I know it's going to
piss some users off who want a "clean" icon task bar in ther vert panel but
still regular TM behavior and options. Instead I could go with 5, which is just
outside typical panel widths used by such users. That's the lowest I could go
without opening this can of worms for now (which may have to be opened
eventually).

Please try this out with:

  plasmoidviewer --formfactor vertical --applet org.kde.plasma.taskmanager

And let me know your opinions.

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

[plasmashell] [Bug 373860] Plasmoids cannot be placed at the screen edge

[Alexander Schier]

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

--- Comment #12 from Alexander Schier  ---
Yes, then it seems like intentional behaviour, which just changed.

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

[plasmashell] [Bug 373860] Plasmoids cannot be placed at the screen edge

[Eike Hein]

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

--- Comment #11 from Eike Hein  ---
This might be it, but it could also be two other reasons:

(a) Invisible margin in the Plasma theme outside the visible edge of the widget
frame
(b) For some reason (e.g.: intentionally for aesthetic reasons) widgets aren't
allowed to be placed in the last cell

Needs actually looking at the code.

Now, personally I will say that I think some extra margin is nice aesthetically
...

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

[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond

[Jan Pavlicek]

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

Jan Pavlicek  changed:

   What|Removed |Added

 CC|jan.pavli...@centrum.cz |

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

[plasmashell] [Bug 374291] regression: folder view popup disappears when touched by mouse cursor

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/pla
   ||sma-desktop/e80a4b87cfa9870
   ||8724942794ca6f051974bb5c0

--- Comment #2 from Eike Hein  ---
Git commit e80a4b87cfa98708724942794ca6f051974bb5c0 by Eike Hein.
Committed on 03/01/2017 at 07:30.
Pushed by hein into branch 'Plasma/5.8'.

Don't clear hover state while a child dialog is open.

Otherwise it won't stay open.

Fixes regression from 7585f295363532eff51f7e11ef6b62925117aba4.

The bug number referenced in the original change is invalid, but
I don't think this should invalidate the intent of that fix. Kai
please let me know the correct bug number so I can double-check.
CCMAIL:k...@privat.broulik.de

M  +4-1containments/desktop/package/contents/ui/FolderView.qml

https://commits.kde.org/plasma-desktop/e80a4b87cfa98708724942794ca6f051974bb5c0

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

[plasmashell] [Bug 373860] Plasmoids cannot be placed at the screen edge

[Alexander Schier]

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

--- Comment #10 from Alexander Schier  ---
Ah, that's quite possible, that the grid does not end on the exact screen edge
and the widget aligns with the bottom line of the grid instead of the bottom of
the screen.

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

[plasmashell] [Bug 374481] Clicking on icons with multiple windows from a different activity does nothing

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Eike Hein  ---
Doing nothing is certainly unexpected. Normally the "Present Windows" effect
should engage, and if the effect is not available, the popup dialog with the
list should appear as in the standard TM. What are you Desktop Effecs settings?

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

[plasmashell] [Bug 374481] New: Clicking on icons with multiple windows from a different activity does nothing

[Shitikanth]

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

Bug ID: 374481
   Summary: Clicking on icons with multiple windows from a
different activity does nothing
   Product: plasmashell
   Version: 5.8.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: golu3...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Expected behavior: It should switch to the most recently used window of the
application, or at least show a list of windows of the application that the
user can select from (this is the behavior of the standard task manager).

Steps to Reproduce:
1. Use icon only task manager
2. Open multiple instances of an application
3. Go to a different activity
4. Click on that application's icon

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

[plasmashell] [Bug 374310] Cannot build plasma-desktop without AppStreamQt installed

[Omar Plummer]

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

--- Comment #2 from Omar Plummer  ---
(In reply to David Edmundson from comment #1)
> >Suggestion: Would it not be more fitting to implement this functionality as 
> >part of the Discover framework?
> 
> In the context of the patch, it would not.


Is it official then, that the AppStream dependency will be non-optional?

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

[krita] [Bug 359128] Add improved transformation filters (perspective transformation blurs the image)

[Boudewijn Rempt]

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

--- Comment #6 from Boudewijn Rempt  ---
Hi Alexandre,

No, this hasn't been implemented yet. The code that actually implements the
filters is in libs/image/kis_filter_strategy.h. Using Qt Creator it's easy to
figure out from where these filters are used. There are, for instance, four
unittests in libs/image/tests:

kis_filter_strategy_test.cpp:#include "kis_filter_strategy.h"
kis_filter_weights_buffer_test.cpp:#include "kis_filter_strategy.h"
kis_processings_test.cpp:#include "kis_filter_strategy.h"
kis_transform_worker_test.cpp:#include "kis_filter_strategy.h"

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

[dolphin] [Bug 374480] should show icons in gnome

[bugzilla_noreply]

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

solot...@gmail.com changed:

   What|Removed |Added

   Severity|critical|major

--- Comment #1 from solot...@gmail.com ---
setting to major, but only for non-kde platforms.

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

[amarok] [Bug 374331] audiocd cannot be opened out of gnome

[bugzilla_noreply]

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

--- Comment #2 from solot...@gmail.com ---
with gnome file browser you mean something like nautilus or nemo? there it
works. it does not work inside amarok. XDG_CURRENT_DESKTOP is GNOME.

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

[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond

[Martin Kostolný]

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

--- Comment #23 from Martin Kostolný  ---
I, on the other hand, cannot replicate it on Arch Linux. I've created a new
user and tried with empty home folder. Activated mouse gestures with mouse
button 3 (right mouse button), added a gesture to send keyboard input Ctrl+w
and it is successfully closing tabs e.g. in Dolphin. Right mouse button single
clicking continues to open context menus.

Package versions:
Plasma 5.8.5
KF 5.29
Xorg (not tested on wayland)

Have you tried with clean config? Probably not related but: what kind of
gestures do you have? I'll try to test it on Neon later.

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

[plasmashell] [Bug 374447] Moving a window around the same desktop should be optional

[Eike Hein]

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

--- Comment #3 from Eike Hein  ---
How about we just disable window moving outright? Does anyone rely on moving
their windows on a square centimeter Pager?

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

[dolphin] [Bug 374480] New: should show icons in gnome

[bugzilla_noreply]

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

Bug ID: 374480
   Summary: should show icons in gnome
   Product: dolphin
   Version: 16.12.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: solot...@gmail.com
  Target Milestone: ---

dolphin in arch linux with gnome wayland as described here:
https://wiki.archlinux.org/index.php/GNOME#Wayland_sessions

does not show icons, except for "downloads" and . i read some threads but
nothing did the trick:
* https://forum.kde.org/viewtopic.php?f=224=128749
* https://wiki.archlinux.org/index.php/Qt#GTK.2B_and_Qt

what am i overlooking?

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

[plasmashell] [Bug 373860] Plasmoids cannot be placed at the screen edge

[Eike Hein]

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

--- Comment #9 from Eike Hein  ---
I think what's going on is that Plasma 4 allowed you to place widgets freely on
every pixel, but we had countless user requests that this made it hard to line
widgets up nicely, so we implemented a grid system. After dragging widgets may
slide slightly to align to the nearest cell.

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

[plasmashell] [Bug 374094] Avoid cells overlapping widgets when deciding initial placement of new icons in desktop containment mode (perhaps optionally)

[Eike Hein]

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

--- Comment #9 from Eike Hein  ---
Hint to interested implementers: The Positioner class contains a firstFreeRow()
method that is used to find free space to initially place new icons in the
positioning proxy. To implement this request, Positioner would have to be made
aware of the (QML level) containment code's occupied widget cells tracking
state and consider icon grid cells overlapping occupied widget cells as
non-free, just as icon grid cells already containing an icon are. It should
then return an icon grid cell that's neither occupied by an icon or overlapping
an occupied widget grid cell, taking arrangement and alignment settings into
account as before.

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

[plasmashell] [Bug 374479] New: Plasma crash on changing display layout with multimonitors

[Kiran]

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

Bug ID: 374479
   Summary: Plasma crash on changing display layout with
multimonitors
   Product: plasmashell
   Version: 5.8.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kiran.sebast...@vodoke.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.14-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
Pressing Fn+F7 on Thinkpad X220 to change desktop display configuration

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

Thread 8 (Thread 0x7f3b13ffe700 (LWP 9278)):
#0  0x7f3c04866743 in QElapsedTimer::isMonotonic () at
tools/qelapsedtimer_unix.cpp:154
#1  0x7f3c049e334e in QTimerInfoList::repairTimersIfNeeded
(this=0x7f3af4071210) at kernel/qtimerinfo_unix.cpp:162
#2  0x7f3c049e33c3 in QTimerInfoList::timerWait (this=0x7f3af4071210,
tm=...) at kernel/qtimerinfo_unix.cpp:389
#3  0x7f3c049e475e in timerSourcePrepareHelper (timeout=0x7f3b13ffdb14,
src=) at kernel/qeventdispatcher_glib.cpp:132
#4  timerSourcePrepare (source=, timeout=0x7f3b13ffdb14) at
kernel/qeventdispatcher_glib.cpp:165
#5  0x7f3bff158d79 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f3bff15979b in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7f3bff15998c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#8  0x7f3c049e518b in QEventDispatcherGlib::processEvents
(this=0x7f3af4052290, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#9  0x7f3c0498eaea in QEventLoop::exec (this=this@entry=0x7f3b13ffdce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#10 0x7f3c047bc813 in QThread::exec (this=) at
thread/qthread.cpp:507
#11 0x7f3c07ae8305 in ?? () from /usr/lib64/libQt5Qml.so.5
#12 0x7f3c047c14c8 in QThreadPrivate::start (arg=0x40e5580) at
thread/qthread_unix.cpp:368
#13 0x7f3c038c7454 in start_thread () from /lib64/libpthread.so.0
#14 0x7f3c040ce37f in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f3b3ed65700 (LWP 2300)):
#0  0x7f3c040c16dd in read () from /lib64/libc.so.6
#1  0x7f3bff19db00 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f3bff159325 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f3bff159814 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f3bff15998c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f3c049e518b in QEventDispatcherGlib::processEvents
(this=0x7f3b380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7f3c0498eaea in QEventLoop::exec (this=this@entry=0x7f3b3ed64cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7f3c047bc813 in QThread::exec (this=) at
thread/qthread.cpp:507
#8  0x7f3b41292df7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#9  0x7f3c047c14c8 in QThreadPrivate::start (arg=0x3eacc80) at
thread/qthread_unix.cpp:368
#10 0x7f3c038c7454 in start_thread () from /lib64/libpthread.so.0
#11 0x7f3c040ce37f in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f3b52012700 (LWP 2293)):
#0  0x7f3c040c566d in poll () from /lib64/libc.so.6
#1  0x7f3bff159876 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f3bff15998c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f3c049e518b in QEventDispatcherGlib::processEvents
(this=0x7f3b4c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3c0498eaea in QEventLoop::exec (this=this@entry=0x7f3b52011c90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f3c047bc813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f3c086772d6 in ?? () from /usr/lib64/libQt5Quick.so.5
#7  0x7f3c047c14c8 in QThreadPrivate::start (arg=0x17e5100) at
thread/qthread_unix.cpp:368
#8  0x7f3c038c7454 in start_thread () from /lib64/libpthread.so.0
#9  0x7f3c040ce37f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f3be49ee700 (LWP 2283)):
#0  0x7f3c038cd10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3c0a108974 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f3c0a1089b9 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f3c038c7454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f3c040ce37f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f3be67b2700 (LWP 2282)):
#0  0x7f3bff19eec4 in g_mutex_unlock () from 

[plasmashell] [Bug 374094] Avoid cells overlapping widgets when deciding initial placement of new icons in desktop containment mode (perhaps optionally)

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
Summary|plasmoids cover icons   |Avoid cells overlapping
   ||widgets when deciding
   ||initial placement of new
   ||icons in desktop
   ||containment mode (perhaps
   ||optionally)
   Severity|normal  |wishlist

--- Comment #8 from Eike Hein  ---
Let's go with a compromise - I'll set this to wishlist and change the ticket
title a bit to capture your intent better.

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

[plasmashell] [Bug 374443] Kicker popup doesn't appear when other windows are on screen

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

Summary|Popup not usable (closes|Kicker popup doesn't appear
   |immediately) with focus |when other windows are on
   |follows mouse   |screen

--- Comment #10 from Eike Hein  ---
Ok, then there is some other reason.

I mean, of course this isn't a common bug. I can't reproduce it and you're the
first person to report it. I still think it must be some sort of unique setting
on your end, so we need to find out which it is ...

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

[kmail2] [Bug 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)

[Vishnu]

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

Vishnu  changed:

   What|Removed |Added

 CC||vishn...@gmail.com

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

[plasmashell] [Bug 374402] startkde and qdbus-- logic in startkde make no sense

[bugzilla_noreply]

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

--- Comment #4 from un...@physics.ubc.ca ---
I disagree. startkde crashing makes the whole system inoperable. That situation
should not happen. If qdbus cannot be found, then startkde crashes. This will
happen if for exqmple the path to qdbus is not in the PATH.  On my system, it
is in /usr/lib{,64}/qt5/bin and that is not a directory anyone would expect to
have to be in the PATH. It never hs before and the lib directories should not
be expected to be there. 
startkde needs to do a much better job of searching for qdbus than it does, and
needs to throw a far more informative error message if it cannot find it. 
To blame the distributors for a crash which makes the system almost inoperative
really should not be acceptable.

Note that there IS an issue. I and many others have had startkde crash on them
because it turns out that /usr/lib64/qt5/bin was not in the PATH. To expect the
user (or even the distrutor) to know this is asking too much of them,
especially when the error message thrown by the crash is incomprehensible.

I cannot reopen this bug, but feel it should be reopened.

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

[systemsettings] [Bug 371772] kfontinst stuck process/dialog after trying to install multiple .otf fonts from Dolphin

[Beer]

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

--- Comment #3 from Beer  ---
This happened again and I can confirm now that it doesn't have anything to do
with multiple fonts.  I tried to install a single font and the same issue
happened.  

How can I install a font from the command line so that uses the same method as
"right click>install" from Dolphin so maybe I can get it to spit out an error?

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

[kate] [Bug 374478] New: Kate project plugin ignores git worktrees

[bugzilla_noreply]

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

Bug ID: 374478
   Summary: Kate project plugin ignores git worktrees
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: dennis.lis...@gmail.com
  Target Milestone: ---

Kate project plugin detects a Git-based project by checking whether `.git`
exists and is a directory.

However, if the git checkout is a separate worktree attached to an external
repository[0], `.git` is actually a file with contents like
```
gitdir: /home/username/path/to/.git/worktrees/worktree-name
```
and thus the directory is not detected as a git-based project. Would be very
nice if it did work with git worktrees.


[0]: https://git-scm.com/docs/git-worktree

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

[frameworks-kservice] [Bug 371885] kservice-5.27.0: fails to build with flex-2.6.2

[Leslie Zhai]

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

Leslie Zhai  changed:

   What|Removed |Added

 Resolution|INVALID |UPSTREAM

--- Comment #4 from Leslie Zhai  ---
flex-2.6.3 fixed ;-)

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

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

[bugzilla_noreply]

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

k...@web.de changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #5 from k...@web.de ---
> Vishesh, Baloo is a worthy attempt at an indexing system, and I commend your 
> work. It uses a quality database backend in the form of LMDB. But any which 
> way you and I might spin it, Baloo has a serious problem with I/O: it simply 
> causes too much of it, too frequently. Numerous users have complained about 
> this, and several currently open and closed bugs are traceable directly to 
> this behaviour. Several users' impressions of Baloo, and KDE writ large, are 
> tainted by Baloo's abusive disk activity.

https://linux.die.net/man/1/ionice
[...]
Idle
A program running with idle io priority will only get disk time when no
other program has asked for disk io for a defined grace period. The impact of
idle io processes on normal system activity should be zero. This scheduling
class does not take a priority argument. Presently, this scheduling class is
permitted for an ordinary user (since kernel 2.6.25). 
Best effort
[...]

Baloo's priority is set to Idle, which means it should not cause "abusive" disk
activity.
Unless your IO scheduler does not support ionice. Could this be your problem?
https://blogs.kde.org/2014/10/15/ubuntus-linux-scheduler-or-why-baloo-might-be-slowing-your-system-1404

> Here's a relatively simple proposal: The indexer operates on a configurable 
> *duty cycle* D of 1%-50% and a time period T of 1s-3600s. For (1-D)*T seconds 
> per period, Baloo sleeps. For D*T seconds per period, Baloo *exclusively* 
> performs data/metadata reads from the filesystem, keeping an eye on 
> wall-clock time. Once D*T seconds of work have elapsed, make a *single 
> transaction* containing all of the stuff that the indexer read in the 
> previous duty cycle. Then go back to sleep again. In this way, exactly one 
> mdb_txn_commit() and fdatasync()/msync() occurs per time period, they are 
> likely to have accumulated far more than 40 files worth of information, and 
> 50-99% of I/O bandwidth is available for other uses, such as satisfying the 
> desktop UI's needs.

You are suggesting rate limiting the IO. Rate limiting is inferior to
scheduling (which is already being done) because:

1. The rate limit is wasting (1-D) of the available bandwidth in idle
situations. (When baloo is the only application using IO.)

2. If Bmin < 1 is needed to satisfy the user requirements, (1-D) might still be
smaller than Bmin. Scheduling with Idle priority will leave 1 instead of of
(1-D) to the user, which is enough in any case. Also, now we don't need to find
Bmin anymore.


Anyway, minimizing the caused IO is still useful.

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

[krita] [Bug 374477] New: TGA Format export into another extension.

[Deo]

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

Bug ID: 374477
   Summary: TGA Format export into another extension.
   Product: krita
   Version: 3.1.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: deodat...@gmail.com
  Target Milestone: ---

Created attachment 103158
  --> https://bugs.kde.org/attachment.cgi?id=103158=edit
TGA file format.

When you export in TGA File, the extension says:

"Image.icb"


So I need to rename all the time the extension.

And will be nice if you rename TYPE from: Image TGA to TGA Image... with this I
can just press Tab key and press "T" Key and this will chage fast.

And another thing that will be good, is to have in FILE Menu>Overwrite File...
this if I export my Krita document as TGA/JPG/PNG, with a click reExport the
last format file... as GImp do ;)

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

[krita] [Bug 374319] SIGABRT exiting Krita after transformation of a pasted image from a secondary window (Krita 3.1.1 appimage - Ubuntu 14.04)

[Phil Blackburn]

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

--- Comment #5 from Phil Blackburn  ---
Thanks a lot for the video. I'm still unable to reproduce as of git 132213b.
Perhaps it's been fixed and one of the core devs can verify.

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

[frameworks-baloo] [Bug 353193] Don't blindly index any folder.

[bugzilla_noreply]

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

k...@web.de changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #5 from k...@web.de ---
Please don't.

> This not only makes indexing faster but more importantly indexes only 
> relevant folders.

What is relevant or not is up to the user. I'd argue that folders created by
the user themselves are more relevant for a person than standard folders
predefined by the distribution. Many don't use the
"Documents-Downloads-Pictures" stereotype.

Most users will not expect this behaviour, much less such a change in
behaviour.
Even if you know about it, having to add a newly created folder to the
whitelist is easily forgotten, and annoying.

The performance argument isn't relevant.
If a user has big data that is causing performance problems and stores them in
~/Documents it will cause performance problems, and this suggestion would not
change anything about that. The better way of handling this big data would be
to blacklist it explicitely.
If a stereotypical user doesn't have any folders besides the user-dirs.dirs,
this won't improve performance either.

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

[kdenlive] [Bug 366441] Kdenlive instantly crashing if GPU acceleration is activated

[Michal]

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

Michal  changed:

   What|Removed |Added

 CC||michal.kl...@gmail.com

--- Comment #3 from Michal  ---
Same problem, disabling GPU acceleration in KDENLIVE solved the problem
instantly.  Using gtx 770 with 375.26 drivers on KDE NEON.

Backtrace of the crash I experienced:

Application: Kdenlive (kdenlive), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fa5172b88c0 (LWP 5422))]

Thread 12 (Thread 0x7fa4a67f6700 (LWP 5443)):
[KCrash Handler]
#6  0x7fa510a51428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fa510a5302a in __GI_abort () at abort.c:89
#8  0x7fa4d992f8c3 in GlslManager::render_frame_texture (this=0x3fc8a30,
chain=0x7fa4b8151870, frame=0x7fa4b813f620, width=1920, height=1080,
image=0x7fa4a67f5cd8) at filter_glsl_manager.cpp:383
#9  0x7fa4d9932802 in convert_image (frame=0x7fa4b813f620,
image=0x7fa4a67f5cd8, format=0x3d3606c, output_format=mlt_image_glsl_texture)
at filter_movit_convert.cpp:573
#10 0x7fa5164ac7a8 in mlt_frame_get_image (self=self@entry=0x7fa4b813f620,
buffer=buffer@entry=0x7fa4a67f5cd8, format=format@entry=0x3d3606c,
width=width@entry=0x7fa4a67f5cc4, height=height@entry=0x7fa4a67f5cc8,
writable=writable@entry=0) at mlt_frame.c:591
#11 0x7fa5164c2679 in producer_get_image (self=self@entry=0x7fa4b813e980,
buffer=buffer@entry=0x7fa4a67f5cd8, format=format@entry=0x3d3606c,
width=width@entry=0x7fa4a67f5cc4, height=height@entry=0x7fa4a67f5cc8,
writable=writable@entry=0) at mlt_tractor.c:370
#12 0x7fa5164ac757 in mlt_frame_get_image (self=self@entry=0x7fa4b813e980,
buffer=buffer@entry=0x7fa4a67f5cd8, format=format@entry=0x3d3606c,
width=width@entry=0x7fa4a67f5cc4, height=height@entry=0x7fa4a67f5cc8,
writable=writable@entry=0) at mlt_frame.c:585
#13 0x7fa5164bfe24 in consumer_read_ahead_thread (arg=0x4288b50) at
mlt_consumer.c:825
#14 0x0072bb4d in RenderThread::run (this=0x7fa4a8152e90) at
/workspace/build/src/monitor/glwidget.cpp:1252
#15 0x7fa511532b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fa50f17b6ba in start_thread (arg=0x7fa4a67f6700) at
pthread_create.c:333
#17 0x7fa510b2282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fa4c0e4f700 (LWP 5442)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa5164c00ab in mlt_consumer_rt_frame (self=self@entry=0x4288b50) at
mlt_consumer.c:1576
#2  0x7fa4d9d70d90 in consumer_thread (arg=0x4288b50) at
consumer_sdl_audio.c:531
#3  0x7fa50f17b6ba in start_thread (arg=0x7fa4c0e4f700) at
pthread_create.c:333
#4  0x7fa510b2282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fa4a77fd700 (LWP 5439)):
#0  0x7fa510b16b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa509c5e39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa509c5e4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa51175e23b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa511708cea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa51152dfb4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa511532b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa50f17b6ba in start_thread (arg=0x7fa4a77fd700) at
pthread_create.c:333
#8  0x7fa510b2282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fa4c0133700 (LWP 5438)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa511533a4b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa515b51eed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7fa515b527c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7fa511532b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa50f17b6ba in start_thread (arg=0x7fa4c0133700) at
pthread_create.c:333
#6  0x7fa510b2282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fa4c18bb700 (LWP 5436)):
#0  0x7fa510b16b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa509c5e39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa509c5e4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa51175e23b in

[digikam] [Bug 374476] New: Exporting to Google Photos changes File modified timestamp

[Roger Foss]

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

Bug ID: 374476
   Summary: Exporting to Google Photos changes File modified
timestamp
   Product: digikam
   Version: 5.3.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Export
  Assignee: digikam-de...@kde.org
  Reporter: roger.f...@gmail.com
  Target Milestone: ---

BACKGROUND
Uploading lots of stuff to Google Photos. Because of how Google sorts photo
albums, if an album contains a photo with a recently modified file timestamp it
will show up first in the list of albums.

I therefore am careful about ensuring all photos in a digikam album have EXIF
original, create and file timestamps set to that of the original photo. This
ensures that the date ranges of albums are correct, which ensures that my
albums are sorted correctly.

PROBLEM
Once I have updated all the time stamps in a digikam album, I export it to
Google Photos.  Only, Digikam seems to update the file modified timestamp in
the export process.
This means all my photos end up with file modified timestamps set to the time
of the upload.  The export doesn't modify my photos (?), so why does it modify
the timestamps?

INFO
Currently on Linux Mint 18.1 with Digikam running on Cinnamon desktop. Not all
digikams GUI buttons display correctly but functionally seem to work.

My photos and digikam files are stored on a btrfs volume, mounted with relatime
option. Mentioning this but it should not be relevant, my bug report is really
that the Export process shouldn't update the file modified timestamp of photos.

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

[digikam] [Bug 296580] Allow to choose photo date-time stamp from digiKam main window

[Kusi]

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

--- Comment #15 from Kusi  ---
Patch under review

https://git.reviewboard.kde.org/r/129755/

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

[kalarm] [Bug 373848] Indicator not showing in Ubuntu Unity 16.10 (4:16.04.3-0ubuntu2)

[David Jarvie]

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

David Jarvie  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1

--- Comment #5 from David Jarvie  ---
I think that KAlarm needs to set the default system tray icon visibility based
on the desktop (determined by XDG_CURRENT_DESKTOP environment variable). If the
desktop is Unity, it should default to visible at all times.

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

[systemsettings] [Bug 374475] New: Kde Plasma las aplicaciones se detienen

[Ramon Silva]

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

Bug ID: 374475
   Summary: Kde Plasma las aplicaciones se detienen
   Product: systemsettings
   Version: 5.8.2
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ramon_al_...@yahoo.com.ar
  Target Milestone: ---

Application: systemsettings5 (5.8.2)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.0-kali2-amd64 x86_64
Distribution: Kali GNU/Linux Rolling

-- Information about the crash:
- What I was doing when the application crashed:
Las aplicaciones proporcionadas por kde5 se detienen inesperadamente al momento
de iniciarlas
- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: Preferencias del sistema (systemsettings5), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f24168018c0 (LWP 5934))]

Thread 6 (Thread 0x7f23df5ec700 (LWP 5941)):
#0  0x7f240e0149e8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f240e016e7b in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f240e01791b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f240e017b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f241383bf5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f24137e58da in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f24136130f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f2411f976a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f2413617da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f2410136464 in start_thread (arg=0x7f23df5ec700) at
pthread_create.c:333
#10 0x7f2412f329df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f23f0dd5700 (LWP 5939)):
#0  0x7f2412f255dd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f240e05bc40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f240e0174be in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f240e017994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f240e017d82 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f23f1d3a4f6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7f240e03f345 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f2410136464 in start_thread (arg=0x7f23f0dd5700) at
pthread_create.c:333
#8  0x7f2412f329df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f23f15d6700 (LWP 5938)):
#0  0x7f240e014a77 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f240e016fd8 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f240e01791b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f240e017b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f240e017b51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f240e03f345 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f2410136464 in start_thread (arg=0x7f23f15d6700) at
pthread_create.c:333
#7  0x7f2412f329df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f23fc6de700 (LWP 5936)):
#0  0x7f240e0149aa in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f240e016e7b in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f240e01791b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f240e017b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f241383bf5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f24137e58da in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f24136130f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f24169586d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x7f2413617da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f2410136464 in start_thread (arg=0x7f23fc6de700) at
pthread_create.c:333
#10 0x7f2412f329df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f24050d5700 (LWP 5935)):
#0  0x7f2412f2956d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f24109b0150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f24109b1ee9 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 

[KScreen] [Bug 365749] kscreen kcm: orientation should be under advanced

[andreas]

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

--- Comment #4 from andreas  ---
in a tablet mode I would prefer a plasmoid that rotate the ui instead of a kcm
where I can do that.

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

[frameworks-kdoctools] [Bug 374435] kdoctools_install() use a wrong directory when the parameter ends with "docs"

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/kdo
   ||ctools/938e439db2067381dd3d
   ||f6a0ea71f50aa73fd310
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Luigi Toscano  ---
Git commit 938e439db2067381dd3df6a0ea71f50aa73fd310 by Luigi Toscano.
Committed on 03/01/2017 at 00:20.
Pushed by ltoscano into branch 'master'.

kdoctools_install: match the full path for the program

Summary:
In order to get the name of the program, match against the full path
which includes the path of the directory currently scanned for a
certain language.
So if docs/ appears somewhere in the path, it does not interfere
with the matching regular expression and the name of the program
is correctly extracted.

Test Plan: kdoctools_install(l10n-docs) now works

Reviewers: #frameworks, #documentation, aacid

Reviewed By: #documentation, aacid

Tags: #frameworks, #documentation

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

M  +1-1KF5DocToolsMacros.cmake

https://commits.kde.org/kdoctools/938e439db2067381dd3df6a0ea71f50aa73fd310

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

[plasmashell] [Bug 366458] wrong icon scaling

[andreas]

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

andreas  changed:

   What|Removed |Added

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

--- Comment #3 from andreas  ---
the system tray use 22px icons

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

[krita] [Bug 359128] Add improved transformation filters (perspective transformation blurs the image)

[Alexandre Blondin Massé]

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

Alexandre Blondin Massé  changed:

   What|Removed |Added

 CC||alexandre.blondin.masse@gma
   ||il.com

--- Comment #5 from Alexandre Blondin Massé  
---
I don't know if this feature has been resolved, but I would be interested in
trying to take care of it. I took a quick look to Krita's source code and I'm a
bit overwhelmed by its size! If someone could just point me in the right
direction (what files should I look, for instance), I'll try!

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

[systemsettings] [Bug 374474] New: Add button which pauses baloo indexing

[bugzilla_noreply]

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

Bug ID: 374474
   Summary: Add button which pauses baloo indexing
   Product: systemsettings
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_baloo
  Assignee: pinak.ah...@gmail.com
  Reporter: k...@web.de
  Target Milestone: ---

There should be a way to do the following two things from systemsettings:

$ balooctl \
  suspend#Suspend the file indexer
$ balooctl \
  resume #Resume the file indexer

This could be represented as a pause/play button.

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

[systemsettings] [Bug 374467] kde crashes everytime

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[systemsettings] [Bug 346519] System Settings Crashed

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||dan.m...@rogers.com

--- Comment #66 from Christoph Feck  ---
*** Bug 374467 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 337563] Switch between 24 and 12-hours time formats

[Tim Edwards]

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

--- Comment #6 from Tim Edwards  ---
Understood, thanks for clarifying. Hopefully Qt will support customising the
settings soon.

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

[systemsettings] [Bug 337583] kcm_baloofile: no option to control indexed files and mimetypes etc.

[Christoph Feck]

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

--- Comment #6 from Christoph Feck  ---
https://gitlab.com/ericlnu/baloo-kcmadv/tree/master

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

[systemsettings] [Bug 337583] kcm_baloofile: no option to control indexed files and mimetypes etc.

[bugzilla_noreply]

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

k...@web.de changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #5 from k...@web.de ---
(In reply to kdebugs.kapush from comment #2)
> Have a look at kcm_baloo_advanced, it allows for mime filters and file
> filters. Available in AUR for archlinux:
> https://aur.archlinux.org/packages/kcm_baloo_advanced/
> 
> Also from upstream gitorious:
> https://gitorious.org/baloo-kcmadv

both links are
404 - Page Not Found

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

[kwin] [Bug 368201] Desktop Effect Filter

[andreas]

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

--- Comment #7 from andreas  ---
if the filter is needed for "bugtracking" or whatever it should be called, than
add some usefull stuff for the filter.

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

[plasmashell] [Bug 360289] open new task with right click on empty space

[andreas]

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

andreas  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WONTFIX

--- Comment #8 from andreas  ---
thomas has right the benefit isn't that big.

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

[kactivitymanagerd] [Bug 374473] New: random desktop crash

[Nancy Hand]

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

Bug ID: 374473
   Summary: random desktop crash
   Product: kactivitymanagerd
   Version: 5.8.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: n_h...@cox.net
CC: plasma-b...@kde.org
  Target Milestone: ---

Running Fedora 25, KDE desktop. Machine was upgraded from 23 to 24 then to 25
in the last month or so. The crashes started shortly after upgrading to f25 but
reported a link back to f23. 

The desktop crashes randomly - logging out the user and closing applications.
There doesn't appear to be any obvious trigger for the crash. The
kactivitymanagerd error says data are incomplete and can't file a report. The
core dump process seems to have locked up.

Applications "involved" in the crash are:
xorg-x11-server   1.19.0-2.fc25x86_64
kdepim16.08.3-1.fc25.x86_64
plasma-desktop5.8.4-1.fc25.x86_64
kdepim-runtime1:16.08.3-1.fc25.x86_64
kactivitymanagerd n/a
drkonqi   n/a

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

[plasmashell] [Bug 368549] Do we need add as launcher and add to panel

[andreas]

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

--- Comment #3 from andreas  ---
+1 for Pin to task bar

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

[Breeze] [Bug 369037] Gradient at LibreOffice toolbar

[andreas]

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

andreas  changed:

   What|Removed |Added

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

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

[Breeze] [Bug 374254] add monochrome free space notifier icon

[andreas]

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

--- Comment #4 from andreas  ---
Is it the hard disk space widget. cause on my system it never show an icon
view, like in your screenshot (plasma 5.8.4)

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

[Breeze] [Bug 374254] add monochrome free space notifier icon

[andreas]

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

--- Comment #3 from andreas  ---
I now know the icon what was used but what's the widget/applet, do you get it
from the store.kde.org or is it an default applet/widget.

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

[digikam] [Bug 374472] New: Crash on Import after going into shell

[mihaela]

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

Bug ID: 374472
   Summary: Crash on Import after going into shell
   Product: digikam
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Import
  Assignee: digikam-de...@kde.org
  Reporter: miha...@prkos.hr
  Target Milestone: ---

Application: digikam (3.5.0)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-51-generic x86_64
Distribution: Ubuntu 14.04.5 LTS

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

I opened the Import dialogue, PTP, kept my default import settings and selected
Download All. The Import started. Then I moved my mouse to top left screen
corner to switch windows/desktop (I'm on Ubuntu 14.04 with Gnome shell).  After
that digiKam crashed. Some of the photos have been downloaded before the crash. 

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9526553ac0 (LWP 14887))]

Thread 9 (Thread 0x7f95015d2700 (LWP 14890)):
#0  0x7f951ff76fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f95069e6248 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x7f951b207184 in start_thread (arg=0x7f95015d2700) at
pthread_create.c:312
#3  0x7f951ff8437d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 8 (Thread 0x7f94fa1a7700 (LWP 14891)):
#0  0x7f9518a7061d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9518a70979 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9518a2eed5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9518a2f30a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f95081f6336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7f9518a53f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f951b207184 in start_thread (arg=0x7f94fa1a7700) at
pthread_create.c:312
#7  0x7f951ff8437d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 7 (Thread 0x7f94f99a6700 (LWP 14892)):
#0  0x7f9518a70622 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9518a70979 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9518a2e87b in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9518a2ef52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9518a2f0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f9518a2f129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f9518a53f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f951b207184 in start_thread (arg=0x7f94f99a6700) at
pthread_create.c:312
#8  0x7f951ff8437d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7f94e8cb0700 (LWP 14896)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f9520d63dd3 in _q_futex (val2=0, addr2=0x0, timeout=0x0, val=2,
op=0, addr=0x146a200) at thread/qmutex_unix.cpp:99
#2  QMutexPrivate::wait (this=this@entry=0x146a200, timeout=timeout@entry=-1)
at thread/qmutex_unix.cpp:113
#3  0x7f9520d603bd in QMutex::lock (this=) at
thread/qmutex.cpp:164
#4  0x7f9523585a69 in Digikam::DatabaseAccess::DatabaseAccess
(this=) at
/build/buildd/digikam-3.5.0/core/libs/database/databaseaccess.cpp:101
#5  0x7f952357ceda in Digikam::CollectionManager::albumRootPath
(this=0x1449140, givenPath=...) at
/build/buildd/digikam-3.5.0/core/libs/database/collectionmanager.cpp:1369
#6  0x7f9523577456 in Digikam::CollectionScanner::partialScan
(this=this@entry=0x7f94e8cafae0, filePath=...) at
/build/buildd/digikam-3.5.0/core/libs/database/collectionscanner.cpp:615
#7  0x005d5e49 in Digikam::ScanController::run (this=0x14481f0) at
/build/buildd/digikam-3.5.0/core/digikam/database/scancontroller.cpp:798
#8  0x7f9520d6532f in QThreadPrivate::start (arg=0x14481f0) at
thread/qthread_unix.cpp:349
#9  0x7f951b207184 in start_thread (arg=0x7f94e8cb0700) at
pthread_create.c:312
#10 0x7f951ff8437d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7f94d700 (LWP 14897)):
#0  0x7f951ff76fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9518a2efe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9518a2f0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9520e947be in QEventDispatcherGlib::processEvents
(this=0x7f94d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f9520e660af in QEventLoop::processEvents
(this=this@entry=0x7f94dfffeae0, flags=...) at kernel/qeventloop.cpp:149
#5  

[digikam] [Bug 374180] Other tags assigned to the picture is disturbing when looking at face tags

[Simon]

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

--- Comment #7 from Simon  ---
Thanks for the screenshot, it definitely helped me understand.
This is however not a bug but intended. The information displayed below
the thumbnail in icon view is specific to the entire image also with
active people sidebar. Only the overlay that allows to confirm/type the
name or discard the face rectangle are specific to the view shown with
people sidebar active.

Regarding your other two questions:
 - There is no way to mark a face but not use this face for face
recognition.
 - There is also no way to separate tags applied to the entire image and
only to areas. Every tag applied to an area (i.e. face) is also applied
as a tag to the entire image.

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

[plasmashell] [Bug 337563] Switch between 24 and 12-hours time formats

[Martin Klapetek]

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

--- Comment #5 from Martin Klapetek  ---
I'm not disagreeing, I'm simply letting you know the Qt devs didn't make any
"very arbitrary decision .. to say Australians always use 12-hour time"; Qt is
using common locale data for your country.

Once Qt actually supports customizing locale settings, then there will be a
simple switch available.

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

[kontact] [Bug 374471] New: Reboot crash everytime

[Eric]

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

Bug ID: 374471
   Summary: Reboot crash everytime
   Product: kontact
   Version: 5.2.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eric.v...@msg4.us
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
zypper patch + zypper up + reboot
- Custom settings of the application:
Simlinks to a different partition, many profiles, many many filters (most
filters stoped working a while ago, and spam filter never worked)

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7d948587c0 (LWP 3548))]

Thread 22 (Thread 0x7f7ce57fa700 (LWP 4050)):
#0  0x7ffde4139b26 in clock_gettime ()
#1  0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f7d91e597d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d91fdab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d89ff74ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f7d89ff7d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f7d89ff7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f7d91fdad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f7d91f81d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f7d91da832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f7d9149f02d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f7ce67fc700 (LWP 4043)):
#0  0x7ffde4139b26 in clock_gettime ()
#1  0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f7d91e597d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d91fdab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d89ff74ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f7d89ff7d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f7d89ff7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f7d91fdad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f7d91f81d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f7d91da832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f7d9149f02d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f7ce6ffd700 (LWP 4041)):
#0  0x7ffde4139b26 in clock_gettime ()
#1  0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f7d91e597d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d91fdab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d89ff74ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f7d89ff7d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f7d89ff7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f7d91fdad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f7d91f81d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f7d91da832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f7d9149f02d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f7ce77fe700 (LWP 4033)):
#0  0x7f7d8a039d10 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f7d89ff78e9 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f7d89ff7df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7d89ff7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7d91fdad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  

[digikam] [Bug 374470] New: Deleted tags are not removed from file metadata

[Simon]

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

Bug ID: 374470
   Summary: Deleted tags are not removed from file metadata
   Product: digikam
   Version: 5.4.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: freisi...@gmail.com
  Target Milestone: ---

Steps to reproduce:
1. Enable writing image tags to metadata (either with or without lazy sync).
2. Create a tag and apply it to one file.
3. Delete this tag in the right tag sidebar.
4. Confirm the prompt warning that this tag is assigned to one item.
5. Reread metadata from file.

Expected results:
The deleted tag stays deleted.

Actual results:
The deleted tag is resurrected and shown as applied to the test image.

This is not https://bugs.kde.org/show_bug.cgi?id=361378 as the tag is correctly
removed from the file when it is explicitly removed for just that file. This
only occurs on deletion of the tag itself.

The documentation states:
You can delete a tag by right-clicking on the tag you want to delete and
selecting Delete Tag. When you delete a tag, the photographs themselves are
not deleted. Simply the tag is removed from those photographs.

This is currently only true for the database, not for the image metadata.

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

[plasmashell] [Bug 374455] scaling, using scaling leads to pointing and displaying problems

[Philippe ROUBACH]

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

--- Comment #3 from Philippe ROUBACH  ---
(In reply to David Edmundson from comment #1)
> Then you need to file bugs with those programs.

Those applications has no problem.
As i said:
>>if i choose scale = 1.2 for example then there are problems
>>if i revert to scaling=1 then no more problems

it's a scaling problem
and
it's not a font rendering problem so i don't understand you mark it as a
duplicate of bug 374014

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

[kphotoalbum] [Bug 374431] Version 5.1 crashes when reading some index files

[Johannes Zarl-Zierl]

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

Johannes Zarl-Zierl  changed:

   What|Removed |Added

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

--- Comment #11 from Johannes Zarl-Zierl  ---
With commit 0088b7aa this situation should not occur again.

Unfortunately, there's not much we can do inside kphotoalbum to fix an
index.xml file that already contains invalid characters. But since the
workaround fixed your immediate problem, I'll close this bug anyways...

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

[kphotoalbum] [Bug 374431] Version 5.1 crashes when reading some index files

[Johannes Zarl-Zierl]

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

--- Comment #10 from Johannes Zarl-Zierl  ---
Git commit 680499cfaafc8e57dfb38f2c0685f58ba0b1fc3f by Johannes Zarl-Zierl.
Committed on 02/01/2017 at 22:29.
Pushed by johanneszarl into branch '4.7'.

Prevent invalid characters in image description.

Some cameras seem to add invalid characters (i.e. control characters) to
the Exif.Image.ImageDescription. When the description is saved into the
database, we end up with an invalid index.xml file.
This patch removes control characters from the exif image description.

M  +4-1DB/FileInfo.cpp

https://commits.kde.org/kphotoalbum/680499cfaafc8e57dfb38f2c0685f58ba0b1fc3f

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

[kdenlive] [Bug 374469] Kdenlive: Cannot reload file after creating proxy video

[Marc Draco]

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

--- Comment #1 from Marc Draco  ---
Would I be correct in assuming this has something to do with a Printf
formatting string? The output does appear to be attempting to print an integer
value (and failing.) I'm not sufficiently au fait with the code to fix this I'm
afraid.

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

[kdenlive] [Bug 374469] Kdenlive: Cannot reload file after creating proxy video

[Marc Draco]

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

Marc Draco  changed:

   What|Removed |Added

 CC||marcdr...@protonmail.com

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

[kphotoalbum] [Bug 374431] Version 5.1 crashes when reading some index files

[Johannes Zarl-Zierl]

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

--- Comment #9 from Johannes Zarl-Zierl  ---
Git commit 0088b7aa3a6b8824d23f68f0f821fe3d4a07a012 by Johannes Zarl-Zierl.
Committed on 02/01/2017 at 22:12.
Pushed by johanneszarl into branch 'master'.

Prevent invalid characters in image description.

Some cameras seem to add invalid characters (i.e. control characters) to
the Exif.Image.ImageDescription. When the description is saved into the
database, we end up with an invalid index.xml file.
This patch removes control characters from the exif image description.

M  +4-1DB/FileInfo.cpp

https://commits.kde.org/kphotoalbum/0088b7aa3a6b8824d23f68f0f821fe3d4a07a012

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

[plasmashell] [Bug 337563] Switch between 24 and 12-hours time formats

[Tim Edwards]

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

--- Comment #4 from Tim Edwards  ---
It's not about one format being wrong or right, it's a personal preference
whether to use 12 or 24-hour time. Most applications/apps/OSes have it as a
settings option (even the KDE Plasma clock app has it as a setting). 

I was hoping that was possible in KDE5 but if it can't be done because of the
way Qt is used then that's it.

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

[plasmashell] [Bug 373613] Notify message not accurate as "This device can now be safely removed."

[CnZhx]

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

--- Comment #5 from CnZhx  ---
Output of `solid-hardware5 list`:
`
udi = '/org/freedesktop/UDisks2/block_devices/sdb'
udi = '/org/freedesktop/UDisks2/drives/Kingston_DataTraveler_3_2e0'
`
I trimmed the output to only include those related to the USB stick. Hopefully
it is enough for the investigation.

And output of `solid-hardware5 listen` while detaching the udisk when it is
still being removed. There is no other operation on this USB stick this time.
`
~> solid-hardware5 listen
Listening to add/remove events: 
"/org/freedesktop/UDisks2/block_devices/sdb1" lost interfaces:
("org.freedesktop.UDisks2.Filesystem")
"/org/freedesktop/UDisks2/block_devices/sdb" lost interfaces:
("org.freedesktop.UDisks2.PartitionTable")
"/org/freedesktop/UDisks2/block_devices/sdb1" lost interfaces:
("org.freedesktop.UDisks2.Partition", "org.freedesktop.UDisks2.Block")
Device Removed:
udi = '/org/freedesktop/UDisks2/block_devices/sdb1'
"/org/freedesktop/UDisks2/block_devices/sdb" lost interfaces:
("org.freedesktop.UDisks2.Block")
Device Removed:
udi = '/org/freedesktop/UDisks2/block_devices/sdb'
"/org/freedesktop/UDisks2/drives/Kingston_DataTraveler_3_2e0" lost interfaces:
("org.freedesktop.UDisks2.Drive")
Device Removed:
udi = '/org/freedesktop/UDisks2/drives/Kingston_DataTraveler_3_2e0'
`

Another output of `solid-hardware5 listen` while detaching the udisk after
making a file-syncing using FreeFileSync. But the udisk is removed after the
messages disappeared. I could not catch the timing because there was a long
time display of "Removing", and then, "Removing" on top of "This device can now
be safely removed." In other words, there is no time of only showing the
message of "This device can now be safely removed", or the time is too short
for me to see.
`
~> solid-hardware5 listen
Listening to add/remove events: 
"/org/freedesktop/UDisks2/block_devices/sdb1" lost interfaces:
("org.freedesktop.UDisks2.Filesystem")
"/org/freedesktop/UDisks2/block_devices/sdb" lost interfaces:
("org.freedesktop.UDisks2.PartitionTable")
"/org/freedesktop/UDisks2/block_devices/sdb1" lost interfaces:
("org.freedesktop.UDisks2.Partition", "org.freedesktop.UDisks2.Block")
Device Removed:
udi = '/org/freedesktop/UDisks2/block_devices/sdb1'
"/org/freedesktop/UDisks2/block_devices/sdb" lost interfaces:
("org.freedesktop.UDisks2.Block")
Device Removed:
udi = '/org/freedesktop/UDisks2/block_devices/sdb'
"/org/freedesktop/UDisks2/drives/Kingston_DataTraveler_3_2e0" lost interfaces:
("org.freedesktop.UDisks2.Drive")
Device Removed:
udi = '/org/freedesktop/UDisks2/drives/Kingston_DataTraveler_3_2e0'
`

Since there were several updates to FreeFileSync and many updates to openSUSE
Tumbleweed, maybe the problem have vanished. I have not tried this since I
filed this bug report. I am really sorry for wasting your time checking this if
this is not a bug in this component.

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

[kdenlive] [Bug 374469] Kdenlive: Cannot reload file after creating proxy video

[Marc Draco]

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

Marc Draco  changed:

   What|Removed |Added

  Flags||timeline_corruption+

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

[kdenlive] [Bug 374469] New: Kdenlive: Cannot reload file after creating proxy video

[Marc Draco]

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

Bug ID: 374469
   Summary: Kdenlive: Cannot reload file after creating proxy
video
   Product: kdenlive
   Version: 16.12.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: marcdr...@protonmail.com
  Target Milestone: ---

Created attachment 103157
  --> https://bugs.kde.org/attachment.cgi?id=103157=edit
Sample error when reloading file,

I've got what might be a bit of an edge case here in that I'm having to work
over two drives (with most of the files on normal HD and some stuff on an SSD)
however, I don't think that's the reason.

I'm using PNG image sequences created by Natron because Kdenlive doesn't have
the facilities I need (not that it should!). 

This all works fine until I create a proxy for these clips (which are
bottlenecked by I/O from the HDD) - hence the reason for using a proxy. 

When I close and re-open Kdenlive, the link between the file and the proxy is
broken resulting in an error as shown.

This has created no end of heartache trying to figure out what was going on -
but I'm happy to have identified the bug (and bloody grateful to have Kdenlive,
TBH).

The workaround seems to be to reconnect the file manually in the diaglog
(recursive scanning isn't working for me - producing an abnormal termination).

This is what appears in the XML at the offending point I believe:

/run/media/marc/0016EB7B3AE5EBFA/Vocalise/Halo/%01d.png?begin:1
  /run/media/marc/fd43d48a-0e5b-44e1-b870-22b8a9c00185/PROXY/proxy/d7f5516f9998fa61fb1eae3e6c77a16d.mov

I trust this is of assistance - I really don't want to have to go back to the
"Shark" if you know what I mean. :)

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

[kontact] [Bug 362339] Kontact crashes on startup with SEGFAULT "Could not create collection trash, resourceId: 3"

[Freek de Kruijf]

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

--- Comment #10 from Freek de Kruijf  ---
Created attachment 103156
  --> https://bugs.kde.org/attachment.cgi?id=103156=edit
traceback of akonadi-server

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

[kontact] [Bug 362339] Kontact crashes on startup with SEGFAULT "Could not create collection trash, resourceId: 3"

[Freek de Kruijf]

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

--- Comment #9 from Freek de Kruijf  ---
Created attachment 103155
  --> https://bugs.kde.org/attachment.cgi?id=103155=edit
traceback of akonadi-server

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

[kontact] [Bug 362339] Kontact crashes on startup with SEGFAULT "Could not create collection trash, resourceId: 3"

[Freek de Kruijf]

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

Freek de Kruijf  changed:

   What|Removed |Added

 CC||freekdekru...@kde.nl

--- Comment #8 from Freek de Kruijf  ---
I also have regular crashes of akonadi-server when closing kontact. See the two
attached traceback files.
I also have Trash folders pointing to the trash folders of the 5 IMAP-servers.
I had a message about a duplicate entry in the MySQL database, which I could
not solve. Finally I solved that by moving the folder ~/.local/share/akonadi to
~/.local/share/akonadi.sav, which effectively destroys the MySQL database. But
starting kontact apparently rebuild the database from scratch. Inspection
showed that I had to redirect the trash again to the trash folders of each IMAP
server, which seems to be the only configuration that is lost. Finally I
destroyed ~/.local/share/akonadi.sav.

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

[digikam] [Bug 374180] Other tags assigned to the picture is disturbing when looking at face tags

[bugzilla_noreply]

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

--- Comment #6 from ohm196...@gmail.com ---
Created attachment 103154
  --> https://bugs.kde.org/attachment.cgi?id=103154=edit
Shows my selection and the confusing extra tags.

Hi Simon.


I am sorry for the somewhat unclear description of the problem.
Trying again.

See picture.
I have selected people tags, Odd Harry, and thumbnail view, ( not preview and
show face tags )
The thumbnails shows only the marked part of the pictures with my face on, but
below the thumbnail all tags for the whole picture is listed.
Also other peoples names if they are tagged on the same picture.

I hope this helps reproducing the slightly confusing situation.

Odd Harry

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

[krita] [Bug 374319] SIGABRT exiting Krita after transformation of a pasted image from a secondary window (Krita 3.1.1 appimage - Ubuntu 14.04)

[mvowada]

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

--- Comment #4 from mvowada  ---
Created attachment 103153
  --> https://bugs.kde.org/attachment.cgi?id=103153=edit
(Video example of the steps)

(In reply to Phil Blackburn from comment #3)
> Was there any other intermediate step, or
> saving of images involved? How did you apply the changes in step 6?

Hi Phil, here is a video showing the steps. Thanks for checking

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

[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond

[Maximilian Hartert]

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

Maximilian Hartert  changed:

   What|Removed |Added

 CC||max.hart...@it-top.de

--- Comment #22 from Maximilian Hartert  ---
I do have the same problem.
But since I also use an (apple) trackpad now, it does not bother me that much
anymore.

Plasma 5.8.5
System Settings 5.8.5
Kernel: 4.4-0-57-generic
Kde Neon Developer Stable

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

[digikam] [Bug 374191] Unusable context menu entries in tags and people view

[bugzilla_noreply]

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

--- Comment #21 from caulier.gil...@gmail.com ---
To comment #13 :

"Moreover, I found some function calls in the code that seem to be superfluous.
I did not remove them, but only set a comment @ODD."

I take a look to the patch #103144. The commented code with @ODD :

+// @ODD : Why is singleton set to true? resetAlbumsAndTags already clears
the selection.
 d->albumSelectors->setPAlbumSelected(album, true);

+// @ODD : Why is singleton set to true? resetAlbumsAndTags already clears
the selection.
 d->albumSelectors->setTAlbumSelected(album, true);

I think this kind of singleton selection exist due to some problem seen while
porting from Qt4 to Qt5. I don't remember exactly.

Check if this argument need to be set to true really, as the model have been
adjusted previously.

Check also where these methods are used outside similarity code to see if this
argument need really to exists.

Gilles Caulier

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

[krita] [Bug 374461] Cannot right-click with a Wacom Tablet

[silva]

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

--- Comment #2 from silva  ---
Hi Boudewijn,

It's a Bamboo tablet. I haven't had this issue on El Capitan. Only on
Sierra.
Thanks!

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

[kate] [Bug 374229] "modified" icon (floppy) is not synchronized between different windows

[Dominik Haumann]

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

Dominik Haumann  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Dominik Haumann  ---
Indeed, this is a bug. Proposed fix is under review:
https://git.reviewboard.kde.org/r/129754/

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

[digikam] [Bug 374191] Unusable context menu entries in tags and people view

[bugzilla_noreply]

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

--- Comment #20 from caulier.gil...@gmail.com ---
The difference between Tags and face-tags is to name just face in the image,
not the whole image.

So search similarity from face-tags, as similarity is implemented will search
for same similar whole image not face.

We need to be be clear for that. I recommend to plan to write some words about
this topic in handbook for end users, if this implementation is add to digiKam.

Gilles

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

[digikam] [Bug 374413] picture sorting by name incorrect

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.4.0
  Latest Commit||https://commits.kde.org/dig
   ||ikam/e447c19c861dcc7bb65fcc
   ||61d3f7b7203951816a

--- Comment #4 from Maik Qualmann  ---
Git commit e447c19c861dcc7bb65fcc61d3f7b7203951816a by Maik Qualmann.
Committed on 02/01/2017 at 21:18.
Pushed by mqualmann into branch 'master'.

fix natural sort order and add special case for versioning images if sort after
filename selected
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-1libs/models/albumfiltermodel.cpp
M  +5-1libs/models/imagesortsettings.cpp
M  +3-2libs/models/imagesortsettings.h
M  +1-1showfoto/thumbbar/showfotoitemsortsettings.h
M  +5-1utilities/importui/models/camitemsortsettings.cpp
M  +3-2utilities/importui/models/camitemsortsettings.h

https://commits.kde.org/digikam/e447c19c861dcc7bb65fcc61d3f7b7203951816a

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

[frameworks-plasma] [Bug 374463] Plasma themes are installed to .local/share/ instead of .local/share/plasma/desktoptheme

[Lucas]

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

--- Comment #3 from Lucas  ---
I see that  other items from kde store like color schemes and window
decorations  are also installed to .local/share/

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

[krusader] [Bug 309300] Esc as the default shortcut of "Set Focus to The Panel" is problematic for the embedded terminal

[Toni Asensi Esteve]

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

--- Comment #10 from Toni Asensi Esteve  ---
Created attachment 103151
  --> https://bugs.kde.org/attachment.cgi?id=103151=edit
"Show" nomenclature in Dolphin, instead of "show/hide"

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

[krusader] [Bug 309300] Esc as the default shortcut of "Set Focus to The Panel" is problematic for the embedded terminal

[Toni Asensi Esteve]

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

--- Comment #9 from Toni Asensi Esteve  ---
Created attachment 103150
  --> https://bugs.kde.org/attachment.cgi?id=103150=edit
"Show" nomenclature in Krusader, instead of "show/hide"

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

[krusader] [Bug 309300] Esc as the default shortcut of "Set Focus to The Panel" is problematic for the embedded terminal

[Toni Asensi Esteve]

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

Toni Asensi Esteve  changed:

   What|Removed |Added

 CC||toni.ase...@kdemail.net

--- Comment #8 from Toni Asensi Esteve  ---
> * to change the misleading description to shortcut entry from "Show Terminal 
> Emulator" to "Show/Hide Terminal Emulator"

We have to notice that there are a lot of uses of the "show" word (not
"show/hide"), and every one should be changed, I'll attach an screenshot. 

Other programs, like Dolphin, also use the word "show" instead of "show/hide",
it seems to be the norm, I'll attach another screenshot. 

> * to set "Set Focus to The Panel" to "no key" by default, because:
>  * eliminating shortcut conflicts is good :-)
>  [...]

Maybe it's better not to use Esc to "Set Focus to The Panel" because it's used
by a lot of programs that may be running in the embedded terminal. Nowadays
Ctrl+Up can be used to "set focus to the panel", and also.. Ctrl+Down to return
from the panel to the embedded terminal, those shortcuts are intuitive, related
one to another, and easy to remember.

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

[plasmashell] [Bug 373613] Notify message not accurate as "This device can now be safely removed."

[David Edmundson]

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

--- Comment #4 from David Edmundson  ---
Can you also include the output of

 solid-hardware5 listen

whilst trying to recreate this.

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

[plasmashell] [Bug 373613] Notify message not accurate as "This device can now be safely removed."

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #3 from David Edmundson  ---
That's not very concrete evidence to suggest it hasn't actually been unmounted
properly.

The Solid code definitely waits for udisks to reply that the unmount call has
finished before emitting it's finished and the device notifier plasmoid
definitely waits for solid to reply before it displays that notification. 

I've done a brief code review and I can't see anything wrong on KDE's side.

We should check that you're using the udisks backend though: Can you include
the output of "solid-hardware5 list"

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

[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond

[Dj YB]

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

--- Comment #21 from Dj YB  ---
Had this tested again on 
Linux (x86_64) release 4.8.15-200.fc24.x86_64
systemsettings version 5.8.4

The problem still exists. When activating mouse gestures the selected mouse
button stops acting on click.
However it is still acting on drag.

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

[knetwalk] [Bug 348686] knetwalk 3.3.0 does not update network node icons

[Max]

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

--- Comment #7 from Max  ---
It works great! Thank you

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

[knetwalk] [Bug 348686] knetwalk 3.3.0 does not update network node icons

[Hatto Von Hatzfeld]

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

Hatto Von Hatzfeld  changed:

   What|Removed |Added

 Attachment #103145|0   |1
is obsolete||

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

[knetwalk] [Bug 348686] knetwalk 3.3.0 does not update network node icons

[Hatto Von Hatzfeld]

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

--- Comment #6 from Hatto Von Hatzfeld  ---
Created attachment 103149
  --> https://bugs.kde.org/attachment.cgi?id=103149=edit
improved version file qml/logic.js

Substituting the file logic.js (in my case located in /usr/share/knetwalk/qml/)
solves this bug. This is an improved version which avoids to create unnecessary
new nodes (and memory leaks).

No new compiling needed, so this can be done even by beginners.

Should work in versions at least from 15.04 to 16.12, probably more.

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

[plasmashell] [Bug 371858] Occasional wrong desktop at startup

[bugzilla_noreply]

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

--- Comment #19 from it...@inwind.it ---
Problem is back again for me: it may have coincided with the upgrade to Plasma
5.8.5 (27th December) or kernel 4.9.0 (today). In any case, this is what is
currently installed

- KDE Plasma 5.8.5
- KDE Frameworks 5.29
- KDE Applications 16.12.0
- Qt 5.6.2
- KDE 4 Workspace 4.11.22
- SDDM 0.14
- kernel 4.9.0

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

[kphotoalbum] [Bug 374431] Version 5.1 crashes when reading some index files

[Alex6]

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

--- Comment #8 from Alex6  ---
Thanks! it works!

Not understood where te "WANGZ^B" comes from...
Not apparently from camera: the so tagged images were transformed from Nef
Nikon D80 with Gimp for 6/7 years and saved as xcf or jpg , Gimp ignored
metadata, related nef files in this index have no "WANGZ^B" tag...
Hav*e pasted this accidentally?*

Thanks again and happy Kpa + personal/private* 2017 !!

*My taylor is rich, but my english is poor.



Le lundi 2 janvier 2017 16:56:18 CET, vous avez écrit :
> https://bugs.kde.org/show_bug.cgi?id=374431
> 
> Johannes Zarl-Zierl  changed:
> 
>What|Removed |Added
> 
>  Ever confirmed|0   |1
>  Status|UNCONFIRMED |CONFIRMED
> 
> --- Comment #7 from Johannes Zarl-Zierl  ---
> Thanks.
> 
> The issue seems to be that your camera puts the string "WANGZ^B" into the EXIF
> description.
> 
> Between Qt4 and Qt5, the handling of control characters like '\x02' ('^B')
> seems to have changed, which causes KPhotoAlbum to choke on the previously
> working database.
> 
> As an immediate workaround you can remove the '^B' characters from your
> database:
> 
>  mv index.xml index.xml.bak
>  sed 's/\x02/#/' index.xml.bak > index.xml
> 
>

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

[ksmserver] [Bug 374468] New: KSMserver crash on wake from suspend

[bugzilla_noreply]

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

Bug ID: 374468
   Summary: KSMserver crash on wake from suspend
   Product: ksmserver
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: a.harrington080...@gmail.com
  Target Milestone: ---

This was fixed for about a week but the issue has come back. Crashing on nearly
every wake from suspend.


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

Thread 2 (Thread 0x7fd2a1f36700 (LWP 1331)):
#0  0x7fd2b919056d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fd2ad7b19f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd2ad7b1b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd2b4911f5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd2b48bb8da in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd2b46e90f3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd2b98166d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fd2b46edda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fd2af6cc464 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#9  0x7fd2b91999df in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fd2a52c7940 (LWP 1322)):
[KCrash Handler]
#6  0x7fd2b912c354 in free () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x7fd2b339b771 in XIQueryDevice () from
/usr/lib/x86_64-linux-gnu/libXi.so.6
#8  0x7fd2a5068366 in QXcbConnection::handleEnterEvent() () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#9  0x7fd2a5054d18 in QXcbWindow::handleEnterNotifyEvent(int, int, int,
int, unsigned char, unsigned char, unsigned int) () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#10 0x7fd2a505528f in QXcbWindow::handleXIEnterLeave(xcb_ge_event_t*) ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#11 0x7fd2a506d3bc in QXcbConnection::xi2HandleEvent(xcb_ge_event_t*) ()
from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#12 0x7fd2a503faca in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#13 0x7fd2a5040015 in QXcbConnection::processXcbEvents() () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#14 0x7fd2b48ea399 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fd2b51a0b2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fd2b51a82e1 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7fd2b48bd8f0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fd2b48c007d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7fd2b4911b33 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7fd2ad7b17f7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fd2ad7b1a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fd2ad7b1b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fd2b4911f3f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7fd2b48bb8da in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7fd2b48c404c in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7fd2b9461591 in kdemain () from
/usr/lib/x86_64-linux-gnu/libkdeinit5_ksmserver.so
#27 0x7fd2b90d12b1 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#28 0x004006fa in _start ()

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

[systemsettings] [Bug 374467] New: kde crashes everytime

[dmera]

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

Bug ID: 374467
   Summary: kde crashes everytime
   Product: systemsettings
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: dan.m...@rogers.com
  Target Milestone: ---

Application: systemsettings5 (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-41-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
Trying to open SystemSettings and it crashes immediately.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0ce3f9b780 (LWP 19950))]

Thread 3 (Thread 0x7f0cbef38700 (LWP 19953)):
#0  0x7f0ce05ef691 in idleTimerSourcePrepare (source=0x7f0cb8002f20,
timeout=0x7f0cbef37c74) at kernel/qeventdispatcher_glib.cpp:197
#1  0x7f0cdbd034ad in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f0cdbd03d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f0cdbd03f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f0ce05eed8b in QEventDispatcherGlib::processEvents
(this=0x7f0cb80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f0ce0595d53 in QEventLoop::exec (this=this@entry=0x7f0cbef37e30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f0ce03b761a in QThread::exec (this=this@entry=0x15b7590) at
thread/qthread.cpp:503
#7  0x7f0cde937e18 in QQmlThreadPrivate::run (this=0x15b7590) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7f0ce03bc32f in QThreadPrivate::start (arg=0x15b7590) at
thread/qthread_unix.cpp:331
#9  0x7f0cdc2200a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f0cdfcca02d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f0ccff74700 (LWP 19951)):
#0  0x7f0cdfcc1bfd in poll () from /lib64/libc.so.6
#1  0x7f0cdca96422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f0cdca9800f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f0cd28fb3c9 in QXcbEventReader::run (this=0x1065ea0) at
qxcbconnection.cpp:1229
#4  0x7f0ce03bc32f in QThreadPrivate::start (arg=0x1065ea0) at
thread/qthread_unix.cpp:331
#5  0x7f0cdc2200a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f0cdfcca02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0ce3f9b780 (LWP 19950)):
[KCrash Handler]
#6  0x7f0cdfc1a0c7 in raise () from /lib64/libc.so.6
#7  0x7f0cdfc1b478 in abort () from /lib64/libc.so.6
#8  0x7f0ce03aa7ce in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=this@entry=0x7fff7ad85660,
msg=msg@entry=0x7f0cdef820aa "%s") at global/qlogging.cpp:781
#10 0x7f0cdedfde71 in QSGRenderLoop::handleContextCreationFailure
(this=this@entry=0x1546e60, window=0x156a160, isEs=isEs@entry=false) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:244
#11 0x7f0cdee06ce9 in QSGThreadedRenderLoop::handleExposure
(this=this@entry=0x1546e60, window=window@entry=0x156a160) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:919
#12 0x7f0cdee070db in QSGThreadedRenderLoop::exposureChanged
(this=0x1546e60, window=0x156a160) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:857
#13 0x7f0ce1957b69 in QWindow::event (this=this@entry=0x156a160,
ev=ev@entry=0x7fff7ad85ab0) at kernel/qwindow.cpp:2028
#14 0x7f0cdee380d1 in QQuickWindow::event (this=0x156a160,
e=0x7fff7ad85ab0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/items/qquickwindow.cpp:1413
#15 0x7f0ce20e1e7c in QApplicationPrivate::notify_helper
(this=this@entry=0x102f2d0, receiver=receiver@entry=0x156a160,
e=e@entry=0x7fff7ad85ab0) at kernel/qapplication.cpp:3716
#16 0x7f0ce20e6cc8 in QApplication::notify (this=0x7fff7ad85ea0,
receiver=0x156a160, e=0x7fff7ad85ab0) at kernel/qapplication.cpp:3499
#17 0x7f0ce0597e95 in QCoreApplication::notifyInternal
(this=0x7fff7ad85ea0, receiver=receiver@entry=0x156a160,
event=event@entry=0x7fff7ad85ab0) at kernel/qcoreapplication.cpp:965
#18 0x7f0ce19505d4 in QCoreApplication::sendSpontaneousEvent
(event=0x7fff7ad85ab0, receiver=0x156a160) at
../../src/corelib/kernel/qcoreapplication.h:227
#19 QGuiApplicationPrivate::processExposeEvent (e=0x14fb260) at
kernel/qguiapplication.cpp:2650
#20 0x7f0ce19511ed in QGuiApplicationPrivate::processWindowSystemEvent
(e=e@entry=0x14fb260) at kernel/qguiapplication.cpp:1645
#21 0x7f0ce1936268 in QWindowSystemInterface::sendWindowSystemEvents

[plasmashell] [Bug 374455] scaling, using scaling leads to pointing and displaying problems

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|WONTFIX |DUPLICATE

--- Comment #2 from David Edmundson  ---
See also linked reports, it seems one has been filed for kmail.

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

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

[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||philippe.roub...@free.fr

--- Comment #13 from David Edmundson  ---
*** Bug 374455 has been marked as a duplicate of this bug. ***

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

[calligrawords] [Bug 374466] New: Calligra crashed while saving documents

[Brian]

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

Bug ID: 374466
   Summary: Calligra crashed while saving documents
   Product: calligrawords
   Version: 2.9.11
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: br...@g2growth.com
  Target Milestone: ---

Application: calligrawords (2.9.11)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.9.0-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I opened Calligra Words and attempted to save a blank document (So I wouldn't
forget to later). It crashed all 3 times I tried doing this. The fourth time it
crashed as soon as I tried to input text.

The crash can be reproduced every time.

-- Backtrace:
Application: Calligra Words (calligrawords), signal: Bus error
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3c6676a840 (LWP 8242))]

Thread 2 (Thread 0x7f3c3fbf3700 (LWP 8266)):
#0  0x7f3c661a048d in poll () at /usr/lib/libc.so.6
#1  0x7f3c6165a786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f3c6165a89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f3c6485ceee in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQtCore.so.4
#4  0x7f3c6482b3ff in
QEventLoop::processEvents(QFlags) () at
/usr/lib/libQtCore.so.4
#5  0x7f3c6482b765 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQtCore.so.4
#6  0x7f3c64719789 in QThread::exec() () at /usr/lib/libQtCore.so.4
#7  0x7f3c6480b273 in  () at /usr/lib/libQtCore.so.4
#8  0x7f3c6471c05a in  () at /usr/lib/libQtCore.so.4
#9  0x7f3c6192a454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f3c661a97df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f3c6676a840 (LWP 8242)):
[KCrash Handler]
#6  0x7f3c661e97f8 in __memmove_avx_unaligned_erms () at /usr/lib/libc.so.6
#7  0x7f3c64ddf506 in  () at /usr/lib/libkdecore.so.5
#8  0x7f3c64ddfd64 in KSharedDataCache::insert(QString const&, QByteArray
const&) () at /usr/lib/libkdecore.so.5
#9  0x7f3c621e1fae in  () at /usr/lib/libkdeui.so.5
#10 0x7f3c621e2a43 in KIconLoader::loadIcon(QString const&,
KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () at
/usr/lib/libkdeui.so.5
#11 0x7f3c621d8d59 in  () at /usr/lib/libkdeui.so.5
#12 0x7f3c65336179 in QIcon::pixmap(QSize const&, QIcon::Mode,
QIcon::State) const () at /usr/lib/libQtGui.so.4
#13 0x7f3c4f45875d in  () at /usr/lib/libkfile.so.4
#14 0x7f3c4f458f24 in KUrlNavigator::Private::Private(KUrlNavigator*,
KFilePlacesModel*) () at /usr/lib/libkfile.so.4
#15 0x7f3c4f45b9c8 in KUrlNavigator::KUrlNavigator(KFilePlacesModel*, KUrl
const&, QWidget*) () at /usr/lib/libkfile.so.4
#16 0x7f3c4f43022e in KFileWidget::KFileWidget(KUrl const&, QWidget*) () at
/usr/lib/libkfile.so.4
#17 0x7f3c3f1f0e05 in  () at /usr/lib/kde4/kfilemodule.so
#18 0x7f3c62ccbe29 in KFileDialog::KFileDialog(KUrl const&, QString const&,
QWidget*, QWidget*) () at /usr/lib/libkio.so.5
#19 0x7f3c62ccfc38 in  () at /usr/lib/libkio.so.5
#20 0x7f3c6577a49e in QFileDialog::getSaveFileName(QWidget*, QString
const&, QString const&, QString const&, QString*, QFlags)
() at /usr/lib/libQtGui.so.4
#21 0x7f3c6407cfbd in KoFileDialog::url() () at /usr/lib/libkowidgets.so.14
#22 0x7f3c65e3ba6b in KoMainWindow::saveDocument(bool, bool, int) () at
/usr/lib/libkomain.so.14
#23 0x7f3c65e3d6af in KoMainWindow::slotFileSave() () at
/usr/lib/libkomain.so.14
#24 0x7f3c65e40b0d in  () at /usr/lib/libkomain.so.14
#25 0x7f3c64840c50 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib/libQtCore.so.4
#26 0x7f3c65285082 in QAction::triggered(bool) () at /usr/lib/libQtGui.so.4
#27 0x7f3c652863e3 in QAction::activate(QAction::ActionEvent) () at
/usr/lib/libQtGui.so.4
#28 0x7f3c656612f3 in  () at /usr/lib/libQtGui.so.4
#29 0x7f3c65661444 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /usr/lib/libQtGui.so.4
#30 0x7f3c65726a7a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib/libQtGui.so.4
#31 0x7f3c652e1840 in QWidget::event(QEvent*) () at /usr/lib/libQtGui.so.4
#32 0x7f3c6528af2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQtGui.so.4
#33 0x7f3c652935b7 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQtGui.so.4
#34 0x7f3c65e0eaf5 in KoApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkomain.so.14
#35 0x7f3c6482cb2d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib/libQtCore.so.4
#36 0x7f3c652915db in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, 

[plasmashell] [Bug 374455] scaling, using scaling leads to pointing and displaying problems

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Then you need to file bugs with those programs.

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

[plasmashell] [Bug 374310] Cannot build plasma-desktop without AppStreamQt installed

[David Edmundson]

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

--- Comment #1 from David Edmundson  ---
>Suggestion: Would it not be more fitting to implement this functionality as 
>part of the Discover framework?

In the context of the patch, it would not.

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

[krita] [Bug 374319] SIGABRT exiting Krita after transformation of a pasted image from a secondary window (Krita 3.1.1 appimage - Ubuntu 14.04)

[Phil Blackburn]

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

Phil Blackburn  changed:

   What|Removed |Added

 CC||pab...@gmail.com

--- Comment #3 from Phil Blackburn  ---
I'm unable to reproduce on Ubuntu 16.04 LTS with the most recent Krita source,
gdb reports a clean exit. Was there any other intermediate step, or saving of
images involved? How did you apply the changes in step 6?

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