[frameworks-kxmlgui] [Bug 415591] In a multi-display setup, KDE apps only remember window size across program launches when closed on the left-most display
https://bugs.kde.org/show_bug.cgi?id=415591 S. Bryant changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459964] Application Menu (Kicker) pushes windows out of the way
https://bugs.kde.org/show_bug.cgi?id=459964 --- Comment #3 from S. Bryant --- (In reply to Nate Graham from comment #2) > Already fixed in Frameworks 5.99, which was released today! That's excellent. I've now installed it and can confirm the bug is fixed. Many thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459964] Application Menu (Kicker) pushes windows out of the way
https://bugs.kde.org/show_bug.cgi?id=459964 --- Comment #1 from S. Bryant --- Just noticed: the calendar date popup from the panel clock does exactly the same thing. It's animated; the animation draws in front of other windows, but when complete, windows are pushed out of the way or resized. Maximised windows on other virtual desktops are also resized. This becomes apparent, as they are sometimes not restored. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459964] New: Application Menu (Kicker) pushes windows out of the way
https://bugs.kde.org/show_bug.cgi?id=459964 Bug ID: 459964 Summary: Application Menu (Kicker) pushes windows out of the way Classification: Plasma Product: plasmashell Version: 5.25.90 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: st...@bawue.de Target Milestone: 1.0 SUMMARY The "Application Menu" widget pushes windows out of the way instead of displaying in front of them. Maximised windows are resized to make space for the application menu, instead of being pushed. In both cases, the windows are returned to their original location/size when the application menu closes, but not always. Moving the launcher button away from the end of the panel restores the old behaviour. I tested by putting the clock as the leftmost panel widget. The "Application Launcher" widget does not do this - it displays in front of other windows as expected. STEPS TO REPRODUCE 1. Have "Application Menu" selected as the launcher alternative 2. Have the launcher button at the either end of the full-width panel 3. Click on the launcher button in the panel OBSERVED RESULT Windows are pushed out of the way or resized, and the menu displayed next to them. EXPECTED RESULT The menu is displayed in front of the windows; windows are not moved or resized SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION This bug was observed under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 S. Bryant changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #13 from S. Bryant --- Minor update: I changed the BIOS setting to "discrete", ie: use Nvidia only and ignore the Intel graphics card. Now the lag has gone, the kwin_wayland CPU usage is down to a negligable amount, and the mouse is smooth across all screens. Glxgears runs at around 60FPS (the screen refresh rate), and my windows are wobbly again as they should be. As this was working (for me) until yesterday, I suspect we have a regression in the handling of the passthrough to the second graphics card. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #12 from S. Bryant --- I'm seeing this problem since an update yesterday (openSUSE RPMs), which makes me wonder why I haven't been bitten by it before. Perhaps a default setting was changed. System setup is a laptop (2021 HP ZBook Fury) with Intel+Nvidia graphics in "hybrid" mode (BIOS setting). I'm using Intel as the primary, so the external screens connected via a Thunderbolt dock go via the Nvidia path. I have Plasma 5.25.4 and Nvidia G06 515.65. I have the same symptoms as others. The kwin_wayland process is now always using the CPU. Just moving the mouse around causes a large increase in CPU usage. Screen updates are very slow, and to my eye it looks like single digit FPS. I note that glxgears, while slower on the Nvidia screen, still reports a fairly high FPS. I suspect that the problem lies solely with the transfer between the graphics cards, and that the application doesn't see this. It reports around 600FPS in glxgears, regardless of whether I use DRI_PRIME=1 or not, but as mentioned above, it does not look like that. Both variations use a similarly high amount of CPU. Possibly related: with this last update, auto-blanking (after a timeout) has stopped working, as has the wobbly windows effect. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425799] Snapping makes it impossible to set up the positioning perfectly on a multi screen setup in the KCM
https://bugs.kde.org/show_bug.cgi?id=425799 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #4 from S. Bryant --- Hi.. Just to say this issue still exists (Plasma 5.25, Wayland). The snapping does seem to be related to the screen scales, but it ends up hindering more than helping. I have three screens, set to 145%, 170% and 100%. The first two are the laptop and an external monitor that physically align at the bottom. The snapping in the system settings stops them from being alignable at their lower edges. It would allow aligning them at the top, but who has a laptop physically aligned with an external monitor at the top? The problem wasn't really visible under X11 as all screens had the same scale; it was also possible to use xrandr to do stuff the system settings couldn't. A checkbox in the system settings to disable snapping would be great. A CLI program with a subset of xrandr functionality for Wayland (ie: positioning) would also be a usable workaround. Does one exist already? Lastly, even hand-editing an rc-file and killing+restarting plasmashell or some other process would do, I think. Perhaps somebody could tell me which file and which process - I wasn't able to find out. Thanks... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 --- Comment #59 from S. Bryant --- After a system update openSUSE 15.3 -> 15.4 and Plasma -> 5.25.1, I'm no longer seeing this problem. BTW, I'm using the G06 v515.48 Nvidia driver. I was able to switch the laptop to discrete graphics and use only the NVidia chip. Wayland no longer crashes as it did previously, so this particular problem seems to be fixed. Many thanks... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452393] New: Screen layout changes every login after ScreenConnectors changes [Wayland]
https://bugs.kde.org/show_bug.cgi?id=452393 Bug ID: 452393 Summary: Screen layout changes every login after ScreenConnectors changes [Wayland] Product: plasmashell Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: st...@bawue.de CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY The multi-monitor layout is different each login on Wayland. This affects a number of related settings: position, size (zoom), desktop background, panel configuration etc. The cause appears to be the name assignment in `~/.config/plasmashellrc`. First login: [ScreenConnectors] 0=eDP-1 1=DP-8 2=DP-9 Second login: [ScreenConnectors] 0=eDP-1 1=DP-6 2=DP-7 On my system, the laptop screen (eDP-1) is always screen 0. The other displays are the same physical displays on the same physical ports, but the DP-n number changes each time. STEPS TO REPRODUCE 1. Login to Wayland and configure screen layout 2. Logout + reboot 3. Login to Wayland OBSERVED RESULT The screen layout has changed EXPECTED RESULT The screen layout is the same SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2+kde294 ADDITIONAL INFORMATION The laptop has hybrid Intel/Nvidia graphics. The Intel UHD graphics drive the primary laptop display, the external monitors are connected via a Thunderbolt dock, which is routed via the Nvidia chip. This may be related to bug 427278 - although that was for X11 & VNC, and is resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 --- Comment #51 from S. Bryant --- (In reply to Victor Ryzhykh from comment #50) > I do not know what to say. > It didn't work for me, but as soon as I made a symbolic link, it started > working. I already had the symlinks - except for libnvidia-allocator.so -> libnvidia-allocator.so.1, so I created that. I'm still seeing the segfault. This is with the 510.54 nv drivers. I don't think I've seen any mesa-loader errors that some have mentioned, only the kwin_wayland segfault described in the original report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 --- Comment #40 from S. Bryant --- (In reply to Stefan from comment #39) > Is maybe some Qt patch missing in KDE neon and openSUSE Tumblweed but not in > Arch? E.g. this one? > https://www.phoronix.com/scan.php?page=news_item=Qt-Wayland-NVIDIA-Thread That's quite possible. I'm not using Tumbleweed but Leap 15.3, with the additional KDE repositories from download.opensuse.org. I currently have libqt5-qtwayland-5.15.2+kde54-lp153.1.1.x86_64 installed (build date Feb 23 -- yesterday). I'm still seeing this bug. Does anybody know how to tell if the QtWayland patch is included? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450446] Multi-monitor setup messed up on every start.
https://bugs.kde.org/show_bug.cgi?id=450446 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #3 from S. Bryant --- I'm seeing this behaviour too, with Wayland and Plasma 5.24.1 on openSUSE Leap 15.3. I'm using a laptop with 2 external screens - both connected via display port connections. The laptop monitor (also the primary display) is always correct, but the other monitors often lose their settings. This morning, both external monitors were rotated 90 degrees (only one is physically rotated). This suggests that the name assignment is inconsistent; there was a similar problem under X11 a couple of years back. The position and scaling settings are similarly affected - which means that sometimes I log in and the mouse pointer is not only on a screen with no panel and default wallpaper, but that screen is positioned away from the others so it won't let the mouse go from one screen to the other. If it happens to match the right name to the monitor, all of these are correct (position, scaling, wallpaper, panel). This issue may be vaguely related to #385135 - the same fix seems to help: remove the whole `[ScreenConnectors]` section from `~/.config/plasmashellrc` and restart plasma. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 --- Comment #38 from S. Bryant --- (In reply to Zamundaaa from comment #32) > 510 is known to work: > https://www.reddit.com/r/linux_gaming/comments/su5dmb/kde_wayland_nvidia_issues/ > > Can you test putting "KWIN_DRM_USE_MODIFIERS=1" into /etc/environment, and > launching the session again after a reboot? Just to make sure that KWin > doesn't mis-detect the driver. Sorry about the delay in replying. I tried that with the G06 (510) drivers. The result was the same, except that this time the keyboard was also unresponsive after trying to log in. All of the people in the Reddit thread appear to have desktop GPUs. I'm using a Quadro T2000 Mobile. As mentioned the BIOS is set to turn off the hybrid graphics, although turning hybrid on (with G06/510) makes kwin_wayland segfault in libnvidia-egl-gbm.so. What DOES work with Wayland is this: enabling hybrid graphics and using the G05 (470) Nvidia drivers. This therefore uses the Intel GPU for primary rendering and 3D. The additional display connections (eg: on the dock) connect through the Nvidia chip - and they work fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 --- Comment #31 from S. Bryant --- (In reply to Zamundaaa from comment #23) > 470 is too old - you need gbm support, with driver 490 or newer I have installed the G06 (510.54) drivers and Plasma 5.24.1 on an HP laptop with an Intel i7. When the BIOS is set to "discrete" (Nvidia only), kwin_wayland segfaults as noted in this bug report. When set to "hybrid", kwin_wayland segfaults in libnvidia-egl-gbm.so. What GBM support do we need exactly? Do we know if there is any driver version that is working? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU and multiple screens: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 --- Comment #16 from S. Bryant --- It is perhaps worth noting: the NVidia drivers 510.47.03 are from their CUDA repository. The normal NVidia repository has 470.103.01. I reverted to the non-CUDA drivers, but it had no effect on the segfault. This matches what Kapil reported, so the behaviour is consistent across at least Neon and Leap. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU and multiple screens: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #15 from S. Bryant --- I'm not sure that the "multiple screens" part of the title is relevant. I'm seeing this on an HP laptop, with no additional screens connected. The laptop is set to use NVidia only (ie: hybrid is disabled). NVidia driver: 510.47.03 Mesa: 20.2.4 (from March 2021) Plasma: 5.24.0 Plasma Framework 5.90.0 Qt 5.15.2 + KDE patches This is with openSUSE Leap 15.3. I tried installing Mesa 21.3.6, but the same segfault occurs. Current workaround: use X11 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430036] konsole repeatedly losing no-toolbar setting
https://bugs.kde.org/show_bug.cgi?id=430036 S. Bryant changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 430826] Unable to rotate screen
https://bugs.kde.org/show_bug.cgi?id=430826 S. Bryant changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 422322] Session logout does not terminate all running user processes.
https://bugs.kde.org/show_bug.cgi?id=422322 --- Comment #16 from S. Bryant --- (In reply to David Edmundson from comment #12) > try putting: systemctl --user restart dbus.service > in an executable shell script in > > .config/plasma-workspace/shutdown > > and report back OK.. tried that. Unfortunately it stopped the logout procedure, and left X sort of hanging. The mouse moved, but there was nothing clickable, and no response to keyboard shortcuts (eg: Alt-F2 etc). I had to Ctrl-Alt-Bksp the X-Server, after which I noticed a number of programs were still hanging about (more than previously). I tried adding 'sleep 2' to the script before the restart command, but it made no difference. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 359651] Dangling user processes after KDE session crash
https://bugs.kde.org/show_bug.cgi?id=359651 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #12 from S. Bryant --- This is reproducible under openSUSE Leap 15.2 with Plasma 5.19.90 (prebuilt RPMs). I have two systems here. The list of dangling processes on each is not identical to each other. I tested a little: on one machine, killing only kio_http_cache_cleaner resulted in the other dangling processes exiting without needing to be killed. This is reproducible on that machine. On the other machine, some processes still remained after killing kio_http_cache_cleaner. I was able to trigger them exiting by killing kwin_x11 I think (didn't make a note). Perhaps they don't exit because they're still waiting for the bus. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 358709] TS video files are recognized as text files on remote slaves
https://bugs.kde.org/show_bug.cgi?id=358709 --- Comment #10 from S. Bryant --- > Determining the mimetype when multiple types have the same file suffix > involves downloading a portion of the file and looking for a magic sequence > of bytes. For obvious reasons we do not do that on non-local slave types as > we'd flood the network and server with a gazillion requests when entering a > directory with a gazillion files. While this is true, it may or may not be a problem, and may even be preferred behaviour. If I'm going across the Internet, it causes problems. However, when I access files on a local server across a gigabit LAN, I'd like the option to have the gazillion requests made. Dolphin already does this, based on file size. Preferences->General->Previews: "Skip previews for remote files above" (size). Would it not be possible to use the same setting to determine whether to perform magic number checking? At least, can data obtained for previews not also be used for magic numbers? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 358709] TS video files are recognized as text files and opened with text editors by default.
https://bugs.kde.org/show_bug.cgi?id=358709 --- Comment #6 from S. Bryant --- This is not quite fixed properly (Plasma 5.19.5 on openSUSE 15.2). Dolphin will now correctly differentiate for local files, but _not_ for 'sftp://' - it wants to open MPEG files with Linguist. The same is true for 'webdavs://'. I haven't tested other IO slaves. For 'file://', I notice that Typescript files are also correctly identified as plain text, despite sharing the same '*.ts' naming. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 422322] Session logout does not terminate all running user processes.
https://bugs.kde.org/show_bug.cgi?id=422322 S. Bryant changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #9 from S. Bryant --- > This report has become a mix of too many conflicting things. I must disagree. Given that a number of programs that used to terminate no longer do so, it seems reasonable to assume there is a common problem. That problem may be outside of ksmserver, however. It would be nice to narrow things down. Can you (David) confirm that no processes linger on your system? Here's a list of lingering programs after logout on this system (now with Plasma 5.19.2): /usr/lib/systemd/systemd --user (sd-pam) /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only /usr/lib/gvfs/gvfsd /usr/lib/gvfs/gvfsd-fuse /run/user/1026/gvfs -f -o big_writes /usr/lib/at-spi2/at-spi-bus-launcher /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 /usr/bin/kwin_x11 /usr/lib/dconf-service /usr/bin/baloo_file /usr/lib/bluetooth/obexd /usr/bin/ksystemstats /usr/bin/ksysguardd /usr/lib/GConf/2/gconfd-2 /usr/lib64/libexec/kf5/kio_http_cache_cleaner > If gvfs lingers, that lies with gvfs. Is that true for the others too? > If logout scripts are broken make a new report. Fair enough, let's ignore those in this bug report. Given that it's not possible to log in after logging out (unless the processes are manually killed), the "not a bug" status is incorrect. BTW: the original report mentioned shutdown waits for 2 minutes. This is after the display manager has exited - it's one of the system scripts waiting for user processes to terminate so partitions can be unmounted. It's not Plasma waiting for 2 minutes. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 422322] Session logout does not terminate all running user processes.
https://bugs.kde.org/show_bug.cgi?id=422322 --- Comment #5 from S. Bryant --- (In reply to David Edmundson from comment #3) > To test if it's related to another task does > > qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logoutAndShutdown > > shutdown the computer for you or logout? I tested on two machines. One shut down, the other only logged out. Both are 5.19.1. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 422322] Session logout does not terminate all running user processes.
https://bugs.kde.org/show_bug.cgi?id=422322 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #1 from S. Bryant --- I'm seeing this problem. A number of processes - including kwin_x11 - are hanging about after logout. I've also noticed that scripts in ~/.config/plasma-workspace/shutdown appear not to be run, as the processes they should kill are also still there after logout. Plasma 5.19.1, openSUSE 15.1 precompiled binaries. Seen on two separate machines. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 421821] New system monitor widgets are broken: "Error loading QML file..."
https://bugs.kde.org/show_bug.cgi?id=421821 --- Comment #6 from S. Bryant --- While the bug is fixed, the widgets have been rewritten and may not appear fixed. It may be necessary to tweak the settings to be able to see some of the graphics - including resizing the widget and/or removing the widget background (depending on theme). -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 420664] plasma-pk-update ignores proxyType=0 (in proxy configuration)
https://bugs.kde.org/show_bug.cgi?id=420664 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #1 from S. Bryant --- I'm also seeing this, using the pre-compiled openSUSE RPMs. I periodically get an 'Update Error' pop-up: ~~~ Download (curl) error for 'http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_15.1/repodata/repomd.xml': 
Error code: Connection failed
 Error message: Could not resolve proxy: HTTP_PROXY ~~~ The error can also be triggered by going to "Software Updates" (via the system tray) and clicking on the "Check for Updates" button. The same error can be seen when "Discover" is started. My user is set to not use a proxy; HTTP_PROXY is not set. The system default is also set to not use a proxy. Running the system update tool (in my case zypper) directly does not produce any such error. Versions: plasma5-pk-updates: 0.3.2 plasma5-workspace: 5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 421821] New system monitor widgets are broken: "Error loading QML file..."
https://bugs.kde.org/show_bug.cgi?id=421821 --- Comment #4 from S. Bryant --- I'm seeing output like this from 'plasmashell': file:///usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml:253: TypeError: Cannot read property 'value' of undefined -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 421821] New system monitor widgets are broken: "Error loading QML file..."
https://bugs.kde.org/show_bug.cgi?id=421821 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #1 from S. Bryant --- Possibly related: on openSUSE 15.1, those same widgets are completely blank. Other widgets work (eg: clock). This is with Plasma 5.18.90, Qt 5.14.1, using the openSUSE RPMs. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 421902] New: Package ksysguard5 cannot be installed on the current openSUSE Leap
https://bugs.kde.org/show_bug.cgi?id=421902 Bug ID: 421902 Summary: Package ksysguard5 cannot be installed on the current openSUSE Leap Product: ksysguard Version: 5.18.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: libksysguard Assignee: plasma-de...@kde.org Reporter: st...@bawue.de Target Milestone: --- SUMMARY Package ksysguard5 (and some others) cannot be installed on the current openSUSE Leap. STEPS TO REPRODUCE 1. On Leap 15.1, add the KDE repos; see: https://en.opensuse.org/SDB:KDE_repositories 2. zypper in ksysguard5-5.18.90 3. OBSERVED RESULT Problem: ksysguard5-5.18.90-lp151.264.1.x86_64 requires libprocesscore.so.9()(64bit), but this requirement cannot be provided not installable providers: libksysguard5-5.18.90-lp151.257.1.x86_64[KDE_Frameworks5] ... EXPECTED RESULT The installation succeeds. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: upgrading 5.18.5 -> 5.18.90 KDE Frameworks Version: Qt Version: 5.14.1 ADDITIONAL INFORMATION The previous package libksysguard5-5.18.5 includes /usr/lib64/libprocesscore.so.7. It appears that the 5.18.90 package does not include the required libprocesscore.so.9, and it's not available in any other package that I can find. This in turn means a number of other packages won't install either; in my case I'm left with a version mix and some broken functionality. I'm hoping this is just a minor error in the packaging process. What is the correct severity for uninstallable packages? Please adjust accordingly! -- 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 #333 from S. Bryant --- I have also noticed occasional reordering of some screens under [ScreenConnectors]. Make sure your primary screen is still set correctly. The fact that it can get unset or altered is possibly its own bug - but it affects ScreenConnectors entry 0 (which is the primary), and thus other entries will get reordered. Plasmashell will always put the primary first, which is fair enough. That's not to say that's the only problem. I've also seen my non-primary external screens on the laptop be forcibly reordered by the plasma shell, resulting in the panels/widgets/backgrounds coming up on the wrong monitor. FWIW, `xrandr --listmonitors` always seems to return the monitors in the same order, so it's not clear where the reordering is coming from. It should also be noted that the problem doesn't require plugging/unplugging of monitors to be triggered. Sometimes, but not often, it happens after a reboot and fresh login, where the hardware was not touched. I'm using NVidia's driver, in case it makes any difference. I've set the laptop to use NVidia only. I did get Optimus/Bumblebee working, but the Intel chip isn't connected to all of the ports, and Intel's virtual output has issues of its own with plug'n'play. Work doesn't have AMD laptops as an option. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 404405] Needs to unlock twice occasionally
https://bugs.kde.org/show_bug.cgi?id=404405 S. Bryant changed: What|Removed |Added CC||st...@bawue.de --- Comment #2 from S. Bryant --- This bug is over a year old, but I had not seen it in that year despite keeping relatively up to date. I have now updated to Plasma 5.18.2, and now this happens quite often. I've generally noticed the behaviour after suspending, but it is not reproducible after a short suspend. There may be a time factor involved. Possibly relevant: the first unlock screen has the user picture enclosed and cropped in a circle; the second does not. Perhaps the behaviour is caused by a bug in the lock screen theme. I'll see if I can test that; I was using "Breeze for openSUSE". -- You are receiving this mail because: You are watching all bug changes.
[kresources] [Bug 335355] Groupdav resources disappear when server not available
https://bugs.kde.org/show_bug.cgi?id=335355 --- Comment #3 from S. Bryant --- Further testing is not currently possible (by me), as I am unable to properly set up a groupdav resource - see #386985. It is possible this issue may have been resolved since Plasma 5 etc. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387657] Folders panel does not auto scroll vertically
https://bugs.kde.org/show_bug.cgi?id=387657 S. Bryant <st...@bawue.de> changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 358709] TS video files are recognized as text files and opened with text editors by default.
https://bugs.kde.org/show_bug.cgi?id=358709 S. Bryant <st...@bawue.de> changed: What|Removed |Added CC||st...@bawue.de --- Comment #4 from S. Bryant <st...@bawue.de> --- It's still a problem with shared-mime-info 1.6 too (Leap 42.2). I suspect very strongly that the shared MIME info is not the problem, but - assuming the magic numbers are correct - the problem is that the checking fails. What is worse: there is no way to change the default (Plasma5 5.8). If I remove "*.ts" from the linguist definition using System Settings, it is still there the next time I go in. The method used to override system MIME settings is not working. The default itself is also unreasonable: the number of users who want to watch videos/TV they've recorded will far outweigh the number who use Qt Linguist. That said, this point is irrelevant if magic number checking is working. -- 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 #222 from S. Bryant <st...@bawue.de> --- > tail -f /var/log/syslog | grep org.kde.KScreen The system log can be retrieved with the command 'journalctl', which writes it to stdout. Use '-b' with it to get only messages since the last boot. There's also '-h' and the man page for more info. That said, this is not the log you are looking for. Have a look at the file "$HOME/.xsession-errors-:0" instead. Adjust the name if you're on a different display number. Steve -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #62 from S. Bryant <st...@bawue.de> --- I've just installed the OpenSuse Leap 42.2 beta to test this (Kontact 5.1.3). The bug is still present - Kontact is not seeing calendar events from the server. I should point out that I'm not using Owncloud for this either, so no kitten-eating here. I'm using the caldav software from Synology that's on my diskstation (with the most up-to-date software). Thunderbird (Lightning) and Android (Davdroid) sync just fine here, and Synology list other software they've tested it with. The bug is not on the server side. -- 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 S. Bryant <st...@bawue.de> changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 361157] Akonadi does not work properly after Update to KDE FW 5.20, Plasma 5.6 and Qt5.6 on Opensuse Leap 42.1
https://bugs.kde.org/show_bug.cgi?id=361157 --- Comment #23 from S. Bryant <st...@bawue.de> --- I've upgraded to Plasma 5.7 (kontact5 16.04.2), and can confirm that the problem is still very much there. Akonadi (and by extension, all related applications) are still completely unusable on OpenSUSE 42.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor
https://bugs.kde.org/show_bug.cgi?id=344076 --- Comment #15 from S. Bryant <st...@bawue.de> --- I'm using Plasma 5.7 on OpenSUSE 42.1, and the problem is very much still there. The behaviour is now worse than it was before: unplugging the external screen leaves me without any visible panels. Plugging it back in puts one panel on top of the other. It is also apparent that panels really don't like to be moved from one screen to another. They hang on the screen edge and try to not go any further. The machine (a laptop) has hybrid Intel/Nvidia graphics, in case that makes any difference; it has Bumblebee setup. Running "xrandr -q" gives sane information about the currently connected screens. The information is updated when the external screen is plugged in or unplugged. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344076] Panels appear on top of each other when switching back to single-monitor
https://bugs.kde.org/show_bug.cgi?id=344076 S. Bryant <st...@bawue.de> changed: What|Removed |Added CC||st...@bawue.de --- Comment #8 from S. Bryant <st...@bawue.de> --- I'm using Plasma 5.6.2 on OpenSUSE Leap, and the problem is very much still there. When I connect my external screen to the laptop, the panel from the laptop screen may get moved to the external screen (or moved back if it was on the external screen). The panel on the external screen doesn't get moved. Connecting/disconnecting the external screen prior to X starting results in the same behaviour as doing so after logging in. Moving a panel to a specific display/position seemed to help for the remainder of that session, but the behavour reverted at the next login. Disconnecting the external screen leaves the panels where they are. While this bug's problem description could be counted as solved, the underlying issue is not. This problem was never correctly addressed in the previous generation of the software, as there are two opposing use cases: 1. having a panel that always remain visible, and automatically changes screen to do so (and returns to the user's preferred screen when it becomes available again). This is probably what a user expects when a single panel is in use; Windows also works like this. 2. having panels tied to specific screens, and being unreachable if that particular screen is not connected. My recommendations: On screen disconnect, there should be a check that at least one panel remains visible - if not, the first panel should be moved (but the lastScreen setting should not be altered). On screen connect, each panel should be moved to its 'lastScreen' if there is no panel already at that position on that screen. The lastScreen setting should only be updated when a panel is created or when the user explicitly moves the panel to a different screen. (Not sure if this is currently the case.) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361157] Akonadi does not work properly after Update to KDE FW 5.20, Plasma 5.6 and Qt5.6 on Opensuse Leap 42.1
https://bugs.kde.org/show_bug.cgi?id=361157 S. Bryant <st...@bawue.de> changed: What|Removed |Added CC||st...@bawue.de --- Comment #1 from S. Bryant <st...@bawue.de> --- Possibly related: After performing the same upgrade on Leap, I'm seeing "The Akonadi personal information management service is not operational" in any program that uses Akonadi, but I haven't seen this particular crash. It was working before the upgrade, and the Leap install was a fresh one, not an upgrade, so no generations old data to deal with. After running "akonadictl fsck" it's still "not operational". Running "akonadictl stop" doesn't stop anything. The MySQL instance was up - at least the Workbench connected to it (and complained about a MySQL version mismatch). If somebody can confirm that the combination FW5.20/Plasma5.6/Qt5.6 is known to work for Akonadi, we may be able to narrow it down to either a local configuration problem or a distribution-specific problem. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 353958] Akregator marks all unread feeds in list as read when set status to unread and click on one of the unread articles
https://bugs.kde.org/show_bug.cgi?id=353958 S. Bryant <st...@bawue.de> changed: What|Removed |Added CC||st...@bawue.de --- Comment #6 from S. Bryant <st...@bawue.de> --- This bug still exists with Akregator 5.1.1 in OpenSuse Leap 42.1. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #44 from S. Bryant <st...@bawue.de> --- Thanks. I had already tried that, but I tried again just to be sure: I deleted and re-added my diskstation (ie: webdav) address books and calendars. Kontact is not showing me any entries for either, even though I know there are entries on the server. I tried adding an event from Kontact 4.14.9 and from Kontact 5.1. Both events show up on my Android phone, but neither Kontact shows anything that came from the server. I therefore confirm that the bug is still present. @sparhawk: what version of libical is on your system? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #42 from S. Bryant <st...@bawue.de> --- I'm with Chris on this. I cannot reproduce what Metko wrote. I have a machine runnine OpenSuse Leap 42.1, and upgraded to Kontact 5.1 (kdepim-15.12.0-6.1, akonadi5-15.12.0-6.1 etc), and I still can't sync from my Diskstation (DSM 5.2) - which Android and Thunderbird both can. I note that OpenSuse Leap has the package libical1-1.0-9.7 installed, but no libical2. I assume that it doesn't contain Martin's fix. @Moritz: what version of libical is in your Kubuntu where this is working? Perhaps the lib dependency needs explicitly changing to version 2? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 S. Bryant <st...@bawue.de> changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
