[plasmashell] [Bug 401558] New: Plasma crashes when changing the battery icon visibility

2018-11-30 Thread Neil Turton 
https://bugs.kde.org/show_bug.cgi?id=401558

Bug ID: 401558
   Summary: Plasma crashes when changing the battery icon
visibility
   Product: plasmashell
   Version: 5.12.6
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: 0neiltk@chiark.greenend.org.uk
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.6)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-39-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

-- Information about the crash:
- To reproduce:
 1. Open system tray settings
 2. Select the "Entries" tab on the left
 3. Change the visiblity of "Battery and Brightness"
 4. Click "Okay".

At this point, the desktop background goes black and the panel at the top
disappears.  They both return to normal after a moment.

Effects of different visibility changes:
  "Auto" to "Shown": Crashes
  "Shown" to "Auto": Crashes
  "Hidden" to "Auto": No crash
  "Auto" to "Hidden": No crash
  "Hidden" to "Shown": Crashes
  "Shown" to "Hidden": Crashes

The cases which don't crash are the ones where the actual visibility of the
icon doesn't change.  At the time of testing, Auto means that the icon is
hidden.

Clicking the "Apply" button instead of "Okay" in step 4 occasionally causes a
crash, but only rarely.

-- 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 0x7fa7a21a4800 (LWP 5069))]

Thread 17 (Thread 0x7fa69d7fa700 (LWP 24093)):
#0  0x7fa79b02a9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55eff79681b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fa79b02a9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55eff7968160, cond=0x55eff7968188) at pthread_cond_wait.c:502
#2  0x7fa79b02a9f3 in __pthread_cond_wait (cond=0x55eff7968188,
mutex=0x55eff7968160) at pthread_cond_wait.c:655
#3  0x7fa79bea459b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa6e6277ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fa6e627bba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fa6e627bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fa6e6279a6b in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7fa79bea316d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fa79b0246db in start_thread (arg=0x7fa69d7fa700) at
pthread_create.c:463
#12 0x7fa79b79e88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7fa69dffb700 (LWP 24092)):
#0  0x7fa79b02a9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55eff79681b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fa79b02a9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55eff7968160, cond=0x55eff7968188) at pthread_cond_wait.c:502
#2  0x7fa79b02a9f3 in __pthread_cond_wait (cond=0x55eff7968188,
mutex=0x55eff7968160) at pthread_cond_wait.c:655
#3  0x7fa79bea459b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa6e6277ad5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fa6e627bba8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fa6e627bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fa6e627bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7fa6e627bc02 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7fa6e6276c8d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5

[qaccessibilityclient] [Bug 375419] New: KDE accessibility dialogue appears at inappropriate times

2017-01-22 Thread Neil Turton 
https://bugs.kde.org/show_bug.cgi?id=375419

Bug ID: 375419
   Summary: KDE accessibility dialogue appears at inappropriate
times
   Product: qaccessibilityclient
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gladh...@kde.org
  Reporter: 0neiltk@chiark.greenend.org.uk
  Target Milestone: ---

I can reproduce this problem with a guest session, so it isn't due to a
particularly strange configuration.

  1. Start a KDE session
  2. Open System settings and go to Desktop Behavior/Accessibility
  3. On the Activation Gestures tab, disable "Use gestures for activating
sticky keys and slow keys".
  4. Enable "Show a confirmation dialog whenever a keyboard accessibility
feature is toggled".
  5. Open an xterm (not konsole)
  6. Run this command to ring the terminal bell: perl -e 'print pack("C",7)'
  7. A dialogue appears reading 'Do you really want to activate "Slow keys",
"Bounce keys", and "Mouse keys"?'
  8. Select "Deactivate all AccessX features and gestures".
  9. Press the "No" button to close the dialog.
 10. Run the command to ring the terminal bell: perl -e 'print pack("C",7)'
 11. The dialogue appears again.

I would expect the system bell to be rung without generating a dialogue.

Step 6 can be replaced by pressing the backspace key or tab twice or a variety
of other actions which cause xterm to ring the bell.

A workaround for this bug is to disable the confirmation dialog which was
enabled in step 4.  I don't think there's any side-effect of the workaround.

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

[plasmashell] [Bug 375113] New: Plasmashell crashes when selecting a status widget with "Status and Notifications" open.

2017-01-15 Thread Neil Turton 
https://bugs.kde.org/show_bug.cgi?id=375113

Bug ID: 375113
   Summary: Plasmashell crashes when selecting a status widget
with "Status and Notifications" open.
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: 0neiltk@chiark.greenend.org.uk
  Target Milestone: 1.0

I can reliably crash plasmashell as follows:
  Make sure the touchpad is on the "Status & Notifications" panel.
  Select Touchpad settings.
  Assign a "Meta+Shift+T" as the shortcut for Touchpad.
  Press "Ok".
  Open the "Status & Notifications" panel.
  Press Meta+Shift+T to activate the Touchpad widget.
  The "Status & Notifications" panel closes and then plasmashell crashes.

Normally, Meta+Shift+T would open the "Status & Notifications" panel in order
to show the Touchpad widget.

The same procedure works with the "Notifications" widget, the "Device Notifier"
widget and the "Printers" widget.

I am using the Ubuntu package version "4:5.5.5.2-0ubuntu1".  The --version
option reports "plasmashell 5.5.5".

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