[kmail2] [Bug 378007] Cannot display attached files for some weird content-type

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #2 from Laurent Montel  ---
I confirm it. 
I already created some autotests.
I need to understand where is the bug.

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

[kmail2] [Bug 379467] Display "Date:" header in sender's local timezone

[Laurent Montel]

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

--- Comment #3 from Laurent Montel  ---
Which is your messageviewer theme ?

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

[valgrind] [Bug 381162] possible array overrun in VEX register allocator

[Ivo Raisr]

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

--- Comment #7 from Ivo Raisr  ---
I concur.
I hope this will shed some light for a mysterious bug I see on x86/Solaris (not
amd64/Solaris) which manifests in the following debug output printed for almost
all gdbserver_tests:

vex iropt: 4 x unrolling (25 sts -> 100 sts)
vex iropt: 2 x unrolling (50 sts -> 100 sts)
vex iropt: 2 x unrolling (34 sts -> 68 sts)
vex iropt: fold_Expr: no ident rule for: 32HLto64(t47,t47)
vex iropt: 8 x unrolling (13 sts -> 104 sts)
vex iropt: 2 x unrolling (56 sts -> 112 sts)
vex iropt: 8 x unrolling (14 sts -> 112 sts)
vex iropt: 2 x unrolling (57 sts -> 114 sts)
vex iropt: 2 x unrolling (47 sts -> 94 sts)
vex iropt: 2 x unrolling (33 sts -> 66 sts)
vex iropt: fold_Expr: no ident rule for: 32HLto64(t68,t68)
vex iropt: fold_Expr: no ident rule for: 32HLto64(t62,t62)
vex iropt: fold_Expr: no ident rule for: 32HLto64(t66,t66)
vex iropt: fold_Expr: no ident rule for: 32HLto64(t57,t57)
vex iropt: 2 x unrolling (39 sts -> 78 sts)
vex iropt: 2 x unrolling (33 sts -> 66 sts)
vex iropt: 2 x unrolling (57 sts -> 114 sts)
vex iropt: 2 x unrolling (39 sts -> 78 sts)
vex iropt: IRStmt_Exit became unconditional
vex iropt: IRStmt_Exit became unconditional
vex iropt: 2 x unrolling (32 sts -> 64 sts)
vex iropt: 2 x unrolling (44 sts -> 88 sts)
vex iropt: IRStmt_Exit became unconditional
vex iropt: fold_Expr: no ident rule for: 32HLto64(t118,t118)
vex iropt: 2 x unrolling (33 sts -> 66 sts)

This is printed only for a brief duration and I can reproduce it outside the
'regtest' harness.
For example with nlvgdbsigqueue, following GDB commands in
nlvgdbsigqueue.stdinB.gdb, it is printed only after I hit "continue":


../vg-in-place --tool=none --vgdb=yes --vgdb-error=0
--vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue ./sleepers 10 10 1
BSBSBSBS 1
==9979== Nulgrind, the minimal Valgrind tool
==9979== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote.
==9979== Using Valgrind-3.14.0.SVN and LibVEX; rerun with -h for copyright info
==9979== Command: ./sleepers 10 10 1 BSBSBSBS 1
==9979==
==9979== (action at startup) vgdb me ...
==9979==
==9979== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==9979==   /path/to/gdb ./sleepers
==9979== and then give GDB the following command
==9979==   target remote |
/export/home/tester1/valgrind-32/gdbserver_tests/../.in_place/../../bin/vgdb
--vgdb-prefix=./vgdb-prefix-nlvgdbsigqueue --pid=9979
==9979== --pid is optional if only one valgrind process is running
==9979==

[here all the signals are queued as described in nlvgdbsigqueue.stdinB.gdb]
[then do "continue" in GDB]

vex iropt: 4 x unrolling (20 sts -> 80 sts)
vex iropt: 2 x unrolling (41 sts -> 82 sts)
vex iropt: 4 x unrolling (29 sts -> 116 sts)
vex iropt: 2 x unrolling (38 sts -> 76 sts)
vex iropt: 8 x unrolling (12 sts -> 96 sts)
vex iropt: 2 x unrolling (32 sts -> 64 sts)
vex iropt: 8 x unrolling (13 sts -> 104 sts)
vex iropt: 4 x unrolling (30 sts -> 120 sts)
vex iropt: 2 x unrolling (39 sts -> 78 sts)
vex iropt: 4 x unrolling (16 sts -> 64 sts)
vex iropt: 8 x unrolling (15 sts -> 120 sts)
vex iropt: 2 x unrolling (34 sts -> 68 sts)
vex iropt: not unrolling (75 sts)
vex iropt: 4 x unrolling (29 sts -> 116 sts)
vex iropt: 4 x unrolling (16 sts -> 64 sts)
vex iropt: 8 x unrolling (15 sts -> 120 sts)
vex iropt: 4 x unrolling (23 sts -> 92 sts)
vex iropt: IRStmt_Exit became unconditional
vex iropt: 8 x unrolling (13 sts -> 104 sts)
vex iropt: 8 x unrolling (12 sts -> 96 sts)
vex iropt: IRStmt_Exit became unconditional
vex iropt: 2 x unrolling (35 sts -> 70 sts)
loops/sleep_ms/burn/threads_spec/affinity:  10 10 1 BSBSBSBS 1
vex iropt: IRStmt_Exit became unconditional
vex iropt: 2 x unrolling (50 sts -> 100 sts)
vex iropt: IRStmt_Exit became unconditional
vex iropt: 2 x unrolling (31 sts -> 62 sts)
vex iropt: 2 x unrolling (34 sts -> 68 sts)
vex iropt: 8 x unrolling (13 sts -> 104 sts)
vex iropt: 2 x unrolling (50 sts -> 100 sts)
Brussels ready to sleep and/or burn
London ready to sleep and/or burn
Petaouchnok ready to sleep and/or burn
main ready to sleep and/or burn


Unfortunately I cannot attach to the main Valgrind process with gdb to watch
who has supposedly mistakenly overwritten vex_control.iropt_verbosity. Because
by that time procfs agent thread is created in the process and gdb is confused
about it and crashes.

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

[kdevelop] [Bug 381218] New: Perforce not listed when creating project

[Shervin Emami]

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

Bug ID: 381218
   Summary: Perforce not listed when creating project
   Product: kdevelop
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: VCS: Perforce
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: shervin.em...@gmail.com
  Target Milestone: ---

Using kdevelop 5.1.0 or the latest nightly build (on 15th June 2017), I tried
enabling the perforce plugin, but when I click on New Project, the Version
Control System list doesn't mention perforce.

My method of enabling the perforce plugin:
1) Setting the P4CONFIG environment variable to my .p4config file,
2) running kdevelop from my project folder with that file (as mentioned in
"https://bugs.kde.org/show_bug.cgi?id=376789;),
3) in the Configure KDevelop -> Plugins settings I enabled the perforce plugin,
4) verified it was still enabled after going back into the Plugins settings.

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

[valgrind] [Bug 381162] possible array overrun in VEX register allocator

[Julian Seward]

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

--- Comment #6 from Julian Seward  ---
(In reply to Philippe Waroquiers from comment #5)
> In the particular case of the lib VEX 'fast allocator', there is
> no instrumentation of this allocator [..]

Ah.  Good point.  Hmm.  Given that VEX is a big(ish) and complex bit of
code, and that it will be getting more complex with Ivo's IR work, it would
be nice if we could Memcheck it properly.  In particular I'd like to be able
to check for uninitialised value uses in it.  Is it possible you could make
a patch to do what you said, at some point?

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

[k3b] [Bug 380255] K3b does not remember its window size/position under Wayland

[Leslie Zhai]

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

--- Comment #7 from Leslie Zhai  ---
Dear Martin,

Thanks for your kind response!

> That it works on Weston is pure chance. The window placing algorithm is just
> not good enough there.
> 
> On Wayland it is not possible for applications to position themselves. 

I am not familiar with set_position
https://cgit.freedesktop.org/wayland/wayland/tree/protocol/wayland.xml#n2649

PS: why you changed your family name?

Regards,
Leslie Zhai

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

[tellico] [Bug 378477] Can't see the star icon in the column view and in the entry editor

[Robby Stephenson]

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

--- Comment #7 from Robby Stephenson  ---
Thanks for the screenshots. Looking at them, there are other missing icons in
the UI., too, it appears. The Filters tab should have an icon, the Nouveau
button should have one, etc...checkmark icons probably don't shown in the
column view, either, right?

That symptom gives me a few pointers to go check...

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

[Plasma SDK] [Bug 381217] New: Multi Monitor Taskbar Drag

[bugzilla_noreply]

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

Bug ID: 381217
   Summary: Multi Monitor Taskbar Drag
   Product: Plasma SDK
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: greylee...@gmail.com
CC: antonis.tsiapalio...@kde.org
  Target Milestone: ---

Created attachment 106104
  --> https://bugs.kde.org/attachment.cgi?id=106104=edit
This is the window at the bottom of my left monitor while I am attempting to
drag the window

I have two monitors and I prefer to have my taskbar on the leftside of my right
monitor. If I try to move a window on my left monitor with this configuration,
I lose the ability to place the window on the left monitor. Dragging it to an
edge for fullscreen or split screen still works, however.

I have also noticed that this puts that window at the bottom of my left screen
and I am able to grab it from there.

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

[Plasma SDK] [Bug 381217] Multi Monitor Taskbar Drag

[bugzilla_noreply]

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

greylee...@gmail.com changed:

   What|Removed |Added

   Severity|normal  |minor

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

[bugs.kde.org] [Bug 366840] Bump version numbers to match KDE Neon releases

[KDE Neon user]

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

KDE Neon user  changed:

   What|Removed |Added

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

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

[dolphin] [Bug 368418] Add audio -> bitrate column to "Details" view mode

[KDE Neon user]

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

KDE Neon user  changed:

   What|Removed |Added

Summary|Add audio -> bitrate column |Add audio -> bitrate column
   |to detais mode  |to "Details" view mode

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

[systemsettings] [Bug 381207] Allow the use of a solid color as the background instead of a wallpaper

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Please also report this to SDDM developers via
https://github.com/sddm/sddm/issues

The option can only be added to the KCM if SDDM supports it.

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

[kdenlive] [Bug 381208] Kdenlive crashes on exit and messing up Backupfile

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[kdenlive] [Bug 378469] 17.04 - Crash on Exit

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||vor...@z-ray.de

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

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

[kdialog] [Bug 381121] kdialog raise segment fault

[Dorian Han]

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

Dorian Han  changed:

   What|Removed |Added

 CC||tung...@outlook.com

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

[kwin] [Bug 380865] kwin_x11 freezes with 100% CPU when using Desktop Grid with Present Windows

[Kelvie Wong]

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

Kelvie Wong  changed:

   What|Removed |Added

 CC||kel...@ieee.org

--- Comment #1 from Kelvie Wong  ---
Created attachment 106103
  --> https://bugs.kde.org/attachment.cgi?id=106103=edit
two backtraces on all threads on kwin_x11 while it's frozen, I let it run for a
few seconds before taking the second one

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

[digikam] [Bug 380847] MP4 video not importing with correct date

[bugzilla_noreply]

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

--- Comment #6 from matrix43...@gmail.com ---
>From what metadata field does Digikam then source the MP4 date? As I said in
the original post, all metadata fields have the correct date except for the
Encoding Time. I viewed metadata using Exiftool.

Cheers

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

[bindings] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)

[Scott Kitterman]

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

--- Comment #5 from Scott Kitterman  ---
Honestly, I don't know.  I don't have anything to do with Neon, but this isn't
a KDE bug, it's a bug in their packaging.

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

[bindings] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)

[Bernard Gray]

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

--- Comment #4 from Bernard Gray  ---
Hi Scott, 
Thanks for the reply.
I apologise, but I thought this bugtracker is where I would make neon related
requests. I gather from your post that I was wrong - can you point me in the
direction of where I should post my request to rebuild python3-pykde4?

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

[Discover] [Bug 381161] Discover uses a low resolution icon for Kdenlive

[KDE Neon user]

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

KDE Neon user  changed:

   What|Removed |Added

Version|5.10.1  |5.10.2

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

[dolphin] [Bug 367681] Option to display the creation or modification dates of the selected file on the status bar

[KDE Neon user]

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

KDE Neon user  changed:

   What|Removed |Added

Version|16.12.2 |17.04.2

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

[plasmashell] [Bug 368822] Laptop is suspended when locked even though it's connected to a power source

[KDE Neon user]

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

KDE Neon user  changed:

   What|Removed |Added

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

--- Comment #9 from KDE Neon user  ---
I'm back to KDE Neon and haven't had this problem again yet. I'll open a new
issue in case something like that happens again.

Guillaume DE BURE, open a separate issue if you're still having problems.

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

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

[Christoph Feck]

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

--- Comment #7 from Christoph Feck  ---
Please do not mix unrelated bug reports.

The crash reported here looks caused by conflicting shortcut settings. It
should not crash, though, but show a dialog instead.

To debug this, try changing locale/language or (if you had reconfigured
shortcuts) starting with a clean
~/.local/share/kxmlgui5/konversation/konversationui.rc configuration.

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

[konsole] [Bug 381014] Text scatter

[Christoph Feck]

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

--- Comment #4 from Christoph Feck  ---
But it doesn't happen in every KDE/Qt application? We need to find a pattern
here, but from looking at the screen shot, I suspect your X11 video drivers are
not working correctly. Please check if disabling compositing (Alt+Shift+F12)
helps.

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

[plasmashell] [Bug 381216] New: Plasma fails after multiple copies

[Edar José Blanco Rodríguez]

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

Bug ID: 381216
   Summary: Plasma fails after multiple copies
   Product: plasmashell
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: edar.bla...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.3-1-ARCH x86_64
Distribution: "Arch Linux"

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

Plasma failure after using 2 tabs in dolphin and 2 panels in one of them, in a
window to a copy from a backup server using sftp and in the other to a usb
memory

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 0x7f988a45ad80 (LWP 621))]

Thread 23 (Thread 0x7f976ac0b700 (LWP 1878)):
#0  0x7f988336439d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f98841970eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f9887f378d8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f9887f37d3a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f9884195cbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7f988335e297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f9883aaa25f in clone () at /usr/lib/libc.so.6

Thread 22 (Thread 0x7f976bfff700 (LWP 1671)):
#0  0x7f988336439d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f98841970eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f97c88333cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f97c88382b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f97c8832913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f97c8835b6b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f9884195cbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7f988335e297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f9883aaa25f in clone () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7f9784b30700 (LWP 1670)):
#0  0x7f988336439d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f98841970eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f97c88333cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f97c88382b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f97c8832913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f97c8835b6b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f9884195cbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7f988335e297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f9883aaa25f in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f9785331700 (LWP 1669)):
#0  0x7f988336439d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f98841970eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f97c88333cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f97c88382b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f97c8832913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f97c8838312 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f97c8832913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f97c8835b6b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f9884195cbd in  () at /usr/lib/libQt5Core.so.5
#9  0x7f988335e297 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f9883aaa25f in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f9785b32700 (LWP 1668)):
#0  0x7f988336439d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f98841970eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f97c88333cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f97c88382b8 in  () at 

[digikam] [Bug 381165] multiple assigned shortcut CTRL+L in Dutch after [Importeren] -> autodetected device

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |5.4.0

--- Comment #2 from Christoph Feck  ---
Could also be caused by translations.

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

[kdevelop] [Bug 381203] Kdevelop crashes when editing Python Code

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Hmm, never seen that trace. Did you try clearing ~/.cache/kdevduchain?

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

[kwin] [Bug 381210] kwin>=5.10.0 crashes immediately on start on FreeBSD

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #6 from Christoph Feck  ---
Backtrace from comment #3 looks useful. Could be a regression caused by the
KWin::Xkb split.

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

[okular] [Bug 381209] Print to PDF file with more than one page per sheet doesn't work (instead it prints only one per sheet)

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---


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

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

[okular] [Bug 252596] okular printing options not working when printing to file (pdf/ps)

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||elias@gmail.com

--- Comment #20 from Albert Astals Cid  ---
*** Bug 381209 has been marked as a duplicate of this bug. ***

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

[Breeze] [Bug 381196] Make notification popup have rounded corners

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||aleix...@kde.org

--- Comment #3 from Aleix Pol  ---
Michael, please get in touch with the kde visual design group and discuss it
with them.

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

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

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||aa...@kde.org
 Ever confirmed|0   |1

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

[krusader] [Bug 381179] Problems with shortcut

[Toni Asensi Esteve]

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

Toni Asensi Esteve  changed:

   What|Removed |Added

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

--- Comment #1 from Toni Asensi Esteve  ---
I tried it and it didn't happen using Kubuntu 17.04 and the git version of
Krusader. 

Can you try using a new version of Krusader? (2.4.0-beta3 is no longer
supported). In order to use the git version of Krusader there are instructions
in https://cgit.kde.org/krusader.git/plain/INSTALL

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

[gwenview] [Bug 381215] When opening an image, Gwenview asks to report the bug below.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[gwenview] [Bug 362295] No such object path '/modules/kdeconnect/devices/_d05cbcbd_dea5_4135_949c_6430342eec97_/sftp'

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||alain.salvatore@espe-paris.
   ||fr

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

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

[kmail2] [Bug 365138] Regression: new taskbar icon hard to read on both default themes

[kjetil]

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

--- Comment #11 from kjetil  ---
Created attachment 106102
  --> https://bugs.kde.org/attachment.cgi?id=106102=edit
Screenshot confirming lack of emai-count in Kmail tray icon

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

[kmail2] [Bug 365138] Regression: new taskbar icon hard to read on both default themes

[kjetil]

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

kjetil  changed:

   What|Removed |Added

 CC||kjetil.fjesbokbruker@gmail.
   ||com

--- Comment #10 from kjetil  ---
Just to confirm; also present on:

Kubuntu 17.04 Zesty
Plasma 5.10.1
Kde Frameworks 5.34.0
Kmail 5.4.3 
KDE PIM 16.12.3

Theme: Breeze-Light (everything default)

The same bug that is described above. Icon changes but no count for unread
email. Icon email-count disappeared after upgrading to PIM 16.12.3 and plasma
5.10.1 from backports.

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

[gwenview] [Bug 381215] New: When opening an image, Gwenview asks to report the bug below.

[Salvatore]

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

Bug ID: 381215
   Summary: When opening an image, Gwenview asks to report the bug
below.
   Product: gwenview
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: alain.salvat...@espe-paris.fr
CC: myr...@kde.org
  Target Milestone: ---

No such object path '/modules/kdeconnect/devices/9951fc0d1f4d31b8/sftp'

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

[konsole] [Bug 381115] tab completion in konsole freezes system for about 20s

[govindarajulu]

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

--- Comment #2 from govindarajulu  ---
I am seeing the same issue after upgrading plasma-workspace from 5.9.5.1-1 
 to 5.10.0-3

Am running i3-wm. Did not see the issue on gnome3.
If nothing seems abvious, I can git bisect it. Let me know.

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

[Discover] [Bug 381182] Scrolling choppy/slow under Wayland

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
I can confirm this. I thought it was
https://bugreports.qt.io/browse/QTBUG-57186 but it happens also on Wayland
(where other qml applets work fine), so it must be something else.

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

[konsole] [Bug 381115] tab completion in konsole freezes system for about 20s

[govindarajulu]

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

govindarajulu  changed:

   What|Removed |Added

 CC||govindarajul...@gmail.com

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

[dolphin] [Bug 381187] Please add Miller Columns back to Dolphin

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kde.org

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

[k3b] [Bug 380255] K3b does not remember its window size/position under Wayland

[Dr . Chapatin]

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

--- Comment #6 from Dr. Chapatin  ---
Splash screen appears on top left side here.
The same happens with qbittorrent splash screen.

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

[digikam] [Bug 381214] New: Import may mix up picture content and metadata of different pictures

[bugzilla_noreply]

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

Bug ID: 381214
   Summary: Import may mix up picture content and metadata of
different pictures
   Product: digikam
   Version: 5.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Import
  Assignee: digikam-de...@kde.org
  Reporter: b3nm...@googlemail.com
  Target Milestone: ---

Created attachment 106101
  --> https://bugs.kde.org/attachment.cgi?id=106101=edit
Screenshots inconsistent import.

I recently imported pictures from a Sony R100 M3 (which is recognized as a
generic usb mass storage device). Some pictures are saved with the wrong
picture contents. That means the meta data does not fit to the actual picture,
since the picture contents belongs to another picture. For a better
explanation, please have a look at the attached screenshot. It shows the import
window with the correct picture content, filename and metadata. The lower part
shows the main window where the filename and the metadata is copied correctly,
but now belong to another picture content (actually to a picture which was
recorded several days later).

I've checked the copied picture with other programs and they show that it is
indeed a mixture of the file name and metadata of one picture and the content
of another one (so not a database or thumbnail issue).

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

[kwin] [Bug 381210] kwin>=5.10.0 crashes immediately on start on FreeBSD

[bugzilla_noreply]

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

--- Comment #5 from mnd...@gmail.com ---
Actually, can just run in lldb:

(lldb) bt all
* thread #1, stop reason = signal SIGSEGV: invalid address (fault address:
0x80)
  * frame #0: 0x00080718ee93
libxkbcommon.so.0`xkb_state_mod_index_is_active + 19
frame #1: 0x000800e20956
libkwin.so.5`KWin::Xkb::modifiersRelevantForGlobalShortcuts(void) const + 38
frame #2: 0x000800d0a7a5
libkwin.so.5`KWin::KeyboardInputRedirection::processKey(unsigned int,
KWin::InputRedirection::KeyboardKeyState, unsigned int,
KWin::LibInput::Device*) + 277
frame #3: 0x00081a23d6f2
KWinX11Platform.so`___lldb_unnamed_symbol107$$KWinX11Platform.so + 114
frame #4: 0x000800d2ff38
libkwin.so.5`KWin::Workspace::workspaceEvent(xcb_generic_event_t*) + 840
frame #5: 0x000800d265ec
libkwin.so.5`___lldb_unnamed_symbol881$$libkwin.so.5 + 76
frame #6: 0x00080a468ab3
libQt5Core.so.5`QAbstractEventDispatcher::filterNativeEvent(QByteArray const&,
void*, long*) + 115
frame #7: 0x000818546bb5
libQt5XcbQpa.so.5`QXcbConnection::handleXcbEvent(xcb_generic_event_t*) + 69
frame #8: 0x000818549246
libQt5XcbQpa.so.5`QXcbConnection::processXcbEvents(void) + 710
frame #9: 0x00080a497562 libQt5Core.so.5`QObject::event(QEvent*) + 146
frame #10: 0x000818549afc
libQt5XcbQpa.so.5`QXcbConnection::event(QEvent*) + 76
frame #11: 0x00080916ff20
libQt5Widgets.so.5`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 304
frame #12: 0x0008091723ed
libQt5Widgets.so.5`QApplication::notify(QObject*, QEvent*) + 4669
frame #13: 0x00080082bbdb
libkdeinit5_kwin_x11.so`___lldb_unnamed_symbol14$$libkdeinit5_kwin_x11.so + 59
frame #14: 0x00080a46da37
libQt5Core.so.5`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 151
frame #15: 0x00080a46e77b
libQt5Core.so.5`QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
QThreadData*) + 875
frame #16: 0x00080a4bcf89
libQt5Core.so.5`QEventDispatcherUNIX::processEvents(QFlags)
+ 73
frame #17: 0x0008185bb17e
libQt5XcbQpa.so.5`___lldb_unnamed_symbol1312$$libQt5XcbQpa.so.5 + 14
frame #18: 0x00080a469820
libQt5Core.so.5`QEventLoop::exec(QFlags) + 400
frame #19: 0x00080a46e095 libQt5Core.so.5`QCoreApplication::exec(void)
+ 325
frame #20: 0x00080082c74e libkdeinit5_kwin_x11.so`kdemain + 2574
frame #21: 0x00400bff kwin_x11`___lldb_unnamed_symbol1$$kwin_x11 +
383
  thread #2
frame #0: 0x00080b2f258a libc.so.7`__sys_poll + 10
frame #1: 0x00080afdb706
libthr.so.3`___lldb_unnamed_symbol38$$libthr.so.3 + 54
frame #2: 0x0008081b4e62
libxcb.so.1`___lldb_unnamed_symbol3$$libxcb.so.1 + 226
frame #3: 0x0008081b675b libxcb.so.1`xcb_wait_for_event + 123
frame #4: 0x000818548525
libQt5XcbQpa.so.5`___lldb_unnamed_symbol61$$libQt5XcbQpa.so.5 + 69
frame #5: 0x00080a2ac6ba
libQt5Core.so.5`___lldb_unnamed_symbol241$$libQt5Core.so.5 + 234
frame #6: 0x00080afd8bc5
libthr.so.3`___lldb_unnamed_symbol1$$libthr.so.3 + 325
  thread #3
frame #0: 0x00080b2f258a libc.so.7`__sys_poll + 10
frame #1: 0x00080afdb706
libthr.so.3`___lldb_unnamed_symbol38$$libthr.so.3 + 54
frame #2: 0x00080a4bbbc0 libQt5Core.so.5`qt_safe_poll(pollfd*, unsigned
int, timespec const*) + 544
frame #3: 0x00080a4bd2a8
libQt5Core.so.5`QEventDispatcherUNIX::processEvents(QFlags)
+ 872
frame #4: 0x00080a469820
libQt5Core.so.5`QEventLoop::exec(QFlags) + 400
frame #5: 0x00080a2a8da3 libQt5Core.so.5`QThread::exec(void) + 115
frame #6: 0x000805361a43
libQt5DBus.so.5`___lldb_unnamed_symbol12$$libQt5DBus.so.5 + 19
frame #7: 0x00080a2ac6ba
libQt5Core.so.5`___lldb_unnamed_symbol241$$libQt5Core.so.5 + 234
frame #8: 0x00080afd8bc5
libthr.so.3`___lldb_unnamed_symbol1$$libthr.so.3 + 325
  thread #4
frame #0: 0x00080afe6c7c
libthr.so.3`___lldb_unnamed_symbol180$$libthr.so.3 + 92
frame #1: 0x00080afe49f8
libthr.so.3`___lldb_unnamed_symbol158$$libthr.so.3 + 488
frame #2: 0x00080a2adae2
libQt5Core.so.5`___lldb_unnamed_symbol250$$libQt5Core.so.5 + 290
frame #3: 0x00080a2ad8b9 libQt5Core.so.5`QWaitCondition::wait(QMutex*,
unsigned long) + 153
frame #4: 0x00080a2a969e
libQt5Core.so.5`___lldb_unnamed_symbol218$$libQt5Core.so.5 + 430
frame #5: 0x00080a2ac6ba
libQt5Core.so.5`___lldb_unnamed_symbol241$$libQt5Core.so.5 + 234
frame #6: 0x00080afd8bc5
libthr.so.3`___lldb_unnamed_symbol1$$libthr.so.3 + 325
  thread #5
frame #0: 0x00080b2f258a libc.so.7`__sys_poll + 10
frame #1: 0x00080afdb706
libthr.so.3`___lldb_unnamed_symbol38$$libthr.so.3 + 54
frame #2: 0x00080a4bbbc0 libQt5Core.so.5`qt_safe_poll(pollfd*, unsigned
int, timespec const*) + 544
frame #3: 0x00080a4bd2a8
libQt5Core.so.5`QEventDispatcherUNIX::processEvents(QFlags)
+ 872
frame #4: 0x00080a469820

[kwin] [Bug 381210] kwin>=5.10.0 crashes immediately on start on FreeBSD

[bugzilla_noreply]

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

--- Comment #4 from mnd...@gmail.com ---
Yes, I'm getting a similar trace. Is there any way to stop the auto relaunch
behaviour?

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

[frameworks-kxmlgui] [Bug 356489] Black field

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||herve.mo...@skynet.be

--- Comment #12 from Albert Astals Cid  ---
*** Bug 381206 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 381117] Desktop Theme - System Settings Module - Plasma 4 themes available for Plasma 5

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

   Target Milestone|--- |1.0
Product|plasma-integration  |plasmashell
   Assignee|mgraess...@kde.org  |k...@davidedmundson.co.uk
  Component|general |general
 CC||bhus...@gmail.com,
   ||plasma-b...@kde.org

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

[knetwalk] [Bug 381206] Knetwalk starts up but the content of the screen is not visible (black screen)

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||aa...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #1 from Albert Astals Cid  ---


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

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

[plasmashell] [Bug 380943] bad rendering logout screen

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

Product|plasma-integration  |plasmashell
   Assignee|mgraess...@kde.org  |k...@davidedmundson.co.uk
   Target Milestone|--- |1.0
  Component|general |general
 CC||bhus...@gmail.com,
   ||plasma-b...@kde.org

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

[k3b] [Bug 380255] K3b does not remember its window size/position under Wayland

[Martin Flöser]

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

--- Comment #5 from Martin Flöser  ---
That it works on Weston is pure chance. The window placing algorithm is just
not good enough there.

On Wayland it is not possible for applications to position themselves. Hints
like splash screen also do not exist. Currently there is no solution for these
problems.

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

[plasmashell] [Bug 380887] Meta key launcher shortcut interfering with compose key settings

[Martin Flöser]

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

--- Comment #4 from Martin Flöser  ---
Please see
https://www.reddit.com/r/kde/comments/55udc1/how_do_i_stop_the_meta_key_from_opening_the/
for a workaround.

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

[plasma-integration] [Bug 380899] Theme changing with time of day (Example: Breeze from 6am to 9pm and Breeze-Dark from 9pm to 6am)

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---
This is out of scope for plasma-integration. I suggest to just do this with a
script.

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

[valgrind] [Bug 381162] possible array overrun in VEX register allocator

[Philippe Waroquiers]

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

--- Comment #5 from Philippe Waroquiers  ---
(In reply to Julian Seward from comment #2)

> But that might explain why it works.  And why Philippe's self-hosting 
> Memcheck runs never detected it: because LibVEX_Alloc_inline will surely
> have rounded that value up to the next word size (or allocation unit,
> I think 8 or 16 bytes) and in so doing will have removed the effect
> of the "-1".  Bizarre, huh!

In the particular case of the lib VEX 'fast allocator', there is
no instrumentation of this allocator : outer memcheck is simply
not informed that the 'big memory piece' is cut in small blocks.

To detect bugs in this area, it will be needed to change
LibVEX_Alloc_inline (in the inner) to:
   * add some redzone before/after each block
   * increase the permanent and temporary size to cope with the redzone
   * use some mempool client requests to inform
 the outer memcheck of the allocated blocks
   * release all the blocks in one single operation, when the
 temporary zone is cleared via vexSetAllocModeTEMP_and_clear

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

[kscreenlocker] [Bug 380416] Please allow a hook script in kscreenlock

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---
kscreenlocker supports the org.freedesktop.ScreenSaver dbus interface which
provides an ActiveChanged signal. You can connect any script to it as you wish
and perform any action you want.

Given that I don't see the need to add custom code to execute scripts.

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

[kwin] [Bug 371221] Restored maximized windows can't be minimized

[Gabriel C]

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

--- Comment #5 from Gabriel C  ---
Still an bug in 5.10.2

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

[kwin] [Bug 381210] kwin>=5.10.0 crashes immediately on start on FreeBSD

[Tobias C . Berner]

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

--- Comment #3 from Tobias C. Berner  ---
I'm not sure how helpful this is:

#0  0x00080738b903 in xkb_state_mod_index_is_active () from
/usr/local/lib/libxkbcommon.so.0
No symbol table info available.
#1  0x000800f14697 in KWin::Xkb::modifiersRelevantForGlobalShortcuts
(this=0x815b28880) at
/wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/xkb.cpp:391
mods = {i = 0}
consumedMods = {i = 364021888}
#2  0x000800d48c11 in
KWin::KeyboardInputRedirection::modifiersRelevantForGlobalShortcuts
(this=0x819616740) at
/wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/keyboard_input.h:87
No locals.
#3  0x000800d44999 in
KWin::InputRedirection::modifiersRelevantForGlobalShortcuts (this=0x815ae85c0)
at /wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/input.cpp:1948
No locals.
#4  0x000800d66c20 in KWin::PointerInputRedirection::processButton
(this=0x815a45760, button=272,
state=KWin::InputRedirection::PointerButtonPressed, time=1171810, device=0x0)
at
/wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/pointer_input.cpp:306
type = QEvent::MouseButtonPress
event = { = { = { = {_vptr$QEvent =
0x801247f48 , static staticMetaObject = {d =
{superdata = 0x0, stringdata = 0x80aab2ec0, data = 0x80a7ff770, static_metacall
= 0x0, relatedMetaObjects = 0x0, extradata = 0x0}},
d = 0x0, t = 2, posted = 0, spont = 0, m_accept = 1, reserved =
816}, modState = {i = 0}, ts = 1171810}, l = {xp = 0, yp = 0}, w = {xp = 0, yp
= 0}, s = {xp = 0, yp = 0}, b = Qt::LeftButton, mouseState = {i = 1}, caps = 0,
velocity = {xp = 0, yp = 0}}, m_delta = {wd = -1,
ht = -1}, m_deltaUnccelerated = {wd = -1, ht = -1},
m_timestampMicroseconds = 0, m_device = 0x0, m_modifiersRelevantForShortcuts =
{i = 0}, m_nativeButton = 0}
#5  0x000800d44180 in KWin::InputRedirection::processPointerButton
(this=0x815ae85c0, button=272,
state=KWin::InputRedirection::PointerButtonPressed, time=1171810) at
/wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/input.cpp:1828
No locals.
#6  0x000800ee8c7e in KWin::Platform::pointerButtonPressed
(this=0x815b28180, button=272, time=1171810) at
/wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/platform.cpp:205
No locals.
#7  0x000819043f43 in KWin::XInputEventFilter::event (this=0x81a0a5920,
event=0x8188648c0) at
/wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/plugins/platforms/x11/standalone/xinputintegration.cpp:99
e = 0x8188648c0
ge = {m_event = 0x8188648c0}
#8  0x000800d9aa34 in KWin::Workspace::workspaceEvent (this=0x818846000,
e=0x8188648c0) at
/wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/events.cpp:239
filter = 0x81a0a5920
_container_ = {c = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {>
= {__a_ = -1}, }, }}},
  alloc = 0, begin = 0, end = 0, array = {0x0}}, d =
0x815b2ea00}, d = 0x815b2ea00}}, i = {i = 0x815b2ea10}, e = {i = 0x815b2ea18},
control = 1}
ge = 0x8188648c0
values = {0}
eventType = 35 '#'
eventWindow = 16777232
#9  0x000800d8e0e3 in KWin::XcbEventFilter::nativeEventFilter
(this=0x81880db00, eventType=..., message=0x8188648c0, result=0x7fffded0)
at /wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/main.cpp:420
event = 0x8188648c0
#10 0x00080a65cad0 in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
from /usr/local/lib/qt5/libQt5Core.so.5
No symbol table info available.
#11 0x000817741745 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /usr/local/lib/qt5/libQt5XcbQpa.so.5
No symbol table info available.
#12 0x000817743c13 in QXcbConnection::processXcbEvents() () from
/usr/local/lib/qt5/libQt5XcbQpa.so.5
No symbol table info available.
#13 0x00080a68a4c1 in QObject::event(QEvent*) () from
/usr/local/lib/qt5/libQt5Core.so.5
No symbol table info available.
#14 0x00080936ff60 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/local/lib/qt5/libQt5Widgets.so.5
No symbol table info available.
#15 0x000809371300 in QApplication::notify(QObject*, QEvent*) () from
/usr/local/lib/qt5/libQt5Widgets.so.5
No symbol table info available.
#16 0x00080082cb77 in KWin::ApplicationX11::notify (this=0x7fffe718,
o=0x815aa9000, e=0x81889f9c0) at
/wrkdirs/usr/ports/x11-wm/plasma5-kwin/work/kwin-5.10.2/main_x11.cpp:277
No locals.
#17 0x00080a6615d3 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/local/lib/qt5/libQt5Core.so.5
No symbol table info available.
#18 0x00080a6622da in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/local/lib/qt5/libQt5Core.so.5
No symbol table info available.
#19 0x00080a6ae658 in

[kate] [Bug 380861] >> Replace checked << cause a freeze/crash

[Kåre Särs]

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

--- Comment #9 from Kåre Särs  ---
Mathias: You can test the disable buttons and replace status from master :)
Please close the bug if the change fixes the freeze for you.

Thanks,
  Kåre

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

[kate] [Bug 380861] >> Replace checked << cause a freeze/crash

[Kåre Särs]

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

--- Comment #8 from Kåre Särs  ---
Git commit 72e8bd3dcc27a5216003693ceb8fe4d5f7b02ca3 by Kåre Särs.
Committed on 14/06/2017 at 19:45.
Pushed by sars into branch 'master'.

S: Disable search buttons while replacing + add replace status

M  +59   -0addons/search/plugin_search.cpp
M  +2-0addons/search/plugin_search.h
M  +7-1addons/search/replace_matches.cpp
M  +3-0addons/search/replace_matches.h

https://commits.kde.org/kate/72e8bd3dcc27a5216003693ceb8fe4d5f7b02ca3

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

[kwin] [Bug 381210] kwin>=5.10.0 crashes immediately on start on FreeBSD

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---
The backtraces are misleading, because they only show the "give-up" exit() when
kwin has crashed four times in a row.

Is it possible to get the backtrace of the actual crash?

-- 
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

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

See this report:
https://bugs.launchpad.net/cdemu/+bug/1697987

Regards,
--
Cristian

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

[plasma-nm] [Bug 355079] [RFE] Fortigate VPN plugin

[Christian González]

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

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

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

[digikam] [Bug 381193] Digikam crashes after uploading photos from smartphone via USB

[Andrea Malfagia]

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

--- Comment #8 from Andrea Malfagia  ---
(In reply to caulier.gilles from comment #6)
> I suspect a dysfunction
> from your openSuse (perhaps a wrong update).

Hi, I forced zypper to reinstall the relevant package, but nothing changed. Any
more suggestions? Thank you in advance.

Andrea

-- 
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

--- Comment #6 from Cristian Aravena Romero  ---
ping Leslie :-)

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

[kdeplasma-addons] [Bug 381173] Wrong countdown speed in timer plasmoid's window.

[Natalia]

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

Natalia  changed:

   What|Removed |Added

 CC||rk...@mail.ru

--- Comment #2 from Natalia  ---
I have the same problem at openSUSE 42.2.

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

[kwin] [Bug 381210] kwin>=5.10.0 crashes immediately on start on FreeBSD

[bugzilla_noreply]

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

mnd...@gmail.com changed:

   What|Removed |Added

 CC||mnd...@gmail.com

--- Comment #1 from mnd...@gmail.com ---

[mark at markspc /usr/home/mark]$ lldb /usr/local/bin/kwin_x11 -c
kwin_x11.core
(lldb) target create "/usr/local/bin/kwin_x11" --core "kwin_x11.core"
Core file '/usr/home/mark/kwin_x11.core' (x86_64) was loaded.
(lldb) bt all
error: libkdeinit5_kwin_x11.so :: Class 'KSelectionOwner' has a base class
'QObject' which does not have a complete definition.
error: libkdeinit5_kwin_x11.so :: Try compiling the source file with
-fno-limit-debug-info.
* thread #1: tid = 101549, 0x000818d48525, name = 'kwin_x11', stop
reason = signal SIGSEGV
  * frame #0: 0x000818d48525
frame #1: 0x00080a8cd83f
libQt5Core.so.5`QThreadPrivate::start(arg=0x000816b31000) + 511 at
qthread_unix.cpp:368
frame #2: 0x00080b7d9b55 libthr.so.3`??? + 325

  thread #2: tid = 100635, 0x00080badf48a libc.so.7`__sys_nanosleep +
10, name = 'kwin_x11', stop reason = signal SIGSEGV
frame #0: 0x00080badf48a libc.so.7`__sys_nanosleep + 10
frame #1: 0x00080b7dc4cc libthr.so.3`??? + 44
frame #2: 0x00080ba632cb libc.so.7`sleep + 59
frame #3: 0x00080082ac25
libkdeinit5_kwin_x11.so`KWin::ApplicationX11::crashHandler(signal=6) + 213
at main_x11.cpp:325
frame #4: 0x000808ad3b8b
libKF5Crash.so.5`KCrash::defaultCrashHandler(int) + 91
frame #5: 0x00080b7df78f libthr.so.3`??? + 223
frame #6: 0x00080b7ded6f libthr.so.3`??? + 319
frame #7: 0x7003
frame #8: 0x00080babf499 libc.so.7`abort + 73
frame #9: 0x00080a8a8538
libQt5Core.so.5`qt_message_fatal((null)=QtFatalMsg,
context=0x7fffc100, message=0x7fffc0c8) + 24 at
qlogging.cpp:1682
frame #10: 0x00080a8aa66e
libQt5Core.so.5`QMessageLogger::fatal(this=0x7fffc100, msg="")
const + 446 at qlogging.cpp:793
frame #11: 0x00080a8a0ffa libQt5Core.so.5`qt_assert_x(where="",
what="Cannot send events to objects owned by a different thread. Current
thread 816a44030. Receiver '' (of type 'KWin::ApplicationX11') was created
in thread 816a44050", file="", line=541) + 90 at qglobal.cpp:3089
frame #12: 0x00080ab83fd7
libQt5Core.so.5`QCoreApplicationPrivate::checkReceiverThread(receiver=0x7fffe498)
+ 711 at qcoreapplication.cpp:533
frame #13: 0x0008095782b9
libQt5Widgets.so.5`QApplication::notify(this=0x7fffe498,
receiver=0x7fffe498, e=0x7fffd128) + 169 at
qapplication.cpp:3021
frame #14: 0x00080082ab07
libkdeinit5_kwin_x11.so`KWin::ApplicationX11::notify(this=0x7fffe498,
o=0x7fffe498, e=0x7fffd128) + 87 at main_x11.cpp:277
frame #15: 0x00080ab85dcd
libQt5Core.so.5`QCoreApplication::notifyInternal2(receiver=0x7fffe498,
event=0x7fffd128) + 269 at qcoreapplication.cpp:988
frame #16: 0x00080ab8a8d8
libQt5Core.so.5`QCoreApplication::sendEvent(receiver=0x7fffe498,
event=0x7fffd128) + 56 at qcoreapplication.h:231
frame #17: 0x00080abcd2a3
libQt5Core.so.5`QObjectPrivate::setParent_helper(this=0x000816a58c30,
o=0x) + 371 at qobject.cpp:1996
frame #18: 0x00080abccf8b
libQt5Core.so.5`QObject::~QObject(this=0x000816b8fa00) + 2203 at
qobject.cpp:1048
frame #19: 0x000800ee6060
libkwin.so.5`KWin::Platform::~Platform(this=0x000816b8fa00) + 96 at
platform.cpp:45
frame #20: 0x00081bc1309d
KWinX11Platform.so`KWin::X11StandalonePlatform::~X11StandalonePlatform(this=0x000816b8fa00)
+ 61 at x11_platform.cpp:66
frame #21: 0x00081bc130c9
KWinX11Platform.so`KWin::X11StandalonePlatform::~X11StandalonePlatform(this=0x000816b8fa00)
+ 25 at x11_platform.cpp:66
frame #22: 0x00080ab78219
libQt5Core.so.5`QLibraryPrivate::unload(this=0x000816ba0240,
flag=UnloadSys) + 137 at qlibrary.cpp:562
frame #23: 0x00080ab7ae17 libQt5Core.so.5`QLibraryStore::cleanup()
+ 231 at
qlibrary.cpp:405
frame #24: 0x00080ab7a759 libQt5Core.so.5`qlibraryCleanup() + 9 at
qlibrary.cpp:427

frame #25: 0x00080ab77a71 libQt5Core.so.5`(anonymous
namespace)::qlibraryCleanup_dtor_class_::~qlibraryCleanup_dtor_class_(this=0x00080b0c62e0)
+ 17 at
qlibrary.cpp:429

frame #26: 0x00080bb2fe22 libc.so.7`__cxa_finalize +
306

frame #27: 0x00080a887524 libQt5Core.so.5`__do_global_dtors_aux +
36

frame #28: 0x00080ac95451
libQt5Core.so.5

frame #29: 0x000800606de9 ld-elf.so.1`??? +
681

frame #30: 0x00080060604b ld-elf.so.1`??? +
43

frame #31: 0x00080bb2fe26 libc.so.7`__cxa_finalize +
310

frame #32: 0x00080babf191 libc.so.7`exit +
33

frame #33: 0x00080082a56b

[k3b] [Bug 380064] [MATSHITA BD-MLT UJ240AS] Estimated writing speed: 4046 KB/s (0,9x)*?

[Cristian Aravena Romero]

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

Cristian Aravena Romero  changed:

   What|Removed |Added

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

--- Comment #18 from Cristian Aravena Romero  ---
https://cgit.kde.org/k3b.git/commit/?id=c8ed0188800a5b8e010a6f25fc9e7d8af363892a

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

[plasmashell] [Bug 381213] New: Plasma crash on ctrl tab

[Hector Gonzalez]

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

Bug ID: 381213
   Summary: Plasma crash on ctrl tab
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: hhg...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashes: i was moving from Chrome to
nautilus to see a download, and then plasma crash with out explanation

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
write () at ../sysdeps/unix/syscall-template.S:84
[Current thread is 1 (Thread 0x7fc98d4b68c0 (LWP 2139))]

Thread 16 (Thread 0x7fc8a9ffb700 (LWP 11148)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc9882c4a5b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fc8d4bb02bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7fc8d4bb44e8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fc8d4baf46d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fc8d4bb4542 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fc8d4baf46d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fc8d4bb2353 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fc9882c37be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fc9873b06ba in start_thread (arg=0x7fc8a9ffb700) at
pthread_create.c:333
#10 0x7fc987bd982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fc8aa7fc700 (LWP 11147)):
[KCrash Handler]
#6  0x7fc987b08428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fc987b0a02a in __GI_abort () at abort.c:89
#8  0x7fc987b4a7ea in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x7fc987c632e0 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9  0x7fc987b52e0a in malloc_printerr (ar_ptr=,
ptr=, str=0x7fc987c633f0 "double free or corruption (out)",
action=3) at malloc.c:5004
#10 _int_free (av=, p=, have_lock=0) at
malloc.c:3865
#11 0x7fc987b5698c in __GI___libc_free (mem=) at
malloc.c:2966
#12 0x7fc8b2564e6f in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#13 0x7fc8b25655fd in mdb_env_open () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#14 0x7fc8b27752ca in Baloo::Database::open(Baloo::Database::OpenMode) ()
from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#15 0x7fc8b2bd11e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#16 0x7fc8b2bc2b99 in Baloo::Query::exec() () from
/usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#17 0x7fc8b2de3f2f in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#18 0x7fc8b2de4879 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#19 0x7fc8d569a540 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () from
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5
#20 0x7fc8d4bb3c90 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#21 0x7fc8d4bb27e0 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#22 0x7fc8d4bb228a in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#23 0x7fc9882c37be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7fc9873b06ba in start_thread (arg=0x7fc8aa7fc700) at
pthread_create.c:333
#25 0x7fc987bd982d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fc8aaffd700 (LWP 11146)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc9882c4a5b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fc8d4bb02bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from 

[plasma-pa] [Bug 381211] Crashed while I was changing volume level.

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Component|general |applet
   Assignee|k...@davidedmundson.co.uk|now...@gmail.com
Product|plasmashell |plasma-pa
   Target Milestone|1.0 |---

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

[frameworks-kio] [Bug 381212] New: Usability and legibility suggestion on user@domain paths (i.e.: fish://user@ip:path)

[Rafael]

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

Bug ID: 381212
   Summary: Usability and legibility suggestion on user@domain
paths (i.e.: fish://user@ip:path)
   Product: frameworks-kio
   Version: 5.35.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: rafael.linux.u...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

For usability, I think it will be fine to narrow distance between some
elements. Let me show what I'm talking about, reading my wish for Krusader
https://bugs.kde.org/show_bug.cgi?id=380878.

You can see what I'm talking about seeing image
https://bugsfiles.kde.org/attachment.cgi?id=105962  (take into account that
where I put "stretched" I should type "narrowed".

Thank you

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

[krusader] [Bug 380878] fish protocol: Show user when logged in

[Rafael]

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

--- Comment #6 from Rafael  ---
Thank you for the information. I didn't know these details.
I'll suggest it to KIO developers. 

Best regards

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

[plasmashell] [Bug 381211] New: Crashed while I was changing volume level.

[Nota]

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

Bug ID: 381211
   Summary: Crashed while I was changing volume level.
   Product: plasmashell
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: 10.j...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
Changing volume level. I have changed the default volume step option from 3% to
2% and when i tried to change the volume level in the volume control icon on
the panel, Plasma crashed.

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

Thread 16 (Thread 0x7fa565794700 (LWP 4952)):
#0  0x7fa6570242bd in poll () at /usr/lib/libc.so.6
#1  0x7fa651bdfbf9 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa651bdfd0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa65794ce9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa6578f321a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa65771540a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa65a884645 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7fa657719cbd in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa6568e2297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa65702e25f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7fa56d3b8700 (LWP 842)):
#0  0x7fa6570242bd in poll () at /usr/lib/libc.so.6
#1  0x7fa651bdfbf9 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa651bdfd0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa65794ce9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa6578f321a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa65771540a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa657719cbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7fa6568e2297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fa65702e25f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fa574939700 (LWP 836)):
#0  0x7fa6570242bd in poll () at /usr/lib/libc.so.6
#1  0x7fa651bdfbf9 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa651bdfd0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa65794ce9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa6578f321a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa65771540a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa578e5f427 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7fa657719cbd in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa6568e2297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa65702e25f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fa59eb67700 (LWP 828)):
#0  0x7ffc9e8cc937 in  ()
#1  0x7ffc9e8ccbcb in clock_gettime ()
#2  0x7fa65703b7b6 in clock_gettime () at /usr/lib/libc.so.6
#3  0x7fa65794c041 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fa65794a879 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#5  0x7fa65794ae55 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#6  0x7fa65794c47e in  () at /usr/lib/libQt5Core.so.5
#7  0x7fa651bdf138 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#8  0x7fa651bdfb2b in  () at /usr/lib/libglib-2.0.so.0
#9  0x7fa651bdfd0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#10 0x7fa65794ce9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#11 0x7fa6578f321a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#12 0x7fa65771540a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#13 0x7fa65b43c836 in  () at /usr/lib/libQt5Quick.so.5
#14 0x7fa657719cbd in  () at /usr/lib/libQt5Core.so.5
#15 0x7fa6568e2297 in start_thread () at /usr/lib/libpthread.so.0
#16 0x7fa65702e25f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fa5a562a700 (LWP 801)):
#0  0x7fa6568e839d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa6308bb2fb in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7fa6308bb037 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7fa6568e2297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa65702e25f in clone () at 

[plasma-nm] [Bug 362729] [Openconnect] Cannot connect to OpenConnect VPN with username/password

[Joe]

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

--- Comment #9 from Joe  ---
So that bug didn't fix this issue for me, but, 380399 finally has, which is
awesome.

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

[kwin] [Bug 381210] New: kwin>=5.10.0 crashes immediately on start on FreeBSD

[Tobias Berner]

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

Bug ID: 381210
   Summary: kwin>=5.10.0 crashes immediately on start on FreeBSD
   Product: kwin
   Version: 5.10.0
  Platform: Other
OS: FreeBSD
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tcber...@gmail.com
  Target Milestone: ---

Since the update to 5.10.* kwin_x11 crashes immediately on startup as reported
in [1] and [2].



[1] https://mail.kde.org/pipermail/kde-freebsd/2017-June/026159.html
[2] https://mail.kde.org/pipermail/kde-freebsd/2017-June/026176.html

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

[krusader] [Bug 381022] RFE: enable Primary Clipboard support on "edit location"

[Alex Bikadorov]

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

--- Comment #14 from Alex Bikadorov  ---
* Desktop Environment (KDE, Gnome, ...) and/or window manager (OpenBox, ...).
* KDE Frameworks 5

Can you please install Dolphin temporary or at least test with other KDE
applications (Kate, KWrite, Konqueror, KMail, ...)? I think it's a general
problem and has nothing directly to do with Krusader. We don't implement
copy related stuff ourself but rely on the UI framework -> Qt.

Additional to the desktop environment please just post the information shown in
Krusader->Help->About Krusader->Libraries

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

[Discover] [Bug 379943] Text in updater section is pale when using a dark theme

[Aleix Pol]

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

--- Comment #5 from Aleix Pol  ---
It should use the KDE color scheme (see Kirigami.Theme)

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

[okular] [Bug 381209] Print to PDF file with more than one page per sheet doesn't work (instead it prints only one per sheet)

[Elias Vanderstuyft]

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

Elias Vanderstuyft  changed:

   What|Removed |Added

 CC||elias@gmail.com

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

[okular] [Bug 381209] New: Print to PDF file with more than one page per sheet doesn't work (instead it prints only one per sheet)

[Elias Vanderstuyft]

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

Bug ID: 381209
   Summary: Print to PDF file with more than one page per sheet
doesn't work (instead it prints only one per sheet)
   Product: okular
   Version: 0.26.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: printing
  Assignee: okular-de...@kde.org
  Reporter: elias@gmail.com
  Target Milestone: ---

Created attachment 106100
  --> https://bugs.kde.org/attachment.cgi?id=106100=edit
Screenshot of the print dialog triggering the issue

Steps to reproduce:

1. Open a multi-page PDF file with Okular, e.g.,
http://www.ets.org/Media/Tests/GRE/pdf/gre_research_validity_data.pdf
2a. Click "File"->"Print"
2b. Select "Print to File (PDF)"
2c. Select a valid location for "Output file:"
2d. Press "Options >>"
2e. Open the "Pages" tab
2f. Select a number higher than one in the "Pages Per Sheet" groupbox, e.g.,
"6"
2g. Press "Print"
3. Verify the output file
=> Observed: the output file contains 1 page per sheet
=> Expected: the output file contains 6 pages per sheet

It would be nice if this would work, currently I have to switch to using
GNOME's 'Documentviewer' to get the job done, there it works fine.

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

[kirigami] [Bug 381185] Scrolling down on Settings with mouse wheel cause list to "flick"

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

  Component|discover|general
Product|Discover|kirigami
   Assignee|aleix...@kde.org|notm...@gmail.com
Version|5.10.1  |Master
   Target Milestone|--- |Not decided

--- Comment #1 from Aleix Pol  ---
I think it was fixed, can you confirm marco?

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

[neon] [Bug 381183] latest libzip4 package breaks applications

[Leandro Martins de Sá]

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

Leandro Martins de Sá  changed:

   What|Removed |Added

 CC||leandrosa.e...@gmail.com

--- Comment #1 from Leandro Martins de Sá  ---
Problem happened here too.
Thanks, this solved my problem with the workbench.

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

[kdenlive] [Bug 381208] New: Kdenlive crashes on exit and messing up Backupfile

[bugzilla_noreply]

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

Bug ID: 381208
   Summary: Kdenlive crashes on exit and messing up Backupfile
   Product: kdenlive
   Version: 17.04.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: vor...@z-ray.de
  Target Milestone: ---

Created attachment 106099
  --> https://bugs.kde.org/attachment.cgi?id=106099=edit
Backtrace of Dr Konqi because sendind the error via Dr Konqi failed
mutlipletimes

I was just saving the project and exiting Kdenlive.
After the next restart Kdenlive asked me to restore the last session or don't,
if I openign the backup version all transisions where mixed up and some where
missing.
If I don't restore the last session and just open it, everything ist fine.
Also I had a temporary bug, that I was not able to click Compositing
Transissionnodes and Kdenlive was crashing instantly.

The crash can be reproduced every time.

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

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

[wintonian]

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

--- Comment #6 from wintonian  ---
Okey I spoke too soon - it's just crashed again :(

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

[konsole] [Bug 380799] Konsole remembers window size across launches, but not position

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #4 from kishor...@gmail.com ---
(In reply to Nate Graham from comment #3)
> If I choose "Centered", then the window spawns in the center of the screen.
> But that's not what I want. I want it to spawn in the same location that it
> was in the last time I closed it. Size is already correctly remembered
> across launches in this manner, but location isn't.
> 
> I am aware of workarounds such as KWin positioning rules. Workarounds are
> great, but even greater is fixing the bug that requires the workaround! :)

There is an option called placement option called 'smart', which if I
understand correctly, will do what you want.

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

[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar

[Alex6]

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

--- Comment #19 from Alex6  ---
There was no anticonstructivism in my comments (on the contrary!) to the people
who try to rebuild Konqueror. Thanks, David Faure (and eventual coworkers) !!!

But, it's true, a little caustic concerning the decision to "kill" konqueror
and spend work to write a kde-thunar with less features...

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

[kwin] [Bug 380476] Kwin draws 1px overlay on the left screen border

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

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

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

[wintonian]

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

--- Comment #5 from wintonian  ---
Possibly, but I tried (and installed) HexChat with exactly the same results as
reported at red Hat; https://bugzilla.redhat.com/show_bug.cgi?id=1461502.

Interestingly I am currently using an older kernel i.e. 4.10.5-200.fc25.x86_64,
and not had any crashes yet.

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

[systemsettings] [Bug 364902] Add option to respect Windows hidden files on auto-mounted drives

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

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

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

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #4 from kishor...@gmail.com ---
Is this bug related to https://bugs.kde.org/show_bug.cgi?id=378854 ?

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

[plasmashell] [Bug 380801] KDE applications menu crash after typing a few characters.

[Henrique de Moraes Holschuh]

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

--- Comment #4 from Henrique de Moraes Holschuh  ---
(In reply to Christoph Feck from comment #3)
> Henrique, I can assure you that this (randomly occuring) crash is not
> related to Intel microcode. It also happens on AMD systems.

Christoph, thank you very much for the information!

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

[kwin] [Bug 381205] Toggle presents windows shortcut does not toggle 'off'

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #1 from kishor...@gmail.com ---
Duplicate of https://bugs.kde.org/show_bug.cgi?id=380902

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

[plasmashell] [Bug 380866] Images become yellow pixelated upon closing and opening laptop

[bugzilla_noreply]

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

--- Comment #3 from lingtj...@hotmail.com ---
Err, I'm not sure if it is suspended or not but... I can tell you this...

- if I just wait until my laptop screen turns off and then press a button to
open the login screen then it also creates this effect.

- if I press ctrl+alt+l then it doesn't create this yellow pixelation effect

I have the options:

energy saving -> button events handling -> when laptop lid closed: suspend
energy saving -> suspend session -> after: 5 mins

Yes I am using NVIDIA drivers

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

[plasmashell] [Bug 381160] Battery plasmoid does not show a notification that an application is inhibiting screenlock when it uses xdg-screensaver to do so

[bugzilla_noreply]

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

--- Comment #2 from kishor...@gmail.com ---
(In reply to Kai Uwe Broulik from comment #1)
> When I run xdg-screensaver from console I can see it telling
> org.freedesktop.ScreenSaver on DBus which in turn tells PowerDevil.  Then it
> immediately uninhibits because the application (xdg-screensaver) that
> requested the inhibition quit.
> 
> powerdevil: Scheduling inhibition from ":1.10" "0x5a5" with cookie 1 and
> reason "xdg-screensaver"
> powerdevil: Releasing inhibition with cookie  1
> 
> I don't actually have mpv installed here, so I don't know if this behavior
> applies to it at all. I just don't understand why the inhibition still holds
> after it, screen locker also uninhibits in this case. Are you sure the
> inhibition is applied? Perhaps it's doing another thing (simulate user
> activity) repeatedly.
> 
> In any case the "appName" which is ":1.10" with reason "xdg-screensaver" is
> just plain wrong and perhaps that causes the issue of it not showing up,
> ":1.10" is not a valid application name after all.

It seems mpv calls 'xdg-screensaver reset' at regular intervals
(https://github.com/mpv-player/mpv/issues/3851).

However, as a test, I got the window ID of my konsole window using 'xwininfo',
and then ran 'xdg-screensaver suspend 0x386' (0x386 was the window ID).
I was still not able to see any notification in the battery monitor plasmoid or
any new messages in my system logs (running 'journalctl -f').

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

[plasmashell] [Bug 378700] There is gap on the right of every invoked tray icon

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #10 from Christoph Feck  ---
Thanks for the update; closing.

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

[frameworks-kio] [Bug 380810] Context menu not usable with a lot of folders

[Trebol-a]

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

--- Comment #3 from Trebol-a  ---
Perhaps some method of scrolling and reducing the maximum size of the
context window would suffice


2017-06-14 17:57 GMT+02:00 Alberto Garcia Quesada :

> No, of course,
> ignore the current dirname or filename, The problem is not the name but
> the quantity and the behavior in a multimonitor system
>
> 2017-06-14 17:37 GMT+02:00 Christoph Feck :
>
>> https://bugs.kde.org/show_bug.cgi?id=380810
>>
>> --- Comment #1 from Christoph Feck  ---
>> Well, if you had a folder for every month it would be managable. But what
>> I see
>> is a folder for every day.
>>
>> Do you expect the menu to automatically understand months vs. days and
>> create
>> groups automatically?
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>>
>
>

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

[frameworks-kio] [Bug 380810] Context menu not usable with a lot of folders

[Trebol-a]

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

--- Comment #2 from Trebol-a  ---
No, of course,
ignore the current dirname or filename, The problem is not the name but the
quantity and the behavior in a multimonitor system

2017-06-14 17:37 GMT+02:00 Christoph Feck :

> https://bugs.kde.org/show_bug.cgi?id=380810
>
> --- Comment #1 from Christoph Feck  ---
> Well, if you had a folder for every month it would be managable. But what
> I see
> is a folder for every day.
>
> Do you expect the menu to automatically understand months vs. days and
> create
> groups automatically?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita

[KDE Neon user]

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

KDE Neon user  changed:

   What|Removed |Added

 OS|Linux   |All

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

[krita] [Bug 365222] Custom buttons disappear from toolbar after restarting Krita

[KDE Neon user]

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

KDE Neon user  changed:

   What|Removed |Added

Version|3.0 |3.1.4

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

[plasmashell] [Bug 380866] Images become yellow pixelated upon closing and opening laptop

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #2 from Christoph Feck  ---
Did the laptop suspend when closing the cover? Are you using NVIDIA drivers?

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

[frameworks-kio] [Bug 380810] Context menu not usable with a lot of folders

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Well, if you had a folder for every month it would be managable. But what I see
is a folder for every day.

Do you expect the menu to automatically understand months vs. days and create
groups automatically?

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

[plasmashell] [Bug 380801] KDE applications menu crash after typing a few characters.

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
Henrique, I can assure you that this (randomly occuring) crash is not related
to Intel microcode. It also happens on AMD systems.

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