Created attachment 131906 [details] Monitor configuration that gets reseted SUMMARY I have 2 monitors. 1st main monitor. 2nd is on the right in portrait mode. I setup my monitors like in set.png. But everytime I logout and login it comes back to default(two monitors in landscape next to each other). STEPS TO REPRODUCE 1. Login 2. Setup monitors like in set.png 3. Logout 4. Log back in OBSERVED RESULT Settings are not saved, monitors are back to default EXPECTED RESULT Settings are saved and monitors after relogin should be like in set.png SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74 Qt Version: 5.15.1 (Arch linux latest KDE-Unstable) ADDITIONAL INFORMATION
Can you include output of kscreen-console config please
START: Requesting Config kscreen.kwayland: Loading Wayland backend. Received config. Took 15 milliseconds Screen: maxSize: QSize(64000, 64000) minSize: QSize(0, 0) currentSize: QSize(3840, 1615) ----------------------------------------------------- Id: 1 Name: "Goldstar Company Ltd HDMI-A-2-LG IPS FULLH" Type: "HDMI" Connected: true Enabled: true Primary: false Rotation: 1 Pos: QPoint(0,535) MMSize: QSize(480, 270) FollowPreferredMode: false Size: QSize(-1, -1) Scale: 1 Clones: None Mode: "0" Preferred Mode: "0" Preferred modes: ("0") Modes: "0" "1920x1080@60" QSize(1920, 1080) 60 "10" "1280x800@60" QSize(1280, 800) 59.91 "11" "1152x864@75" QSize(1152, 864) 75 "12" "1280x720@60" QSize(1280, 720) 60 "13" "1280x720@60" QSize(1280, 720) 60 "14" "1280x720@60" QSize(1280, 720) 59.94 "15" "1280x720@50" QSize(1280, 720) 50 "16" "1024x768@75" QSize(1024, 768) 75.029 "17" "1024x768@60" QSize(1024, 768) 60.004 "18" "800x600@75" QSize(800, 600) 75 "19" "800x600@60" QSize(800, 600) 60.317 "2" "1920x1080@60" QSize(1920, 1080) 59.94 "20" "720x576@50" QSize(720, 576) 50 "21" "720x480@60" QSize(720, 480) 60 "22" "720x480@60" QSize(720, 480) 60 "23" "720x480@60" QSize(720, 480) 59.94 "24" "720x480@60" QSize(720, 480) 59.94 "25" "640x480@75" QSize(640, 480) 75 "26" "640x480@60" QSize(640, 480) 60 "27" "640x480@60" QSize(640, 480) 59.94 "28" "640x480@60" QSize(640, 480) 59.94 "29" "720x400@70" QSize(720, 400) 70.082 "3" "1920x1080@50" QSize(1920, 1080) 50 "4" "1680x1050@60" QSize(1680, 1050) 59.883 "5" "1400x1050@60" QSize(1400, 1050) 59.948 "6" "1600x900@60" QSize(1600, 900) 60 "7" "1280x1024@75" QSize(1280, 1024) 75.025 "8" "1280x1024@60" QSize(1280, 1024) 60.02 "9" "1440x900@60" QSize(1440, 900) 59.901 EDID Info: Unavailable ----------------------------------------------------- Id: 2 Name: "Philips Consumer Electronics Company DVI-D-1-PHL 273V5/UK5140408069" Type: "DVI" Connected: true Enabled: true Primary: true Rotation: 8 Pos: QPoint(1920,0) MMSize: QSize(600, 340) FollowPreferredMode: false Size: QSize(-1, -1) Scale: 1 Clones: None Mode: "0" Preferred Mode: "0" Preferred modes: ("0") Modes: "0" "1920x1080@60" QSize(1920, 1080) 60 "1" "1680x1050@60" QSize(1680, 1050) 59.883 "10" "720x400@70" QSize(720, 400) 70.082 "2" "1280x1024@60" QSize(1280, 1024) 60.02 "3" "1440x900@60" QSize(1440, 900) 59.901 "4" "1280x800@60" QSize(1280, 800) 60 "5" "1280x720@60" QSize(1280, 720) 60 "6" "1024x768@60" QSize(1024, 768) 60.004 "7" "800x600@60" QSize(800, 600) 60.317 "8" "640x480@67" QSize(640, 480) 66.667 "9" "640x480@60" QSize(640, 480) 59.94 EDID Info: Unavailable This is with monitors setup currently.
Created attachment 131907 [details] wayland debug I setup debug. Logout, login, it showed default monitor setup, crashed randomly(probably unrelated). Log back again and uploaded the log.
Heh; KCrash: Attempting to start /usr/bin/kded5 That's what's wrong, kded is crashing. This could be entirely unrelated, but we need to fix that. Do you have the sad face icon in the panel when plasma starts? If you manually invoke kded5 does that work?
[fatino@greyhill ~]$ kded5 bluedevil: Created org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: No such interface “” org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon KCrash: Attempting to start /usr/bin/kded5 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kded5 path = /usr/bin pid = 11647 KCrash: Arguments: /usr/bin/kded5 KCrash: Attempting to start /usr/lib/drkonqi QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... bluedevil: Created kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: No such interface “” org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon [1]+ Zatrzymano kded5
(gdb) r Starting program: /usr/bin/kded5 [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7ffff1449640 (LWP 11851)] bluedevil: Created [New Thread 0x7fffeb664640 (LWP 11852)] [New Thread 0x7fffeae63640 (LWP 11853)] org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: No such interface “” org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon [Detaching after fork from child process 11854] [New Thread 0x7fffea090640 (LWP 11856)] [New Thread 0x7ffff3982280 (LWP 11857)] process 11847 is executing new program: /usr/bin/pidof warning: Probes-based dynamic linker interface failed. Reverting to original interface. [LWP 11857 exited] [New LWP 11858] process 11847 is executing new program: /usr/bin/pidof warning: Probes-based dynamic linker interface failed. Reverting to original interface. [LWP 11858 exited] [New LWP 11859] process 11847 is executing new program: /usr/bin/pidof warning: Probes-based dynamic linker interface failed. Reverting to original interface. [LWP 11859 exited] [New LWP 11860] process 11847 is executing new program: /usr/bin/pidof warning: Probes-based dynamic linker interface failed. Reverting to original interface. [LWP 11860 exited] [New LWP 11861] process 11847 is executing new program: /usr/bin/pidof warning: Probes-based dynamic linker interface failed. Reverting to original interface. [LWP 11861 exited] [New LWP 11862] process 11847 is executing new program: /usr/bin/pidof warning: Probes-based dynamic linker interface failed. Reverting to original interface. [LWP 11862 exited] [New LWP 11863] process 11847 is executing new program: /usr/bin/pidof warning: Probes-based dynamic linker interface failed. Reverting to original interface. [LWP 11863 exited] [New LWP 11864] process 11847 is executing new program: /usr/bin/pidof warning: Probes-based dynamic linker interface failed. Reverting to original interface. [LWP 11864 exited] [New LWP 11847] --Type <RET> for more, q to quit, c to continue without paging--bt Thread 14 "kded5" received signal SIGSEGV, Segmentation fault. 0x00007fffea171e66 in ?? ()
[fatino@greyhill ~]$ valgrind kded5 ==12114== Memcheck, a memory error detector ==12114== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==12114== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==12114== Command: kded5 ==12114== bluedevil: Created --12114-- WARNING: unhandled amd64-linux syscall: 315 --12114-- You may be able to write your own handler. --12114-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --12114-- Nevertheless we consider this a bug. Please report --12114-- it at http://valgrind.org/support/bug_reports.html. org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: No such interface “” org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon ==12114== Warning: noted but unhandled ioctl 0x5441 with no size/direction hints. ==12114== This could cause spurious value errors to appear. ==12114== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==12114== Conditional jump or move depends on uninitialised value(s) ==12114== at 0xF2899BB: ??? ==12114== by 0xD979817: ??? ==12114== ==12114== Syscall param waitid(infop) points to unaddressable byte(s) ==12114== at 0x6056D5D: syscall (in /usr/lib/libc-2.32.so) ==12114== by 0x5A74277: ??? (in /usr/lib/libQt5Core.so.5.15.1) ==12114== by 0x5A5823B: ??? (in /usr/lib/libQt5Core.so.5.15.1) ==12114== by 0x116DFD27: ??? (in /usr/lib/qt/plugins/kf5/kded/gtkconfig.so) ==12114== by 0x116EE95F: ??? (in /usr/lib/qt/plugins/kf5/kded/gtkconfig.so) ==12114== by 0x116EE91F: ??? (in /usr/lib/qt/plugins/kf5/kded/gtkconfig.so) ==12114== by 0x5D752CF: ??? (in /usr/lib/libQt5Core.so.5.15.1) ==12114== by 0xDAB772F: ??? ==12114== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==12114== ==12114== Invalid read of size 8 ==12114== at 0x116E9E66: ??? (in /usr/lib/qt/plugins/kf5/kded/gtkconfig.so) ==12114== by 0x1F7FFFFFFF: ??? ==12114== by 0xEFF838F: ??? ==12114== by 0x7: ??? ==12114== by 0x1F000004ED: ??? ==12114== by 0x74447B50E5A96DFF: ??? ==12114== by 0x1101: ??? ==12114== by 0xDC7720F: ??? ==12114== by 0xEF2583F: ??? ==12114== by 0x1FFEFFFD57: ??? ==12114== by 0x1FFEFFFE97: ??? ==12114== by 0x1FFEFFFDCF: ??? ==12114== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==12114== KCrash: Attempting to start /usr/bin/kded5 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kded5 path = /usr/bin pid = 12114 KCrash: Arguments: /usr/bin/kded5 KCrash: Attempting to start /usr/lib/drkonqi QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... bluedevil: Created org.kde.libkbolt: Failed to connect to Bolt manager DBus interface: No such interface “” org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP [1]+ Zatrzymano valgrind kded5
Thread 1 (Thread 0x7f3c2aa8f280 (LWP 19441)): [KCrash Handler] #4 KPluginFactory::create<KDecoration2::Decoration>(QObject*, QList<QVariant> const&) (args=..., parent=0x0, this=0x0) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:543 #5 KDecoration2::DummyDecorationBridge::DummyDecorationBridge(QString const&, QObject*) (this=0x555998386fb0, decorationTheme=..., parent=<optimized out>) at /usr/src/debug/kde-gtk-config-5.19.90/kded/kwin_bridge/dummydecorationbridge.cpp:57 #6 0x00007f3c17fef6d0 in StandardDecorationPainter::StandardDecorationPainter(QString const&) (this=0x55599809c010, themeName=...) at /usr/src/debug/kde-gtk-config-5.19.90/kded/kwin_bridge/decorationpainter.h:18 #7 0x00007f3c17fef08a in DecorationPainter::fromThemeName(QString const&) (themeName=...) at /usr/src/debug/kde-gtk-config-5.19.90/kded/kwin_bridge/decorationpainter.cpp:24 #8 0x00007f3c17fe79b9 in ConfigValueProvider::windowDecorationsButtonsImages() const (this=0x7fff66f7e168) at /usr/src/debug/kde-gtk-config-5.19.90/kded/configvalueprovider.cpp:194 #9 0x00007f3c17fe279e in GtkConfig::setWindowDecorationsAppearance() const (this=0x7f3c20099390) at /usr/include/qt/QtCore/qscopedpointer.h:116 #10 GtkConfig::setWindowDecorationsAppearance() const (this=0x7f3c20099390) at /usr/src/debug/kde-gtk-config-5.19.90/kded/gtkconfig.cpp:148 #11 0x00007f3c17fe30eb in GtkConfig::applyAllSettings() const (this=this@entry=0x7f3c20099390) at /usr/src/debug/kde-gtk-config-5.19.90/kded/gtkconfig.cpp:192
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
David, could you please clarify which additional information is needed? Otherwise, please reset the status.
New information was added; changing status for investigation.
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26? If it is, please change the status to CONFIRMED when replying. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot!