[okular] [Bug 356285] Not enough space for page number

[bugzilla_noreply]

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

--- Comment #9 from l-t+li...@mailbox.org ---
As reported in Bug 377299 the situation is somewhat different for me, as it
displays 2 digit page numbers correctly, but fails to display more digits. This
is due to a fixed text box size. It is independent of the window size and
independent of the document, which you view.

An adjustable page number box size would be preferred. If this is not possible,
you might consider increasing the width to, lets say, 6 or 7 digits or so.

Okular Version 0.25.0
KDE 4.14.22
Kubuntu 16.04

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

[okular] [Bug 356285] Not enough space for page number

[bugzilla_noreply]

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

--- Comment #8 from l-t+li...@mailbox.org ---
Created attachment 104429
  --> https://bugs.kde.org/attachment.cgi?id=104429=edit
Page number box independent of window size w/o document - larger window

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

[Akonadi] [Bug 377324] New: akonadi server crashed when trying to create a task in my calendar

[Mathias Homann]

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

Bug ID: 377324
   Summary: akonadi server crashed when trying to create a task in
my calendar
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: mathias.hom...@opensuse.org
  Target Milestone: ---

Application: akonadiserver (5.4.2)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.4.49-16-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
I tried to create a task in my calendar. Akonadi server crashed as soon as the
edit task window came up.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe9e4673780 (LWP 9800))]

Thread 41 (Thread 0x7fe90f7fe700 (LWP 11710)):
#0  0x7fe9e23f451d in read () from /lib64/libc.so.6
#1  0x7fe9dd436073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.375.39
#2  0x7fe9df1b3670 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe9df172e49 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fe9df1732a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7fe9df17342c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7fe9e2f088ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#7  0x7fe9e2eb86ab in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#8  0x7fe9e2d009aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#9  0x7fe9e2d05019 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7fe9e1275734 in start_thread () from /lib64/libpthread.so.0
#11 0x7fe9e2400d3d in clone () from /lib64/libc.so.6

Thread 40 (Thread 0x7fe90700 (LWP 11678)):
#0  0x7fe9e23f451d in read () from /lib64/libc.so.6
#1  0x7fe9dd436073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.375.39
#2  0x7fe9df1b3670 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe9df172e49 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fe9df1732a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7fe9df17342c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7fe9e2f088ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#7  0x7fe9e2eb86ab in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#8  0x7fe9e2d009aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#9  0x7fe9e2d05019 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7fe9e1275734 in start_thread () from /lib64/libpthread.so.0
#11 0x7fe9e2400d3d in clone () from /lib64/libc.so.6

Thread 39 (Thread 0x7fe930ff9700 (LWP 11676)):
#0  0x7fe9e127ca6c in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x7fe9e12777eb in pthread_mutex_lock () from /lib64/libpthread.so.0
#2  0x7fe9de22de7c in ?? () from /usr/X11R6/lib64/libGL.so.1
#3  0x7fe9de232db1 in ?? () from /usr/X11R6/lib64/libGL.so.1
#4  0x7fe9de23326b in ?? () from /usr/X11R6/lib64/libGL.so.1
#5  0x7fe9dd4360f1 in ?? () from /usr/lib64/tls/libnvidia-tls.so.375.39
#6  0x7fe9df1b3670 in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7fe9df172e49 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#8  0x7fe9df1732a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#9  0x7fe9df17342c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#10 0x7fe9e2f088ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#11 0x7fe9e2eb86ab in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#12 0x7fe9e2d009aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#13 0x7fe9e2d05019 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#14 0x7fe9e1275734 in start_thread () from /lib64/libpthread.so.0
#15 0x7fe9e2400d3d in clone () from /lib64/libc.so.6

Thread 38 (Thread 0x7fe972ffd700 (LWP 11652)):
#0  0x7fe9e127ca6c in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x7fe9e12777eb in pthread_mutex_lock () from /lib64/libpthread.so.0
#2  0x7fe9de22de7c in ?? () from /usr/X11R6/lib64/libGL.so.1
#3  0x7fe9de232db1 in ?? () from /usr/X11R6/lib64/libGL.so.1
#4  0x7fe9de23326b in ?? () from /usr/X11R6/lib64/libGL.so.1
#5  0x7fe9dd4360f1 in ?? () from /usr/lib64/tls/libnvidia-tls.so.375.39
#6  0x7fe9df1b3670 in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7fe9df172e49 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#8  0x7fe9df1732a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#9  0x7fe9df17342c in 

[okular] [Bug 356285] Not enough space for page number

[bugzilla_noreply]

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

--- Comment #7 from l-t+li...@mailbox.org ---
Created attachment 104428
  --> https://bugs.kde.org/attachment.cgi?id=104428=edit
Page number box independent of window size w/o document - small window

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

[okular] [Bug 356285] Not enough space for page number

[bugzilla_noreply]

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

--- Comment #6 from l-t+li...@mailbox.org ---
Created attachment 104427
  --> https://bugs.kde.org/attachment.cgi?id=104427=edit
Example of 3 digit page number not fully shown

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

[plasma4] [Bug 377323] Poor mouse movement implementation

[bugzilla_noreply]

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

--- Comment #1 from bobert.campb...@gmail.com ---
This would also drastically reduce general cpu processing time for systems that
are slow enough to build up mouse move messages, and they are the ones that
really need it.

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

[plasma4] [Bug 377323] Poor mouse movement implementation

[bugzilla_noreply]

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

bobert.campb...@gmail.com changed:

   What|Removed |Added

 CC||bobert.campb...@gmail.com

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

[plasma4] [Bug 377323] Poor mouse movement implementation

[bugzilla_noreply]

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

bobert.campb...@gmail.com changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[plasma4] [Bug 377323] New: Poor mouse movement implementation

[bugzilla_noreply]

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

Bug ID: 377323
   Summary: Poor mouse movement implementation
   Product: plasma4
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: mouse actions
  Assignee: plasma-b...@kde.org
  Reporter: bobert.campb...@gmail.com
CC: chan...@gmail.com
  Target Milestone: ---

It seems to queue up all mouse movement messages and process every message. 
For me this can result in 10 second delays when I sweep my mouse across an
application that draws tool tips and the like.

This happens to me on the plasma task manager widget and several apps include
VLC.  I can slowly watch all the mouse movement messages get processed.  This
is resulting in a horrendous user experience.

This reeks of poor implementation.  I'm pretty sure the correct way to handle
mouse movement is to set a flag when the mouse is moved and when you are able
to then process it and get the current mouse location.  That way by the time
you are processing the message, if your system has been busy, you are only
processing the latest mouse movement message and that is it, the rest should be
ignored, except for any message preceding a click.

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

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

[zephyrus00jp]

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

--- Comment #6 from zephyrus00jp  ---
Created attachment 104426
  --> https://bugs.kde.org/attachment.cgi?id=104426=edit
A log to show valgrind with --vex-iropt-register-updates=all still segfaults
(under 4.7.0.1)

Sorry I was not specific.

I DID follow Julien's advice in the last several months and still no luck.

The following options for creating Thunderbird are in my mozconfig
file (on two PCs where I test.  

>  ac_add_options --disable-jemalloc
>  ac_add_options --enable-valgrind

[And I don't see unhandled syscall: 317 before segfault
in recent logs as you can verify. At least, I didn't recall seeing this for the
last few months.]

Re the following option:

>  --vex-iropt-register-updates=allregs-at-mem-access

This has been added to the valgrind option when I ran 
|make mozmill| test suite under one of the test machines, and
still no luck. Even with this and a few other options Julian suggested, the
combination valgrind+thunderbird runs under 3.19.5 and
segfaults under 4.7.0.1 and 4.9.x series.
Actually, this option does not make a difference as far as I can tell :-(

> https://bugs.kde.org/show_bug.cgi?id=345414#c3

Yes, that thread was reported by me almost two years ago.

Back then 4.y series kernel was not available for Debian (it was only
in testing repository). But it is now. And I want to use the later
kernel versions for obvious reasons.

I have to emphasize that the bug still stands with the suggested option.

I am attaching the segfault case when valgrind is run with the following
parameter under kernel 4.7.0.1 (Debian's distribution). Note the addition of
--vex-iropt-register-updates=allregs-at-mem-access.
(It does not make a difference. valgrind+thunderbird still
segfaults. Sorry I was not specific enough about this in my original
report. I did not want to clutter the bug report with the options that
do not seem to have effect.)

strace -ff valgrind --verbose --trace-syscalls=yes --trrace-signals=yes
--show-mismatched-frees=no --trace-children=yes
--vex-iropt-register-updates=allregs-at-mem-access
~ishikawa/objdir-tb3/dist/bin/thunderbird-bbin 

On this machine with this kernel, original valgrind+thunderbird segfaults AFTER
a child process spawned by thunderbird finishes.
On another machine with 4.9.x kernel, valgrind+thunderbird segfaults way before
the child process fork/exec happens.

It is really frustrating to see the combination of valgrind+thunderbird work
only under certain kernel revisions (in my case, 3.19.5) as noted in
https://bugs.kde.org/show_bug.cgi?id=345414#c6

With a slim hope of success, I tried to use the old kernel config for 3.19.5 to
create 4.9.z kernel (using make oldconfig ), but valgrind+thunderbird still
segfaults under the resulting kernel. (That was on a different PC.)

It would be great to find out TO WHERE (if it is meaningful) the stray pointer
reported in SIGSEGV points.

I think the routine to report the symbols that get mapped to anonymous
maps area as viewed by valgrind can be very useful for this.

I have a few pet theories for possible issues:

1. Given that when the fatal SIGSEGV is received, the stack trace
seems to messed up somehow (they seem to be too low address in
comparison to other values), I suspect that it may be that valgrind is
experiencing a segfault in the code to set up signal handlers
including SIGSEGV.  (There were some races in linux kernel regarding
some signal issues before after a fork(). Maybe valgrind code inherits similar
problems. But do note that under 4.9.x, the valgrind+thunderbird combination 
still crashes BEFORE fork() is reached. So there may be multpile issues here.

2. I am not sure how valgrind handles this, but, given the different mmap
layout, I wonder if the malloc routine in valgrind may assign an area as a
return value of malloc() which is at the end of sbrk()'ed area. If so, what
happens if multiple-bytes access by x86_64 for strcmp, etc. goes beyond the
sbrk() value during operation. That is what happens, that eager access to speed
up operation by reading extra bytes (8 or 16 octes) and if the tail part of the
octet array falls beyond the user's valid vm address are. Does it get caught as
SIGSEGV? Or is such an access checked byte by byte before such an illegal
access is attemped?

If the reason for the segfault is not one of the above,
I am at my wit's end.

TIA

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

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

[Murz]

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

Murz  changed:

   What|Removed |Added

 CC||mur...@gmail.com

--- Comment #2 from Murz  ---
I also very often got problems with deleting mail, especially after resume from
suspend.

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

[kwin] [Bug 376132] No refresh of complete screen when maximizing window

[Martin Gräßlin]

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

--- Comment #2 from Martin Gräßlin  ---
Please provide the output of:
qdbus org.kde.KWin /KWin supportInformation

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

[kwin] [Bug 377321] KWIN crashes sometimes when opening VBOX client

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is lacking debug symbols. If you are able to 
reproduce please install the debug packages provided by your 
distribution (please ask the distribution support channel on how to 
install them) and attach a new backtrace.

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

[Martin Gräßlin]

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

--- Comment #6 from Martin Gräßlin  ---
Am 2017-03-06 23:49, schrieb Christoph Feck:
> COMMENT # 5 [2] ON BUG 377225 [3] FROM CHRISTOPH FECK
> 
> Martin, do you really need more backtraces?

I'm not seeing to duplicate without knowing that it is truly the same. 
If I get a bug report with lacking debug symbols I all for a newer 
backtrace. In fact I don't even look at the backtrace if it's lacking 
debug symbols.

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

[kwin] [Bug 377294] Application Launcher pops out very slowly

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin  ---
> OpenGL platform interface: EGL

Here we have the reason. Egl on Intel is really bad. It is so bad that 
we removed the option to switch to it. Go back to glx (you need to 
manually edit the config file) and I'm confident the problem will be 
gone.

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

[dolphin] [Bug 377322] New: "Open with" menu can get polluted with extra entries

[Nate Graham]

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

Bug ID: 377322
   Summary: "Open with" menu can get polluted with extra entries
   Product: dolphin
   Version: 16.12.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Plasma 5.9.2 on OpenSUSE Tumbleweed, dolphin-16.12.2-1.1

STEPS TO REPRODUCE:
1. Right-click on a file (in a Dolphin window or on the desktop)
2. Choose Open With > Other...
3. In the "Choose Application" window that appears, type the name of an
application in the search field
4. Hit the OK button

Now the text string you typed in the search bar appears as a new entry in the
Open With sub-menu. You can do this as many times as you want and it will
happen again. Each entry works, but the menu becomes polluted with extra
entries.

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

[dolphin] [Bug 377322] "Open with" menu can get polluted with extra entries

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kwin] [Bug 377321] New: KWIN crashes sometimes when opening VBOX client

[Eric]

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

Bug ID: 377321
   Summary: KWIN crashes sometimes when opening VBOX client
   Product: kwin
   Version: 5.8.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ebelc...@eacbelcher.net
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.49-16-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
On starting a VirtualBox client (Windows 10) with two screens, one window will
sometimes fail during startup. Disabling and restarting the second screen
resolves the symptom.

VirtualBox Graphical User Interface
Version 5.1.14 r112924 (Qt5.6.1)
NAME="openSUSE Leap"
VERSION="42.2"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.2"
PRETTY_NAME="openSUSE Leap 42.2"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.2"
BUG_REPORT_URL="https://bugs.opensuse.org;
HOME_URL="https://www.opensuse.org/

The problem is a reasonably new one, 4-6 weeks and I believe due to a OpenSUSE
patch. VBOX has remained at the above version since it was released.

The crash can be reproduced sometimes.

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

Thread 7 (Thread 0x7f5217ce5700 (LWP 2847)):
#0  0x7f52d2f26b03 in select () at /lib64/libc.so.6
#1  0x7f52d05f9849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f52d05fb0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f52d05fb527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f52d05aafdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f52cafd79c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f52d03ea9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f52b1ffc700 (LWP 2773)):
#0  0x7f52d31f40af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f52cf58093b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f52cf580969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f529871e700 (LWP 2772)):
#0  0x7f52d31f40af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f52a398e533 in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f52a398dd57 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f52b2ffd700 (LWP 2749)):
#0  0x7f52d05fb1f9 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#1  0x7f52d05fb527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#2  0x7f52d05aafdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#4  0x7f52cafd79c8 in  () at /usr/lib64/libQt5Qml.so.5
#5  0x7f52d03ea9e9 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#7  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f52b3fff700 (LWP 2702)):
#0  0x7f52d2f26b03 in select () at /lib64/libc.so.6
#1  0x7f52d05f9849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f52d05fb0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f52d05fb527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f52d05aafdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f52ca1b81d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f52d03ea9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f52b9ee0700 (LWP 2671)):
#0  0x7f52d2f2549d in poll () at /lib64/libc.so.6
#1  0x7f52d20ac3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f52d20adfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f52bab90839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  

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

[Stefano Forli]

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

Stefano Forli  changed:

   What|Removed |Added

 CC||ntro...@gmail.com

--- Comment #31 from Stefano Forli  ---
Bumped into this because of the Escape key issue
(https://bugs.kde.org/show_bug.cgi?id=373354) which doesn't seem to be
mentioned here.

Still exists with the following setup:
KDE Plasma Version: 5.8.5
KDE Frameworks Version: 5.28.0
Qt Version: 5.7.0
(Kubuntu 16.04.2 with backports)

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

[valgrind] [Bug 372861] Test pselect_alarm for Bug 359871 seg faults on RHEL 4

[Tushar]

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

--- Comment #1 from Tushar  ---
The stack trace after commenting out lines 51 and 54 from the test code
pselect_alarm.c and running the compiled binary on RHEL 4 machine

cacofonix:/home/tdnair> /opt/gdb-7.9.1/bin/gdb pselect_alarm.EL4 -c
core.8357 
GNU gdb (GDB) 7.9.1
Copyright (C) 2015 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-unknown-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 pselect_alarm.EL4...done.

warning: core file may not match specified executable file.
[New LWP 8357]
[New LWP 8358]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/tls/libthread_db.so.1".
Core was generated by `./pselect_alarm.EL4'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00382b22e799 in sigprocmask () from /lib64/tls/libc.so.6
(gdb) where
#0  0x00382b22e799 in sigprocmask () from /lib64/tls/libc.so.6
#1  0x00382b2c3438 in pselect () from /lib64/tls/libc.so.6
#2  0x00400a2a in main () at pselect_alarm.c:52

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

[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7

[Tushar]

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

--- Comment #13 from Tushar  ---
Julian,

Thanks for getting back. I tried to find out what is happening and didn't make
much headway.  The problem can be reliably reproduced on an RHEL 4 system.  So
if you want me to instrument something or if you have debug binary for me to
try,  I will be more than happy to do so

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

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

[John Reiser]

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

John Reiser  changed:

   What|Removed |Added

 CC||jrei...@bitwagon.com

--- Comment #5 from John Reiser  ---
Apparently this user has been in a very similar situation before:
 https://bugs.kde.org/show_bug.cgi?id=345414#c3
which is only 6 months ago (September, 2016).

I wonder if the user has followed Julian's advice from bug #345414 Comment 3:
=
In your mozconfig, you need these

  ac_add_options --disable-jemalloc
  ac_add_options --enable-valgrind

and when you run Valgrind, you need this

  --vex-iropt-register-updates=allregs-at-mem-access
=

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

[okular] [Bug 356285] Not enough space for page number

[Oliver Sander]

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

Oliver Sander  changed:

   What|Removed |Added

 CC||oliver.san...@tu-dresden.de

--- Comment #5 from Oliver Sander  ---
Albert, did you post to the correct bug?

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

[kdeconnect] [Bug 371224] SMS Text Message Appears on Desktop Only

[Reuben Martin]

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

Reuben Martin  changed:

   What|Removed |Added

 CC||reube...@gmail.com

--- Comment #1 from Reuben Martin  ---
I have also observed this happening.

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

[juk] [Bug 377320] New: Request to update Juk to KF5 because it is great software!

[Alberto Gonzalez]

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

Bug ID: 377320
   Summary: Request to update Juk to KF5 because it is great
software!
   Product: juk
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: whee...@kde.org
  Reporter: lulosals...@gmail.com
CC: mp...@kde.org
  Target Milestone: ---

Created attachment 104425
  --> https://bugs.kde.org/attachment.cgi?id=104425=edit
DJ'ing with Juk in Canada!

Hello! I am a salsa dance instructor in Canada and I use Juk *A LOT* in my
parties and in my dance classes. I have about 4,400 music files that I organize
with Juk into playlists. Juk is perfect for us because my partner is
comfortable using it, who is not computer savvy. For example, she will not use
Mixxx.

We're using Juk instead of mixing software like Mixxx because of the user
interface and completeness of Juk.

Because we have an Analog Mixer machine, we don't use any other software (Mixxx
once in a while). That is why we are comfortable using Juk! 

We have Juk running on a Kubuntu 16.04 laptop. I've heard that Juk may be
orphaned because it is not being updated from KF4 to KF5. Is this true? It's
our hope that Juk will be upgraded to KF5 along with the rest of the KDE
Applications family because it is an excellent piece of software!

P.S. Our website is http://www.hotsalsadancezone.com/gallery where everyone is
dancing because of Juk. Please feel free to let others know about this and use
our photos to show what Juk is doing to spread salsa to the world.

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

[valgrind] [Bug 377006] valgrind/memcheck segfaults under certain kernel versions (amd64) but not others.

[zephyrus00jp]

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

--- Comment #4 from zephyrus00jp  ---
Created attachment 104424
  --> https://bugs.kde.org/attachment.cgi?id=104424=edit
log of segfault failure under 4.9.x series kernel (debian). with
--trace-syscalls=yes


This is under 4.9.x.

The log file by running a shell script that contains the following command
with
  bash -vx the_script_file 2>&1 | tee /tmp/t-log

strace -ff valgrind --verbose --trace-syscalls=yes --trace-signals=yes
--show-mismatched-frees=no --trace-children=yes
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/thunderbird-bin

"--trace-syscalls" ought to show the syscalls executed by the traced program,
namely, thunderbird-binary.
I see the message about such syscalls written by write(1027, ...) by valgrind.

Because of the way the log was captured, the trace of |write| by strace
is immediately followed by the string written by |write|.


In any case, the following last portion of the log suggests to me that
it is indeed valgrind that is causing the mysterious crash. Isn't it?

--- begin quote
...
write(1027, "SYSCALL[3810,1](202) ... [async]"..., 49SYSCALL[3810,1](202) ...
[async] --> Success(0x0)) = 49
write(1027, " ", 1 ) = 1
write(1027, "\n", 1
)= 1
mmap(0x802fb, 196608, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x802fb
munmap(0x802f9, 131072) = 0
gettid()= 3810
write(1029, "Q", 1) = 1
gettid()= 3810
read(1028, "Q", 1)  = 1
gettid()= 3810
rt_sigprocmask(SIG_SETMASK, ~[], ~[KILL STOP], 8) = 0
rt_sigtimedwait(~[], 0x802f8de20, {tv_sec=0, tv_nsec=0}, 8) = -1 EAGAIN
(Resource temporarily unavailable)
rt_sigprocmask(SIG_SETMASK, ~[KILL STOP], NULL, 8) = 0
gettid()= 3810
mmap(0x802d3d000, 16384, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x802d3d000
getpid()= 3810
write(1027, "--3810-- REDIR: 0x52e68b0 (libst"..., 115--3810-- REDIR: 0x52e68b0
(libstdc++.so.6:operator delete(void*)) redirected to 0x4c2d19c (operator
delete(void*))
) = 115
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xffeffa22c} ---
+++ killed by SIGSEGV +++
/home/ishikawa/bin/run-valgrind-thunderbird.sh: line 13:  3808 Segmentation
fault  strace -ff valgrind --verbose --trace-syscalls=yes
--trace-signals=yes --show-mismatched-frees=no --trace-children=yes
/NREF-COMM-CENTRAL/objdir-tb3/dist/bin/thunderbird-bin

--- end quote 

The address reported is slightly changed: I think it is due to the slight 
change in the source code..
final error in the 4.9.x series: 

The following is the old address reported in sigsegv.

gettid()= 3174
mmap(0x803041000, 16384, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0x803041000
getpid()= 3174
write(1027, "--3174-- REDIR: 0x52e68b0 (libst"..., 115) = 115
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xffeffa24c} ---
+++ killed by SIGSEGV +++


The address in SIGSEGV is interesting:
>From the old log:
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xffeffa24c} ---

>From the current log:
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xffeffa22c} ---


It is BELOW the last (anonymous) map (reported in the old log)
--- begin
>From 4.9.x series kernel: Failure case
  ...
806203000-806334000 rwxp  00:00 0 
806af9000-806ce2000 rwxp  00:00 0   <-- the si_addr is after this.
ffeffe000-fff001000 rw-p  00:00 0   <---the si_addr is before this. 
7ffd0347-7ffd03492000 rw-p  00:00 0 
[stack]
7ffd034ba000-7ffd034bc000 r--p  00:00 0  [vvar]
ff60-ff601000 r-xp  00:00 0 
[vsyscall]
(gdb) cont
--- end

Hope this helps.

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

[kdeconnect] [Bug 377319] New: Integrate PulseAudio volume control (e.g. Reverb)

[kmi]

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

Bug ID: 377319
   Summary: Integrate PulseAudio volume control (e.g. Reverb)
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: kamika...@web.de
  Target Milestone: ---

Would be cool if KDE Connect could set the volume not only for MPRIS media
players. There exists at least one FOSS project to implement a PulseAudio
mixer: https://github.com/goozler/reverb

If feasible, KDE Connect should implement that functionality (maybe by
importing aforementioned GPLed code).

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

[dolphin] [Bug 377318] New: MP3 files with a % symbol in file name do not play in preview pane

[Alberto Gonzalez]

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

Bug ID: 377318
   Summary: MP3 files with a % symbol in file name do not play in
preview pane
   Product: dolphin
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: information
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: lulosals...@gmail.com
  Target Milestone: ---

Using Dolphin 16.04.3 (and earlier), previewing .mp3 files that have a % sign
in the file name prevents from playing its preview. This may occur for other
media files but only mp3 were tested.

How to duplicate:

Find an .mp3 file, for example: "02 - Mia.mp3" and then highlight it in
Dolphin. In the right Information pane, click the circular play button. The mp3
should play just fine. 

Now rename the file to "02 - Mia 10%.mp3" (note the % symbol). Re-highlight the
file and move over to the Information pane at the right of Dolphin. Click the
circular play button. Nothing happens, no audio playback.

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

[plasmashell] [Bug 367831] chinese word render error

[TOM Harrison]

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

--- Comment #1 from TOM Harrison  ---
this is still happened in 5.9.3

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

[kdeconnect] [Bug 341175] Remote filesystem does not work with Android L

[HD]

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

--- Comment #24 from HD  ---
Small update: Manually specifying folders in my sdcard works, I just can't list
the sdcard's main/"root" folder. So for instance ...//music works.
Doesn't seem to be affected by changing perms.

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

[plasmashell] [Bug 375331] Black screen after resuming from hibernation

[wahn]

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

wahn  changed:

   What|Removed |Added

 CC||ontw...@gmail.com

--- Comment #6 from wahn  ---
SUSPEND was fine until 2017MAR04 after I installed updates (could be
coincidence) 1- SUSPEND caused a reboot. Although it did not happen again. 2-
SUSPEND went fine, but at wake up, computer started, but lost screen (all
black) lost cursor, and system was not responding to keyboard.
I had to reboot.

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

[digikam] [Bug 351866] Make focus to input field after adding a face rectangle as an option and not by default

[Yingjie Liu]

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

--- Comment #8 from Yingjie Liu <1127553...@qq.com> ---
Created attachment 104423
  --> https://bugs.kde.org/attachment.cgi?id=104423=edit
which region

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

[digikam] [Bug 351866] Make focus to input field after adding a face rectangle as an option and not by default

[Yingjie Liu]

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

--- Comment #7 from Yingjie Liu <1127553...@qq.com> ---
(In reply to Wolfgang Scheffner from comment #6)
> (In reply to Yingjie Liu from comment #2)
> > Created attachment 104401 [details]
> > Action added for controlling the focus in the text field
> > 
> > Hi,
> > I add a QAction in the toolbar beside the "Show Fullscreen" action, ...
> 
> Just something about usability / GUI: I don't like the idea of having that
> action in the Main Toolbar. Should be better somewhere in the Left Sidebar
> so that it disappears once you leave People View.
> 
> Wolfgang Scheffner (documenter)

Hi, Wolfgang,
I added the action in the people's view which is shown in attachment "which
region", and it will disappear when user leave people view. Do you mean that I
have to add the action in region A (which is able to add a left sidebar) I
circled in attachment "which region"? Thanks.
Yingjie Liu

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

[kdenlive] [Bug 377255] Git master - multiple crashes on Clip:clone

[alcinos]

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

--- Comment #13 from alcinos  ---
For the Mlt problem, I've already opened an issue:
https://github.com/mltframework/mlt/issues/212

Your workaround seems good enough for now, but we must make sure that there is
no other way to trigger race conditions. The XML parsing seems a bit clanky
overall on MLT's side…
Anyway, I'd advocate for a non XML solution in the long run. One benefit is
speed, I experienced a decent speed-up with the temporary solution without XML

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

[kdeconnect] [Bug 341175] Remote filesystem does not work with Android L

[HD]

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

HD  changed:

   What|Removed |Added

 CC||haako...@ifi.uio.no

--- Comment #23 from HD  ---
I have similar permission problems, on Android 7.1 (also happened on Android
6). 

I can browse my general files fine, as well as both the camera folders on
internal and sdcard storage. However I can't browse the files on the sdcard
main folder, it doesn't give me an error in dolphin, it just shows zero files.
It tries getting the correct folder, but just shows nothing. 

Everyone I know using kdeconnect has the same issue of not being able to access
the sdcard itself.

Permissions:
drwxrwx--x 21 root sdcard_rw   
drwxrwx--x  5 root sdcard_rw/DCIM

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

[Discover] [Bug 376977] absence de liste des applications dans DISCOVER

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #2 from Aleix Pol  ---


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

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

[Discover] [Bug 376241] software centre is empty

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||ab7...@gmail.com

--- Comment #21 from Aleix Pol  ---
*** Bug 376977 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 376988] help with software there are no packeges

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[Discover] [Bug 376241] software centre is empty

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||harmondavi...@yahoo.com

--- Comment #19 from Aleix Pol  ---
*** Bug 376988 has been marked as a duplicate of this bug. ***

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

[Discover] [Bug 376914] no programs

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---


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

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

[Discover] [Bug 376241] software centre is empty

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 CC||irr...@citromail.hu

--- Comment #20 from Aleix Pol  ---
*** Bug 376914 has been marked as a duplicate of this bug. ***

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

[umbrello] [Bug 377317] No extension points in use case diagrams

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

 OS|Linux   |All

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

[umbrello] [Bug 377317] New: No extension points in use case diagrams

[Ralf Habacker]

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

Bug ID: 377317
   Summary: No extension points in use case diagrams
   Product: umbrello
   Version: Git
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de
  Target Milestone: ---

Created attachment 104422
  --> https://bugs.kde.org/attachment.cgi?id=104422=edit
use case diagram showing what is currently implemented

Umbrello use case diagrams do not support extension points. 

For an example see
https://de.wikipedia.org/wiki/Anwendungsfalldiagramm#/media/File:Uml-UseCase-Beispiel2.svg

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

[umbrello] [Bug 123633] new diagram type: object diagram

[Ralf Habacker]

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

--- Comment #10 from Ralf Habacker  ---
Created attachment 104421
  --> https://bugs.kde.org/attachment.cgi?id=104421=edit
related xmi model file

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

[kate] [Bug 377316] New: Kate and Kwrite don't remember your position in documents

[Nate Graham]

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

Bug ID: 377316
   Summary: Kate and Kwrite don't remember your position in
documents
   Product: kate
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Plasma 5.9.2 on OpenSUSE Tumbleweed, kate 16.12.2-1.1


STEPS TO REPRODUCE
1. Open Kate or Kwrite and open a document
2. Scroll to some part of the document
3. Close Kate or Kwrite
4. Open that same document in Kate or Kwrite again


EXPECTED RESULTS
The document is opened, displaying the same place you were looking when you
closed it


ACTUAL RESULTS
The document is opened and the very beginning is displayed.


REGRESSION
Happens in both Kate and Kwrite. Gedit does remember the position, which is a
nice feature.

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

[kate] [Bug 377316] Kate and Kwrite don't remember your position in documents

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[umbrello] [Bug 123633] new diagram type: object diagram

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

 Attachment #104418|0   |1
is obsolete||

--- Comment #9 from Ralf Habacker  ---
Created attachment 104420
  --> https://bugs.kde.org/attachment.cgi?id=104420=edit
State of implemented use cases (update)

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

[kate] [Bug 377315] Kate doesn't remember window position (new window always opens in top left corner)

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
Works properly in Kwrite; the window position is saved as expected.

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

[kate] [Bug 377315] New: Kate doesn't remember window position (new window always opens in top left corner)

[Nate Graham]

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

Bug ID: 377315
   Summary: Kate doesn't remember window position (new window
always opens in top left corner)
   Product: kate
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Plasma 5.9.2 on OpenSUSE Tumbleweed, kate 16.12.2-1.1


STEPS TO REPRODUCE
1. Open Kate, with or without a specific document
2. Move the Kate window somewhere that's not the top-left corner, where it
spawned
3. Close Kate
4. Open Kate again


EXPECTED RESULTS
Kate creates a new window in exactly the same place where the last window was
closed.


ACTUAL RESULTS
Kate creates a new window in the top-left corner of the screen, not at the
location where you last closed a Kate window.


REGRESSION
The window's *size* is remembered if you change it; the positioning is not.

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

[kate] [Bug 377315] Kate doesn't remember window position (new window always opens in top left corner)

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 337060] Desktop toolbox can visually conflict with (e.g. overlap) containment contents

[Rik Mills]

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

--- Comment #18 from Rik Mills  ---
(In reply to Eike Hein from comment #17)
> Patch under review https://phabricator.kde.org/D4956

Works with broulik's panel/toolbox/icon setup as shown in video in that phab
review, but does not work in the default plasma arrangement; i.e. panel at
bottom, toolbox top left, and Home and Wastebin items in default places.

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Jure Repinc]

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

Jure Repinc  changed:

   What|Removed |Added

 CC||j...@holodeck1.com

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

[plasmashell] [Bug 377251] Plasma suddenly stop

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||junta.kristo...@gmail.com

--- Comment #2 from David Edmundson  ---
*** Bug 376096 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 376119] Application Launcher does not appear on button press after a certain duration of uptime

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Not seen many other reports of this.

Can you run plasmashell from a command line, and then include any output.

Are you switching between monitor setups?

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

[kwin] [Bug 376132] No refresh of complete screen when maximizing window

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

Product|plasmashell |kwin
   Assignee|aleix...@kde.org|kwin-bugs-n...@kde.org
  Component|Multi-screen support|general
 CC||k...@davidedmundson.co.uk
   Target Milestone|1.0 |---

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

[plasmashell] [Bug 376726] Can't switch to Global Menu by hitting Alt key.

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #4 from David Edmundson  ---
*** Bug 376897 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 376897] Adding a keyboard shortcut to activate the global menu

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from David Edmundson  ---


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

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

[plasmashell] [Bug 357443] black/invisible squares on systray and top left of screen after kwin restarted

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||p...@ralfj.de

--- Comment #6 from David Edmundson  ---
*** Bug 375686 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 375686] Black square in top-left corner

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||k...@davidedmundson.co.uk
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Edmundson  ---


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

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

[plasmashell] [Bug 376560] [Feature request] Grouping Plasmoid

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #3 from David Edmundson  ---
Thanks, but I'm not going to add more config options and features without a
reason.

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

[Discover] [Bug 377314] New: Crash when clicking on a GTK3.x Theme

[Russell Greene]

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

Bug ID: 377314
   Summary: Crash when clicking on a GTK3.x Theme
   Product: Discover
   Version: 5.9.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: russellgree...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.9.3)

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

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

If you go plasma addons->GTK3.x themes->and click on any of the themes it
crahses.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4a30e767c0 (LWP 5560))]

Thread 10 (Thread 0x7f49637fe700 (LWP 5617)):
#0  0x7f4a28ec04b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4a0d094e44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7f4a06fd5394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7f4a0d09412c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7f4a28eba454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f4a2c3677df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f4963fff700 (LWP 5616)):
#0  0x7f4a28ec010f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4a2cd5758b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4a3022f665 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f4a3022ff72 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f4a2cd566d8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f4a28eba454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f4a2c3677df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f49fd543700 (LWP 5572)):
#0  0x7f4a26f90753 in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f4a26f92d73 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f4a26f936cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f4a26f938bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f4a2cf8606b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f4a2cf2f89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f4a2cd51a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f4a2cd566d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f4a28eba454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f4a2c3677df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f49ffbd4700 (LWP 5568)):
#0  0x7f4a2c35e48d in poll () at /usr/lib/libc.so.6
#1  0x7f4a26f937a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f4a26f938bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f4a2cf8606b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f4a2cf2f89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f4a2cd51a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f4a2cd566d8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f4a28eba454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f4a2c3677df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f4a0530b700 (LWP 5567)):
#0  0x7f4a2cf85603 in  () at /usr/lib/libQt5Core.so.5
#1  0x7f4a26f92c8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f4a26f936cb in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f4a26f938bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f4a2cf8606b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f4a2cf2f89a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f4a2cd51a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f4a301bdfd6 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7f4a2cd566d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f4a28eba454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f4a2c3677df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f4a0cddc700 (LWP 5565)):
#0  0x7f4a28ec04b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4a0d094e44 in  () at /usr/lib/libGLX_nvidia.so.0
#2  0x7f4a06fd5394 in  () at /usr/lib/libnvidia-glcore.so.378.13
#3  0x7f4a0d09412c in  () at /usr/lib/libGLX_nvidia.so.0
#4  0x7f4a28eba454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f4a2c3677df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f4a0700 (LWP 5563)):
#0  0x7ffc98fe8bd0 in clock_gettime ()
#1  0x7f4a2c3746b6 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7f4a2cf85201 in  () at /usr/lib/libQt5Core.so.5
#3  

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Ernie]

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

--- Comment #242 from Ernie  ---
Well said
On Mar 6, 2017 3:37 PM, "Jay"  wrote:

> https://bugs.kde.org/show_bug.cgi?id=341143
>
> Jay  changed:
>
>What|Removed |Added
> 
> 
>  CC||atlp...@excite.com
>
> --- Comment #241 from Jay  ---
> For all the good things in Plasma 5, they are worthless owing to the loss
> of
> ability to set different wallpaper for each virtual desktop.  That's how I
> keep
> track of which desktop I'm working in.  It greatly aided efficiency.
>
> Without this vital feature, I'm better off using XFCE because it boots two
> seconds faster and has fewer parts that kill the DE when things get messed
> up.
> I've always used XFCE to recover from fatal KDE errors.  Might as well use
> it
> for my DE.
>
> Thanks to the KDE team for the many years of wonderful Plasma pre-5.  I
> look
> forward to your new programs and features.  There are better DE's than
> Plasma
> when there's no wallpaper difference, especially when KDE's other great
> features are loaded into XFCE.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

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

[Akonadi] [Bug 377273] Akonadi server crashed while viewing mail

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

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

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

[Akonadi] [Bug 376976] Akonadi server crashed while using KMail

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||dennis.schridde@uni-heidelb
   ||erg.de

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

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

[Akonadi] [Bug 376923] Akonadi crashes on restart when KMail hangs on "Retrieving folder content" (POP accounts). Akonadi also creates many dupplicates.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

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


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

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

[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||s.pa...@spiekerbros.com

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

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

[plasmashell] [Bug 376096] Plasma crashed on login

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #2 from David Edmundson  ---


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

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

[Breeze] [Bug 377008] Breeze scrollbar width with Firefox (version >= 52) broken (too wide)

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

--- Comment #2 from Dr. Chapatin  ---
I updated to Firefox 52 on Arch today and I can confirm this bug.

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

[korganizer] [Bug 361419] Unaccepted Google calendar events not shown

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

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

--- Comment #6 from Daniel Vrátil  ---
Turns out the events are not shown because they are automatically added to
"Open Invitations" virtual search folder which is normally not shown in
KOrganizer.

At the same time, KOrganizer does not support a single event being present in
multiple calendars at once and you guys are simply hit by the case when the
"Open Invitations" folder is "above" your calendar folders. This leads to
KOrganizer not showing the actual invitation in the real calendar.

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

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

[Cqoicebordel]

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

Cqoicebordel  changed:

   What|Removed |Added

 CC||david.bar...@wanadoo.fr

--- Comment #4 from Cqoicebordel  ---
I confirm I have the same behavior in 1.6.1, with stock message app from
CyanogenMod (Android 2.3.3).
Let's note also that I have two apps creating backups for my SMS (they send it
to a mail address), and none of them pick them up.

Maybe the differences between your behavior and ours is the API version (I see
there are some behavior changes in the docs starting from API 19). Or maybe
it's because you use SmsManager instead of an intent using the default app. I
have no idea, I'm not an Android dev.

Anyway, I see that behavior too, so I can confirm.

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

[plasmashell] [Bug 377313] Touchpad indicator says `no touchpad found` under Wayland

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Component|System Tray |generic-wayland
 CC||k...@davidedmundson.co.uk

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

[kdenlive] [Bug 377255] Git master - multiple crashes on Clip:clone

[Jean-Baptiste Mardelle]

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

--- Comment #12 from Jean-Baptiste Mardelle  ---
properties.inherit does not copy the filters. However, trying to copy the
filters on the clips copied with properties.inherit caused various corruptions
and crashes for example on clip reload. My guess is that properties.inherit
also copies some internal parameters that should not be duplicated between
clips.

Since all this was really last minute for 16.12, I opted for a different
workaround that I hope will not reveal worse. Based on the conclusion that the
producer xml was messing the master profile when parsing a  tag in the
xml, in the clone() method, I manually removed the "profile" tag, avoiding the
threading / corruption problem.

I think the xml producer should allow creating an MLT producer without messing
the project profile, so in my opinion, something is wrong in MLT. Don't you
think ? I will think a little more about it and ask on MLT's list what they
think about it.

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

[plasmashell] [Bug 376848] Folder View not rendering images correctly.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #3 from Christoph Feck  ---
There are two thumbnails at the right-hand side (inside the black area), which
really look pixelated.

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

[kwin] [Bug 377225] kwin crash when saving VirtualBox settings

[Christoph Feck]

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

--- Comment #5 from Christoph Feck  ---
Martin, do you really need more backtraces? It is clear that all these
https://bugs.kde.org/buglist.cgi?product=kwin_status=NEEDSINFO=QScriptEngine%3A%3AnewQObject_type=casesubstring
are duplicates of bug 363224.

I suggest to ask reporters for exact steps to reproduce. Additionally, pointing
them to the duplicate allows them to follow what has been investigated so far,
e.g. which effects are causing it.

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

[plasmashell] [Bug 375517] Submenu in context menu opening on another monitor

[Maxim]

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

Maxim  changed:

   What|Removed |Added

 CC||ya.maxi...@yandex.ru

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

[plasmashell] [Bug 377313] New: Touchpad indicator says `no touchpad found` under Wayland

[Dr . Chapatin]

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

Bug ID: 377313
   Summary: Touchpad indicator says `no touchpad found` under
Wayland
   Product: plasmashell
   Version: 5.8.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: yy...@gmx.com
  Target Milestone: 1.0

Tested in plasma 5.9.3 Wayland session on Arch.
Enable the touchpad indicator/widget in system tray settings, its icon is
greyed the tooltip says `no touchpad found`.
My touchpad works fine under Wayland.

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

[kdenlive] [Bug 356493] "Save Layout As" menu option in menu bar redundant? Suggest removing "Save Layout As" sub-menu text

[Ashark]

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

--- Comment #1 from Ashark  ---
You can just remove "Save As " from kdenlive/src/layoutmanagement.cpp on line
34.
But I am not sure if current msgid "Save As Layout %1" will be automatically
removed from po files of translation teams.

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

[systemsettings] [Bug 377312] Colosing of Plasma settings

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||k...@privat.broulik.de
  Latest Commit||https://cgit.kde.org/kcmuti
   ||ls.git/commit/?id=3dd734584
   ||1be292b3dff91acbd59ac0d0a98
   ||1790
 Resolution|--- |FIXED

--- Comment #1 from Kai Uwe Broulik  ---
Thanks for your report, this has been fixed in KDE Frameworks 5.32.

https://cgit.kde.org/kcmutils.git/commit/?id=3dd7345841be292b3dff91acbd59ac0d0a981790

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

[plasmashell] [Bug 366062] Icons for Electron apps are too large in the System Tray

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

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

[systemsettings] [Bug 377312] New: Colosing of Plasma settings

[Kamil Szmit]

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

Bug ID: 377312
   Summary: Colosing of Plasma settings
   Product: systemsettings
   Version: 5.8.6
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k.a.sz...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.6)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.9.13-200.fc25.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- I had set settings of apperance of Plasma

- Windows do not have title bars.

-- Backtrace:
Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9c427ea8c0 (LWP 7902))]

Thread 8 (Thread 0x7f9bff5f2700 (LWP 8414)):
#0  0x7f9c4cff801d in poll () at /lib64/libc.so.6
#1  0x7f9c45e5d166 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9c45e5d27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9c4ddfe6eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f9c4ddaf68a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f9c4dc0c5e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f9c4dc109ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f9c4a0c36ca in start_thread () at /lib64/libpthread.so.0
#8  0x7f9c4d003f7f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f9c0d66f700 (LWP 8411)):
#0  0x7f9c4cff801d in poll () at /lib64/libc.so.6
#1  0x7f9c45e5d166 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f9c45e5d27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f9c4ddfe6eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f9c4ddaf68a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f9c4dc0c5e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f9c4dc109ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f9c4a0c36ca in start_thread () at /lib64/libpthread.so.0
#8  0x7f9c4d003f7f in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f9c0e8b8700 (LWP 8409)):
#0  0x7fff48eb6b12 in clock_gettime ()
#1  0x7f9c4d012726 in clock_gettime () at /lib64/libc.so.6
#2  0x7f9c4dca7b31 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7f9c4ddfcd99 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7f9c4ddfd195 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f9c4ddfe38c in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7f9c4ddfe455 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#7  0x7f9c45e5c69d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#8  0x7f9c45e5d08b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#9  0x7f9c45e5d27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#10 0x7f9c4ddfe6eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#11 0x7f9c4ddaf68a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#12 0x7f9c4dc0c5e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#13 0x7f9c4c7d04e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#14 0x7f9c4dc109ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#15 0x7f9c4a0c36ca in start_thread () at /lib64/libpthread.so.0
#16 0x7f9c4d003f7f in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f9c1a61e700 (LWP 8165)):
#0  0x7fff48eb6b12 in clock_gettime ()
#1  0x7f9c4d012726 in clock_gettime () at /lib64/libc.so.6
#2  0x7f9c4dca7b31 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7f9c4ddfcd99 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7f9c4ddfd195 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f9c4ddfe38c in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7f9c4ddfe455 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#7  0x7f9c45e5c69d in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#8  0x7f9c45e5d08b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#9  0x7f9c45e5d27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#10 0x7f9c4ddfe6eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#11 0x7f9c4ddaf68a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#12 0x7f9c4dc0c5e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#13 0x7f9c4c7d04e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#14 0x7f9c4dc109ca in 

[rsibreak] [Bug 377274] Option to reset timer

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Astals Cid  ---
Where would you add that option?
Why do you need that? 
Can't you just press "ignore" when the popup appears?

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

[systemsettings] [Bug 377139] Changing widget style does not work

[North]

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

--- Comment #6 from North  ---
The problem is seen in Dolphin.  I did not realise the widget style is supposed
to apply only to KDE applications.

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

[frameworks-kxmlgui] [Bug 375555] Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut"

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED
  Latest Commit||https://commits.kde.org/kco
   ||nfig/59b184735c057482995cc0
   ||a8014bb90d12f09cf9

--- Comment #22 from Albert Astals Cid  ---
Git commit 59b184735c057482995cc0a8014bb90d12f09cf9 by Albert Astals Cid.
Committed on 06/03/2017 at 21:58.
Pushed by aacid into branch 'master'.

Sanitize shortcut list on read/write from kdeglobals

For some reason some people have kdeglobals entries like
   Close=Ctrl+W; Ctrl+Esc; Ctrl+W; Ctrl+Esc;
having the same shortcut more than once in the shortcut declaration is clearly
bogus so fix it
REVIEW: 129987

M  +20   -0src/gui/kstandardshortcut.cpp

https://commits.kde.org/kconfig/59b184735c057482995cc0a8014bb90d12f09cf9

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

[umbrello] [Bug 123633] new diagram type: object diagram

[Ralf Habacker]

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

--- Comment #8 from Ralf Habacker  ---
Created attachment 104418
  --> https://bugs.kde.org/attachment.cgi?id=104418=edit
State of implemented use cases

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

[yakuake] [Bug 365030] terminal doesn't get focus after opening yakuake

[André Martins]

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

--- Comment #2 from André Martins  ---
Ok, I think the main bug was solved but there's some lose ends.

1. Open yakuake with F12
2. CTRL+SHIFT+9 to create a new vertical split.
3. Close yakuake with F12.
4. Open yakuake with F12.
5. Notice the pointer always jumps to the other terminal every time you open
and close yakuake.

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

[dolphin] [Bug 377304] DOLPHIN CRASH WHEN CONNECTING WITH smb:// to Windows 10

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

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


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

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

[kio-extras] [Bug 359278] Crash when opening smb:// folders

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||hi...@tahiti-ingenierie.pf

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

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

[plasmashell] [Bug 376899] FolderView - Folder Preview PopUps - Closing on Mouse Pointer Enter

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #3 from Eike Hein  ---
This was fixed by e80a4b87cfa98708724942794ca6f051974bb5c0 which is indeed in
5.8.6.

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

[plasmashell] [Bug 377311] New: a panel crash

[Pali]

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

Bug ID: 377311
   Summary: a panel crash
   Product: plasmashell
   Version: 5.7.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pstr...@pobox.sk
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.7.4)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.10.0-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
panel crashed after click on application after search them.

The crash can be reproduced sometimes.

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

Thread 24 (Thread 0x7f154e7fc700 (LWP 3622)):
#0  0x7f165c80010f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f165d6f419b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f15a332be90 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f15a3330048 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f15a33300a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f15a332ded9 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f165d6f32e8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f165c7fa454 in start_thread () at /lib64/libpthread.so.0
#10 0x7f165d00137f in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f154effd700 (LWP 3621)):
#0  0x7f165c80010f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f165d6f419b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f15a332be90 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f15a3330048 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f15a33300a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f15a33300a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f15a33300a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f15a33300a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f15a33300a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7f15a33300a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7f15a33300a2 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#19 0x7f15a332ded9 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#20 0x7f165d6f32e8 in  () at /usr/lib64/libQt5Core.so.5
#21 0x7f165c7fa454 in start_thread () at /lib64/libpthread.so.0
#22 0x7f165d00137f in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f154f7fe700 (LWP 3620)):
#0  0x7f165c80010f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f165d6f419b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f15a332be90 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f15a3330048 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f15a332b00d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f15a33300a2 

[plasmashell] [Bug 377050] Plasmashell crashes whenever I close VLC

[Michail Vourlakos]

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

--- Comment #6 from Michail Vourlakos  ---
user also added that tried the following players:

DragonPlayer
Amarok
MPV
MPlayer

and the crash does not occur...

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Jay]

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

Jay  changed:

   What|Removed |Added

 CC||atlp...@excite.com

--- Comment #241 from Jay  ---
For all the good things in Plasma 5, they are worthless owing to the loss of
ability to set different wallpaper for each virtual desktop.  That's how I keep
track of which desktop I'm working in.  It greatly aided efficiency.

Without this vital feature, I'm better off using XFCE because it boots two
seconds faster and has fewer parts that kill the DE when things get messed up. 
I've always used XFCE to recover from fatal KDE errors.  Might as well use it
for my DE.

Thanks to the KDE team for the many years of wonderful Plasma pre-5.  I look
forward to your new programs and features.  There are better DE's than Plasma
when there's no wallpaper difference, especially when KDE's other great
features are loaded into XFCE.

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

[kdeconnect] [Bug 377040] SFTP: filesystem unmounts itself after a while

[Albert Vaca]

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

--- Comment #4 from Albert Vaca  ---
Hey Yuxan,

Thanks for your patch! Why don't you submit it through
https://reviewboard.kde.org/ ? I have some questions/comments and it's easier
over there.

Thanks again,
Albert

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

[systemsettings] [Bug 377310] Single/double click option is in inappropriately in the mouse settings

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
   Platform|Other   |openSUSE RPMs

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

[systemsettings] [Bug 377310] New: Single/double click option is in inappropriately in the mouse settings

[Nate Graham]

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

Bug ID: 377310
   Summary: Single/double click option is in inappropriately in
the mouse settings
   Product: systemsettings
   Version: 5.9.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: pointedst...@zoho.com
CC: unassigned-b...@kde.org
  Target Milestone: ---

To make Dolphin files and folders open with double-clicks instead of
single-clicks, you currently need to change a setting in systemsettings > Input
Devices > Mouse > "Double-click to open files and folders ()select icons on
first click)"

This is an inappropriate place for the setting, since it's not mouse-specific
(I need to double-click with my laptop's touchpad, for example). It should be
in Dolphin's settings, or somewhere else in systemsettings (Icons or Desktop
Behavior seem more appropriate).

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

[systemsettings] [Bug 377309] When Dolphin icons are set to double-click mode, systemsettings inappropriately uses the same behavior in icon view

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
Related: https://bugs.kde.org/show_bug.cgi?id=254431

However in my case this occurred on a brand new install (just set up the system
yesterday and this was the first thing I changed).

If this is caused by an OpenSUSE patch, let me know and I'll take it up with
them.

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

[systemsettings] [Bug 377309] When Dolphin icons are set to double-click mode, systemsettings inappropriately uses the same behavior in icon view

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[okular] [Bug 356285] Not enough space for page number

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||aa...@kde.org
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #4 from Albert Astals Cid  ---
I can not reproduce this problem, do you do something special when opening the
file? Or is it the second file you open? or?

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

[systemsettings] [Bug 377309] New: When Dolphin icons are set to double-click mode, systemsettings inappropriately uses the same behavior in icon view

[Nate Graham]

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

Bug ID: 377309
   Summary: When Dolphin icons are set to double-click mode,
systemsettings inappropriately uses the same behavior
in icon view
   Product: systemsettings
   Version: 5.9.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: treeview
  Assignee: sourtooth+ssb...@gmail.com
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Plasma 5.9.2 on OpenSUSE Tumbleweed

SUMMARY
systemsettings icons always respond to a single-click irrespective of Dolphin's
files and folders click behavior

STEPS TO REPRODUCE:
1. systemsettings > Input Devices > Mouse > "Double-click to open files and
folders ()select icons on first click)"
2. Close and re-open systemsettings
3. Make sure systemsettings is using icon view, not tree view
4. Single-click on any of the icons

EXPECTED RESULT:
Clicking on the icon should take you to a new page, since it's a button, not a
file or a folder

ACTUAL RESULT:
Clicking on the icon uselessly selects it, and you have to double-click to go
to the desired new page. These icons are buttons, not files or folders. Buttons
produce their desired action on a single-click; a double-click behavior doesn't
make any sense here.

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