[kdenlive] [Bug 380044] New: speed effect - timeline and add clip bugs

[Vic]

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

Bug ID: 380044
   Summary: speed effect - timeline and add clip bugs
   Product: kdenlive
   Version: 17.04.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: v...@dodo.com.au
  Target Milestone: ---

Hi.
Have found that speed change effect applied to a clip is not retained when
moving the clip in the time line. Not sure if it only happens when that clip is
moved together with other clips selected also.

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

[Discover] [Bug 380043] discover freezes till all updates/packages are installed . should also show progress bar

[bugzilla_noreply]

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

kehar...@gmx.com changed:

   What|Removed |Added

 CC||kehar...@gmx.com

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

[Discover] [Bug 380043] New: discover freezes till all updates/packages are installed . should also show progress bar

[bugzilla_noreply]

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

Bug ID: 380043
   Summary: discover freezes till all updates/packages are
installed . should also show progress bar
   Product: Discover
   Version: 5.9.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: kehar...@gmx.com
  Target Milestone: ---

Created attachment 105655
  --> https://bugs.kde.org/attachment.cgi?id=105655=edit
plasma addons section in DISCOVER. the icon themes& icons section take ages to
populate and sometimes fail to do so completely

1)in the discover software centre if i click to install updates etc i just get
an installing dialog. the progress bars freeze as well as the whole discover
app. it only unfreezes after all programs have stopped
updating/installing.there is no way to see progress or time remaining or to do
anything else in the app. 

2) when clicking on icons or icon themes in discover application in PLASMA
addons it takes a LONG time for the themes options to load. sometimes they dont
even load at all. pls see screenshot of what im referring to

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

[krusader] [Bug 380042] Calculate dir size option disappeared

[bugzilla_noreply]

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

owe...@gmail.com changed:

   What|Removed |Added

  Component|disk-usage  |general

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

[krusader] [Bug 380042] New: Calculate dir size option disappeared

[bugzilla_noreply]

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

Bug ID: 380042
   Summary: Calculate dir size option disappeared
   Product: krusader
   Version: 2.6.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: disk-usage
  Assignee: m...@fork.pl
  Reporter: owe...@gmail.com
  Target Milestone: ---

'Calculate dir size by pressing space' option disappeared. 

Steps to reproduce:

1. Click on dir
2. Press space
3. Nothing happens

Expected results
1. Click on dir
2. Press space
3. Dir size calculated

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

[gwenview] [Bug 379194] Ambiguous Shortcuts - gwenview Cut and Remove -> Shift+Del

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #5 from Christoph Feck  ---


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

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

[gwenview] [Bug 377880] Gwenview There are two actions (Cut, Delete)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||gurge...@gmail.com

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

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

[gwenview] [Bug 380041] Key bindings duplicate

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[gwenview] [Bug 379823] Message to cut and delete when opening image

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---


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

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

[gwenview] [Bug 377880] Gwenview There are two actions (Cut, Delete)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||muhl...@gmail.com

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

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

[gwenview] [Bug 377880] Gwenview There are two actions (Cut, Delete)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||caynannu...@gmail.com

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

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

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

[Thomas Murach]

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

Thomas Murach  changed:

   What|Removed |Added

 CC||asiasuppenes...@gmx.de

--- Comment #68 from Thomas Murach  ---
Same issue here (KOrganizer 5.5.1, OpenSuse 42.2, KDE Frameworks 5.34.0).
It would be very nice to see this fixed. Thanks in advance!

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

[gwenview] [Bug 380041] New: Key bindings duplicate

[Julián Muhlberger]

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

Bug ID: 380041
   Summary: Key bindings duplicate
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: muhl...@gmail.com
CC: myr...@kde.org
  Target Milestone: ---

Created attachment 105654
  --> https://bugs.kde.org/attachment.cgi?id=105654=edit
message at program start

When I start Gwenview I get a message warning me about a duplicity on Shift+Del
key binding for the cut and delete actions.
I attach a picture.

Gwenview version is 16.04

OS ver: Linux Mint 18.1 Serena

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

[dolphin] [Bug 380009] Pictures file repeats any picture interminably for ever paralyzing the whole computer.

[bugzilla_noreply]

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

--- Comment #4 from diazbeat...@gmail.com ---
Hi, Elvis,
When I open the Application Launcher, I go to Applications, then to File
Manager, next to diazbeat-Dolphin, then to Pictures and it is there when
the mess is done. When I started the computer today the front page was the
repetition of the picture folder many, many times. I tried to turn it off
many times and at some point I could control it but the picture exist
repeated many times and it is worse. I don't know if I responded your
question.
Thank you so much,
Beatriz

On Sat, May 20, 2017 at 1:03 AM, Elvis Angelaccio 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=380009
>
> --- Comment #3 from Elvis Angelaccio  ---
> Thanks for the reply. Which program is being used to open the pictures?
> (right-click the file and check the first entry of the "Open With"
> sub-menu)
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[valgrind] [Bug 322935] disInstr(arm): unhandled instruction: 0xF1010200, valgrind: Unrecognised instruction on Raspbian

[Graham Leggett]

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

Graham Leggett  changed:

   What|Removed |Added

 CC||minf...@sharp.fm

--- Comment #38 from Graham Leggett  ---
Having smashed headlong into this issue yet again, I have raised the following
issue in an effort to get the RPi people to fix this bug:

https://github.com/RPi-Distro/repo/issues/68

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

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

[Graham Leggett]

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

--- Comment #4 from Graham Leggett  ---
Turned out the session I was using to run valgrind had libasan preloaded with
LD_PRELOAD, and this turns AddressSanitizer on and triggers this crash.

Removing LD_PRELOAD produces the next crash, this time in valgrind:

vex: priv/guest_arm_toIR.c:13352 (decode_V8_instruction): Assertion `szBlg2 <=
3' failed.
vex storage: T total 243148328 bytes allocated
vex storage: P total 0 bytes allocated

valgrind: the 'impossible' happened:
   LibVEX called failure_exit().

Looks like this is this bug:

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

Building bleeding edge valgrind to see if that will get further...

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

[plasmashell] [Bug 380040] Can't get plasma (wayland) to start because of a fatal error

[Munzir Taha Obeid]

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

Munzir Taha Obeid  changed:

   What|Removed |Added

 CC||munzirt...@gmail.com
   Platform|Other   |Archlinux Packages

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

[plasmashell] [Bug 380039] New: Plasma crashed when I was browsing (in Opera)

[Piotr Mierzwinski]

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

Bug ID: 380039
   Summary: Plasma crashed when I was browsing (in Opera)
   Product: plasmashell
   Version: 5.9.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: piotr.mierzwin...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.5)

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

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

Plasma crashed when I was browsing (in Opera).
Maybe it was only coincidence, but I only clicked in Opera "hide comments this
user" (on website https://www.dobreprogramy.pl) and confirmed that all.

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

Thread 10 (Thread 0x7f976936a700 (LWP 4506)):
#0  0x7f98444fc67d in poll () at /usr/lib/libc.so.6
#1  0x7f983f2d39b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f983f2d3acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9844e2309b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9844dcc8ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9844beea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9847d27025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f9844bf36d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9843aa82e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f984450654f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f9788e99700 (LWP 1016)):
#0  0x7f98444fc67d in poll () at /usr/lib/libc.so.6
#1  0x7f983f2d39b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f983f2d3acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9844e2309b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9844dcc8ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9844beea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9844bf36d8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9843aa82e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f984450654f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f978969a700 (LWP 1015)):
[KCrash Handler]
#6  0x7f98da10 in raise () at /usr/lib/libc.so.6
#7  0x7f98f13a in abort () at /usr/lib/libc.so.6
#8  0x7f984448c2b0 in __libc_message () at /usr/lib/libc.so.6
#9  0x7f984449290e in malloc_printerr () at /usr/lib/libc.so.6
#10 0x7f9844494d61 in _int_malloc () at /usr/lib/libc.so.6
#11 0x7f9844496674 in malloc () at /usr/lib/libc.so.6
#12 0x7f9844bf490c in QArrayData::allocate(unsigned long, unsigned long,
unsigned long, QFlags) () at
/usr/lib/libQt5Core.so.5
#13 0x7f9844c71446 in QString::QString(QChar const*, int) () at
/usr/lib/libQt5Core.so.5
#14 0x7f9844c760f5 in QString::left(int) const () at
/usr/lib/libQt5Core.so.5
#15 0x7f9844d2ecf9 in  () at /usr/lib/libQt5Core.so.5
#16 0x7f9844d26798 in QUrl::setUrl(QString const&, QUrl::ParsingMode) () at
/usr/lib/libQt5Core.so.5
#17 0x7f97897601bc in QXmlQuery::bindVariable(QXmlName const&, QIODevice*)
() at /usr/lib/libQt5XmlPatterns.so.5
#18 0x7f97897603e1 in QXmlQuery::bindVariable(QString const&, QIODevice*)
() at /usr/lib/libQt5XmlPatterns.so.5
#19 0x7f9789c941b8 in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#20 0x7f9789c95627 in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#21 0x7f9789c96160 in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#22 0x7f9789c9631d in  () at
/usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#23 0x7f9845d3c34c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#24 0x7f9845d43b61 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#25 0x7f9844dce470 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#26 0x7f9844dd0bfd in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#27 0x7f9844e22c73 in  () at /usr/lib/libQt5Core.so.5
#28 0x7f983f2d37b7 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#29 0x7f983f2d3a20 in  () at /usr/lib/libglib-2.0.so.0
#30 0x7f983f2d3acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#31 0x7f9844e2307f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5

[plasmashell] [Bug 380040] New: Can't get plasma (wayland) to start because of a fatal error

[Munzir Taha Obeid]

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

Bug ID: 380040
   Summary: Can't get plasma (wayland) to start because of a fatal
error
   Product: plasmashell
   Version: 5.9.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: munzirt...@gmail.com
  Target Milestone: 1.0

Created attachment 105652
  --> https://bugs.kde.org/attachment.cgi?id=105652=edit
journalctl -ab

When I try to login via sddm, I get black screen. journalctl shows this error:

plasmashell[815]: The Wayland connection experienced a fatal error (Protocol
error)

Tried a nested setup:
$ export $(dbus-launch)
$ kwin_wayland --xwayland
No backend specified through command line argument, trying auto resolution
kwin_core: choose config failed
kwin_core: Creating egl surface failed
kwin_core: Failed to initialize compositing, compositing disabled
kwin_core: The used windowing system requires compositing
kwin_core: We are going to quit KWin now as it is broken
Segmentation fault (core dumped)

My hardware is the HP Spectre 15" with intel/nvidia
> lspci -nn
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916]
(rev 02)
00:13.0 Non-VGA unclassified device []: Intel Corporation Device
[8086:9d35] (rev 21)
01:00.0 3D controller [0302]: NVIDIA Corporation GM108M [GeForce 940MX]
[10de:134d] (rev ff)

However, my nvidia is disabled as can be verified by:
> cat /proc/acpi/bbswitch 
:01:00.0 OFF


The full journalctl log is attached

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

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

[Graham Leggett]

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

--- Comment #3 from Graham Leggett  ---
Having completely rebuilt both gstreamer git-master and valgrind v3.12.0 from
source using gcc v6.20 with AddressSanitizer disabled, I am still getting the
same error:

==26049== 
==26049==ASan runtime does not come first in initial library list; you should
either link runtime to your application or manually preload it with LD_PRELOAD.
==26049== Jump to the invalid address stated on the next line
==26049==at 0x0: ???
==26049==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==26049== 
==26049== 
==26049== Process terminating with default action of signal 11 (SIGSEGV)
==26049==  Bad permissions for mapped region at address 0x0
==26049==at 0x0: ???
==26049== 
==26049== HEAP SUMMARY:
==26049== in use at exit: 0 bytes in 0 blocks
==26049==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==26049== 
==26049== All heap blocks were freed -- no leaks are possible
==26049== 
==26049== For counts of detected and suppressed errors, rerun with: -v
==26049== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

Is there any mechanism to switch off AddressSanitizer, or at least get valgrind
to coexist peacefully with AddressSanitizer on modern compilers?

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

[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland

[bugzilla_noreply]

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

--- Comment #6 from djmcbrat...@gmail.com ---
Again, I don't think I'm arguing with your priorities, and it sounds like
Wayland support will come when it becomes necessary (at some juncture after
some number of those developers are using Wayland systems.) I can understand
why something that's still somewhat prospective like this isn't a priority for
a fairly small development team. In any case, thanks for the information.

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

[kmymoney4] [Bug 249844] wrong memo field after duplicating and editing transaction

[Christian David]

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

Christian David  changed:

   What|Removed |Added

   Version Fixed In|5.0 |4.8.1

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

[kmymoney4] [Bug 378379] Segfault if a Report is deleted from reports menu whilst it is open in a tab.

[Christian David]

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

Christian David  changed:

   What|Removed |Added

   Version Fixed In|5.0 |4.8.1

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

[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland

[Boudewijn Rempt]

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

--- Comment #5 from Boudewijn Rempt  ---
I'm not the only person working on Krita, but there's nobody who is working on
Krita who has a wayland system. If people want krita to work on Wayland, they
have to do the work to make Krita work on Wayland; until there is someone who
cares both about wayland and about krita, no work will happen.

I am, more or less, the only developer regularly checking bugzilla. I don't use
wayland, not with kwin, not with gnome; wayland right now is something that
might be relevant in the future, it's not relevant right now. Nobody is going
to make better art, or make art quicker, or have more fun making art because
their system is using wayland: that means that people who care about wayland
need to do work.

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

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

[Tom Hughes]

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

--- Comment #2 from Tom Hughes  ---
By the way the specific problem you're seeing here is that asan is trying to
make sure it's intercepting malloc etc but of course valgrind also wants to do
the same thing and they can't both do so.

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

[valgrind] [Bug 380037] valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD

[Tom Hughes]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #1 from Tom Hughes  ---
Using valgrind and asan together is never likely to work anyway. I haven't seen
that error before but usually it falls over because the address space
manipulation each tries to do is incompatible.

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

[plasma4] [Bug 380038] New: Unrecognized program names.

[jose caynan]

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

Bug ID: 380038
   Summary: Unrecognized program names.
   Product: plasma4
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panel
  Assignee: plasma-b...@kde.org
  Reporter: caynannu...@gmail.com
  Target Milestone: ---

Created attachment 105651
  --> https://bugs.kde.org/attachment.cgi?id=105651=edit
Screen print

>From time to time this happens, the names of the program's menu and some
functions are unrecognizable, but not all of them are appended. Just what the
user sees.

My operating system is:
Linux mint 18.1 x64 KDE: 4.14.22

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

[kdenlive] [Bug 380035] use GLSL compositing/dissolve/zoom by default when GLSL is enabled

[Anton Gubarkov]

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

--- Comment #1 from Anton Gubarkov  ---
Side note. The rendering (with manual compositing and GLSL overlay, GLSL wipe,
GLSL pan/zoom, GLSL white balance transitions/effects only) produces max 20 fps
(from render log measuring). I tested it on both VAAPI and NVENC encoders. Both
are capable of over 90 fps encoding - ie encoder is not a bottleneck.

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

[kdenlive] [Bug 355824] kdenlive-15.08.03 composite transition broken on GPU rendering (does dissolve instead)

[Anton Gubarkov]

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

Anton Gubarkov  changed:

   What|Removed |Added

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

--- Comment #6 from Anton Gubarkov  ---
The compositing has changed a lot. This bug is no longer applicable

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

[kwin] [Bug 380005] Not detecting Windows Edge on first try

[richardlm]

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

--- Comment #4 from richardlm  ---
(In reply to Martin Flöser from comment #3)
> Does it make a difference whether the window is maximized?

Yes, if the windows starts up maximized it always seems to work on first try.

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

[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland

[bugzilla_noreply]

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

--- Comment #4 from djmcbrat...@gmail.com ---
I don't understand. Are you saying that you're the only person presently
working on Krita, and that Krita is not targeting Wayland in the foreseeable
future? Because that's an answer to both the original question and mine. 

I didn't question (or mention) anyone's priorities, but perhaps I was a bit
unclear in distinguishing the two separate possibilities I was considering
there. If this was exclusively a GNOME problem, that'd be unfortunate from my
perspective. If it was a Krita / Wayland problem, I would have guessed that
someone would have been looking into it, but I'm not making an argument for
that here, I simply assumed that would probably be the case. I do also
understand that Wayland support in KDE Plasma is just now becoming available,
while it's beginning to be the default in GNOME systems. 

In any case, so far as I can tell, tablet input does not seem to function at
all through xwayland in GNOME (the pointer disappears when it enters a xwayland
app and moves the window if dragged), and Krita appears to be running as an
xwayland window. 

I'm well aware that I can just use X, which is (naturally) how I'm using Krita
at present.

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

[valgrind] [Bug 380037] New: valgrind + AddressSanitizer: ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PR

[Graham Leggett]

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

Bug ID: 380037
   Summary: valgrind + AddressSanitizer: ASan runtime does not
come first in initial library list; you should either
link runtime to your application or manually preload
it with LD_PRELOAD.
   Product: valgrind
   Version: 3.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: minf...@sharp.fm
  Target Milestone: ---

When trying to run valgrind on a binary that has been built linked to
AddressSanitizer, valgrind immediately crashes at startup with a SIGSEGV as
below.

It appears whatever valgrind does to the LD_PRELOAD environment variable breaks
AddressSanitizer, which then causes valgrind to crash.

minfrin@towerofpi9:/var/www/html/stream$ GST_LEAKS_TRACER_STACK_TRACE=1
GST_LEAKS_TRACER_SIG=1 ASAN_OPTIONS=atexit=1
GST_TRACERS="leaks(stack-traces-flags=full,filters=GstMemory,check-refs=true)"
GST_DEBUG_DUMP_DOT_DIR=. G_DEBUG="fatal-warnings"
LD_PRELOAD=/usr/local/gcc-6.2.0/lib/libasan.so.3
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/gcc-6.2.0/lib
/tmp/valgrind/bin/valgrind gst-launch-1.0 --gst-debug-no-color
--gst-debug=1,GST_TRACER:7,GST_REFCOUNTING:0,GST_PADS:1,GST_STATES:5,tdttsparse:5,tsdemux:1,omx:1,omxvideo:1,omxvideodec:1,omxh264dec:1,omxvideoenc:1,omxh264enc:1,videoencoder:1,videorate:1,videoscale:1,mpegtsmux:4,decodebin:1,encodebin:1,h264parse:1,transcoder:5,hlssink:5
udpsrc multicast-iface=eth0 uri=udp://239.106.0.0:1234
"caps=application/x-rtp,media=(string)video,clock-rate=(int)9" ! rtpbin !
rtpmp2tdepay ! progressreport update-freq=5 ! transcoder name=transcoder !
capsfilter caps=audio/x-raw ! fakesink   transcoder. ! capsfilter
caps=video/mpegts ! hlssink target-duration=0transcoder. ! capsfilter
caps=audio/x-raw ! fakesink
==4810== Memcheck, a memory error detector
==4810== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==4810== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==4810== Command: gst-launch-1.0 --gst-debug-no-color
--gst-debug=1,GST_TRACER:7,GST_REFCOUNTING:0,GST_PADS:1,GST_STATES:5,tdttsparse:5,tsdemux:1,omx:1,omxvideo:1,omxvideodec:1,omxh264dec:1,omxvideoenc:1,omxh264enc:1,videoencoder:1,videorate:1,videoscale:1,mpegtsmux:4,decodebin:1,encodebin:1,h264parse:1,transcoder:5,hlssink:5
udpsrc multicast-iface=eth0 uri=udp://239.106.0.0:1234
caps=application/x-rtp,media=(string)video,clock-rate=(int)9 ! rtpbin !
rtpmp2tdepay ! progressreport update-freq=5 ! transcoder name=transcoder !
capsfilter caps=audio/x-raw ! fakesink transcoder. ! capsfilter
caps=video/mpegts ! hlssink target-duration=0 transcoder. ! capsfilter
caps=audio/x-raw ! fakesink
==4810== 
==4810==ASan runtime does not come first in initial library list; you should
either link runtime to your application or manually preload it with LD_PRELOAD.
==4810== Jump to the invalid address stated on the next line
==4810==at 0x0: ???
==4810==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==4810== 
==4810== 
==4810== Process terminating with default action of signal 11 (SIGSEGV)
==4810==  Bad permissions for mapped region at address 0x0
==4810==at 0x0: ???
==4810== 
==4810== HEAP SUMMARY:
==4810== in use at exit: 0 bytes in 0 blocks
==4810==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==4810== 
==4810== All heap blocks were freed -- no leaks are possible
==4810== 
==4810== For counts of detected and suppressed errors, rerun with: -v
==4810== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

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

[kmail2] [Bug 362608] Default colours unusable on dark theme

[Denis Kurz]

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

Denis Kurz  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #13 from Denis Kurz  ---
Ok, you might be right. Fixing one bug probably wouldn't fix the other: One
describes the problem with color schemes, the other with some default css.
Sorry for the noise.

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

[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland

[Boudewijn Rempt]

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

--- Comment #3 from Boudewijn Rempt  ---
Probably, but I don't know. I haven't got a wayland setup, so, like I said
before, someone who cares about wayland should start working on making Krita
work on Wayland. I'm not that person. Just telling me that Krita is completely
unusable on Wayland doesn't convince me to change my priorities: you can always
stop using Wayland and use X11 instead.

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

[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland

[bugzilla_noreply]

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

djmcbrat...@gmail.com changed:

   What|Removed |Added

 CC||djmcbrat...@gmail.com

--- Comment #2 from djmcbrat...@gmail.com ---
Does this issue affect Krita under KDE's Wayland implementation? 

I'd really rather not have to choose between GNOME and Krita at some point in
the future. For the moment, it's not the only app with some issues on Wayland,
but it is the only one I use that's completely unusable there at the moment.

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

[kdenlive] [Bug 380036] New: Since v17, Render always crashes on Win10: Qt can't find platform plugin "windows"

[bugzilla_noreply]

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

Bug ID: 380036
   Summary: Since v17, Render always crashes on Win10: Qt can't
find platform plugin "windows"
   Product: kdenlive
   Version: 17.04.0
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Installation
  Assignee: vpi...@kde.org
  Reporter: e...@ebinary.net
  Target Milestone: ---

kdenlive, windows 10, render

On any attempt to render with 17.04.0, it always crashes with the message: 
This application failed to start because it could not find or load the qt
platform plugin "windows".

I confirmed that qwindows.dll is in the same place as it is on v16.12.1, which
works fine for me.  I assume it's a path or other discovery error, because 16
works ok and the file is there.

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

[kdenlive] [Bug 380035] New: use GLSL compositing/dissolve/zoom by default when GLSL is enabled

[Anton Gubarkov]

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

Bug ID: 380035
   Summary: use GLSL compositing/dissolve/zoom by default when
GLSL is enabled
   Product: kdenlive
   Version: git-master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: anton.gubar...@gmail.com
  Target Milestone: ---

I've come across the page on compositing here
https://kdenlive.org/project/timeline-track-compositing/ that explains many
performance issues I have with kdenlive when compositing multiple tracks. The
default High Quality compositing is CPU. Even when I do GLSL transition,
kdenlive ends up doing CPU compositing.  As a result, the frame rate for every
transition drops to 5 fps (on Intel 4700MQ/16GB RAM). If I add a CPU based
effect, I get 1 fps slide show. 
The sound doesnt' play smoothly either. It stutters every second. 
I work with 28M FHD movies (up to 3 cameras at a time)

Can you please accept the request to make basic video operations in GLSL
entirely to make edition smooth? 

Thanks

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

[valgrind] [Bug 375415] free list of blocks, mempool blocks and describe addr do not work properly together

[Philippe Waroquiers]

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

--- Comment #7 from Philippe Waroquiers  ---
The useless condition was removed in revision 16402.

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

[KAccounts] [Bug 377827] Online Accounts in system settings not working

[bugzilla_noreply]

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

hoe...@gmx.de changed:

   What|Removed |Added

 CC||hoe...@gmx.de

--- Comment #1 from hoe...@gmx.de ---
I faced a similar issue on Gentoo. However, I by chance found a workaround. My
guess would be that installing telepathy-kde-accounts-kcm and
kaccounts-providers should solve the issue.

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

[kleopatra] [Bug 380034] New: Possible exploit: If signed message has added arbitrary text in third line, Kleopatra doesnt warn user that "gpg: Invalid armor header:[content of line]"

[lurker69]

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

Bug ID: 380034
   Summary: Possible exploit: If signed message has added
arbitrary text in third line, Kleopatra doesnt warn
user that "gpg: Invalid armor header:[content of
line]"
   Product: kleopatra
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: lurke...@mail.com
CC: kdepim-b...@kde.org, m...@kde.org
  Target Milestone: ---

When verifying signed message in this format: https://pastebin.com/raw/yEiTHhvF 
anybody can insert any text in third line, and Kleopatra will verify message
and not notify user that Header contained a line that should not be there. 


GPG2.exe or GPG in linux bash show warning:  
gpg: Invalid armor header: [inserted line] https://i.imgur.com/V28UTgJ.jpg

Kleopatra omits this warning and just shows green verification successful
window.
https://i.imgur.com/0w3AasI.jpg


You can reproduce this with: 
https://pastebin.com/raw/yEiTHhvF  <--original unaltered
https://pastebin.com/raw/np4v7ZFM  <--altered message that also verifies in GUI
but shows warning in command prompt 
https://pgp.mit.edu/pks/lookup?op=vindex=0x181F01E57A35090F

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

[systemsettings] [Bug 380033] New: Systemsettings crashes when opening Font Management in Fonts section

[Dennis Schridde]

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

Bug ID: 380033
   Summary: Systemsettings crashes when opening Font Management in
Fonts section
   Product: systemsettings
   Version: 5.9.5
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: devuran...@gmx.net
  Target Milestone: ---

Application: systemsettings5 (5.9.5)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.11.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.3"

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

When opening the Font Management part in the Fonts section of Systemsettings,
Systemsettings will crash.

This is a duplicate of bug #364746, but due to bug #355807, I cannot attach
this report to that one.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f221f2df700 (LWP 17455)):
#0  0x7f2244617f9f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f222c6c4593 in cnd_wait (mtx=0xb720f0, cond=0xb72118) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0xb62030) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/src/util/u_queue.c:158
#3  0x7f222c6c42c7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:87
#4  0x7f2244612384 in start_thread () from /lib64/libpthread.so.0
#5  0x7f22471d16af in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f221fae0700 (LWP 17454)):
#0  0x7f2244617f9f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f222c6c4593 in cnd_wait (mtx=0xb720f0, cond=0xb72118) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x9dfa60) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/src/util/u_queue.c:158
#3  0x7f222c6c42c7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:87
#4  0x7f2244612384 in start_thread () from /lib64/libpthread.so.0
#5  0x7f22471d16af in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f22202e1700 (LWP 17453)):
#0  0x7f2244617f9f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f222c6c4593 in cnd_wait (mtx=0xb720f0, cond=0xb72118) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0xb62030) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/src/util/u_queue.c:158
#3  0x7f222c6c42c7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:87
#4  0x7f2244612384 in start_thread () from /lib64/libpthread.so.0
#5  0x7f22471d16af in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f2220ae2700 (LWP 17452)):
#0  0x7f2244617f9f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f222c6c4593 in cnd_wait (mtx=0xb720f0, cond=0xb72118) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x9dfa60) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/src/util/u_queue.c:158
#3  0x7f222c6c42c7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:87
#4  0x7f2244612384 in start_thread () from /lib64/libpthread.so.0
#5  0x7f22471d16af in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f22214ea700 (LWP 17451)):
#0  0x7f2244617f9f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f222c6c4593 in cnd_wait (mtx=0xb62500, cond=0xb62528) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0xb7d8d0) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/src/util/u_queue.c:158
#3  0x7f222c6c42c7 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:87
#4  0x7f2244612384 in start_thread () from /lib64/libpthread.so.0
#5  0x7f22471d16af in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f682700 (LWP 17450)):
#0  0x7f2244617f9f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f222c6c4593 in cnd_wait (mtx=0xb8c1c0, cond=0xb8c1e8) at
/var/tmp/portage/media-libs/mesa-17.1.0/work/mesa-17.1.0/include/c11/threads_posix.h:159
#2  util_queue_thread_func 

[systemsettings] [Bug 364746] Crash when accessing 'Font Management' inside Fonts section of 'Settings'

[Dennis Schridde]

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

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

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

[Breeze] [Bug 379861] The Kontact icon is a wifi icon

[Christophe Giboudeaux]

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

--- Comment #3 from Christophe Giboudeaux  ---
All the rss icons I see have a point and two lines (vs 3 on the akregator's
icon). Maybe removing a line and making the remaining two larger would be less
confusing for users who never saw a rss icon ?

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

[dolphin] [Bug 379135] Dolphin crash when closing tab

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=380032

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

[dolphin] [Bug 380032] New: Active view is toggled when switching tabs

[Elvis Angelaccio]

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

Bug ID: 380032
   Summary: Active view is toggled when switching tabs
   Product: dolphin
   Version: 17.04.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Keywords: regression
  Severity: normal
  Priority: NOR
 Component: split view
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: elvis.angelac...@kde.org
  Target Milestone: ---

This is another regression of:
https://phabricator.kde.org/R318:6af0dad2eeba82929c2299f66ea81e5d0140a251

Steps to reproduce:

1. Open split view with different URLs, say A and B.
2. Open another tab
3. Go back to the split view tab.

The active status of view A and B is inverted every time you switch between the
two tabs (if A is inactive, it will become active the next time, and
viceversa).

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

[frameworks-kcmutils] [Bug 366299] System setting "Energy Saving" window is too large for a standard laptop screen

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

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

[dolphin] [Bug 379135] Dolphin crash when closing tab

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

   Keywords||regression

--- Comment #4 from Elvis Angelaccio  ---
This is what happens:

1. The searchbox of the first tab gets disactivated (as side effect of
   disactivating its container).
2. Second tab gets closed, we call removeTab(1) in the tab widget.
3. The searchbox of the first tab gets a FocusIn event and calls
setActive(true).
4. Since it was disactivated, it emits activated() and this results in the 
   activeViewChanged() signal which causes the crash, because the
currentIndex() 
   of the tab page is still 1 but widget(1) has already been invalidated.

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

[kdenlive] [Bug 379274] Can't select affine transition without crash.

[Jean-Pierre Bovee]

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

Jean-Pierre Bovee  changed:

   What|Removed |Added

 CC||jpbo...@free.fr

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

[kscreenlocker] [Bug 377152] [Wayland] Resuming session after screen lock results in black screen

[Dennis Schridde]

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

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

--- Comment #7 from Dennis Schridde  ---
A workaround is to login to another VT and run `loginctl unlock-session
` (you'll find the session ID by running `loginctl`). When you
switch back to the graphical VT, you'll see the lock screen in a window, which
you cannot close. You can, however kill the process using CTRL+ALT+ESC and then
clicking the lock-screen-window using the read skull mouse cursor.

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

[telepathy] [Bug 380031] New: Telepathy Text UI does not render chat content when running in Wayland

[Dennis Schridde]

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

Bug ID: 380031
   Summary: Telepathy Text UI does not render chat content when
running in Wayland
   Product: telepathy
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: text-ui
  Assignee: kde-telepathy-b...@kde.org
  Reporter: devuran...@gmx.net
  Target Milestone: Future

When running the Telepathy KDE Plasmoid and opening a conversation with a
contact, the Telepathy Text UI opens, displays the menu bar, but no chat
content. The part where usually a while background with the previous
conversation, and below it a text input widget, is displayed, is plain grey.

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

[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore

[bluelupo]

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

--- Comment #5 from bluelupo  ---
Hi Alex,
Thanks for the info on the 17.04.2 release where the error is fixed ;-)

Michael

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

[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup

[Dennis Schridde]

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

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

--- Comment #52 from Dennis Schridde  ---
I have the same issue with KDE Apps 17.04.1, Plasma 5.9.5, KF 5.34.0 using
Wayland: The panel at the top screen edge is rendered on top of Yakuake, making
the upper part of the console unusable. This worked fine with X11.

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

[yakuake] [Bug 378849] yakuakerc from 3.0.2 breaks 3.0.4 on Wayland

[Dennis Schridde]

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

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

--- Comment #1 from Dennis Schridde  ---
I confirm the issue. Deleting the Window section from the config solves the
issue. Keeping the window open is enabled in the settings menu after restarting
Yakuake, and KeepOpen is not set to false in yakuakerc.

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

[konqueror] [Bug 372777] no kwallet integration in 16.12

[Graeme Hewson]

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

Graeme Hewson  changed:

   What|Removed |Added

 CC||b...@wormhole.me.uk

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

[kwayland-integration] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Dennis Schridde]

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

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

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

[kwayland-integration] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Dennis Schridde]

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

--- Comment #32 from Dennis Schridde  ---
Created attachment 105650
  --> https://bugs.kde.org/attachment.cgi?id=105650=edit
New crash information added by DrKonqi

kaccess () using Qt 5.7.1

- What I was doing when the application crashed:

KAccess with KDE Apps 17.04.1, Plasma 5.9.5, KF 5.34.0 crashed upon startup in
Wayland session.

-- Backtrace (Reduced):
#6  0x7f9e84bbcb21 in wl_map_insert_at () from
/usr/lib64/libwayland-client.so.0
#7  0x7f9e84bb8e6e in wl_proxy_destroy () from
/usr/lib64/libwayland-client.so.0
#8  0x7f9e840fa6a5 in KWayland::Client::Registry::release() () from
/usr/lib64/libKF5WaylandClient.so.5
#9  0x7f9e840fa6cc in KWayland::Client::Registry::~Registry() () from
/usr/lib64/libKF5WaylandClient.so.5
#10 0x7f9e840fa759 in KWayland::Client::Registry::~Registry() () from
/usr/lib64/libKF5WaylandClient.so.5

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

[calligrasheets] [Bug 380030] New: Misspell in i18n text

[Guo Yunhe]

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

Bug ID: 380030
   Summary: Misspell in i18n text
   Product: calligrasheets
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: calligra-sheets-bugs-n...@kde.org
  Reporter: guoyunhebr...@gmail.com
  Target Milestone: ---

sheets/latex/export/latexexportwidget.ui:67

The document will be generated as a full latex document since all the include
will be generated before the \begin[document} and \end{document} commands.

\begin[document}  should be \begin{document}

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

[umbrello] [Bug 379899] unable to save work

[Ralf Habacker]

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

--- Comment #4 from Ralf Habacker  ---
Does this bug happens in ubuntu release 16.04 ? If yes there is already a
related bug report
https://bugs.launchpad.net/ubuntu/+source/umbrello/+bug/1585611

If no, this is the link to report such issues
https://bugs.launchpad.net/ubuntu/+source/umbrello/+filebug

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

[umbrello] [Bug 373854] My solution: umbrello there was a problem saving, in Ubuntu 16.04

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

 CC||ralf.habac...@freenet.de
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #2 from Ralf Habacker  ---
https://bugs.launchpad.net/ubuntu/+source/umbrello/+bug/1585611

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

[kdeconnect] [Bug 368069] SMS messages not shown in the list even though they are sent

[Cqoicebordel]

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

--- Comment #10 from Cqoicebordel  ---
Yeah, 2.3.3. It's probably an issue of this old version, indeed, but as I said
earlier, when using https://github.com/everythingandroid/android-smspopup, it
works flawlessly. And they are open source... ;)

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

[umbrello] [Bug 373854] My solution: umbrello there was a problem saving, in Ubuntu 16.04

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

 CC||pnadegen...@gmail.com

--- Comment #1 from Ralf Habacker  ---
*** Bug 379899 has been marked as a duplicate of this bug. ***

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

[umbrello] [Bug 379899] unable to save work

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE

--- Comment #3 from Ralf Habacker  ---
This is a bug in packaging umbrello/KF5 on ubuntu and should be reported at
https://help.ubuntu.com/community/ReportingBugs

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

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

[lokalize] [Bug 380007] Improvements for Gettext entries wordwrapping

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

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

[systemsettings] [Bug 380029] New: Crash when opening workspace themes

[Marcos Grandi]

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

Bug ID: 380029
   Summary: Crash when opening workspace themes
   Product: systemsettings
   Version: 5.9.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: bellinca...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.9.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
Just opened system setting and clicked on workspace themes.

-- 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 0x7f3f43f018c0 (LWP 7179))]

Thread 7 (Thread 0x7f3ef2eee700 (LWP 7206)):
#0  0x7f3f3b7bda79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3f3b778dcc in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3f3b779330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3f3b77949c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3f40f4675b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3f40ef10ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3f40d20f64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3f3f67bbf5 in QQmlThreadPrivate::run (this=0x1790c30) at
qml/ftw/qqmlthread.cpp:147
#8  0x7f3f40d25b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f3f3d8346ba in start_thread (arg=0x7f3ef2eee700) at
pthread_create.c:333
#10 0x7f3f4063282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f3f0db39700 (LWP 7199)):
#0  0x7f3f2bbb8890 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#1  0x7f3f2bbb9458 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7f3f2bbb9789 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#3  0x7f3f2bbba01a in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#4  0x7f3f304be0b7 in pa_mainloop_dispatch () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f3f304be4bc in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f3f304be560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f3f304cc7a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#8  0x7f3f2bbca078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#9  0x7f3f3d8346ba in start_thread (arg=0x7f3f0db39700) at
pthread_create.c:333
#10 0x7f3f4063282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f3f106ab700 (LWP 7193)):
#0  0x7f3f40626b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3f3b77938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3f3b779712 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3f109949d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f3f3b79fbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f3f3d8346ba in start_thread (arg=0x7f3f106ab700) at
pthread_create.c:333
#6  0x7f3f4063282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f3f1cefe700 (LWP 7192)):
#0  0x7f3f3b7bda79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3f3b779488 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3f3b7794d9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3f3b79fbb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3f3d8346ba in start_thread (arg=0x7f3f1cefe700) at
pthread_create.c:333
#5  0x7f3f4063282d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f3f2a2e2700 (LWP 7181)):
#0  0x7f3f40626b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3f3b77938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3f3b77949c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3f40f4675b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3f40ef10ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3f40d20f64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3f44058735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  

[forum.kde.org] [Bug 380028] plantage de baloo_file (5.18.0) qui est remplacé aussitot par le même processus avec un nouveau PID

[sournies]

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

--- Comment #1 from sournies  ---
l'ordinateur fonctionne quand même mais c'est génant.

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

[forum.kde.org] [Bug 380028] plantage de baloo_file (5.18.0) qui est remplacé aussitot par le même processus avec un nouveau PID

[sournies]

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

sournies  changed:

   What|Removed |Added

Summary|plantage de baloo_file  |plantage de baloo_file
   |(5.18.0) qui est remplacé   |(5.18.0) qui est remplacé
   |aussitot par le même|aussitot par le même
   |processus avec un nouvea|processus avec un nouveau
   ||PID

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

[forum.kde.org] [Bug 380028] New: plantage de baloo_file (5.18.0) qui est remplacé aussitot par le même processus avec un nouvea

[sournies]

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

Bug ID: 380028
   Summary: plantage de baloo_file (5.18.0) qui est remplacé
aussitot par le même processus avec un nouvea
   Product: forum.kde.org
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: forum-ad...@kde.org
  Reporter: aime.sourn...@sfr.fr
  Target Milestone: ---

Created attachment 105649
  --> https://bugs.kde.org/attachment.cgi?id=105649=edit
inutile elle parle d'elle même. C'est le 4° rapport, et toujour le même et
toujours au démarrage.

bug au démarrage
Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-77-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:


The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f9ffe40673b in Baloo::IdFilenameDB::get(unsigned long long) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#7  0x7f9ffe41b984 in
Baloo::WriteTransaction::replaceDocument(Baloo::Document const&,
QFlags) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x00429a25 in
Baloo::MetadataMover::updateMetadata(Baloo::Transaction*, QString const&,
QString const&) ()
#9  0x0042a023 in Baloo::MetadataMover::moveFileMetadata(QString
const&, QString const&) ()
#10 0x7f9ffdf44baf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x0042aaba in KInotify::moved(QString const&, QString const&) ()
#12 0x0042cbff in KInotify::slotEvent(int) ()
#13 0x7f9ffdf44baf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f9ffdfc424e in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f9ffdf511cb in QSocketNotifier::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f9ffdf1636c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f9ffdf6cc95 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f9ffa507197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f9ffa5073f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f9ffa50749c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f9ffdf6c7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f9ffdf13b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f9ffdf1bbec in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x0041698c in main ()

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

[krita] [Bug 379963] Play button crashes in macOS

[bugzilla_noreply]

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

--- Comment #2 from john.lac...@gmail.com ---
Hi Boudewijn,
Not able to install 3.1.4-alpha.1 right now, but I found your code fix
(https://cgit.kde.org/krita.git/commit/?id=03b3dbd0a1f64c7d44cfbd98ee44524e59db25b3)
and after enabling opengl in my settings, animations work now! :)

I suggest this code fix be backported into the stable release that is in the
main website.

Thanks for the support and your work on this project!

-John

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

[kdeconnect] [Bug 380027] New: AVM Fritz!Box support for KDEConnect

[Dennis Schridde]

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

Bug ID: 380027
   Summary: AVM Fritz!Box support for KDEConnect
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: devuran...@gmx.net
  Target Milestone: ---

It would be great if KDEConnect would support AVM Fritz!Boxes [1]. The support
I envision would be mostly for reporting callers (and silencing music when
being called), but browsing the NAS of the Fritz!Box could also be an
interesting feature to some.

[1]: https://avm.de/produkte/fritzbox/

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

[kdeconnect] [Bug 368069] SMS messages not shown in the list even though they are sent

[Albert Vaca]

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

--- Comment #9 from Albert Vaca  ---
Oh, 2.3 right? It might be something that only happens on super old versions...

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

[kdeconnect] [Bug 368069] SMS messages not shown in the list even though they are sent

[Albert Vaca]

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

--- Comment #8 from Albert Vaca  ---
Which Android version are you using?

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

[kwin] [Bug 380010] Compositing is turned off completely and abruptly while windows with _NET_WM_BYPASS_COMPOSITOR 1 exist.

[bugzilla_noreply]

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

--- Comment #4 from unsuspicious.fakename+kdeb...@gmail.com ---
Thanks, the config option works as advertised (file permissions were messed
up)! 


Would it be possible to get the wm-specs updated to include the KDE behavior?
So applications that contemplate using the window hint know that it might cause
changes in appearance of the window?

Getting the last half sentence removed from the specs should be enough - at the
moment it says: "...but MUST NOT bypass if it would cause differences from the
composited appearance." which sounds - among other things - a lot as if the
feature would not interfere with accessibility features etc.

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

[kmail2] [Bug 371826] Kmail new mail systray icon invisible unless hovered

[Oleksandr Natalenko]

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

Oleksandr Natalenko  changed:

   What|Removed |Added

 CC||oleksa...@natalenko.name

--- Comment #11 from Oleksandr Natalenko  ---
Confirming this with KMail 5.5.1, Arch Linux and Breeze Dark theme.

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

[Breeze] [Bug 354820] KMail2 Tray icon doesn't match Breeze icon theme

[Oleksandr Natalenko]

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

Oleksandr Natalenko  changed:

   What|Removed |Added

 CC||oleksa...@natalenko.name

--- Comment #19 from Oleksandr Natalenko  ---
Confirming this with KMail 5.5.1, Arch Linux and Breeze Dark theme.

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

[phonon-backend-vlc] [Bug 330475] Dragon Player crashed when trying to play DVD

[Norbert Kovács]

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

Norbert Kovács  changed:

   What|Removed |Added

 CC||norbert.kovacs@contactoffic
   ||e.net

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

[dragonplayer] [Bug 240850] dragon player will not play dvd's

[Norbert Kovács]

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

Norbert Kovács  changed:

   What|Removed |Added

 CC||norbert.kovacs@contactoffic
   ||e.net

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

[dragonplayer] [Bug 198796] Dragon Player doesn't play DVD

[Norbert Kovács]

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

Norbert Kovács  changed:

   What|Removed |Added

 CC||norbert.kovacs@contactoffic
   ||e.net

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

[dolphin] [Bug 380009] Pictures file repeats any picture interminably for ever paralyzing the whole computer.

[Elvis Angelaccio]

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

--- Comment #3 from Elvis Angelaccio  ---
Thanks for the reply. Which program is being used to open the pictures?
(right-click the file and check the first entry of the "Open With" sub-menu)

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

[kio-gdrive] [Bug 379999] Unable to install on Linux Mint KDE

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #1 from Elvis Angelaccio  ---
Sorry but you need to ask in a Mint support channel (like IRC or forums).

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

[plasmashell] [Bug 380026] New: Plasmashell craqsh

[Xwang]

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

Bug ID: 380026
   Summary: Plasmashell craqsh
   Product: plasmashell
   Version: 5.9.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: xwaang1...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
I have just installed Kmag on my archlinux system and I was searching for the
app shortcut in the menu

- Unusual behavior I noticed:
Plasmashell crashed

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

Thread 8 (Thread 0x7f27a72fa700 (LWP 7735)):
#0  0x7f286c8b71c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f286c871536 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#2  0x7f286c871a20 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f286c871acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f28723c109b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f287236a8ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f287218ca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f27a9c9d0a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#8  0x7f28721916d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f2871aa454f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f27be552700 (LWP 7721)):
#0  0x7f286c8b71c9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f286c870d67 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f286c8718db in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f286c871acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f28723c109b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f287236a8ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f287218ca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f2875e78fd6 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7f28721916d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f2871aa454f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f284a92b700 (LWP 7720)):
#0  0x7f287104c756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2877b6c234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f2877b6c279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f2871aa454f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f2858953700 (LWP 7712)):
#0  0x7f2871a9a67d in poll () at /usr/lib/libc.so.6
#1  0x7f286c8719b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f286c871acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f28723c109b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f287236a8ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f287218ca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f28752c5025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f28721916d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f2871aa454f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f285a9e1700 (LWP 7690)):
#0  0x7f286c8b71e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f286c87154a in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#2  0x7f286c871a20 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f286c871acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f28723c109b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f287236a8ca in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f287218ca73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f28752c5025 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f28721916d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f28710462e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f2871aa454f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f285bfff700 (LWP 7630)):
#0  0x7f2871a9a67d in poll () at /usr/lib/libc.so.6
#1  0x7f286c8719b6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f286c871acc in 

[Akonadi] [Bug 379809] akonadiserver crashes with SIGSEGV after "akonadictl stop"

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/ako
   ||nadi/76fac925362e55c0919d9f
   ||faf688bdf77865d7a4
   Version Fixed In||5.5.2
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Daniel Vrátil  ---
Git commit 76fac925362e55c0919d9ffaf688bdf77865d7a4 by Daniel Vrátil.
Committed on 20/05/2017 at 07:33.
Pushed by dvratil into branch 'Applications/17.04'.

Fix crash when Connection is terminated before init()
FIXED-IN: 5.5.2

M  +3-1src/server/connection.cpp

https://commits.kde.org/akonadi/76fac925362e55c0919d9ffaf688bdf77865d7a4

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

[kio] [Bug 380025] New: Reddit search provider

[LtWorf]

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

Bug ID: 380025
   Summary: Reddit search provider
   Product: kio
   Version: 4.14.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: desktop
  Assignee: fred...@kde.org
  Reporter: tipos...@tiscali.it
  Target Milestone: ---

Could you include this search provider for subreddits?

I find it quite convenient.

[Desktop Entry]
Type=Service
Name=Reddit
Keys=r
Query=https://www.reddit.com/r/\\{@}/
Charset=utf8
X-KDE-ServiceTypes=SearchProvider

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

[Akonadi] [Bug 379155] Imap resources crash when trying to open settings

[Reuben Peterkin]

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

Reuben Peterkin  changed:

   What|Removed |Added

 CC||reube...@yahoo.com

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