[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 Martin Riethmayer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #15 from Martin Riethmayer --- This is no longer happening in Plasma 5.8.0, Qt 5.7.0. Marking as resolved fixed - thanks for your work on MultiScreen-Issues! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 Martin Riethmayer changed: What|Removed |Added Version|5.6.95 |5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #8 from Martin Riethmayer --- Still happening in neon-useredition-20160705-0929-amd64 and also openSUSE Tumbleweed (5.7.0) It has improved slightly as long as I don't turn of the primary monitor. However, when I turn off primary, everything is still misconfigured when turning it back on again: - panels gone or on the wrong screen - second user's configuration (not logged in at that time) scrambled: sometimes with a black background, no panels, I can see the mouse but can't right click, sometimes only the panels are misconfigured, sometimes - in the VM, monitors are still set to clone instead of side-by-side after off/on Unfortunately, http://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/ did not solve this -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365467] New: Positioning changes in display configuration need to be applied twice
https://bugs.kde.org/show_bug.cgi?id=365467 Bug ID: 365467 Summary: Positioning changes in display configuration need to be applied twice Product: KScreen Version: 5.7.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: rip...@freakmail.de The KScreen KCM somehow does and at the same time doesn't recognize changing the position in a multiscreen setup. If I change the Display Configuration and hit "Apply" the changes are indeed applied, but the "Apply"-Button remains active, leaving the KCM prompts for "Unsaved changes" and the "*" in the titlebar remains. Note: This is not true for all parameter, e.g. changing the resolution of one monitor on a multiscreen setup, the "Apply"-Button works as expected. Reproducible: Always Steps to Reproduce: 1. Open the "Display and Configuration" KCM 2. Change the positioning of a multiscreen setup (e.g. from "left-of" to "right-of") 3. Hit "Apply" Actual Results: The changes are applied but the "Apply"-Button stays active, KCM thinks there's changed information. A second hit on "Apply" works. Expected Results: The "Apply"-Button should be disabled and the KCM shouldn't think there are any more changes to be applied I don't know if there are other properties except changing the positioning of a multiscreen-setup where this bug appears as well. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #10 from Martin Riethmayer --- It's getting a bit weird now - latest KDE neon dev stable with apt-get update and apt-get upgrade: The initial bug (kind of) persists: after xrandr --off and xrandr --auto of VGA-2 (in the VirtualBox VM) my screen configuration is broken. I had set an empty panel on screen two, now both panels are shown on both screens, the konsole-window is shown on both screens (and in sync when typing) BUT the mouse courser is in only one screen and can be moved as if they are side-by-side. Again: everything (including the KCM kscreen config) appears to have the two screens in "Clone" mode - except the mouse courser which I can move from left to right screen and is only shown in one screen. I also noticed that the resize-handle of the mouse is appearing a couple of pixels to the right and to the bottom of where they should actually appear (I'll attach a screenshot). If I update the config in the KCM the panels appear in the correct screen. Note: xrandr can only turn off VGA-2 in this snapshot, trying to turn off VGA-1 has an effect in the KCM only (where the resolution of VGA-1 is increased and the display is labelled to be disabled (i.e. the "Enabled" checkbox is off)) but the screen actually stays active. I'll also attach the output of "kscreen-console bug" -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #11 from Martin Riethmayer --- Created attachment 100164 --> https://bugs.kde.org/attachment.cgi?id=100164&action=edit Screenshot KDE Neon 2016-07-19 "Cloned" desktop (except mouse cursor) and resize-handle misplaced -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #12 from Martin Riethmayer --- Created attachment 100165 --> https://bugs.kde.org/attachment.cgi?id=100165&action=edit output of kscreen bug (2016.07-09) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #14 from Martin Riethmayer --- Created attachment 100166 --> https://bugs.kde.org/attachment.cgi?id=100166&action=edit Outpu of kscreen-console bug and kscreen config files before, during and after -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background
https://bugs.kde.org/show_bug.cgi?id=367893 --- Comment #2 from Martin Riethmayer --- Created attachment 101107 --> https://bugs.kde.org/attachment.cgi?id=101107&action=edit Loading this file with background parser enabled crashes KDevelop for me Sorry for the late reply, I was now able to reproduce the issue, I've attached the file that is causing the freeze / crash. As soon as I open that file, KDevelopkdev increases its memory usage from ca 100MB to 14.6 GB (which is probably the maximum available at that time) if the background parser is active. If I deactivate the background parser, everything is working as expected. This is on KDevelop 5.0.0, KDE FW 5.25.0, Qt 5.6.1, KDE-Plasma 5.74, Kernel 4.7.2-1-default, 64-bit xcb windowing system, Intel Core i7-4770R CPU@3.2 GHz, 16 GB RAM. Two more observations: If I open the file with disabled background parser, then enable the parser and immediately quit KDevelop (CTRL+Q), the application window disappears, but the process is still active and will grab all RAM until it crashes. You can actually watch the RAM usage go up in the system monitor. After KDevelop crashes, there's usually (but not every time) still some kind of zombie-process in the system monitor. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367893] New: KDevelop crashes - probably while parsing JS-file in background
https://bugs.kde.org/show_bug.cgi?id=367893 Bug ID: 367893 Summary: KDevelop crashes - probably while parsing JS-file in background Product: kdevelop Version: 5.0.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rip...@freakmail.de Application: kdevelop (5.0.0) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.7.1-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160822) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was editing some PHP and XSL files without problems. When I opened a (simple) JS file and switched to another tab, the entire computer began to "stutter" (e.g. mp3 playback with Amarok with gaps). A few seconds later, KDevelop crashed. I've turned of the background parser and have again opende a couple of php and XSL files and a JS file, this time, no crash occured . I did not do excessive testing if this is a coincidence This is on a freshly installed Opensuse Tumbleweed, KDevelop 5.0.0, KF 5.24, Qt 5.6.1, xcb windowing system -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f90640d2900 (LWP 27228))] Thread 16 (Thread 0x7f8ff28b4700 (LWP 27683)): #0 0x7f9060dafa7d in read () from /lib64/libc.so.6 #1 0x7f9059dafd00 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9059d6cb26 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9059d6cff4 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f9059d6d16c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f90616dfaeb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f906168776a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f90614ad3b3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f905efb66df in ?? () from /usr/lib64/libKDevPlatformLanguage.so.10 #9 0x7f90614b22d8 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7f905a9f8474 in start_thread () from /lib64/libpthread.so.0 #11 0x7f9060dbc3ed in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f8ff3fff700 (LWP 27349)): #0 0x7f905a9fe09f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f90614b318b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f9055e9aec0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f9055e9f068 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f9055e9cf09 in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f90614b22d8 in ?? () from /usr/lib64/libQt5Core.so.5 #15 0x7f905a9f8474 in start_thread () from /lib64/libpthread.so.0 #16 0x7f9060dbc3ed in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f9010b94700 (LWP 27348)): #0 0x7f905a9fe09f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f90614b318b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f9055e9aec0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f9055e9f068 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #
[kwin] [Bug 354115] One of the screens stays blank after energy saving mode
https://bugs.kde.org/show_bug.cgi?id=354115 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #14 from Martin Riethmayer --- Sorry for commenting on a "Resolved" issue, this is mainly to provide a solution that worked for me: xset dpms force off did turn all monitors blank, moving the mouse then woke them all up. "xset dpms force on" did not work. Should this be reported upstream? Where? Additional info: I sometimes have the same problem, but I'm on Kubuntu 14.04 LTS, KDE Platform Version 4.13.3 Version === KWin version: 4.11.11 KDE SC version (runtime): 4.13.3 KDE SC version (compile): 4.13.2 Qt Version: 4.8.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #5 from Martin Riethmayer --- This is still happening with the latest versions of kscreen in OpenSUSE Factory from GIT: kscreen5: 5.6.90git~20160613T210802~b0e02c9-12.1 libkscreen2-plugin: 5.6.90git~20160614T154913~2792f55-16.1 Steps to reproduce: 1.) Start a VirtualBox VM with up-to-date OpenSUSE factory and two monitors for the VM 2.) Place the monitors side-by-side in KCM 3.) Go to a konsole and run "xrandr --output VGA-2 --off", then "xrandr --output VGA-2 --auto" Expected result: The monitors should be configured side-by-side again Actual result: The monitors are in "clone" mode Reproducible: Always I'll attach the kscreen log. I've set kscreen.*=true in qtdebugging.ini and restarted kded5. I'll also attach the config files after each step, e.g. the initial state is "xyz.0", after applying the side-by-side config once in KCM "xyz.1", second apply is "xyz.2", xrandr off is "xyz.3" and xrandr auto is "xyz.4" At the time of restarting kded5, my monitors where in "clone" mode (config file ".0"), so I went to the KCM and positioned them side-to-side. After hitting "Apply" once, the config is saved twice (e.g. the log was written up to and including line 16) (config file ".1") The KCM still believes that there are changes to apply, so after hitting "Apply" for the second time, the log gets written up to and including line 24. (config file ".2") After running "xrandr --output VGA-2 --off", log is written including line 32 (config file ".3") After running "xrandr --output VGA-2 --auto", log is written until the last line. (config file ".4") I noted that the filename of the kscreen config is always the same - I don't know if this is the way it's supposed to be? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #6 from Martin Riethmayer --- Created attachment 99544 --> https://bugs.kde.org/attachment.cgi?id=99544&action=edit Log of kded5 debug output, config files of kscreen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #7 from Martin Riethmayer --- This is also happening in KDE Neon ( neon-devedition-gitstable-20160619-1048-amd64.iso ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 Martin Riethmayer changed: What|Removed |Added Platform|openSUSE RPMs |Neon Packages Version|5.6.2 |5.6.95 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358283] VD: Make user-added plasmoid icons the same size of the system tray icons
https://bugs.kde.org/show_bug.cgi?id=358283 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 331963] KDE Telepathy rename contact - no way to change contact name and avatar
https://bugs.kde.org/show_bug.cgi?id=331963 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #8 from Martin Riethmayer --- Would it be possible to have a temporary solution with some kind of "merge" strategy? It's been more than 2 years now for (quote) "One of the most requested features in KDE Telepathy" and this is still not possible. I trust that the overall design and pairing with the PIM-stack is a really good idea in the long term, however it's blocking the development of important features, it seems. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] New: Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 Bug ID: 361750 Summary: Multi-Screen configuration lost Product: plasmashell Version: 5.6.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: rip...@freakmail.de CC: plasma-b...@kde.org After powering off and on one monitor, the configuration is completely broken Reproducible: Always Steps to Reproduce: 1. Set-up a Multi-Monitor environment: 2 screens (1xHDMI / 1xDVI->HDMI, monitors next to each other) 2. Turn off the left monitor 3. Turn the left monitor back on again Actual Results: The off/on Monitor does not regain it's setup Expected Results: The Multi-Monitor setup should not change in any way. If it is possible (which I don't know) I'd prefer that there'd be no change at all just because a monitor powers off - only change something if a monitor physically gets disconnected, though I'm afraid that this is probably impossible to distinguish. At least there should not be any change if monitors are powered of by Powerdevil or other system-energy-saving tools (I believe that this happened to me before, but I'm not 100% sure). This is most likely related to https://bugs.kde.org/show_bug.cgi?id=356225 but I'm not on a Laptop and I'm not physically unplugging a monitor (i.e. pulling a cable) but simply powering off/on. xrandr -q is identical after powering off/on one of the monitors (so xrandr actually get's it right) - could it be some timing issue / race condition? Additionally, after going to systemsettings and deactivating / re-activating the "broken" monitor, I sometimes do not get my panels back on the original spot. I'm attaching some files in the next comment(s) (it's not possible to make attachments in the original report, is it?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #1 from Martin Riethmayer --- Created attachment 98391 --> https://bugs.kde.org/attachment.cgi?id=98391&action=edit diff output of complete home directory after powering off/on one of the monitors I copied my complete home directory before powering off one of the monitors. Powered off one monitor, powered it back on and made a diff of the backup-home-directory and my new "live" home directory. Only .xsession-errors changed, which you can see in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #2 from Martin Riethmayer --- Created attachment 98392 --> https://bugs.kde.org/attachment.cgi?id=98392&action=edit xrandr -q output before AND after powering off/on There's no change in the output of xrandr -q before and after powering one monitor off, then on again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #3 from Martin Riethmayer --- Created attachment 98393 --> https://bugs.kde.org/attachment.cgi?id=98393&action=edit Output of hwinfo (just in case, I don't think this actually is a hardware issue) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #4 from Martin Riethmayer --- One more thing (sorry, this just happened and I wasn't aware of this before): My system is a two-user-system. If I turn off one monitor while being logged in as user1, the configuration of user2 (not logged in at that moment) is changed and not restored to the correct settings. Reproducible: I think it's always, but it's a bit harder to test Steps to reproduce: 1.) Set up two (or more) users 2.) Log in as user1 3.) Turn off one monitor, than on again 4.) Log off as user1, log on as user2 Expected results: The configuration of user2 should not have changed in any way Actual result: The multi-monitor setup of user2 is broken -- You are receiving this mail because: You are watching all bug changes.
