[ktorrent] [Bug 368114] KTorrent fills up .xsession-errors with connection logs

[Edward Donovan]

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

Edward Donovan  changed:

   What|Removed |Added

 CC||kde-b...@numble.net

--- Comment #1 from Edward Donovan  ---
Yes, this is happening here, too, with KTorrent 5.  A flood of messages is
printed to stdout, and I have to work around it for now by setting up a custom
desktop file to run ktorrent with stdout redirected to /dev/null.  

After a bunch of digging, it looks like this is set in the libktorrent code, in
util/log.h at line 97:

void setOutputToConsole(bool on);

The comments say:

   * By default all messages will also be printed on the standard output. This
   * can be turned down using the @a setOutputToConsole function.

I don't know all the reasons that default may have been chosen...  From my
experience, I'd be delighted if the default for general distribution was
changed to 'off'. :)  

If not, is it a matter of where the log level is chosen, somewhere else, and
the problem is that we're getting all these LOG_NOTICE and some LOG_DEBUG
messages? 

This is echoing what Knut said, but here's the impact this is having: Over
several days of running ktorrent off and on, my .xsession-errors file has grown
to over a gigabyte.  The vast majority of that file is ktorrent's messages.  I
first noticed this problem when trying to find another program's diagnostics in
.xsession-errors; it becomes a bit of a DOS attack against trying to find
anything in that file. :)  I haven't done a performance analysis, but from past
experiences, I would think the heavy logging would have at least some
performance impact?

Thank you, if you'll consider this.  And thank you for KTorrent!


(I'm running the Fedora rawhide package of ktorrent 5.0.1, under fedora 25.  I
got the package from
https://rpmfind.net/linux/RPM/fedora/devel/rawhide/x86_64/k/ktorrent-5.0.1-3.fc26.x86_64.html
)

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

[ksudoku] [Bug 381087] Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu.

[Darin Miller]

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

--- Comment #1 from Darin Miller  ---
Forgot to mention, version 1.4 is not available in the Version drop-down.  But
this bug applies to said version.

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

[krita] [Bug 380981] Animation is hung up on Fetching Palette

[bugzilla_noreply]

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

--- Comment #2 from mowerdaugh...@gmail.com ---
(In reply to Boudewijn Rempt from comment #1)
> Which OS? Which version of Krita? What is the color model and channel depth
> of your image? Does the render folder contain frame images?

I'm running on Windows 10, with Krita 3. 1. 4. 

The render folder does have the frame images. I believe the Color Model is
RGB/Alpha, if I found it right. The channel depth is 8-bit integer/channel.

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

[kdelibs] [Bug 381088] New: "report bug" from KDE applications does start infinite number of wine processes

[Peter Ped Helcmanovsky]

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

Bug ID: 381088
   Summary: "report bug" from KDE applications does start infinite
number of wine processes
   Product: kdelibs
   Version: 4.14.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: kbugreport
  Assignee: kdelibs-b...@kde.org
  Reporter: p...@7gods.org
  Target Milestone: ---

I had clean install of KDE Neon distribution, added some applications (many,
including wine), but I didn't touch any specific MIME config, OS was in the
state as it was left by doing `apt-get install ` after installation.

When I tried the button "Launch Bug Report Wizard" in kmahjong, the `xdg-open
http://bugs.kde.org/wizard.cgi` was ran, which ended by launching infinite
number of wine instances (not sure about exact process name, wineservice
maybe).

After I did open firefox -> preferences -> set as default browser, the "Launch
Bug Report Wizard" in kmahjong works as expected, and opens the bug report
wizard in Firefox.

So it looks to me like the KDE neon does not set any default browser, or the
settings is invalid, but how the wine gets picked, and why infinite number of
instances is being launched?

I understand this is more like bad configuration, then code bug, but imagine
unexperienced user watching his task list filled with infinite processes after
he just did want to report some bug in some KDE app, maybe some config sanity
check would be possible? Or reconfigure neon to set Firefox as default browser
right after install?

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

[kmail2] [Bug 380903] KMail crashes when selecting an email

[John]

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

John M. Harris, Jr.  changed:

   What|Removed |Added

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

--- Comment #1 from John M. Harris, Jr.  ---
This is clearly an issue with nouveau, and has been known on the Fedora side
for some time. For future reference, and to help any other Fedora users (and
perhaps others) who may run into similar issues, this is being tracked over on
the Red Hat tracker at https://bugzilla.redhat.com/show_bug.cgi?id=1376107

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

[kdelibs] [Bug 170177] Launch Bugreport Wizard starts Konqueror instead of Default Browser

[Peter Ped Helcmanovsky]

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

Peter Ped Helcmanovsky  changed:

   What|Removed |Added

 CC||p...@7gods.org

--- Comment #11 from Peter Ped Helcmanovsky  ---
WFM on "KDE Neon 5.10". After I set inside firefox preferences "make me default
browser", the "Report bug" menu in KDE applications does finish with "kde-open5
http://bugs.kde.org/wizard.cgi;, which does launch inside Firefox (53.0.3).

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

[ksudoku] [Bug 381087] New: Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu.

[Darin Miller]

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

Bug ID: 381087
   Summary: Newly ported KF5 .desktop Exec line contains an
invalid -caption option preventing ksudoku from
launching via the icon menu.
   Product: ksudoku
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: iandw...@gmail.com
  Reporter: darinsmil...@gmail.com
CC: kde-games-b...@kde.org
  Target Milestone: ---

The org.kde.ksudoku.desktop file need to be updated to exclude the -caption
option as I have been told this function has been deprecated in plasma5. The
app fails to launch via the menu/icon in its current state.  

The following line in src/gui/org.kde.ksudoku.desktop need fixed:

   Exec=ksudoku %i -caption %c

Removing the "%i -caption %c" allows the app to launch without issue.

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

[kmahjongg] [Bug 381086] New: Undo allows to cheat (removal of blocked tiles)

[Peter Ped Helcmanovsky]

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

Bug ID: 381086
   Summary: Undo allows to cheat (removal of blocked tiles)
   Product: kmahjongg
   Version: 0.9
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: p...@7gods.org
CC: kde-games-b...@kde.org
  Target Milestone: ---

Created attachment 106044
  --> https://bugs.kde.org/attachment.cgi?id=106044=edit
Screenshot of result after using the undo-cheat.

What I did:

1) Find some target pair which has one tile blocked (and blocked tiles are easy
to remove), and other free to select.

2) Play regularly to unblock the target pair (remove other tiles, which are
blocking it).

3) Select only the one tile of target pair, which was blocked previously in
step 1.

4) hit Undo as many times, as you need, to get back into the state 1). Now the
blocked tile is drawn as unselected, but the selection is still active.

5) select the other free tile of target pair => the blocked pair is removed
from the game (invalid move).

I'm attaching screenshot of result, I was able to remove two tiles in the
middle (while using Undo to restore all other removals).

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

[yakuake] [Bug 381084] Unexpected switching the active window after hide/show

[Vyacheslav]

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

Vyacheslav  changed:

   What|Removed |Added

Summary|Switching the active window |Unexpected switching the
   |after hide/show |active window after
   ||hide/show

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

[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard

[Xavion]

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

--- Comment #4 from Xavion  ---
Downgrading kwin to v5.9.5 didn't fix the problem either.  I tried it with both
plasma-workspace v5.9.5.1 and v5.10.1.  I'm still thinking incompatibility with
Qt v5.9.0 is the likely cause.

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

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

[Xavion]

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

--- Comment #38 from Xavion  ---
Downgrading kwin to v5.9.5 didn't fix the problem either.  I tried it with both
plasma-workspace v5.9.5.1 and v5.10.1.  I'm still thinking incompatibility with
Qt v5.9.0 is the likely cause.

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

[kwin] [Bug 381021] Hotkeys have no effect in the Kwin window management modes

[Xavion]

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

--- Comment #10 from Xavion  ---
Downgrading kwin to v5.9.5 didn't fix the problem either.  I tried it with both
plasma-workspace v5.9.5.1 and v5.10.1.  I'm still thinking incompatibility with
Qt v5.9.0 is the likely cause.

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

[kwin] [Bug 381076] Alt+Tab crashes KWin

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christoph Feck  ---
Crash is in radeonsi_dri.so OpenGL drivers. Please report directly to
radeonsi_dri developers via https://bugs.freedesktop.org/

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

[valgrind] [Bug 381085] New: Use of SXTX in a memory address is treated as an illegal instruction on Aarch64

[bugzilla_noreply]

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

Bug ID: 381085
   Summary: Use of SXTX in a memory address is treated as an
illegal instruction on Aarch64
   Product: valgrind
   Version: 3.11.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: callgrind
  Assignee: josef.weidendor...@gmx.de
  Reporter: isaacos...@hotmail.com
  Target Milestone: ---

When using a SXTX as part of a memory operand in

e.g, when running the following c program compiled with GCC 5.4.0
int main()
{
asm("MOV X0, #0\n"
"LDR X0, [X29, X0, SXTX #3]");
}

Through callgrind (valgrind --tool=callgrind -v ./a.out) I recieve an illegal
instruction error (specifically I get the following output):

==31690== Callgrind, a call-graph generating cache profiler
==31690== Copyright (C) 2002-2015, and GNU GPL'd, by Josef Weidendorfer et al.
==31690== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==31690== Command: ./a.out
==31690==
--31690-- Valgrind options:
--31690----tool=callgrind
--31690---v
--31690-- Contents of /proc/version:
--31690--   Linux version 4.4.0-75-generic (buildd@bos01-arm64-049) (gcc
version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #96-Ubuntu SMP
Thu Apr 20 09:56:48 UTC 2017
--31690--
--31690-- Arch and hwcaps: ARM64, LittleEndian, baseline
--31690-- Page sizes: currently 4096, max supported 65536
--31690-- Valgrind library directory: /usr/lib/valgrind
==31690== For interactive control, run 'callgrind_control -h'.
--31690-- Reading syms from /home/isaacg/a.out
--31690-- Reading syms from /lib/aarch64-linux-gnu/ld-2.23.so
--31690--   Considering /lib/aarch64-linux-gnu/ld-2.23.so ..
--31690--   .. CRC mismatch (computed 0cfa2cfe wanted e5fee7d4)
--31690--   Considering /usr/lib/debug/lib/aarch64-linux-gnu/ld-2.23.so ..
--31690--   .. CRC is valid
--31690-- Reading syms from /usr/lib/valgrind/callgrind-arm64-linux
--31690--   Considering /usr/lib/valgrind/callgrind-arm64-linux ..
--31690--   .. CRC mismatch (computed 8bef36ae wanted 0f59708e)
--31690--object doesn't have a symbol table
--31690--object doesn't have a dynamic symbol table
--31690-- Scheduler: using generic scheduler lock implementation.
==31690== embedded gdbserver: reading from
/tmp/vgdb-pipe-from-vgdb-to-31690-by-isaacg-on-???
==31690== embedded gdbserver: writing to  
/tmp/vgdb-pipe-to-vgdb-from-31690-by-isaacg-on-???
==31690== embedded gdbserver: shared mem  
/tmp/vgdb-pipe-shared-mem-vgdb-31690-by-isaacg-on-???
==31690==
==31690== TO CONTROL THIS PROCESS USING vgdb (which you probably
==31690== don't want to do, unless you know exactly what you're doing,
==31690== or are doing some strange experiment):
==31690==   /usr/lib/valgrind/../../bin/vgdb --pid=31690 ...command...
==31690==
==31690== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==31690==   /path/to/gdb ./a.out
==31690== and then give GDB the following command
==31690==   target remote | /usr/lib/valgrind/../../bin/vgdb --pid=31690
==31690== --pid is optional if only one valgrind process is running
==31690==
--31690-- Reading syms from /usr/lib/valgrind/vgpreload_core-arm64-linux.so
--31690--   Considering /usr/lib/valgrind/vgpreload_core-arm64-linux.so ..
--31690--   .. CRC mismatch (computed ce9dff7a wanted 728c1b44)
--31690--object doesn't have a symbol table
--31690-- Reading syms from /lib/aarch64-linux-gnu/libc-2.23.so
--31690--   Considering /lib/aarch64-linux-gnu/libc-2.23.so ..
--31690--   .. CRC mismatch (computed 8dc9f479 wanted a6ed6c12)
--31690--   Considering /usr/lib/debug/lib/aarch64-linux-gnu/libc-2.23.so ..
--31690--   .. CRC is valid
--31690-- Symbol match: found runtime_resolve: ld-2.23.so +0x136f8=0x40136f8
gen_indexed_EA: unhandled case optS == 0xF
ARM64 front end: load_store
disInstr(arm64): unhandled instruction 0xF860FBA0
disInstr(arm64): '1000 0110' '1011 1010'
==31690== valgrind: Unrecognised instruction at address 0x400574.
==31690==at 0x400574: main (in /home/isaacg/a.out)
==31690== Your program just tried to execute an instruction that Valgrind
==31690== did not recognise.  There are two possible reasons for this.
==31690== 1. Your program has a bug and erroneously jumped to a non-code
==31690==location.  If you are running Memcheck and you just saw a
==31690==warning about a bad jump, it's probably your program's fault.
==31690== 2. The instruction is legitimate but Valgrind doesn't handle it,
==31690==i.e. it's Valgrind's fault.  If you think this is the case or
==31690==you are not sure, please let us know and we'll try to fix it.
==31690== Either way, Valgrind will now raise a SIGILL signal which will
==31690== probably kill your program.
==31690==
==31690== Process terminating with default action of signal 4 (SIGILL)
==31690==  Illegal opcode at address 

[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error

[Cristian Aravena Romero]

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

--- Comment #23 from Cristian Aravena Romero  ---
Created attachment 106043
  --> https://bugs.kde.org/attachment.cgi?id=106043=edit
Finished K3b

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

[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error

[Cristian Aravena Romero]

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

--- Comment #22 from Cristian Aravena Romero  ---
Created attachment 106042
  --> https://bugs.kde.org/attachment.cgi?id=106042=edit
K3b log Good

Hello,

I have good news!!!

I followed this [0] guide for updating the firmware.
Https://apingxh.blogspot.cl/2015/02/how-to-upgrade-firmware-for-uj240as-blu.html

And then I've burned the ISO image again.

Apparently the firmware update gave solution to the previous recording error.

Thank you,
-
Cristian

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

[krita] [Bug 381047] layer option gone

[bugzilla_noreply]

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

--- Comment #2 from ziviar...@gmail.com ---
It worked, thank you!

Sent from my iPhone

> On Jun 10, 2017, at 1:06 AM, Boudewijn Rempt  wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=381047
> 
> Boudewijn Rempt  changed:
> 
>   What|Removed |Added
> 
> Resolution|--- |INVALID
> CC||b...@valdyas.org
> Status|UNCONFIRMED |RESOLVED
> 
> --- Comment #1 from Boudewijn Rempt  ---
> Why are people always uninstalling and reinstalling? That doesn't do a thing.
> You can re-open closed dockers in settings/dockers, you can reset your
> workspace to a default with the right-most button in the top toolbar, or you
> can reset the entire Krita configuration
> (https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration). You might
> accidentally have entered canvas-only mode by pressing tab; pressing tab again
> gets you of there.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

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

[k3b] [Bug 381083] [MATSHITA BD-MLT UJ240AS] Finalized recording difference to full recording

[Cristian Aravena Romero]

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

Cristian Aravena Romero  changed:

   What|Removed |Added

Summary|Finalized recording |[MATSHITA BD-MLT UJ240AS]
   |difference to full  |Finalized recording
   |recording   |difference to full
   ||recording

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

[yakuake] [Bug 381084] New: Switching the active window after hide/show

[Vyacheslav]

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

Bug ID: 381084
   Summary: Switching the active window after hide/show
   Product: yakuake
   Version: 3.0.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: alexeev.c...@gmail.com
  Target Milestone: ---

I uses yakuake with 2 splitted windows.
When I hide and show yakuake, it switch active window.

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

[k3b] [Bug 381083] New: Finalized recording difference to full recording

[Cristian Aravena Romero]

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

Bug ID: 381083
   Summary: Finalized recording difference to full recording
   Product: k3b
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: carav...@gmail.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

Created attachment 106041
  --> https://bugs.kde.org/attachment.cgi?id=106041=edit
image of K3b

Hello,

Attach image.

Thanks you,
--
Cristian

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

[kdenlive] [Bug 379729] Crash when adding clip

[farid]

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

--- Comment #1 from farid  ---
Here is another one but with a different versaion of Kdenlive. I still can't
reproduce them though.


Kdenlive 17.07.70
KDE Frameworks 5.34.0
Qt 5.9.0 (built against 5.8.0)
MLT 6.5


(gdb) thread apply all bt

Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault.
0x70dd07c9 in QPersistentModelIndex::parent() const () from
/usr/lib/libQt5Core.so.5

Thread 39 (Thread 0x7fff8700 (LWP 9785)):
#0  0x70dd07c9 in QPersistentModelIndex::parent() const () at
/usr/lib/libQt5Core.so.5
#1  0x70de3288 in QItemSelection::indexes() const () at
/usr/lib/libQt5Core.so.5
#2  0x70de5621 in QItemSelectionModel::selectedIndexes() const () at
/usr/lib/libQt5Core.so.5
#3  0x00839d2b in Bin::slotProducerReady(requestClipInfo const&,
ClipController*) (this=0x1936600, info=..., controller=)
at /tmp/yaourt-tmp-frd/aur-kdenlive-git/src/kdenlive/src/bin/bin.cpp:2190
#4  0x008ddd29 in Bin::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**) (_o=0x1936600, _c=, _id=,
_a=)
at
/tmp/yaourt-tmp-frd/aur-kdenlive-git/src/build/src/kdenlive_autogen/NNRPYQ7WAA/moc_bin.cpp:1223
#5  0x70e62465 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#6  0x008c2af4 in ProducerQueue::gotFileProperties(requestClipInfo,
ClipController*) (this=this@entry=0x19d01b0, _t1=..., _t2=)
at
/tmp/yaourt-tmp-frd/aur-kdenlive-git/src/build/src/kdenlive_autogen/EHEF7UJZKY/moc_producerqueue.cpp:309
#7  0x00825aa3 in ProducerQueue::processFileProperties()
(this=)
at
/tmp/yaourt-tmp-frd/aur-kdenlive-git/src/kdenlive/src/mltcontroller/producerqueue.cpp:841
#8  0x004d748d in QtConcurrent::RunFunctionTask::run()
(this=0xc156850)
at /usr/include/qt/QtConcurrent/qtconcurrentrunbase.h:136
#9  0x70c55171 in  () at /usr/lib/libQt5Core.so.5
#10 0x70c58cbd in  () at /usr/lib/libQt5Core.so.5
#11 0x7fffee281297 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7025b25f in clone () at /usr/lib/libc.so.6

Thread 38 (Thread 0x7fff6cc23700 (LWP 9779)):
#0  0x7fffee28739d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fffb6ba36dd in  () at /usr/lib/mlt/libmltsdl.so
#2  0x7fffee281297 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7025b25f in clone () at /usr/lib/libc.so.6

Thread 37 (Thread 0x7fff99e36700 (LWP 9778)):
#0  0x70251396 in ppoll () at /usr/lib/libc.so.6
#1  0x7fffe79c079d in pa_mainloop_poll () at /usr/lib/libpulse.so.0
#2  0x7fffe79c0d8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
---Type  to continue, or q  to quit---
#3  0x7fffb693a55d in  () at /usr/lib/libSDL-1.2.so.0
#4  0x7fffb690e76b in  () at /usr/lib/libSDL-1.2.so.0
#5  0x7fffb6916e18 in  () at /usr/lib/libSDL-1.2.so.0
#6  0x7fffb6957d39 in  () at /usr/lib/libSDL-1.2.so.0
#7  0x7fffee281297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7025b25f in clone () at /usr/lib/libc.so.6

Thread 36 (Thread 0x7fff6e025700 (LWP 9777)):
#0  0x7fffee28739d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x76fea86b in  () at /usr/lib/libmlt.so.6
#2  0x007624fd in RenderThread::run() (this=0x7fff84183ea0)
at
/tmp/yaourt-tmp-frd/aur-kdenlive-git/src/kdenlive/src/monitor/glwidget.cpp:1282
#3  0x70c58cbd in  () at /usr/lib/libQt5Core.so.5
#4  0x7fffee281297 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7025b25f in clone () at /usr/lib/libc.so.6

Thread 35 (Thread 0x7fffa113c700 (LWP 9776)):
#0  0x7fffee28739d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fffb6ba40c0 in  () at /usr/lib/mlt/libmltsdl.so
#2  0x7fffee281297 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7025b25f in clone () at /usr/lib/libc.so.6

Thread 30 (Thread 0x7fff7affd700 (LWP 9768)):
#0  0x7fffee28739d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x76ff2a43 in  () at /usr/lib/libmlt.so.6
#2  0x7fffee281297 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7025b25f in clone () at /usr/lib/libc.so.6

Thread 29 (Thread 0x7fff7b7fe700 (LWP 9767)):
#0  0x7fffee28739d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x76ff2a43 in  () at /usr/lib/libmlt.so.6
#2  0x7fffee281297 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7025b25f in clone () at /usr/lib/libc.so.6

Thread 28 (Thread 0x7fff7bfff700 (LWP 9766)):
#0  0x7fffee28739d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
---Type  to continue, or q  to quit---
#1  0x76ff2a43 in  () at /usr/lib/libmlt.so.6
#2  0x7fffee281297 in start_thread () at /usr/lib/libpthread.so.0
#3  0x7025b25f in clone () at /usr/lib/libc.so.6

Thread 27 (Thread 0x7fff8e7fc700 (LWP 

[kdenlive] [Bug 380410] Kdenlive crashes when selecting video from bin

[farid]

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

farid  changed:

   What|Removed |Added

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

--- Comment #1 from farid  ---
You seem to have movit enabled, disable it and test... this is an experimental
feature and still unstable,

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

[kdenlive] [Bug 375864] git master - Import images as sequence not working through "Add Clip" method in Project Bin

[farid]

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

--- Comment #8 from farid  ---
(In reply to Jesse from comment #5)
> @Wegwerf, Yes, I went to Add Clip, then selected all of the images in the
> dialog box, then checked the "import images as sequence", then clicked OK.
> They imported with the duration I'd put in settings for single still images,
> leading me to believe Kdenlive was recognizing them as single images during
> import.
> 
> @farid, sorry for the delay in my replies -- been super busy with some new
> virtual reality projects. Cool stuff, but I don't want to let it sway my
> devotion to Kdenlive and free video editing. :) I'll try to be more prompt
> in my replies.


I prefer to add the images from add clip and set the length of them to one 1 in
the settings. playback is smoother than adding the images as a slideshow clip.
have you noticed this?

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

[kdenlive] [Bug 375864] git master - Import images as sequence not working through "Add Clip" method in Project Bin

[farid]

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

farid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #7 from farid  ---
Now, when I add a clip and check the import image sequence it doesn't work any
more. This happened after an update:

Kdenlive 17.07.70
KDE Frameworks 5.34.0
Qt 5.9.0 (built against 5.8.0)
MLT 6.5

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

[systemsettings] [Bug 381082] New: System Settings crashed when changing from one color scheme to another

[Nate Graham]

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

Bug ID: 381082
   Summary: System Settings crashed when changing from one color
scheme to another
   Product: systemsettings
   Version: 5.9.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Application: systemsettings5 (5.9.4)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-22-generic x86_64
Distribution: Ubuntu 17.04

-- Information about the crash:
Steps to reproduce:
System Setting > Colors > change from one color schemeto another

System Settings crashed.

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7fb69b1b1700 (LWP 26183)):
#0  0x7fb6d4479593 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fb6cdd13f89 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb6cdd14514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb6cdd1468c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb6d4479f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb6d442388a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb6d4250fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb6d259bdf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fb6d4255c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fb6cfe456da in start_thread (arg=0x7fb69b1b1700) at
pthread_create.c:456
#10 0x7fb6d3b6217f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7fb6aa83c700 (LWP 26182)):
#0  0x7fb6cdd59ef4 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb6cdd134be in g_main_context_acquire () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb6cdd14425 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb6cdd1468c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb6d4479f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb6d442388a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb6d4250fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb6d259bdf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fb6d4255c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fb6cfe456da in start_thread (arg=0x7fb6aa83c700) at
pthread_create.c:456
#10 0x7fb6d3b6217f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7fb6a3d59700 (LWP 26181)):
#0  0x7fb6cdd13a03 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb6cdd1449b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb6cdd1468c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb6d4479f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb6d442388a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb6d4250fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb6d259bdf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fb6d4255c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb6cfe456da in start_thread (arg=0x7fb6a3d59700) at
pthread_create.c:456
#9  0x7fb6d3b6217f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fb6bbfff700 (LWP 26174)):
#0  0x7fb6d3b5618d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb6cdd14576 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb6cdd1468c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb6d4479f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb6d442388a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb6d4250fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb6d4d7d5c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7fb6d4255c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb6cfe456da in start_thread (arg=0x7fb6bbfff700) at
pthread_create.c:456
#9  0x7fb6d3b6217f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 

[Discover] [Bug 381081] New: Discover crashes when searching immediately after it starts

[Zachary Mazza]

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

Bug ID: 381081
   Summary: Discover crashes when searching immediately after it
starts
   Product: Discover
   Version: 5.10.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: zwjma...@gmail.com
  Target Milestone: ---

If I start searching too quickly after the application window opens, Discover
crashes. If I wait a few seconds after opening Discover and then search, it
doesn't crash.

This crash is repeatable and happens every time.


Backtrace
-

Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd47c1a98c0 (LWP 7109))]

Thread 20 (Thread 0x7fd3c8ff9700 (LWP 7153)):
#0  0x7fd472434ef4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fd4723eeb70 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd4723ef49b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd4723ef68c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fd47836af2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd47831488a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd478141fe3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fd478146c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fd4745206da in start_thread (arg=0x7fd3c8ff9700) at
pthread_create.c:456
#9  0x7fd47774a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 19 (Thread 0x7fd3c97fa700 (LWP 7152)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fd478147a86 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fd4781432b2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fd478146c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd4745206da in start_thread (arg=0x7fd3c97fa700) at
pthread_create.c:456
#5  0x7fd47774a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 18 (Thread 0x7fd3e97fa700 (LWP 7145)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fd478147a86 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fd4781432b2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fd478146c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd4745206da in start_thread (arg=0x7fd3e97fa700) at
pthread_create.c:456
#5  0x7fd47774a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 17 (Thread 0x7fd434ff9700 (LWP 7132)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fd478147a86 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fd4781432b2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fd478146c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd4745206da in start_thread (arg=0x7fd434ff9700) at
pthread_create.c:456
#5  0x7fd47774a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7fd435ffb700 (LWP 7130)):
#0  0x7fd47773e18d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd4723ef576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd4723ef68c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd47836af2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fd47831488a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fd478141fe3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fd478146c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fd4745206da in start_thread (arg=0x7fd435ffb700) at
pthread_create.c:456
#8  0x7fd47774a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 15 (Thread 0x7fd437fff700 (LWP 7126)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fd478147a86 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fd4781432b2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fd478146c98 in ?? () from 

[kwin] [Bug 381021] Hotkeys have no effect in the Kwin window management modes

[Jesse]

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

--- Comment #9 from Jesse  ---
I believe you have to downgrade kwin, not plasma workspace

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

[kwin] [Bug 381021] Hotkeys have no effect in the Kwin window management modes

[Kamil]

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

Kamil  changed:

   What|Removed |Added

Summary|Allow arrow keys to |Hotkeys have no effect in
   |navigate in Desktop Grid|the Kwin window management
   ||modes

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

[kwin] [Bug 381021] Allow arrow keys to navigate in Desktop Grid

[Kamil]

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

Kamil  changed:

   What|Removed |Added

  Component|effects-desktop-grid|effects-window-management

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

[kwin] [Bug 381021] Allow arrow keys to navigate in Desktop Grid

[Xavion]

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

--- Comment #8 from Xavion  ---
Downgrading plasma-workspace to v5.9.5.1 didn't fix the problem, so I'd say it
has something to do with the qt5-base jump (excuse the pun) from v5.8.0 to
v5.9.0.  I can't be bothered downgrading Qt5; there are too many packages to
rebuild.

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

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

[Xavion]

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

--- Comment #37 from Xavion  ---
Downgrading plasma-workspace to v5.9.5.1 didn't fix the problem, so I'd say it
has something to do with the qt5-base jump (excuse the pun) from v5.8.0 to
v5.9.0.  I can't be bothered downgrading Qt5; there are too many packages to
rebuild.

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

[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard

[Xavion]

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

--- Comment #3 from Xavion  ---
Downgrading plasma-workspace to v5.9.5.1 didn't fix the problem, so I'd say it
has something to do with the qt5-base jump (excuse the pun) from v5.8.0 to
v5.9.0.  I can't be bothered downgrading Qt5; there are too many packages to
rebuild.

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

[plasmashell] [Bug 381055] repeated first icon when multiple systray icons belongs to a single application (kdocker)

[Kethen Chui]

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

--- Comment #3 from Kethen Chui  ---
Another workaround would be modifying kdocker source code to make it one window
to one process, which works better with gtk apps and ibus.

Like this modified version
https://github.com/Kethen/kdocker_ubuntu_one_window_one_process

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

[kwin] [Bug 380237] Spawning programs under cursor only works for monitor of focused window

[Sefa Eyeoglu]

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

Sefa Eyeoglu  changed:

   What|Removed |Added

Version|5.10.0  |5.10.1

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

[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error

[Thomas Schmitt]

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

--- Comment #21 from Thomas Schmitt  ---
Thomas
Hi,

> Upgrade firmware?

If there is a newer version than "1.02" it would be worth a try.
But usually you need a MS-Windows system to run the firmware installer
program.
(I conclude "1.02" from the log text
 Devices 
 --- 
 MATSHITA BD-MLT UJ240AS 1.02  (/dev/sr0 ...
)

"UJ240AS firmware" is probably the term to search for in google or on
firmware providing sites. (I expect a substantial risk of malware on
such sites if not run by the drive manufacturer.)

Have a nice day :)

Thomas

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

[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error

[Cristian Aravena Romero]

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

--- Comment #20 from Cristian Aravena Romero  ---
Hi,

Upgrade firmware?
What Firmware???

Regards,
--
Cristian

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

[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error

[Thomas Schmitt]

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

--- Comment #19 from Thomas Schmitt  ---
Hi,

> :-[ WRITE@LBA=596780h failed with SK=4h/ASC=03h/ACQ=01h]: Input/output error

This is not good news.

SK=4h means "Hardware error". SPC-3 table 27:
"Indicates that the device server detected a non-recoverable hardware
 failure (e.g., controller failure, device failure, or parity error)
 while performing the command or during a self test.

ASC=03h/ACQ=01h is listed in SPC-3 as "NO WRITE CURRENT". No idea what this
shall mean. According to
  http://www.t10.org/lists/asc-num.htm#ASC_03
it is supposed to be emitted by SSC tapes, not by MMC optical drives.
I'd say it indicates a period of drive unconsciousness. This would be
a situation after which one could get the wake-up message from the first
failure in this bug report:
> > :-[ FLUSH CACHE failed with SK=6h/NOT READY TO READY CHANGE, MEDIUM MAY 
> > HAVE CHANGED]: Input/output error

This is surely not K3B's fault and very probably not the fault of growisofs.
It rather looks like the drive hates the medium and gets into strange
states while gnawing on it.

It does not happen always. I assume that the shorter burn runs without
Defect Management improve the chance to get done before madness strikes.
But the situation is clearly unstable.

The only proposal i have is to try other media or a different drive.

Have a nice day :)

Thomas

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

[kate] [Bug 381080] New: Crash when replacing new lines with spaces

[John Salatas]

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

Bug ID: 381080
   Summary: Crash when replacing new lines with spaces
   Product: kate
   Version: 17.04.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: jsala...@gmail.com
  Target Milestone: ---

Application: kate (17.04.2)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.8.0-54-generic x86_64
Distribution: KDE neon User Edition 5.10

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

Seems to happen everytime. Steps to reproduce
1) open kate and type type some lines of text, eg 
a
b
c
d

2) Press CTRL + R  to replace \n (new lines) with a single space and select
mode "Escape Sequences"

3) Press ALT + A to replace all occurences

4) Press ESC to close the replace dialog 

5) Press the UP_ARROW 

Kate crashes

The crash can be reproduced sometimes.

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

Thread 2 (Thread 0x7f837e3b0700 (LWP 6242)):
#0  0x7f8392968a28 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f83929692bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f839296949c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f839853075b in QEventDispatcherGlib::processEvents
(this=0x7f83780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f83984db0ba in QEventLoop::exec (this=this@entry=0x7f837e3afcd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f839830af64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f839c6a8735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f839830fb48 in QThreadPrivate::start (arg=0x7f839c71cd60) at
thread/qthread_unix.cpp:368
#8  0x7f8394a546ba in start_thread (arg=0x7f837e3b0700) at
pthread_create.c:333
#9  0x7f839791382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f838a14e8c0 (LWP 6240)):
[KCrash Handler]
#6  KateLineLayout::viewLineCount (this=) at
/workspace/build/src/render/katelinelayout.cpp:178
#7  KateLineLayout::viewLine (this=0x0, viewLine=viewLine@entry=-1) at
/workspace/build/src/render/katelinelayout.cpp:184
#8  0x7f839c145456 in KateLayoutCache::textLayout (this=,
realLine=, _viewLine=_viewLine@entry=-1) at
/workspace/build/src/render/katelayoutcache.cpp:368
#9  0x7f839c18bdab in KateViewInternal::previousLayout
(this=this@entry=0x1c143f0) at
/workspace/build/src/view/kateviewinternal.cpp:1361
#10 0x7f839c190b41 in KateViewInternal::cursorUp (this=0x1c143f0,
sel=sel@entry=false) at /workspace/build/src/view/kateviewinternal.cpp:1543
#11 0x7f839c1774fe in KTextEditor::ViewPrivate::up (this=)
at /workspace/build/src/view/kateview.cpp:2836
#12 0x7f839c273e08 in KTextEditor::ViewPrivate::qt_static_metacall
(_o=, _c=, _id=, _a=) at /workspace/build/obj-x86_64-linux-gnu/src/moc_kateview.cpp:680
#13 0x7f8398507e89 in QMetaObject::activate (sender=sender@entry=0x1cfebf0,
signalOffset=, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffc973517c0) at kernel/qobject.cpp:3740
#14 0x7f8398508837 in QMetaObject::activate (sender=sender@entry=0x1cfebf0,
m=m@entry=0x7f839975de60 ,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc973517c0)
at kernel/qobject.cpp:3602
#15 0x7f8399282552 in QAction::triggered (this=this@entry=0x1cfebf0,
_t1=false) at .moc/moc_qaction.cpp:369
#16 0x7f8399284ec0 in QAction::activate (this=0x1cfebf0, event=) at kernel/qaction.cpp:1170
#17 0x7f8399285834 in QAction::event (this=, e=) at kernel/qaction.cpp:1098
#18 0x7f8399288ecc in QApplicationPrivate::notify_helper (this=, receiver=0x1cfebf0, e=0x7ffc97351a90) at kernel/qapplication.cpp:3799
#19 0x7f83992908c6 in QApplication::notify (this=0x7ffc973521c0,
receiver=0x1cfebf0, e=0x7ffc97351a90) at kernel/qapplication.cpp:3556
#20 0x7f83984dd0c8 in QCoreApplication::notifyInternal2
(receiver=0x1cfebf0, event=event@entry=0x7ffc97351a90) at
kernel/qcoreapplication.cpp:988
#21 0x7f8398d1a016 in QCoreApplication::sendEvent (event=0x7ffc97351a90,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#22 QShortcutMap::dispatchEvent (this=this@entry=0x16ae158,
e=e@entry=0x7ffc97351b40) at kernel/qshortcutmap.cpp:674
#23 0x7f8398d1a0c9 in QShortcutMap::tryShortcut (this=this@entry=0x16ae158,
e=e@entry=0x7ffc97351b40) at kernel/qshortcutmap.cpp:351
#24 0x7f8398cd2966 in QWindowSystemInterface::handleShortcutEvent
(window=, window@entry=0x1dbf770, timestamp=,
keyCode=16777235, 

[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard

[Xavion]

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

Xavion  changed:

   What|Removed |Added

 CC||xavio...@gmail.com

--- Comment #2 from Xavion  ---
I've just started experiencing the same problem here.  Specifically:
* I can no longer hide the Desktop Grid via its shortcut
* The arrow and Enter keys no longer have any effect

I'm using plasma-framework v5.34.0, plasma-workspace v5.10.1, and qt5-base
v5.9.0 (on Arch Linux).  Only plasma-workspace and qt5-base were upgraded
yesterday.  I wasn't experiencing the problem before then.

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

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

[Xavion]

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

Xavion  changed:

   What|Removed |Added

 CC||xavio...@gmail.com

--- Comment #36 from Xavion  ---
I've just started experiencing the same problem here.  Specifically:
* I can no longer hide the Desktop Grid via its shortcut
* The arrow and Enter keys no longer have any effect

I'm using plasma-framework v5.34.0, plasma-workspace v5.10.1, and qt5-base
v5.9.0 (on Arch Linux).  Only plasma-workspace and qt5-base were upgraded
yesterday.  I wasn't experiencing the problem before then.

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

[Spectacle] [Bug 374009] Spectacle keeps hanging my system

[Jonathan Ringstad]

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

Jonathan Ringstad  changed:

   What|Removed |Added

 CC||jwrings...@gmail.com

--- Comment #9 from Jonathan Ringstad  ---
I can confirm that spectacle hangs my system, on manjaro, bumblebee
(proprietary nvidia + mesa intel) with kernel 4.4.70, xorg 1.19.3 and spectacle
17.04.1.

Everything becomes unresponsive, even switching to a VT becomes impossible. The
mouse still moves, about once every 5-15 seconds. Clicking, dragging, pressing
escape or enter does not do anything (I tried all of those + waited a couple of
minutes for a reaction)

Using anything other than rectangle select does not hang the system, and even
rectangle selection works without crashing the system *sometimes*, but I did
not notice any obvious pattern.

Here are the relevant-looking entries from the journalctl log:

Jun 10 23:16:29 vega kdeinit5[896]: D-Bus call: "org.kde.Spectacle" : "/" :
"StartAgent" : ()
Jun 10 23:16:29 vega dbus-daemon[859]: Activating service
name='org.kde.Spectacle'
Jun 10 23:16:29 vega dbus-daemon[859]: Successfully activated service
'org.kde.Spectacle'
Jun 10 23:16:29 vega spectacle[8168]: WARNING: Cannot find style
"org.kde.desktop" - fallback: "/usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop"
Jun 10 23:16:29 vega spectacle[8168]: qrc:/JobDialog.qml:67: TypeError: Cannot
read property 'Layout' of null
Jun 10 23:16:29 vega spectacle[8168]: qrc:/JobDialog.qml:66: TypeError: Cannot
read property 'Layout' of null
Jun 10 23:16:33 vega kwin_x11[945]: QXcbConnection: XCB error: 3 (BadWindow),
sequence: 57866, resource id: 33554646, major code: 10 (UnmapWindow), minor
code: 0
Jun 10 23:16:33 vega kwin_x11[945]: QXcbConnection: XCB error: 3 (BadWindow),
sequence: 57871, resource id: 33554646, major code: 4 (DestroyWindow), minor
code: 0

Hope that helps, and hope this bug can be resolved quickly!

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

[kwin] [Bug 381021] Allow arrow keys to navigate in Desktop Grid

[Xavion]

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

Xavion  changed:

   What|Removed |Added

 CC||xavio...@gmail.com

--- Comment #7 from Xavion  ---
I've just started experiencing the same problem here.  Specifically:
* I can no longer hide the Desktop Grid via its shortcut
* The arrow and Enter keys no longer have any effect

I'm using plasma-framework v5.34.0, plasma-workspace v5.10.1, and qt5-base
v5.9.0 (on Arch Linux).  Only plasma-workspace and qt5-base were upgraded
yesterday.  I wasn't experiencing the problem before then.

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

[gwenview] [Bug 381079] New: Oversaturated thumbs for sRGB images

[george]

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

Bug ID: 381079
   Summary: Oversaturated thumbs for sRGB images
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: stu...@anchev.net
CC: myr...@kde.org
  Target Milestone: ---

gwenview5-16.08.2-1.1.x86_64 on openSUSE Leap 42.2 shows oversaturated thumbs
(perhaps not color managed properly) for images which are properly displayed
when viewed otherwise (after double clicking the thumb). It seems to happen for
images without color profile or with embedded sRGB profile.

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

[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error

[Cristian Aravena Romero]

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

--- Comment #18 from Cristian Aravena Romero  ---
Created attachment 106040
  --> https://bugs.kde.org/attachment.cgi?id=106040=edit
k3b log - Fail

caravena@caravena-530U3C-530U4C:/media/mis-doc/ISO/tmp$ dd if=/dev/zero
of=archivoX.txt bs=1024 count=4048576
4048576+0 registros leídos
4048576+0 registros escritos
4145741824 bytes (4,1 GB, 3,9 GiB) copied, 247,034 s, 16,8 MB/s



caravena@caravena-530U3C-530U4C:/media/mis-doc/ISO/tmp$ ls -lihsa
total 20G
74249 4,0K drwxrwx--- 1 root plugdev 4,0K jun 10 16:04 .
10828 8,0K drwxrwx--- 1 root plugdev 8,0K jun 10 16:09 ..
78259 3,9G -rwxrwx--- 1 root plugdev 3,9G jun 10 15:47 archivo1.txt
78858 3,9G -rwxrwx--- 1 root plugdev 3,9G jun 10 15:51 archivo2.txt
78859 3,9G -rwxrwx--- 1 root plugdev 3,9G jun 10 15:56 archivo3.txt
79568 3,9G -rwxrwx--- 1 root plugdev 3,9G jun 10 16:01 archivo4.txt
81161 3,9G -rwxrwx--- 1 root plugdev 3,9G jun 10 16:08 archivo5.txt



caravena@caravena-530U3C-530U4C:/media/mis-doc/ISO$ genisoimage -r -J -o
blu-ray.iso tmp
I: -input-charset not specified, using utf-8 (detected in locale settings)
  0.05% done, estimate finish Sat Jun 10 16:09:02 2017
  0.10% done, estimate finish Sat Jun 10 16:09:02 2017
  0.15% done, estimate finish Sat Jun 10 16:20:16 2017
  0.20% done, estimate finish Sat Jun 10 16:17:27 2017

[...]


 99.79% done, estimate finish Sat Jun 10 16:26:09 2017
 99.84% done, estimate finish Sat Jun 10 16:26:09 2017
 99.89% done, estimate finish Sat Jun 10 16:26:10 2017
 99.93% done, estimate finish Sat Jun 10 16:26:09 2017
 99.98% done, estimate finish Sat Jun 10 16:26:10 2017
Total translation table size: 0
Total rockridge attributes bytes: 589
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
10121621 extents written (19768 MB)



caravena@caravena-530U3C-530U4C:/media/mis-doc/ISO$ md5sum blu-ray.iso 
7d671d16ec304caf1d9a07eccd1133a3  blu-ray.iso

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

[kgeography] [Bug 381078] New: Scotlands capital edinburgh missing

[bugzilla_noreply]

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

Bug ID: 381078
   Summary: Scotlands capital edinburgh missing
   Product: kgeography
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aa...@kde.org
  Reporter: k.mal...@btinternet.com
CC: lauran...@free.fr
  Target Milestone: ---

Edinburgh is a Borough as well as being the Capital of Scotland, its Northern
border is the Firth of Forth, where it stretches from Portabello in the East,
where it meets East Lothian, to Cramond Island in the West where it meets West
Lothian. From the Forth it extends South through Gillmerton to its Southern
Border
with Midlothian.

Your map shows the Southern shore of the Forth Estuary, shows from West
Lothian, through Midlothian to East Lothian, with Midlothian dipping its toes
in the Forth.
at Leith.
on a par with placing Washington DC in Washington State

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

[plasmashell] [Bug 381077] New: Kwin crash while tray plasmoid settings were open

[Serge Pavlyuk]

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

Bug ID: 381077
   Summary: Kwin crash while tray plasmoid settings were open
   Product: plasmashell
   Version: 5.10.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: flo...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.1)

Qt Version: 5.9.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Current report was triggered when i was setting up weather tray.
Sometimes it happened with different tray settings, starts after last update.

The crash can be reproduced sometimes.

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

Thread 37 (Thread 0x7f782f744700 (LWP 18452)):
#0  0x7fba228c539d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fba23a0a0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fba277a68d8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fba277a6d3a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fba23a08cbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fba228bf297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fba2331d25f in clone () at /usr/lib/libc.so.6

Thread 36 (Thread 0x7f7830524700 (LWP 18451)):
#0  0x7fba29ba14f0 in __tls_get_addr () at /lib64/ld-linux-x86-64.so.2
#1  0x7fba23a07b46 in  () at /usr/lib/libQt5Core.so.5
#2  0x7fba23c3b60a in  () at /usr/lib/libQt5Core.so.5
#3  0x7fba1ded2e8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#4  0x7fba1ded38db in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fba1ded3acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#6  0x7fba23c3be9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#7  0x7fba23be221a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#8  0x7fba23a0440a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#9  0x7fba26b72645 in  () at /usr/lib/libQt5Qml.so.5
#10 0x7fba23a08cbd in  () at /usr/lib/libQt5Core.so.5
#11 0x7fba228bf297 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7fba2331d25f in clone () at /usr/lib/libc.so.6

Thread 35 (Thread 0x7f78caffe700 (LWP 23628)):
#0  0x7fba228c539d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fba23a0a0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fba277a68d8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fba277a6d3a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fba23a08cbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fba228bf297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fba2331d25f in clone () at /usr/lib/libc.so.6

Thread 34 (Thread 0x7f78cbfff700 (LWP 23569)):
#0  0x7fba233132bd in poll () at /usr/lib/libc.so.6
#1  0x7fba1ded39b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fba1ded3d42 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x7fb96a7bdf86 in  () at /usr/lib/libgio-2.0.so.0
#4  0x7fba1defb295 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fba228bf297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fba2331d25f in clone () at /usr/lib/libc.so.6

Thread 33 (Thread 0x7f78d7fff700 (LWP 23568)):
#0  0x7fba233132bd in poll () at /usr/lib/libc.so.6
#1  0x7fba1ded39b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fba1ded3acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fba1ded3b11 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fba1defb295 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fba228bf297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fba2331d25f in clone () at /usr/lib/libc.so.6

Thread 32 (Thread 0x7fb8e31db700 (LWP 7951)):
#0  0x7fba228c539d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fba23a0a0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fba277a68d8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fba277a6d3a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fba23a08cbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7fba228bf297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fba2331d25f in clone () at /usr/lib/libc.so.6

Thread 31 (Thread 0x7fb8e3fff700 (LWP 7698)):
#0  0x7fba228c539d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fba23a0a0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fba277a68d8 in  () at 

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

[jose luis m]

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

--- Comment #35 from jose luis m  ---
With previous versions (last months), when in present windows, filtering was
working. 
I had this from Frameworks, Plasmashell and Qt5 in my package cache:

plasma-workspace-5.10.0
plasma-workspace-5.9.5.1
plasma-workspace-5.9.4
frameworks 5.34 and 5.33
qt5-base-5.8.0 

Yesterday I updated my system, plasma-workspace and Qt5 got updated (Frameworks
didn't),  and filtering stopped working:
plasma-workspace-5.10.1
qt5-base-5.9.0

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

[amarok] [Bug 375981] Launching application fails

[Chouloute]

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

Chouloute  changed:

   What|Removed |Added

 CC||moice...@wanadoo.fr

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

[Breeze] [Bug 380508] Using the Breeze icon theme for LibreOffice results in small icons always being used even when large ones should be used--and are available (visible in Task Switcher with Large I

[Nate Graham]

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

--- Comment #3 from Nate Graham  ---
Reproduces with (K)Ubuntu's packages for LibreOffice and Breeze, so this isn't
an openSUSE-specific issue.

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

[kwin] [Bug 381076] New: Alt+Tab crashes KWin

[bugzilla_noreply]

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

Bug ID: 381076
   Summary: Alt+Tab crashes KWin
   Product: kwin
   Version: 5.10.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mafr...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.10.1)

Qt Version: 5.9.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-2-zen x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I pressed Alt+Tab to show the Window changer and it hung and crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8792a88840 (LWP 5001))]

Thread 11 (Thread 0x7f8753507700 (LWP 5026)):
#0  0x7f878b60039d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f878e9c3ac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f878e9c3b09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f878b5fa297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f87924c825f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f8754509700 (LWP 5024)):
#0  0x7f878b60039d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f875f4d971b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f875f4d9447 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f878b5fa297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f87924c825f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f8754d0a700 (LWP 5023)):
#0  0x7f878b60039d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f875f4d971b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f875f4d9447 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f878b5fa297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f87924c825f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f875cb81700 (LWP 5022)):
#0  0x7f878b60039d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f875f4d971b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f875f4d9447 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f878b5fa297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f87924c825f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f875d382700 (LWP 5021)):
#0  0x7f878b60039d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f875f4d971b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f875f4d9447 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f878b5fa297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f87924c825f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f875dd8a700 (LWP 5020)):
#0  0x7f878b60039d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f875f4d971b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f875f4d9447 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f878b5fa297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f87924c825f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f875e6d2700 (LWP 5019)):
#0  0x7f878b60039d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f875f4d971b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f875f4d9447 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f878b5fa297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f87924c825f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f876b64f700 (LWP 5017)):
#0  0x7f87924be396 in ppoll () at /usr/lib/libc.so.6
#1  0x7f878faac471 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f878faadb5e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f878fa5721a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f878f87940a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f878a30a645 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f878f87dcbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7f878b5fa297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f87924c825f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f8772a92700 (LWP 5005)):
#0  0x7f87924be396 in ppoll () at /usr/lib/libc.so.6
#1  0x7f878faac471 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f878faadb5e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f878fa5721a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  

[kwin] [Bug 381021] Allow arrow keys to navigate in Desktop Grid

[Kamil]

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

--- Comment #6 from Kamil  ---
(In reply to Jesse from comment #5)
> I'm also having this issue. The arrow keys stopped working for the 'present
> windows' effect too. I think this problem started after the 5.10.1 update. 
> 
> The qt packages were also updated, to 5.9. I'm not sure if that could be
> related.

Hey there Jessie!
I ensured whether it is not any planned resolution to remove that function
since Christoph marked that as the duplicate of the bug which was marked as a
wish. (Mine got too..)
Though the function is happily present in the newest unstable KDE Neon
Developer release.

I hope they'll sort that out soon..or it's been already solved in the packages
that haven't pulled out of testing repos (in my case, Arch's ones).
If it is not.. Well, one bug entry more will not overwhelm active KDE
developers.
Arrivederci!

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

[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"

[Cristian Aravena Romero]

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

Cristian Aravena Romero  changed:

   What|Removed |Added

Summary|Does not write image|[MATSHITA BD-MLT UJ240AS]
   |"debian-8.8.0-amd64-BD-1.is |Does not write image
   |o"  |"debian-8.8.0-amd64-BD-1.is
   ||o"

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

[Discover] [Bug 381075] New: Cannot search for Calibre in Discover

[bugzilla_noreply]

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

Bug ID: 381075
   Summary: Cannot search for Calibre in Discover
   Product: Discover
   Version: 5.10.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: avraham.ish.sha...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.1)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.8.0-54-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed:
searching "calibre". every time I search for calibre, Discover crashes. Other
searches perform as expected.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb72215f8c0 (LWP 2093))]

Thread 8 (Thread 0x7fb6a0ff9700 (LWP 2158)):
#0  0x7fb71e47969d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb7198966f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb719852e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb719853330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb71985349c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb71f0a675b in QEventDispatcherGlib::processEvents
(this=0x7fb68800f9e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fb71f0510ba in QEventLoop::exec (this=this@entry=0x7fb6a0ff8d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fb71ee80f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#8  0x7fb71ee85b48 in QThreadPrivate::start (arg=0x21199b0) at
thread/qthread_unix.cpp:368
#9  0x7fb71b90e6ba in start_thread (arg=0x7fb6a0ff9700) at
pthread_create.c:333
#10 0x7fb71e48982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fb6e3fff700 (LWP 2102)):
#0  0x7fb71ef2b229 in qt_clock_gettime (ts=,
clock=) at tools/qelapsedtimer_unix.cpp:109
#1  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#3  0x7fb71f0a43d9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7fb6dc002cd0) at kernel/qtimerinfo_unix.cpp:91
#4  0x7fb71f0a4945 in QTimerInfoList::timerWait (this=0x7fb6dc002cd0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#5  0x7fb71f0a5fac in timerSourcePrepareHelper (timeout=0x7fb6e3ffeb34,
src=) at kernel/qeventdispatcher_glib.cpp:132
#6  idleTimerSourcePrepare (source=, timeout=0x7fb6e3ffeb34) at
kernel/qeventdispatcher_glib.cpp:212
#7  0x7fb71985291d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fb7198532bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fb71985349c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fb71f0a675b in QEventDispatcherGlib::processEvents
(this=0x7fb6dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#11 0x7fb71f0510ba in QEventLoop::exec (this=this@entry=0x7fb6e3ffed00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#12 0x7fb71ee80f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#13 0x7fb71ee85b48 in QThreadPrivate::start (arg=0x2008b00) at
thread/qthread_unix.cpp:368
#14 0x7fb71b90e6ba in start_thread (arg=0x7fb6e3fff700) at
pthread_create.c:333
#15 0x7fb71e48982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fb6f252a700 (LWP 2099)):
#0  0x7fb719852da8 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb719853330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb71985349c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb71f0a675b in QEventDispatcherGlib::processEvents
(this=0x7fb6ec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb71f0510ba in QEventLoop::exec (this=this@entry=0x7fb6f2529d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fb71ee80f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fb71ee85b48 in QThreadPrivate::start (arg=0x1f87400) at
thread/qthread_unix.cpp:368
#7  0x7fb71b90e6ba in start_thread (arg=0x7fb6f252a700) at
pthread_create.c:333
#8  0x7fb71e48982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fb6fffd1700 (LWP 2098)):
#0  0x7fb71e47969d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb7198966f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb719852e74 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  

[k3b] [Bug 381074] Does not write image "debian-8.8.0-amd64-BD-1.iso"

[Cristian Aravena Romero]

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

--- Comment #2 from Cristian Aravena Romero  ---
Hello,

Download with jigdo:
http://cdimage.debian.org/debian-cd/current/amd64/jigdo-bd/

Regards,
--
Cristian

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

[k3b] [Bug 381074] Does not write image "debian-8.8.0-amd64-BD-1.iso"

[Cristian Aravena Romero]

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

Cristian Aravena Romero  changed:

   What|Removed |Added

Summary|No graba imagen |Does not write image
   |"debian-8.8.0-amd64-BD-1.is |"debian-8.8.0-amd64-BD-1.is
   |o"  |o"

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

[k3b] [Bug 381074] No graba imagen "debian-8.8.0-amd64-BD-1.iso"

[Cristian Aravena Romero]

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

--- Comment #1 from Cristian Aravena Romero  ---
Created attachment 106038
  --> https://bugs.kde.org/attachment.cgi?id=106038=edit
Empty BD-R medium

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

[k3b] [Bug 381074] New: No graba imagen "debian-8.8.0-amd64-BD-1.iso"

[Cristian Aravena Romero]

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

Bug ID: 381074
   Summary: No graba imagen "debian-8.8.0-amd64-BD-1.iso"
   Product: k3b
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: carav...@gmail.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

Created attachment 106037
  --> https://bugs.kde.org/attachment.cgi?id=106037=edit
Waiting for Disk -- K3b

Hi,

25GB DB-R insert and throw me that it does not have enough space to record.



== Information ==
$ls -lihsa debian-8.8.0-amd64-BD-1.iso
72751 22G -rwxrwx--- 1 root plugdev 22G jun 10 13:35
debian-8.8.0-amd64-BD-1.iso

http://cdimage.debian.org/debian-cd/current




Regards,
--
Cristian

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

[konversation] [Bug 378854] Konversation crashes randomly

[Peter Simonsson]

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

Peter Simonsson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kon
   ||versation/783dc0f595ecf90e3
   ||7225a57da0ffa2c030a470d
 Resolution|--- |FIXED

--- Comment #3 from Peter Simonsson  ---
Git commit 783dc0f595ecf90e37225a57da0ffa2c030a470d by Peter Simonsson.
Committed on 10/06/2017 at 18:41.
Pushed by psn into branch '1.7'.

Fix crash in join handling in inputfilter

Make sure to check size of parameter list for extended join.

M  +6-13   src/irc/inputfilter.cpp

https://commits.kde.org/konversation/783dc0f595ecf90e37225a57da0ffa2c030a470d

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

[k3b] [Bug 380909] Wrong app icon under plasma wayland session

[Dr . Chapatin]

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

--- Comment #9 from Dr. Chapatin  ---
Sorry for the noob question, but are packages from neon dev from ~git master~?
Here K3b has wrong icon on neon dev too.

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

[plasmashell] [Bug 381073] New: plasma crash while configuring desktop

[Rolf Pedersen]

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

Bug ID: 381073
   Summary: plasma crash while configuring desktop
   Product: plasmashell
   Version: 5.8.6
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rolfpeder...@mindspring.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.28-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

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

Setting up the plasma desktop on first boot after installation of Mageia6 RC,
configuring panel.

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

Thread 7 (Thread 0x7f758bc0c700 (LWP 7256)):
#0  0x7f763848b92d in read () at /lib64/libc.so.6
#1  0x7f763543a690 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f76353f679e in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f76353f6c38 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f76353f6d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f7638d98e1b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f7638d4448a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f7638b7e3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f763bd94902 in QQuickPixmapReader::run() () at
/lib64/libQt5Quick.so.5
#9  0x7f7638b82ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7f7637c8c66d in start_thread () at /lib64/libpthread.so.0
#11 0x7f763849be4d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f7615df8700 (LWP 7155)):
#0  0x7f7637c91c4f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f763d7fc234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f763d7fc279 in  () at /lib64/libQt5Script.so.5
#3  0x7f7637c8c66d in start_thread () at /lib64/libpthread.so.0
#4  0x7f763849be4d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f7617bbf700 (LWP 7057)):
#0  0x7f76353f5c5f in g_main_context_acquire () at /lib64/libglib-2.0.so.0
#1  0x7f76353f6b65 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f76353f6d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f7638d98e1b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f7638d4448a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f7638b7e3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f763b40f205 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f7638b82ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f7637c8c66d in start_thread () at /lib64/libpthread.so.0
#9  0x7f763849be4d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f76253de700 (LWP 7024)):
#0  0x7f7638d9826d in socketNotifierSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#1  0x7f76353f622d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f76353f6bc3 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f76353f6d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f7638d98e1b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f7638d4448a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f7638b7e3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f763b40f205 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7f7638b82ff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f7637c8c66d in start_thread () at /lib64/libpthread.so.0
#10 0x7f763849be4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f7626e23700 (LWP 7001)):
#0  0x7f763848b92d in read () at /lib64/libc.so.6
#1  0x7f763543a690 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f76353f679e in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f76353f6c38 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f76353f6d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f7638d98e1b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f7638d4448a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f7638b7e3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f763dee4635 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#9  0x7f7638b82ff9 in 

[kwin] [Bug 381021] Allow arrow keys to navigate in Desktop Grid

[Jesse]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse...@gmail.com

--- Comment #5 from Jesse  ---
I'm also having this issue. The arrow keys stopped working for the 'present
windows' effect too. I think this problem started after the 5.10.1 update. 

The qt packages were also updated, to 5.9. I'm not sure if that could be
related.

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

[plasmashell] [Bug 373819] "Open with file manager" action does not work with audio cd

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |k...@privat.broulik.de
 CC||k...@privat.broulik.de

--- Comment #8 from Kai Uwe Broulik  ---
I don't have a cd drive but I'll make a patch for kio-audiocd to call
kioclient5 instead, stay tuned.

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

[kwin] [Bug 381071] Compositing disabled on boot when any aurorae theme is chosen

[Alberto Mattea]

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

Alberto Mattea  changed:

   What|Removed |Added

 CC||albe...@mattea.info

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

[kipiplugins] [Bug 381026] Plugin piwigo not sort albums

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kip
   ||i-plugins/4296041b7cdf6a582
   ||b7029ca3639608f4a0539fa
 Resolution|--- |FIXED
   Version Fixed In||5.6.0

--- Comment #1 from Maik Qualmann  ---
Git commit 4296041b7cdf6a582b7029ca3639608f4a0539fa by Maik Qualmann.
Committed on 10/06/2017 at 18:05.
Pushed by mqualmann into branch 'master'.

enable sorting for the Piwigo album treeview
FIXED-IN: 5.6.0

M  +2-1NEWS
M  +2-0piwigo/piwigowindow.cpp

https://commits.kde.org/kipi-plugins/4296041b7cdf6a582b7029ca3639608f4a0539fa

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

[plasmashell] [Bug 373819] "Open with file manager" action does not work with audio cd

[Dr . Chapatin]

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

--- Comment #7 from Dr. Chapatin  ---
This bug is still present in plasma 5.10.1.

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

[calligrasheets] [Bug 381072] New: Crash after insert new row

[bugzilla_noreply]

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

Bug ID: 381072
   Summary: Crash after insert new row
   Product: calligrasheets
   Version: 2.9.11
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: calligra-sheets-bugs-n...@kde.org
  Reporter: n...@qakq.com
  Target Milestone: ---

Application: calligrasheets (2.9.11)
KDE Platform Version: 4.14.30
Qt Version: 4.8.7
Operating System: Linux 4.11.3-202.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

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

Typing into new row. Crash right after hypen was typed. This was repeated 3
times.

The crash can be reproduced every time.

-- Backtrace:
Application: Calligra Sheets (calligrasheets), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x0021 in  ()
#7  0x7fa999c7253f in Calligra::Sheets::StyleStorage::invalidateCache() ()
at /lib64/libcalligrasheetsodf.so.14
#8  0x7fa999c0dc98 in
Calligra::Sheets::Map::handleDamages(QList const&)
() at /lib64/libcalligrasheetsodf.so.14
#9  0x7fa9b6630090 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#10 0x7fa999c09482 in
Calligra::Sheets::Map::damagesFlushed(QList const&)
() at /lib64/libcalligrasheetsodf.so.14
#11 0x7fa999c0951c in Calligra::Sheets::Map::flushDamages() () at
/lib64/libcalligrasheetsodf.so.14
#12 0x7fa9b6635db1 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4
#13 0x7fa9b5732ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#14 0x7fa9b5739dcc in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#15 0x7fa9a3d08df5 in KoApplication::notify(QObject*, QEvent*) () at
/lib64/libkomain.so.14
#16 0x7fa9b661beed in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQtCore.so.4
#17 0x7fa9b661f556 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQtCore.so.4
#18 0x7fa9b664c2ee in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQtCore.so.4
#19 0x7fa9b0e96e52 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#20 0x7fa9b0e971d0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#21 0x7fa9b0e9727c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#22 0x7fa9b664c45e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#23 0x7fa9b57db5a6 in
QGuiEventDispatcherGlib::processEvents(QFlags)
() at /lib64/libQtGui.so.4
#24 0x7fa9b661a7bf in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#25 0x7fa9b661ab25 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#26 0x7fa9b6620779 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#27 0x7fa9a3fbd5a5 in kdemain () at
/usr/lib64/libkdeinit4_calligrasheets.so
#28 0x55af741f944a in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) ()
#29 0x55af741fa196 in handle_launcher_request(int, char const*) [clone
.isra.15] ()
#30 0x55af741faa27 in handle_requests(int) ()
#31 0x55af741f60df in main ()

The reporter indicates this bug may be a duplicate of or related to bug 376742.

Possible duplicates by query: bug 376742, bug 374407, bug 373743, bug 371910.

Reported using DrKonqi

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

[kwin] [Bug 377171] Clicking outside of any presented windows should show desktop

[Vishnu]

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

--- Comment #5 from Vishnu  ---
I have a scenario now, where this will help:

Say I do not use a 'Panel', and have lost of 'Widgets' on the desktop. Now, if
I also have lots of windows open, the only way as of now, to get to the
desktop, is to minimized all of my open windows.

But if this were implemented, it would be mcuh easier to do that.

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

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

[Mateusz]

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

--- Comment #34 from Mateusz  ---
This got even worse in 5.10.1 plasma version with KDE Frameworks 5.34.0 and Qt
5.9.0.
Restarting Plasmashell and Kwin does not help;(

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

[kwin] [Bug 381071] New: Compositing disabled on boot when any aurorae theme is chosen

[Alberto Mattea]

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

Bug ID: 381071
   Summary: Compositing disabled on boot when any aurorae theme is
chosen
   Product: kwin
   Version: 5.10.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: albe...@mattea.info
  Target Milestone: ---

Created attachment 106036
  --> https://bugs.kde.org/attachment.cgi?id=106036=edit
Support information

First of all, this started happening when I moved my installation on a faster
ssd (Samsung 960 pro), so I think it could be a race condition.
When I select any kind of aurorae theme for kwin, on every boot compositing is
disabled and the compositor kcm is opened automatically. I have to manually
enable compositing either with the keyboard shortcut or with said kcm. After
this, everything works normally. This does not happen with the breeze theme. I
can reproduce it with a fresh user too.

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

[plasmashell] [Bug 381070] New: Changing themes(and layout) leads to crash Also some windows are drawn with the old theme instead.

[bugzilla_noreply]

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

Bug ID: 381070
   Summary: Changing themes(and layout) leads to crash Also some
windows are drawn with the old theme instead.
   Product: plasmashell
   Version: 5.10.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: akarshan.bis...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.1)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.8.0-54-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed: Trying to change theme.
Sometimes plasma boots up to a black screen..

-- 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 0x7f9c1dfae8c0 (LWP 1554))]

Thread 8 (Thread 0x7f9b559fd700 (LWP 1678)):
#0  0x7f9c188e8b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9c1407e38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9c1407e49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9c1920875b in QEventDispatcherGlib::processEvents
(this=0x7f9b58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f9c191b30ba in QEventLoop::exec (this=this@entry=0x7f9b559fccc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f9c18fe2f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f9b57edb587 in KCupsConnection::run() () from
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#7  0x7f9c18fe7b48 in QThreadPrivate::start (arg=0x3fd0420) at
thread/qthread_unix.cpp:368
#8  0x7f9c17e8d6ba in start_thread (arg=0x7f9b559fd700) at
pthread_create.c:333
#9  0x7f9c188f482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f9b6988e700 (LWP 1661)):
#0  0x7f9c1407b3f5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9c1407d8bb in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9c1407e2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9c1407e49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9c1920875b in QEventDispatcherGlib::processEvents
(this=0x7f9b640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f9c191b30ba in QEventLoop::exec (this=this@entry=0x7f9b6988dc90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f9c18fe2f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f9c1bf9afc6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f9c18fe7b48 in QThreadPrivate::start (arg=0x1c93950) at
thread/qthread_unix.cpp:368
#9  0x7f9c17e8d6ba in start_thread (arg=0x7f9b6988e700) at
pthread_create.c:333
#10 0x7f9c188f482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f9bfa5a7700 (LWP 1660)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9c1d9ff6f4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f9c1d9ff739 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f9c17e8d6ba in start_thread (arg=0x7f9bfa5a7700) at
pthread_create.c:333
#4  0x7f9c188f482d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f9bfbfff700 (LWP 1659)):
#0  0x7ffecedf8a4a in clock_gettime ()
#1  0x7f9c18902c86 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f9bfbffea40) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f9c1908d241 in qt_clock_gettime (ts=0x7f9bfbffea40, clock=) at tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x7f9c192063d9 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f9bf0002ed0) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f9c19206945 in QTimerInfoList::timerWait (this=0x7f9bf0002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f9c19207d0e in timerSourcePrepareHelper (timeout=0x7f9bfbffeb14,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=, timeout=0x7f9bfbffeb14) at
kernel/qeventdispatcher_glib.cpp:165
#9  0x7f9c1407d91d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f9c1407e2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f9c1407e49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f9c1920875b in QEventDispatcherGlib::processEvents
(this=0x7f9bf8c0, 

[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error

[Leslie Zhai]

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

--- Comment #17 from Leslie Zhai  ---
Good news :)

> 
> Apparently I record well, now I'm going to do the test that Thomas asks:
> Burn an ISO image and then make a md5sum of the BD-R to see if it is
> correctly recorded.
> 
> Regards,
> --
> Cristian

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

[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error

[Cristian Aravena Romero]

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

--- Comment #16 from Cristian Aravena Romero  ---
(In reply to Leslie Zhai from comment #14)
> growisofs command:
> ---
> /usr/bin/growisofs ... -use-the-force-luke=spare=none
> 
> Then failed?

Apparently I record well, now I'm going to do the test that Thomas asks: Burn
an ISO image and then make a md5sum of the BD-R to see if it is correctly
recorded.

Regards,
--
Cristian

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

[plasmashell] [Bug 374651] Tray based app cannot run properly

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

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

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

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

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

[kdialog] [Bug 378227] KDialog scans all fonts directory before showing dialog box making it super slow

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

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

[frameworks-plasma] [Bug 381065] PlasmaComponents.ComboBox does not follow selected colorscheme

[Michail Vourlakos]

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

Michail Vourlakos  changed:

   What|Removed |Added

 CC||mvourla...@gmail.com

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

[kwin] [Bug 381045] Logout greeter gets title bar and breaks background view

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

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

[cantor] [Bug 379404] Cantor can't initialize session for maxima backend

[bugzilla_noreply]

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

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com
 Status|UNCONFIRMED |CONFIRMED
Version|unspecified |17.04
 Ever confirmed|0   |1

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

[plasmashell] [Bug 379888] [Feature Request] - Force the FolderView widget in CompactRepresentation when in panel

[Michail Vourlakos]

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

--- Comment #4 from Michail Vourlakos  ---
An update on this for Plasma 5.10, I have set panel icon size to 256px.  the
forlderview still changes its representation to file list at some point when it
is in the plasma panel

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

[amarok] [Bug 381069] New: amarok: position marker created at end of track every time "stop playing after this track" used

[bugzilla_noreply]

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

Bug ID: 381069
   Summary: amarok: position marker created at end of track every
time "stop playing after this track" used
   Product: amarok
   Version: 2.8.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: miss...@hotmail.com
  Target Milestone: 2.9

I am noticing Position Markers in many of my tracks which I did not place
myself. 

I mostly notice them in podcasts when I go back to listen to them again after
listening through and stopping at the end with the "Stop Playing After This
Track" option selected.

It is not only podcasts where I notice the markers, but I use "Stop Playing
After This Track" much less frequently on local collection songs.

I believe that "Stop Playing After This Track" is creating a Position Marker at
the end of the track every time when play is stopped.

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

[krita] [Bug 381067] Keyboard shortcuts not working

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

   Platform|Other   |Mac OS X Disk Images
 CC||b...@valdyas.org
 OS|Linux   |OS X

--- Comment #1 from Boudewijn Rempt  ---
Hi Niall,

I think I've heard other reports like this, but I cannot find them right now.
It seems it's actually a bug in the development framework, but I'm not sure
either...

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

[plasmashell] [Bug 381035] Plasmashell crashing when changing the location of the panel

[bugzilla_noreply]

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

--- Comment #1 from raist...@gmail.com ---
It still happens on 5.10.1

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

[kate] [Bug 381052] Path separator copied to clipboard should be original character

[Yuki]

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

--- Comment #2 from Yuki  ---
File path text is converted like following

D:\Downloads\desktop.ini  --->   D:/Downloads/desktop.ini

Text in clipboard doesn't contain file:// prefix

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

[gwenview] [Bug 381068] New: There are two actions (Ausschneiden, Löschen) that want to use the same shortcut (Umschalt+Entf). This is most probably a bug. Please report it in bugs.kde.org

[bugzilla_noreply]

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

Bug ID: 381068
   Summary: There are two actions (Ausschneiden, Löschen) that
want to use the same shortcut (Umschalt+Entf). This is
most probably a bug. Please report it in bugs.kde.org
   Product: gwenview
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: importer
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: fritz.ruess...@gmail.com
CC: myr...@kde.org
  Target Milestone: ---

There are two actions (Ausschneiden, Löschen) that want to use the same
shortcut (Umschalt+Entf). This is most probably a bug. Please report it in
bugs.kde.org 

Kubuntu 16.04

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

[kate] [Bug 381050] Keeping multiple backup files

[Yuki]

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

--- Comment #2 from Yuki  ---
Thank you for your comment.

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

[systemsettings] [Bug 378262] krdb/kcminit sets wrong font for Qt4 applications on login

[Wolfgang Bauer]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #8 from Wolfgang Bauer  ---
Same here on openSUSE with the latest Qt5, KF5 and Plasma.

KDE4 applications do use the font from KDE4's kdeglobals (which is correctly
synced), but plain Qt4 applications use the font specified in Trolltech.conf
(which gets set to "Sans Serif 9" on every login to Plasma5).

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

[krita] [Bug 381067] New: Keyboard shortcuts not working

[Niall]

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

Bug ID: 381067
   Summary: Keyboard shortcuts not working
   Product: krita
   Version: 3.1.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: shortcuts
  Assignee: krita-bugs-n...@kde.org
  Reporter: manofthe...@tutanota.com
  Target Milestone: ---

Hi,

Got an issue with the following application involving the pan function. It does
not seem to work in certain circumstances.

Application - Krita 3.1.4 
System - Mac OS X (El Capitan Ver.10.11.6)

Bug Reproduction
-

I've got the keyboard shortcut scheme set to emulate Photoshop via the
preferences. So in this instance, the pan function is set to the space bar.

I have the brush tool selected. 

If I zoom (Cmd + '+/-') in or out of the canvas, then click on the canvas, the
pan function works correctly. 

If I zoom in or out, then immediately press space bar to pan, it doesn't work,
regardless if I have the mouse cursor over the canvas or not. 

This also applies to the colour spot tool, pressing (Cmd) whilst brush tool is
selected.

In some circumstances however, clicking on the canvas does not resolve bug, I
either need to click on the UI (Layer, brush, colour palette, etc.) Or pressing
(Ctrl +Tab).

It's a small bug, but one that impedes my workflow quite considerably! X_X;;

Hope this info helps. If you require any further info from me, give me a shout.

Cheers.

Niall

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

[plasmashell] [Bug 380495] Freezes during login process

[bugzilla_noreply]

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

--- Comment #3 from yy.y.ja...@gmail.com ---
Here is some additional info for more clarity:

Actually the attached patch just changes ksplashqml to simulate pre-5.3.90
behavior, where it does not emit log anywhere (because it had closed all the
file descriptors). The only difference is that SplashApp's file descriptors 0,
1 and 2 are open during its initialization phase.

The ksplashqml's caller is /usr/bin/startkde (symlinked by
/usr/bin/x-session-manager in a fresh Debian KDE desktop installation), at line
187:
> ksplash_pid=`ksplashqml "${ksplashrc_ksplash_theme}" --pid`
The caller hangs at this point. As in the previous comment it is reading file
descriptor 3, which is apparently the stdout of the ksplashqml process, and is
waiting forever, which means the pipe is not closed and is empty. The pipe's
file descriptor (writer side) is shared through fork. A small main.c and small
caller script attached are a minimal example of the situation.
The caller expects that ksplashqml with "--pid" option emit the pid string of
its forked process and immediately exit. In reality the ksplashqml process
emits the string, but its forked process also holds the pipe and does not
close. Thus it hangs. The forked process must not write anything to the pipe,
otherwise the caller reads it after the (expected) pid string. So in order to
only fix the problem closing (replacing) stdout should suffice.

ksplashqml splash app is a qt5 QGuiApplication, which by default loads
QPlatformInputContext (input method) plugins. This is why ksplashqml launches
an input method system.

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

[plasmashell] [Bug 380495] Freezes during login process

[bugzilla_noreply]

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

--- Comment #2 from yy.y.ja...@gmail.com ---
Created attachment 106035
  --> https://bugs.kde.org/attachment.cgi?id=106035=edit
an example launcher script for the app to illustrate the hang situation

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

[plasmashell] [Bug 380495] Freezes during login process

[bugzilla_noreply]

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

--- Comment #1 from yy.y.ja...@gmail.com ---
Created attachment 106034
  --> https://bugs.kde.org/attachment.cgi?id=106034=edit
an example app to illustrate the hang situation

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

[krita] [Bug 381012] bug in popup palette color

[Tomasz]

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

--- Comment #2 from Tomasz  ---
I didn`t cheked the line because I don`t know how. I asked my friend but he
didn`t answer yet. I send you a short movie with first problem. It shows
better then screenshot. When I will check line I will send you another mail
and attach second film with second problem witch I descriped in raport,
maybe corresponding to this bug.

greetings

2017-06-09 13:43 GMT+02:00 Boudewijn Rempt :

> https://bugs.kde.org/show_bug.cgi?id=381012
>
> Boudewijn Rempt  changed:
>
>What|Removed |Added
> 
> 
>  CC||b...@valdyas.org
>  Resolution|--- |WAITINGFORINFO
>  Status|UNCONFIRMED |NEEDSINFO
>
> --- Comment #1 from Boudewijn Rempt  ---
> Check whether your kritarc contains a line
>
> popuppalette/usevisualcolorselector=true
>
> Because this sounds like you've got the new color selector, not the default
> one. Also, please attach a screenshot to the bug so I can verify which
> color
> selector is enabled.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

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

[codywohlers]

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

codywohlers  changed:

   What|Removed |Added

 CC||k...@codywohlers.ca

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

[konversation] [Bug 381066] New: Konversation crashes with a segmentation fault

[Fabian Niepelt]

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

Bug ID: 381066
   Summary: Konversation crashes with a segmentation fault
   Product: konversation
   Version: 1.7.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: bugs...@takios.de
  Target Milestone: ---

Application: konversation (1.7.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
Started Konversation. Automatically connected to snoonet and freenode. Joined 2
rooms on snoonet and 3 rooms on freenode. Did not send a message, only read.

I have no specific action that triggers the crash, it can happen while writing
or not doing anything with the application at.

I reported the bug at my distribution's bugtracker
(https://bugzilla.opensuse.org/show_bug.cgi?id=1041130) and was advised to
report this behaviour upstream.

The crash can be reproduced every time.

-- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7d77251100 (LWP 13620))]

Thread 10 (Thread 0x7f7d3fae0700 (LWP 13632)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ddcb115c00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55ddcb115bb0,
cond=0x55ddcb115bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55ddcb115bd8, mutex=0x55ddcb115bb0) at
pthread_cond_wait.c:655
#3  0x7f7d4a4b52fb in cnd_wait (mtx=0x55ddcb115bb0, cond=0x55ddcb115bd8) at
../../include/c11/threads_posix.h:159
#4  util_queue_thread_func (input=input@entry=0x55ddcafe0500) at u_queue.c:158
#5  0x7f7d4a4b5037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7f7d6e4844e7 in start_thread (arg=0x7f7d3fae0700) at
pthread_create.c:456
#7  0x7f7d6ff61a2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 9 (Thread 0x7f7d402e1700 (LWP 13631)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ddcb115c00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55ddcb115bb0,
cond=0x55ddcb115bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55ddcb115bd8, mutex=0x55ddcb115bb0) at
pthread_cond_wait.c:655
#3  0x7f7d4a4b52fb in cnd_wait (mtx=0x55ddcb115bb0, cond=0x55ddcb115bd8) at
../../include/c11/threads_posix.h:159
#4  util_queue_thread_func (input=input@entry=0x55ddcb01cc80) at u_queue.c:158
#5  0x7f7d4a4b5037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7f7d6e4844e7 in start_thread (arg=0x7f7d402e1700) at
pthread_create.c:456
#7  0x7f7d6ff61a2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 8 (Thread 0x7f7d40ae2700 (LWP 13630)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ddcb115c00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55ddcb115bb0,
cond=0x55ddcb115bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55ddcb115bd8, mutex=0x55ddcb115bb0) at
pthread_cond_wait.c:655
#3  0x7f7d4a4b52fb in cnd_wait (mtx=0x55ddcb115bb0, cond=0x55ddcb115bd8) at
../../include/c11/threads_posix.h:159
#4  util_queue_thread_func (input=input@entry=0x55ddcb08bd20) at u_queue.c:158
#5  0x7f7d4a4b5037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7f7d6e4844e7 in start_thread (arg=0x7f7d40ae2700) at
pthread_create.c:456
#7  0x7f7d6ff61a2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 7 (Thread 0x7f7d412e3700 (LWP 13629)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ddcb115c00) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55ddcb115bb0,
cond=0x55ddcb115bd8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55ddcb115bd8, mutex=0x55ddcb115bb0) at
pthread_cond_wait.c:655
#3  0x7f7d4a4b52fb in cnd_wait (mtx=0x55ddcb115bb0, cond=0x55ddcb115bd8) at
../../include/c11/threads_posix.h:159
#4  util_queue_thread_func (input=input@entry=0x55ddcafe0500) at u_queue.c:158
#5  0x7f7d4a4b5037 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7f7d6e4844e7 in start_thread (arg=0x7f7d412e3700) at
pthread_create.c:456
#7  0x7f7d6ff61a2f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f7d41ce9700 (LWP 13628)):
#0  0x7f7d6e48a5ed in futex_wait_cancelable (private=,
expected=0, 

[kde] [Bug 381064] The shortcut Ctrl + D and Ctrl + S DOES NOT work

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
... while typing D, S

Do not confuse me :)

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

[kde] [Bug 381064] The shortcut Ctrl + D and Ctrl + S DOES NOT work

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
It says "Alt", not "Ctrl", and you need to keep "Alt" pressed why typing S, D

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

[kmail2] [Bug 376156] Deleting messages in IMAP account with server side folders enabled isn't possible

[Sebastian Held]

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

Sebastian Held  changed:

   What|Removed |Added

 CC||sebastian.h...@gmx.de

--- Comment #6 from Sebastian Held  ---
I have the same problem.
Comment 5 provides a workaround that works.

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

[frameworks-plasma] [Bug 381065] PlasmaComponents.ComboBox does not follow selected colorscheme

[Patrick Auernig]

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

--- Comment #2 from Patrick Auernig  ---
Created attachment 106033
  --> https://bugs.kde.org/attachment.cgi?id=106033=edit
Dropdown with light plasma theme and colorscheme

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

[frameworks-plasma] [Bug 381065] PlasmaComponents.ComboBox does not follow selected colorscheme

[Patrick Auernig]

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

--- Comment #1 from Patrick Auernig  ---
Created attachment 106032
  --> https://bugs.kde.org/attachment.cgi?id=106032=edit
Dropdown with light plasma theme and dark colorscheme

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

[digikam] [Bug 379855] QtAV is not detected but assumed present on MacOS [patch]

[bugzilla_noreply]

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

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

   What|Removed |Added

  Latest Commit||https://commits.kde.org/dig
   ||ikam/022278cad5dd4707565ec2
   ||12d171f8fe58f9e11d
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.6.0

--- Comment #1 from caulier.gil...@gmail.com ---
Git commit 022278cad5dd4707565ec212d171f8fe58f9e11d by Gilles Caulier.
Committed on 10/06/2017 at 14:22.
Pushed by cgilles into branch 'master'.

Apply patch from Rene about to improve QtAV detection under MacOS
FIXED-IN: 5.6.0

M  +1-2NEWS
M  +21   -2cmake/modules/FindQtAV.cmake

https://commits.kde.org/digikam/022278cad5dd4707565ec212d171f8fe58f9e11d

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

[frameworks-plasma] [Bug 381065] New: PlasmaComponents.ComboBox does not follow selected colorscheme

[Patrick Auernig]

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

Bug ID: 381065
   Summary: PlasmaComponents.ComboBox does not follow selected
colorscheme
   Product: frameworks-plasma
   Version: 5.34.0
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: patrick.auer...@gmail.com
  Target Milestone: ---

Created attachment 106031
  --> https://bugs.kde.org/attachment.cgi?id=106031=edit
Dropdown with dark plasma theme and colorscheme (Latte Dock)

Dropdown elements do not use the correct colorscheme.

It appears that it always falls back to some default scheme instead of applying
the correct one (in this case Breeze Dark).

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