[kst] [Bug 362802] binary dir file will not update live plot

[jhg via KDE Bugzilla]

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

jhg  changed:

   What|Removed |Added

 CC||jhgo...@gmail.com

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

[kst] [Bug 362802] New: binary dir file will not update live plot

[jhg via KDE Bugzilla]

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

Bug ID: 362802
   Summary: binary dir file will not update live plot
   Product: kst
   Version: 2.0.8
  Platform: Homebrew (Mac OS X)
   URL: https://github.com/Kst-plot/kst/issues/6
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plotting
  Assignee: k...@kde.org
  Reporter: jhgo...@gmail.com

Environment and steps to reproduce:

* Mac OS X 10.11.4
* kst version 2.0.6 and master (2.0.x ~9ish)
* follow steps in video EXCEPT using binary dir file mode instead of ASCII
Aberrent behavior:
* Plots do not update.

Other things tried:

there is no way to change the update rate
update on file change also does not work

Reproducible: Always

Steps to Reproduce:
1. try to plot a binary dir file datasource

Actual Results:  
1. plots don't update when data source is written to

Expected Results:  
1. plot should update, just like it does for ASCII files

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

[kdenlive] [Bug 362801] New: Waveform thumbnails aren't generating for certain files, regardless of file type

[Benjamin via KDE Bugzilla]

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

Bug ID: 362801
   Summary: Waveform thumbnails aren't generating for certain
files, regardless of file type
   Product: kdenlive
   Version: 16.04.0
  Platform: Debian unstable
   URL: https://drive.google.com/file/d/0B74NKcdHp59cOTVlelFxN
VVJMlU/view?usp=sharing
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: benjaminne...@yandex.com

This affects me on both self-compiled and repository binary:
- MOV (Canon DSLR) and WAV (ZOOM Audio Recorder) files throw errors and do not
generate audio thumbnails. The issue persists even after the WAV file is
converted to MP3 (Using Audacity) and the MOV is converted to an MPEG4 M4V
(Using Handbrake).

- MP4 and MP3 formats DO generate waveform thumbnails as expected, provided
that they're not conversions of the previously mentioned files. However, when a
working MP3 file is converted to WAV, it can no longer generate thumbnails.

Reproducible: Always

Steps to Reproduce:
1. Import a MOV from a Canon DSLR or WAV from a ZOOM Audio Recorder

Actual Results:  
Program continued working without waveform thumbnails for the project.

Expected Results:  
Generated waveform thumbnails.

mlt_repository_init: failed to dlopen
/home/benjamin/Dev/kdenlive/lib/mlt/libmltopengl.so
  (libmovit.so.2: cannot open shared object file: No such file or directory)
Removing cache at "/home/benjamin/.cache/kdenlive-thumbs.kcache"
OpenGL vendor:  "NVIDIA Corporation"
OpenGL renderer:  "GeForce GTX 660 Ti/PCIe/SSE2"
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
OpenGL vendor:  "NVIDIA Corporation"
OpenGL renderer:  "GeForce GTX 660 Ti/PCIe/SSE2"
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
[swscaler @ 0x7fffad3509c0] Warning: data is not aligned! This can lead to a
speedloss
"Creating audio thumbnails (1/1)"
"Error reading audio thumbnail"
"Creating audio thumbnails (1/1)"
"Error reading audio thumbnail"
"Error reading audio thumbnail"
"Error reading audio thumbnail"
 / / / / /WARNING, VIDEO CONTEXT IS NULL!!
"Creating audio thumbnails (1/1)"
"Error reading audio thumbnail"
/// READY TO CUT AT:  1071  /  1071 , duration:  476
// chking moved clip at:  1071
// chking moved clip at:  1071
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setOpacity: Painter not active
QPainter::setOpacity: Painter not active
QPainter::end: Painter not active, aborted
Adjusting effect to duraion
Adjusting effect to duraion
Adjusting effect to duraion
Adjusting effect to duraion
Adjusting effect to duraion
/// READY TO CUT AT:  305  /  305 , duration:  237
// chking moved clip at:  305
// chking moved clip at:  305
Adjusting effect to duraion
Adjusting effect to duraion
1462680744293addons.productaddonsERRORRequest failed certificate
checks: [Exception... "SSL is required and URI scheme is not https."  nsresult:
"0x8000 (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
resource://gre/modules/CertUtils.jsm :: checkCert :: line 145"  data: no]

(process:9391): GLib-CRITICAL **: g_path_get_basename: assertion 'file_name !=
NULL' failed
"Creating audio thumbnails (1/1)"
/// READY TO CUT AT:  606  /  606 , duration:  211
// chking moved clip at:  606
// chking moved clip at:  606
[mp3 @ 0x30b6760] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x3526040] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x3c6e9e0] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x34d86a0] Estimating duration from bitrate, this may be inaccurate
 / / / / /WARNING, VIDEO CONTEXT IS NULL!!
"Creating audio thumbnails (1/1)"
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setOpacity: Painter not active
QPainter::setOpacity: Painter not active
QPainter::end: Painter not active, aborted
[mp3 @ 0x7ffdf3ed9960] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x7fff8813db20] Estimating duration from bitrate, this may be inaccurate
 / / / / /WARNING, VIDEO CONTEXT IS NULL!!
"Creating audio thumbnails (1/1)"
"Error reading audio thumbnail"
1462681524145addons.productaddonsERRORRequest failed certificate
checks: [Exception... "SSL is required and URI scheme is not https."  nsresult:
"0x8000 (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
resource://gre/modules/CertUtils.jsm :: checkCert :: line 145"  data: no]
1462681525461addons.update-checkerWARNUpdate manifest for
{972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
 / / / / /WARNING, VIDEO CONTEXT IS NULL!!
"Creating audio thumbnails (1/1)"
"Error reading audio thumbnail"
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setOpacity: Painter not active

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[Ry via KDE Bugzilla]

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

Ry  changed:

   What|Removed |Added

 CC||ryg...@bellsouth.net

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

[Touchpad-KCM] [Bug 362800] New: Touchpad setting "Disable taps and scrolling only" ignored

[Mark via KDE Bugzilla]

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

Bug ID: 362800
   Summary: Touchpad setting "Disable taps and scrolling only"
ignored
   Product: Touchpad-KCM
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: rajeeshknamb...@gmail.com
  Reporter: mark.fit...@hotmail.com

I have an HP Envy 17 which includes a no-button touchpad.  Using KDE System
Settings I can enable the touchpad setting "Disable touchpad when typing"
however the sub-setting "Disable taps and scrolling only" is not honored. 
Further, disabling the main setting "Disable touchpad when typing" is not
honored either, whether or not I log out and back in or reboot the system.

Reproducible: Always

Steps to Reproduce:
1. Open System Settings -> Input Devices -> Touchpad -> Enable/Disable Touchpad
2. Ensure "Disable touchpad when typing" and "Disable taps and scrolling only"
are enabled
3. Open Kate (text editor) and continually hold a key, such as 'w' while trying
to move the mouse cursor with the touchpad.

Actual Results:  
The mouse cursor does not move.  Releasing the 'w' key will allow mouse cursor
movement again using the touchpad.

Expected Results:  
The mouse cursor responds to movement requests even during keyboard key
presses.

I have both the xorg-x11-drv-synaptics and xorg-x11-drv-libinput installed on
my Fedora 23 x64 install.  I've already tried renaming the files
/usr/share/X11/xorg.conf.d/50-synaptics.conf and
/usr/share/X11/xorg.conf.d/90-libinput.conf as suggested in another bug report:
https://bugs.kde.org/show_bug.cgi?id=360943, but it didn't work.

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

[parley] [Bug 362799] New: can't write export file

[Juergen via KDE Bugzilla]

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

Bug ID: 362799
   Summary: can't write export file
   Product: parley
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: parley-bugs-n...@kde.org
  Reporter: b4tas...@auroville.org.in

Version 2.1.0 4:15.12.3-0ubuntu1 Using: KDE Frameworks 5.18.0 Qt 5.5.1 (built
against 5.5.1) The xcb windowing system, ubuntu 16.04 64 bit

When trying to export practise results Parley gives an error message:

Could not write to /home/user/practice_export


Parley can't write export file

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

[okular] [Bug 306886] Merge selection and browse tool functionality

[Jonathan via KDE Bugzilla]

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

Jonathan  changed:

   What|Removed |Added

 CC||jonat...@imatix.com

--- Comment #8 from Jonathan  ---
Hear hear!

This issue is another example of a broader problem in the Okular UI in the
over-use of modes, and inconsistency in the operation in different modes. This
is particularly annoying when you need to switch often between modes. I raised
earlier this year some problems of inconsistency in the Okular UI
https://mail.kde.org/pipermail/okular-devel/2016-February/022421.html I have
also submitted a trivial review request that without breaking any currently
working function eliminates one annoying inconsistency between selection modes:
https://git.reviewboard.kde.org/r/127496/ I've had zero response to the review
request.

How do people feel about starting a broader discussion about these issues in
the Okular UI? Even a working group perhaps? I'd certainly be keen to get the
ball rolling.

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

[Breeze] [Bug 362631] KAlarm icon is indistinct and unrecognisable at smaller sizes

[David Jarvie via KDE Bugzilla]

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

--- Comment #6 from David Jarvie  ---
I tried out the 24x24 chronometer icons. The 'chronometer' icon doesn't look
obviously connected to KAlarm at all, and it's also completely different from
the other chronometer icons. The basic idea might work in the system tray, with
the normal kalarm icon being the same as chronometer-start but with the arrow
in the middle removed (i.e. an empty circle). Since the normal status of KAlarm
is to have alarms enabled, I don't think it's appropriate to show the arrow in
the 'kalarm' icon.

I don't see a suitable icon for kalarm-disabled or kalarm-partdisabled. For me,
the chronometer-pause icon doesn't convey a disabled meaning if the normal
'kalarm' icon doesn't have the arrow in the middle. Perhaps some other
variations on the same basic idea might work for these two icons, though.

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

[krunner] [Bug 362581] Run-command window (alt-f2): re-enable 'floating' option

[via KDE Bugzilla]

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

--- Comment #2 from slartibar...@gmail.com ---
Thanks for the info!
I tried - and it works well. I haven't found any problems yet. 
Can you share some of the reasons why this feature is disabled by default?

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

[krita] [Bug 344263] Scale/Transform from centre/pivot

[eliotJ via KDE Bugzilla]

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

eliotJ  changed:

   What|Removed |Added

 CC||os...@jadamspam.pl

--- Comment #4 from eliotJ  ---
+1 I also often miss these functionality...

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

[krita] [Bug 361911] Overriding hotkeys won't work (conflict of new hotkey with old one)

[eliotJ via KDE Bugzilla]

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

eliotJ  changed:

   What|Removed |Added

 CC||os...@jadamspam.pl

--- Comment #5 from eliotJ  ---
#ocumo
There was fixed other bugs with shortcuts. You should notice that this bug
still has status "confirmed", not "fixed".

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

[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra

[wolthera via KDE Bugzilla]

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

--- Comment #4 from wolthera  ---
Try to see whether you can open them in the latest 3.0 beta that you can
download from the news posts on krita.org. We fixed quite a few bugs there.

Otherwise, you can always try to rename the file from a .kra to a .zip, en then
get out 'mergedimage.png', you'll lose your layers, but not your drawing. (Do
tell us if it doesn't work with the 3.0 beta either though, that's a pretty
serious problem)

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

[frameworks-baloo] [Bug 362153] KDE v5.21 Lags as long as baloo_file and baloo_file_extractor runs in background

[via KDE Bugzilla]

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

bjoe...@arcor.de changed:

   What|Removed |Added

 CC||bjoe...@arcor.de

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

[frameworks-baloo] [Bug 358548] baloo_file_extractor high CPU and memory usage

[via KDE Bugzilla]

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

bjoe...@arcor.de changed:

   What|Removed |Added

 CC||bjoe...@arcor.de

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

[plasmashell] [Bug 362798] New: Plasma crashes from time to time with no obvious reason

[Herr Schmidt via KDE Bugzilla]

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

Bug ID: 362798
   Summary: Plasma crashes from time to time with no obvious
reason
   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: wettererschein...@bb-goettingen.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
This happens from time to time - but every day. I couldn't find a relation to
my actions.

- Unusual behavior I noticed:
I have several problems regarding graphics, probably kwin or ksystemsettings.
See my bugreports #362720 #362726 and #362728.

I've got quite new Hardware (Thinkpad T560) don't know wether it could be
related to that. I hope you can find something in the technical details. The
program said it's useful...

Thanks for your work - by the way!

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 0x7f20a20348c0 (LWP 2640))]

Thread 8 (Thread 0x7f208d1f3700 (LWP 2643)):
#0  0x7f209c73ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f20a07ffc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f20a08018d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f208f341629 in QXcbEventReader::run (this=0x2440860) at
qxcbconnection.cpp:1253
#4  0x7f209ce3084e in QThreadPrivate::start (arg=0x2440860) at
thread/qthread_unix.cpp:331
#5  0x7f209bf1d6fa in start_thread (arg=0x7f208d1f3700) at
pthread_create.c:333
#6  0x7f209c746b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f20868fe700 (LWP 2645)):
#0  0x7f2099514a64 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f20994d0311 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f20994d042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f209d067a9b in QEventDispatcherGlib::processEvents
(this=0x7f2088c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f209d00edea in QEventLoop::exec (this=this@entry=0x7f20868fdce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f209ce2b8a4 in QThread::exec (this=this@entry=0x251d980) at
thread/qthread.cpp:503
#6  0x7f209f6d33c5 in QQmlThreadPrivate::run (this=0x251d980) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f209ce3084e in QThreadPrivate::start (arg=0x251d980) at
thread/qthread_unix.cpp:331
#8  0x7f209bf1d6fa in start_thread (arg=0x7f20868fe700) at
pthread_create.c:333
#9  0x7f209c746b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f207b34d700 (LWP 2646)):
#0  0x7f209c73ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f20994d031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f20994d042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f209d067a9b in QEventDispatcherGlib::processEvents
(this=0x7f20740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f209d00edea in QEventLoop::exec (this=this@entry=0x7f207b34cce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f209ce2b8a4 in QThread::exec (this=this@entry=0x2891420) at
thread/qthread.cpp:503
#6  0x7f209f6d33c5 in QQmlThreadPrivate::run (this=0x2891420) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f209ce3084e in QThreadPrivate::start (arg=0x2891420) at
thread/qthread_unix.cpp:331
#8  0x7f209bf1d6fa in start_thread (arg=0x7f207b34d700) at
pthread_create.c:333
#9  0x7f209c746b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f2079479700 (LWP 2647)):
#0  update_get_addr (ti=0x7f209d25b788) at dl-tls.c:807
#1  0x7f209ce2f792 in get_thread_data () at thread/qthread_unix.cpp:181
#2  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at
thread/qthread_unix.cpp:212
#3  0x7f209d0672e1 in postEventSourcePrepare (timeout=0x0,
s=0x7f206c0012d0) at kernel/qeventdispatcher_glib.cpp:247
#4  postEventSourceCheck (source=0x7f206c0012d0) at
kernel/qeventdispatcher_glib.cpp:264
#5  0x7f20994cfd51 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f20994d02c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f20994d042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f209d067a9b in QEventDispatcherGlib::processEvents
(this=0x7f206c0008c0, 

[kontact] [Bug 362795] Attempt to add google calendar fails

[MikeC via KDE Bugzilla]

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

--- Comment #2 from MikeC  ---
After refreshing the calendar manually using the options available when right
clicking the specific calendar listed does bring in the list of events into the
calendar now.  I will continue to test to see if it updates at the interval I
have entered in the settings - and if so I will then close this bug.

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

[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra

[via KDE Bugzilla]

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

--- Comment #3 from gedgep...@gmail.com ---
https://gyazo.com/124762534383ef8d59d565d58a4c7918

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

[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra

[via KDE Bugzilla]

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

--- Comment #2 from gedgep...@gmail.com ---
(In reply to wolthera from comment #1)
> which version are you using?

2.9.11

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

[kontact] [Bug 362795] Attempt to add google calendar fails

[MikeC via KDE Bugzilla]

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

--- Comment #1 from MikeC  ---
I have seen the warning at the top of the page I referenced saying "These
instructions are no longer needed because a Google Calendar resource is shipped
with KDE. You do not need to use DAV any more. In KOrganizer simply go to
Settings->General->Calendars and filter for google" - and this seems initially
to work - and the calendar does appear to log in successfully. However after
that although the calendars are listed with checked boxes in the lower left
window - no calendar events appear in the calendar ( even though the events are
listed normally in my android calendars as well as in the Thunderbird with
calendar using the lightning extension). So neither method seems to work for
me.

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

[krita] [Bug 362797] Could not open C:/Users/Paul/Pictures/Mun.kra Reason: Not a valid Krita file: C:/Users/Paul/Pictures/Mun.kra

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
which version are you using?

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

[gwenview] [Bug 362796] New: Gwenview crashed

[via KDE Bugzilla]

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

Bug ID: 362796
   Summary: Gwenview crashed
   Product: gwenview
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: pedron.alexan...@gmail.com
CC: myr...@kde.org

Application: gwenview (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was looking for a picture in BMP when the application crashed.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f56b69959c0 (LWP 7871))]

Thread 2 (Thread 0x7f56b48ae700 (LWP 7872)):
#0  0x7f56c52eee8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f56be1e3c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f56be1e58d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f56b65d9629 in QXcbEventReader::run (this=0x1c4ab10) at
qxcbconnection.cpp:1253
#4  0x7f56c59e484e in QThreadPrivate::start (arg=0x1c4ab10) at
thread/qthread_unix.cpp:331
#5  0x7f56c07f66fa in start_thread (arg=0x7f56b48ae700) at
pthread_create.c:333
#6  0x7f56c52fab5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f56b69959c0 (LWP 7871)):
[KCrash Handler]
#6  0x7f56c46a3d60 in ?? () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2
#7  0x7f56c46aabab in ?? () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2
#8  0x7f56c99e8c99 in Gwenview::RasterImageView::updateFromScaler
(this=0x22f2e20, zoomedImageLeft=-390, zoomedImageTop=-61, image=...) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/documentview/rasterimageview.cpp:322
#9  0x7f56c5bf3e4f in QtPrivate::QSlotObjectBase::call (a=0x7fff8ea4e060,
r=0x22f2e20, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#10 QMetaObject::activate (sender=sender@entry=0x26807c0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff8ea4e060) at kernel/qobject.cpp:3698
#11 0x7f56c5bf47d7 in QMetaObject::activate (sender=sender@entry=0x26807c0,
m=m@entry=0x7f56c9c90800 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff8ea4e060)
at kernel/qobject.cpp:3578
#12 0x7f56c9a4c581 in Gwenview::ImageScaler::scaledRect
(this=this@entry=0x26807c0, _t1=-390, _t2=-61, _t3=...) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/obj-x86_64-linux-gnu/lib/moc_imagescaler.cpp:135
#13 0x7f56c9a09947 in Gwenview::ImageScaler::scaleRect
(this=this@entry=0x26807c0, rect=...) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/imagescaler.cpp:132
#14 0x7f56c9a0a0e7 in Gwenview::ImageScaler::doScale (this=0x26807c0) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/imagescaler.cpp:122
#15 0x7f56c9a0a1a5 in Gwenview::ImageScaler::setDestinationRegion
(this=, region=...) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/imagescaler.cpp:102
#16 0x7f56c99e7474 in
Gwenview::RasterImageViewPrivate::setScalerRegionToVisibleRect (this=0x262c140)
at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/documentview/rasterimageview.cpp:151
#17 Gwenview::RasterImageView::updateBuffer (this=this@entry=0x22f2e20,
region=...) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/lib/documentview/rasterimageview.cpp:443
#18 0x7f56c9a4efbb in Gwenview::RasterImageView::qt_static_metacall
(_o=_o@entry=0x22f2e20, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=7, _a=_a@entry=0x7fff8ea4e3b0) at
/build/gwenview-iJ9mAT/gwenview-15.12.3/obj-x86_64-linux-gnu/lib/moc_rasterimageview.cpp:109
#19 0x7f56c5bf3fca in QMetaObject::activate (sender=sender@entry=0x2651cb0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3713
#20 0x7f56c5bf47d7 in QMetaObject::activate (sender=sender@entry=0x2651cb0,
m=m@entry=0x7f56c5e0e840 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3578
#21 0x7f56c5c736d0 in QTimer::timeout (this=this@entry=0x2651cb0) at
.moc/moc_qtimer.cpp:197
#22 0x7f56c5c00878 in QTimer::timerEvent (this=0x2651cb0, e=) at kernel/qtimer.cpp:247
#23 0x7f56c5bf4e53 in QObject::event (this=0x2651cb0, e=) at
kernel/qobject.cpp:1261
#24 0x7f56c6e8805c in QApplicationPrivate::notify_helper
(this=this@entry=0x1c34c20, receiver=receiver@entry=0x2651cb0,
e=e@entry=0x7fff8ea4e6e0) at kernel/qapplication.cpp:3716
#25 0x7f56c6e8d516 in QApplication::notify (this=0x7fff8ea4ea30,
receiver=0x2651cb0, e=0x7fff8ea4e6e0) at kernel/qapplication.cpp:3499
#26 0x7f56c5bc562b in QCoreApplication::notifyInternal

[kontact] [Bug 362795] New: Attempt to add google calendar fails

[MikeC via KDE Bugzilla]

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

Bug ID: 362795
   Summary: Attempt to add google calendar fails
   Product: kontact
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: calendar
  Assignee: korganizer-de...@kde.org
  Reporter: mike.cloa...@gmail.com

I have been trying to get Kontact to work with my google calendars - so I
followed the procedure at https://userbase.kde.org/Working_with_Google_Calendar
and when I reached the last stage for fetching my calendar I had a response
within Kontact saying there had been a problem when I clicked "Fetch" at the
last step.  Within a few seconds I received an email from gmail saying
"Someone just tried to sign in to your Google Account xxx....@gmail.com
from an app that doesn't meet modern security standards.
Details:
Saturday, May 7, 2016 8:44 PM (British Summer Time)
United Kingdom*
We strongly recommend that you use a secure app, like Gmail, to access your
account. All apps made by Google meet these security standards. Using a less
secure app, on the other hand, could leave your account vulnerable. Learn more.
Google stopped this sign-in attempt, but you should review your recently used
devices:"

Reproducible: Always

Steps to Reproduce:
1. In Kontact go to Settings -> Configure Calendar
2. Select the Calendars tab on the General area to prepare to add the Google
calendar. Next, Select the DAV groupware resource (you may need to add this
resource first by clicking Add... and selecting it in the list). After this
click Cancel when a prompt appears asking to enter your credentials to login to
the groupware server.
3. Another window will appear, and here you can enter the location of your
Google Calendar resource. In the Server Configuration area, click on Add. Now,
this opens the last window. Here, ensure that CalDAV is selected as the Remote
calendar access protocol.

The remote URL takes the form:
https://www.google.com/calendar/dav/GoogleCalendarID/events/

4. After pressing the Fetch button Kontact fails to sync with Google and an
error message appears saying there was a problem

Actual Results:  
Fails to connect and gmail sends an email saying "Someone just tried to sign in
to your Google Account xxx....@gmail.com from an app that doesn't meet
modern security standards"

Expected Results:  
Should connect and set up calendar access in Kontact

This is possibly because Google supports OAuth 2.0 as the recommended
authentication mechanism for all of its APIs but perhaps Kontact does not use
this mechanism?

The version I am using is kontact 16.04.0-3

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

[kdeconnect] [Bug 362794] Gmail notifications expand beyond screen

[Umberto Tozzato via KDE Bugzilla]

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

Umberto Tozzato  changed:

   What|Removed |Added

 CC||umbertotozz...@gmail.com

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

[kdeconnect] [Bug 362794] New: Gmail notifications expand beyond screen

[Umberto Tozzato via KDE Bugzilla]

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

Bug ID: 362794
   Summary: Gmail notifications expand beyond screen
   Product: kdeconnect
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: umbertotozz...@gmail.com

Sometimes gmail notifications expand above the top of the screen. This is
particularly annoying since the close button is unreachable, thus you have to
wait for it to disappear on his own.

It doesn't happen all the times, thought i still have to understand the
pattern.

Reproducible: Sometimes

Steps to Reproduce:
1. Enable KDEconnect notifications pop-up.
2. Receive a gmail notification


Expected Results:  
Notifications gets a limited pop-up size

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

[krita] [Bug 362793] New: 3.0 Beta (git 962bfe1) Krita buggy tools performance, crashes on save and OpenGL Error on Restart

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 362793
   Summary: 3.0 Beta (git 962bfe1) Krita buggy tools performance,
crashes on save and OpenGL Error on Restart
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

The Version: 3.0 Beta (git 962bfe1) build has been giving me a rough time
performance wise today (filed another bug report about it today). 

I've been using it for the past five hours and during the last two it has
basically become unusable.

Changing the visibility of 3 Adjustment  Layers takes about a minute. Changing
the order of layers is also very slow and sometimes crashes Krita. I have found
a partial workaround to this by hiding the visibility of layers before changing
their order.

The Polygon and Brush tools get stuck often.The brush tool "chooses" to paint
on its own after I end a stroke and the polygon tool jumps around or does not
register a click making it almost unusable. 

Then Krita becomes unresponsive on file save. On program restart it threw me
this error:
Krita could not initialize the OpenGL canvas:
Checker vertex shader
Vertex shader failed to compile with the following errors:
 Krita will disable OpenGL and close now.

I think that I'm done testing this build and going back to the previous one. 

I'm on an old Toshiba Satellite laptop running Windows 7 32bit and using a
Wacom Intuos. I am aware that it's not the fastest system around but I never
had these kind of problems  with the previous builds of Krita 3.0 and I've
spent quite a bit of time testing them. 

Reproducible: Sometimes

Steps to Reproduce:
1
2.
3.

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

[krunner] [Bug 362792] New: krunner started applications but crashed and left 2 processes

[Arthur Marsh via KDE Bugzilla]

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

Bug ID: 362792
   Summary: krunner started applications but crashed and left 2
processes
   Product: krunner
   Version: 5.5.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: arthur.ma...@internode.on.net

Application: krunner (5.5.4)

Qt Version: 5.5.1
Operating System: Linux 4.6.0-rc6+ x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
when starting iceweasel from krunner, iceweasel started but krunner crashed
leaving 2 krunner processes that did not respond to alt-F2. Manually killing
the 2 krunner processes and restarting krunner did work though.

The crash can be reproduced sometimes.

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

Thread 12 (Thread 0x7fb900c61700 (LWP 3972)):
#0  0x0030004dfe5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00300340a382 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fb900c60d00) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  0x00300340a382 in _xcb_conn_wait (c=c@entry=0x1e13470,
cond=cond@entry=0x1e134b0, vector=vector@entry=0x0, count=count@entry=0x0) at
../../src/xcb_conn.c:459
#3  0x00300340bff7 in xcb_wait_for_event (c=0x1e13470) at
../../src/xcb_in.c:693
#4  0x7fb9010c0789 in QXcbEventReader::run() (this=0x1e264c0) at
qxcbconnection.cpp:1230
#5  0x0030174a57fe in QThreadPrivate::start(void*) (arg=0x1e264c0) at
thread/qthread_unix.cpp:331
#6  0x003000c07454 in start_thread (arg=0x7fb900c61700) at
pthread_create.c:334
#7  0x0030004e8eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fb8f7572700 (LWP 3975)):
#0  0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb8fac5e3f3 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7fb8fac5db17 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x003000c07454 in start_thread (arg=0x7fb8f7572700) at
pthread_create.c:334
#4  0x0030004e8eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7fb8f5bfc700 (LWP 3979)):
#0  0x0030004dfe5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00300284a32c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7fb8f0003070, timeout=, context=0x7fb8f990) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:4135
#2  0x00300284a32c in g_main_context_iterate
(context=context@entry=0x7fb8f990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3835
#3  0x00300284a43c in g_main_context_iteration (context=0x7fb8f990,
may_block=may_block@entry=1) at
/build/glib2.0-2CrUwg/glib2.0-2.48.0/./glib/gmain.c:3901
#4  0x0030176dca5b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fb8f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x003017683d6a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fb8f5bfbde0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x0030174a0854 in QThread::exec() (this=) at
thread/qthread.cpp:503
#7  0x0030480d5105 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x0030174a57fe in QThreadPrivate::start(void*) (arg=0x21b37a0) at
thread/qthread_unix.cpp:331
#9  0x003000c07454 in start_thread (arg=0x7fb8f5bfc700) at
pthread_create.c:334
#10 0x0030004e8eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7fb8eb996700 (LWP 4172)):
#0  0x003000c0d04f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0030174a6a9b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x205a940) at
thread/qwaitcondition_unix.cpp:136
#2  0x0030174a6a9b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x2117700, time=time@entry=18446744073709551615)
at thread/qwaitcondition_unix.cpp:208
#3  0x7fb8ef9b202b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
(this=this@entry=0x2118b90, th=) at ../../src/weaver.cpp:594
#4  0x7fb8ef9b2ddf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) (this=0x2118b90, th=th@entry=0x2a61460,
threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554
#5  0x7fb8ef9b7038 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool)

[marble] [Bug 362791] recorded video file corrupted

[RJ via KDE Bugzilla]

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

--- Comment #1 from RJ  ---
Created attachment 98837
  --> https://bugs.kde.org/attachment.cgi?id=98837=edit
it looks like this

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

[marble] [Bug 362791] recorded video file corrupted

[RJ via KDE Bugzilla]

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

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

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

[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

[Luca Mastromatteo via KDE Bugzilla]

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

--- Comment #2 from Luca Mastromatteo  ---
Nothing interesting from the dmesg. 
And yes, it seems to be the blur effect, no artifacts after disabling it. 
I didn't know where to put this since I didn't had problems with this driver
since I've encountered in this.

Output of the command https://paste.kde.org/pg6yqrbf9

Running kwin from the terminal, with and without the option enabled in kwinrc
didn't changed anything.

QXcbConnection: XCB error: 3 (BadWindow), sequence: 176, resource id: 10485766,
major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 8 (BadMatch), sequence: 1531, resource id: 88080425,
major code: 42 (SetInputFocus), minor code: 0
OpenGL vendor string:   X.Org
OpenGL renderer string: Gallium 0.4 on AMD TONGA (DRM 3.1.0,
LLVM 3.7.1)
OpenGL version string:  4.1 (Core Profile) Mesa 11.2.1
OpenGL shading language version string: 4.10
Driver: Unknown
GPU class:  Unknown
OpenGL version: 4.1
GLSL version:   4.10
Mesa version:   11.2.1
X server version:   1.18.3
Linux kernel version:   4.5.2
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1753, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1754, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1755, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1756, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1757, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1758, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1759, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1760, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1763, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1764, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1765, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1766, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1767, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1768, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1769, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1770, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QMetaProperty::read: Unable to handle unregistered datatype
'KWayland::Server::SurfaceInterface*' for property 'KWin::Toplevel::surface'

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

[marble] [Bug 362791] New: recorded video file corrupted

[RJ via KDE Bugzilla]

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

Bug ID: 362791
   Summary: recorded video file corrupted
   Product: marble
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: ogldel...@mail.ru

after recording video file in ogg or avi format video was corrupted

Reproducible: Always

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

[konsole] [Bug 362790] New: Konsole sometimes received escape codes during focus changes

[via KDE Bugzilla]

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

Bug ID: 362790
   Summary: Konsole sometimes received escape codes during focus
changes
   Product: konsole
   Version: 15.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: emulation
  Assignee: konsole-de...@kde.org
  Reporter: bjoe...@arcor.de

Since some month my Konsole behaves strange.

If a foreground job (e.g. sleep) which does not listen on keyboard events is
running in Konsole, I see the escape codes "^[[O" if Konsole looses the focus
and "^]]I" if Konsole get's the focus.

Foreground jobs like editors receive the keyboard events too and may insert
them into editor text.

Reproducible: Sometimes

Steps to Reproduce:
1. open Konsole
2. Type "sleep 1000"
3. Click in another window so that Konsole looses focus
4. Click back in the Konsole windows

Actual Results:  
You will see something like this:

> sleep 1000
^[[O^[[I^

Expected Results:  
No escape codes:

> sleep 1000

openSUSE Tumbleweed 20160504 x86_64
KDE Frameworks 5.21.0
Qt 5.5.1
German keyboard layout
System settings -> Activating windows Policy: "Click To Focus - Mouse
Precedence",
Focus stealing prevention: Low, [x] Click raises active windows

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

[konsole] [Bug 362790] Konsole sometimes receives escape codes during focus changes

[via KDE Bugzilla]

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

bjoe...@arcor.de changed:

   What|Removed |Added

Summary|Konsole sometimes received  |Konsole sometimes receives
   |escape codes during focus   |escape codes during focus
   |changes |changes

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

[krita] [Bug 362789] Layer docker loses focus while renaming in floating mode (undocked mode)

[Raghavendra kamath via KDE Bugzilla]

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

--- Comment #1 from Raghavendra kamath  ---
Created attachment 98836
  --> https://bugs.kde.org/attachment.cgi?id=98836=edit
video demonstrating the issue

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

[krita] [Bug 362789] New: Layer docker loses focus while renaming in floating mode (undocked mode)

[Raghavendra kamath via KDE Bugzilla]

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

Bug ID: 362789
   Summary: Layer docker loses focus while renaming in floating
mode (undocked mode)
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: raghavendr.ra...@gmail.com

When the layer docker is undocked and kept floating above the canvas or other
place, it becomes near impossible to rename a layer, as it constantly loses
focus and the text entry field is reset . even if we trigger the text entr
field by pressing the f2 button , the moment we type text it loses the focus
and the canvas get's in focus thus triggering the keyboard shortcuts. Double
clicking on the layer name is not usefull as the text field is de selected the
moment we double click making it nearly impossible to rename .

P.S. I also assume that this focus issue is shared with other dockers as well ,
which need thorough testing 

Reproducible: Always

Steps to Reproduce:
1.Open krita and a new document, then add two or three layers 
2.Undock the layer docker and keep it floating somewhere above the canvas
3.double click ont he layer name to trigger text field for renaming
4. if that doesn't work press f2 to trigger text input field, then start typing

Actual Results:  
the focus of the text input field is lost immediately when it is triggered thus
making it impossible to rename a layer when layer docker is in floating mode

Expected Results:  
layer docker or any component shouldn't loose focus while in free floating mode

I have made a video fo the problem, notice the title flicker changes itself as
if it is out of focus and greyed out. Also see that the text field is gone as
soon as it is triggered. ->
https://dl.dropboxusercontent.com/u/3793/focus-issue.mp4 (i'll upload this
file to bug tracker too)

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

[kwin] [Bug 362788] Artifacts in the logout effect using amdgpu driver and opengl renderer

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

  Component|scene-opengl|effects-various

--- Comment #1 from Thomas Lübking  ---
Smells like the blur shader being the ultimate trigger.

Could you add/override

[Effect-Logout]
UseBlur=false

in ~/.config/kwinrc

I'm *dead* sure we just had this, but cannot find the other bug.
The bug is probably in the driver, you could check dmesg and/or kwin's debug
output for GL errors/warnings.

Can you please attach the output of "qdbus org.kde.KWin /KWin
supportInformation"?

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

[kstars] [Bug 361646] KStars hogs CPU until unusable

[Rob via KDE Bugzilla]

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

--- Comment #22 from Rob  ---
I've not reached a conclusion yet, but results so far suggest:

- the latest KStars may be slightly better but the slow down is still there
(sorry!)
- switching off as much OpenGL as I can in the video driver doesn't help
- pausing the KStars clock at launch doesn't help
- I needed to increase the speed/use of my CPU fan to keep improve laptop
performance in general

That said, I've now performed four sessions, rebooting inbetween, without a
slow down and the only difference is that setting in KStars to use the computer
for time/location etc. rather than the devices.

I'm going to leave it running for the evening and then I will try switching
KStars back to using device for time/location to see if the problem then comes
back.

KStars/Ekos/Indi is sooo sweet with this problem resolved, I'm really looking
forward to using it for real. :-)

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

[kinfocenter] [Bug 347344] KInfoCenter crashes after click Energy Information

[via KDE Bugzilla]

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

haoxian.z...@gmail.com changed:

   What|Removed |Added

 CC||haoxian.z...@gmail.com

--- Comment #28 from haoxian.z...@gmail.com ---
My system might also have this bug, but I am not sure. Here is what I found and
I hope this could be helpful.
---
Application: kinfocenter (5.6.2)

Qt Version: 5.5.1
Frameworks Version: 5.21.0
Operating System: Linux 4.5.2-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160422) (x86_64)"

-- Information about the crash:
What I am doing:
1. Run kinfocenter in GUI,
2. Click to view "Energy Information",
3. Then "Graphical Information" -> "X Server",
4. Click x (close) from the top-right corner.

BUT, the app doesn't crash if the step 2 and step 3 not included both, but they
could be in reverse sequence.

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org/

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

[kstars] [Bug 361646] KStars hogs CPU until unusable

[Jasem Mutlaq via KDE Bugzilla]

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

--- Comment #21 from Jasem Mutlaq  ---
Any update?

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

[skrooge] [Bug 362786] Error importing protected or unprotected Money file

[Stephane MANKOWSKI via KDE Bugzilla]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1
   Assignee|guillaume.deb...@gmail.com  |steph...@mankowski.fr

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

[kwin] [Bug 362788] New: Artifacts in the logout effect using amdgpu driver and opengl renderer

[Luca Mastromatteo via KDE Bugzilla]

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

Bug ID: 362788
   Summary: Artifacts in the logout effect using amdgpu driver and
opengl renderer
   Product: kwin
   Version: unspecified
  Platform: Archlinux Packages
   URL: http://imgur.com/a/zcAzO
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: scene-opengl
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukycroci...@gmail.com

I've got two archlinux running on two different pcs, one running with an AMD R9
380 using the amdgpu driver, and the other one running an integrated skylake
iGPU. 
Basically, i've got artifacts when I push the logout button to exit my session,
this does not happen into the other PC running the intel iGPU.
The great thing is that this problem seems to occur only with the OpenGL
Renderer, and not with the XRender one. 
I was able to take some screenshots.

Reproducible: Always

Steps to Reproduce:
1. Press the logout button using the openGL renderer
2. Have a video card with the AMDGPU driver
3.

Actual Results:  
The fade animation has artifacts.

Expected Results:  
The animation should be normal

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

[kaddressbook] [Bug 357228] KAddressbook crashes on startup with configured CardDav

[Chris Williamson via KDE Bugzilla]

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

Chris Williamson  changed:

   What|Removed |Added

 CC||chris@johnchristianwilliams
   ||on.name

--- Comment #4 from Chris Williamson  ---
Crashes for me too with an OwnCloud CardDAV resource on Kubuntu.

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

[kate] [Bug 362604] Kate on Windows doesn't recognize UTF-8 encoding, even using BOM

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #1 from Dominik Haumann  ---
Hi Christian, could you please attach a demo file before and after the save? It
would help us to reproduce and see what happens.

Usually, Kate should detect the BOM (see Tools > Add Byte Order Mark for
current file, or general settings in Settings > Configure Kate > Open/Save > in
the General tab "Enable byte order mark".

If you play around with these settings, does anything change?

Also, could you please attach a screenshot of your Open/Save config page? It
contains all the Encoding stuff that is used.

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

[krita] [Bug 362025] [multiscreen setup] 'drop down dockers' pop-up on the wrong screen

[David REVOY via KDE Bugzilla]

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

--- Comment #2 from David REVOY  ---
Created attachment 98835
  --> https://bugs.kde.org/attachment.cgi?id=98835=edit
[ ^ screenrecord video of the bug ]

@Scott: Hey! Yes. Still a big issue here with 3.0 . May be my number #1 problem
with 3.0. I attach here a video of my two screen ( 2 x 1920x1080 screen. I'm
used to work on the right one. ) because I guess it's hard to reproduce:

description of the video:
* 00:00 I start Krita on the menu of the right screen but it startup on(left) 
-BUG-
* 00:15 I move Krita on my right screen with my tablet mapped on it ( with
mouse )
* 00:20 'New' dialog is OK
* 00:34 'Tool Option' is OK
* 00:38 I close Krita
* 00:45 I start Krita another time: this time it appears on the good screen
(the right). OK
* 00:47 'New' dialog appears on the left screen -BUG-
* 00:58 'Tool options' appears on the wrong screen -BUG-
* 01:03 'Brush settings' appears on the wrong screen -BUG-
* 01:14 Testing the -BUG- in maximised windows mode.

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

[krita] [Bug 362721] Ability to use Edit -> Paste option without create canvas

[RJ via KDE Bugzilla]

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

--- Comment #2 from RJ  ---
No I dont think so because if one click on menu entry and nothing happens is
not good. Could you open that window when press Edit -> Paste

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

[kwin] [Bug 362782] Crash when click shutdown

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Thomas Lübking  ---
This only says kwin aborted, but not why.
Do you get a crash dialog? Can you provide the "developer information" (aka a
backtrace)?

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

[krita] [Bug 362722] regression in "Create from clipboard window

[RJ via KDE Bugzilla]

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

--- Comment #2 from RJ  ---
Ok. Just tested new builds from link [1].
On OSX and Windows 7 all went fine. Tested in ALTLinux failed. Seems it' linux
specific bug.

More deeper explanation:
1. Start Krita and open New->From clipboard dialog.
2. Width was 1600 Height was 1200.
3. Start Kolourpaint and choose image ( ex. 1041x615)
4. Copy it and focus on Krita
5. Width 128 Height 75

And yes all time Krita was opened before I copy something to clipboard.

[1] https://krita.org/item/new-development-builds-ready/

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

[kmail2] [Bug 362787] Unread option seems to work in the opposite way

[Ian via KDE Bugzilla]

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

--- Comment #1 from Ian  ---
Kmail 5.2.0, 
KDE Frameworks 5.21.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

openSUSE Tumbleweed (20160504) (x86_64)

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

[kmail2] [Bug 362787] New: Unread option seems to work in the opposite way

[Ian via KDE Bugzilla]

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

Bug ID: 362787
   Summary: Unread option seems to work in the opposite way
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-b...@kde.org
  Reporter: ianse...@yahoo.co.uk

Right click "Name" above the folders and select "Unread", it no longer dispays
an Unread count next to each folder.

Reproducible: Always

Steps to Reproduce:
1. Right click "Name" above the folders
2. select "Unread" in "View Columns" popup
3.

Actual Results:  
This removes teh unread emails count next to the folders

Expected Results:  
display count of unread emails in a folder

Default is unset but it displays the count.

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

[skrooge] [Bug 362786] New: Error importing protected or unprotected Money file

[Thierry_AP via KDE Bugzilla]

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

Bug ID: 362786
   Summary: Error importing protected or unprotected Money file
   Product: skrooge
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: guillaume.deb...@gmail.com
  Reporter: thierry.arpin-p...@orange.fr
CC: steph...@mankowski.fr

My first attempt was to import into Skrooge 1.9.3BETA a MS MONEY 99 .mny file
with a passwd.
This file doesn't appear as protected in Skroodge (no lock icon); Skroodge asks
for a passwd : "Ce fichier semble être protégé.Veuillez saisir le mot de
passe". After typing the passwd, the message is "Mauvais mot de passe".

My second attempt was to suppress the passwd in MS MONEY and generate a new
.mny file.
Unfortunately, Skroodge behaves exactly the same as in the first attempt.

Reproducible: Always

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

[ark] [Bug 346342] Ark (should) support xar archive

[Ragnar Thomsen via KDE Bugzilla]

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

Ragnar Thomsen  changed:

   What|Removed |Added

   Version Fixed In||16.08.0
  Latest Commit||http://commits.kde.org/ark/
   ||5dff013d4a3fdc473bc17d608c8
   ||22a221aa75f01
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Ragnar Thomsen  ---
Git commit 5dff013d4a3fdc473bc17d608c822a221aa75f01 by Ragnar Thomsen.
Committed on 07/05/2016 at 16:22.
Pushed by rthomsen into branch 'master'.

Add XAR support

Enable read-only XAR support in libarchiveplugin. The XAR mimetype was
added in shared-mime-info 1.6 released in February 2016, so we install
the mimetype ourselves in case the user is running an older version than
1.6.
FIXED-IN: 16.08.0
Differential Revision: D1551

M  +23   -0autotests/kerfuffle/archivetest.cpp
A  +---autotests/kerfuffle/data/simplearchive.xar
M  +2-0autotests/kerfuffle/mimetypetest.cpp
M  +8-0kerfuffle/mime/kerfuffle.xml
M  +1-1plugins/libarchive/CMakeLists.txt
M  +2-1plugins/libarchive/kerfuffle_libarchive_readonly.json

http://commits.kde.org/ark/5dff013d4a3fdc473bc17d608c822a221aa75f01

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

[krita] [Bug 362785] New: Undoing layer opacity change not working sometimes

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 362785
   Summary: Undoing layer opacity change not working sometimes
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

This happens in Version: 3.0 Beta (git 962bfe1)

It's a bit bizarre. 

Sometimes  pressing Ctrl+Z (or clicking the Undo option from the top Edit menu)
after changing the opacity of a layer will not undo it. Instead it will undo
the step before the Opacity Change. Also Opacity Change doesn't show up in the
History list. 

And then after a while Opacity Change re-appears as an option and undoing it
works... 

Reproducible: Sometimes

Steps to Reproduce:
1.Change layer opacity
2.Try to undo it (either Ctrl+Z or from the Edit Menu
3. Sometimes it will not undo the Opacity Change but the step before.

Actual Results:  
Undoing layer opacity does not work sometimes

Expected Results:  
Undoing Opacity change should work.

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

[Breeze] [Bug 361192] File managers use wrong breeze icons size.

[Tsu Jan via KDE Bugzilla]

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

--- Comment #2 from Tsu Jan  ---
Wrong address! Sorry, the bug is in qiconloader.cpp -> directoryMatchesSize().

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

[Breeze] [Bug 361192] File managers use wrong breeze icons size.

[Tsu Jan via KDE Bugzilla]

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

Tsu Jan  changed:

   What|Removed |Added

 CC||tsujan2...@gmail.com

--- Comment #1 from Tsu Jan  ---
This is a Qt bug (in qiconloader.cpp -> directorySizeDistance()).

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

[krita] [Bug 362453] Crash if I creat new file while half screen the krita window

[via KDE Bugzilla]

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

--- Comment #4 from aqua...@gmail.com ---
(In reply to ninjadamus from comment #2)
> i cant reproduce it either on windows 7. which version of windows are you
> using? 
> 
> and i never knew about the windows key + left/right shortcut thanks! seems
> like a useful shortcut for us artist people.

I am running windows 8.

Also, windows up/down is maximize and restore down, and if you do windows down
a second time it minimizes. Unfortunately windows up doesn't open it back up.

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

[kdenlive] [Bug 362784] New: git master: deselecting split audio/video config option does not deselect target track(s)

[via KDE Bugzilla]

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

Bug ID: 362784
   Summary: git master: deselecting split audio/video config
option does not deselect target track(s)
   Product: kdenlive
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: wegwerf-1-...@gmx.de

When switching of splitting audio from video in Kdenlive's config dialog,
target tracks that still might be selected are not switched off. Only after
clicking on a status LED all tracks gets properly deselected.

Reproducible: Always

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

[krita] [Bug 362453] Crash if I creat new file while half screen the krita window

[via KDE Bugzilla]

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

--- Comment #3 from aqua...@gmail.com ---
(In reply to Boudewijn Rempt from comment #1)
> That sounds very strange and I cannot reproduce it. Does that also happen if
> you disable opengl first?

I am sorry, but I do not know how to disable opengl.

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

[krita] [Bug 362721] Ability to use Edit -> Paste option without create canvas

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

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

--- Comment #1 from Scott Petrovic  ---
This option exists already. Go to Edit > Paste  Into New Image. We might be
able to modify Edit > Paste, but it is probably ok with the existing way.

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

[krita] [Bug 362421] [windows only] Crash when i creat a second animation file

[via KDE Bugzilla]

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

--- Comment #3 from aqua...@gmail.com ---
(In reply to Scott Petrovic from comment #2)
> I am on a Windows 10 box on the May 5 build
> (krita-3.0-Beta-master-962bfe1-x64). I cannot get this crash following the
> steps.
> 
> There were a few bug fixes recently with closing documents and openGL. could
> you try to grab the latest version and see if the same problem is still 
> happening?

I got the May 5 build and I am no longer able to reproduce the crash.

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

[krita] [Bug 362421] [windows only] Crash when i creat a second animation file

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

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

--- Comment #4 from wolthera  ---
yay!

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

[krita] [Bug 360601] [INTEL] Canvas doesn't update but is not black either

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #6 from Scott Petrovic  ---
Do the latest builds of the 64-bit version work. There have been some fixes
with OpenGL and input that have happened since your last message. It may have
resolved this issue.

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

[krita] [Bug 362025] [multiscreen setup] 'drop down dockers' pop-up on the wrong screen

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
Is this still an issue. There were some fixes done with saving and loading the
window and docker positions since this bug was filed.

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

[krita] [Bug 362626] Color to Alpha - Create filter mask issue

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

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

--- Comment #1 from Scott Petrovic  ---
The functionality works like you say in 3.0. It also works the same way in
2.9.11, so it isn't a regression but a bug that has existed for a while.

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

[umbrello] [Bug 362783] Crash after removing a component diagramm

[Artem Goncharov via KDE Bugzilla]

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

--- Comment #1 from Artem Goncharov  ---
Created attachment 98834
  --> https://bugs.kde.org/attachment.cgi?id=98834=edit
autosave.xmi of the project, that causes a fail

uploading autosave.xmi file of the project, which causes crash removing a
component diagram

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

[umbrello] [Bug 362783] New: Crash after removing a component diagramm

[Artem Goncharov via KDE Bugzilla]

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

Bug ID: 362783
   Summary: Crash after removing a component diagramm
   Product: umbrello
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: artem.goncha...@gmail.com

Application: umbrello (2.16.1)
KDE Platform Version: 4.14.18
Qt Version: 4.8.7
Operating System: Linux 4.4.8-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
- What I was doing when the application crashed:
Drawed a test project, tried to remove component diagram, having some elements
on it

The crash can be reproduced every time.

-- Backtrace:
Application: Umbrello UML Modeller (umbrello), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f0e1c247900 (LWP 6185))]

Thread 3 (Thread 0x7f0dfbf0b700 (LWP 6767)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f0e1877a8f6 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x563e3c7882b0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=this@entry=0x563e3c7e4958,
mutex=mutex@entry=0x563e3c7e4950, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f0e19cec12c in QFileInfoGatherer::run (this=0x563e3c7e4940) at
dialogs/qfileinfogatherer.cpp:214
#4  0x7f0e1877a38c in QThreadPrivate::start (arg=0x563e3c7e4940) at
thread/qthread_unix.cpp:352
#5  0x7f0e184d860a in start_thread (arg=0x7f0dfbf0b700) at
pthread_create.c:334
#6  0x7f0e17977a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f0dfb70a700 (LWP 6768)):
#0  0x7ffcdb9d5ca7 in clock_gettime ()
#1  0x7f0e17985cc6 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f0dfb7099e0) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f0e187d4c35 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7f0e188bad15 in QTimerInfoList::updateCurrentTime
(this=0x7f0dec002ee0) at kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7f0dec002ee0, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7f0e188b954c in timerSourcePrepareHelper (src=,
timeout=0x7f0dfb709ab4) at kernel/qeventdispatcher_glib.cpp:143
#7  0x7f0e188b9615 in timerSourcePrepare (source=,
timeout=timeout@entry=0x7f0dfb709ab4) at kernel/qeventdispatcher_glib.cpp:176
#8  0x7f0e1305a70d in g_main_context_prepare
(context=context@entry=0x7f0dec0009a0, priority=priority@entry=0x7f0dfb709b40)
at gmain.c:3442
#9  0x7f0e1305b09b in g_main_context_iterate
(context=context@entry=0x7f0dec0009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3820
#10 0x7f0e1305b27c in g_main_context_iteration (context=0x7f0dec0009a0,
may_block=may_block@entry=1) at gmain.c:3901
#11 0x7f0e188b9e7e in QEventDispatcherGlib::processEvents
(this=0x7f0dec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#12 0x7f0e1131 in QEventLoop::processEvents
(this=this@entry=0x7f0dfb709c80, flags=...) at kernel/qeventloop.cpp:149
#13 0x7f0e14a5 in QEventLoop::exec (this=this@entry=0x7f0dfb709c80,
flags=...) at kernel/qeventloop.cpp:204
#14 0x7f0e18777a99 in QThread::exec (this=this@entry=0x563e3c76af70) at
thread/qthread.cpp:538
#15 0x7f0e18868203 in QInotifyFileSystemWatcherEngine::run
(this=0x563e3c76af70) at io/qfilesystemwatcher_inotify.cpp:265
#16 0x7f0e1877a38c in QThreadPrivate::start (arg=0x563e3c76af70) at
thread/qthread_unix.cpp:352
#17 0x7f0e184d860a in start_thread (arg=0x7f0dfb70a700) at
pthread_create.c:334
#18 0x7f0e17977a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f0e1c247900 (LWP 6185)):
[KCrash Handler]
#6  QPointer::operator QGraphicsScene* (this=)
at ../../src/corelib/kernel/qpointer.h:78
#7  QGraphicsView::scene (this=this@entry=0x0) at
graphicsview/qgraphicsview.cpp:1592
#8  0x563e3abd8e05 in UMLView::umlScene (this=this@entry=0x0) at
../../umbrello/umlview.cpp:56
#9  0x563e3aaa73e3 in Uml::CmdBaseWidgetCommand::scene
(this=this@entry=0x563e3c792900) at
../../umbrello/cmds/widget/cmd_baseWidgetCommand.cpp:49
#10 0x563e3aaa7c02 in Uml::CmdRemoveWidget::redo (this=0x563e3c792900) at
../../umbrello/cmds/widget/cmd_removeWidget.cpp:48
#11 0x7f0e19e59357 in QUndoStack::push (this=0x563e3c1c23a0,
cmd=cmd@entry=0x563e3c792900) at util/qundostack.cpp:583
#12 0x563e3ab81eb5 in UMLApp::executeCommand (this=0x563e3bfd1160,
cmd=0x563e3c792900) at ../../umbrello/uml.cpp:3297
#13 0x563e3abc3ee7 in 

[krita] [Bug 362421] [windows only] Crash when i creat a second animation file

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #2 from Scott Petrovic  ---
I am on a Windows 10 box on the May 5 build
(krita-3.0-Beta-master-962bfe1-x64). I cannot get this crash following the
steps.

There were a few bug fixes recently with closing documents and openGL. could
you try to grab the latest version and see if the same problem is still 
happening?

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

[krita] [Bug 362642] Whenever I open Krita 3.0 beta with my Tablet, the brush tool does not work at all.

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #4 from Scott Petrovic  ---
If the other tools work, this doesn't sound like a tablet or OpenGL issue. Does
the dynamic brush tool work? that is very similar to the freehand brush tool.

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

[krita] [Bug 362714] going to frame 1, krita closes when onion skin is activated

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
I am on Windows 10 and cannot get this crash to happen on the May 5 build
(krita-3.0-Beta-master-962bfe1-x64). Can anyone else get this crash to happen?

If you have been testing earlier builds, maybe there is something odd in the
config file that is messing it up. Clearing that could potentially help.

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

[krita] [Bug 362730] Instant preview makes Ctrl+LMB color picking unresponsive

[Tyson Tan via KDE Bugzilla]

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

--- Comment #5 from Tyson Tan  ---
Created attachment 98833
  --> https://bugs.kde.org/attachment.cgi?id=98833=edit
Krita 3.0 beta Instant Preview drawing artifact

Apparently, it was not an Undo/Redo related artifact, it's a canvas drawing
artifact. As you can see in this video, Instant Preview is actually making the
canvas drawing much slower. The progress bar took seconds to finish. When I
turn Instant Preview OFF, then there is no delay at all.

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

[krita] [Bug 362722] regression in "Create from clipboard window

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #1 from Scott Petrovic  ---
can you provide more information. it appears to be working fine for me on the
May 5 build ( krita-3.0-Beta-master-962bfe1-x64) on Windows 10.

When I copy an image to my clipboard, the height and width update on the
clipboard. You need krita open. It doesn't remember what is on the clipboard
before the application starts.

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

[krita] [Bug 362730] Instant preview makes Ctrl+LMB color picking unresponsive

[Tyson Tan via KDE Bugzilla]

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

--- Comment #4 from Tyson Tan  ---
It probably has something to do with the size of the document.
It happened to a 5500x6000px, 3 layers, 500M memory usage document. Maybe not
the first few picking, but the picking will fail after a few strokes.

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

[krita] [Bug 362352] Brush engine scratchpad crashes krita now. (regression in Beta1 due to MinGW)

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

 CC||scottpetro...@gmail.com

--- Comment #4 from Scott Petrovic  ---
I am on the beta build that boud release on May 5
(krita-3.0-Beta-master-962bfe1-x64)

I am on Windows 10 and an Intuos3. Painting on the scratchpad does not give me
any crashes.

Does the latest build still do this?

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

[krita] [Bug 362730] Instant preview makes Ctrl+LMB color picking unresponsive

[Tyson Tan via KDE Bugzilla]

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

--- Comment #3 from Tyson Tan  ---
Created attachment 98832
  --> https://bugs.kde.org/attachment.cgi?id=98832=edit
Krita 3.0 beta Instant Preview related Ctrl Color picking issue test file

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

[krita] [Bug 362730] Instant preview makes Ctrl+LMB color picking unresponsive

[Tyson Tan via KDE Bugzilla]

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

--- Comment #2 from Tyson Tan  ---
Created attachment 98831
  --> https://bugs.kde.org/attachment.cgi?id=98831=edit
Krita 3.0 beta Instant Preview related Ctrl Color picking issue video

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

[krita] [Bug 362659] Move and transform tool can cause krita to pan to the side indefinitely.

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
Summary|Canvas stuck to top of the  |Move and transform tool can
   |screen (scrollbars do not   |cause krita to pan to the
   |move the canvas, nor does   |side indefinitely.
   |the move tool)  |

--- Comment #4 from wolthera  ---
Thanks, then I know which bug this is :)

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

[krita] [Bug 362712] Crash when switching OpenGL on/off

[Scott Petrovic via KDE Bugzilla]

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

Scott Petrovic  changed:

   What|Removed |Added

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

--- Comment #3 from Scott Petrovic  ---
this also happens on my windows 10 build

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

[krita] [Bug 362740] G'MIC Filter Black & White Interactive Colorize

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Ever confirmed|0   |1
   Severity|normal  |wishlist
 Status|UNCONFIRMED |CONFIRMED

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

I agree with your observations, but these are feature additions, so I'm
changing the bug report accordingly. I've asked Lukas to look into this.

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

[krita] [Bug 362487] [Huion 610] Cursor is misaligned with brush/tools

[Julia via KDE Bugzilla]

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

Julia  changed:

   What|Removed |Added

 CC||julia_le...@aol.com

--- Comment #3 from Julia  ---
I'm having this exact problem because I also have a 610pro, but I'm awful with
computer stuff and I'm not really sure how to uninstall my drivers and install
new ones. I went on the krita faq but it only shows how to do it on Linux, and
I have windows 10. Idk how to do any of these things, please help!

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

[krita] [Bug 362533] Tremulous lines when drawing with pencil (hidpi related?)

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|Tremolous lines when|Tremulous lines when
   |drawing with pencil (hidpi  |drawing with pencil (hidpi
   |related?)   |related?)
 CC||b...@valdyas.org

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

[krita] [Bug 355752] Scaling down a Paint Layer creates visual artifacts

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #5 from Boudewijn Rempt  ---
I suspect so... Thanks for checking back!

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

[krita] [Bug 362412] Krita won't start

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #5 from Boudewijn Rempt  ---
The ancient-distro appimage now has gmic, but without openmp, so it's slower.
But it's in there :-)

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

[kmail2] [Bug 339887] KMail shows pictures in html messages as attachments.

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

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

--- Comment #21 from Laurent Montel  ---
Verify in 5.2.0 it's fixed

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

[kwin] [Bug 362782] New: Crash when click shutdown

[Eric via KDE Bugzilla]

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

Bug ID: 362782
   Summary: Crash when click shutdown
   Product: kwin
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: eric.linjial...@gmail.com

When clink Power/session > shutdown, the crash notification will appear with
the '30 second left' alert.
Executable: kwin_x11 PID: 30430 Signal: Aborted (6) Time: 5/7/16 15:10:42

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

[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view

[Elvis Angelaccio via KDE Bugzilla]

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

--- Comment #19 from Elvis Angelaccio  ---
Created attachment 98830
  --> https://bugs.kde.org/attachment.cgi?id=98830=edit
Weng's backtrace (duplicate #361946)

The Weng's backtrace in duplicate #361946 is more detailed, it looks like the
crash happens when appending to the 'overlays' stringlist?

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

[plasmashell] [Bug 362781] New: Plasma Crash

[Adnan Kurniawan via KDE Bugzilla]

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

Bug ID: 362781
   Summary: Plasma Crash
   Product: plasmashell
   Version: 5.6.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: adnan...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.3)

Qt Version: 5.6.0
Frameworks Version: 5.21.0
Operating System: Linux 4.5.1-5.g99697f1-default x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
open firefox, opening youtube, but before I always had a connect and disconnect
wifi conection, this because of access point hardware malfunction. after
numerous connect and disconnect suddenly plasma is crash

- Unusual behavior I noticed:
bottom panel dissapear, but any active window still active and work as ussual
even youtube video still play, after a few second, bottom panel appear again.

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

Thread 18 (Thread 0x7f2c8ee1b700 (LWP 3016)):
#0  0x7f2c9cdc9bdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f2ca1cd6422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f2ca1cd809f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f2c91a36cd9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f2c9d44b749 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f2c9c5d30a4 in start_thread (arg=0x7f2c8ee1b700) at
pthread_create.c:309
#6  0x7f2c9cdd200d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 17 (Thread 0x7f2c8cdfb700 (LWP 3017)):
#0  0x7f2c994b42d5 in g_main_context_prepare
(context=context@entry=0x7f2c8990, priority=priority@entry=0x7f2c8cdfaca8)
at gmain.c:3447
#1  0x7f2c994b4b03 in g_main_context_iterate
(context=context@entry=0x7f2c8990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3761
#2  0x7f2c994b4cec in g_main_context_iteration (context=0x7f2c8990,
may_block=1) at gmain.c:3842
#3  0x7f2c9d65d43b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f2c9d60b16b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2c9d446caa in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f2c9e418095 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f2c9d44b749 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f2c9c5d30a4 in start_thread (arg=0x7f2c8cdfb700) at
pthread_create.c:309
#9  0x7f2c9cdd200d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 16 (Thread 0x7f2c873ea700 (LWP 3033)):
#0  0x7f2c9cdc5cad in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f2c994f5750 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f2c873e9bf0, __fd=) at /usr/include/bits/unistd.h:44
#2  0x7f2c994f5750 in g_wakeup_acknowledge (wakeup=0x7f2c800025a0) at
gwakeup.c:210
#3  0x7f2c994b4714 in g_main_context_check
(context=context@entry=0x7f2c7c000990, max_priority=2147483647,
fds=fds@entry=0x7f2c7c002e70, n_fds=n_fds@entry=1) at gmain.c:3579
#4  0x7f2c994b4b7b in g_main_context_iterate
(context=context@entry=0x7f2c7c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3778
#5  0x7f2c994b4cec in g_main_context_iteration (context=0x7f2c7c000990,
may_block=1) at gmain.c:3842
#6  0x7f2c9d65d43b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f2c9d60b16b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f2c9d446caa in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f2ca0798b98 in  () at /usr/lib64/libQt5Qml.so.5
#10 0x7f2c9d44b749 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f2c9c5d30a4 in start_thread (arg=0x7f2c873ea700) at
pthread_create.c:309
#12 0x7f2c9cdd200d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 15 (Thread 0x7f2c748a4700 (LWP 3035)):
#0  0x7f2c9cda3d8d in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f2c9cdcb994 in usleep (useconds=) at
../sysdeps/unix/sysv/linux/usleep.c:32
#2  0x7f2c7b62adf0 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#3  0x7f2c7acf9932 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#4  0x7f2c7acf9985 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#5  0x7f2c9c5d30a4 in start_thread (arg=0x7f2c748a4700) at
pthread_create.c:309
#6  0x7f2c9cdd200d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 14 (Thread 0x7f2c6efe6700 (LWP 3036)):
#0  0x7f2c9cdc9bdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f2c994b4be4 in 

[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||wen...@gmail.com

--- Comment #18 from Elvis Angelaccio  ---
*** Bug 361946 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 361946] Dolphin may crash when file in opened folder get modified

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||elvis.angelac...@kdemail.ne
   ||t

--- Comment #1 from Elvis Angelaccio  ---


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

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

[dolphin] [Bug 359556] Crash after closing a split pane

[Elvis Angelaccio via KDE Bugzilla]

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

--- Comment #6 from Elvis Angelaccio  ---
@Luca: your stacktrace is the same of bug #357479:
https://bugs.kde.org/show_bug.cgi?id=357479

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

[plasmashell] [Bug 358328] Application systray icon: No context menu

[EMR_Kde via KDE Bugzilla]

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

--- Comment #18 from EMR_Kde  ---
(In reply to Elia Devito from comment #17)
> On this bug there is two potential patch to fix/workaround this (at least
> for java app)
> 
> https://bugs.kde.org/show_bug.cgi?id=355504

Maybe I am missing something, but after following all of these bugs, I came
full circle back here. I am running DavMail and the icon, when I left click, a
pop up says "JavaEmbeddedFrame", right click does nothing.

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

[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||kde-b...@kristiankoch.com

--- Comment #17 from Elvis Angelaccio  ---
*** Bug 362500 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 362500] dolphin is crashing randomly

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kdemail.ne
   ||t
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Elvis Angelaccio  ---


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

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

[dolphin] [Bug 357479] crash if I close the splitscreen while focused on it and then change the view

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||m_loui...@yahoo.com

--- Comment #16 from Elvis Angelaccio  ---
*** Bug 362506 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 362506] Occasional crash when browsing Owncloud-synced directory

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||elvis.angelac...@kdemail.ne
   ||t
 Resolution|--- |DUPLICATE

--- Comment #1 from Elvis Angelaccio  ---


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

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

[plasmashell] [Bug 356500] xembedsniproxy icons doesn't respond to clicks

[EMR_Kde via KDE Bugzilla]

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

EMR_Kde  changed:

   What|Removed |Added

 CC||emre...@gmail.com

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

[plasmashell] [Bug 355504] xembedsniproxy: java tray icon doesn't work

[EMR_Kde via KDE Bugzilla]

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

EMR_Kde  changed:

   What|Removed |Added

 CC||emre...@gmail.com

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

[frameworks-kactivities-stats] [Bug 362198] Plasma Crashes

[Mebuntu via KDE Bugzilla]

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

Mebuntu  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |---

--- Comment #2 from Mebuntu  ---
This issue occurred immediately after the upgrade to the latest LTS, there have
been no such problems for the past three years.  Home drive is not a network
mount, it is a drive on this computer.  File system does have enough space:
temple@ubuntu:~$ df
Filesystem  1K-blocks   Used  Available Use% Mounted on
udev  4025932  04025932   0% /dev
tmpfs  809024   9944 799080   2% /run
/dev/sda140186200   17259396   20862372  46% /
tmpfs 4045108  748883970220   2% /dev/shm
tmpfs5120  4   5116   1% /run/lock
tmpfs 4045108  04045108   0% /sys/fs/cgroup
/dev/sdb2   204441596  179996848   2748  89% /media/Windows8.1
/dev/sdb3  1912067604   20730672 1794186468   2% /media/TestBackup
/dev/sda4  1843996612 1593704132  156599860  92% /Data
cgmfs 100  0100   0% /run/cgmanager/fs
/dev/sde1  8454885252 6114842360 1910552720  77% /media/DROBO
tmpfs  809024 20 809004   1% /run/user/1000

let me know what information you need and I will add it to the issue.

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

[Akonadi] [Bug 325224] CalDav doesn't read server items

[via KDE Bugzilla]

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

gilbert.d...@gmail.com changed:

   What|Removed |Added

 CC||gilbert.d...@gmail.com

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

[plasmashell] [Bug 358328] Application systray icon: No context menu

[Elia Devito via KDE Bugzilla]

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

Elia Devito  changed:

   What|Removed |Added

 CC||eliadev...@yahoo.it

--- Comment #17 from Elia Devito  ---
On this bug there is two potential patch to fix/workaround this (at least for
java app)

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

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

[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[stephane via KDE Bugzilla]

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

stephane  changed:

   What|Removed |Added

 CC||steph...@scachemaille.ch

--- Comment #7 from stephane  ---
I can confirm the same issue on my manjaro kde installation and also an other
user reported it
in the manjaro forum
https://forum.manjaro.org/index.php?topic=33812.0

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

[plasmashell] [Bug 362780] New: Keyboard Layout order not taken into account

[via KDE Bugzilla]

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

Bug ID: 362780
   Summary: Keyboard Layout order not taken into account
   Product: plasmashell
   Version: 5.6.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slartibar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

I have two different keyboard layouts configured: german and english
In systemsettings5 / input devices / keyboard / layouts i have defined the
order:
1) german
2) english
Switching policy is 'global'.

After logging out and in, english is default again.
No problem switching over to the other layout using keyboard shortcuts or mouse
clicks, but compared to kde4 - the ordering of layouts _was_ taken into
account.

Any chance for a fix ?


Reproducible: Always

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

[plasma-nm] [Bug 356587] Connecting to openconnect vpn fails

[Kete Tefid via KDE Bugzilla]

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

Kete Tefid  changed:

   What|Removed |Added

 CC||ketete...@gmail.com

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