[krdc] [Bug 338646] Login via rdp:// URL into Windows 8 when username=email address does not work from bookmark or history
https://bugs.kde.org/show_bug.cgi?id=338646 Stefan Radermacher changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460517] Plasma 5.26 completely breaks my multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=460517 --- Comment #7 from Stefan Radermacher --- > (In reply to Felix Miata from comment #5) > How would I best “disable automatic KScreen2 startup”? Never mind, I found it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460517] Plasma 5.26 completely breaks my multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=460517 --- Comment #6 from Stefan Radermacher --- (In reply to Felix Miata from comment #5) > It really doesn't matter whether this is dup'd to bug 450068 or bug 385135 > or some other "multi-screen support" bug. The fix for 450068 when it arrives > will be fixing multiple bugs that were made worse, or were unhelped by, or > were new in, 5.26. In the mean time, disable automatic KScreen2 startup and > manage displays with xrandr/arandr as best suits your own setup, if X > automagic display management doesn't work well enough on its own without > KScreen2 interference. How would I best “disable automatic KScreen2 startup”? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460517] Plasma 5.26 completely breaks my multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=460517 --- Comment #4 from Stefan Radermacher --- I'm not sure that this is really a duplicate of bug 450068. That bug already occurs in Plasma 5.24, but my problem is new with 5.26, previously this catastrophic failure did not occur. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 338646] Login via rdp:// URL into Windows 8 when username=email address does not work from bookmark or history
https://bugs.kde.org/show_bug.cgi?id=338646 --- Comment #8 from Stefan Radermacher --- (In reply to Justin Zobel from comment #7) > Thank you for reporting this bug in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! This bug seems to have been fixed in the meantime. I can no longer reproduce the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460517] Plasma 5.26 completely breaks my multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=460517 --- Comment #1 from Stefan Radermacher --- Additional info: I've tried this with a separate, new user account, the effects are the same. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460517] New: Plasma 5.26 completely breaks my multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=460517 Bug ID: 460517 Summary: Plasma 5.26 completely breaks my multi-monitor setup Classification: Plasma Product: kwin Version: 5.26.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: k...@zaister.de Target Milestone: --- SUMMARY *** After updating to Plasma 5.26 my system now becomes completely unusable after waking up from power save mode, or after switching the monitors that I use for multiple machines back to the KDE machine. Let me describe my screen setup. 1) My main screen is a 4K monitor at 3840×2160 resolution, connected to the DP-0 port. 2) My secondary screen is an HD monitor at 1920×1080 resolution, connected to HDMI-0. 3) My main screen is to the right of the secondary screen. Until Plasma 5.26 this has mostly worked, but with flaws: when the system wakes up or regains control of the monitors, windows on the main screen were moved around a certain distance to the left, overlapping both monitors. Some windows on the main screen that were maximized vertically were resized to the lesser height of the secondary screen. Rather annoying, but more or less workable. Now, with Plasma 5.26 this behavior has been replaced with something even worse. When the system wakes up now, the main monitor is completely deactivated (“NO SIGNAL”), and plasma tries to paint both screens on the secondary monitor. The screens overlap on the secondary monitor, and the screen that is too big scrolls around in the top half of the monitor when I move the mouse pointer. The system is completely unusable after that. By the way, after killing the X-Server and logging in again, the main monitor keeps being deactivated until I manually delete the folder ~/.local/share/kscreen. *** SOFTWARE/OS VERSIONS Linux/KDE Plasma: Plasma KDE Plasma Version: 5.26 KDE Frameworks Version: 5.99 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #72 from Stefan Radermacher --- (In reply to Nate Graham from comment #71) > That's a different thing and that behavior comes from KWin. It should also > have been fixed already in Plasma 5.26. Is there a bug I can comment on? I just installed the Plasma 5.26 beta to check this, but this actually breaks my system completely. When the monitors wake up, now the right monitor gets no signal at all, and Plasma tries to paint both screens on the left monitor, which leaves the system unusable until I kill X. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #70 from Stefan Radermacher --- > https://invent.kde.org/frameworks/kconfig/commit/ > 21e02655a78b5d241c35fd934f7665564420327c This patch helps with windows where they should open after they were closed. However, there is still another aspect of this bug. When I have windows open on the right-hand screen and the monitors go into sleep mode, once they wake again the positions and sizes of these windows are changed, everything is moved partly to the left, so that the windows straddle both monitors. For information purposes, I have two monitors, my main monitor is at 3940×2160 and to the right, the second monitor is at 1920×1080 and to the left. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 451560] New: Missing German localization in Plasma Taskbar
https://bugs.kde.org/show_bug.cgi?id=451560 Bug ID: 451560 Summary: Missing German localization in Plasma Taskbar Product: i18n Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: de Assignee: kde-i18n...@kde.org Reporter: k...@zaister.de Target Milestone: --- Missing German localization: If you right-click on a window button in the taskbar, the menu entry "More" (which leads to move, resize, maximize, etc.) is non localized. The menu entry is English "More", when it should be in German: "Mehr". SOFTWARE/OS VERSIONS Windows: – macOS: – Linux/KDE Plasma: Gentoo Linux Kernel 5.16.14 (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #50 from Stefan Radermacher --- (In reply to Lo from comment #49) I can confirm this exact behavior on my system. I think it started in early October, after I updated to the Plasma 5.23 beta. The workaround helps, but I hope this gets fixed soon. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 Stefan Radermacher changed: What|Removed |Added CC||k...@zaister.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 312027] Natural sorting should correctly sort associated numbered and unnumbered files
https://bugs.kde.org/show_bug.cgi?id=312027 --- Comment #4 from Stefan Radermacher --- (In reply to Justin Zobel from comment #3) > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. The behavior is still the same as originally reported. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 171743] Shortcut for moving between parts in Split View
https://bugs.kde.org/show_bug.cgi?id=171743 --- Comment #38 from Stefan Radermacher --- What version will this commit show up in? I can't find it in 16.08.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354823] Plasma crashes on multiscreen setup activation
https://bugs.kde.org/show_bug.cgi?id=354823 --- Comment #11 from Stefan Radermacher --- Yes, indeed this crash is fixed, but still something strange happens after my monitors ware up: all the windows on my right monitors are moved some distance to the left so that they start on the left monitor but still overlap the right monitor. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 --- Comment #48 from Stefan Radermacher --- It seems the upcoming Qt release fixes the plasmashell crash. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 --- Comment #46 from Stefan Radermacher --- Addendum: this is what I get after the crash in the terminal when I start plasmashell from there: requesting unexisting screen 1 requesting unexisting screen 1 requesting unexisting screen 1 requesting unexisting screen 1 KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/tmp/runtime-stefan/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 35 and type 'Read', disabling... KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/tmp/runtime-stefan/kdeinit5__0 Unable to start Dr. Konqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 --- Comment #45 from Stefan Radermacher --- I'm still getting plasmashell crashes everytime my monitors wake up from standby. KF 5.21, Plasma 5.6.4, Qt 5.6.0. Plasmashell is usually gone when they wake up, and my windows have been moved around. I do not get a Dr. Konqui message box anymore, though, the shell is just simply gone, so I can't post a trace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354823] Plasma crashes on multiscreen setup activation
https://bugs.kde.org/show_bug.cgi?id=354823 --- Comment #9 from Stefan Radermacher --- My previous post is missing the KDE Frameworks version: 5.21.0 My setup is two monitors where the right-side one is the main monitor connected via DisplayPort, while the right-side monitor is connected via DVI. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354823] Plasma crashes on multiscreen setup activation
https://bugs.kde.org/show_bug.cgi?id=354823 Stefan Radermacher changed: What|Removed |Added CC||k...@zaister.de --- Comment #8 from Stefan Radermacher --- I have this issue as well, with KDE Frameworks, Plasma 5.6.3, and Qt 5.6.0. I do not get any error dialog, but when my systgem wakes up, plasmashell is crashed. When I start plasmashell from the command line, this is logged; requesting unexisting screen 1 requesting unexisting screen 1 requesting unexisting screen 1 requesting unexisting screen 1 KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/tmp/runtime-stefan/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 35 and type 'Read', disabling... KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/tmp/runtime-stefan/kdeinit5__0 Unable to start Dr. Konqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 --- Comment #35 from Stefan Radermacher --- So, should I try again with the Qt patches I had installed when I made the original report? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 --- Comment #33 from Stefan Radermacher --- Interesting. Maybe then my original bug report should not be classified as a duplicate? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 --- Comment #31 from Stefan Radermacher --- Sure. To make sure I removed the Qt patch I mentioned in my earlier bugreport and to make sure I have your patch, I recompiled the kde-plasma/plasma-workspace-5.5.4 package again. Here's the start from the compile log, where it lists the patches used (plasma-workspace-5.5.4-crash-fix.patch is your patch): >>> Emerging (1 of 1) kde-plasma/plasma-workspace-5.5.4::gentoo * plasma-workspace-5.5.4.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking plasma-workspace-5.5.4.tar.xz to >>> /var/tmp/portage/kde-plasma/plasma-workspace-5.5.4/work >>> Source unpacked in /var/tmp/portage/kde-plasma/plasma-workspace-5.5.4/work >>> Preparing source in >>> /var/tmp/portage/kde-plasma/plasma-workspace-5.5.4/work/plasma-workspace-5.5.4 >>> ... * Applying plasma-workspace-5.4-startkde-script.patch ... [ ok ] * Applying plasma-workspace-tests-optional.patch ... [ ok ] * Applying patches from /etc/portage/patches/kde-plasma/plasma-workspace-5.5.4 ... * plasma-workspace-5.5.4-crash-fix.patch ... [ ok ] * User patches applied. >>> Source prepared. So I think this is covered. I have a new backtrace generated by simply turning off my main monitor and then turning it back on again, but it is too big to paste here, so you can find it here: https://paste.kde.org/pcdzif4s7 Regards Stefan -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 --- Comment #29 from Stefan Radermacher --- This patch does not seem to fix the problem I reported in bug 358919. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 358919] New: plasmashell crashes when external monitor is switched off and then on again
https://bugs.kde.org/show_bug.cgi?id=358919 Bug ID: 358919 Summary: plasmashell crashes when external monitor is switched off and then on again Product: KScreen Version: 5.5.4 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: libkscreen Assignee: se...@kde.org Reporter: k...@zaister.de I use a two-monitor setup, my primary monitor is connected via Displayport at a resolution of 3840x2160, and the secondary monitor via HDMI at 1280x1024. Installed software: KDE Frameworks 5.18.0, KDE Plasma 5.5.4, Qt 5.5.1 (with patch, see below), Nvidia proprietary driver 361.18 Symptom: when I turn off my primary monitor and later turn it back on again, plasmashell crashes and restarts. Previously, this also happened when I woke up my PC after monitor power management shut them down. This was fixed by a patch for Qt 5.5.1 as detailed in this upstream bugtracker: https://bugreports.qt.io/browse/QTBUG-42985. On the freenode channel #kde it was suggested that the crash after turning off the monitor is probably a KScreen bug. Reproducible: Always Steps to Reproduce: 1. Turn main monitor off 2. Turn main monitor on Actual Results: Plasmashell crashes, then restarts. Expected Results: Plasmashell does not crash. Here's a backtrace of the crash from DrKonqi: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f30712007c0 (LWP 20489))] Thread 9 (Thread 0x7f305de66700 (LWP 20492)): #0 0x7f306ba135bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f306f9b6ac2 in poll (__timeout=-1, __nfds=1, __fds=0x7f305de65d00) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x9159d0, cond=cond@entry=0x915a10, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459 #3 0x7f306f9b872f in xcb_wait_for_event (c=0x9159d0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693 #4 0x7f305fdb93d9 in QXcbEventReader::run (this=0x921d80) at qxcbconnection.cpp:1264 #5 0x7f306c0f30d2 in QThreadPrivate::start (arg=0x921d80) at thread/qthread_unix.cpp:331 #6 0x7f306b224434 in start_thread (arg=0x7f305de66700) at pthread_create.c:334 #7 0x7f306ba1c6dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f305693c700 (LWP 20504)): #0 g_mutex_unlock (mutex=0x7f305990) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gthread-posix.c:1350 #1 0x7f306787a4d0 in g_main_context_prepare (context=context@entry=0x7f305990, priority=priority@entry=0x7f305693bcb0) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3440 #2 0x7f306787ae7b in g_main_context_iterate (context=context@entry=0x7f305990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3820 #3 0x7f306787b05c in g_main_context_iteration (context=0x7f305990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7f306c2e355b in QEventDispatcherGlib::processEvents (this=0x7f3058c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f306c29553a in QEventLoop::exec (this=this@entry=0x7f305693bde0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f306c0eeab4 in QThread::exec (this=this@entry=0xa04b70) at thread/qthread.cpp:503 #7 0x7f306e888675 in QQmlThreadPrivate::run (this=0xa04b70) at qml/ftw/qqmlthread.cpp:141 #8 0x7f306c0f30d2 in QThreadPrivate::start (arg=0xa04b70) at thread/qthread_unix.cpp:331 #9 0x7f306b224434 in start_thread (arg=0x7f305693c700) at pthread_create.c:334 #10 0x7f306ba1c6dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f304b6ce700 (LWP 20505)): #0 0x7f306ba135bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f306787af4c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f3044002e70, timeout=, context=0x7f3044000990) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f3044000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3835 #3 0x7f306787b05c in g_main_context_iteration (context=0x7f3044000990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7f306c2e355b in QEventDispatcherGlib::processEvents (this=0x7f30440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f306c29553a in QEventLoop::exec (this=this@entry=0x7f304b6cdde0,
