[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 337355] plasma 5 panel gets too transparent in desktop cube
https://bugs.kde.org/show_bug.cgi?id=337355 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 351827] No way to see elided application names in Application Dashboard in full
https://bugs.kde.org/show_bug.cgi?id=351827 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225
Bob Wya changed:
What|Removed |Added
CC||bob.mt@gmail.com
--- Comment #21 from Bob Wya ---
I purposely don't unplug my external whilst using Plasma 5 - because of this
annoying bug!!
Playing fullscreen games (which alter xrandr settings) also will makes your
Plasma 5 panel(s) disappear... Logging out and logging back in brings it back -
but that is not exactly super-convenient!!
grep -B 6 -A 2 panel "${HOME}/.config/plasma-org.kde.plasma.desktop-appletsrc"
[Containments][1]
activityId=
formfactor=3
immutability=1
lastScreen=1
location=5
plugin=org.kde.panel
wallpaperplugin=org.kde.image
xrandr -q
Screen 0: minimum 8 x 8, current 4480 x 1630, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 1920x1080+2560+550 (normal left inverted right x axis y
axis) 382mm x 215mm
1920x1080 60.02*+
HDMI-0 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm
x 336mm
2560x1440 59.95*+
1920x1200 59.9559.88
1920x1080 60.0059.9450.0029.9760.0560.0050.04
1680x1050 59.95
1600x1200 60.00
1600x900 60.00
1280x1024 75.0260.02
1280x720 60.0059.9450.00
1152x864 75.00
1024x768 75.0360.00
800x600 75.0060.32
720x576 50.00
720x480 59.94
640x480 75.0059.9459.93
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 358108] Persistent favorite apps in Application Dashboard (and possibly in Kicker and Kickoff)
https://bugs.kde.org/show_bug.cgi?id=358108 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #1 from Bob Wya --- Yup. This is not really ideal. Say you have 2 panels (1 / monitor) each with a kickoffdash. Then you might (!!) want to have the favourites linked / synced between. However think again - bzzzt - no!! So basically I've got to manually hack about in the configuration files to fix this issue. 1) Alter: /usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/config/main.xml to "fix" / change the default global favourites. and / or 2) Add further cruft to my BASH script to fix (which runs pre-startup): ~/.config/plasma-org.kde.plasma.desktop-appletsrc which already "fixes" another Plasma 5 bug where panels randomly move when you change screen configuration... Add a hack to sync my favourites between the panels (each with a separate kickoffdash). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #26 from Bob Wya ---
Created attachment 97673
--> https://bugs.kde.org/attachment.cgi?id=97673&action=edit
Plasma 5 panel location reset BASH script (hack!!)
For anyone where restarting the Plasma Shell is not enough to fix your panel
locations...
For my own use I had to write a little script to move my panels back to the
screens I want them on - when running games in dual monitor setup. The script
is simply a hack to go through the main configuration file and re-write you
panel settings back to some sane defaults (of your choosing).
The script details the codes for the panel locations (left, top, right, bottom)
- but you'll probably want to copy your existing panel settings, from your own
configuration file, into the script. You can read your existing Plasma 5 panel
settings with:
grep -B 6 -A 1 'org.kde.panel'
"${HOME}/.config/plasma-org.kde.plasma.desktop-appletsrc"
I've got this script set on a global shortcut and it's a life saver - till this
bug gets fixed!!
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #35 from Bob Wya ---
(In reply to Bernd Steinhauser from comment #34)
> This got actually worse with 5.5.95. Not sure about the desktop, because I
> gave up on using wallpapers, because plasmashell will do whatever it wants
> with them anyway.
> However, it is really impressive with what accuracy and determination,
> plasmashell moves two panels that were on different screens onto the same
> screen after reboot.
>
> I mean I can understand if screen numbering gets messed up and things that
> should be on screen X end up on screen Y and the other way round. But just
> putting everything on screen X and nothing on screen Y? Why?
> It really feels like there is no concept of remembering where things were
> when shutting down.
>
> Also interesting is that it constantly complains about
> "requesting unexisting screen 3"
> when nothing in .config/plasma-org.kde.plasma.desktop-appletsrc has an entry
> that could be related to a "screen 3". Everything in there says -1, 0, 1 or
> 2.
> The other plasma config files don't mention screen 3 either, afaics.
> Not sure what's going on, or is it just that some parts of plasma count from
> 0 and some count from 1?
> Well then I could understand if it gets confused by itself. ;)
Have a look at my (cough) workaround script...
https://bugs.kde.org/attachment.cgi?id=97673
I've actually got a copy of the script globally bound to CTRL+ATL+BACKSPACE !!
The settings in my script are specific to my system (a bottom panel on each, of
2 screens).
So you'll need to edit the script first and put in your personal panel
settings. :-)
To obtain the settings for your current panel setup - execute:
egrep -B 6 -A 1 '^plugin=org.kde.panel'
"${HOME}/.config/plasma-org.kde.plasma.desktop-appletsrc"
I've added a comment table to deceiver the codes that determine where a panel
is positioned (LEFT, RIGHT, TOP, BOTTOM).
Screen numbering is from 0 ... (as you speculated).
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #46 from Bob Wya --- (In reply to Bernd Steinhauser from comment #44) > This is getting repetitive. The bug is not fixed by Qt 5.6, it's not fixed > by KF5 5.20 and neither Plasma 5.5.95. > > If you don't see, you're lucky (congrats), but the bug is still there, as > pointed out above. No, but it's weird that I can't reproduce it any more... I've not applied any special patches (just the 2 extra qtdbus patches that Arch picked up and Gentoo hasn't)... Oh well :-) I did add "/etc/X11/xorg.conf.d/70-screen.conf" recently: # xrandr -s 0 : both internal laptop display & external monitor on # xrandr -s 1 : internal laptop display off & external monitor on # xrandr -s 2 : internal laptop display on & external monitor off Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 Option "Stereo" "0" Option "nvidiaXineramaInfoOrder" "DFP-2" Option "metamodes" "DP-2: nvidia-auto-select +2560+506, HDMI-0: nvidia-auto-select +0+0" Option "metamodes" "DP-2: 1920x1080 +2560+506, HDMI-0: 2560x1440 +0+0; DFP-2: NULL, HDMI-0: 2560x1440 +0+0" Option "metamodes" "DP-2: 1920x1080 +2560+506, HDMI-0: 2560x1440 +0+0; DFP-2: 1920x1080 +0+0, HDMI-0: NULL" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection EndSection So I'll try booting without that (I just added it to get my monitors lined up correctly in SDDM)... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #91 from Bob Wya --- (In reply to Martin Gräßlin from comment #90) > and a patch: https://phabricator.kde.org/D2483 Thanks for all your hardwork on this one! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #92 from Bob Wya --- (In reply to Martin Gräßlin from comment #90) > and a patch: https://phabricator.kde.org/D2483 I've tested this patch on kde-win 5.7.3. Dual monitor setup - so I can see compositing switch off and on (to confirm this aspect of the bug). KWin rule to force enable compositing deleted. Breeze decorations re-enabled. Ran my current test - dhewm with Doom 3 HD texture pack mod. No decoration shadow breakage and none of the secondary weird side-effects (like one display flickering constantly - when new application windows are created), etc. So looking good at my end!! :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #94 from Bob Wya --- (In reply to wolfyrion from comment #93) > > hi Bob Wya , > One question please: > When you run an opengl game/app does it turn off the compositor or not?? > (Before it said that this happening because the drivers request to do so > and we had to force to enable compositor using the rules) > if compositor is getting disable you will notice a lot of tearing in most of > the games thats why we want the compositor to be enable. > > Broken Texures/Shadows and Turning off compositor when launching an opengl > game or app. > So with this patch both of these problems are solved? The original problem that I reported: Launching a 3D Opengl game. Sometime during the switch from compositor on, to compositor off and back again (automatically handled by Kwin/Plasma) the Breeze decoration shadows break. By that definition the bug is fixed on my system... I'm not exactly sure what you are asking... The problem, _I_ reported, has been fixed, by Martin, as I clearly stated... You still got issues?? Then open another (SEPARATE) bug - no bug hi-jacking :-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364524] kcmshell5 kcm_sddm dumps core everytime it is executed
https://bugs.kde.org/show_bug.cgi?id=364524 --- Comment #3 from Bob Wya --- (In reply to andreas.sturmlechner from comment #2) > Is it safe to assume you have built Qt with USE=debug? You presume correctly. You may also presume, that building with Qt 5.7.0 with USE=-debug, fixes the issue! I am able launch kcm_sddm without any issues in this instance. I might have forgotten to report this fact - I stumbled upon a month or two ago (cough). :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] after suspend/resume, some widgets show graphic failure
https://bugs.kde.org/show_bug.cgi?id=364766 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 362864] Kate does not save Sidebar state in configuration settings files
https://bugs.kde.org/show_bug.cgi?id=362864 --- Comment #2 from Bob Wya --- (In reply to Buovjaga from comment #1) > I don't have this problem. > > Arch Linux 64-bit > Kate 16.04.2 > KDE Frameworks 5.23.0 > Qt 5.7 > xcb wm Ditto on the base packages and Kate version. So maybe it's a Plasma 5 specific issue? Some more testing ... 1. Ensure you have *NO* saved Kate sessions 2. Start Kate session (either from shell or application menu/krunner) 3. Disable plugin "File system browser" 4. In Kate settings menu : enable save Window state in Session / Load last used Session 5. Sessions -> Save session (i.e. save to a blank/default session) 6. Close Kate 7. Restart Kate (as per 2.) In my mind (!!) a blank session name should still be saved to a "default" location. But even when I used a named session and the above steps - none of my plugins are staying enabled. Even when I manually reload the session... The other Kate settings are being restored successfully. Very weird??!! I've tried cleaning out the "cruft" - removing my kate* config files from ~/.config. There are no KDE 4 config kate* config files in my ~/.kde4 profile directories. So it I guess it might be a cache issue - with Plasma 5. I'll try cleaning this out next!! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 362864] Kate does not save Sidebar state in configuration settings files
https://bugs.kde.org/show_bug.cgi?id=362864 Bob Wya changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Bob Wya --- *** This bug has been marked as a duplicate of bug 319396 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 319396] Kate should ask for a session name upon clicking "Save session" in an unnamed session
https://bugs.kde.org/show_bug.cgi?id=319396 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #3 from Bob Wya --- *** Bug 362864 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #139 from Bob Wya --- (In reply to Jakub from comment #138) > I want to add that, when I connect a second, bigger screen, my mouse cursor > get scaled (is bigger) in some apps. Looks ridiculous. Hmm, no you don't actually. Because that's not at all relevant to this bug report... -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 365716] Digital clock display is missing digits
https://bugs.kde.org/show_bug.cgi?id=365716 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #2 from Bob Wya --- I can reproduce this issue... I'll do some more testing... I've tried increasing the width in: org.kde.plasma.digitalclock/ ... /DigitalClock.qml 96: Layout.minimumWidth: Math.max(labelsFlow.width+2, dateLabel.paintedWidth) just to see what effect this has... :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1
https://bugs.kde.org/show_bug.cgi?id=365570 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #10 from Bob Wya --- Created attachment 100134 --> https://bugs.kde.org/attachment.cgi?id=100134&action=edit Refactored: John Salatas's plasma-workspace-5.7.0-systray_iconsize.patch I don't see how watering down John Salatas's original patch into a secret/ hidden setting - so basically it fixes nothing - achieves anything?? Last time I checked Plasma isn't going after the i3 DE market!! I remember requesting this feature back in 2014 (!!) on the VDG forums - I was not alone... https://forum.kde.org/viewtopic.php?f=285&t=121695 If user requests for features are to be ignored... What was the point of the VDG?? I've finally got the feature I wanted - thanks to John Salatas... But not really - because I've got to refactor this patch - every plasma-workspace release now... :-( Just to add Vertical side panels are still broken - by default - with no "user visible" switch to fix them. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 365910] New: Adjust Date and Time applet crash following suspend-resume cycle
https://bugs.kde.org/show_bug.cgi?id=365910 Bug ID: 365910 Summary: Adjust Date and Time applet crash following suspend-resume cycle Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bob.mt@gmail.com Application: kcmshell5 (5.7.2) (Compiled from sources) Qt Version: 5.7.0 Frameworks Version: 5.24.0 Operating System: Linux 4.6.4-zen x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: Updated Gentoo to Plasma 5.7.2 Unable to access Date and Time settings from Digital Clock in panel (on either dual-display)... Unable to restart the Date and Time settings applet (crash dialog simply reappears). Digital Clock also missing digits from clock face (not date) on one display (internal laptop display). Possibly unrelated?? Nvidia proprietary drivers 367.35 on a Geforce GTX 970M. Backtrace attached. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efef74817c0 (LWP 21943))] Thread 5 (Thread 0x7efed214c700 (LWP 21947)): #0 0x7efef6f8d37d in poll () from /lib64/libc.so.6 #1 0x7efef060f00c in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7efef060f392 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x7efed2c36a26 in gdbus_shared_thread_func () from /usr/lib64/libgio-2.0.so.0 #4 0x7efef0635825 in g_thread_proxy () from /usr/lib64/libglib-2.0.so.0 #5 0x7efef262d424 in start_thread () from /lib64/libpthread.so.0 #6 0x7efef6f963fd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7efed294d700 (LWP 21946)): #0 0x7efef0653759 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7efef060eff2 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7efef060f11c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7efef060f159 in glib_worker_main () from /usr/lib64/libglib-2.0.so.0 #4 0x7efef0635825 in g_thread_proxy () from /usr/lib64/libglib-2.0.so.0 #5 0x7efef262d424 in start_thread () from /lib64/libpthread.so.0 #6 0x7efef6f963fd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7efeddca1700 (LWP 21945)): #0 0x7efef6f8d37d in poll () from /lib64/libc.so.6 #1 0x7efef060f00c in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7efef060f11c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7efef4ef8ebb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7efef4ea01ba in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7efef4cdd88b in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7efef7588c08 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #7 0x7efef4ce32ad in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7efef262d424 in start_thread () from /lib64/libpthread.so.0 #9 0x7efef6f963fd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7efee6885700 (LWP 21944)): #0 0x7efef6f8d37d in poll () from /lib64/libc.so.6 #1 0x7efef2c658f2 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7efef2c67707 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7efee941dbf9 in QXcbEventReader::run() () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7efef4ce32ad in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7efef262d424 in start_thread () from /lib64/libpthread.so.0 #6 0x7efef6f963fd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7efef74817c0 (LWP 21943)): [KCrash Handler] #6 0x7efef6ee02f8 in raise () from /lib64/libc.so.6 #7 0x7efef6ee174a in abort () from /lib64/libc.so.6 #8 0x7efef4ccb9e9 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #9 0x7efef7587f88 in QDBusArgumentPrivate::checkRead(QDBusArgumentPrivate*) [clone .part.27] () from /usr/lib64/libQt5DBus.so.5 #10 0x7efef75d6428 in QDBusArgumentPrivate::checkReadAndDetach(QDBusArgumentPrivate*&) () from /usr/lib64/libQt5DBus.so.5 #11 0x7efef75d93e9 in QDBusArgument::beginMapEntry() const () from /usr/lib64/libQt5DBus.so.5 #12 0x7efed33576b2 in PolkitQt1::Authority::Private::init() () from /usr/lib64/libpolkit-qt5-core-1.so.1 #13 0x7efed3358051 in PolkitQt1::Authority::Authority(_PolkitAuthority*, QObject*) () from /usr/lib64/libpolkit-qt5-core-1.so.1 #14 0x7efed3358312 in PolkitQt1::Authority::instance(_PolkitAuthority*) () from /usr/lib64/libpolkit-qt5-core-1.so.1 #15 0x7efed35d05fa in KAuth::Polkit1Backend::Polkit1Backend() () from /usr/lib64/qt5/plu
[kdeplasma-addons] [Bug 365716] Digital clock display is missing digits
https://bugs.kde.org/show_bug.cgi?id=365716 --- Comment #3 from Bob Wya --- Created attachment 100218 --> https://bugs.kde.org/attachment.cgi?id=100218&action=edit KDE Plasma 5.7.2 panel - digital clock - missing digits -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364524] kcmshell5 kcm_sddm dumps core everytime it is executed
https://bugs.kde.org/show_bug.cgi?id=364524 --- Comment #1 from Bob Wya --- Still present in 5.7.2 ... Sigh... kcmshell5 kcm_sddm QDBusArgument: read from a write-only object Aborted (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1
https://bugs.kde.org/show_bug.cgi?id=365570 Bob Wya changed: What|Removed |Added Attachment #100134|0 |1 is obsolete|| --- Comment #12 from Bob Wya --- Created attachment 100220 --> https://bugs.kde.org/attachment.cgi?id=100220&action=edit Refactored for Plasma 5.7.2: John Salatas's plasma-workspace-5.7.0-systray_iconsize.patch Sigh :-( -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 --- Comment #16 from Bob Wya --- (In reply to lmk from comment #13) > Hello! 5.7 is hard masked on gentoo. So you can confirm that it is qt 5.6 > problem? It runs OK... It's only masked for minor build issues (i.e. Quality Control): https://bugs.gentoo.org/show_bug.cgi?id=589412 # Michael Palimaka (12 Aug 2016) # Requires revdeps to build with at least C++11. Bug 589412. # Masked for wider testing. But it's running as well as any Qt 5.x version on my Gentoo install (i.e. all the old bugs are still present :-) ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #195 from Bob Wya --- (In reply to abac00s from comment #194) > THANK YOU Bob Wya for the awesome script. You encouraged me to learn bash > scripting ;) Sorry guys - this bad form for a Bugzilla! But the bug is closed - so I'm letting myself off :-) O.T. Well the script is mainly awk. But you can do amazing stuff with awk! I can highly recommend learning it - it's very powerful and has C-like features/syntax. I spent a month doing a deep dive - so I can make it do pretty much anything (I've even written an xml parser in it). I can highly recommend installing / using mawk (which is only awk compatible - and does not support the gawk extensions) - but it's multiple orders of magnitude faster!! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #197 from Bob Wya --- (In reply to Dan Duris from comment #196) > Still happening in the latest Ubuntu 16.04.1 LTS with KDE 4.14.16 See Comment 192 and the initial version the bug was opened with 5.4.3... So how is your KDE 4 issue related to a Plasma 5 / Qt 5 bug? -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 321912] kcalc: radix point not available in any other than base 10
https://bugs.kde.org/show_bug.cgi?id=321912 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #3 from Bob Wya --- Still not available in kcalc version 16.08.1... One can live in hope... :-( I'd like to be able to use binary radix points - in Numerical System mode - as well! Why? Well it's useful for calculating the reciprocal of a decimal number, in binary, to do bit-shift unsigned division. See: http://www.hackersdelight.org/divcMore.pdf -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 367759] System occasionally unable to suspend if Dolphin left running with sshfs folder open
https://bugs.kde.org/show_bug.cgi?id=367759 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 367759] System occasionally unable to suspend if Dolphin left running with sshfs folder open
https://bugs.kde.org/show_bug.cgi?id=367759 --- Comment #2 from Bob Wya --- I've got a systemd sleep script to stop and then restart my sshfs mount unit. This used to work more cleanly - but I believe a few months ago systemd was made atomic during a critical stage of the suspend process (not sure what version that was now). NFS mountpoints are similarly affected. -- 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 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #34 from Bob Wya --- Created attachment 99563 --> https://bugs.kde.org/attachment.cgi?id=99563&action=edit xrandr -q I've just upgraded my Gentoo install to Qt 5.7.0 and Plasma 5.6.5. I've a laptop screen and a LHS external HDMI monitor. They are slightly offset vertically. See xrandr output for what I mean. I'm seeing this bug now for both my panels... 2x panels: bottom of laptop DP screen bottom of HDMI external monitor -- 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 --- Comment #35 from Bob Wya --- Created attachment 99564 --> https://bugs.kde.org/attachment.cgi?id=99564&action=edit xprop (laptop bottom panel) xprop attached. RHS screen (Laptop DP internal screen). bottom panel. -- 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 --- Comment #36 from Bob Wya --- Created attachment 99565 --> https://bugs.kde.org/attachment.cgi?id=99565&action=edit xprop (external HDMI monitor bottom panel) xprop attached. LHS screen (external HDMI monitor). bottom panel. -- 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 --- Comment #37 from Bob Wya --- So I'm booted into my Arch install - same machine - same 2 panels - same monitor setup. My Arch install is on Qt 5.6.1 / plasma 5.6.5. The strut's for the panels are clearly being miscalculated when 2+ mismatched screen size multi-monitor setups are used. Compare the following with the Gentoo Qt 5.7.0 results (see above). Screen 0: minimum 8 x 8, current 4480 x 1588, maximum 16384 x 16384 VGA-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 1920x1080+2560+508 (normal left inverted right x axis y axis) 382mm x 215mm 1920x1080 60.02*+ HDMI-0 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1200 59.9559.88 1920x1080 60.0059.9450.0029.9760.0560.0050.04 1680x1050 59.95 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 With Qt 5.6.1 (LHS): _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 190 _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 190, 0, 0, 0, 0, 0, 0, 0, 2559 With Qt 5.6.1 (RHS): _NET_WM_STRUT(CARDINAL) = 0, 0, 0, 44 _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 44, 0, 0, 0, 0, 0, 0, 2560, 4479 So the RHS base is -148 of the LHS screen (1440-508-1080). Top strut is 190 on LHS panel (higher) = 42 pixel panel height = correct!! Top strut is 44 on RHS panel (lower) = 44 pixel panel height = correct!! -- 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 --- Comment #38 from Bob Wya --- Created attachment 99613 --> https://bugs.kde.org/attachment.cgi?id=99613&action=edit xprop (laptop bottom panel) RHS screen: Laptop bottom panel Correct panel functionality observed Arch Linux with Qt 5.6.1 -- 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 --- Comment #39 from Bob Wya --- Created attachment 99614 --> https://bugs.kde.org/attachment.cgi?id=99614&action=edit xprop (external HDMI monitor bottom panel) LHS screen: HDMI external monitor Correct panel functionality observed Arch Linux with Qt 5.6.1 -- 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 --- Comment #40 from Bob Wya --- Martin, I saw you'd made some commits to plasma/kwin to resolve the "ongoing" STRUT issues in Plasma 5 - that got merged into Plasma 5.6.95. Updating my Gentoo install from Plasma 5.6.5 to 5.6.95 resolved the panel issues for me. The panel STRUT values are back to being positive integers again! Great stuff. Thanks for your hardwork!! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364524] New: kcmshell5 kcm_sddm dumps core everytime it is executed
https://bugs.kde.org/show_bug.cgi?id=364524 Bug ID: 364524 Summary: kcmshell5 kcm_sddm dumps core everytime it is executed Product: systemsettings Version: 5.6.95 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bob.mt@gmail.com Application: systemsettings5 (5.6.95) (Compiled from sources) Qt Version: 5.7.0 Frameworks Version: 5.23.0 Operating System: Linux 4.6.0-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: I'm unable to access the KCM module for SDDM (either via the SystemSettings5 menu or via a direct launch from a console). I'm getting the following message when I attempt: kcmshell 5 kcm_sddm QDBusArgument: read from a write-only object Aborted (core dumped) The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff41bcdb7c0 (LWP 19310))] Thread 6 (Thread 0x7ff3ea693700 (LWP 19317)): #0 0x7ff41836537d in poll () from /lib64/libc.so.6 #1 0x7ff4139dd0ac in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff4139dd432 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff3eb17da26 in gdbus_shared_thread_func () from /usr/lib64/libgio-2.0.so.0 #4 0x7ff413a037b5 in g_thread_proxy () from /usr/lib64/libglib-2.0.so.0 #5 0x7ff415732424 in start_thread () from /lib64/libpthread.so.0 #6 0x7ff41836e3fd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7ff3eae94700 (LWP 19316)): #0 0x7ff41836537d in poll () from /lib64/libc.so.6 #1 0x7ff4139dd0ac in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff4139dd1bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff4139dd1f9 in glib_worker_main () from /usr/lib64/libglib-2.0.so.0 #4 0x7ff413a037b5 in g_thread_proxy () from /usr/lib64/libglib-2.0.so.0 #5 0x7ff415732424 in start_thread () from /lib64/libpthread.so.0 #6 0x7ff41836e3fd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7ff3f4801700 (LWP 19315)): #0 0x7ff41836537d in poll () from /lib64/libc.so.6 #1 0x7ff4139dd0ac in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff4139dd1bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff418cdbebb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7ff418c831ba in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7ff418ac088b in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7ff41736f2e5 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #7 0x7ff418ac62ad in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7ff415732424 in start_thread () from /lib64/libpthread.so.0 #9 0x7ff41836e3fd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7ff4027aa700 (LWP 19313)): #0 0x7ff41836537d in poll () from /lib64/libc.so.6 #1 0x7ff4139dd0ac in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff4139dd1bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff418cdbebb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7ff418c831ba in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7ff418ac088b in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7ff41bddfc08 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #7 0x7ff418ac62ad in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7ff415732424 in start_thread () from /lib64/libpthread.so.0 #9 0x7ff41836e3fd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff40b321700 (LWP 19312)): #0 0x7ff41836537d in poll () from /lib64/libc.so.6 #1 0x7ff415faa8f2 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1 #2 0x7ff415fac707 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7ff40deb9bf9 in QXcbEventReader::run() () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7ff418ac62ad in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #5 0x7ff415732424 in start_thread () from /lib64/libpthread.so.0 #6 0x7ff41836e3fd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff41bcdb7c0 (LWP 19310)): [KCrash Handler] #6 0x7ff4182b82f8 in raise () from /lib64/libc.so.6 #7 0x7ff4182b974a in abort () from /lib64/libc.so.6 #8 0x7ff418aae9e9 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #9 0x7ff41bddef88 in QDBusArgumentPrivate::checkRead(QDBusArgumentPrivate*) [clone .part.27] () from /
[kwin] [Bug 342716] translucency effect causes zombie when closing a window (likely due to multiple and uncancelled "set" calls)
https://bugs.kde.org/show_bug.cgi?id=342716 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #19 from Bob Wya --- Created attachment 99616 --> https://bugs.kde.org/attachment.cgi?id=99616&action=edit KWin Support Information I can reproduce this bug on both Arch with Plasma 5.6.5 and Gentoo with Plasma 5.6.95 (see Gentoo Kwin Support information attached). Simply enabling translucency for Dialogue windows (only) is enough to trigger the issue. Undirect fullscreen windows - makes no difference. Global Animation Speed changes - makes no difference. Disabling and Enabling compositing removes the "ghost" windows. Otherwise the "ghost" windows just hang around (on all desktops). They cannot be interacted with and get overlaid by other Windows - as these are given focus. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps
https://bugs.kde.org/show_bug.cgi?id=340267 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #68 from Bob Wya --- (In reply to wolfyrion from comment #67) > As it mentioned in previous comments > > -> Temporary Fix Solution > Run "kcmshell5 kwinrules" and create a blind rule (just don't press the > detect button),name it whatever you want, then go to the last tab Appearance > and Fixes > --> "Block Compositing" -> Force -> "No" > > This will prevent opengl games or apps to turn off the compositor so the > compositor will always stay on and you will not experience these kind of > problems anymore. > I have been using this temporary fix solution for almost 2 weeks now and > everything works fine :) Further testing :-) A new test case game ;-) : dhewm git (https://github.com/dhewm) - compiled w/ SDL-2 support + original doom 3 assets + doom3 redux mod (http://www.moddb.com/mods/doom-3-redux) Perhaps significant - because it uses the SDL-2 libraries? I have been able to break kwin, with the Oxygen decorator, with this game. Flicking windows, flicking external monitor, i.e. the "full works". So finally broke down and used the kwin force enable compositing rule (see above). No issues what-so-ever after the game exits... So just to confirm a kwin rule to "globally force enabling compositing" clearly fixes the original issue I reported. So this will be my chosen route going forwards... Sadly I feel I'll probably be using this "temporary fix" for months - going forwards!! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray
https://bugs.kde.org/show_bug.cgi?id=355587 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray
https://bugs.kde.org/show_bug.cgi?id=355587 --- Comment #7 from Bob Wya --- (In reply to Rog131 from comment #6) > Kubuntu forums has an example how to edit the Layout.js to get smaller icons > to the vertical system tray: > https://www.kubuntuforums.net/showthread.php?69658-Reduce-icon-size-in- > vertical-panel&p=384036&viewfull=1#post384036 Boom!! IMHO that should exposed in the (rather anaemic) system tray configuration gui... Thanks :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray
https://bugs.kde.org/show_bug.cgi?id=355587 --- Comment #8 from Bob Wya --- (In reply to Martin Klapetek from comment #3) > I think this https://git.reviewboard.kde.org/r/125773/ could/would fix it. > > Are you able to test patches? Could you test this one? I've tested the patch - along with setting my systemtray icons to a fixed size (16x16) - in the systemtray plasmoid. I don't normally run with a Vertical Panel (since KDE4 / Plasma 5 have not supported this configuration very well). Now I've got to say it's become a totally viable option!! It's possible to match the look 'n' feel of a Windows vertical panel (which previously looked far better). Should this bug have the VisualDesign + set? The vertical panel configuration thread - was a hot topic in the VDG subforum - when Plasma 5 was being worked on!! Personally I really like my new look desktop. It's now possible to have much thinner panels - without the systemtray icons looking dumbly oversized. Screenshots can be supplied - if anyone is interested... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 344074] Tabs not movable
https://bugs.kde.org/show_bug.cgi?id=344074 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363424] Kate does not save settings regarding extensions when closed
https://bugs.kde.org/show_bug.cgi?id=363424 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 354482] scrolling quickly with the mouse wheel jumps and can even scroll backwards
https://bugs.kde.org/show_bug.cgi?id=354482 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #6 from Bob Wya --- Unlike KDE-4 I've got to remember to give Qt 5 applications explicit mouse focus before scrolling in them... I don't see what's hard about reproducing this Qt 5 bug... It occurs every time that I mouse over a scrollable region, in a Qt 5 application, and I don't give that Window explicit focus (by giving it a LHS mouse button event)!! It's really annoying... :-( -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 --- Comment #11 from Bob Wya --- Created attachment 97973 --> https://bugs.kde.org/attachment.cgi?id=97973&action=edit Rex Dieter's patch : kcalc don't set a zero minimum size Thanks Rex. The Attachment button (cough) it's a thing... :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #43 from Bob Wya --- I'm running Gentoo - but now with: Qt 5.6.0 kde-frameworks 5.20.0 kde-plasma 5.5.95 Newly "minted" from the gcc factory. I can't reproduce the bug anymore!! Played a full screen game. Unplugged and re-plugged in an external (HDMI connected) monitor. My 2 bottom panels are restored to their original positions - in both instances. Previously they would both fly onto the external monitor and stick there... Yay!! All is right(ish) now :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361091] Translucency lost when starting video using mpv bypassing the compositor
https://bugs.kde.org/show_bug.cgi?id=361091 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #4 from Bob Wya --- (In reply to rphl from comment #2) > _NET_WM_BYPASS_COMPOSITOR hint that got support in plasma 5.6 by kwin breaks > a lot of user apps like this https://github.com/mpv-player/mpv/issues/2997 > Plus if I try to turn on\off effects while app is still running window > decorations break and I have graphical artifacts around window which persist > until kwin is restarted. @rphl, I'm also seeing this issue.. Launching a (native) Steam game and returning to the desktop leaves all the Window decorations broken... A large black border replaces the shadow region. All applications are affected. @Thomas, I've rebuild all my (Gentoo) Plasma packages with debug info enabled... So I guess I will (now) be able to supply more useful info... Do you want: qdbus org.kde.KWin /KWin supportInformation from before / after window breakage - or both? I can confirm that it was only my move from Plasma 5.5.5 to 5.6.0 that caused this breakage... All other packages were held at a fixed version. Restarting Plasmashell or turning compositing off & on doesn't clear the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] New: Running native OpenGL games - with compositing enabled - breaks Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 Bug ID: 361154 Summary: Running native OpenGL games - with compositing enabled - breaks Plasma 5.6.0 Window Decorations Product: kwin Version: 5.6.0 Platform: Gentoo Packages URL: http://i116.photobucket.com/albums/o35/bob_mt_wya/KDE% 20Plasma%205.6.0%20Window%20Decoration%20breakage_zpsp 458pdal.jpg OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: bob.mt@gmail.com Using: emerge -pv nvidia-drivers xorg-server =sys-kernel/gentoo-sources-4.4.6 [ebuild R #] x11-base/xorg-server-1.18.1-r1:0/1.18.1::bobwya USE="ipv6 suid systemd udev xorg -dmx -doc -glamor -kdrive -libressl -minimal (-selinux) -static-libs -tslib -unwind -wayland -xephyr -xnest -xvfb" 5,710 KiB [ebuild R #] x11-drivers/nvidia-drivers-364.12-r2:0/364::bobwya USE="X acpi driver kms multilib tools uvm -compat -gtk3 -pax_kernel -static-libs -wayland" 0 KiB [ebuild R ~] sys-kernel/gentoo-sources-4.4.6:4.4.6::gentoo USE="experimental -build -kdbus -symlink" 85,566 KiB Including, the following configuration options enabled in my kernel: CONFIG_DRM_KMS_HELPER=y CONFIG_DRM_KMS_FB_HELPER=y Reproducible: Always Steps to Reproduce: 1. Compositing on 2. Launch a fullscreen 3D/GL based game Actual Results: Window Decorations break. Window shadows become solid black bars around all windows. Opening new Windows causes alternate monitor (dual-monitor setup) to flicker rapidly (sync issue / Nvidia driver issue?) Expected Results: Window Shadowing should be restored - after exiting the 3D game. Window Shadows do NOT break if compositing is disabled before running a GL-based game. Window Shadowing only restores if I log out (or presumably if I restart kwin_x11 - I'll test this!!). Moving or resizing windows has no effect - the shadowing remains in a broken state. Flicking issues get significantly worse whilst doing this... Desktop effects (3D Cube, etc.) appear to remain intake and also show the Window artefacts... I haven't done much testing - because I only did an update from Plasma 5.5.5 -> 5.6.0 yesterday... I'll add any other useful information as and when... :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #1 from Bob Wya --- Created attachment 98148 --> https://bugs.kde.org/attachment.cgi?id=98148&action=edit qdbus org.kde.KWin /KWin supportInformation Output from running: qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 Bob Wya changed: What|Removed |Added Summary|Running native OpenGL games |Running native OpenGL games |- with compositing enabled |- with compositing enabled |- breaks Plasma 5.6.0 |- breaks X11 Plasma 5.6.0 |Window Decorations |Window Decorations -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361091] Translucency lost when starting video using mpv bypassing the compositor
https://bugs.kde.org/show_bug.cgi?id=361091 --- Comment #6 from Bob Wya --- (In reply to Thomas Lübking from comment #5) > And please open a new bug about this - this one here is *very* prone to be > closed as "invalid" anytime soon (the hint is supposed to have such or > similar effect) Okey dokey... https://bugs.kde.org/show_bug.cgi?id=361154 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #2 from Bob Wya --- Just to confirm... running: DISPLAY=:0 kwin_x11 --replace restores full Desktop compositing functionality (as I postulated above)... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #4 from Bob Wya --- I've just rev-bumped to Plasma 5.6.1 and the issue is unchanged. (In reply to Martin Gräßlin from comment #3) > Is the debug output from when the problem is visible? If not could you > please attach one when the problem is visible? Maybe also one while running > the game. Yes the debug output is from when the problem was visible. > As you say that kwin_x11 --replace fixes it: what about using alt+shift+F12 > twice? Does that work as well? No I tried the less drastic tests first... :-) Toggling compositing off/on and restarting the Plasma Shell has no effect - the aforementioned glitches remain. I've not seen it reported anywhere else... So perhaps it's just a bug in the Nvidia beta driver? I believe it's the first version to offer proper (well nearly) KMS support... Would it help if dropped back to the new Nvidia stable release 361.42? I'm trying to avoid making too many "random changes" at once!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #9 from Bob Wya --- (In reply to Thomas Lübking from comment #8) > @Bob, this bug derived from bug #361091 so the major question is whether > > Launch a fullscreen 3D/GL based game > or the autosuspension is crucial here. > > Do you eg. get the problem when running "glxgears -fullscreen" or when > adding a window rule (run "kcmshell5 kwinrules") for xterm to block > compositing (last tab)? glxgears -fullscreen doesn't actually run fullscreen (the KDE/Plasma panel remains below the window). I don't see any compositing issues in this instance (during or post execution of glxgears). I can disable compositing for say the Steam client (in a kwin rule) and launching a Steam game - does not cause the compositing issues. Is that what you're asking? > Assuming running a fullscreen GL game is the problem, what if you disable > "suspend the compositor for fullscreen windows" in "kcmshell5 > kwincompositing"? This setting has no effect on the issue - in my case... In either case the compositing glitching appears. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #10 from Bob Wya --- (In reply to Steffen Klee from comment #6) > > I've experienced this issue after upgrading to plasma 5.6 and I'm using > radeon driver. To be clear... Are you seeing the same shadowing glitching - for all Windows? (See my screenshot URL above) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #13 from Bob Wya --- (In reply to Thomas Lübking from comment #11) > (In reply to Bob Wya from comment #9) > > > glxgears -fullscreen > > doesn't actually run fullscreen > > you can "kstart5 --fullscreen glxgears" Yes it's fullscreen now. No compositing issues (during or post). > And depending on your findings (and since you're on gentoo ;-): > https://github.com/luebking/starfield > > Sorry for advertising, but "starfield fullscreen" (run from the build dir > since it looks for the star textures in . only) > a) should work (fullscreenwise) and > b) it's a pretty dumb implementation on the fixed function pipeline, yet in > comparism to glxgears uses textures (in case that should be relevant) Damn spam again :-) I like it so much - I've packaged it up for my Layman Overlay. Seriously looks quite cool across my dual-monitor setup :-) Sadly (or not sadly) there are still no compositing issues (during or post). > > I can disable compositing for say the Steam client (in a kwin rule) and > > launching a Steam game - does not cause the compositing issues. Is that what > > you're asking? > > Yes, because it means it's not related to 361091, ie. > _NET_WM_BYPASS_COMPOSITOR and whatever rphl encounters in this case. Sure. Seems to be a separate issue. May not even be a "thing" if Steffen doesn't having matching symptoms. Every second Nvidia driver appears to have some annoying bug in it - that breaks something for me (like suspend-resume). Just now I've even got access to TTY consoles (finally) - damn UEFI!! So I'm reluctant to change versions... 8-) Thanks -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 344456] Plasma 5 desktop does not suspend with only upower, no systemd
https://bugs.kde.org/show_bug.cgi?id=344456 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #22 from Bob Wya --- (In reply to Martin Gräßlin from comment #21) > Could anybody please attach a screenshot of those broken window decorations. Martin, I did originally link to a screenshot in the URL - top field in the bug report - when I first created the bug (sorry about the use of Photobucket!!) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #23 from Bob Wya --- ( I linked to it originally - because the KDE Bugs website wouldn't let me attach the screenshot - still doesn't ??!!) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #33 from Bob Wya --- Created attachment 98361 --> https://bugs.kde.org/attachment.cgi?id=98361&action=edit KDE Plasma 5.6.0 Window Decoration breakage.jpg Window shadowing breakage with Plasma Desktop 5.6.0/5.6.1 (dual-monitor setup). Effect only observed after playing a full-screen native GL game (or full-screen game via Wine). Glitch cleared by restarting kwin_x11 process Glitch not effected by restarting plasma-shell process System packages: media-libs/mesa-11.1.2 x11-base/xorg-server-1.18.1 x11-drivers/nvidia-drivers-364.12 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #34 from Bob Wya --- Created attachment 98363 --> https://bugs.kde.org/attachment.cgi?id=98363&action=edit kwin_x11 console output @Martin, here's the kwin_x11 console log you wanted (see attachment): 1) DISPLAY=:0 kwin_x11 --replace &>kwin_x11.txt 2) Launch the original (offending) native game as before (PAYDAY 2) 3) Get to the main game menu 4) Exit game. 5) Stop kwin_x11 console logging at this point. I'm sticking to the same nvidia-drivers, xorg-server, etc. - to avoid any further complications/ issues that might arise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #42 from Bob Wya --- Created attachment 98386 --> https://bugs.kde.org/attachment.cgi?id=98386&action=edit pkill -9 kwin_x11 ; DISPLAY=:0 kwin_x11 --replace &>/dev/null & (In reply to Martin Gräßlin from comment #35) > Thanks for the log! There are two things in the log which I consider > suspicious: > * lots of "QPainter::restore: Unbalanced save/restore" - that's probably the > breeze deco > * QOpenGLContext::swapBuffers() called with non-exposed window, behavior is > undefined > > the latter must be from Qt, we don't use that in the rendering path, so > hopefully should not matter. > > Let's focus on the first issue: maybe try a different window decoration? Martin I've attached the log from running with the Plastik Window decoration... No other system changes. This time I do not notice the Window shadow artefacts or the monitor flashing/sync issues after running my test game. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #43 from Bob Wya --- (In reply to wolfyrion from comment #40) ... blah blah... blah... Any tips? Reminder, time to "focus": "Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations" Clicky, clicky here... https://bugs.kde.org/enter_bug.cgi?format=guided Thankfully I don't need to be as polite as Thomas - also I've just finished a 14 hour shift :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #45 from Bob Wya --- (In reply to Thomas Lübking from comment #44) > It really looks like the imbalanced painter in/with the breeze deco is the > problem. > Does altering the breeze shadow settings "fix" anything (ie. resolve the > artifacts) > > Run > breeze-settings5 > and adjust settings in decoration/shadows (pick a different size or color) Thomas, making the breeze shadows smaller - makes the affected area a bit smaller (surprise, surprise). But things are still just as broken - there's the odd flashing blob in the decoration area (round the buttons). I've tried turning off as much as possible (animations, background gradient, etc.) - but the problem isn't going away. I've read a few Arch forum threads complaining about the breeze theme breaking stuff - but I haven't noticed any issues with it - till now with Plasma 5.6.0. > Fwwi, I simply write 2 versions of such replies >-) Yeah, also it's so easy to mix up soapboxes, forums and bugzillas - the Internet is sooo complex 8-] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #47 from Bob Wya --- Created attachment 98397 --> https://bugs.kde.org/attachment.cgi?id=98397&action=edit pkill -9 kwin_x11 ; DISPLAY=:0 kwin_x11 --replace &>~/kwin_x11_oxygen.txt & (In reply to Martin Gräßlin from comment #46) > Thanks Bob, > > though Plastik doesn't have shadows, so maybe that's just an effect of > having less large shadows. Maybe give a try with a downloaded theme which > has shadows? Martin, I was planning to try try the Oxygen decoration theme last night (which I've got installed already) - but owing to tiredness I'd get round to it :-) . I presume that would be a valid test (since the Oxygen decorations have configurable shadowing)??! After running the test game, with the Oxygen decorations, the Kwin compositor appears to restart correctly and the shadowing is restored - without visible glitches. I've set the active Window setup with a lurid (!!)/ large purple shadow - so it'd be pretty obvious if this was broken. I've attached the log for kwin_x11 whilst running the game with the Oxygen theme... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 170582] Configure Konsole Scroll Wheel Behavior
https://bugs.kde.org/show_bug.cgi?id=170582 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #77 from Bob Wya --- (In reply to thomi_ch from comment #76) > achat1...@free.fr i tried your script, but no success.. > i needed to change the file manually and restart plasma... Now we are getting meta bug reports about workaround scripts for the original bug... 8-> -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 148939] wheel mouse: provide immediate scrolling of the tab content instead of scrolling through the tabs
https://bugs.kde.org/show_bug.cgi?id=148939 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360942] Misplaced menus and tooltips after 2 screen size changes
https://bugs.kde.org/show_bug.cgi?id=360942 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 362864] New: Kate does not save Sidebar state in configuration settings files
https://bugs.kde.org/show_bug.cgi?id=362864 Bug ID: 362864 Summary: Kate does not save Sidebar state in configuration settings files Product: kate Version: 5.0.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: bob.mt@gmail.com Using Kate 16.04.0 Everytime I start Kate it opens the documents Sidebar. I don't use this feature... So I turn it off. But because this setting is not saved anywhere (I've checked the before/after Kate configuration files with diff). The Sidebar reappears the next time I open Kate... Reproducible: Always Steps to Reproduce: 1. Start Kate session (either from shell or application menu/krunner) 2. Close Sidebar 3. In Kate settings menu : enable save Window state in Session / Load last used Session 4. Close Kate 5. Restart Kate (as per 1.) Actual Results: Re-started Kate session has Sidebar enabled. Expected Results: Re-started Kate session remembers Sidebar state. Therefore Kate SIdebar is disabled. This was NOT a "feature" in the KDE 4.x branch of Kate!! If I turned off the Sidebar - it would STAY turned OFF - the next time I opened Kate... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #91 from Bob Wya --- (In reply to Martin Gräßlin from comment #90) > and a patch: https://phabricator.kde.org/D2483 Thanks for all your hardwork on this one! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #92 from Bob Wya --- (In reply to Martin Gräßlin from comment #90) > and a patch: https://phabricator.kde.org/D2483 I've tested this patch on kde-win 5.7.3. Dual monitor setup - so I can see compositing switch off and on (to confirm this aspect of the bug). KWin rule to force enable compositing deleted. Breeze decorations re-enabled. Ran my current test - dhewm with Doom 3 HD texture pack mod. No decoration shadow breakage and none of the secondary weird side-effects (like one display flickering constantly - when new application windows are created), etc. So looking good at my end!! :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #94 from Bob Wya --- (In reply to wolfyrion from comment #93) > > hi Bob Wya , > One question please: > When you run an opengl game/app does it turn off the compositor or not?? > (Before it said that this happening because the drivers request to do so > and we had to force to enable compositor using the rules) > if compositor is getting disable you will notice a lot of tearing in most of > the games thats why we want the compositor to be enable. > > Broken Texures/Shadows and Turning off compositor when launching an opengl > game or app. > So with this patch both of these problems are solved? The original problem that I reported: Launching a 3D Opengl game. Sometime during the switch from compositor on, to compositor off and back again (automatically handled by Kwin/Plasma) the Breeze decoration shadows break. By that definition the bug is fixed on my system... I'm not exactly sure what you are asking... The problem, _I_ reported, has been fixed, by Martin, as I clearly stated... You still got issues?? Then open another (SEPARATE) bug - no bug hi-jacking :-) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364524] kcmshell5 kcm_sddm dumps core everytime it is executed
https://bugs.kde.org/show_bug.cgi?id=364524 --- Comment #3 from Bob Wya --- (In reply to andreas.sturmlechner from comment #2) > Is it safe to assume you have built Qt with USE=debug? You presume correctly. You may also presume, that building with Qt 5.7.0 with USE=-debug, fixes the issue! I am able launch kcm_sddm without any issues in this instance. I might have forgotten to report this fact - I stumbled upon a month or two ago (cough). :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] after suspend/resume, some widgets show graphic failure
https://bugs.kde.org/show_bug.cgi?id=364766 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 337355] plasma 5 panel gets too transparent in desktop cube
https://bugs.kde.org/show_bug.cgi?id=337355 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 351827] No way to see elided application names in Application Dashboard in full
https://bugs.kde.org/show_bug.cgi?id=351827 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225
Bob Wya changed:
What|Removed |Added
CC||bob.mt@gmail.com
--- Comment #21 from Bob Wya ---
I purposely don't unplug my external whilst using Plasma 5 - because of this
annoying bug!!
Playing fullscreen games (which alter xrandr settings) also will makes your
Plasma 5 panel(s) disappear... Logging out and logging back in brings it back -
but that is not exactly super-convenient!!
grep -B 6 -A 2 panel "${HOME}/.config/plasma-org.kde.plasma.desktop-appletsrc"
[Containments][1]
activityId=
formfactor=3
immutability=1
lastScreen=1
location=5
plugin=org.kde.panel
wallpaperplugin=org.kde.image
xrandr -q
Screen 0: minimum 8 x 8, current 4480 x 1630, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 1920x1080+2560+550 (normal left inverted right x axis y
axis) 382mm x 215mm
1920x1080 60.02*+
HDMI-0 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm
x 336mm
2560x1440 59.95*+
1920x1200 59.9559.88
1920x1080 60.0059.9450.0029.9760.0560.0050.04
1680x1050 59.95
1600x1200 60.00
1600x900 60.00
1280x1024 75.0260.02
1280x720 60.0059.9450.00
1152x864 75.00
1024x768 75.0360.00
800x600 75.0060.32
720x576 50.00
720x480 59.94
640x480 75.0059.9459.93
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 358108] Persistent favorite apps in Application Dashboard (and possibly in Kicker and Kickoff)
https://bugs.kde.org/show_bug.cgi?id=358108 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #1 from Bob Wya --- Yup. This is not really ideal. Say you have 2 panels (1 / monitor) each with a kickoffdash. Then you might (!!) want to have the favourites linked / synced between. However think again - bzzzt - no!! So basically I've got to manually hack about in the configuration files to fix this issue. 1) Alter: /usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/config/main.xml to "fix" / change the default global favourites. and / or 2) Add further cruft to my BASH script to fix (which runs pre-startup): ~/.config/plasma-org.kde.plasma.desktop-appletsrc which already "fixes" another Plasma 5 bug where panels randomly move when you change screen configuration... Add a hack to sync my favourites between the panels (each with a separate kickoffdash). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #26 from Bob Wya ---
Created attachment 97673
--> https://bugs.kde.org/attachment.cgi?id=97673&action=edit
Plasma 5 panel location reset BASH script (hack!!)
For anyone where restarting the Plasma Shell is not enough to fix your panel
locations...
For my own use I had to write a little script to move my panels back to the
screens I want them on - when running games in dual monitor setup. The script
is simply a hack to go through the main configuration file and re-write you
panel settings back to some sane defaults (of your choosing).
The script details the codes for the panel locations (left, top, right, bottom)
- but you'll probably want to copy your existing panel settings, from your own
configuration file, into the script. You can read your existing Plasma 5 panel
settings with:
grep -B 6 -A 1 'org.kde.panel'
"${HOME}/.config/plasma-org.kde.plasma.desktop-appletsrc"
I've got this script set on a global shortcut and it's a life saver - till this
bug gets fixed!!
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #35 from Bob Wya ---
(In reply to Bernd Steinhauser from comment #34)
> This got actually worse with 5.5.95. Not sure about the desktop, because I
> gave up on using wallpapers, because plasmashell will do whatever it wants
> with them anyway.
> However, it is really impressive with what accuracy and determination,
> plasmashell moves two panels that were on different screens onto the same
> screen after reboot.
>
> I mean I can understand if screen numbering gets messed up and things that
> should be on screen X end up on screen Y and the other way round. But just
> putting everything on screen X and nothing on screen Y? Why?
> It really feels like there is no concept of remembering where things were
> when shutting down.
>
> Also interesting is that it constantly complains about
> "requesting unexisting screen 3"
> when nothing in .config/plasma-org.kde.plasma.desktop-appletsrc has an entry
> that could be related to a "screen 3". Everything in there says -1, 0, 1 or
> 2.
> The other plasma config files don't mention screen 3 either, afaics.
> Not sure what's going on, or is it just that some parts of plasma count from
> 0 and some count from 1?
> Well then I could understand if it gets confused by itself. ;)
Have a look at my (cough) workaround script...
https://bugs.kde.org/attachment.cgi?id=97673
I've actually got a copy of the script globally bound to CTRL+ATL+BACKSPACE !!
The settings in my script are specific to my system (a bottom panel on each, of
2 screens).
So you'll need to edit the script first and put in your personal panel
settings. :-)
To obtain the settings for your current panel setup - execute:
egrep -B 6 -A 1 '^plugin=org.kde.panel'
"${HOME}/.config/plasma-org.kde.plasma.desktop-appletsrc"
I've added a comment table to deceiver the codes that determine where a panel
is positioned (LEFT, RIGHT, TOP, BOTTOM).
Screen numbering is from 0 ... (as you speculated).
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #46 from Bob Wya --- (In reply to Bernd Steinhauser from comment #44) > This is getting repetitive. The bug is not fixed by Qt 5.6, it's not fixed > by KF5 5.20 and neither Plasma 5.5.95. > > If you don't see, you're lucky (congrats), but the bug is still there, as > pointed out above. No, but it's weird that I can't reproduce it any more... I've not applied any special patches (just the 2 extra qtdbus patches that Arch picked up and Gentoo hasn't)... Oh well :-) I did add "/etc/X11/xorg.conf.d/70-screen.conf" recently: # xrandr -s 0 : both internal laptop display & external monitor on # xrandr -s 1 : internal laptop display off & external monitor on # xrandr -s 2 : internal laptop display on & external monitor off Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 Option "Stereo" "0" Option "nvidiaXineramaInfoOrder" "DFP-2" Option "metamodes" "DP-2: nvidia-auto-select +2560+506, HDMI-0: nvidia-auto-select +0+0" Option "metamodes" "DP-2: 1920x1080 +2560+506, HDMI-0: 2560x1440 +0+0; DFP-2: NULL, HDMI-0: 2560x1440 +0+0" Option "metamodes" "DP-2: 1920x1080 +2560+506, HDMI-0: 2560x1440 +0+0; DFP-2: 1920x1080 +0+0, HDMI-0: NULL" Option "SLI" "Off" Option "MultiGPU" "Off" Option "BaseMosaic" "off" SubSection "Display" Depth 24 EndSubSection EndSection So I'll try booting without that (I just added it to get my monitors lined up correctly in SDDM)... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 354482] scrolling quickly with the mouse wheel jumps and can even scroll backwards
https://bugs.kde.org/show_bug.cgi?id=354482 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #6 from Bob Wya --- Unlike KDE-4 I've got to remember to give Qt 5 applications explicit mouse focus before scrolling in them... I don't see what's hard about reproducing this Qt 5 bug... It occurs every time that I mouse over a scrollable region, in a Qt 5 application, and I don't give that Window explicit focus (by giving it a LHS mouse button event)!! It's really annoying... :-( -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 --- Comment #11 from Bob Wya --- Created attachment 97973 --> https://bugs.kde.org/attachment.cgi?id=97973&action=edit Rex Dieter's patch : kcalc don't set a zero minimum size Thanks Rex. The Attachment button (cough) it's a thing... :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #43 from Bob Wya --- I'm running Gentoo - but now with: Qt 5.6.0 kde-frameworks 5.20.0 kde-plasma 5.5.95 Newly "minted" from the gcc factory. I can't reproduce the bug anymore!! Played a full screen game. Unplugged and re-plugged in an external (HDMI connected) monitor. My 2 bottom panels are restored to their original positions - in both instances. Previously they would both fly onto the external monitor and stick there... Yay!! All is right(ish) now :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361091] Translucency lost when starting video using mpv bypassing the compositor
https://bugs.kde.org/show_bug.cgi?id=361091 Bob Wya changed: What|Removed |Added CC||bob.mt@gmail.com --- Comment #4 from Bob Wya --- (In reply to rphl from comment #2) > _NET_WM_BYPASS_COMPOSITOR hint that got support in plasma 5.6 by kwin breaks > a lot of user apps like this https://github.com/mpv-player/mpv/issues/2997 > Plus if I try to turn on\off effects while app is still running window > decorations break and I have graphical artifacts around window which persist > until kwin is restarted. @rphl, I'm also seeing this issue.. Launching a (native) Steam game and returning to the desktop leaves all the Window decorations broken... A large black border replaces the shadow region. All applications are affected. @Thomas, I've rebuild all my (Gentoo) Plasma packages with debug info enabled... So I guess I will (now) be able to supply more useful info... Do you want: qdbus org.kde.KWin /KWin supportInformation from before / after window breakage - or both? I can confirm that it was only my move from Plasma 5.5.5 to 5.6.0 that caused this breakage... All other packages were held at a fixed version. Restarting Plasmashell or turning compositing off & on doesn't clear the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] New: Running native OpenGL games - with compositing enabled - breaks Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 Bug ID: 361154 Summary: Running native OpenGL games - with compositing enabled - breaks Plasma 5.6.0 Window Decorations Product: kwin Version: 5.6.0 Platform: Gentoo Packages URL: http://i116.photobucket.com/albums/o35/bob_mt_wya/KDE% 20Plasma%205.6.0%20Window%20Decoration%20breakage_zpsp 458pdal.jpg OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: bob.mt@gmail.com Using: emerge -pv nvidia-drivers xorg-server =sys-kernel/gentoo-sources-4.4.6 [ebuild R #] x11-base/xorg-server-1.18.1-r1:0/1.18.1::bobwya USE="ipv6 suid systemd udev xorg -dmx -doc -glamor -kdrive -libressl -minimal (-selinux) -static-libs -tslib -unwind -wayland -xephyr -xnest -xvfb" 5,710 KiB [ebuild R #] x11-drivers/nvidia-drivers-364.12-r2:0/364::bobwya USE="X acpi driver kms multilib tools uvm -compat -gtk3 -pax_kernel -static-libs -wayland" 0 KiB [ebuild R ~] sys-kernel/gentoo-sources-4.4.6:4.4.6::gentoo USE="experimental -build -kdbus -symlink" 85,566 KiB Including, the following configuration options enabled in my kernel: CONFIG_DRM_KMS_HELPER=y CONFIG_DRM_KMS_FB_HELPER=y Reproducible: Always Steps to Reproduce: 1. Compositing on 2. Launch a fullscreen 3D/GL based game Actual Results: Window Decorations break. Window shadows become solid black bars around all windows. Opening new Windows causes alternate monitor (dual-monitor setup) to flicker rapidly (sync issue / Nvidia driver issue?) Expected Results: Window Shadowing should be restored - after exiting the 3D game. Window Shadows do NOT break if compositing is disabled before running a GL-based game. Window Shadowing only restores if I log out (or presumably if I restart kwin_x11 - I'll test this!!). Moving or resizing windows has no effect - the shadowing remains in a broken state. Flicking issues get significantly worse whilst doing this... Desktop effects (3D Cube, etc.) appear to remain intake and also show the Window artefacts... I haven't done much testing - because I only did an update from Plasma 5.5.5 -> 5.6.0 yesterday... I'll add any other useful information as and when... :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 --- Comment #1 from Bob Wya --- Created attachment 98148 --> https://bugs.kde.org/attachment.cgi?id=98148&action=edit qdbus org.kde.KWin /KWin supportInformation Output from running: qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 Bob Wya changed: What|Removed |Added Summary|Running native OpenGL games |Running native OpenGL games |- with compositing enabled |- with compositing enabled |- breaks Plasma 5.6.0 |- breaks X11 Plasma 5.6.0 |Window Decorations |Window Decorations -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361091] Translucency lost when starting video using mpv bypassing the compositor
https://bugs.kde.org/show_bug.cgi?id=361091 --- Comment #6 from Bob Wya --- (In reply to Thomas Lübking from comment #5) > And please open a new bug about this - this one here is *very* prone to be > closed as "invalid" anytime soon (the hint is supposed to have such or > similar effect) Okey dokey... https://bugs.kde.org/show_bug.cgi?id=361154 -- You are receiving this mail because: You are watching all bug changes.
