[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 --- Comment #13 from PGillespie--- okay, I think I might have Googled the source of all these problems: http://www.spinics.net/lists/intel-gfx/msg82135.html I reverted to Kernel 4.2.0-25-generic x86_64 (64 bit) and, so far, TTY is stable, there are no missing glyphs/letters after switching to TTY or suspend/resume, and no graphic resets/plasmashell crashes. Stay tuned. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361945] "More Settings" Panel Menu doesn't indicate selection...
https://bugs.kde.org/show_bug.cgi?id=361945 PGillespiechanged: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from PGillespie --- Thanks for asking. I wasn't using the default plasma theme. Marked this as invalid. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 --- Comment #12 from PGillespie--- //wtf is so hard to understand about "the graphics reset messages do not describe the process crash"?// And as to wtf's so hard about it? I'm not a developer/programmer or hacker. I'm a builder and writer who used to work as a tech support technician in the early 1990's when Windows vs. DOS was still open to debate. So yeah, it's hard to understand. I've spent several hours this morning contributing my time reporting bugs/problems I'm experiencing with KDE/Kubuntu 16.04, having very little knowledge beyond the GUI. Nonetheless, I'm trying to educate myself in the use of gdb and bug reporting so that I waste less of my time and yours. FYI: I enabled dri3 and used sna. Didn't help. And Intel microcode is installed. "it's not a bug at all - kwin noticed that your gpu too a nap and restarts the compositor." Or doesn't. How this isn't a bug is beyond me. So it's perfectly normal for KDE's compositor to crash? Okay. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?
https://bugs.kde.org/show_bug.cgi?id=362589 --- Comment #4 from PGillespie--- Okay. I attached GDB to plasmashell and the appropriate PID. I suspended and resumed twice while GDB was attached. The KDE panel locked up after the second suspend. Had to kill GDB and restart plasmashell in order use it. The backtrace follows: Thread 16 (Thread 0x7fa84861e700 (LWP 8524)): #0 0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa85bacfc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa85bad18d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa84a76c629 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fa85810084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8571ed6fa in start_thread (arg=0x7fa84861e700) at pthread_create.c:333 #6 0x7fa857a16b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fa845e10700 (LWP 8525)): #0 0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8547a031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8547a042c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa858337a7f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa8582dedea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8580fb8a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa85a9a33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa85810084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa8571ed6fa in start_thread (arg=0x7fa845e10700) at pthread_create.c:333 #9 0x7fa857a16b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fa83664c700 (LWP 8526)): #0 0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8547a031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8547a042c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa858337a7f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa8582dedea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8580fb8a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa85a9a33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa85810084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ---Type to continue, or q to quit--- #8 0x7fa8571ed6fa in start_thread (arg=0x7fa83664c700) at pthread_create.c:333 #9 0x7fa857a16b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fa82700 (LWP 8527)): #0 0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8547a031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8547a042c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa858337a7f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa8582dedea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8580fb8a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa85a9a33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fa85810084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa8571ed6fa in start_thread (arg=0x7fa82700) at pthread_create.c:333 #9 0x7fa857a16b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fa82edf6700 (LWP 8528)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa85cd48bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fa85cd48c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fa8571ed6fa in start_thread (arg=0x7fa82edf6700) at pthread_create.c:333 #4 0x7fa857a16b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7fa79ed45700 (LWP 8532)): #0 0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa8547a031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8547a042c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa858337a7f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa8582dedea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8580fb8a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa85b329ed6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7
[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?
https://bugs.kde.org/show_bug.cgi?id=362589 --- Comment #3 from PGillespie--- I'm sorry, scratch that last question (and you only have to confirm this with me once and we're on our way) . Would plasma-workspace be the component in question? gdb plasma-workspace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362588] TTY Non-Functional
https://bugs.kde.org/show_bug.cgi?id=362588 --- Comment #2 from PGillespie--- Thank you. I've been Googling this bug based on your description of the cause. All of the posts I've read associate it with NVIDIA, which I'm not using. Card: Intel Device 0a1e Display Server: X.Org 1.18.3 driver: intel Resolution: 1366x768@60.00hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 11.2.0 Not that this doesn't apply to INTEL. Where then, should I report this bug? - or are we stuck with it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?
https://bugs.kde.org/show_bug.cgi?id=362589 --- Comment #2 from PGillespie--- It's not something I've done before, but I'm just reading about it here: https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports In regards to the problem above, there's no KDE Crash Dialogue. Based on the site above, I would use GDB. Would that be? gdb plasmashell If I wanted to trace the error in window borders, panel failure, and compositing errors? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 --- Comment #10 from PGillespie--- Done. Two new bugs reported: Bug 362588 & Bug 362589 And that's that. If you or anyone wants to go deeper, I'm available. All I can do is to report. Thanks and good luck. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362589] New: After resume from Suspend / Compositing Failure?
https://bugs.kde.org/show_bug.cgi?id=362589 Bug ID: 362589 Summary: After resume from Suspend / Compositing Failure? Product: plasmashell Version: 5.5.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org Based on my discussions reporting Bug 361935, this would appear to be unrelated to: bug 356394 or Bug 357551 So, I'm filing a new bug as relates to the compositor. Reproducible: Sometimes Steps to Reproduce: 1. Suspend 2. Resume 3. After more than one suspend/resume cycle, the compositor fails "almost always". The compositor's failure is always accompanied by the symptoms described in Bug 357551 (though a bug tracker has never popped up). "After waking from suspend Plasma is always broken, most commonly the panel and window borders are gone... [and] sometimes I am left with a broken session with no panel, borders, or way to switch windows. Once in a while I get a blank screen and can't even switch to a tty." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362588] New: TTY Non-Functional
https://bugs.kde.org/show_bug.cgi?id=362588 Bug ID: 362588 Summary: TTY Non-Functional Product: plasmashell Version: 5.5.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org I can access TTY 1-6 but cannot interact with the sessions. The login text appears, but no prompt and no mouse cursor. Reproducible: Always Steps to Reproduce: 1. CTRL+ALT F1-6 Actual Results: Can't login/interact with prompt. After resume from suspend, accessing TTY 1-6 results in a blank screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 --- Comment #9 from PGillespie--- Here's what I can tell you: 1.) The missing text issues have seemingly gone away -- solved by updates? 2.) Bug 357551 describes the remaining symptoms: "sometimes I am left with a broken session with no pannel, borders, or way to switch windows. Once in a while I get a blank screen and can't even switch to a tty." 3.) If you want to parse out the "Desktop Effects were restarted due to a graphics reset," then take it up with my laptop. Of note: I have not received "Desktop Effects" error messages since reporting this bug yet the problem continues. The compositor simply crashes alongside the symptoms described in Bug 357551. And TTY doesn't work. Yet you insist these aren't related!?! Then it's a new bug. I'm reporting it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 --- Comment #7 from PGillespie--- I'm inclined disagree with you based on Bug 357551, which perfectly describes my symptoms and was itself marked as a duplicate of Bug 356394 by David Edmundson (take it up with *him* maybe?): "After waking from suspend Plasma is always broken, most commonly the pannel and window borders are gone. In the best case they restart, and the bug tracker pops up, but sometimes I am left with a broken session with no pannel, borders, or way to switch windows. Once in a while I get a blank screen and can't even switch to a tty. I also can't switch to TTY. I see the login prompt but can't interact with the session. Should I file a separate bug on this? Quatsch... my legs are getting stiff and I'm tired of trying to sort this out. If I don't hear anything definite concerning the bug with TTY, I guess I'll file a separate bug report including everything above. Not a threat, it's just what it is. It's a bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356394] Crash at some point while monitor power cycled
https://bugs.kde.org/show_bug.cgi?id=356394 PGillespiechanged: What|Removed |Added CC||vtp...@myfairpoint.net --- Comment #16 from PGillespie --- *** Bug 361935 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 PGillespiechanged: What|Removed |Added Status|RESOLVED|VERIFIED Resolution|INVALID |DUPLICATE --- Comment #5 from PGillespie --- Okay, after some research, it appears that this bug might be a duplicate of the following: https://bugs.kde.org/show_bug.cgi?id=357551 Which is itself a duplicate of: https://bugs.kde.org/show_bug.cgi?id=356394 I notice that this has been resolved upstream in QT 5.6. Any idea when Kubuntu Backports will be available to Xenial, or KDE NEON. *** This bug has been marked as a duplicate of bug 356394 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 --- Comment #4 from PGillespie--- Well, there's extreme instability after every suspend. Almost without exception the compositor restarts without warning (or error message) and sometimes not at all. Just this morning, waking up my laptop, I tried to demonstrate accessing TTY to my kids (because of the disappearing mouse bug) and arrived at a blank screen (no prompt), when I returned to plasma, compositing was off (due to a compositing error--as stated in settings) and I could discover no workaround to recover any functionality. Restarting plasmashell didn't work and ALT+Shift+F12 failed to toggle the compositor. Windows were opening without borders or not opening at all, and the panel was non-functional. Had to reboot. Unless I hear otherwise, I'm opening another bug report. If you think the current bug should be renamed, that's your call. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 --- Comment #2 from PGillespie--- //'s not a bug at all - kwin noticed that your gpu too a nap and restarts the compositor.// Except when my gpu doesn't take a nap... As I wrote above, it can occur "seemingly at random" and not always when recovering from suspend. Should I file another bug report? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Letters
https://bugs.kde.org/show_bug.cgi?id=361211 --- Comment #11 from PGillespie--- (In reply to Nikola Schnelle from comment #10) > Well I had "missing letters" problem after wake from suspend in firefox, but > since I use DRI3 - never faced the problem again. > > Install intel-microcode if you didn't already. Maybe it will help. > > Anyway this is not kwin/kde bug. Intel-Microcode?!? I think I'll pass on that. That's like telling me my electric motor needs an oil change. And as for whether its kwin/kde bug? Maybe you're right. Maybe you're not. As it is, both my systems say it happened after upgrading to Kbuntu 16.04. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Letters
https://bugs.kde.org/show_bug.cgi?id=361211 --- Comment #9 from PGillespie--- (In reply to Nikola Schnelle from comment #7) > That is intel driver bug. Switching to DRI3 fixes it for me. > > Look at this thread: > https://www.kubuntuforums.net/showthread.php?69984-FIX-for-flickering- > flashing-panel-on-Intel-gpu Okay. Results are in. I followed the advice on the thread. Sdding the 20-intel.conf file actually made the problem much worse. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Letters
https://bugs.kde.org/show_bug.cgi?id=361211 --- Comment #8 from PGillespie--- Thanks, I'll try it, but I don't have a flickering or flashing panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Letters
https://bugs.kde.org/show_bug.cgi?id=361211 --- Comment #6 from PGillespie--- Created attachment 98570 --> https://bugs.kde.org/attachment.cgi?id=98570=edit Missing letters in the Firefox Bookmark dropdown menu. 16.04 Final. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Letters
https://bugs.kde.org/show_bug.cgi?id=361211 --- Comment #5 from PGillespie--- As of 16.04's release, the bug hasn't been as drastic. That is, there appear to have been some improvement since BETA. The problem persists however, usually occurring after suspend. There are occasional hick-ups when Plasma locks up and compositing is restarted. Also, this is a problem on both my systems -- instability in plasmashell and compositing. Prior to 16.04, neither of my system experienced these instabilities. Kernel: 4.4.0-21-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5 Distro: Ubuntu 16.04 xenial Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11 Mobo: LENOVO model: VIUU4 v: 31900058WIN Bios: LENOVO v: AACN21WW date: 01/30/2015 CPU: Dual core Intel Core i3-4012Y (-HT-MCP-) cache: 3072 KB clock speeds: max: 1500 MHz 1: 1500 MHz 2: 1500 MHz 3: 1500 MHz 4: 1500 MHz Graphics: Card: Intel Device 0a1e Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 11.2.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361945] "More Settings" Panel Menu doesn't indicate selection...
https://bugs.kde.org/show_bug.cgi?id=361945 PGillespiechanged: What|Removed |Added Summary|Visibility Customizations |"More Settings" Panel Menu |no longer selectable... |doesn't indicate ||selection... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361945] New: Visibility Customizations no longer selectable...
https://bugs.kde.org/show_bug.cgi?id=361945 Bug ID: 361945 Summary: Visibility Customizations no longer selectable... Product: plasmashell Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: vtp...@myfairpoint.net After the last update to 16.04 (April 15th 2016), Mouse Over does not highlight any of the options under Panel Alignment or Visibility. In some cases, this makes confirmation that one has actually selected the item difficult to ascertain. This may or may not be related to: https://bugs.kde.org/show_bug.cgi?id=348043 Which also affects this system. Kernel: 4.4.0-18-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5 Distro: Ubuntu 16.04 xenial Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11 Reproducible: Always Steps to Reproduce: 1. Select More Settings under Panel Options. 2. Select any option under Panel Alignment or Visibility. Actual Results: Nothing. Expected Results: The selected option is highlighted with a mouse click (or some indication confirming the mouse click). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361935] New: Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 Bug ID: 361935 Summary: Desktop Effects were restarted due to a graphics reset... Product: plasmashell Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org This error is a regular occurrence after upgrading to 16.04. I've been using this system since 14.10 and have never before run into this bug. Kernel: 4.4.0-18-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5 Distro: Ubuntu 16.04 xenial Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11 Mobo: LENOVO model: VIUU4 v: 31900058WIN Bios: LENOVO v: AACN21WW date: 01/30/2015 CPU: Dual core Intel Core i3-4012Y (-HT-MCP-) cache: 3072 KB clock speeds: max: 1500 MHz 1: 1500 MHz 2: 1500 MHz 3: 1155 MHz 4: 1498 MHz Graphics: Card: Intel Device 0a1e Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 11.2.0 Reproducible: Sometimes Steps to Reproduce: 1.) It can seemingly occur at random---though possibly related to page-rendering in browsers. 2.) It also frequently occurs (though not always) when recovering from suspend mode. 3.) If the system has been unplugged during suspend, restarting can not only cause the above error but also lead to missing text as described in Bug: https://bugs.kde.org/show_bug.cgi?id=361211 But the two Bugs may not be directly related? That is, restarting Desktop Effects only leads to Missing Text 1 out of every 10 restarts. I've marked the Bug as Grave because of its unpredictability and because, at its worst (with missing text) the system is "basically unusable now" and needs to be rebooted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".
https://bugs.kde.org/show_bug.cgi?id=348043 PGillespiechanged: What|Removed |Added CC||vtp...@myfairpoint.net --- Comment #21 from PGillespie --- After the most recent update (as of April 15th 2016) : Kernel: 4.4.0-18-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5 Distro: Ubuntu 16.04 xenial I'm also experiencing this bug. This appears to be a direct result of the upgrade, as I never previously experienced his bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361393] 15.10 ---> 16.04 Release Upgrade Hangs (Mime Configuration)
https://bugs.kde.org/show_bug.cgi?id=361393 --- Comment #2 from PGillespie--- Thanks. And done: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1566847 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361393] New: 15.10 ---> 16.04 Release Upgrade Hangs (Mime Configuration)
https://bugs.kde.org/show_bug.cgi?id=361393 Bug ID: 361393 Summary: 15.10 ---> 16.04 Release Upgrade Hangs (Mime Configuration) Product: plasmashell Version: 5.5.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org Concerning: kubuntu-devel-release-upgrade Sorry I don't know what component this should go under. On two separate systems using this application, upgrading 15.10 to 16.04 locked up while configuring MIME types. If there's an error message, I don't know enough to know where to look. I realize this is a BETA upgrade -- but might affect official upgrade when released? Reproducible: Always Steps to Reproduce: 1. kubuntu-devel-release-upgrade Actual Results: Upgrade locks up configuring MIME Types. Expected Results: An upgraded system. In order to avoid a completely borked upgrade (If someone else stumbles on this): 1.) Logout. 2.) CTRL+ALT+F1 (TTY) 3.) (Login) 4.) sudo rm /var/lib/dpkg/lock 5.) sudo dpkg --configure -a 6.) sudo apt-get autoremove 7.) sudo apt dist-upgrade (normally nothing needs updating) 8.) sudo apt-get autoclean 9.) shutdown -r now -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361349] Random jpg's not Thumbnailed by Desktop Settings "Open Image" Window
https://bugs.kde.org/show_bug.cgi?id=361349 --- Comment #5 from PGillespie--- Created attachment 98228 --> https://bugs.kde.org/attachment.cgi?id=98228=edit With Gwenview -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361349] Random jpg's not Thumbnailed by Desktop Settings "Open Image" Window
https://bugs.kde.org/show_bug.cgi?id=361349 --- Comment #3 from PGillespie--- Yes. See Incoming Attachements... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 --- Comment #12 from PGillespie--- Okay. So I don't confuse matters. Working hard not to give you bad info: //KDE 4? => ~/.kde/share/config/kwinrulesrc// No, running 5. What I meant by empty is that I haven't made any window rules on that laptop yet (except by way of sussing out this bug). //Sounds like it's less a popup but more a normal window that is running into the focus stealing protecion?// That's above my pay grade: Can neither confirm nor deny. :) However! I think I've discovered the problem (or a workaround at least). XFCE4 Panel behaves as expected as long as I don't set it to "intelligently" hide. If "hide" is set to or , it functions as expected. If set to hide, I can't mouse click the panel (it will immediately disappear on clicking) unless the desktop is cleared. So... all this is probably a separate issue. Update on Second System: I was either wrong or the system (since updating to 15.10) no longer retains window rules (even when set via mouse right-clicking). The behavior on both systems is now the same. I can control the two instances of FF via ALTF3, separating them into their respective activities while the apps are running, but those preferences (as expected) are lost once the applications are closed. I cannot use "kcmshell5 kwinrules" to *permanently* assign them separate preferences. Plasma seems unable to recognize them as distinct instances of FF. If I set preferences for FF-A, then FF-B assumes those presets. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 --- Comment #10 from PGillespie--- Okay, writing from my other system: Kernel: 4.2.0-34-generic x86_64 (64 bit) Desktop: KDE 5 Distro: Ubuntu 15.10 wily If I try to edit special window settings for my two instances of FF, nothing sticks. If I edit application settings, the settings stick but are applied to both instances of FF. If I individually apply settings via right clicking the window border: Activities --> X or Y Then the assignments stick, even after closing and rebooting either instance of FF. The only difference (besides version of KDE -- and these issues still applied when I was running 15.10 on both) is that I am activating the successful system via right clicking the window border. Since I've deactivated window borders on my other system (smaller screen real-estate) I access the same options via ALTF3. Don't know if that makes a difference. Will test. The contents of .config/kwinrulesrc are empty on this system. Also, being 15.10, this system uses the older version of GThumbvand so isn't an issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 --- Comment #9 from PGillespie--- So, wrapper-1.0 was me trying to improve XFCE4 Panel's behavior in Plasma5. I use XFCE4-Panel because I really like the Weather & Dictionary App. However, getting the Dictionary App to "visibly" pop up is inconsistent. I usually have to clear the Desktop and *then* click the Dictionary App (on the XFCE4 Panel) before it will "visibly" pop up. It will also only pop up in the first/default activity. I tried experimenting by assigning Application rules to the Dictionary App but what resulted is what you saw. I don't know whether this should considered a "bug" so much as general incompatibility. If you think this deserves a separate Bug Report, I'll file one. Meanwhile, I used "kcmshell5 kwinrules", as suggested, and gthumb appears to be behaving. Interestingly, "kcmshell5 kwinrules" doesn't appear to differentiate between the two versions of Firefox. FYI: To invoke Repository Firefox: firefox %u -P default To invoke the manually "installed" version of Firefox; /home/vtpoet/.icefox/firefox/firefox -no-remote -P icefox So, the two FF's are working out of entirely separate directories. One is updated via the repository, one is manually updated. I use two FFs in two separate Activities because I run separate blogs and having separate instances of FF allows me to be logged into both at the same time and logged into separate Gmail accounts at the same time. I'm going to check my other install and see if I can figure out why it's working on that system and not the one I'm writing from. That system still uses 15.10 but is updated with Kubuntu backports. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361349] Random jpg's not Thumbnailed by Desktop Settings "Open Image" Window
https://bugs.kde.org/show_bug.cgi?id=361349 --- Comment #1 from PGillespie--- Created attachment 98218 --> https://bugs.kde.org/attachment.cgi?id=98218=edit Missing Thumbnails -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361349] New: Random jpg's not Thumbnailed by Desktop Settings "Open Image" Window
https://bugs.kde.org/show_bug.cgi?id=361349 Bug ID: 361349 Summary: Random jpg's not Thumbnailed by Desktop Settings "Open Image" Window Product: plasmashell Version: 5.5.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org See Attachment Reproducible: Always Steps to Reproduce: 1. Right Click Desktop Settings 2. Open (For new wallpaper) 3. Randomly Missing Thumbnails Thumbnails are not missing in either Dolphin or Thunar. Only when the folder is viewed through the Desktop Settings app. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 --- Comment #7 from PGillespie--- :~$ qdbus org.kde.ActivityManager /ActivityManager/Activities ListActivities 252a0153-22c9-4308-af0d-cd52f865cf83 30e27801-8b2d-498f-ab4a-1ca39cb629df -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 --- Comment #6 from PGillespie--- Created attachment 98217 --> https://bugs.kde.org/attachment.cgi?id=98217=edit kwinrulesrc Not 100% sure what you mean by "before restarting client". Assume you mean before restarting gthumb or either instance of FF. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Letters
https://bugs.kde.org/show_bug.cgi?id=361211 --- Comment #4 from PGillespie--- Created attachment 98210 --> https://bugs.kde.org/attachment.cgi?id=98210=edit Completely gone... -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 361324] New: Update kradio4 --> kradio5 and integrate with plasma5
https://bugs.kde.org/show_bug.cgi?id=361324 Bug ID: 361324 Summary: Update kradio4 --> kradio5 and integrate with plasma5 Product: plasma-pa Version: 5.5.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vtp...@myfairpoint.net Since radiotray stopped working on kubuntu 16.04 I've been using kradio4. It doesn't appear to be an official component of plasma5 but I'd like to see it added. It's a great piece of software. Lastly, the tray icon for kradio4 is ***ghastly*** -- sort of a "Walking Dead" Van Gogh ear (after it was cut off). Who wants to see somebody's disembodied ear on their desktop? I replaced all the icons (laboriously) so that it played well with Breeze. Would also like to see it more tightly integrated with the plasma-pa widget (on top of everything else you're doing). Reproducible: Always Kernel: 4.4.0-16-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.4 Distro: Ubuntu 16.04 xenial -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 --- Comment #4 from PGillespie--- Hi Thomas, in reference to gthumb, both activities are correctly listed under altf3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361062] New Multi-Media Tray Icon Doesn't Open KRadio4
https://bugs.kde.org/show_bug.cgi?id=361062 --- Comment #3 from PGillespie--- Yes. In the meantime, I've noticed that the "Open..." button also doesn't work for other apps. As an aesthetic matter, the Media Player applet displays three "blank/generic" music icons on the left (one larger with two superimposed at the bottom) when streaming radio on KRadio. Strikes me as rather pointless, ugly and inelegant (also makes less room for song information). Wouldn't it be more elegant to simply omit icons if none are available? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361274] Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 --- Comment #2 from PGillespie--- Yes, I can successfully assign a fixed geometry and keep it above others. It will also retain a virtual desktop assignment but... just noticed another bug. I have 2 activities and two virtual desktops in each. KWIN only gives me the option to assign gthumb to 1:1 or 2:2. In other words, no options for 1:2 or 2:1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361274] New: Special Application/Window Settings Inconsistent
https://bugs.kde.org/show_bug.cgi?id=361274 Bug ID: 361274 Summary: Special Application/Window Settings Inconsistent Product: plasmashell Version: 5.5.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org Applying Special Application/Window settings is inconsistent, sometimes working and sometimes not. The first example might be unusual: I have two laptops running Plasma 5. They both have two different versions of Firefox running (running from separate directories). Identical installations on both laptops. On one laptop I can successfully set the separate instances of Firefox to appear in separate activities (the preferences will be stored). On the other, I can't (the preferences aren't stored). I have to reset both instances of Firefox manually each time I invoke the browsers. And then a more common use-case: gthumb (which I prefer to Gwenview). I cannot permanently (through Special Application settings) assign gthumb to one Activity. Plasma resets my preferences to "All Activities" as soon as I close the dialog window. Reproducible: Always Steps to Reproduce: 1. alt+f3 Set gthumb to a specific activity. 2. Close window. 3. Reopen Actual Results: ghtumb re-assigned to *all* activities. Expected Results: assignment to preferred activity. Kernel: 4.4.0-16-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.4 Distro: Ubuntu 16.04 xenial -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Letters
https://bugs.kde.org/show_bug.cgi?id=361211 --- Comment #2 from PGillespie--- Rebooted. Phew. Now I can read everything again. System Info: Kernel: 4.4.0-16-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.4 Distro: Ubuntu 16.04 xenial Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11 Mobo: LENOVO model: VIUU4 v: 31900058WIN Bios: LENOVO v: AACN21WW date: 01/30/2015 CPU: Dual core Intel Core i3-4012Y (-HT-MCP-) cache: 3072 KB clock speeds: max: 1500 MHz 1: 948 MHz 2: 1500 MHz 3: 602 MHz 4: 605 MHz Graphics: Card: Intel Device 0a1e Display Server: X.Org 1.18.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 11.1.2 Audio: Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel Sound: ALSA v: k4.4.0-16-generic -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Letters
https://bugs.kde.org/show_bug.cgi?id=361211 PGillespiechanged: What|Removed |Added Summary|Missing Fonts |Missing Letters -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] Missing Fonts
https://bugs.kde.org/show_bug.cgi?id=361211 --- Comment #1 from PGillespie--- Created attachment 98166 --> https://bugs.kde.org/attachment.cgi?id=98166=edit Where are my letters? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361211] New: Missing Fonts
https://bugs.kde.org/show_bug.cgi?id=361211 Bug ID: 361211 Summary: Missing Fonts Product: plasmashell Version: 5.5.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org The attached png is self explanatory. Reproducible: Always Various solutions for this problem exist for Ubuntu, but I can't find anything for KDE. I would type more, but I can't see what I'm typing. :-/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361138] No Double-Click Option Available in Navigation
https://bugs.kde.org/show_bug.cgi?id=361138 PGillespiechanged: What|Removed |Added Severity|major |wishlist --- Comment #3 from PGillespie --- Well, I guess that makes the "bug" easy to solve. Far be it for me to question design decisions, but this strikes as a poor one. Thank you though, and I remain a fan of Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361140] After resume from Suspend / Compositing and/or PlasmaShell Failure?
https://bugs.kde.org/show_bug.cgi?id=361140 --- Comment #4 from PGillespie--- Speak of the devil. Just checked upgradable and both packages were updated. Stay tuned. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361140] After resume from Suspend / Compositing and/or PlasmaShell Failure?
https://bugs.kde.org/show_bug.cgi?id=361140 --- Comment #3 from PGillespie--- More information: Finally getting error messages: "Desktop effects were restrarted due to a graphics reset." Further error messages when resuming from suspend: There seems to be a problem with "klockscreen"? (Getting above my pay grade here.) When attempting to report the bug a dialog window prompted that the following packages were obsolete and the bug could not be reported. (Don't know if this is all related.) gcc-5-base, libstdc++6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361140] After resume from Suspend / Compositing and/or PlasmaShell Failure?
https://bugs.kde.org/show_bug.cgi?id=361140 --- Comment #2 from PGillespie--- For informational purposes: *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0b width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:43 memory:b000-b03f memory:a000-afff ioport:3000(size=64) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361140] After resume from Suspend / Compositing and/or PlasmaShell Failure?
https://bugs.kde.org/show_bug.cgi?id=361140 --- Comment #1 from PGillespie--- Created attachment 98142 --> https://bugs.kde.org/attachment.cgi?id=98142=edit Results after switching to GL 2.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361140] New: After resume from Suspend / Compositing and/or PlasmaShell Failure?
https://bugs.kde.org/show_bug.cgi?id=361140 Bug ID: 361140 Summary: After resume from Suspend / Compositing and/or PlasmaShell Failure? Product: plasmashell Version: 5.5.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org After resuming from Suspend PlasmaShell is nonresponsive. Reproducible: Sometimes Steps to Reproduce: 1. Suspend. 2. Resume Actual Results: 1. First sign of trouble: No Compositing Effects 2. Minimally Functional Panel: Can hover over Task Manger and see drop down windows, but clicking on windows doesn't "activate" application. 3. Application Launcher drops down but attempting to launch any application fails. System is unusable. Have attempted to restart plasmashell: killall plasmashell && kstart plasmashell But results in same issues -- and no compositor. Tried switching to OpenGL 2 with disastrous results. I'll attach an image. Currently using open GL 3.1 with GLX Interface and Full Screen Repaints (tearing). Didn't have these issues with 15.04 or 15.10. They all started after upgrading to 16.04, so maybe this is a BETA issue? And possibly relevant information: System:Kernel: 4.4.0-15-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.4 Distro: Ubuntu 16.04 xenial Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11 Mobo: LENOVO model: VIUU4 v: 31900058WIN Bios: LENOVO v: AACN21WW date: 01/30/2015 CPU: Dual core Intel Core i3-4012Y (-HT-MCP-) cache: 3072 KB clock speeds: max: 1500 MHz 1: 767 MHz 2: 818 MHz 3: 998 MHz 4: 999 MHz Graphics: Card: Intel Device 0a1e Display Server: X.Org 1.18.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 11.1.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361138] No Double-Click Option Available in Navigation
https://bugs.kde.org/show_bug.cgi?id=361138 --- Comment #1 from PGillespie--- Created attachment 98140 --> https://bugs.kde.org/attachment.cgi?id=98140=edit Where's the double-click option? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361138] New: No Double-Click Option Available in Navigation
https://bugs.kde.org/show_bug.cgi?id=361138 Bug ID: 361138 Summary: No Double-Click Option Available in Navigation Product: dolphin Version: 15.12.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: vtp...@myfairpoint.net Title Says it All Kernel: 4.4.0-15-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.4 Distro: Ubuntu 16.04 xenial Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 361062] New Multi-Media Tray Icon Doesn't Open KRadio4
https://bugs.kde.org/show_bug.cgi?id=361062 PGillespiechanged: What|Removed |Added Summary|kradio4 Tray Icon Doesn't |New Multi-Media Tray Icon |Open KRadio4|Doesn't Open KRadio4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361089] New: Logging Out Results in "Reboot"
https://bugs.kde.org/show_bug.cgi?id=361089 Bug ID: 361089 Summary: Logging Out Results in "Reboot" Product: plasmashell Version: 5.5.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org Kernel: 4.4.0-15-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.4 Distro: Ubuntu 16.04 xenial After upgradng to 16.04 (from 15.10), I've had to logout in order to "reboot" plasmashell once or twice. The problem is that logging out appears to reboot the system. Reproducible: Always Steps to Reproduce: 1. Logout Actual Results: Reboots system rather logging out. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 361062] kradio4 Tray Icon Doesn't Open KRadio4
https://bugs.kde.org/show_bug.cgi?id=361062 PGillespiechanged: What|Removed |Added Version|unspecified |5.5.4 Product|ksystraycmd |plasma-pa Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[ksystraycmd] [Bug 361062] kradio4 Tray Icon Doesn't Open KRadio4
https://bugs.kde.org/show_bug.cgi?id=361062 --- Comment #1 from PGillespie--- Update: After rebooting, the KRadio4 Icon showed up in the icon tray. However, the button on the separate Play/Pause Icon(?) still doesn't actually open KRadio4. This would appear to be a minor bug (if a bug at all?). -- You are receiving this mail because: You are watching all bug changes.
[ksystraycmd] [Bug 361062] New: kradio4 Tray Icon Doesn't Open KRadio4
https://bugs.kde.org/show_bug.cgi?id=361062 Bug ID: 361062 Summary: kradio4 Tray Icon Doesn't Open KRadio4 Product: ksystraycmd Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: vtp...@myfairpoint.net My update to 16.04, from 15.10, broke RadioTray. I uploaded and am trying KRadio4. Am noticing that when I close all windows and depend on the Kradio4 Panel Icon, clicking on "Open Kradio4" doesn't work. This means that if I want to change a station (I listen to Internet Radio), I have to killall, then restart KRadio4. I haven't found any other way, yet, to "re-invoke" the KRadio4 dialog window. Reproducible: Always Steps to Reproduce: 1. Start KRadio4 2. Pick a station. Close all Windows. 3. Try to "open" KRadio4 from the tray Icon. Actual Results: Nothing happens. Expected Results: Opens the KRadio4 dialog window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359868] Can't remove Application Dashboard from the panel
https://bugs.kde.org/show_bug.cgi?id=359868 --- Comment #3 from PGillespie--- I gave up trying to remove the widget. After several restarts during the normal course of usage and updates, the issue magically resolved itself. I could suddenly highlight and move the widget. I'm at a loss for an explanation. In the meantime, I'm loving Plasma5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359870] New: Sidebar pops up and disappears when activated by Desktop/Activities(?) Tab
https://bugs.kde.org/show_bug.cgi?id=359870 Bug ID: 359870 Summary: Sidebar pops up and disappears when activated by Desktop/Activities(?) Tab Product: plasmashell Version: 5.5.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org This concerns the little tab on the right screen edge with the Hamburger for activating the Widget, Activities. Lock Screen, Show Desktop Menu. If I choose to activate the Widget or Activities Sidebar, the sidebar blips (technical term) into view for a fraction of a second before disappearing. Reproducible: Always Steps to Reproduce: 1. Click on Plasma/Desktop(?) tab for menu options. 2. Choose 'Activities' or 'Add Widgets...' Menu Option. Actual Results: Sidebar does not remain accessible. Expected Results: Sidebar remains accessible. Am currently set up with two Activities. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359868] New: Application Dashboard
https://bugs.kde.org/show_bug.cgi?id=359868 Bug ID: 359868 Summary: Application Dashboard Product: plasmashell Version: 5.5.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org Installed 'Application-Dashboard Widget' next to System Tray (between system tray and clock in standard default arrangement) as a trial run. I later wanted to move/remove it and make it the default launcher, but KDE doesn't seem to recognize the widget. I'm only able to select the system tray (which "grey's over" the Application-Dashboard Widget" or the clock. Unfortunately KDE doesn't allow me to take a screen shot while customizing the panel. Reproducible: Always Steps to Reproduce: 1. Install Application-Dashboard Widget next to System Tray (or anywhere?) 2. Attempt to move or remove. Actual Results: Unable to select widget. Expected Results: Ability to select widget. Latest KDE installed from backports onto Kubuntu Wily. Love KDE. Looking forward to NEON. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358437] Digital Clock Settings Window is Blank/Transparent
https://bugs.kde.org/show_bug.cgi?id=358437 --- Comment #1 from PGillespie--- So, I've noticed that this bug affects all widget configuration windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358437] Digital Clock Settings Window is Blank/Transparent
https://bugs.kde.org/show_bug.cgi?id=358437 --- Comment #3 from PGillespie--- Sorry, can't do. Apparently I've also lost "Print Screen" functionality after upgrading to 15.10. The PrtSc button no longer works. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358438] File Content Window is Blank
https://bugs.kde.org/show_bug.cgi?id=358438 PGillespiechanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from PGillespie --- Okay, after more updates, upgrades, dist-upgrades, and dpkg --configure -a this bug has, so far, resolved itself. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358438] New: File Content Window is Blank
https://bugs.kde.org/show_bug.cgi?id=358438 Bug ID: 358438 Summary: File Content Window is Blank Product: dolphin Version: 15.08.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: vtp...@myfairpoint.net After upgrading from 15.04 to 15.10, Dolphin returns the following error: Could not start process Unable to create io-slave: klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'. Reproducible: Always Steps to Reproduce: 1. Open Dolphin Actual Results: Blank "FIle Content" Window Expected Results: List of Directories and Files -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358435] New: Krunner no longer launches applications...
https://bugs.kde.org/show_bug.cgi?id=358435 Bug ID: 358435 Summary: Krunner no longer launches applications... Product: krunner Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: filesearch Assignee: m...@vhanda.in Reporter: vtp...@myfairpoint.net Waited as long as I could. Just successfully, more or less, upgraded 15.04 to 15.10. Among other issues, I now notice that krunner has lost its mojo. If I type in an application, it no longer autofills or offers options and even when the complete application name is typed, like Thunderbird or Libreoffice, krunner is a dud. Reproducible: Always Steps to Reproduce: 1. Invoke Krunner 2. Type Application Name --> Return 3. Nothing. Expected Results: Launch application. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358435] Krunner no longer launches applications...
https://bugs.kde.org/show_bug.cgi?id=358435 --- Comment #1 from PGillespie--- Just noticed that when starting Dolphin, I get the following error: Could not start process Unable to create io-slave: klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'. Not sure if this is related, but "klauncher" made me think it might be... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358437] Digital Clock Settings Window is Blank/Transparent
https://bugs.kde.org/show_bug.cgi?id=358437 PGillespiechanged: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358437] New: Digital Clock Settings Window is Blank/Transparent
https://bugs.kde.org/show_bug.cgi?id=358437 Bug ID: 358437 Summary: Digital Clock Settings Window is Blank/Transparent Product: plasmashell Version: 5.3.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: mklape...@kde.org Reporter: vtp...@myfairpoint.net CC: plasma-b...@kde.org After upgrading from 15.04 to 15.10 Kubuntu, calling up the Digital Clock Settings Window results in a blank window, as in see-through to the desktop blank. Reproducible: Always Steps to Reproduce: 1. Right Click Digital Clock Widget 2. Select "Digital Clock Settings" Actual Results: Blank/Empty Window Expected Results: Settings Window -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358437] Digital Clock Settings Window is Blank/Transparent
https://bugs.kde.org/show_bug.cgi?id=358437 --- Comment #4 from PGillespie--- Okay, good news and a little bad news: After: dpkg --configure -a apt-get update autoremove dist-upgrade And rebooting, this bug has gone away. But still no Print Screen functionality. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358437] Digital Clock Settings Window is Blank/Transparent
https://bugs.kde.org/show_bug.cgi?id=358437 --- Comment #6 from PGillespie--- Okay, ksnapshot was apparently uninstalled during the upgrade (along with other software apparently, like LIbreoffice). Had to reinstall. Looks like I'll be running into more of this as I break in 15.10. Don't know whether that counts as a bug or not? Will be practice for the big upgrade to 16.04. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 341184] 'Left Mouse Click' doesn't work / function with Plasma Widgets
https://bugs.kde.org/show_bug.cgi?id=341184 --- Comment #12 from PGillespie--- This has been posted for a while. Not trying to be provocative or in-your-face, but am I correct in thinking this is pretty much a "Won't Fix" bug? KDE 4 is yesterday's news and ARM is a niche of a niche. My little ARMHF CPU was so ill-suited to Linux that I altogether quit using it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356910] No Ability to Edit Activities without Installing "Activities" widget
https://bugs.kde.org/show_bug.cgi?id=356910 --- Comment #5 from PGillespie--- (In reply to Ivan Čukić from comment #4) > > If KDE devs want Super+Tab to behave like Alt+Tab, then Activities should > > be editable within Preferences. > > In the latest release, it is also possible to edit activities in the system > settings :) That's good news. I like this feature in Plasma 5. As soon as support ends on 15.04, I'll be installing 16.04. Beta but that's alright by me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356910] No Ability to Edit Activities without Installing "Activities" widget
https://bugs.kde.org/show_bug.cgi?id=356910 --- Comment #2 from PGillespie--- (In reply to Kai Uwe Broulik from comment #1) > Previously there was no indication whatsoever when switching activities with > Meta+Tab, it is intended that it only serves as an Alt+Tab like switcher. To > get the full blown UI you can use Meta+Q Okay, thanks. Then I guess discoverability is the issue. I couldn't remember where to locate this key combination---got it into my head that Meta+Tab was the same as Meta+Q. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356910] New: No Ability to Edit Activities without Installing "Activities" widget
https://bugs.kde.org/show_bug.cgi?id=356910 Bug ID: 356910 Summary: No Ability to Edit Activities without Installing "Activities" widget Product: frameworks-kactivities Version: 5.1.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: vtp...@myfairpoint.net CC: plasma-b...@kde.org In earlier versions of Plasma (I assume) if one depressed Super+Tab, the sidebar would remain active, allowing one to edit or add activities. Currently, Super+Tab acts like Alt+Tab, which means as soon as the keys are lifted, the sidebar/editing window disappears. The only workaround to this bug (that I know of) is to temporarily install the "Activities" widget. Clicking on the Activities widget allows the sidebar to remain active (and the user can edit or add Activities). Afterwards, the user must remove the widget (if, as in my case, it isn't wanted). Reproducible: Always Steps to Reproduce: 1. Super+Tab 2. Attempt to edit or Add activities is impossible. . If KDE devs want Super+Tab to behave like Alt+Tab, then Activities should be editable within Preferences. -- You are receiving this mail because: You are watching all bug changes.