[frameworks-baloo] [Bug 384209] New: Confusing error message when mmap() fails

[Marc Mezzarobba]

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

Bug ID: 384209
   Summary: Confusing error message when mmap() fails
   Product: frameworks-baloo
   Version: 5.37.0
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: pinak.ah...@gmail.com
  Reporter: marc+b...@mezzarobba.net
  Target Milestone: ---

It would be nice it the following could give a more helpful error:

$ ulimit -Sv $((6*1024*1024))
$ balooctl enable
Failed to create database, removing corrupted database.
Failed to create database after deleting corrupted one.

(Probably related to bug 364042.)

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

[bugs.kde.org] [Bug 383753] Consider changing some resolution statuses in bugs.kde.org to avoid making some people feel bad

[Boudewijn Rempt]

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

--- Comment #4 from Boudewijn Rempt  ---
On Wed, 30 Aug 2017, Christoph Feck wrote:

> https://bugs.kde.org/show_bug.cgi?id=383753
> 
> --- Comment #3 from Christoph Feck  ---
> > I'm marking this as RESOLVED INVALID, which just means that it's not our 
> > bug.
> 
> We have UPSTREAM and DOWNSTREAM to indicate that it is not our bug. Do you 
> know
> of tickets that we need to correct?

Here's a bug that I close as invalid:

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

> 
> > WONTFIX implies that we know it's a bug, but are [...] refusing to fix it
> 
> WONTFIX should not be used for bugs. The exception is when WONTFIX is used as
> in CANNOTFIX (because of requirements or limitations of the underlying
> components), such as X11 requiring grabs for popups, etc. If a developer is 
> not
> able to fix a bug, the ticket must remain open. Again, do you know of tickets
> where a developer used this resolution incorrectly?

I use wontfix when the report is about something that shouldn't be "fixed" --
the reporter doesn't know how blending mode maths work, for instance, and
demands
that the 2 * 2 becomes 3.

> For feature request, a developer may decide that the feature should never be
> added and use the WONTFIX solution. The alternative to marking feature 
> requests
> as WONTFIX is keeping them open. This is the norm, because a future developer
> might have a different opinion than the developer who first decided this. If,
> however, multiple developers raised valid points against a feature, it makes
> sense to close as WONTFIX. If it was a useful idea, it will be suggested again
> years later anyway, so a different batch of developers can decide anew.
> 
> > I'd also like a TRIAGED_COULD_NOT_CONFIRM
> 
> We have keywords, such as "triaged", "investigated", "reproducible",
> "needs_testcase" and "needs_verification".

Yeah, but what resolution belongs to that?

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

[krita] [Bug 384202] Fix Resize and text tool!!!!!

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---
Sorry, this bug report is not useful. We are working on a new text tool
already. And I have no idea what you mean with the rest of your report. A
useful bug report is about one issue and explains how to reproduce that issue.

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

[krita] [Bug 384195] empty window on no action with toolbar new button

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||b...@valdyas.org

--- Comment #2 from Boudewijn Rempt  ---
Yes, we definitely need more information. Please also attach the contents of
help/show system information to the report.

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

[kmail2] [Bug 384180] Special characters in attachment names are displayed improperly

[Martin Pola]

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

Martin Pola  changed:

   What|Removed |Added

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

--- Comment #2 from Martin Pola  ---
The example I provided was from an e-mail message sent on June 2, 2017. I just
tried again, and I couldn't reproduce the problem either. Perhaps it has
already been fixed? Nevertheless, I am sorry for wasting your time.

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

[krita] [Bug 384187] [XP-Star] Graphics tablet buttons not working

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Summary|Graphics tablet buttons not |[XP-Star] Graphics tablet
   |working |buttons not working

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

[krita] [Bug 384187] [XP-Star] Graphics tablet buttons not working

[Boudewijn Rempt]

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

--- Comment #4 from Boudewijn Rempt  ---
So it's specifically about the buttons on the tablet itself? How are they
configured, and what keypresses are they supposed to send?

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

[dolphin] [Bug 384210] New: Dolphin hanged during usage

[Germano Massullo]

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

Bug ID: 384210
   Summary: Dolphin hanged during usage
   Product: dolphin
   Version: 17.04.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: germano.massu...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

While I was using my system, Amarok hanged, then Dolphin too. Aware of
gam_server bug, I tried to kill it, but this has not solved the problem.

$ gdb dolphin 3268
GNU gdb (GDB) Fedora 8.0-24.fc26
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from dolphin...Reading symbols from
/usr/lib/debug/usr/bin/dolphin.debug...done.
done.
Attaching to program: /usr/bin/dolphin, process 3268
[New LWP 3271]
[New LWP 3272]
[New LWP 3273]
[New LWP 3274]
[New LWP 3275]
[New LWP 3276]
[New LWP 3277]
[New LWP 3278]
[New LWP 3280]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x7fed1daff43d in nanosleep () at ../sysdeps/unix/syscall-template.S:84
84  T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
Missing separate debuginfos, use: dnf debuginfo-install
compat-openssl10-1.0.2j-6.fc26.x86_64
(gdb) thread apply all backtrace

Thread 10 (Thread 0x7fecef9d3700 (LWP 3280)):
#0  0x7fed1db2facd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fed16720569 in g_main_context_poll (priority=,
n_fds=1, fds=0x7fece8002e20, timeout=, context=0x7fece8000990)
at gmain.c:4271
#2  0x7fed16720569 in g_main_context_iterate
(context=context@entry=0x7fece8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at gmain.c:3967
#3  0x7fed1672067c in g_main_context_iteration (context=0x7fece8000990,
may_block=may_block@entry=1) at gmain.c:4033
#4  0x7fed1e946e4f in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fece80008c0, flags=...)
at kernel/qeventdispatcher_glib.cpp:423
#5  0x7fed1e8f760a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fecef9d2c70, flags=..., flags@entry=...)
at kernel/qeventloop.cpp:212
#6  0x7fed1e74f99a in QThread::exec() (this=) at
thread/qthread.cpp:507
#7  0x7fed1e753c9e in QThreadPrivate::start(void*) (arg=0x2b5b923bf0) at
thread/qthread_unix.cpp:368
#8  0x7fed1b47036d in start_thread (arg=0x7fecef9d3700) at
pthread_create.c:456
#9  0x7fed1db3bbbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 9 (Thread 0x7fecf3909700 (LWP 3278)):
#0  0x7fed1b47681b in futex_wait_cancelable (private=,
expected=0, futex_word=0x2b5b748ca0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fed1b47681b in __pthread_cond_wait_common (abstime=0x0,
mutex=0x2b5b748c50, cond=0x2b5b748c78) at pthread_cond_wait.c:502
#2  0x7fed1b47681b in __pthread_cond_wait (cond=0x2b5b748c78,
mutex=0x2b5b748c50) at pthread_cond_wait.c:655
#3  0x7fecfa1c86ab in cnd_wait (mtx=0x2b5b748c50, cond=0x2b5b748c78) at
../../include/c11/threads_posix.h:159
#4  0x7fecfa1c86ab in util_queue_thread_func
(input=input@entry=0x2b5b749860) at u_queue.c:158
---Type  to continue, or q  to quit---
#5  0x7fecfa1c83e7 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7fed1b47036d in start_thread (arg=0x7fecf3909700) at
pthread_create.c:456
#7  0x7fed1db3bbbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 8 (Thread 0x7fecf410a700 (LWP 3277)):
#0  0x7fed1b47681b in futex_wait_cancelable (private=,
expected=0, futex_word=0x2b5b748ca0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fed1b47681b in __pthread_cond_wait_common (abstime=0x0,
mutex=0x2b5b748c50, cond=0x2b5b748c78) at pthread_cond_wait.c:502
#2  0x7fed1b47681b in __pthread_cond_wait (cond=0x2b5b748c78,
mutex=0x2b5b748c50) at pthread_cond_wait.c:655
#3  0x7fecfa1c86ab in cnd_wait (mtx=0x2b5b748c50, cond=0x2b5b748c78) at
../../include/c11/threads_posix.h:159
#4  0x7fecfa1c86ab in util_queue_thread_func
(input=input@entry=0x2b5b749670) at u_queue.c:158
#5  0x7fecfa1c83e7 in impl_thrd_routine (p=) at
../../include/c11/threads_posix.h:87
#6  0x7fed1b47036d in start_thread (arg=0x7fecf410a700) at
pthre

[amarok] [Bug 384211] New: Amarok hangs

[Germano Massullo]

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

Bug ID: 384211
   Summary: Amarok hangs
   Product: amarok
   Version: 2.8.90 (2.9 beta)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: germano.massu...@gmail.com
  Target Milestone: 2.9

Created attachment 107609
  --> https://bugs.kde.org/attachment.cgi?id=107609&action=edit
crashreport

While I was using my system, Amarok hanged, then Dolphin too. Aware of
gam_server bug, I tried to kill it, but this has not solved the problem.

I attached the gdb trace.

In case you may want to investigate, the dolphin bugreport is
https://bugs.kde.org/show_bug.cgi?id=384210

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

[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive

[Jens Reuterberg]

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

Jens Reuterberg  changed:

   What|Removed |Added

 CC||jens...@kolabnow.com

--- Comment #20 from Jens Reuterberg  ---
The reason other icons are there is because the Get Hot New Stuff is linked to
a webpage which is not directly controlled by KDE that used to be called KDE
look, and which was mirrored by sites like gnome-look and openbox-look etc.

That means that many of the icon themes are in fact GTK icon themes and, as you
noticed, unsuitable for KDE (this is the confusing part of KDE look and Get Hot
New Stuff - its not communicated clearly enough that this is a third party area
and not something native)

The elementary theme Andreas mentions is the one called Elementary-KDE in Get
Hot New Stuff

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

[dolphin] [Bug 384210] Dolphin hanged during usage

[Germano Massullo]

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

--- Comment #1 from Germano Massullo  ---
In case you may want to investigate, the amarok bugreport is
https://bugs.kde.org/show_bug.cgi?id=384211

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

[korgac] [Bug 384212] New: No reminder dialogs are triggering

[Andreas Schneider]

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

Bug ID: 384212
   Summary: No reminder dialogs are triggering
   Product: korgac
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: a...@cryptomilk.org
  Target Milestone: ---

I've updated to KDE Applications 17.08.0 but had the issue also before. But the
issue also appeared before the update to 17.08.

I'm running openSUSE Tumbleweed.

If I create a new calender entry in 10 minutes and say to trigger a reminder
dialog in 5 minutes nothing will happpen.

Please assist in debugging the issue.


I'm gladiac at #kde-devel

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

[akregator] [Bug 384213] New: Kontact opens but Akregator shows no feeds.

[Dave Morley]

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

Bug ID: 384213
   Summary: Kontact opens but Akregator shows no feeds.
   Product: akregator
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kontact plugin
  Assignee: kdepim-b...@kde.org
  Reporter: davm...@davmor2.co.uk
  Target Milestone: ---

Created attachment 107610
  --> https://bugs.kde.org/attachment.cgi?id=107610&action=edit
Screenshot showing lack of feeds

DATE:
2017-08-31

OS:
KDE Neon 5.10.5

PACKAGE:
akregator 4:17.08.0-0neon+16.04+xenial+build24 amd64

STEPS:
1. Start the system
2. Open Kontact
3. Move to the Akregator page in Kontact
4. Close Kontact completely
5. Restart the system
6. Reopen Kontact

EXPECTED:
I expect Akregator to display the feed list and any new articles

ACTUAL:
Half the time it does the other half it doesn't see attached screenshot

If there is any additional info please put in accurate steps and I can follow
them and give you the info.

Many thanks, keep up the good work.

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

[korganizer] [Bug 384075] korganizer crashes on startup

[Achim Bohnet]

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

Achim Bohnet  changed:

   What|Removed |Added

 CC||a...@mpe.mpg.de

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

[plasmashell] [Bug 384214] New: Plasma shell crash when dragging panel to other screen

[Szaman]

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

Bug ID: 384214
   Summary: Plasma shell crash when dragging panel to other screen
   Product: plasmashell
   Version: 5.8.7
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: wolfm...@o2.pl
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.7)

Qt Version: 5.9.1
Frameworks Version: 5.28.0
Operating System: Linux 4.12.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
I have 3 monitors connected through 3 display ports. I'm using open source
radeondrm drivers. When all 3 monitors goes to sleep and are later awaken, then
there are no panels, looks like plasma shell restarts.

When I try to add new panel it appears on the last onitor, and when I try to
drag it to other monitor then plasmashell crashes again.

The crash can be reproduced every time.

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

Thread 13 (Thread 0x7f34f96da700 (LWP 5877)):
#0  0x7f35e0d5666d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f35dbc2a119 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f35dbc2a22c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f35e167541b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f35e161adba in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f35e143a3ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f35e47f39d5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f35e143f29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f35e0559494 in start_thread (arg=0x7f34f96da700) at
pthread_create.c:333
#9  0x7f35e0d5fabf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 12 (Thread 0x7f352bdbe700 (LWP 5861)):
#0  0x7f35e0d5666d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f35dbc2a119 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f35dbc2a22c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f35e167541b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f35e161adba in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f35e143a3ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f35e51937e6 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f35e143f29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f35e0559494 in start_thread (arg=0x7f352bdbe700) at
pthread_create.c:333
#9  0x7f35e0d5fabf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 11 (Thread 0x7f3530860700 (LWP 5860)):
#0  0x7f35e055f15f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f353746979b in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7f35374694c7 in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7f35e0559494 in start_thread (arg=0x7f3530860700) at
pthread_create.c:333
#4  0x7f35e0d5fabf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 10 (Thread 0x7f3531061700 (LWP 5859)):
#0  0x7f35e055f15f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f353746979b in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7f35374694c7 in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7f35e0559494 in start_thread (arg=0x7f3531061700) at
pthread_create.c:333
#4  0x7f35e0d5fabf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 9 (Thread 0x7f3531862700 (LWP 5858)):
#0  0x7f35e055f15f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f353746979b in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7f35374694c7 in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#3  0x7f35e0559494 in start_thread (arg=0x7f3531862700) at
pthread_create.c:333
#4  0x7f35e0d5fabf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 8 (Thread 0x7f3532063700 (LWP 5857)):
#0  0x7f35e055f15f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f353746979b in  () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#2  0x7f35374694c7 in  () at /usr/lib/x86_64

[frameworks-kio] [Bug 384215] New: Short freezes with KDE applications when sharing directories via Samba

[Teunizz]

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

Bug ID: 384215
   Summary: Short freezes with KDE applications when sharing
directories via Samba
   Product: frameworks-kio
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: teu...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

System: Opensuse Leap 42.2 & plasmashell 5.8.6

Applications that depend on KDE libs/framework, suffer from freezes during
fileactivity when sharing directories and a Samba server is running.

During those freezes the network interface is flooded with DNS requests trying
to resolve the hostname of the system.

How to reproduce:

In Yast2, enable/setup a Samba server. Startup -> During Boot. Shares ->
Disable all available shares. Check Allow Users to Share Directories. Check
Allow Guest Access.

In Dolphin, select a couple of directories to share. Rightclick on it and
select Properties -> Share. Check Share with Samba. Check Allow Guests.

Reboot.

Start Wireshark and filter on DNS packets only.

Start a couple of KDE-libs dependent applications like Kate (preferably with th
filesystem browser plugin activated), Okular, Dolphin, and perform some file
manipulations (copy/edit/save).

Look what happens in Wireshark.

A temporary workaround is to open Yast2 -> System -> Network Settings ->
Hostname/DNS and check Assign Hostname to Loopback IP.
It will make the desktop usable again but still not snappy.
For a snappy KDE experience, you can't share directories using the above setup.

What did I expect: to have a snappy/responsive desktop when sharing directories
using a Samba server.

Here's some output of Wireshark:

No. Time   SourceDestination   Protocol
Length Info
  1 0.0192.168.1.2   192.168.1.1   DNS  73 
   Standard query 0x53ae A cetriolo.suse

Frame 1: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on interface
0
Ethernet II, Src: AsustekC_c9:f2:f1 (48:5b:39:c9:f2:f1), Dst: Netgear_7f:3a:10
(28:c6:8e:7f:3a:10)
Internet Protocol Version 4, Src: 192.168.1.2, Dst: 192.168.1.1
User Datagram Protocol, Src Port: 38071, Dst Port: 53
Domain Name System (query)

No. Time   SourceDestination   Protocol
Length Info
  2 0.17735192.168.1.2   192.168.1.1   DNS  73 
   Standard query 0xd632  cetriolo.suse

Frame 2: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on interface
0
Ethernet II, Src: AsustekC_c9:f2:f1 (48:5b:39:c9:f2:f1), Dst: Netgear_7f:3a:10
(28:c6:8e:7f:3a:10)
Internet Protocol Version 4, Src: 192.168.1.2, Dst: 192.168.1.1
User Datagram Protocol, Src Port: 38071, Dst Port: 53
Domain Name System (query)

No. Time   SourceDestination   Protocol
Length Info
  3 0.011026167192.168.1.1   192.168.1.2   DNS  148
   Standard query response 0x53ae No such name A cetriolo.suse SOA
a.root-servers.net

Frame 3: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) on
interface 0
Ethernet II, Src: Netgear_7f:3a:10 (28:c6:8e:7f:3a:10), Dst: AsustekC_c9:f2:f1
(48:5b:39:c9:f2:f1)
Internet Protocol Version 4, Src: 192.168.1.1, Dst: 192.168.1.2
User Datagram Protocol, Src Port: 53, Dst Port: 38071
Domain Name System (response)

No. Time   SourceDestination   Protocol
Length Info
  4 0.011628077192.168.1.1   192.168.1.2   DNS  148
   Standard query response 0xd632 No such name  cetriolo.suse SOA
a.root-servers.net

Frame 4: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) on
interface 0
Ethernet II, Src: Netgear_7f:3a:10 (28:c6:8e:7f:3a:10), Dst: AsustekC_c9:f2:f1
(48:5b:39:c9:f2:f1)
Internet Protocol Version 4, Src: 192.168.1.1, Dst: 192.168.1.2
User Datagram Protocol, Src Port: 53, Dst Port: 38071
Domain Name System (response)

No. Time   SourceDestination   Protocol
Length Info
  5 0.011700108192.168.1.2   192.168.1.1   DNS  68 
   Standard query 0x8681 A cetriolo

Frame 5: 68 bytes on wire (544 bits), 68 bytes captured (544 bits) on interface
0
Ethernet II, Src: AsustekC_c9:f2:f1 (48:5b:39:c9:f2:f1), Dst: Netgear_7f:3a:10
(28:c6:8e:7f:3a:10)
Internet Protocol Version 4, Src: 192.168.1.2, Dst: 192.168.1.1
User Datagram Protocol, Src Port: 33958, Dst Port: 53
Domain Name System (query)

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

[frameworks-kio] [Bug 384215] Short freezes with KDE applications when sharing directories via Samba

[Teunizz]

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

Teunizz  changed:

   What|Removed |Added

Version|unspecified |5.8.0
 CC||teu...@gmail.com

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

[plasmashell] [Bug 384214] Plasma shell crash when dragging panel to other screen

[Szaman]

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

--- Comment #1 from Szaman  ---
I have a suspicion that it crashes not when switching monitors but when trying
to render the panel on the left or right edge (vertical layout). When I try to
move panel very fast then it sometimes reaches the other monitor without crash.

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

[korganizer] [Bug 384075] korganizer crashes on startup

[Achim Bohnet]

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

--- Comment #3 from Achim Bohnet  ---
Here is a much better stacktrace, because I've managed to install debsym pkgs.

Application: korganizer (5.6.0)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.10.0-32-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed:
 In the agenda view, selected the calender 'arbeiten' so that the events would
be shown -> crashes immediately
[always reproduceable on 4 system (kde neon user + dev stable)]

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

Thread 4 (Thread 0x7f48f6dee700 (LWP 16393)):
#0  0x7f4929a0470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f49202da38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f49202da49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f492a54294b in QEventDispatcherGlib::processEvents
(this=0x7f48e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f492a4eb7ca in QEventLoop::exec (this=this@entry=0x7f48f6dedc40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f492a314cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f492a319989 in QThreadPrivate::start (arg=0x13a1f50) at
thread/qthread_unix.cpp:368
#7  0x7f49220096ba in start_thread (arg=0x7f48f6dee700) at
pthread_create.c:333
#8  0x7f4929a103dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f48f75ef700 (LWP 16391)):
#0  0x7f4929a0470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f49202da38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f49202da49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f492a54294b in QEventDispatcherGlib::processEvents
(this=0x7f48f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f492a4eb7ca in QEventLoop::exec (this=this@entry=0x7f48f75eec40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f492a314cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f492a319989 in QThreadPrivate::start (arg=0x1031900) at
thread/qthread_unix.cpp:368
#7  0x7f49220096ba in start_thread (arg=0x7f48f75ef700) at
pthread_create.c:333
#8  0x7f4929a103dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f48fcfc3700 (LWP 16390)):
#0  0x7f4929a0470d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f49202da38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f49202da49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f492a54294b in QEventDispatcherGlib::processEvents
(this=0x7f48f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f492a4eb7ca in QEventLoop::exec (this=this@entry=0x7f48fcfc2c10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f492a314cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f492dbdab75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f492a319989 in QThreadPrivate::start (arg=0x7f492dc50da0) at
thread/qthread_unix.cpp:368
#8  0x7f49220096ba in start_thread (arg=0x7f48fcfc3700) at
pthread_create.c:333
#9  0x7f4929a103dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f4906b71980 (LWP 16388)):
[KCrash Handler]
#6  greaterThan (node1=..., node2=...) at
/workspace/build/src/todo/incidencetreemodel.cpp:48
#7  0x7f492873cbb8 in __gnu_cxx::__ops::_Val_comp_iter const&, QSharedPointer
const&)>::operator(), QList
>::iterator> (__it=..., __val=..., this=) at
/usr/include/c++/5/bits/predefined_ops.h:169
#8  std::__unguarded_linear_insert >::iterator,
__gnu_cxx::__ops::_Val_comp_iter const&,
QSharedPointer const&)> > (__last=..., __comp=__comp@entry=...) at
/usr/include/c++/5/bits/stl_algo.h:1823
#9  0x7f492873907a in
std::__unguarded_insertion_sort >::iterator,
__gnu_cxx::__ops::_Iter_comp_iter const&,
QSharedPointer const&)> > (__comp=..., __last=..., __first=...) at
/usr/include/c++/5/bits/stl_algo.h:1862
#10 std::__final_insertion_sort >::iterator,
__gnu_cxx::__ops::_Iter_comp_iter const&,
QSharedPointer const&)> > (__comp=..., __last=..., __first=...) at
/usr/include/c++/5/bits/stl_algo.h:1881
#11 std::__sort >::iterator,
__gnu_cxx::__ops::_Iter_comp_iter const&,
QSharedPointer const&)> > (__comp=..., __last=..., __first=...) at
/usr/include/c++/5/bits/stl_algo.h:1966
#12 std::sort >::iterator, bool
(*)(QSharedPointer const&, QSharedPointer const&)>
(__comp=0x7f4928733d50  const&,
QSharedPointer const&)>, __last=..., __first=...) at
/usr/include/c++/5/bits/stl_algo.h:4729
#13 sortedPrenodes (nodes=...) at
/workspace/build/src/to

[konsole] [Bug 384216] New: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

[=]

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

Bug ID: 384216
   Summary: QDBusConnection: session D-Bus connection created
before QCoreApplication. Application may misbehave.
   Product: konsole
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: rookang...@gmail.com
  Target Milestone: ---

kate(1270)/kate-filetree KateFileTreePluginView::KateFileTreePluginView: BEGIN:
mw: Kate::MainWindow(0x902e2d0)
kate(1270)/kate-filetree ProxyItem::ProxyItem:
ProxyItem(0x91eeca8,0x0,-1,QObject(0x0) ,"m_root")
kate(1270)/kate-filetree ProxyItem::ProxyItem:
ProxyItem(0x91f0058,0x0,-1,QObject(0x0) ,"Untitled")
kate(1270)/kate-filetree KateFileTreeModel::documentOpened: before add:
ProxyItem(0x91f0058,0x0,-1,KateDocument(0x912c1a8) , "Untitled" )
kate(1270)/kate-filetree KateFileTreeModel::setupIcon: BEGIN!
kate(1270)/kate-filetree KateFileTreeModel::setupIcon: END!
kate(1270)/kate-filetree KateFileTreeModel::handleInsert: BEGIN!
kate(1270)/kate-filetree KateFileTreeModel::handleInsert: empty item
kate(1270)/kate-filetree ProxyItem::addChild: added
ProxyItem(0x91f0058,0x91eeca8,0,KateDocument(0x912c1a8) , "Untitled" )   to
ProxyItemDir(0x91eeca8,0x0,-1,"m_root", children:1)
kate(1270)/kate-filetree KateFileTreeModel::documentOpened: after add:
ProxyItem(0x91f0058,0x91eeca8,0,KateDocument(0x912c1a8) , "Untitled" )
kate(1270)/kate-filetree KateFileTreeProxyModel::KateFileTreeProxyModel: BEGIN!
kate(1270)/kate-filetree KateFileTreePluginView::setListMode: BEGIN
kate(1270)/kate-filetree KateFileTreePluginView::setListMode: treeMode
kate(1270)/kate-filetree KateFileTreePluginView::setListMode: END
kate(1270)/kate-filetree KateFileTreePluginView::viewChanged: BEGIN!
kate(1270)/kate-filetree KateFileTreePluginView::viewChanged: BEGIN!
kate(1270)/kate-filetree KateFileTreeProxyModel::docIndex: !
kate(1270)/kate-filetree KateFileTreeModel::docIndex: BEGIN!
kate(1270)/kate-filetree KateFileTreeModel::docIndex: END!
kate(1270)/kate-filetree KateFileTreePluginView::viewChanged: selected doc=
KateDocument(0x912c1a8)
QModelIndex(0,0,0x9042240,KateFileTreeProxyModel(0x91f1780) )
kate(1270)/kate-filetree KateFileTreePluginView::viewChanged: display=
"Untitled"
kate(1270)/kate-filetree KateFileTreeModel::documentActivated: BEGIN!
kate(1270)/kate-filetree KateFileTreeModel::documentActivated: adding
viewHistory ProxyItem(0x91f0058,0x91eeca8,0,KateDocument(0x912c1a8) ,
"Untitled" )
kate(1270)/kate-filetree KateFileTreeModel::updateBackgrounds: BEGIN!
kate(1270)/kate-filetree KateFileTreeModel::updateBackgrounds: m_editHistory
contains  0  elements
kate(1270)/kate-filetree KateFileTreeModel::updateBackgrounds: END!
kate(1270)/kate-filetree KateFileTreeModel::documentActivated: END!
kate(1270)/kate-filetree KateFileTree::slotCurrentChanged: current:
QModelIndex(0,0,0x9042240,KateFileTreeProxyModel(0x91f1780) )  previous:
QModelIndex(-1,-1,0x0,QObject(0x0) )
kate(1270)/kate-filetree KateFileTree::slotCurrentChanged: got doc, setting
prev: QModelIndex(0,0,0x9042240,KateFileTreeProxyModel(0x91f1780) )
kate(1270)/kate-filetree KateFileTreePluginView::viewChanged: END!
kate(1270)/kate-filetree KateFileTreePluginView::viewChanged: BEGIN!
kate(1270)/kate-filetree KateFileTreeProxyModel::docIndex: !
kate(1270)/kate-filetree KateFileTreeModel::docIndex: BEGIN!
kate(1270)/kate-filetree KateFileTreeModel::docIndex: END!

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

[plasmashell] [Bug 384217] New: Applications launched via Launcher share the same volume control.

[Matthew Guiddy]

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

Bug ID: 384217
   Summary: Applications launched via Launcher share the same
volume control.
   Product: plasmashell
   Version: 5.10.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: mgui...@yahoo.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 107611
  --> https://bugs.kde.org/attachment.cgi?id=107611&action=edit
Firefox was launched via Kickoff

When launching applications via Kickoff and/or Kicker, they usually show up as
"Plasma" to pulseaudio instead of the actual application name.  It's almost
like Kickoff/Kicker is launching applications as child processes.

I've been experiencing this on and off since I first upgraded to Opensuse
Tumbleweed and Plasma5.  
Only recently tested the bug on a fresh install on a virtual machine using
Tumbleweed.

I am attaching the output of "pacmd list-sink-inputs" of Firefox launched via
Kickoff vs launched via a shortcut widget placed on the Panel.

I decided to submit the bug here instead of pulseaudio because it will
occasionally work as intended.

Reproducible: Almost always - It might work correctly for a short while after a
reboot, but it invariably starts to act up.

Steps to Reproduce:
1. Launch an application via Kickoff or Kicker
2. Play audio in the application
3. View list of sinks via pavucontrol application, Audio Volume widget, or the
command "pacmd list-sink-inputs"

Actual Results:  
Shared volume control between all applications started via Kickoff or Kicker
with "Plasma" being the application name.

Expected Results:  
Application independent volume control with the name of the application listed.

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

[plasmashell] [Bug 384217] Applications launched via Launcher share the same volume control.

[Matthew Guiddy]

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

--- Comment #1 from Matthew Guiddy  ---
Created attachment 107612
  --> https://bugs.kde.org/attachment.cgi?id=107612&action=edit
Firefox was launched via Panel shortcut widget.

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

[plasmashell] [Bug 369658] Different windows from same app show icon defined in .desktop file instead of app-specified icon

[Eike Hein]

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

--- Comment #42 from Eike Hein  ---
> it is still possible (w/o patching) to have individual task icons for a 
> multi-window program by writing a specific .desktop file, right?

1. make sure the window has a different WM_CLASS
2. deploy a .desktop file with a matching name or StartupWMClass key value

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

[plasmashell] [Bug 384172] Status information glitches on Plasma task manager

[Eike Hein]

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

--- Comment #1 from Eike Hein  ---
Kai?

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

[konsole] [Bug 384216] QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

[=]

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

=  changed:

   What|Removed |Added

 CC||rookang...@gmail.com

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

[plasmashell] [Bug 353041] Menu fails to open under specific circumstances.

[Eike Hein]

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

--- Comment #4 from Eike Hein  ---
Aye, I didn't notice at first that Alexander was going through old tickets :).

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

[plasmashell] [Bug 360212] Icon positions in folder view of the desktop are often scrambled after reboot or logout

[Eike Hein]

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

--- Comment #16 from Eike Hein  ---
FWIW: Whether the names consider non-ASCII characters or not will have zero
impact, please don't needlessly go out of your way to avoid them. It's just
superstition.

> 
Btw, how can this annoying bug still bear the "UNCONFIRMED" status is a
mystery...

Because I haven't been able to confirm or reproduce it. The status doesn't
really matter though, I see the ticket and get emails either way.

To make progress on this I need to work with one of the affected people more
closely and get debug data from their system.

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

[yakuake] [Bug 383523] Support merging tabs aka undo split

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #3 from Eike Hein  ---
Setting status appropriately.

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

[konsole] [Bug 384218] New: clear/^l shouldn't add empty lines to the scrollback buffer

[RJVB]

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

Bug ID: 384218
   Summary: clear/^l shouldn't add empty lines to the scrollback
buffer
   Product: konsole
   Version: unspecified
  Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: history
  Assignee: konsole-de...@kde.org
  Reporter: rjvber...@gmail.com
  Target Milestone: ---

Executing the `clear` command clears the current view and leaves the
prompt/cursor at the top of the window, but also adds the remaining number of
empty lines to the scrollback buffer. IOW, if you execute it when the cursor is
already at the top of a view that's N lines high, you get N empty lines in the
scrollback buffer.

That's counterproductive.

The clear manpage states that the command `clears  your screen if this is
possible, including its scrollback buffer (if the extended "E3" capability is
defined).  clear looks in the environment for the terminal type and then in the
terminfo database to determine how to clear the screen`.

I'm not certain we'd want the scrollback clearing but there must be a way to
avoid the empty lines to it.

FWIW, I use TERM=xterm, and I note that xterms (v297) behave as I'd expect
(`clear` doesn't affect the scrollback buffer contents at all).

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

[plasmashell] [Bug 384172] Status information glitches on Plasma task manager

[Yannick]

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

--- Comment #2 from Yannick  ---
(In reply to Eike Hein from comment #1)
> Kai?

Huh?

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

[plasmashell] [Bug 384172] Status information glitches on Plasma task manager

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #3 from Kai Uwe Broulik  ---
Haven't experienced that yet. In fact, I don't even get the badge with the
number here :/

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

[okular] [Bug 384185] Markdown backend does not reload automatically if the file has changed

[Oliver Sander]

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

--- Comment #4 from Oliver Sander  ---
No, I merely looked at these patches, but never tested them.

More experimentation has revealed the following: Automatic reload does work as
expected when I 'touch' the file, or when I save it from 'vi'.  It does not
work when I save it from Kate.  How can that be?

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

[plasma-integration] [Bug 384163] smplayer crashes at startup when using global menu + plasma QPA

[Kai Uwe Broulik]

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

--- Comment #1 from Kai Uwe Broulik  ---
Works here both with global menu applet and title bar menu button. smplayer
15.11.0 on Qt 5.9.1 (compiled against Qt 5.5.1 though) and MPV 0.14.0

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

[okular] [Bug 384185] Markdown backend does not reload automatically if the file has changed

[Julian Wolff]

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

Julian Wolff  changed:

   What|Removed |Added

 CC||wo...@julianwolff.de

--- Comment #5 from Julian Wolff  ---
I can confirm this too, for both markdown and txt documents (and probably
others).

In part.cpp:1729, slotFileDirty, we check if the path of a document that got
dirty matches with the file path of the currently loaded document.
When editing a document with Kate, the .kate-swp file gets dirty, but not the
actual document.

For me this seems like a bug in either Kate or KDirWatch, not in Okular.

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

[plasma-integration] [Bug 384163] smplayer crashes at startup when using global menu + plasma QPA

[Antonio Rojas]

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

--- Comment #2 from Antonio Rojas  ---
smplayer 15.11.0 also works here. Whatever triggers this has been introduced in
a later version (reproducible at least with 17.8.0)

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

[Heaptrack] [Bug 383889] Heaptrack does not build with glibc 2.26

[Bastian Beischer]

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

Bastian Beischer  changed:

   What|Removed |Added

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

--- Comment #3 from Bastian Beischer  ---
Fixed with commit f0a682550118b7019e74af71d9e8624902b8a984.

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

[plasmashell] [Bug 384172] Status information glitches on Plasma task manager

[Eike Hein]

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

--- Comment #4 from Eike Hein  ---
> Huh?

The relevant developer.

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

[kdepim] [Bug 384219] New: Kube fail to sync IMAP account from office365.com

[bugzilla_noreply]

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

Bug ID: 384219
   Summary: Kube fail to sync IMAP account from office365.com
   Product: kdepim
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: boris.sh.1983+kde.bugzi...@gmail.com
  Target Milestone: ---

Sorry for the wrong product , but it was the closest thing I could find.

Kube installed from flatpak fail to sync my IMAP account at office365. 
It chokes mid work with "A15 Bad Command error. 10 .\n Sent Command: ".

Steps to reproduce : 

Install Kube from flatpak:
1. flatpak --user install --from
https://kube.kde.org/files/org.kde.kube.flatpakref
2. sudo flatpak remote-add kderuntime --from
http://distribute.kde.org/kderuntime.flatpakrepo
3. sudo flatpak install kderuntime org.kde.Sdk
4. flatpak run --devel org.kde.kube

Prepare mailbox:
1. Setup an IMAP account on office365 
2. put 10 gb of emails in the Inbox folder, make sure to have threads (sent/
reply to the same email etc).

Setup an IMAP account on kube (imaps://outlook.office365.com:993/)
click on mail icon. 

It may be related to :

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

I would have added much more IMAP traces , but kube.kde.org doesn't explain how
to do that.

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

[plasmashell] [Bug 360212] Icon positions in folder view of the desktop are often scrambled after reboot or logout

[firewalker]

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

--- Comment #17 from firewalker  ---
Please! Fell free to instruct us as to what exactly we need to do in order to
help you. Rebuild packets with Debug enabled? What packets? 

Can you tell us what packet/process/function places icons on the desktop during
KDE loading, in order to set debug (Qdebug) "traps"? I tried to locate my self,
running through the plasma shell code, but it was more complicated than I
expected.

I believe that the process fails to read part of the file with the icons
coordinates. At least partially

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

[korgac] [Bug 384212] No reminder dialogs are triggering

[Andreas Schneider]

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

Andreas Schneider  changed:

   What|Removed |Added

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

--- Comment #1 from Andreas Schneider  ---
This has been fixed with:

https://cgit.kde.org/akonadi.git/commit/?h=Applications/17.08&id=d3c6ba904798768b0c83c2e182c27b1c624f78ca

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

[kdepim] [Bug 384219] Kube fail to sync IMAP account from office365.com

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Laurent Montel  ---
Better to send email directly to maintainer as for sure nobody here will fix
it.
kube != kdepim
so we will not fix it.

Sorry
Regards

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

[marble] [Bug 381984] Some countries are invisible on the political map

[Oleg Solovyov]

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

--- Comment #1 from Oleg Solovyov  ---
Fix revision: https://phabricator.kde.org/D7625

https://phabricator.kde.org/D7625

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

[plasmashell] [Bug 360212] Icon positions in folder view of the desktop are often scrambled after reboot or logout

[Florian Röhrer]

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

--- Comment #18 from Florian Röhrer  ---
It just happend again and since I have stored a backup of the file
~/.config/plasma-org.kde.plasma.desktop-appletsrc in my home folder before the
last shutdown of my system, I used this opportunity to compare the two files.
As you can see, they are obviously different. So it seems like some process is
altering the file content which describes the icon positions at system
shutdowns. Here is the comparison:

Florian@linux-vaio-tumbleweed:~> diff
/home/Florian/.config/plasma-org.kde.plasma.desktop-appletsrc
/home/Florian/plasma-org.kde.plasma.desktop-appletsrc
59c59
< positions=8,20,desktop:/Universe Cluster 2.desktop,1,4,desktop:/Unmount PC
Hard
Drive.desktop,1,5,desktop:/FPGA,6,18,desktop:/WhatsApp.desktop,5,1,desktop:/Data,6,17,desktop:/Radio
Arabella.desktop,0,18,desktop:/Signalverarbeit_950289968_(S17)-20170820.zip,0,19,desktop:/Dolphin
- root.desktop,0,16,desktop:/Ark.desktop,7,0,desktop:/Physik MSc
Fächer,0,17,desktop:/trash.desktop,1,2,desktop:/TUMOnline,1,3,desktop:/Home.desktop,1,0,desktop:/Samsung
CLX-3305FN Druckerstatus,1,1,desktop:/Network,2,0,desktop:/Universe
Cluster.desktop,4,0,desktop:/MakeMKV,0,10,desktop:/Mount LRZ
Webdisk.desktop,0,11,desktop:/kinfocenter.desktop,0,8,desktop:/LibreOffice.desktop,0,9,desktop:/Oracle
VM VirtualBox.desktop,0,14,desktop:/Unmount LRZ
Webdisk,1,15,desktop:/parallel.pdf,0,15,desktop:/Questions.txt,7,16,desktop:/Mount
PC Hard
Drive.desktop,0,12,desktop:/Network.txt,0,13,desktop:/collectNWData-master.zip,0,2,desktop:/collectNWData-master,0,3,desktop:/Dropbox,0,0,desktop:/Latex,0,1,desktop:/Entertain
TV.xspf,0,6,desktop:/GIMP.desktop,0,7,desktop:/Signalverarbeit_950289968_(S17)-20170820,0,4,desktop:/Studium,0,5,desktop:/Windows
7 Ultimate.desktop,1,6,desktop:/Yast.desktop,3,0
---
> positions=10,20,desktop:/collectNWData-master,0,3,desktop:/collectNWData-master.zip,0,2,desktop:/trash.desktop,1,16,desktop:/MakeMKV,0,1,desktop:/kinfocenter.desktop,0,0,desktop:/Latex,7,15,desktop:/LibreOffice.desktop,2,1,desktop:/parallel.pdf,0,5,desktop:/Network,2,0,desktop:/Network.txt,0,4,desktop:/Radio
>  
> Arabella.desktop,4,1,desktop:/Signalverarbeit_950289968_(S17)-20170820.zip,7,18,desktop:/Universe
>  Cluster.desktop,4,0,desktop:/Physik MSc 
> Fächer,7,17,desktop:/Questions.txt,7,16,desktop:/TUMOnline,6,1,desktop:/GIMP.desktop,6,0,desktop:/Mount
>  LRZ Webdisk.desktop,0,15,desktop:/Mount PC Hard 
> Drive.desktop,0,14,desktop:/Oracle VM VirtualBox.desktop,8,0,desktop:/Dolphin 
> - root.desktop,0,16,desktop:/Dropbox,6,15,desktop:/Samsung CLX-3305FN 
> Druckerstatus,1,1,desktop:/Home.desktop,1,0,desktop:/Entertain 
> TV.xspf,3,1,desktop:/Signalverarbeit_950289968_(S17)-20170820,6,19,desktop:/Yast.desktop,3,0,desktop:/FPGA,6,18,desktop:/Data,6,17,desktop:/Studium,6,16,desktop:/WhatsApp.desktop,5,1,desktop:/Universe
>  Cluster 2.desktop,5,0,desktop:/Ark.desktop,7,0,desktop:/Unmount LRZ 
> Webdisk,1,15,desktop:/Unmount PC Hard Drive.desktop,1,14,desktop:/Windows 7 
> Ultimate.desktop,9,0

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

[plasmashell] [Bug 360212] Icon positions in folder view of the desktop are often scrambled after reboot or logout

[Florian Röhrer]

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

--- Comment #19 from Florian Röhrer  ---
---
> positions=10,20,desktop:/collectNWData-master,0,3,desktop:/collectNWData-master.zip,0,2,desktop:/trash.desktop,1,16,desktop:/MakeMKV,0,1,desktop:/kinfocenter.desktop,0,0,desktop:/Latex,7,15,desktop:/LibreOffice.desktop,2,1,desktop:/parallel.pdf,0,5,desktop:/Network,2,0,desktop:/Network.txt,0,4,desktop:/Radio
>  
> Arabella.desktop,4,1,desktop:/Signalverarbeit_950289968_(S17)-20170820.zip,7,18,desktop:/Universe
>  Cluster.desktop,4,0,desktop:/Physik MSc 
> Fächer,7,17,desktop:/Questions.txt,7,16,desktop:/TUMOnline,6,1,desktop:/GIMP.desktop,6,0,desktop:/Mount
>  LRZ Webdisk.desktop,0,15,desktop:/Mount PC Hard 
> Drive.desktop,0,14,desktop:/Oracle VM VirtualBox.desktop,8,0,desktop:/Dolphin 
> - root.desktop,0,16,desktop:/Dropbox,6,15,desktop:/Samsung CLX-3305FN 
> Druckerstatus,1,1,desktop:/Home.desktop,1,0,desktop:/Entertain 
> TV.xspf,3,1,desktop:/Signalverarbeit_950289968_(S17)-20170820,6,19,desktop:/Yast.desktop,3,0,desktop:/FPGA,6,18,desktop:/Data,6,17,desktop:/Studium,6,16,desktop:/WhatsApp.desktop,5,1,desktop:/Universe
>  Cluster 2.desktop,5,0,desktop:/Ark.desktop,7,0,desktop:/Unmount LRZ 
> Webdisk,1,15,desktop:/Unmount PC Hard Drive.desktop,1,14,desktop:/Windows 7 
> Ultimate.desktop,9,0

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

[plasmashell] [Bug 360212] Icon positions in folder view of the desktop are often scrambled after reboot or logout

[Florian Röhrer]

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

--- Comment #20 from Florian Röhrer  ---
Created attachment 107613
  --> https://bugs.kde.org/attachment.cgi?id=107613&action=edit
Comparison of the Icon config file with its backup

Sorry, for some reason, I can not post the whole output. I attached a textfile
with it.

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

[plasmashell] [Bug 384220] New: Systray pop-ups stop working when switching desktop while a pop-up is active

[Martin van Es]

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

Bug ID: 384220
   Summary: Systray pop-ups stop working when switching desktop
while a pop-up is active
   Product: plasmashell
   Version: 5.10.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: b...@mrvanes.com
  Target Milestone: 1.0

It's quite hard to explain the bug but here's what happens:

Normally, systray icons have some pop-up on left-button click, e.g. Device
Notifier. When I insert SD card, so a Device Notifier pops up showing possible
actions and at the same time I switch desktops, the pop-up disappears and will
not return when clicked. The only visible clue is a tiny blue bar over the
Device Notifier icon.

All systray pop-ups stop working, so this is not limited to Device Notifier,
just an example.

I use "slide" as desktop switch effect in kwin.

Only work-around I've found so far is restarting plasmashell.

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

[frameworks-syntax-highlighting] [Bug 381396] Add support for fish shell highlighting

[michele mazza]

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

michele mazza  changed:

   What|Removed |Added

 CC||michele.ma...@gmail.com

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

[kio-extras] [Bug 366638] [16.04] sftp stuck operations. Can operate only if reopening Dolphin

[Germano Massullo]

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

--- Comment #7 from Germano Massullo  ---
Is anybody working on this?

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

[plasmashell] [Bug 360212] Icon positions in folder view of the desktop are often scrambled after reboot or logout

[firewalker]

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

--- Comment #21 from firewalker  ---
The file changes content after the fact. In my case at least. I have the file
permissions as Read Only.

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

[korganizer] [Bug 384221] New: Korganizer crashed after inserting a new task

[Ulrich Pretzsch]

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

Bug ID: 384221
   Summary: Korganizer crashed after inserting a new task
   Product: korganizer
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: ulrich.pretz...@hamburg.de
  Target Milestone: ---

Application: korganizer (5.5.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.79-19-default x86_64
Distribution: "openSUSE Leap 42.3"

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

I created a new task in may Personal Calendar and tried to fill in some
details, when the application crashed.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff20f766940 (LWP 3311))]

Thread 6 (Thread 0x7ff1daec9700 (LWP 3317)):
#0  0x7ff2026318b4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7ff2025efd99 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7ff2025f02a8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7ff2025f042c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7ff20bb151ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7ff20bac2bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7ff20b8fdf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7ff20b902a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ff202b0d744 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff20aff9aad in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7ff1db6e4700 (LWP 3315)):
#0  0x7ff20aff120d in poll () at /lib64/libc.so.6
#1  0x7ff2025f0314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff2025f042c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff20bb151ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ff20bac2bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff20b8fdf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ff20b902a29 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ff202b0d744 in start_thread () at /lib64/libpthread.so.0
#8  0x7ff20aff9aad in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7ff1dbefd700 (LWP 3314)):
#0  0x7ff20bb1380d in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#1  0x7ff20bb13d85 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#2  0x7ff20bb14f7e in  () at /usr/lib64/libQt5Core.so.5
#3  0x7ff2025ef95d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#4  0x7ff2025f0230 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7ff2025f042c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7ff20bb151ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7ff20bac2bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7ff20b8fdf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7ff20a4eb295 in  () at /usr/lib64/libQt5DBus.so.5
#10 0x7ff20b902a29 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7ff202b0d744 in start_thread () at /lib64/libpthread.so.0
#12 0x7ff20aff9aad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7ff1dc972700 (LWP 3313)):
#0  0x7ff202b120bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7ff1e364db4b in  () at /usr/lib64/dri/r300_dri.so
#2  0x7ff1e364d8c7 in  () at /usr/lib64/dri/r300_dri.so
#3  0x7ff202b0d744 in start_thread () at /lib64/libpthread.so.0
#4  0x7ff20aff9aad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ff1e929b700 (LWP 3312)):
#0  0x7ff20aff120d in poll () at /lib64/libc.so.6
#1  0x7ff20073a3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7ff20073bfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7ff1ead7e0d9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ff20b902a29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7ff202b0d744 in start_thread () at /lib64/libpthread.so.0
#6  0x7ff20aff9aad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7ff20f766940 (LWP 3311)):
[KCrash Handler]
#6  0x7ff20af448d7 in raise () at /lib64/libc.so.6
#7  0x7ff20af45caa in abort () at /lib64/libc.so.6
#8  0x7ff20b5632b5 in __gnu_cxx::__verbose_terminate_handler() () at
/usr/lib64/libstdc++.so.6
#9  0x7ff20b5610a6 in  () at /usr/lib64/libstdc++.so.6
#10 0x7ff20b5610f1 in  () at /usr/lib64/libstdc++.so.6
#11 0x7ff20b561333 in  () at /usr/lib64/libstdc++.so.6
#12 0x7ff2073e6b1f in Akonadi::Item::throwPayloadException(int, int) const
() at /usr/lib64/libKF5AkonadiCore.so.5
#13 0x7ff2073f3

[plasmashell] [Bug 384222] Do not changed background on login screen

[Yura Shinkarev]

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

Yura Shinkarev  changed:

   What|Removed |Added

Version|master  |5.8.7

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

[plasmashell] [Bug 384222] New: Do not changed background on login screen

[Yura Shinkarev]

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

Bug ID: 384222
   Summary: Do not changed background on login screen
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Theme - Breeze
  Assignee: visual-des...@kde.org
  Reporter: bugs.kde@yshinkarev.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 107614
  --> https://bugs.kde.org/attachment.cgi?id=107614&action=edit
Login screen settings

OS: Kubuntu 16.04 amd64
Plasma: 5.8.7
Can not change background color.
Open 'Login screen (SDDM)' from main menu.
Click on 'Background' > 'Load from file' > choose png/jpg file with resolution
as my notebook has. Click 'Apply'. 
But nothing changed.
I still see default blue background.

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

[plasmashell] [Bug 384222] Do not changed background on login screen

[Yura Shinkarev]

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

Yura Shinkarev  changed:

   What|Removed |Added

 CC||bugs.kde@yshinkarev.ru

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

[systemsettings] [Bug 384222] Do not changed background on login screen

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

   Assignee|visual-des...@kde.org   |k...@davidedmundson.co.uk
Product|plasmashell |systemsettings
 CC||k...@davidedmundson.co.uk
  Component|Theme - Breeze  |kcm_sddm
   Target Milestone|1.0 |---

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

[systemsettings] [Bug 384222] Do not changed background on login screen

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Can you run systemsettings5 from a command line, reproduce and send me the
output. 

Do you get a prompt for a password?

Can you include your /usr/share/sddm/themes/breeze/theme.conf.user

Then set this status back to "unconfirmed"

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

[systemsettings] [Bug 384222] Do not changed background on login screen

[Yura Shinkarev]

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

--- Comment #2 from Yura Shinkarev  ---
Created attachment 107615
  --> https://bugs.kde.org/attachment.cgi?id=107615&action=edit
theme.conf.user

/usr/share/sddm/themes/breeze/theme.conf.user

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

[akregator] [Bug 384223] New: corrupted xml

[Pauli Prokki]

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

Bug ID: 384223
   Summary: corrupted xml
   Product: akregator
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: pauli.pro...@gmail.com
  Target Milestone: ---

Created attachment 107616
  --> https://bugs.kde.org/attachment.cgi?id=107616&action=edit
screenshot

after reboot akregator tell that there is corruption in default xml.

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

[systemsettings] [Bug 384222] Do not changed background on login screen

[Yura Shinkarev]

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

--- Comment #3 from Yura Shinkarev  ---
Created attachment 107617
  --> https://bugs.kde.org/attachment.cgi?id=107617&action=edit
systemsettings5.log

When I click on 'Login screen (SDDM)' item, I get lines in console:
QDBusArgument: read from a write-only object
QDBusArgument: read from a write-only object
QDBusArgument: read from a write-only object
true

When I click on 'Load from file', get:
kf5.kio.core: KSambaShare: Could not find smb.conf!

When I press ESC at opened choose file dialog I get:
XcbConnection: XCB error: 3 (BadWindow), sequence: 4170, resource id: 33569820,
major code: 40 (TranslateCoords), minor code: 0

When I press next 'Apply', then showing dialog 'Authentication Required', I get
in console:
idx: 0
And some later:
kf5.kauth: "Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken."
Save Failed
"DBus Backend error: could not contact the helper. Connection error: Did not
receive a reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.. Message error: "
"DBus Backend error: could not contact the helper. Connection error: Did not
receive a reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.. Message error: "

I input my password. Nothing new in console. 

Strange. I repeat and get some another log.

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

[systemsettings] [Bug 384222] Do not changed background on login screen

[Yura Shinkarev]

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

--- Comment #4 from Yura Shinkarev  ---
I record video too: https://youtu.be/nNhQUIW7npA

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

[systemsettings] [Bug 384222] Do not changed background on login screen

[Yura Shinkarev]

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

Yura Shinkarev  changed:

   What|Removed |Added

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

--- Comment #5 from Yura Shinkarev  ---
See from comment3 https://bugs.kde.org/show_bug.cgi?id=384222#c3

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

[kio-extras] [Bug 366638] [16.04] sftp stuck operations. Can operate only if reopening Dolphin

[Sebastian Kügler]

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

Sebastian Kügler  changed:

   What|Removed |Added

   Assignee|plasma-de...@kde.org|plasma-b...@kde.org

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

[kmail2] [Bug 381795] Unnecessary Popup that needs [OK] pressed to clear

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
Fixed in 5.6.0

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

[kcharselect] [Bug 351945] Missing Comment in desktop file

[Jonathan Riddell]

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

Jonathan Riddell  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kch |https://commits.kde.org/kch
   |arselect/c7aab0b76253a6cf6a |arselect/b5afdc16904a437e52
   |47df9615edf584a5df269b  |9f890e1d9c54e4d90c03a7

--- Comment #2 from Jonathan Riddell  ---
Git commit b5afdc16904a437e529f890e1d9c54e4d90c03a7 by Jonathan Riddell.
Committed on 31/08/2017 at 11:35.
Pushed by jriddell into branch 'Applications/17.08'.

add missing comment for appstream compliance

http://metadata.neon.kde.org/appstream/html/xenial/main/issues/kcharselect.html

M  +1-0org.kde.kcharselect.desktop

https://commits.kde.org/kcharselect/b5afdc16904a437e529f890e1d9c54e4d90c03a7

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

[ktimer] [Bug 351965] Missing Comment in desktop file

[Jonathan Riddell]

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

Jonathan Riddell  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kti |https://commits.kde.org/kti
   |mer/60a81dbac904b421c56d2c9 |mer/b40c6a910db317aa7c0fbdb
   |4ef2121b5cd2e188e   |aa288d9babf1fe503

--- Comment #2 from Jonathan Riddell  ---
Git commit b40c6a910db317aa7c0fbdbaa288d9babf1fe503 by Jonathan Riddell.
Committed on 31/08/2017 at 11:36.
Pushed by jriddell into branch 'Applications/17.08'.

add comment needed by appstream

http://metadata.neon.kde.org/appstream/html/xenial/main/issues/ktimer.html

M  +1-0org.kde.ktimer.desktop

https://commits.kde.org/ktimer/b40c6a910db317aa7c0fbdbaa288d9babf1fe503

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

[neon] [Bug 384224] New: Dependency error when trying to install ibgtk2.0-0:i386

[p . b]

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

Bug ID: 384224
   Summary: Dependency error when trying to install
ibgtk2.0-0:i386
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: p.b+...@mailbox.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 107618
  --> https://bugs.kde.org/attachment.cgi?id=107618&action=edit
apt-get

Dear kde devs,

Trying to install ibgtk2.0-0:i386 with the latest user or user/lts neon results
in a dependency error.

Steps to reproduce (option 1):
# dpkg --add-architecture i386
# apt-get update
# apt-get install libgtk2.0-0:i386

Steps to reproduce (option 2):
# dpkg --add-architecture i386
# apt-get update
# aptitude install libgtk2.0-0:i386

Expected behavior:
libgtk2.0-0:i386 should install without complaining

Guessed problem from aptitude output:
 libharfbuzz0b : Breaks: libharfbuzz0b:i386 (!=
1.4.6-0neon+16.04+xenial+build2) but 1.0.1-1ubuntu0.1 is to be installed.
 libharfbuzz0b:i386 : Breaks: libharfbuzz0b (!= 1.0.1-1ubuntu0.1) but
1.4.6-0neon+16.04+xenial+build2 is installed.

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

[neon] [Bug 384224] Dependency error when trying to install ibgtk2.0-0:i386

[p . b]

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

--- Comment #1 from p.b  ---
Created attachment 107619
  --> https://bugs.kde.org/attachment.cgi?id=107619&action=edit
aptitude

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

[neon] [Bug 384224] Dependency error when trying to install ibgtk2.0-0:i386

[Jonathan Riddell]

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

--- Comment #2 from Jonathan Riddell  ---
we don't make i386 packages so indeed they will clash where they depend on a
specific version we have updated.

it's on the todo but it's not high priority

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

[systemsettings] [Bug 384222] Do not changed background on login screen

[David Edmundson]

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

--- Comment #6 from David Edmundson  ---
>kf5.kauth: "Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken."
Save Failed

Well that explains our problem.

The bit of code that runs as root to update the SDDM settings is either
crashing or getting blocked.

That's tricky to debug.

You can try running:
 sudo /usr/lib64/libexec/kauth/kcmsddm_authhelper


then clicking apply from system settings in the next 10 seconds. It should use
the executable we started and can then get output. Or even a gdb trace if
possible?

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

[neon] [Bug 384224] Dependency error when trying to install ibgtk2.0-0:i386

[p . b]

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

--- Comment #3 from p.b  ---
What a pity! The latest update just broke one of my most used sync apps.

But thank you for your quick reply.

Is there any specific place to look for, to find news about your i386 progress?

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

[kwin] [Bug 384225] New: Modifier key 'leaks' to focused application after key release

[bugzilla_noreply]

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

Bug ID: 384225
   Summary: Modifier key 'leaks' to focused application after key
release
   Product: kwin
   Version: 5.10.5
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: adikur...@gmail.com
  Target Milestone: ---

When using a libvirt-spice virtual machine with keyboard grabbing disabled
every combination of the Windows key is passed to the application triggering
the start menu in Windows after key release. This is the case for both existing
and not existing shortcuts.

For example: I use Win+1,2,3 to switch between the virtual desktops. For this
to work I disabled the qemu keyboard grabbing. On desktop 1 pressing Win+2
switches to desktop 2, but a single Windows key press is sent to the VM window
triggering actions in the guest os.

Expected result: after key release (if there is no global shortcut set for that
combination) the windows key press is not sent to the VM.
Note:
This doesn't happen under gnome-shell X11 session.

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

[systemsettings] [Bug 384222] Do not changed background on login screen

[Yura Shinkarev]

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

--- Comment #7 from Yura Shinkarev  ---
I have kcmsddm_authhelper in only specific path:
usr/lib/x86_64-linux-gnu/libexec/kauth/kcmsddm_authhelper
Again record video: https://youtu.be/86ZEUATBlp8
kcmsddm_authhelper have no output in console.
Sorry, I have no necessary skills and do not understand what'is gdb and what I
need todo more.

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

[kwin] [Bug 384225] Modifier key 'leaks' to focused application after key release

[bugzilla_noreply]

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

--- Comment #1 from adikur...@gmail.com ---
Slight correction:
if there is a global shortcut that kwin reacted to then the modifier shouldn't
get passed to the active application.

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

[kmail2] [Bug 381795] Unnecessary Popup that needs [OK] pressed to clear

[BingMyBong]

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

--- Comment #2 from BingMyBong  ---
(In reply to Laurent Montel from comment #1)
> Fixed in 5.6.0

Thanks.

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

[plasmashell] [Bug 372090] Plasma show events only after second enable of holidays

[Kai Uwe Broulik]

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

--- Comment #3 from Kai Uwe Broulik  ---
Git commit 11e416bea6cdfc0556522502852379a1d52483b4 by Kai Uwe Broulik.
Committed on 31/08/2017 at 12:29.
Pushed by broulik into branch 'master'.

[ConfigModel] Allow programmatically adding and removing ConfigCategory

The appendCategory(ConfigCategory*) allows to add a category created by e.g. an
Instantiator
that can use bindings rather than fixed arguments.
The removeCategory methods allow to remove a category when e.g. the model in an
Instantiator resets.

Differential Revision: https://phabricator.kde.org/D7602

M  +42   -0src/plasmaquick/configmodel.cpp
M  +5-0src/plasmaquick/configmodel.h

https://commits.kde.org/plasma-framework/11e416bea6cdfc0556522502852379a1d52483b4

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

[plasmashell] [Bug 372090] Plasma show events only after second enable of holidays

[Kai Uwe Broulik]

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

--- Comment #4 from Kai Uwe Broulik  ---
Git commit 03b37c94bd3bd615e43c88dfdb74928b2d06c396 by Kai Uwe Broulik.
Committed on 31/08/2017 at 12:33.
Pushed by broulik into branch 'master'.

[Digital Clock] Show event plugin configurations only if enabled

This replaces the loop with fixed values by an Instantiator creating bindings
on the model.

Differential Revision: https://phabricator.kde.org/D7603

M  +11   -13   applets/digital-clock/package/contents/config/config.qml

https://commits.kde.org/plasma-workspace/03b37c94bd3bd615e43c88dfdb74928b2d06c396

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

[plasma-nm] [Bug 376664] Bridged connections are not visible in the applet

[Jan Grulich]

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

Jan Grulich  changed:

   What|Removed |Added

 Resolution|WONTFIX |FIXED
  Latest Commit||https://commits.kde.org/pla
   ||sma-nm/4634aa6e68e2e4d5a117
   ||7a3ee90a6461a9e3f44a

--- Comment #32 from Jan Grulich  ---
Git commit 4634aa6e68e2e4d5a1177a3ee90a6461a9e3f44a by Jan Grulich.
Committed on 31/08/2017 at 12:38.
Pushed by grulich into branch 'master'.

Add option to allow managing virtual connections

If this option is enabled, users will see virtual connections in applet
and in the connection editor and they will be able to create new virtual
connections as well. This option is disabled by default as we don't want
regular users to be bothered by this.

M  +4-0applet/contents/config/main.xml
M  +10   -0applet/contents/ui/configGeneral.qml
M  +1-0applet/contents/ui/main.qml
M  +1-0libs/CMakeLists.txt
R  +20   -7libs/configuration.cpp [from: libs/declarative/configuration.cpp
- 070% similarity]
R  +6-5libs/configuration.h [from: libs/declarative/configuration.h -
077% similarity]
M  +0-1libs/declarative/CMakeLists.txt
M  +2-15   libs/declarative/connectionicon.cpp
M  +2-20   libs/declarative/networkstatus.cpp
M  +1-0libs/editor/CMakeLists.txt
M  +28   -0libs/models/creatableconnectionsmodel.cpp
M  +14   -7libs/uiutils.cpp

https://commits.kde.org/plasma-nm/4634aa6e68e2e4d5a1177a3ee90a6461a9e3f44a

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

[plasmashell] [Bug 374072] plasmashell spams log with "QFileInfo::absolutePath: Constructed with empty filename"

[kevin paetzold]

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

kevin paetzold  changed:

   What|Removed |Added

 CC||kevin.paetz...@gmail.com

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

[akregator] [Bug 384213] Kontact opens but Akregator shows no feeds.

[Dave Morley]

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

Dave Morley  changed:

   What|Removed |Added

 CC||davm...@davmor2.co.uk

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

[plasmashell] [Bug 374072] plasmashell spams log with "QFileInfo::absolutePath: Constructed with empty filename"

[kevin paetzold]

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

--- Comment #5 from kevin paetzold  ---
i see tons of these messages.  i am running fedora 27 with Mate (although there
are various/many kde packages loaded).   This seems to be provoked by copying
large (multi gb) files using the gui interface (caja).

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

[plasmashell] [Bug 374072] plasmashell spams log with "QFileInfo::absolutePath: Constructed with empty filename"

[kevin paetzold]

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

--- Comment #6 from kevin paetzold  ---
i lied.  i am running fedora 26.

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

[plasmashell] [Bug 384226] New: Plasma crashed while actioning notification icon of an MTP device.

[bugzilla_noreply]

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

Bug ID: 384226
   Summary: Plasma crashed while actioning notification icon of an
MTP device.
   Product: plasmashell
   Version: 5.10.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: raulvior@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.7.1
Frameworks Version: 5.37.0
Operating System: Linux 4.10.0-33-generic x86_64
Distribution: Ubuntu 17.04

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

1. Left-Clicked on the icon. The action menu unfolded.
2. Right-clicked on the icon.
3. Left-Clicked again. The action menu folded.

Crash. But it is not reproducible. I have done again the same while I was
writing this report and it did not crash.

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

Thread 25 (Thread 0x7f1a437fe700 (LWP 8129)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1b68e68aeb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1aadec08e0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f1aadec4b18 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x7f1aadec2929 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#14 0x7f1b68e67c38 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f1b67d0a6da in start_thread (arg=0x7f1a437fe700) at
pthread_create.c:456
#16 0x7f1b68774d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 24 (Thread 0x7f1a43fff700 (LWP 8128)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1b68e68aeb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1aadec08e0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f1aadec4b18 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7f1aadebfa5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x7f1aadec4b72 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#14 0x7f

[kontact] [Bug 384227] New: kontact crashes when loading or receiving new messages

[Carmelo Piccione]

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

Bug ID: 384227
   Summary: kontact crashes when loading or receiving new messages
   Product: kontact
   Version: 5.2.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: carmelo.picci...@gmail.com
  Target Milestone: ---

Application: kontact (5.2.3)

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

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

Loading messages , or getting notifcations, from an imap kolab provider.

The crash can be reproduced every time.

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

Thread 25 (Thread 0x7fbbce228700 (LWP 3524)):
#0  0x7fbc932aa8b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7fbc9a9b2a26 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fbc9a9ae252 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fbc9a9b1c38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fbc932a46da in start_thread (arg=0x7fbbce228700) at
pthread_create.c:456
#5  0x7fbc9a0a7d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 24 (Thread 0x7fbbcea29700 (LWP 3523)):
#0  0x7fbc9a9a8d99 in QMutex::lock() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fbc9abd482f in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fbc914d5a6d in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbc914d649b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbc914d668c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbc9abd50bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fbc9ab7ebea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fbc9a9acf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fbc9a9b1c38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fbc932a46da in start_thread (arg=0x7fbbcea29700) at
pthread_create.c:456
#10 0x7fbc9a0a7d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 23 (Thread 0x7fbbc700 (LWP 3520)):
#0  0x7fbc9abd50c1 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fbc9ab7ebea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fbc9a9acf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fbc9a9b1c38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fbc932a46da in start_thread (arg=0x7fbbc700) at
pthread_create.c:456
#5  0x7fbc9a0a7d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 22 (Thread 0x7fbbe0f81700 (LWP 3518)):
#0  0x7fbc9d2c2f90 in update_get_addr (ti=0x7fbc9afc9660) at dl-tls.c:807
#1  0x7fbc9a9b0ac6 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fbc9abd480a in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fbc914d5a6d in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbc914d649b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbc914d668c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fbc9abd50bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fbc9ab7ebea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fbc9a9acf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fbc9a9b1c38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fbc932a46da in start_thread (arg=0x7fbbe0f81700) at
pthread_create.c:456
#11 0x7fbc9a0a7d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 21 (Thread 0x7fbbe1782700 (LWP 3516)):
#0  0x7fbc9a09bd8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbc914d6576 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbc914d668c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbc9abd50bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fbc9ab7ebea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fbc9a9acf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb

[plasma-integration] [Bug 384163] smplayer crashes at startup when using global menu + plasma QPA

[Antonio Rojas]

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

--- Comment #3 from Antonio Rojas  ---
(In reply to Antonio Rojas from comment #2)
> smplayer 15.11.0 also works here. Whatever triggers this has been introduced
> in a later version (reproducible at least with 17.8.0)

More precisely, in this commit:
https://app.assembla.com/spaces/smplayer/subversion/commits/7657

On another machine I'm getting the segfault on close instead of on startup
(still only with global menu + Plasma QPA)

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

[systemsettings] [Bug 317959] access/bounce keys does not give enough adjustment

[Lastique]

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

Lastique  changed:

   What|Removed |Added

 CC||andy...@mail.ru

--- Comment #1 from Lastique  ---
Still an issue in KDE System Settings 5.9.4, Kubuntu 17.04. Please, fix.

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

[kwin] [Bug 384228] New: KWin crash when changing windows of programs

[Lukasz]

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

Bug ID: 384228
   Summary: KWin crash when changing windows of programs
   Product: kwin
   Version: 5.10.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dolo...@outlook.com
  Target Milestone: ---

Application: kwin_x11 (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.12.8-2-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
When I am switching windows of for example Firefox with shortcut alt+`, KWin
crashes.

The crash can be reproduced every time.

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

Thread 10 (Thread 0x7f56357fa700 (LWP 958)):
#0  0x7f566cdff1ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f567018eb04 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f567018eb49 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f566cdf9049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5673c68f0f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f56367fc700 (LWP 938)):
#0  0x7f566cdff1ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5641ec955c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f5641ec9268 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f566cdf9049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5673c68f0f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f5636ffd700 (LWP 937)):
#0  0x7f566cdff1ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5641ec955c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f5641ec9268 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f566cdf9049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5673c68f0f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f56377fe700 (LWP 936)):
#0  0x7f566cdff1ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5641ec955c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f5641ec9268 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f566cdf9049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5673c68f0f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f5637fff700 (LWP 935)):
#0  0x7f566cdff1ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5641ec955c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f5641ec9268 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f566cdf9049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5673c68f0f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f563cd91700 (LWP 934)):
#0  0x7f566cdff1ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5641ec955c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f5641ec9268 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f566cdf9049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5673c68f0f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f563d6d3700 (LWP 933)):
#0  0x7f566cdff1ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f5641ec955c in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f5641ec9268 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f566cdf9049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f5673c68f0f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f5652376700 (LWP 891)):
#0  0x7f5673c5ef76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f567126fba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f567127133f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f5671217ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f567103140e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f566b8f53d9 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f567103615b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f566cdf9049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f5673c68f0f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f5653fff700 (LWP 800)):
#0  0x7f5673c5ef76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f567126fba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f567127133f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f5671217ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f567103140e in QThread::

[plasmashell] [Bug 384229] New: When resizing digital clock to very large, plasma crashes

[Lukasz]

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

Bug ID: 384229
   Summary: When resizing digital clock to very large, plasma
crashes
   Product: plasmashell
   Version: 5.10.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Digital Clock
  Assignee: plasma-b...@kde.org
  Reporter: dolo...@outlook.com
  Target Milestone: 1.0

Hello,

I have a very big display 2880x1800 and when I am resizing Digital Clock on
Desktop to become very big, plasma crashes.

Best,
Łukasz

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

[plasmashell] [Bug 384229] When resizing digital clock to very large, plasma crashes

[Lukasz]

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

--- Comment #1 from Lukasz  ---
This is what plasmashell outputs to console during crash:

file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19:
QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19:
QML Loader: Binding loop detected for property "height"

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

[valgrind] [Bug 384230] New: vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

[Laszlo Papp]

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

Bug ID: 384230
   Summary: vex x86->IR: unhandled instruction bytes: 0x67 0xE8
0xAB 0x68
   Product: valgrind
   Version: 3.13.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: lp...@kde.org
  Target Milestone: ---

Created attachment 107620
  --> https://bugs.kde.org/attachment.cgi?id=107620&action=edit
ld objdump -d

uname -a
Linux pol-lx-007 4.12.8-2-ARCH #1 SMP PREEMPT Fri Aug 18 14:08:02 UTC 2017
x86_64 GNU/Linux


cat /etc/issue
Arch Linux \r (\l)


cat main.c
int main()
{
return 0;
}


gcc -m32 main.c


valgrind -v --sym-offsets=yes ./a.out 
==1594== Memcheck, a memory error detector
==1594== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1594== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==1594== Command: ./a.out
==1594== 
--1594-- Valgrind options:
--1594---v
--1594----sym-offsets=yes
--1594-- Contents of /proc/version:
--1594--   Linux version 4.12.8-2-ARCH (builduser@foutrelis) (gcc version 7.2.0
(GCC) ) #1 SMP PREEMPT Fri Aug 18 14:08:02 UTC 2017
--1594-- 
--1594-- Arch and hwcaps: X86, LittleEndian, x86-mmxext-sse1-sse2-sse3
--1594-- Page sizes: currently 4096, max supported 4096
--1594-- Valgrind library directory: /usr/lib/valgrind
--1594-- Reading syms from /tmp/a.out
--1594-- Reading syms from /usr/lib32/ld-2.25.so
--1594-- Reading syms from /usr/lib/valgrind/memcheck-x86-linux
--1594--object doesn't have a symbol table
--1594--object doesn't have a dynamic symbol table
--1594-- Scheduler: using generic scheduler lock implementation.
--1594-- Reading suppressions file: /usr/lib/valgrind/default.supp
==1594== embedded gdbserver: reading from
/tmp/vgdb-pipe-from-vgdb-to-1594-by-lpapp-on-???
==1594== embedded gdbserver: writing to  
/tmp/vgdb-pipe-to-vgdb-from-1594-by-lpapp-on-???
==1594== embedded gdbserver: shared mem  
/tmp/vgdb-pipe-shared-mem-vgdb-1594-by-lpapp-on-???
==1594== 
==1594== TO CONTROL THIS PROCESS USING vgdb (which you probably
==1594== don't want to do, unless you know exactly what you're doing,
==1594== or are doing some strange experiment):
==1594==   /usr/lib/valgrind/../../bin/vgdb --pid=1594 ...command...
==1594== 
==1594== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==1594==   /path/to/gdb ./a.out
==1594== and then give GDB the following command
==1594==   target remote | /usr/lib/valgrind/../../bin/vgdb --pid=1594
==1594== --pid is optional if only one valgrind process is running
==1594== 
--1594-- REDIR: 0x40195a0 (ld-linux.so.2:strlen) redirected to 0x58057063 (???)
vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68
==1594== valgrind: Unrecognised instruction at address 0x400301f.
==1594==at 0x400301F: dl_main+4975 (in /usr/lib32/ld-2.25.so)
==1594==by 0x4016A65: _dl_sysdep_start+1269 (in /usr/lib32/ld-2.25.so)
==1594==by 0x4001861: _dl_start+513 (in /usr/lib32/ld-2.25.so)
==1594==by 0x4000AF6: ??? (in /usr/lib32/ld-2.25.so)
==1594== Your program just tried to execute an instruction that Valgrind
==1594== did not recognise.  There are two possible reasons for this.
==1594== 1. Your program has a bug and erroneously jumped to a non-code
==1594==location.  If you are running Memcheck and you just saw a
==1594==warning about a bad jump, it's probably your program's fault.
==1594== 2. The instruction is legitimate but Valgrind doesn't handle it,
==1594==i.e. it's Valgrind's fault.  If you think this is the case or
==1594==you are not sure, please let us know and we'll try to fix it.
==1594== Either way, Valgrind will now raise a SIGILL signal which will
==1594== probably kill your program.
==1594== 
==1594== Process terminating with default action of signal 4 (SIGILL): dumping
core
==1594==  Illegal opcode at address 0x400301F
==1594==at 0x400301F: dl_main+4975 (in /usr/lib32/ld-2.25.so)
==1594==by 0x4016A65: _dl_sysdep_start+1269 (in /usr/lib32/ld-2.25.so)
==1594==by 0x4001861: _dl_start+513 (in /usr/lib32/ld-2.25.so)
==1594==by 0x4000AF6: ??? (in /usr/lib32/ld-2.25.so)
==1594== 
==1594== HEAP SUMMARY:
==1594== in use at exit: 0 bytes in 0 blocks
==1594==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1594== 
==1594== All heap blocks were freed -- no leaks are possible
==1594== 
==1594== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==1594== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction (core dumped)

ld --version
GNU ld (GNU Binutils) 2.28.0.20170506
Copyright (C) 2017 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

-- 
You are re

[valgrind] [Bug 384230] vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x68

[Tom Hughes]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #1 from Tom Hughes  ---
Created attachment 107621
  --> https://bugs.kde.org/attachment.cgi?id=107621&action=edit
Patch to implement "addr16 call" aka "call rel16"

Try building valgrind with this patch applied and see if that helps...

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

[krita] [Bug 384231] New: Bristle engine rotation ignores drawing angle

[Jörn PM]

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

Bug ID: 384231
   Summary: Bristle engine rotation ignores drawing angle
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: webmas...@ionflux.org
  Target Milestone: ---

Created attachment 107622
  --> https://bugs.kde.org/attachment.cgi?id=107622&action=edit
bristle brush results with rotation set to drawing angle

I have created a custom brush using the bristle engine, with rotation depending
on drawing angle.

As shown in the attached images, the drawing angle is ignored (compare with
regular pixel engine brush).

There is also a message in the console when using the bristle brush:

krita.general: KisPaintInformation::drawingAngle() Cannot access Distance Info
last dab data

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

[krita] [Bug 384231] Bristle engine rotation ignores drawing angle

[Jörn PM]

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

--- Comment #1 from Jörn PM  ---
Created attachment 107623
  --> https://bugs.kde.org/attachment.cgi?id=107623&action=edit
brush settings

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

[Phonon] [Bug 384232] New: PHONON_BACKEND did not working.

[TOM Harrison]

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

Bug ID: 384232
   Summary: PHONON_BACKEND did not working.
   Product: Phonon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: l12436...@gmail.com
CC: myr...@kde.org, romain.per...@gmail.com
  Target Milestone: 4.8

when I set the PHONON_BACKEND, amarok still using the primary settings in user
config.
It should load user prefered backend rather than first backend in system
settings.

1. using PHONON_DEBUG=5 PHONON_BACKEND_DEBUG=5 PHONON_BACKEND=phonon_vlc amarok
if you are using gstreamer as backend.
2. you will found the console show amarok still using gstreamer rather than
phonon_vlc.

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

[krita] [Bug 384231] Bristle engine rotation ignores drawing angle

[Jörn PM]

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

--- Comment #2 from Jörn PM  ---
using git master, e651f4248079d0

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

[korganizer] [Bug 384122] KOrganizer - No invitation sent when selecting multiple attendees + no email address autocompletion

[Steeven Hudon]

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

--- Comment #7 from Steeven Hudon  ---
To reproduce the bug, I simply create a new event by double-clicking any day of
the month, then in the Attendees tab, I write down the address OR click on the
'Select Attendees...' button and select (2) or more attendees.  Finally, I
click save.

At that point, no invitation email is sent to the attendees : The meeting is
still in my calendar, but no invitation has been sent to the attendees.

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

[plasmashell] [Bug 352988] pressing Esc while renaming on folderview dismisses show the desktop effect

[Kai Uwe Broulik]

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

--- Comment #12 from Kai Uwe Broulik  ---
Git commit 55d74c68219781c8770b1a22ecd5155e9908ccb8 by Kai Uwe Broulik.
Committed on 31/08/2017 at 15:13.
Pushed by broulik into branch 'master'.

[DesktopView] Move cancelling showing desktop into keyPressEvent

This will route the event through the containment first which can then
intercept it, e.g. to prevent
Escape from exiting showing desktop while renaming where it should only cancel
that.

Differential Revision: https://phabricator.kde.org/D7630

M  +13   -11   shell/desktopview.cpp

https://commits.kde.org/plasma-workspace/55d74c68219781c8770b1a22ecd5155e9908ccb8

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

[plasmashell] [Bug 355603] Moving an applet next to an auto-hidden panel will move the applet into the panel

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #2 from Alexander Mentyu  ---
Confirming this bug in:

Distribution: KDE neon Developer Edition Unstable Branches
KDE Plasma Version: 5.10.90
KDE Frameworks Version: 5.37.0
Qt Version: 5.9.1
Kernel Version: 4.10.0-32-generic

Maybe panel could be shown in settings mode upon dragging of a widget - to
point exact target place for dropping widget.

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

[kwin] [Bug 384225] Modifier key 'leaks' to focused application after key release

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #2 from Martin Flöser  ---
I'm sorry, but there is nothing KWin can do about. Global shortcut handling is
provided by kglobalaccel. But even kglobalaccel cannot do anything about it.

The key press of the modifier is always sent, only the key press of the key
which triggered the global shortcut will be hidden from applications, but the
key release is then sent again. There is really nothing we can do about it.

But libvirt can react on it. It gets an event that the another client grabbed
the keyboard. In this case it should dismiss all the pressed events.

I would recommend to change the shortcuts to not use win-modifier.

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

[kwin] [Bug 384228] KWin crash when changing windows of programs

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---
As with all crash reports from Arch users it's utterly useless as Arch does not
provide debug symbols. Please complain to Arch that it wasted your time by
suggesting to create a bug report.

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

[krita] [Bug 384233] New: color value bugging behind when dragging with cursor or changing w/ cursor wheel

[bugzilla_noreply]

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

Bug ID: 384233
   Summary: color value bugging behind when dragging with cursor
or changing w/ cursor wheel
   Product: krita
   Version: 3.2.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: color selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: jamesedwa...@gmx.de
  Target Milestone: ---

When dragging the HSV slider the indicator in the bar bugs slightly behind
mouse cursor. Additionally when attempting to change the value via mouse wheel
it sometimes is impossible to get a certain value.

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

[plasmashell] [Bug 357100] The destUrl of 'Show original directory' of a link is wrong in DesktopView showing desktop folder

[Alexander Mentyu]

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

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #3 from Alexander Mentyu  ---
Cannot reproduce/no longer relevant? i:

Distribution: KDE neon Developer Edition Unstable Branches
KDE Plasma Version: 5.10.90
KDE Frameworks Version: 5.37.0
Qt Version: 5.9.1
Kernel Version: 4.10.0-32-generic

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