[plasmashell] [Bug 366386] New: Plasma (black screen) crashed after kernel update 4.1.27-24-default

[Colin via KDE Bugzilla]

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

Bug ID: 366386
   Summary: Plasma (black screen) crashed after kernel update
4.1.27-24-default
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: hckilb...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.27-24-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Just trying to login. Leap 42.1 after a kernel update to 4.1.27-24-default from
4.1.26-21-default.

 In a terminal I changed the greeter to xdm (/etc/sysconfig/displayManager
file) and rebooted. I was able to log in but Plasma chashed and I was presented
with this Crash Report Assistant.

Previously, on boot, I was able to choose to the previous kernel with the boot
menu and that worked fine. I since updated the kernel again to 4.1.27.27-
default ... now I cannot, as both kernels offered in the menu fail ... 

Not to confuse matters but I am using Parallels 11 VM tool on an iMac.

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7fbe22357700 (LWP 2060)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe35f34422 in  () at /usr/lib64/libxcb.so.1
#2  0x7fbe35f3600f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fbe24ada3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fbe316db32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fbe1b3ea700 (LWP 2075)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe2d6bde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbe2d6bdf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbe3190dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe318b4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe316d661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe349eae18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbe316db32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fbe0f046700 (LWP 2076)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe2d6bde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbe2d6bdf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbe3190dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe318b4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe316d661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe349eae18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbe316db32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fbe0d7ee700 (LWP 2077)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe2d6bde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbe2d6bdf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbe3190dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fbe318b4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fbe316d661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fbe349eae18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fbe316db32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fbe07df7700 (LWP 2078)):
#0  0x7fbe307ee03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fbe371b986b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fbe371b9899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fbe307ea0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fbe30fe902d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fbd7700 (LWP 2079)):
#0  0x7fbe30fe0bfd in poll () at /lib64/libc.so.6
#1  0x7fbe2d6bde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fbe2d6bdf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fbe3190dd8b in

[plasmashell] [Bug 364601] crash kernel update 4.1.21.14 to 4.1.26.21 for Leap 42.1 OS

[Colin via KDE Bugzilla]

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

Colin  changed:

   What|Removed |Added

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

--- Comment #2 from Colin  ---
I reinstalled the Parallel Tools ... and all is now working.
I read about OpenSuse snapper tool, and decided that I "could" revert the
changes if it failed.

I am marking this resolved.

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

[plasmashell] [Bug 364601] crash kernel update 4.1.21.14 to 4.1.26.21 for Leap 42.1 OS

[Colin via KDE Bugzilla]

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

--- Comment #1 from Colin  ---
crash due to kernel update 4.1.21.14 to 4.1.26.21 for Leap 42.1 OS.

useless crash report


Try to install Debug symbols but no appropriate repo is registered.
root's password:
Loading repository data...
Reading installed packages...
No provider of 'debuginfo(build-id)=2b790ed948b1408daaf77963e12248bebc3f589b'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=40a2e107b6601f8f6071c27ae9427bcee5c4f70d'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=be6c056cc7fd2a317bad912e5814f8a33a9f2aab'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=d6cf2376bc65074d483559710b892c1e59aa0d21'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=e587fbd46026f9ab45ed3daa722652b5c782b80d'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=f35a52ebe75933c1fecf3e207e43aa51d32bb332'
found. ['--plus-content debug'?]
Resolving package dependencies... Nothing to do.

The packages containing debug information for the following application and
libraries are missing:
/usr/bin/plasmashell
/usr/lib64/libQt5XcbQpa.so.5
/usr/lib64/libQt5Gui.so.5
/usr/lib64/libQt5Widgets.so.5
/usr/lib64/libQt5Core.so.5
/usr/lib64/libQt5Quick.so.5


Useless bug report ...

Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4f7eacf780 (LWP 2102))]

Thread 7 (Thread 0x7f4f6933a700 (LWP 2105)):
#0  0x7f4f77fc2bbd in poll () from /lib64/libc.so.6
#1  0x7f4f7cf16422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f4f7cf1800f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f4f6babd3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f4f786bd32f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f4f777cc0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f4f77fcafed in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f4f62424700 (LWP 2116)):
#0  0x7f4f77fbec8d in read () from /lib64/libc.so.6
#1  0x7f4f746e0b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f4f7469f999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f4f7469fdf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f4f7469ff7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f4f788efd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f4f78896d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f4f786b861a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f4f7b9cce18 in ?? () from /usr/lib64/libQt5Qml.so.5
#9  0x7f4f786bd32f in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x7f4f777cc0a4 in start_thread () from /lib64/libpthread.so.0
#11 0x7f4f77fcafed in clone () from /lib64/libc.so.6
Try to install Debug symbols but no appropriate repo is registered.
root's password:
Loading repository data...
Reading installed packages...
No provider of 'debuginfo(build-id)=2b790ed948b1408daaf77963e12248bebc3f589b'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=40a2e107b6601f8f6071c27ae9427bcee5c4f70d'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=be6c056cc7fd2a317bad912e5814f8a33a9f2aab'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=d6cf2376bc65074d483559710b892c1e59aa0d21'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=e587fbd46026f9ab45ed3daa722652b5c782b80d'
found. ['--plus-content debug'?]
No provider of 'debuginfo(build-id)=f35a52ebe75933c1fecf3e207e43aa51d32bb332'
found. ['--plus-content debug'?]
Resolving package dependencies... Nothing to do.

The packages containing debug information for the following application and
libraries are missing:
/usr/bin/plasmashell
/usr/lib64/libQt5XcbQpa.so.5
/usr/lib64/libQt5Gui.so.5
/usr/lib64/libQt5Widgets.so.5
/usr/lib64/libQt5Core.so.5
/usr/lib64/libQt5Quick.so.5


Useless bug report ...

Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4f7eacf780 (LWP 2102))]

Thread 7 (Thread 0x7f4f6933a700 (LWP 2105)):
#0  0x7f4f77fc2bbd in poll () from /lib64/libc.so.6
#1  0x7f4f7cf16422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f4f7cf1800f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f4f6babd3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f4f786bd32f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f4f777cc0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f4f77fcafed in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f4f62424700 (LWP 2116)):
#0  0x7f4f77fbec8d in read () from /lib64/libc.so.6
#1  0x7f4f746e0b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f4f7469f999 in g_main_context_check () from

[plasmashell] [Bug 364601] New: crash kernel update 4.1.21.14 to 4.1.26.21 for Leap 42.1 OS

[Colin via KDE Bugzilla]

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

Bug ID: 364601
   Summary: crash kernel update 4.1.21.14 to 4.1.26.21 for Leap
42.1 OS
   Product: plasmashell
   Version: master
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: hckilb...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Yast update installed 8 things, including a kernel update.

I suspect the "Parallels VM Tools" have got out of sync.   
Base system is an iMac running El Capitan OS and Parallels 11 VM.
Originally I had to install the exact kernel source to get the VM tools to
install (compile).

Since the upgrade change the kernel version, i suspect the VM Tools are
conflicting.

On boot, I can successfully revert to the previous kernel.

I am not sure howto install the kernel update and reinstall the "Parallel
Tools" .

I am afraid if I try I may not have a working system to revert to.
As well, I am not sure howto use the Suse snapshot tool to save myself from
further exploring.

The system is functioning ... just in a rough shape.  
The is no application menu;  the crash report window had a link that open the
browser, or I would not be able to type this message. Cant resize or move the
browser window.

When returning to VM session, I had to open a terminal Ctrl-Alt-F3, to unlock
the session with the command "logincrl unlock-sessions"

Since I have little control over the system, I am not sure if I can install
debug repos to get the debug symbols. to make a decent trace. 


 can't paste crap debug trace yet. 
( perhaps try to later from reverted session )



Reproducible: Always

Steps to Reproduce:
1. install Leap 42.1 update on June 21, 2016 with includes kernel update
2. Reboot
3. Plasmashell is badly broke (Parallels 11 VM Tools out of sync? )

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

[k3b] [Bug 360170] New: Failed with error while ripping DVD (may be encrypted DVD)

[Colin via KDE Bugzilla]

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

Bug ID: 360170
   Summary: Failed with error while ripping DVD (may be encrypted
DVD)
   Product: k3b
   Version: 2.0.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video DVD
  Assignee: k...@kde.org
  Reporter: co...@colinwu.ca
CC: mich...@jabster.pl, tr...@kde.org

The DVD I'm trying to rip is a children's educational DVD called "Big
Vocabulary" published by Montessori House. The label says it is NTSC Region
Free. ISBN is 0-9762991-3-5.

The progress bar gets about 50% then fails with error.

Reproducible: Always




Debug output:

Devices
---
Optiarc DVD RW AD-7710H A833 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R,
DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R
Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted
Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R,
CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R,
Restricted Overwrite, Layer Jump] [%7]

System
---
K3b Version: 2.0.3
KDE Version: 4.14.17
QT Version:  4.8.7
Kernel:  4.4.3-300.fc23.x86_64

Used versions
---
transcode: 1.1.7

transcode
---
transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team
libdvdread: Encrypted DVD support unavailable.
=== last message repeated 2 times. ===
[[34;1mdvd_reader.c[0m] DVD title 2/2: 5 chapter(s), 1 angle(s), title set 2
[[34;1mdvd_reader.c[0m] title playback time: 00:27:48.07  1669 sec
libdvdread: Encrypted DVD support unavailable.
=== last message repeated 2 times. ===
[[34;1mdvd_reader.c[0m] DVD title 2/2: 5 chapter(s), 1 angle(s), title set 2
[[34;1mdvd_reader.c[0m] title playback time: 00:27:48.07  1669 sec
[transcode] V: auto-probing | /dev/sr0 (OK)
[transcode] V: import format| MPEG 2 program stream in DVD NTSC
(module=dvd)
[transcode] A: auto-probing | /dev/sr0 (OK)
[transcode] A: import format| LPCM in DVD NTSC (module=dvd)
[transcode] V: AV demux/sync| (2) initial MPEG sequence / enforce frame
rate
[transcode] V: import frame | 720x480  1.50:1  encoded @ 4:3
[transcode] V: clip frame (<-)  | 720x480
[transcode] V: zoom | 720x480  1.50:1 (Lanczos3)
[transcode] V: bits/pixel   | 0.145 (low)
[transcode] V: decoding fps,frc | 23.976,1
[transcode] V: multi-pass   | (mode=1) writing data (pass 1) to
/tmp/k3b_0.log
[transcode] V: video format | YUV420 (4:2:0) aka I420
[transcode] A: import format| 0x10001 LPCM [48000,16,2]
[transcode] A: export   | disabled
[transcode] V: encoding fps,frc | 23.976,1
[transcode] A: language | ��
[transcode] A: bytes per frame  | 8008 (8008.00)
[transcode] A: adjustment   | 0@1000
[transcode] V: IA32/AMD64 accel | sse42 sse41 ssse3 sse3 sse2 sse mmx cmove asm 
[transcode] V: video buffer | 10 @ 720x480 [0x2]
[transcode] A: audio buffer | 10 @ 48000x2x16
[import_dvd.so] v0.4.1 (2007-07-15) (video) DVD | (audio) MPEG/AC3/PCM
[export_null.so] v0.1.2 (2001-08-17) (video) null | (audio) null
[export_ffmpeg.so] v0.3.18 (2008-11-29) (video) Lavc56.60.100 | (audio)
MPEG/AC3/PCM
libdvdread: Encrypted DVD support unavailable.
[import_dvd.so] tccat -T 2,-1,1 -i "/dev/sr0" -t dvd -d 0 | tcdemux -a 0 -x pcm
-S 0 -M 2 -d 0 | tcextract -t vob -x pcm -a 0 -d 0
[import_dvd.so] tccat -T 2,-1,1 -i "/dev/sr0" -t dvd -d 0 | tcdemux -s 0xa0 -x
mpeg2 -S 0 -M 2 -f 23.976024 -P /tmp/file3vHZnG -d 0 | tcextract -t vob -a 0 -x
mpeg2 -d 0 | tcdecode -x mpeg2 -d 0 -y yuv420p
[import_dvd.so] delaying DVD access by 3 seconds
[import_dvd.so] waiting...
libdvdread: Encrypted DVD support unavailable.
[import_dvd.so] waiting...
=== last message repeated 2 times. ===
libdvdread: Encrypted DVD support unavailable.
[[34;1mdecode_mpeg2.c[0m] libmpeg2 acceleration: mmxext
[export_ffmpeg.so] Using FFMPEG codec 'mpeg4' (FourCC 'DIVX', MPEG4 compliant
video).
[export_ffmpeg.so] No profile selected
[export_ffmpeg.so] Error opening configuration file ./ffmpeg.cfg: No such file
or directory
[export_ffmpeg.so] Starting 1 thread(s)
[export_ffmpeg.so] Set display aspect ratio to input
[mpeg4 @ 0x55a0daf96a40] AVFrame.format is not set
[mpeg4 @ 0x55a0daf96a40] AVFrame.width or height is not set
[mpeg4 @ 0x55a0daf96a40] AVFrame.format is not set
[mpeg4 @ 0x55a0daf96a40] AVFrame.width or height is not set
<< the above two lines repeated many times >>
[decoder.c] cancelling the import threads
[transcode] encoded 40029 frames (10004 dropped, 0 cloned), clip length 1669.54
s
transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team
libdvdread: Encrypted DVD support unavailable.
=== last message repeated 2 times. ===
[[34;1mdvd_reader.c[0m] DVD title 2/2: 5 chapter(s), 1 

[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable

[Colin via KDE Bugzilla]

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

--- Comment #15 from Colin  ---
(In reply to Christian Stadelmann from comment #14)
> Can you please check whether this issue is present with different themes
> (e.g. oxygen) too?

It's present for all dark Desktop Themes, including Oxygen. However, I don't
know how to choose a different Look And Feel to test. The only options under
Look And Feel are Breeze/Breeze Dark. There's no button to install another Look
And Feel.

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

[Breeze] [Bug 343369] Menu in QtQuickControls Combo Box on Breeze Dark Theme Unreadable

[Colin via KDE Bugzilla]

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

--- Comment #16 from Colin  ---
Also, the steps to reproduce are different for me since I don't know how to set
the desktop to folder mode and don't care about doing that. I can instead
choose "Desktop Settings" to find the same issue though. Since icons can't be
put on the Desktop, I use the Folder View widget so I can follow the steps to
reproduce if I right-click on that widget instead of the Desktop as well.

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

[Spectacle] [Bug 357223] spectacle fails to capture active window displaying a drop-down menu but xfce4-screenshooter succeeds

[Colin via KDE Bugzilla]

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

--- Comment #5 from Colin  ---
I don't know why this would make a difference, but I am running the "Active
Window Control" widget on the Plasma panel. Just a hunch, maybe try running
that and see if you can reproduce this issue when trying to change Wallpaper.

Also, I'm running plasma 5.5.2 on Arch Linux and was previously running Xfce4
4.12.3 so have all that installed along with Plasma. I installed a fairly
minimal plasma 5.5.2 desktop.

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

[Spectacle] [Bug 357223] spectacle fails to capture active window displaying a drop-down menu but xfce4-screenshooter succeeds

[Colin via KDE Bugzilla]

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

--- Comment #4 from Colin  ---
I'm taking a shot of whatever it is that runs when you try to change wallpaper.
Right-click desktop->Desktop Settings (Alt+D,Alt+S)

I just tried moving the mouse pointer to one of the entries and it only showed
the popup window without the active window that made the popup. For some
strange reason, it also showed the entire Plasma panel, so the small popup
window wasn't easy to even notice.

Then, I switched from "under mouse" to "active window" and it failed the same
as always, except that it didn't even show the mouse pointer.

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

[Spectacle] [Bug 357223] spectacle fails to capture active window displaying a drop-down menu but xfce4-screenshooter succeeds

[Colin via KDE Bugzilla]

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

--- Comment #2 from Colin  ---
(In reply to Boudhayan Gupta from comment #1)
> You'll want to use Window Under Cursor for this, not Active Window.

I just tried that, and got the same failed result.

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

[Spectacle] [Bug 357223] spectacle fails to capture active window displaying a drop-down menu but xfce4-screenshooter succeeds

[Colin via KDE Bugzilla]

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

--- Comment #11 from Colin  ---
Why not just use the window geometry to define the area to be captured and then
capture everything in that area? Surely that's what's expected, not that it
will capture the active window without stuff in front of it.

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

[Spectacle] [Bug 357223] spectacle fails to capture active window displaying a drop-down menu but xfce4-screenshooter succeeds

[Colin via KDE Bugzilla]

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

--- Comment #12 from Colin  ---
I had hacked together some bash scripts to record parts of the screen with
ffmpeg and needed to get the (x,y) coordinates and also the w x h of the active
window. Here is that bash code from genffcom in my
https://github.com/colinkeenan/silentcast package:

```
aw=$(xdotool getactivewindow)
eval $(xwininfo -id "$aw" |
  sed -n -e "s/^ \+Absolute upper-left X: \+\([0-9]\+\).*/x=\1/p" \
 -e "s/^ \+Absolute upper-left Y: \+\([0-9]\+\).*/y=\1/p" \
 -e "s/^ \+Width: \+\([0-9]\+\).*/w=\1/p" \
 -e "s/^ \+Height: \+\([0-9]\+\).*/h=\1/p" )
if [ "$entire" = true ]
then
extents=$(xprop _NET_FRAME_EXTENTS -id "$aw" | grep "NET_FRAME_EXTENTS"
| cut -d '=' -f 2 | tr -d ' ')
bl=$(echo $extents | cut -d ',' -f 1) # width of left border
br=$(echo $extents | cut -d ',' -f 2) # width of right border
t=$(echo $extents | cut -d ',' -f 3)  # height of title bar
bb=$(echo $extents | cut -d ',' -f 4) # height of bottom border

let x=$x-$bl
let y=$y-$t
let w=$w+$bl+$br
let h=$h+$t+$bb
fi
```

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

[Spectacle] [Bug 357223] spectacle fails to capture active window displaying a drop-down menu but xfce4-screenshooter succeeds

[Colin via KDE Bugzilla]

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

--- Comment #8 from Colin  ---
I'm not sure that the Wallpaper plugin is the same as KCM. I just tried to
capture the drop down menu on System Settings :: Application Style :: Widget
Style, and it succeeded in capturing the popup menu without the entire plasma
panel. However, it did not capture the active window either.

I would consider it a bug anyway if the only way to ever capture the popup
drop-down menu was to capture the window under the mouse. It should show up on
full screen and active window captures as well. If there is a delay, then
anything on the screen when the delay is up should be captured.

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

[Spectacle] [Bug 357223] New: spectacle fails to capture active window displaying a drop-down menu but xfce4-screenshooter succeeds

[Colin via KDE Bugzilla]

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

Bug ID: 357223
   Summary: spectacle fails to capture active window displaying a
drop-down menu but xfce4-screenshooter succeeds
   Product: Spectacle
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: colinnkee...@gmail.com

Created attachment 96318
  --> https://bugs.kde.org/attachment.cgi?id=96318=edit
spectacle Fails where xfce-screenshooter Succeeds in capturing active window
with drop-down menu

Neither `spectacle` nor `xfce4-screenshooter` will launch while a drop-down
menu is displayed, but `xfce4-screenshooter` will capture a window displaying a
drop-down menu anyway if "Delay before capturing" is set to allow time to
activate the drop-down menu to be captured. Unfortunately, `spectacle` fails to
capture the drop-down menu even when a "Delay" is specified.

The attached screenshot shows `spectacle` failing where `xfce4-screenshooter`
succeeds. I first tried the capture with `spectacle`, then tried again with
`xfce4-screenshooter`, and finally used `xfce4-screenshooter` to capture the
whole screen including the window with the drop-down menu displayed.

Also, this bug reporting form would not allow me to enter a version. I am using
`spectacle 15.12.0`

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

[plasmashell] [Bug 357202] New: Using Dark Themes, menus in the Desktop Wallpaper Settings Plugin are unreadable because those menus have white background instead of using the dark background from the

[Colin via KDE Bugzilla]

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

Bug ID: 357202
   Summary: Using Dark Themes, menus in the Desktop Wallpaper
Settings Plugin are unreadable because those menus
have white background instead of using the dark
background from the them or selected dark color
scheme.
   Product: plasmashell
   Version: 5.5.2
  Platform: Archlinux Packages
   URL: http://i.imgur.com/9hEjjTj.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Image Wallpaper
  Assignee: notm...@gmail.com
  Reporter: colinnkee...@gmail.com
CC: plasma-b...@kde.org

Menus in the Desktop Wallpaper Settings Plugin obey the color scheme when
presenting text but don't obey the color scheme for the background of that
text. They use a white background while also using the white text as defined.
The result is white text on a white background which is completely unreadable.
It's only possible to see what the menu entries are as they are highlighted
during mouseover.

Reproducible: Always

Steps to Reproduce:
1. Choose a dark theme
2. Right-click on desktop and choose Desktop Settings
3. Click the Wallpaper Type drop-down menu

Actual Results:  
The drop-down menu displays an empty white rectangle with a single highlighted
entry showing the currently selected wallpaper type. The reason the rest of the
rectangle is empty is that the text is the same color as the background: white.

Expected Results:  
The drop-down menu should display a list showing what wallpaper types are
available. This list should be displayed as white text on a black background.

Appearance Settings In Use When The Linked Screenshot Was Taken

-Workspace Theme-
Look And Feel: Breeze Dark
Desktop Theme: SimpleGrey

-Color-
Scheme: vertex negro

-Application Style-
Widget style: Breeze

There is not a "Breeze Dark" widget style. This should not matter for the
drop-down menu because drop-down menus in other settings windows do not have
this problem.

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

[plasmashell] [Bug 357202] Using Dark Themes, menus in the Desktop Wallpaper Settings Plugin are unreadable because those menus have white background instead of using the dark background from the them

[Colin via KDE Bugzilla]

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

Colin  changed:

   What|Removed |Added

Summary|Using Dark Themes, menus in |Using Dark Themes, menus in
   |the Desktop Wallpaper   |the Desktop Wallpaper
   |Settings Plugin are |Settings Plugin are
   |unreadable because those|unreadable because those
   |menus have white background |menus have white background
   |instead of using the dark   |instead of using the dark
   |background from the them or |background from the theme
   |selected dark color scheme. |or dark color scheme

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

[systemsettings] [Bug 354179] File associations cannot be changed if already defined in $XDG_CONFIG_HOME/mimeapps.list

[Colin via KDE Bugzilla]

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

Colin  changed:

   What|Removed |Added

 CC||colinnkee...@gmail.com

--- Comment #6 from Colin  ---
Why is this still "UNCONFIRMED". It's clearly confirmed and a major issue for
the Plasma Desktop.

This table in the Arch Wiki will help the developers to solve this problem:

https://wiki.archlinux.org/index.php/Default_applications#MIME_types_and_desktop_entries

It shows the order of paths that are searched to find mimeapps.list. From this
table, it is obvious that the defaults set by Plasma Desktop should ideally be
stored in

$HOME/.config/$desktop-mimeapps.list

Or, at least in

$HOME/.config/mimeapps.list

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

[plasmashell] [Bug 357136] New: Can't configure Application Launcher Menu to work well in positions other than bottom left of screen

[Colin via KDE Bugzilla]

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

Bug ID: 357136
   Summary: Can't configure Application Launcher Menu to work well
in positions other than bottom left of screen
   Product: plasmashell
   Version: 5.5.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: colinnkee...@gmail.com
CC: plasma-b...@kde.org

Both widgets for launching applications (Application Launcher and Application
Menu) are configured to be most usable when positioned at bottom left of the
screen. There are no settings options to change the configuration so that it
would be just as easy to use from any other corner of the screen.

In particular, there is no way to put the favorites on the right, and for the
Application Launcher widget, there's no way to put the search on top.

if the launcher is on the right side of the screen, there's a lot of mouse
travel required to get from clicking the widget to clicking the application
icon. As the mouse travels, all sorts of stuff pops up if it's set to change on
mouseover hover, making that setting impractical. Worse than that, in the
Application Menu widget, the stuff that pops up blocks the favorites making it
impossible to even click on the launcher. This happens because the widget is
all the way to the right so has to put the pop-ups on the left side where the
favorites are.

Searching from the Application Launcher is very difficult if it's on top of the
screen both because it's a long travel from activating the window to clicking
in the search box, and because the search box isn't even there all the time.
Why does it alternate between a search box and showing the user@host?

Reproducible: Always

Steps to Reproduce:
1. Put an Application Launcher or Application Menu widget in any location other
than bottom left
2. Try to launch and application
3. Notice that the "Favorites" are located on the left.
4. Notice on Application Launcher that the search is located at the bottom.
5. Go into settings to try and put the search at top or the Favorites on the
right.
6. Fail to find any such options in the settings.

Actual Results:  
Can't get a satisfactory configuration of the launcher widgets for top-right of
screen.

Expected Results:  
I expected to have the ability to configure which side of the widget shows
favorites and whether the search bar is at top or bottom. Being able to reverse
those locations makes the menu properly usable in any corner of the screen.
Currently, both widgets are optimized for the left side of the screen, and the
Application Launcher widget for bottom left only.

I am new to KDE after using Xfce4 for a couple of years. I expected to find a
launcher that is just as configurable as Whiskermenu on Xfce. I'm actually
considering running a small Xfce panel just to be able to use the Whiskermenu
even though it's uglier just because it's so much more functional.

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