[plasmashell] [Bug 373339] New: Plasma crash when returning to open session after second user creates a session

[David]

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

Bug ID: 373339
   Summary: Plasma crash when returning to open session after
second user creates a session
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: davidsbo...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-51-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

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

I locked the machine and another user created a new session and logged in to
her account, then she later locked the machine and I switched back to my
session, and unlocked it to a black screen and a crash reporting assistant.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
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 0x7fef751b88c0 (LWP 31774))]

Thread 8 (Thread 0x7feeb3015700 (LWP 31785)):
[KCrash Handler]
#6  0x7fef6f89450d in __strstr_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S:40
#7  0x7fef73257aca in QSGRenderContext::initialize(QOpenGLContext*) () at
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7fef7327b409 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7fef6ffdb7be in QThreadPrivate::start(void*) (arg=0x1219b00) at
thread/qthread_unix.cpp:331
#10 0x7fef6f0c870a in start_thread (arg=0x7feeb3015700) at
pthread_create.c:333
#11 0x7fef6f8f182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fef3ce22700 (LWP 31784)):
#0  0x7fef6f8e5b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fef6c67c39c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7feeb4002e20, timeout=, context=0x7feeb4000990) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135
#2  0x7fef6c67c39c in g_main_context_iterate
(context=context@entry=0x7feeb4000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835
#3  0x7fef6c67c4ac in g_main_context_iteration (context=0x7feeb4000990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#4  0x7fef702127eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7feeb40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fef701b9b4a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fef3ce21c90, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fef6ffd6834 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x7fef73204ed6 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7fef6ffdb7be in QThreadPrivate::start(void*) (arg=0x12f2090) at
thread/qthread_unix.cpp:331
#9  0x7fef6f0c870a in start_thread (arg=0x7fef3ce22700) at
pthread_create.c:333
#10 0x7fef6f8f182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fef3f7bc700 (LWP 31782)):
#0  0x7fef6f0ce3b0 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fef74c23bd4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fef74c23c19 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fef6f0c870a in start_thread (arg=0x7fef3f7bc700) at
pthread_create.c:333
#4  0x7fef6f8f182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fef4515d700 (LWP 31781)):
#0  0x7fef6f8e169d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fef6c6bf740 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fef4515cae0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7fef6c6bf740 in g_wakeup_acknowledge (wakeup=0x7fef40002720) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gwakeup.c:210
#3  0x7fef6c67be84 in g_main_context_check
(context=context@entry=0x7fef38000990, max_priority=2147483647,
fds=fds@entry=0x7fef38002e70, n_fds=n_fds@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3632
#4  0x7fef6c67c340 in g_main_context_iterate
(context=context@entry=0x7fef38000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3837
#5  0x7fef6c67c4ac in g_main_context_iteration (context=0x7fef38000990,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#6  0x7fef702127eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fef380008c0, flags=...) at 

[plasmashell] [Bug 372384] Memory leak in plasmashell

[Lastique]

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

--- Comment #9 from Lastique  ---
Downgrading Nvidia driver to 367.57 does not help.

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

[kdevelop] [Bug 368555] KDevelop crashes when you attempt to "Kill All Jobs" when no jobs are running

[Bernd Buschinski]

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

Bernd Buschinski  changed:

   What|Removed |Added

 CC||b.buschin...@googlemail.com

--- Comment #2 from Bernd Buschinski  ---
I have the same crash here, with some "dangling" background parser, it was
running forever with 0% progress. I guess I triggered it by using "ccmake"
outside of kdevelop (in the same build dir as configured for kdevelop) and
changing the build type (from Debug to Release, +configure).

I will post the trace as I can reproduce it with kdevelop 5.0.3 and have at
least some debug symbols

Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0672ae5780 (LWP 14836))]

Thread 14 (Thread 0x7f0612ffd700 (LWP 20680)):
#0  pthread_cond_timedwait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f06891228f8 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f068911f312 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x7f06891222ac in ?? () from /usr/lib64/libQt5Core.so.5
#4  0x7f06828113d4 in start_thread (arg=0x7f0612ffd700) at
pthread_create.c:333
#5  0x7f06889d1e3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f06125db700 (LWP 15743)):
#0  0x7f06889c8d7d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f068083287c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f068083298c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f06893115db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f06892c11ca in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f068911dde4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f0686bcb26b in KDevelop::CompletionWorkerThread::run
(this=0x6fb1540) at
/var/tmp/portage/dev-util/kdevplatform-5.0.3/work/kdevplatform-5.0.3/language/codecompletion/codecompletionmodel.cpp:89
#7  0x7f06891222ac in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f06828113d4 in start_thread (arg=0x7f06125db700) at
pthread_create.c:333
#9  0x7f06889d1e3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f0613fff700 (LWP 14934)):
#0  0x7ffdc9b79909 in ?? ()
#1  0x7ffdc9b79ad7 in clock_gettime ()
#2  0x7f06889de916 in __GI___clock_gettime (clock_id=1, tp=0x7f0613ffeb90)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f06891c03b3 in ?? () from /usr/lib64/libQt5Core.so.5
#4  0x7f068930fba9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#5  0x7f068930ff85 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f068931113c in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7f0689311205 in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f0680831d4d in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#9  0x7f06808327a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#10 0x7f068083298c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#11 0x7f06893115db in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#12 0x7f06892c11ca in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#13 0x7f068911dde4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#14 0x7f06891222ac in ?? () from /usr/lib64/libQt5Core.so.5
#15 0x7f06828113d4 in start_thread (arg=0x7f0613fff700) at
pthread_create.c:333
#16 0x7f06889d1e3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f06325a0700 (LWP 14909)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f068912291a in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f067e78a34f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f067e78e398 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f067e78950d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f067e78e3f2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f067e78950d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f067e78e3f2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f067e78950d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f067e78e3f2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f067e78950d in

[neon] [Bug 373138] kmail complains about missing libgpgme-pthread.so.11

[Eric BURGHARD]

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

Eric BURGHARD  changed:

   What|Removed |Added

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

--- Comment #3 from Eric BURGHARD  ---
I confirmed this is resolved from today update (dev/stable).

Thanks a lot guys. You definitively rock !

I don't understand those criticism towards kontact. I was just annoyed the
whole week by the ergonomy and search functionality of thunderbird.

Thanks a lot for the time you are dedicating making kde always better.

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

[kdenlive] [Bug 351381] 16.08.0: no timeline preview for 60fps FullHD project

[bugzilla_noreply]

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

--- Comment #23 from h.k.gh...@gmail.com ---
(In reply to Wegwerf from comment #21)
> Vincent, thank you for adding these profiles! Seems as if ghosts have no
> thanks...?

I have (finally) returned with some results. (Sorry I took so long. I had other
things to take care of and did not try to edit any videos until this past
weekend.)

I'm using version v17.03.70 on
 * KDE Frameworks 5.26.0
 * Qt 5.6.1 (built against 5.6.1)
 * The xcb windowing system

I tried the preview render option with the preview profile and, while it still
needs time and processing power to do that, it's still an improvement, since I
don't need to keep rendering independent sections and trying to see them
outside without the timing data. It's far from ideal, but it's still more
usable than the previous alternative, and therefore, gets my thumbs up.

Although I'm not a pro at editing by any stretch, I'm looking forward to
additional performance improvements that will (hopefully) remove the need to
rely on preview-rendering entirely (e.g. GPU-based stuff going stable and
working very well).

Best Regards.

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

[krita] [Bug 373338] New: Add clone layers of many layers at once

[Spencer Brown]

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

Bug ID: 373338
   Summary: Add clone layers of many layers at once
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: sbrown...@gmail.com
  Target Milestone: ---

Let's say I've got sixteen layers in my base color texture for different
material layers. If I want to clone these layers to inherit alpha from for
another BRDF parameter, I have to click each layer, click the arrow next to the
add layer button, and add a clone layer for each. Then I have to select all of
the layers and drag them into the group for the next BRDF parameter I'm working
on. This can get a bit tedious.

I would like to be able to select multiple layers, right click them, click a
menu item called "Clone these layers" or something similar, and get a big old
stack of clones, selected and ready to go where I need them, above the topmost
layer in my selection.

What do you think?

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

[krita] [Bug 373337] New: Add blending mode to copy red channel to transparency

[Spencer Brown]

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

Bug ID: 373337
   Summary: Add blending mode to copy red channel to transparency
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: sbrown...@gmail.com
  Target Milestone: ---

I've been meaning to add this feature for a while and just haven't gotten
around to it yet.

A lot of game engines expect greyscale textures to be packed into multiple
channels to save texture memory. Copy red, copy green, and copy blue are very
convenient ways to do this for the color channels, but they don't help pack a
greyscale mask into the alpha channel. With DXT5 compression the alpha channel
is compressed separately so it's a good choice for masks that have
high-frequency data or data that doesn't change along with the other masks.

This blending mode would copy the contents of the red channel to the alpha
channel, eliminating the need to copy your alpha channel mask merged and
convert it to a transparency mask every time you change the alpha mask. Putting
the red channel into the alpha channel is also useful for DXT5 normal map
compression which is still used sometimes for compatibility reasons.

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

[kmail2] [Bug 373332] Akondai

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
it's

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

[kmail2] [Bug 373332] Akondai

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Laurent Montel  ---
it's a bug with new nouveau driver.

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

[dolphin] [Bug 369523] DolphinPart: Cannot paste without refreshing the destination tab/window

[Jonathan Marten]

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

Jonathan Marten  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/dol
   ||phin/16db90c7938d09bfa8916a
   ||fef8cce8dd258fa00d
 Status|CONFIRMED   |RESOLVED

--- Comment #7 from Jonathan Marten  ---
Git commit 16db90c7938d09bfa8916afef8cce8dd258fa00d by Jonathan Marten.
Committed on 06/12/2016 at 06:59.
Pushed by marten into branch 'master'.

Dolphin Part: Update the paste action at the end of the listing

Fixes a problem with the paste action not being enabled, only seen in
Konqueror.
REVIEW:129448

M  +1-0src/dolphinpart.cpp

https://commits.kde.org/dolphin/16db90c7938d09bfa8916afef8cce8dd258fa00d

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

[krita] [Bug 373336] New: Layer styles use alpha of the layer incorrectly, resulting in color fringes in semitransparent areas

[Spencer Brown]

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

Bug ID: 373336
   Summary: Layer styles use alpha of the layer incorrectly,
resulting in color fringes in semitransparent areas
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: layer styles
  Assignee: krita-bugs-n...@kde.org
  Reporter: sbrown...@gmail.com
  Target Milestone: ---

Created attachment 102639
  --> https://bugs.kde.org/attachment.cgi?id=102639=edit
This file has a layer with semitransparent strokes and a color overlay layer
style in Normal blending mode.

The strokes are in green and the color overlay is a blue color. There are
visible green fringes in the semitransparent areas of the stroke. These areas
should be blue, not green.

The correct behavior for the color overlay layer style in normal blending mode
should be functionally equivalent to grouping the layer and adding a fill layer
with the color blue set to inherit alpha.

I've also noticed this problem on the inner glow layer style (I think.)

Color overlay layer style is pretty handy in some texture art situations, for
example making a specular power texture for a gun skin for Counter-Strike:
Global Offensive. Specular power textures have big flat areas, and the exact
values required to produce the correct effect can be somewhat unpredictable.
Color overlay is a lot more concise and easy to change than making another
group for specular power and adding a bunch of clone layers from the main layer
stack and putting color fill layers with inherit alpha over those clone layers.
To pack the specular power into the alpha channel of the texture (which is the
format that the game engine expects), you select all layers, enable layer
effects in the layer properties, copy merged, paste, move the layer to the top,
and convert that merged layer to a transparency mask.

Inner (and outer) glow is useful to make certain types of alphas for Zbrush
sculpting, or to convert line art to signed distance fields for crisp line art
rendering in a non-photorealistic renderer without having to use
nearest-neighbor filtering and broken-up texture coordinates.

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

[kmail2] [Bug 373313] Make From field in the composer read only

[Laurent Montel]

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

--- Comment #1 from Laurent Montel  ---
it was never changed and we can change for sure.
Which is your kmail version ? 
could you paste a screenshot to show me where you want to change settings.
Thanks

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

[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps

[Darin Miller]

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

Darin Miller  changed:

   What|Removed |Added

 CC||darinsmil...@gmail.com

--- Comment #16 from Darin Miller  ---
Adding a note from a remmina perspective:

Meta keys are used frequently when remoting into a Windows box:
 by itself on windows provides same functionality as Kicker (user text
search for applications and files)
+D minimizes all windows
+e file manager (Explorer)
+ splits window half screen in corresponding arrow direction.
+ windows settings
etc.

Options:
1. Disable kicker meta shortcut entirely
2. Disable meta key with script when launching key capturing applications,
re-enable when application is closed.  This is a pseudo solution, as kicker
would not work while app is running.  I switch to local desktop frequently when
remoted to a windows box. Though I use krunner to launch most of apps, I would
have used the meta key long ago if it worked.  Thus, new users will expect it
to work if switching from windows.
3. Provide a list of apps in a config file or possibly a "window rules" setting
that will disable the kicker meta key when they have focus.  However, this
requires the user to maintain the key grab setting in the app and in the config
file.
4. Honor the key capture state of the application that has focus. Can the key
capture state of an app be determined when the app obtains focus? If so, auto
disable meta-kicker relationship when respective apps are set to capture the
keyboard and re-enable when non-key capturing apps or local desktop has focus.


Option 4 is preferred as it requires the least amount of configuration. 
Options 1, 2 and 3 keep KDE in the tinkerer's realm and discourages users who
do not like to fiddle with their system.

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

[krita] [Bug 373335] New: Color management: use system monitor profile has no effect in Krita 3.x

[Spencer Brown]

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

Bug ID: 373335
   Summary: Color management: use system monitor profile has no
effect in Krita 3.x
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: sbrown...@gmail.com
  Target Milestone: ---

Possibly related to https://bugs.kde.org/show_bug.cgi?id=373334

In Krita 2.9.x checking Use system monitor profile would change the display
profiles to the display profile that was loaded for your monitor (if one was
loaded.) This was a really nice feature (even if it just worked in Linux iirc)
and it doesn't seem to work in 3.x.

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

[krita] [Bug 373334] New: Color management: adding new display color profiles in Krita settings has no effect

[Spencer Brown]

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

Bug ID: 373334
   Summary: Color management: adding new display color profiles in
Krita settings has no effect
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: sbrown...@gmail.com
  Target Milestone: ---

Created attachment 102638
  --> https://bugs.kde.org/attachment.cgi?id=102638=edit
Here's a display profile from a monitor of mine that you can use to test the
functionality. This particular display doesn't have great color accuracy so you
should be able to notice the difference.

The bit of UI in question is in Settings > Configure Krita > Color Management >
Display > Add new color profile. Clicking the button shows a file chooser where
you can pick out color profiles of your display. After opening the selected ICC
profile, it should show up in the list of color profiles that can be used for
display. However, in all Krita 3 versions I've tested, the new display color
profile doesn't show up in the list.

Unfortunately I haven't got the time to debug and patch this right now.

In Krita 2.9 the new display color profile was kind of anywhere in the display
profiles list (as far as I could tell.) It would be nice if the new profile
showed up in a predictable place, e.g. the beginning of the list.

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

[konsole] [Bug 280738] Select text with mouse in bidi text, like Arabic, highlights wrong part of sentence

[alekulyn]

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

alekulyn  changed:

   What|Removed |Added

 CC||aleku...@gmail.com

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

[digikam] [Bug 373272] No longer shows video previews

[bugzilla_noreply]

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

--- Comment #2 from nikol...@rath.org ---
I have the gstreamer codecs installed, and parole (which uses gstreamer) is
able to play the files.

But that said, shouldn't the codecs be included in the AppImage?

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

[konsole] [Bug 373333] New: Writing in Arabic while in BiDi mode shifts line down, truncating characters

[alekulyn]

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

Bug ID: 37
   Summary: Writing in Arabic while in BiDi mode shifts line down,
truncating characters
   Product: konsole
   Version: 16.08.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: aleku...@gmail.com
  Target Milestone: ---

When Arabic text is written to the terminal, the entire line is shifted down
and letters that dip low are truncated.  This is only a problem when BiDi is
enabled in the current profile.  Turning BiDi off fixes this, but BiDi is
necessary because Arabic is an RTL language.

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

[kmail2] [Bug 223812] Searching doesn't work

[André Verwijs]

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

André Verwijs  changed:

   What|Removed |Added

 CC||dutchgig...@gmail.com

--- Comment #18 from André Verwijs  ---
i have the same in kubuntu 17.04

related to:
304252

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

[kmail2] [Bug 304252] Searching doesn't work

[André Verwijs]

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

André Verwijs  changed:

   What|Removed |Added

 CC||dutchgig...@gmail.com

--- Comment #2 from André Verwijs  ---
i have the same with kubuntu 17.04


related to:
223812

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

[kmail2] [Bug 373332] New: Akondai

[HAJ]

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

Bug ID: 373332
   Summary: Akondai
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: current...@gmail.com
  Target Milestone: ---

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.10-200.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
It crashes all the freaking time

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fac395ec940 (LWP 10839))]

Thread 33 (Thread 0x7fabcef27700 (LWP 10898)):
#0  0x7fac4eff0bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fac42a29bc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7fac42a29c09 in  () at /lib64/libQt5Script.so.5
#3  0x7fac4efeb5ca in start_thread () at /lib64/libpthread.so.0
#4  0x7fac5de3b0ed in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7fabcff5a700 (LWP 10895)):
#0  0x7fac4dbb1a24 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7fac4db6d419 in g_main_context_check () at /lib64/libglib-2.0.so.0
#2  0x7fac4db6d9a4 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fac4db6db1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fac5ec3524b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7fac5ebe45ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7fac5ea43343 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7fac5ea4799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fac4efeb5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fac5de3b0ed in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7fabd1da6700 (LWP 10887)):
#0  0x7fac5ec33c8e in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#1  0x7fac5ec34dac in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#2  0x7fac5ec34e75 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#3  0x7fac4db6cf59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#4  0x7fac4db6d92b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#5  0x7fac4db6db1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#6  0x7fac5ec3524b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#7  0x7fac5ebe45ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#8  0x7fac5ea43343 in QThread::exec() () at /lib64/libQt5Core.so.5
#9  0x7fac5ea4799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7fac4efeb5ca in start_thread () at /lib64/libpthread.so.0
#11 0x7fac5de3b0ed in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7fabd29d7700 (LWP 10880)):
#0  0x7fac4dbb1a09 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7fac4db6cf65 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7fac4db6d92b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7fac4db6db1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7fac5ec3524b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7fac5ebe45ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7fac5ea43343 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7fac5ea4799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fac4efeb5ca in start_thread () at /lib64/libpthread.so.0
#9  0x7fac5de3b0ed in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7fabd619c700 (LWP 10879)):
#0  0x7fac4eff0bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fac55e7be79 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7fac55e7c540 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7fac55e7c710 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7fac55e790fd in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7fac4efeb5ca in start_thread () at /lib64/libpthread.so.0
#6  0x7fac5de3b0ed in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7fabd6ff3700 (LWP 10875)):
#0  0x7fac4eff0bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fac55e7be79 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at 

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

[bugzilla_noreply]

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

d_p_le...@yahoo.com changed:

   What|Removed |Added

 CC||d_p_le...@yahoo.com

--- Comment #2 from d_p_le...@yahoo.com ---
I am also affected by this. 
Debian Testing (Stretch),
Plasma 5.8.2
Turning on scale factor makes random horizontal lines appear in Konsole, on
both screens (one is hidpi, the other is a regular screen).
Resizing Konsole windows makes these lines appear and disappear.

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

[frameworks-kded] [Bug 372904] kded5 maxing one CPU core after search performed in Dolphin

[Gerardo Exequiel Pozzi]

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

--- Comment #2 from Gerardo Exequiel Pozzi  ---
Similar thing happens here, not only CPU usage, but lots of memory is used.
after some time, CPU usage becomes 0, but memory usage keeps high.

Also if logout the session kded5 keeps in memory until explicit "kill -KILL" is
sent.

Running "standalone" dolphin (ie from Xfce) does not have this issue, since not
kded5 is running.

Tomorrow I will test disabling services.

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

[plasmashell] [Bug 373331] New: Add option to disable scroll on system tray

[evea]

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

Bug ID: 373331
   Summary: Add option to disable scroll on system tray
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: everm...@pc-portal.at
  Target Milestone: 1.0

Please add an option to disable the work space switching on the task with the
scroll wheel.


Maybe add a drop down menu where you can also select "change volume/change work
space/disabled" to run:

qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "increase_volume"
qdbus org.kde.kglobalaccel /component/kmix invokeShortcut "decrease_volume"

Thanks.

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

[frameworks-kded] [Bug 372904] kded5 maxing one CPU core after search performed in Dolphin

[Gerardo Exequiel Pozzi]

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

Gerardo Exequiel Pozzi  changed:

   What|Removed |Added

 CC||vmlinuz...@gmail.com

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

[systemsettings] [Bug 373330] New: systemsettings5 crashes after leaving application style area

[Sebastian Dicke]

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

Bug ID: 373330
   Summary: systemsettings5 crashes after leaving application
style area
   Product: systemsettings
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: sdi...@live.de
  Target Milestone: ---

Application: systemsettings5 (5.8.2)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

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

Opened the application, opened application style section, gone to window
decorations tab and clicked on the back buttom. Then, in the most cases, a
segmentation fault occures.

The crash can be reproduced sometimes.

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

Thread 4 (Thread 0x7fa8d8895700 (LWP 19448)):
#0  0x7fa8fd32b56d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa8f86299f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8f8629b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa8fdc496fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa8fdbf307a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8fda150d3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa8fc39b5d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa8fda19d88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa8fa537464 in start_thread (arg=0x7fa8d8895700) at
pthread_create.c:333
#9  0x7fa8fd3349df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7fa8e6be3700 (LWP 19445)):
#0  0x7fa8fd3275dd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa8f866dc40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8f86294be in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa8f8629994 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa8f8629b0c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa8fdc496fb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa8fdbf307a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa8fda150d3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa900d6b6d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7fa8fda19d88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fa8fa537464 in start_thread (arg=0x7fa8e6be3700) at
pthread_create.c:333
#11 0x7fa8fd3349df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fa8ef685700 (LWP 19444)):
#0  0x7fa8fd32b56d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa8fadb1150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fa8fadb2ee9 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fa8f1be4b69 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fa8fda19d88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8fa537464 in start_thread (arg=0x7fa8ef685700) at
pthread_create.c:333
#6  0x7fa8fd3349df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fa900c185c0 (LWP 19442)):
[KCrash Handler]
#6  0x7fa8fc26dd85 in QV4::WeakValue::free() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa8fc2dea82 in QV4::QObjectWrapper::destroyObject(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fa8fc174dbf in QV4::MemoryManager::sweep(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fa8fc1761cc in QV4::MemoryManager::~MemoryManager() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7fa8fc25d69b in QV4::ExecutionEngine::~ExecutionEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7fa8fc39d086 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7fa8fc39d1a9 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7fa8fc1f49a6 in QJSEngine::~QJSEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7fa8fc30890d in QQmlEngine::~QQmlEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#15 0x7fa8fc3089c9 in QQmlEngine::~QQmlEngine() () from

[digikam] [Bug 373321] Add a step to check for duplicates during import from camera

[bugzilla_noreply]

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

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

   What|Removed |Added

Summary|Add a step to check for |Add a step to check for
   |duplicates during import|duplicates during import
   ||from camera

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

[digikam] [Bug 373321] Add a step to check for duplicates during import

[bugzilla_noreply]

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

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

   What|Removed |Added

Summary|Feature Request: check for  |Add a step to check for
   |duplicates during import|duplicates during import
   Severity|normal  |wishlist
 CC||caulier.gil...@gmail.com

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

[digikam] [Bug 373247] No chronological ordering of tags anymroe

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|5.2.0   |5.4.0

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

[digikam] [Bug 369083] database migration sets wrong parent ids for tags

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|5.1.0   |5.4.0

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

[krita] [Bug 373329] New: Problem with Krita

[Ariel]

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

Bug ID: 373329
   Summary: Problem with Krita
   Product: krita
   Version: 3.0.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: langley...@msn.com
  Target Milestone: ---

So, I'm not exactly sure if this is a bug or not. I got a new computer that had
been updated to Windows 10 and I noticed that when I use Krita the freehand
brush tool with the stabilizer on would suddenly zig-zag around, I thought it
had been my mouse since it has issues but I actually think it is just Krita
bugging out but I'm not sure. It hadn't done this before on my old computer
with the same mouse. Is there a fix to this? Or is this something else?

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Leslie Zhai]

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

--- Comment #69 from Leslie Zhai  ---
Created attachment 102637
  --> https://bugs.kde.org/attachment.cgi?id=102637=edit
cdrskin-k3b1.log

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Leslie Zhai]

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

--- Comment #68 from Leslie Zhai  ---
Git commit 702de8d57cebce3d6aefe74fa19f68d70650d0b4 by Leslie Zhai.
Committed on 06/12/2016 at 02:17.
Pushed by lesliezhai into branch 'cdrskin'.

Change arguments for Cdrskin Writter

FAILED: cdrskin-k3b1.log

CCMAIL: scdbac...@gmx.net

M  +6-3libk3b/projects/k3bcdrskinwriter.cpp

https://commits.kde.org/k3b/702de8d57cebce3d6aefe74fa19f68d70650d0b4

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

[kdeplasma-addons] [Bug 373328] New: Add an option to display the Desktop Search result in Application Dashboard more detail

[idmresettrial]

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

Bug ID: 373328
   Summary: Add an option to display the Desktop Search result in
Application Dashboard more detail
   Product: kdeplasma-addons
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Application Dashboard
  Assignee: h...@kde.org
  Reporter: idmresettr...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 102636
  --> https://bugs.kde.org/attachment.cgi?id=102636=edit
current layout

The current layout is lack of information. See the attachment image.

I think the search result will be better if it could show in
detail/list/table... mode with some columns like this for example:

Filename-Type-Filesize

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

[kdeconnect] [Bug 373327] New: KDE Connect cannot see laptop on the android app and can't see android on laptop

[Daniil Vasin]

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

Bug ID: 373327
   Summary: KDE Connect cannot see laptop on the android app and
can't see android on laptop
   Product: kdeconnect
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: danikva...@gmail.com
  Target Milestone: ---

Neither phone nor computer can see each other in their respective menus

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

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

[bugzilla_noreply]

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

nikol...@kakouros.net changed:

   What|Removed |Added

 CC||nikol...@kakouros.net

--- Comment #18 from nikol...@kakouros.net ---
I have the same problem. If I enable the PIM plugin and select calendars that
have todos inside them, then plasmashell consumes all memory. If I remove the
calendars with the todos, it works just fine.

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

[plasmashell] [Bug 373326] New: chromium lock-up, killing chromium kills plasma

[Arthur Marsh]

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

Bug ID: 373326
   Summary: chromium lock-up, killing chromium kills plasma
   Product: plasmashell
   Version: 5.8.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur.ma...@internode.on.net
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.28.0
Operating System: Linux 4.9.0-rc7+ x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
I've had plasma desktop locking up a lot recently, sometimes when shutting down
iceweasel or chromium when they have several windows/tabs open.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7f7137fff700 (LWP 15374)):
#0  0x7f71f19e556d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f71ed5879f6 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f7130002e70, timeout=, context=0x7f713990)
at ././glib/gmain.c:4228
#2  0x7f71ed5879f6 in g_main_context_iterate
(context=context@entry=0x7f713990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#3  0x7f71ed587b0c in g_main_context_iteration (context=0x7f713990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f71f23036fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f71f22ad07a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f71f20cf0d3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f71f20d3d88 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f71f11e8464 in start_thread (arg=0x7f7137fff700) at
pthread_create.c:333
#9  0x7f71f19ee9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7f713c99a700 (LWP 15372)):
#0  0x7f71f19e556d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f71ed5879f6 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f71380013c0, timeout=, context=0x7f7138000990)
at ././glib/gmain.c:4228
#2  0x7f71ed5879f6 in g_main_context_iterate
(context=context@entry=0x7f7138000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#3  0x7f71ed587b0c in g_main_context_iteration (context=0x7f7138000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f71f23036fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f71f22ad07a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f71f20cf0d3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f713cddaa35 in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#8  0x7f71f20d3d88 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f71f11e8464 in start_thread (arg=0x7f713c99a700) at
pthread_create.c:333
#10 0x7f71f19ee9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7f71453e0700 (LWP 15313)):
#0  0x7f71f11ee18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f71ce0302ab in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f71ce030107 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f71f11e8464 in start_thread (arg=0x7f71453e0700) at
pthread_create.c:333
#4  0x7f71f19ee9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7f71cf9c3700 (LWP 15294)):
#0  0x7f71f11ee18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f71f6b652c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f71f6b65309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f71f11e8464 in start_thread (arg=0x7f71cf9c3700) at
pthread_create.c:333
#4  0x7f71f19ee9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f71d997c700 (LWP 15287)):
#0  0x7f71f19fb1e0 in __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:59
#1  0x7f71f19e5562 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f71ed5879f6 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f71c8003070, timeout=, context=0x7f71c8000990)
at ././glib/gmain.c:4228
#3  0x7f71ed5879f6 in g_main_context_iterate
(context=context@entry=0x7f71c8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at 

[systemsettings] [Bug 373325] New: Impossible to UNDO an ugly screen ( Laptop selection made an horrible and difficult to use screen on my Toshiba Laptop )

[Patrick Carabin]

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

Bug ID: 373325
   Summary: Impossible to UNDO an ugly screen ( Laptop selection
made an horrible and difficult to use screen on my
Toshiba Laptop )
   Product: systemsettings
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: krdb
  Assignee: kdelibs-b...@kde.org
  Reporter: patrick.cara...@gmail.com
  Target Milestone: ---

Because I have a Laptop, i selected the «Laptop» option. Catastrophe! 
While asking to «Undo» or «restore default», I still keep a difficult-to-read
screen ), square instead of rectangular-full-screen. Please correct the «undo»
fuction which is NOT WORKING.

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

[kwin] [Bug 94470] unilaterally violate the NETWM spec to support inner xinerama struts

[Patrick Carabin]

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

Patrick Carabin  changed:

   What|Removed |Added

 CC||patrick.cara...@gmail.com

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

[plasmashell] [Bug 373131] plasmashell freezes irretrievably every few minutes -- needs to be killed

[Syd Alsobrook]

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

--- Comment #14 from Syd Alsobrook  ---
(In reply to Syd Alsobrook from comment #12)
> The new versions are:
> xserver-xorg-video-radeon:amd64 1:7.8.0-1+b1
> xserver-xorg-core:amd64 2:1.19.0-2

This were the wrong version numbers. The freeze was happening with those
versions.

I worked all of today without having to restart plasmashell. The versions in
use today are:

xserver-xorg-video-radeon:amd64 1:7.8.0-1
xserver-xorg-core:amd64 2:1.18.4-2

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

[user-manager] [Bug 373276] commit "Do not ask for root permissions when it's unnecessary" makes it difficult to add a new user

[vinnywright]

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

vinnywright  changed:

   What|Removed |Added

 CC||charles.v.wri...@gmail.com

--- Comment #3 from vinnywright  ---
same hear on Neon-/dev/stable ,cant add user , no authentication dialog.

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

[digikam] [Bug 373247] No chronological ordering of tags anymroe

[Kusi]

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

--- Comment #2 from Kusi  ---
yes, still broken in the current AppImage

The functionality was removed during the port from KCompletion to QCompleter in
commit 658d26af. I guess this happened just by accident?

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

[kontact] [Bug 373324] New: crashes at opening

[Eric]

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

Bug ID: 373324
   Summary: crashes at opening
   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.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Restart the computer after last update (zypper patch + zypper up + reboot)

- Custom settings of the application:
Many email account, many profile and aliases, many-many filters

The crash can be reproduced sometimes.

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

Thread 22 (Thread 0x7fac6d7fa700 (LWP 2423)):
#0  0x7fad19b83cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fad19b414b9 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fad19b41d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fad19b41f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fad21b24d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fad21acbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fad218f232f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fad20fe902d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7fac6e7fc700 (LWP 2421)):
#0  0x7fffb5de8b26 in clock_gettime ()
#1  0x7fad20ff5c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fad219a37d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fad21b233b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fad21b23945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fad21b24b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fad19b414ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fad19b41d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fad19b41f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fad21b24d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fad21acbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fad218f232f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fad20fe902d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7fac6effd700 (LWP 2420)):
#0  0x7fad19b83d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fad19b41759 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fad19b41dcf in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fad19b41f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fad21b24d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fad21acbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fad218f232f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fad20fe902d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7fac6f7fe700 (LWP 2414)):
#0  0x7fffb5de8b26 in clock_gettime ()
#1  0x7fad20ff5c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fad219a37d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fad21b233b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fad21b23945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fad21b24b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fad19b414ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fad19b41d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fad19b41f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fad21b24d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fad21acbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fad218f232f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fad20fe902d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7fac6700 (LWP 2413)):

[konqueror] [Bug 373323] New: Unsupported Action: Authorization failed

[Andreas Schwab]

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

Bug ID: 373323
   Summary: Unsupported Action: Authorization failed
   Product: konqueror
   Version: Git
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: sch...@linux-m68k.org
  Target Milestone: ---

When trying to visit https://intra.microfocus.net/, the following error is
displayed:

The requested operation could not be completed

Unsupported Action: Authorization failed.

Details of the Request:

URL: https://intra.microfocus.net/
Protocol: https
Date and Time: Tuesday, December 06, 2016 12:28 AM
Additional Information: Authorization failed.
Description:

The requested action is not supported by the KDE program which is implementing
the https protocol.

Possible Causes:

This error is very much dependent on the KDE program. The additional
information should give you more information than is available to the KDE
input/output architecture.
Possible Solutions:

Attempt to find another way to accomplish the same outcome.

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

[frameworks-kiconthemes] [Bug 373322] Something related to icon-cache.kcache causes the PC to hang

[Larry]

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

--- Comment #1 from Larry  ---
Created attachment 102635
  --> https://bugs.kde.org/attachment.cgi?id=102635=edit
Installed RPMs

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

[frameworks-kiconthemes] [Bug 373322] New: Something related to icon-cache.kcache causes the PC to hang

[Larry]

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

Bug ID: 373322
   Summary: Something related to icon-cache.kcache causes the PC
to hang
   Product: frameworks-kiconthemes
   Version: 5.27.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: la...@oisher.net
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Since installing Fedora 25, I've been plagued with random GUI hangs.  The
Numlock button does not change the LED display and I can't even access the
TTY's.  I tried several troubleshooting steps including disabling Search but it
still occurs.

I can resolve the problem if I SSH into the PC from another device and simply
remove ~/.cache/icon-cache.kcache.  At that point, all of the "buffered" menus
and other acts I tried while the system appeared frozen start occurring.

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

[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting

[bugzilla_noreply]

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

d_p_le...@yahoo.com changed:

   What|Removed |Added

 CC||d_p_le...@yahoo.com

--- Comment #7 from d_p_le...@yahoo.com ---
I'm getting hit by the same bug.
System:
- Debian Stretch (testing)
- KDE Plasma 5.8.2
- dual screen setup (one hidpi, one regular 1920x1200)

Same symptom as described by everybody else: an area within the dolphin window
becomes unresponsive to mouse clicks.  I can still use the cursor keys to
change the currently selected file and open a file by hitting return. But the
window is unresponsive to mouse clicks.

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

[digikam] [Bug 373321] New: Feature Request: check for duplicates during import

[Jochen]

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

Bug ID: 373321
   Summary: Feature Request: check for duplicates during import
   Product: digikam
   Version: 5.3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Keywords: usability
  Severity: normal
  Priority: NOR
 Component: Import
  Assignee: digikam-de...@kde.org
  Reporter: jochen.weya...@gmx.de
  Target Milestone: ---

Hello,
after testing some different picture managing programs I found 
that Digikam is a really superb application.

However, I think it would be nice if duplicates could be found in the importing
process. It should be avoided to add duplicates to the collection rather than
searching for duplicates in already imported material.

Especially if pictures are shared with friends or copied to an importing
directory manually, the applictaion doesn't recognise the pictures as already
known.

Maybe the already existing duplicates function can be integrated into the
import function with an option to not import duplicates.

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

[kwin] [Bug 373319] Plastik decoration hides buttons when a window is rolled up

[Alexander Schier]

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

--- Comment #2 from Alexander Schier  ---
Before you start wondering, the buttons are configured to be on the left.

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

[digikam] [Bug 369083] database migration sets wrong parent ids for tags

[bugzilla_noreply]

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

--- Comment #3 from beaaeecffmiqwryxcmbw2ta2cu...@protected32.unixadm.org ---
Yes, it's still broken, all parent ids are set to "-1".
Did a migration from version 8 (digikam-5.3.0-2.fc24.x86_64) to 8
(digikam-5.4.0-01-x86-64.appimage).

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

[kphotoalbum] [Bug 373264] Selecting a "Token" while in fullscreen (or "big eniugh") makes some of the entries on homescreen vanish

[Johannes Zarl-Zierl]

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

Johannes Zarl-Zierl  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||9be9f02
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Johannes Zarl-Zierl  ---
Thanks for the confirmation!

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

[systemsettings] [Bug 373320] New: systemsettings crash when closing

[Alexander Schier]

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

Bug ID: 373320
   Summary: systemsettings crash when closing
   Product: systemsettings
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: a...@laxu.de
  Target Milestone: ---

Application: systemsettings5 (5.8.2)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

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

I closed systemsettings, then it crashed.
Doesn't matter that much, as i wanted to close it anyway, but here is the
backtrace.

The crash can be reproduced sometimes.

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

Thread 3 (Thread 0x7f7dea30f700 (LWP 29349)):
#0  0x7f7dfa80dda2 in ?? () from
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
#1  0x7f7dfa87e0b5 in ?? () from
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
#2  0x7f7e16c2abc8 in _dl_fini () at dl-fini.c:240
#3  0x7f7e132ac920 in __run_exit_handlers (status=1, listp=0x7f7e1360f5d8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at exit.c:83
#4  0x7f7e132ac97a in __GI_exit (status=) at exit.c:105
#5  0x7f7e1103d2e5 in _XDefaultIOError () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#6  0x7f7e091d46ee in ?? ()
#7  0x0002 in ?? ()
#8  0x in ?? ()

Thread 2 (Thread 0x7f7e06644700 (LWP 29344)):
#0  0x7f7e1335656d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7e10ddc150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f7e10dddee9 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f7e091d6b69 in ?? ()
#4  0x7f7e06643d50 in ?? ()
#5  0x01ed2ae0 in ?? ()
#6  0x7f7e06643d90 in ?? ()
#7  0x01ed2e40 in ?? ()
#8  0x7fff94874f2f in ?? ()
#9  0x7f7e13a44d88 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 0x7f7e16c4a8c0 (LWP 29342)):
[KCrash Handler]
#6  0x7f7e12298d85 in QV4::WeakValue::free() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f7e12309a82 in QV4::QObjectWrapper::destroyObject(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f7e1219fdbf in QV4::MemoryManager::sweep(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f7e121a11cc in QV4::MemoryManager::~MemoryManager() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f7e1228869b in QV4::ExecutionEngine::~ExecutionEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f7e123c8086 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f7e123c81a9 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f7e1221f9a6 in QJSEngine::~QJSEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7f7e1233390d in QQmlEngine::~QQmlEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#15 0x7f7e123339c9 in QQmlEngine::~QQmlEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#16 0x7f7e13c4a4b1 in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f7e13c5382f in QObject::~QObject() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f7e12694084 in QQuickWindow::~QQuickWindow() () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#19 0x7f7e12743c19 in QQuickView::~QQuickView() () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#20 0x7f7e1516ea55 in QWindowContainer::~QWindowContainer() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f7e1516ea79 in QWindowContainer::~QWindowContainer() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f7e13c4a4b1 in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f7e1514cb2b in QWidget::~QWidget() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7f7e1514ce19 in QWidget::~QWidget() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7f7e13c4a4b1 in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f7e1514cb2b in QWidget::~QWidget() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x7f7e1514ce19 in QWidget::~QWidget() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x7f7e13c4a4b1 in QObjectPrivate::deleteChildren() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f7e1514cb2b in QWidget::~QWidget() () 

[kwin] [Bug 373319] Plastik decoration hides buttons when a window is rolled up

[Alexander Schier]

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

--- Comment #1 from Alexander Schier  ---
Doesn't happen with Breeze theme.

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

[kwin] [Bug 373319] New: Plastik decoration hides buttons when a window is rolled up

[Alexander Schier]

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

Bug ID: 373319
   Summary: Plastik decoration hides buttons when a window is
rolled up
   Product: kwin
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: a...@laxu.de
  Target Milestone: ---

Created attachment 102634
  --> https://bugs.kde.org/attachment.cgi?id=102634=edit
Screenshot of a rolled up title bar

Steps to reproduce:
- Use Plastik as Window Decoration
- Roll up window (i.e. scroll with the mouse wheel on the title bar)
- Text and Buttons disappear
- You can see a tiny rest of the buttons at the top of the titlebar

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

[konqueror] [Bug 373318] Crash on visiting https://competitions.codalab.org

[Tristan Miller]

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

--- Comment #1 from Tristan Miller  ---
15 minutes and it still claims to be generating the backtrace.  I'm just going
to kill it.

I tried opening the same page on another machine with Konqueror 4.14.8 and it
worked fine.

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

[kphotoalbum] [Bug 373264] Selecting a "Token" while in fullscreen (or "big eniugh") makes some of the entries on homescreen vanish

[Andreas Schleth]

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

Andreas Schleth  changed:

   What|Removed |Added

 CC||schleth...@web.de

--- Comment #2 from Andreas Schleth  ---
I can confirm the fix with git-master (Version v5.0.1-72-gb7cf518, which is
newer than 9be..).  
Thanks, Andreas

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

[konqueror] [Bug 373318] New: Crash on visiting https://competitions.codalab.org

[Tristan Miller]

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

Bug ID: 373318
   Summary: Crash on visiting https://competitions.codalab.org
   Product: konqueror
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: psychon...@nothingisreal.com
  Target Milestone: ---

Upon visiting https://competitions.codalab.org Konqueror 4.14.26 immediately
segfaults.  It offers to produce a backtrace for me, but it's been stuck on
"Generating backtrace… (this may take some time)" (using 100% CPU) for five
minutes now.  If it ever terminates, I'll attach the backtrace.  Otherwise,
consider this to be a hang as well as a crash…

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

[kwin] [Bug 373268] Application dependent tearing with OpenGL

[Curtis Seizert]

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

--- Comment #4 from Curtis Seizert  ---
What I have set up at the moment is one screen that is actually connected to
two displays and one screen that is just a dummy.  This is so that I can
overclock my graphics card that is not driving a display.

When I disconnect one of my monitors, this does not resolve the problem, but if
I comment out the relevant sections of my xorg.conf file (see below), this does
solve the problem.  Unfortunately, it also makes me unable to overclock my
second GPU, which I would really like to be able to do.

Is there a way to specify which screen gets vsynced?  That would presumably
solve my problem and allow me to overclock my second GPU as well.

Below is the xorg.conf file that results in no tearing.  If I remove the
comments, there is tearing.

xorg.conf:

Section "ServerLayout"
Identifier "Layout0"
Screen  0  "Screen0" 0 0
#Screen "Screen1"
InputDevice"Keyboard0" "CoreKeyboard"
InputDevice"Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Module"
Load   "dbe"
Load   "extmod"
Load   "type1"
Load   "freetype"
Load   "glx"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "LG Electronics LG Ultra HD"
HorizSync   30.0 - 135.0
VertRefresh 56.0 - 61.0
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName  "LG Electronics LG Ultra HD"
HorizSync   30.0 - 135.0
VertRefresh 56.0 - 61.0
Option "DPMS"
EndSection

#Section "Monitor"
#Identifier "Monitor2"
#EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "GeForce GTX 1070"
BusID  "PCI:3:0:0"
Option "UseEdidDpi" "FALSE"
Option "DPI" "144x144"
EndSection

Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName  "GeForce GTX 1080"
BusID  "PCI:4:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
DefaultDepth24
Option "Coolbits" "12"
Option "Stereo" "0"
Option "nvidiaXineramaInfoOrder" "DFP-4"
Option "metamodes" "DP-0: nvidia-auto-select +3840+0, DP-2:
nvidia-auto-select +0+0"
Option "SLI" "Off"
Option "MultiGPU" "Off"
Option "BaseMosaic" "off"
SubSection "Display"
Depth   24
EndSubSection
EndSection

#Section "Screen"
#Identifier "Screen1"
#Device "Device1"
#Monitor"Monitor2"
#Option "Coolbits" "12"
#EndSection

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

[plasmashell] [Bug 373317] New: Plasma crashed on switching activities

[bugzilla_noreply]

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

Bug ID: 373317
   Summary: Plasma crashed on switching activities
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kb...@gmx.de
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.9-1-MANJARO x86_64
Distribution: "Manjaro Linux"

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

I switched from one activity to another. Both already were active.

- Unusual behavior I noticed:

The cursor began to lag behind. The background was switched to the one of the
activity I switched to, but the plasmashell task switcher still displayed the
old windows. After a few seconds, the background went to black, the plasmashell
completely disappeared and restarted. Afterwards, everything went back to
normal.

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

Thread 19 (Thread 0x7f494ad58700 (LWP 30252)):
#0  0x7f8a5716a72a in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f8a5716a89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#2  0x7f8a5c7c472b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f8a5c76e23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f8a5c5910f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f8a5f8f42d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f8a5c595d78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f8a5b6a5454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f8a5beab7df in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f4956fff700 (LWP 8582)):
#0  0x7f8a5beb8092 in __libc_disable_asynccancel () at /usr/lib/libc.so.6
#1  0x7f8a5be9e4f9 in read () at /usr/lib/libc.so.6
#2  0x7f8a4f185f81 in pa_read () at
/usr/lib/pulseaudio/libpulsecommon-9.0.so
#3  0x7f8a4f81550e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0
#4  0x7f8a4f815f80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#5  0x7f8a4f816040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#6  0x7f8a4f824069 in  () at /usr/lib/libpulse.so.0
#7  0x7f8a4f1b4ed8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#8  0x7f8a5b6a5454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f8a5beab7df in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f8972135700 (LWP 8581)):
#0  0x7f8a571afdb9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f8a5716a680 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f8a5716a89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f8a5c7c472b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f8a5c76e23a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f8a5c5910f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f8a5f8f42d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f8a5c595d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f8a5b6a5454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f8a5beab7df in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f8972ffd700 (LWP 4247)):
#0  0x7f8a5b6ab10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8a5c596c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f89a22f71c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f89a22fb988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f89a22f6263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f89a22fb9e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f89a22f6263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f89a22f91f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f8a5c595d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f8a5b6a5454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f8a5beab7df in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f89737fe700 (LWP 4246)):
#0  0x7f8a5b6ab10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f8a5c596c2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f89a22f71c0 in

[krita] [Bug 373316] New: center or follow layer in timeline when going down the layer stack

[Bollebib]

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

Bug ID: 373316
   Summary: center or follow layer in timeline when going down the
layer stack
   Product: krita
   Version: 3.0.2 Alpha
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: kwadraatn...@hotmail.com
  Target Milestone: ---

when you go up or down the layer stack, krita shows the layer in focus. even if
you scroll out of range,if you do one "page up" shortcut it will refocus on the
layer,and show it. This also happens when you PICK the layer on the canvas. 

but it doesn not happen for the timeline and I would like that it does.

This should perhaps be an option though, but for now i don't see what
advantages the current way of working has compared to the one i propose.

Selecting a layer in the layer box should also focus that layer in the
timeline.

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

[krita] [Bug 373315] playback cache doesn't get loaded in a good way

[Bollebib]

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

Bollebib  changed:

   What|Removed |Added

 OS|Linux   |MS Windows

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

[krita] [Bug 373315] New: playback cache doesn't get loaded in a good way

[Bollebib]

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

Bug ID: 373315
   Summary: playback cache doesn't get loaded in a good way
   Product: krita
   Version: 3.0.2 Alpha
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: kwadraatn...@hotmail.com
  Target Milestone: ---

it takes sometimes a long time and multiple 'playbacks' before all the frames
are rendered and retained in cache for fluid playback

When that happens,playback is great. But before that it chugs and sputters
anyway so that doesn't seem to useful.

there should perhaps be a rule that krita force-loads the frames before
playback,instead of gradually like it does now.

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

[kmail2] [Bug 373314] New: Verify GPG key emails when signing an email

[William L . Thomson Jr .]

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

Bug ID: 373314
   Summary: Verify GPG key emails when signing an email
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: wlt...@o-sinc.com
  Target Milestone: ---

Not sure if this is a kmail bug or other. I think it is something Kmail can
address. Since the from field in the composer ng is editable. You can spoof
someone elses email address really easily. I accidentally did that, and Kmail
allowed me to sign an email. Despite the from address in the email not being
one of the email address in my GPG key.

Seems Kmail should only sign an email with a GPG Key that contains the From
address in the email.

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

[kmail2] [Bug 373313] New: Make From field in the composer read only

[William L . Thomson Jr .]

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

Bug ID: 373313
   Summary: Make From field in the composer read only
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composereditor-ng
  Assignee: mon...@kde.org
  Reporter: wlt...@o-sinc.com
  Target Milestone: ---

In newer versions of Kmail, the composer was changed so the From field is not
editable. It does change when you change accounts/identities. But it also
allows you to type in an email. Which I accidentally swapped a To address into
From, and spoofed someones email. Really should not be able to use an email
address without it being in an account. Or at minimum make it an option that
can be turned on off. I almost never need to edit my email address, so being
editable just makes such mistakes possible where they were not before.

Thank you for your consideration!

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

[plasmashell] [Bug 373312] New: In mirrored display widgets disappear when moved

[Enrico]

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

Bug ID: 373312
   Summary: In mirrored display widgets disappear when moved
   Product: plasmashell
   Version: 5.8.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: enr...@pressmail.ch
CC: plasma-b...@kde.org
  Target Milestone: 1.0

In my configuration I use two displays that are mirrored with the desktop
layout. I have both displays on top of each other in the configuration, the
unifying output option does not stick and is gone after each restart. 

The issue:
Placing an icon from the application menu on the desktop works, but after
moving the icon on the desktop it disappears. It returns when I open the add
widgets option after a right click on the desktop. After a restart it is gone
again(including all other widgets) and like before can be made to reappear with
adding a widget. Another way to get them back is by placing the displays side
by side in the interface, only one display will have them in that scenario. 

It almost seems that mirroring the displays creates two desktops one where the
widgets go to and one that does not have them. 

I have had this issue on Fedora from F23 to F24 and on Opensuse Tumbleweed, I
think from version 5.4 and up.

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

[konsole] [Bug 373311] New: Konsole crash when creating a new tab.

[Michael Mol]

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

Bug ID: 373311
   Summary: Konsole crash when creating a new tab.
   Product: konsole
   Version: 16.08.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: mike...@gmail.com
  Target Milestone: ---

Application: konsole (16.08.3)
 (Compiled from sources)
Qt Version: 5.6.2
Frameworks Version: 5.28.0
Operating System: Linux 4.4.6-gentoo x86_64
Distribution: "NAME=Gentoo"

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

Creating a new tab, with an aim to drag it out to create a new window on a
different display.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f24bc5df7c0 (LWP 4616))]

Thread 3 (Thread 0x7f24b9fe0700 (LWP 4617)):
#0  0x7f24cc47014d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f24c5e5f8f2 in poll (__timeout=-1, __nfds=1, __fds=0x7f24b9fdfd00)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x18702f0, cond=cond@entry=0x1870330,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_conn.c:479
#3  0x7f24c5e616df in xcb_wait_for_event (c=0x18702f0) at
/var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_in.c:693
#4  0x7f24bc34b569 in QXcbEventReader::run (this=0x187e3e0) at
qxcbconnection.cpp:1331
#5  0x7f24c8eb989c in QThreadPrivate::start (arg=0x187e3e0) at
thread/qthread_unix.cpp:365
#6  0x7f24c5a3b444 in start_thread (arg=0x7f24b9fe0700) at
pthread_create.c:334
#7  0x7f24cc47912d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f24b3972700 (LWP 4618)):
#0  0x7f24c3f8a097 in g_main_context_iteration (context=0x7f24ac000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3894
#1  0x7f24c90a763c in QEventDispatcherGlib::processEvents
(this=0x7f24ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#2  0x7f24c9059a8a in QEventLoop::exec (this=this@entry=0x7f24b3971dd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:206
#3  0x7f24c8eb5154 in QThread::exec (this=this@entry=0x7f24ccac9240
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#4  0x7f24cca5c235 in QDBusConnectionManager::run (this=0x7f24ccac9240
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#5  0x7f24c8eb989c in QThreadPrivate::start (arg=0x7f24ccac9240 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:365
#6  0x7f24c5a3b444 in start_thread (arg=0x7f24b3972700) at
pthread_create.c:334
#7  0x7f24cc47912d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f24bc5df7c0 (LWP 4616)):
[KCrash Handler]
#6  QHashData::nextNode (node=node@entry=0x5f37101) at tools/qhash.cpp:557
#7  0x7f24cc13b607 in QHash::const_iterator::operator++
(this=) at /usr/include/qt5/QtCore/qhash.h:384
#8  QHash::keys (this=this@entry=0x5d480c8) at
/usr/include/qt5/QtCore/qhash.h:638
#9  0x7f24cc13afa8 in Konsole::Vt102Emulation::updateTitle (this=0x5d477b0)
at
/var/tmp/portage/kde-apps/konsole-16.08.3-r1/work/konsole-16.08.3/src/Vt102Emulation.cpp:429
#10 0x7f24c9082592 in QtPrivate::QSlotObjectBase::call (a=0x7ffe71ab9c00,
r=0x5d477b0, this=0x5d3b270) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#11 QMetaObject::activate (sender=sender@entry=0x5d44040,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3715
#12 0x7f24c9082a97 in QMetaObject::activate (sender=sender@entry=0x5d44040,
m=m@entry=0x7f24c928ff00 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3595
#13 0x7f24c90f3150 in QTimer::timeout (this=this@entry=0x5d44040) at
.moc/moc_qtimer.cpp:198
#14 0x7f24c908f058 in QTimer::timerEvent (this=0x5d44040, e=) at kernel/qtimer.cpp:247
#15 0x7f24c908342b in QObject::event (this=0x5d44040, e=) at
kernel/qobject.cpp:1278
#16 0x7f24c9b8898c in QApplicationPrivate::notify_helper (this=, receiver=0x5d44040, e=0x7ffe71ab9f80) at kernel/qapplication.cpp:3804
#17 0x7f24c9b8d0b0 in QApplication::notify (this=0x1863600,
receiver=0x5d44040, e=0x7ffe71ab9f80) at kernel/qapplication.cpp:3561
#18 0x7f24c905aef0 in QCoreApplication::notifyInternal2
(receiver=0x5d44040, event=event@entry=0x7ffe71ab9f80) at
kernel/qcoreapplication.cpp:1015
#19 0x7f24c90a6c2e in QCoreApplication::sendEvent (event=0x7ffe71ab9f80,
receiver=) at

[krita] [Bug 373310] New: No matter which brush, i only see the result after right-click.

[bugzilla_noreply]

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

Bug ID: 373310
   Summary: No matter which brush, i only see the result after
right-click.
   Product: krita
   Version: 3.0.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: jwverste...@ziggo.nl
  Target Milestone: ---

I am a newbie at Krita.
So my first attempt on a white canvas was to just make some strokes on it.
My first stroke had no result (so I thought).
Therefore I choose another brush by right-clicking the mouse on the canvas.
And there is was instantly: my first stroke.
The strokes thereafter were also invisible until the right-click.
That's no way to make a drawing.

OS: Windows 10 Pro
Processor: Intel Core I7-2600K @ 3,4 GHz
RAM: 8 GB
Type system: 64-bits, x64-processor
No pen, no touch screen.

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

[Piotr Mierzwinski]

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

--- Comment #11 from Piotr Mierzwinski  ---
About Opera.
Seems that recently stable Opera (41.0.2353.69) is still linked with gtk2
(checked on latest Antergos with updates on this day).
$ ldd /usr/lib/opera/opera | grep gtk
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0
(0x7fbe18982000)
$ ldd /usr/lib/opera/opera | grep gdk
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0
(0x7f11d0a7b000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0
(0x7f11d0186000)

I'm not sure if there is any bug (reported in Opera bugs tracker) related with
lack of support xsmp.

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

[amarok] [Bug 373309] New: Cannot download album covers via amarok

[Dieter Jurzitza]

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

Bug ID: 373309
   Summary: Cannot download album covers via amarok
   Product: amarok
   Version: 2.8.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools/Cover Manager
  Assignee: amarok-bugs-d...@kde.org
  Reporter: dieter.jurzi...@t-online.de
CC: stuffcor...@archlinux.us
  Target Milestone: 2.9

I am using opensuse leap 42.1. Amarok 2.8.0 from packman (but this has no
impact at all). When I choose "Album" "download Cover" the apropriate window
opens, but no covers show at all, whatever source I choose (gootle, yahoo,
whatever).
Internet is working flawlessly, just for the records. I can manually download a
cover, can tell amarok where to find it and access it - but no way to use the
cover download from internet functionality. Any ideas?
I tried to build and use an older version of amarok - in vain, no change in
behaviour.
Thank you very much for you support,
take care



Dieter Jurzitza

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

[kdenlive] [Bug 368428] Choose language

[farid]

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

--- Comment #8 from farid  ---
LANG=C kdenlive is the solution. Is it complicated to have a combobox maybe in
the gui to choose the language?

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

[plasmashell] [Bug 373131] plasmashell freezes irretrievably every few minutes -- needs to be killed

[bugzilla_noreply]

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

kilian.cavalotti.w...@gmail.com changed:

   What|Removed |Added

 CC||kilian.cavalotti.work@gmail
   ||.com

--- Comment #13 from kilian.cavalotti.w...@gmail.com ---
I can confirm the exact same behavior here, on an Intel-based system.
Same workaround works (switching to VT and back) for a few minutes, before the
next freeze.

xserver-xorg 1:7.7+18
xserver-xorg-core 2:1.19.0-2
xserver-xorg-input-all 1:7.7+18
xserver-xorg-input-evdev 1:2.10.4-1+b1
xserver-xorg-input-libinput 0.22.0-1+b1
xserver-xorg-input-mouse 1:1.9.2-1+b1
xserver-xorg-input-synaptics 1.9.0-1+b1
xserver-xorg-input-wacom 0.33.0-1+b1
xserver-xorg-video-all 1:7.7+18
xserver-xorg-video-amdgpu 1.2.0-1+b1
xserver-xorg-video-ati 1:7.8.0-1+b1
xserver-xorg-video-cirrus 1:1.5.3-1+b2
xserver-xorg-video-fbdev 1:0.4.4-1+b5
xserver-xorg-video-intel 2:2.99.917+git20161105-1+b1
xserver-xorg-video-mach64 6.9.5-1+b2
xserver-xorg-video-mga 1:1.6.4-2+b1
xserver-xorg-video-neomagic 1:1.2.9-1+b2
xserver-xorg-video-nouveau 1:1.0.13-1+b1
xserver-xorg-video-qxl 0.1.4+20161126git4d7160c-1
xserver-xorg-video-r128 6.10.1-2+b1
xserver-xorg-video-radeon 1:7.8.0-1+b1
xserver-xorg-video-savage 1:2.3.8-2+b1
xserver-xorg-video-tdfx 1:1.4.6-2+b1
xserver-xorg-video-trident 1:1.3.7-2+b1
xserver-xorg-video-vesa 1:2.3.4-1+b2
xserver-xorg-video-vmware 1:13.2.1-1+b1


plasma-dataengines-addons 4:5.8.4-1
plasma-desktop 4:5.8.4-1
plasma-desktop-data 4:5.8.4-1
plasma-discover 5.8.3-1
plasma-discover-common 5.8.3-1
plasma-framework 5.28.0-1
plasma-integration 5.8.4-1
plasma-nm 4:5.8.4-1
plasma-pa 4:5.8.4-1
plasma-runners-addons 4:5.8.4-1
plasma-scriptengine-javascript 4:16.08.3-1
plasma-scriptengine-superkaramba 4:4.14.2-1
plasma-wallpapers-addons 4:5.8.4-1
plasma-widget-networkmanagement 0.9.3.6-1
plasma-workspace 4:5.8.4-1

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

[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()

[bugzilla_noreply]

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

--- Comment #3 from caulier.gil...@gmail.com ---
So, it's not a BC issue with Qt5.

I suspect now a database failure or a wrong application setting.

Now, please create a new account, import your collection, creating a new
database (in a different place than original collection). Try to reproduce the
crash in same condition.

Gilles Caulier

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

[umbrello] [Bug 373308] New: Connection between activity and pin does not end on pin

[Ralf Habacker]

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

Bug ID: 373308
   Summary: Connection between activity and pin does not end on
pin
   Product: umbrello
   Version: 2.20.80 (KDE Applications 16.11.80)
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de
  Target Milestone: ---

After connecting a pin with an activity the association is not drawn between
the pin and the activity. It ends in empty diagram space.

How to reproduce:
1. Add an activity diagram
2. Add two activities
3. Add a pin to the first activity 
4. Connect the pin with the second activity

The association does not connect the pin with the activity.

Same with ports and components.

The bug seems to be introduced with fixing of bug 371990 (commit
536e52fe6f71145cdcee16b5833f1c73b64e61fa)

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

[kipiplugins] [Bug 373304] google picasa photo import

[bugzilla_noreply]

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

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

   What|Removed |Added

Product|digikam |kipiplugins
  Component|Import  |GoogleServices
 CC||caulier.gil...@gmail.com
   Assignee|digikam-de...@kde.org   |kde-imag...@kde.org

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

[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||jlmatura...@gmail.com

--- Comment #28 from Martin Gräßlin  ---
*** Bug 373306 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 373306] Search/filter windows in present windows is not working anymore

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[kwin] [Bug 373268] Application dependent tearing with OpenGL

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin  ---
You have two screens. Due to the way how X works we can only vsync to one
screen. This could (!) explain the problem.

It might be worth a try to disconnect one and check whether it still tears.

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

[plasmashell] [Bug 373307] New: Plasama crashed after usign opengl app

[Sebastian]

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

Bug ID: 373307
   Summary: Plasama crashed after usign opengl app
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sebo.poc...@wp.pl
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.10-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was using steam with Trine2 - i just close game and plasma crashed

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

Thread 19 (Thread 0x7f1322ff6700 (LWP 3164)):
#0  0x7f1409c4610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f140ab3ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f140eafc395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f140eafcc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f140ab3dd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1409c40454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f140a4517df in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f13209c1700 (LWP 2229)):
#0  0x7f1409c4610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f140ab3ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f140eafc395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f140eafcc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f140ab3dd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1409c40454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f140a4517df in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f13211c2700 (LWP 1714)):
#0  0x7f1409c4610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f140ab3ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f140eafc395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f140eafcc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f140ab3dd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1409c40454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f140a4517df in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f13237f7700 (LWP 1658)):
#0  0x7f1409c4610f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f140ab3ec2b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f140eafc395 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f140eafcc8a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f140ab3dd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1409c40454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f140a4517df in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f1323ff8700 (LWP 1657)):
#0  0x7f13ff1871ea in pa_srbchannel_read () at
/usr/lib/pulseaudio/libpulsecommon-9.0.so
#1  0x7f13ff183788 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#2  0x7f13ff18648b in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#3  0x7f13ff186829 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#4  0x7f13ff1870aa in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#5  0x7f13ff806b9c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0
#6  0x7f13ff806f9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#7  0x7f13ff807040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#8  0x7f13ff815069 in  () at /usr/lib/libpulse.so.0
#9  0x7f13ff196ed8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#10 0x7f1409c40454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f140a4517df in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f1335feb700 (LWP 1656)):
#0  0x7f140a44848d in poll () at /usr/lib/libc.so.6
#1  0x7f1405723786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f140572389c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f140ad6c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f140ad1623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f140ab390f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f140dede2d5 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f140ab3dd78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f1409c40454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f140a4517df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f1336940700 (LWP 1453)):
#0  0x7f1409c4610f in pthread_cond_wait@@GLIBC_2.3.2 () at

[kwin] [Bug 373306] New: Search/filter windows in present windows is not working anymore

[jose luis m]

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

Bug ID: 373306
   Summary: Search/filter windows in present windows is not
working anymore
   Product: kwin
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jlmatura...@gmail.com
  Target Milestone: ---

When "present windows" effect is activated one could filter windows typing the
title of the window. Now, when I type, nothing happens. 
I was able to do it until a couple of weeks ago, so probably after the last
update it stopped working.

Im using:
KDE Frameworks 5.28.0
Qt 5.7.0

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

[konsole] [Bug 371687] Unicode characters appear cut off and mess up text height for rest of line

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before

[Ralf Habacker]

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

--- Comment #34 from Ralf Habacker  ---
I just tried to connect a pin on an activity diagram with another activity. The
result is that one end of the connection ends on the "another activity", the
other end does *not* ends on the pin. It ends somewhere in empty diagram space. 
My guess it that the connection end point calculation seems to be wrong now.

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

[kwin] [Bug 373268] Application dependent tearing with OpenGL

[Curtis Seizert]

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

--- Comment #2 from Curtis Seizert  ---
I have overclocked the graphics card, but the problem still occurs when it is
not overclocked.

Here is the output:
KWin Support Information:
The following information should be used when requesting support on e.g.
http://forum.kde.org.
It provides information about the currently running instance, which options are
used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a
paste bin service
like http://paste.kde.org instead of pasting into support threads.

==

Version
===
KWin version: 5.8.4
Qt Version: 5.7.0
Qt compile version: 5.7.0
XCB compile version: 1.12

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11804000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.oxygen
Theme: 
Blur: 0
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 16
font: Gadugi,12,-1,5,50,0,0,0,0,0
smallSpacing: 4
largeSpacing: 16

Options
===
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 20
windowSnapZone: 20
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 2
glSmoothScale: 2
colorCorrected: false
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: false
glStrictBindingFollowsDriver: true
glCoreProfile: true
glPreferBufferSwap: 0
glPlatformInterface: 1
windowsBlockCompositing: false

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Multi-Head: no
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
-
Name: DP-0
Geometry: 3840,0,3840x2160
Refresh Rate: 60

Screen 1:
-
Name: DP-2
Geometry: 0,0,3840x2160
Refresh Rate: 60


Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 375.20
OpenGL platform interface: GLX
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 375.20
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.18.4
Linux kernel version: 4.8.10
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---
zoom
slidingpopups
kwin4_effect_login
wobblywindows
slideback
screenshot
magiclamp
kwin4_effect_windowaperture
glide
kwin4_effect_translucency
flipswitch
desktopgrid
cubeslide
cube
coverswitch
kwin4_effect_morphingpopups
kwin4_effect_fade
kwin4_effect_zoomdesktop
kwin4_effect_cooleffect
slidingtooltips
presentwindows
kwin4_effect_dialogparent
highlightwindow
blur
contrast
startupfeedback
screenedge
kscreen

Currently Active Effects:
-
blur
contrast

Effect Settings:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true

[kdenlive] [Bug 358450] Stem shouldn't be available when export audio is turned off

[Jean-Baptiste Mardelle]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

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

--- Comment #3 from Jean-Baptiste Mardelle  ---
Thanks for your report and path.
Fixed now in this commit:

https://commits.kde.org/kdenlive/42701f3986ee99f4be470ddd4ab5d2fc8e731fc2

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

[kpdf] [Bug 102591] build error in KDE 3.4 branch

[Jean-Baptiste Mardelle]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 CC||j...@kdenlive.org

--- Comment #10 from Jean-Baptiste Mardelle  ---
Oops, sorry I messed up a copy/paste. My fix was indeed for bug #358450
(Kdenlive)

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

[krita] [Bug 373305] New: Apply operation on whole frame selection

[Bollebib]

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

Bug ID: 373305
   Summary: Apply operation on whole frame selection
   Product: krita
   Version: 3.0.2 Alpha
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: kwadraatn...@hotmail.com
  Target Milestone: ---

if i select a range of frames
or even with CTRL-select, various frames ,scattered,

it would be great to then just apply the next operations you do to that
selection

A few things I can imagine

1)delete/create frame
2)apply filter to selection (recolor,blur,color to alpha etc...)
3)transform


it's not a big issue if for bigger operations krita needs to calculate and
apply to each frame in succession,the main issue is to save time and not have
to do it step by step.


There are probably more operations that could be useful to mass-apply but these
for now would already be great

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

[digikam] [Bug 373304] New: google picasa photo import

[Ritesh Raj Sarraf]

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

Bug ID: 373304
   Summary: google picasa photo import
   Product: digikam
   Version: 5.3.0
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Import
  Assignee: digikam-de...@kde.org
  Reporter: kde-b...@researchut.com
  Target Milestone: ---

Hi,

I hope I've chosen the right bugzilla components.

In its current implementation, the "Import from Picasa/Google" feature only
gives a listing of the available albums. It does not give any idea about the
contents of the album.

My Feature Request is that, it would be nice to have a widget show the picasa
web albums and their contents, along with thumbnails.

You could have this as an optional secondary feature. THis will allow users to
decide what all pics they'd want to download. Otherwise, it is a "Catch All"
implementation currently. And with Videos (auto) backed up, this becomes a
sheer waste of network resources.

Take another example: Google Picasaweb has an Album called "Auto Backup", where
it backs up all pictures taken over your Google a/c. WHen importing with
Digikam, the entire "Auto Backup" contents will be imported. Where as, with the
requested Feature, users will have a choice to look and decide what all they
want to import.

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

[kdevelop] [Bug 373171] KDevelop allows to create a project in a directory that doesn't exist, then fails

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

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

--- Comment #5 from Sven Brauch  ---
Ok, nice. Thanks for reporting back. If you hit other issues, optimally please
open a report for each issue, that makes them easier to track. I'll close this
one.

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

[kwin] [Bug 373268] Application dependent tearing with OpenGL

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Flags||NVIDIA+

--- Comment #1 from Martin Gräßlin  ---
Please provide the output of
qdbus org.kde.KWin /KWin supportInformation

Did you change any settings of the NVIDIA driver?

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

[kdevelop] [Bug 372212] Auto-switch run configuration after editing it

[Alexander Potashev]

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

--- Comment #2 from Alexander Potashev  ---
I can do this eventually, but this might also be good for GCI.

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

[kdenlive] [Bug 371798] kdenlive generators don't work

[bugzilla_noreply]

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

--- Comment #3 from dimitrisbolar...@gmail.com ---
Any news or suggestion pls?

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

[gcompris] [Bug 373303] New: Missing 'L' alphabet from the virtual keyboard.

[Karmanya]

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

Bug ID: 373303
   Summary: Missing 'L' alphabet from the virtual keyboard.
   Product: gcompris
   Version: git master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: bruno.coud...@gcompris.net
  Reporter: karmanyashar...@gmail.com
  Target Milestone: ---

Version : Gcompris 0.70 based on Qt 5.6.1
OS  : Microsoft windows

Overview:
The alphabet 'L' is not there in the virtual keyboard.

Steps To Reproduce:
1. Go to the settings tab.
2. Check the option to show the virtual keyboard.

Actual Result:
'L' alphabet is not there after 'K'.

Expected Result:
The alphabet 'L' should have been there in the virtual keyboard between 'K' and
spacebar.

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

[gcompris] [Bug 373302] New: Automatic level completion

[Karmanya]

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

Bug ID: 373302
   Summary: Automatic level completion
   Product: gcompris
   Version: git master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: bruno.coud...@gcompris.net
  Reporter: karmanyashar...@gmail.com
  Target Milestone: ---

Version : Gcompris 0.70 based on Qt 5.6.1
OS  : Microsoft windows

Overview:
The level automatically completes in the activity - Simplified tower of hanoi.

Steps To Reproduce:
1. Open the activity, Simplified tower of hanoi.
2. Complete any level.
3. As soon as the the flower face shows up, rapidly click the left mouse
button.

Actual Result:
The successive level is automatically completed.

Expected Result:
The level after the previously completed level shouldn't have been
finished/completed.

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

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

[Petar Jovanovic]

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

Petar Jovanovic  changed:

   What|Removed |Added

 CC||mips3...@gmail.com

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

[kile] [Bug 373301] New: Problems in user menu

[Enrique Artal]

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

Bug ID: 373301
   Summary: Problems in user menu
   Product: kile
   Version: 2.9.60
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: user interface
  Assignee: michel.lud...@kdemail.net
  Reporter: ar...@unizar.es
  Target Milestone: ---

When editing the usermenu the marked parameters disappear.

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

[gcompris] [Bug 373300] New: Time delay in playing of sound.

[Karmanya]

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

Bug ID: 373300
   Summary: Time delay in playing of sound.
   Product: gcompris
   Version: git master
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: bruno.coud...@gcompris.net
  Reporter: karmanyashar...@gmail.com
  Target Milestone: ---

Version : Gcompris 0.70 based on Qt 5.6.1
OS  : Microsoft windows

Overview:
There is time delay in the playing of sound/music when the flower face shows up
in the activity click to draw.

Steps to reproduce:
1. Open the activity Click to draw.
2. Complete any level.
3. The flower face would show up.

Actual Result:
The face shows up but the sound is played later on.

Expected Result:
The sound should have played when the face showed up.

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

[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin

[Oliver Henshaw]

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

Oliver Henshaw  changed:

   What|Removed |Added

 CC||oliver.hens...@gmail.com

--- Comment #10 from Oliver Henshaw  ---
For future reference: firefox 50 now supports xsmp again - support needed to be
re-added after it moved to gtk3 - see
https://bugzilla.mozilla.org/show_bug.cgi?id=694570 (and presumably
equivalently new version of thunderbird will too); gtk2 applications need
libgnome and libgnomeui installed to register with xsmp; I don't know what the
status of opera or chrome is.

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

[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()

[Ritesh Raj Sarraf]

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

--- Comment #2 from Ritesh Raj Sarraf  ---
Hello Gilles,

Yes. I was able to crash the AppImage build too.


digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digikam.iojob: Trash folder for collection: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/"
digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digikam.iojob: Trash folder for collection: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/"
digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digikam.iojob: Trash folder for collection: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/"
digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digikam.iojob: Trash folder for collection: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/"
digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digikam.iojob: Trash folder for collection: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/"
digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digikam.iojob: Trash folder for collection: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/"
digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digikam.iojob: Trash folder for collection: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/.dtrash"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb/"
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb"
digikam.iojob: Thread Finished
digikam.general: One job is done
digikam.general: Detected change, triggering rescan of
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed//"
digikam.database: Starting scan!
digikam.database: Removed items: (16645, 16646, 16647, 16648, 16649, 16650,
16651, 16652, 16653, 16654, 16655, 16656, 16657, 16658, 16659, 16660, 16661,
16662, 16663, 16664, 16665, 1, 16667, 16668, 16669, 16670, 16671, 16672,
16673, 16674, 16675, 16676, 16677, 16678, 16679, 16680, 16681, 16682, 16683,
16684, 16685, 16686, 16687, 16688, 16689, 16690) related items: ()
digikam.database: Folder does not exist or is not readable: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb"
digikam.database: Folder does not exist or is not readable: 
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed/deb"
digikam.geoiface: 
digikam.geoiface: 
digikam.general: Using  4  CPU core to run threads
digikam.general: Action Thread run  1  new jobs
/tmp/.mount_ZMCjVu/AppRun: line 37: 20599 Segmentation fault  (core dumped)
digikam.wrapper $@
2016-12-05 / 22:27:05 ♒♒♒  ☹  => 139

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

[krita] [Bug 373299] Zoom shortcuts dont work after focus given to docker windows

[bugzilla_noreply]

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

p...@blueyonder.co.uk changed:

   What|Removed |Added

 CC||p...@blueyonder.co.uk

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

[krita] [Bug 373299] New: Zoom shortcuts dont work after focus given to docker windows

[bugzilla_noreply]

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

Bug ID: 373299
   Summary: Zoom shortcuts dont work after focus given to docker
windows
   Product: krita
   Version: 3.1 Beta
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: shortcuts
  Assignee: krita-bugs-n...@kde.org
  Reporter: p...@blueyonder.co.uk
  Target Milestone: ---

My Zoom shortcut keys stop functioning after I interact with either the
"Overview" or "Image Reference" dockers.

Reproduce senario:

1) Zoom in/out main canvas with shortcut keys
2) select either of te above dockers adn interact with the slide size controls
of the docker window
3) go back to main canvas and try to use zoom shortcut keys.

What I experienced was this also happened with the brush preset docker, when
any of the 3 mentioned dockers get the focus the do not seem to release the
event after the main canvas is clicked so using zoom in the main canvas will
still scale the "Reference Image " docker.

If this does not make sense please comment and I will try to attach a small
video clip showing the problem

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

[kmail2] [Bug 373040] Stop line wrapping long links

[bugzilla_noreply]

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

--- Comment #4 from w...@obsidian-studios.com ---
Created attachment 102633
  --> https://bugs.kde.org/attachment.cgi?id=102633=edit
Screenshot of long link being wrapped and broken

You can see in this attachment the problem. I composed an email to myself with
a long link. It broke the link. A person has to copy and paste the entire
thing. Rather than clicking on the link.

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