[plasma-systemmonitor] [Bug 486156] New: System Monitor will randomly crash
https://bugs.kde.org/show_bug.cgi?id=486156 Bug ID: 486156 Summary: System Monitor will randomly crash Classification: Applications Product: plasma-systemmonitor Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: devguy...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I've am seeing odd random crash, something when I am using it, othertime it just sitting idle and then disappears. I just notice this bug when I opened it to kill my multiple Brave browser session, and then after a little while it just disappeared. This is on a freshly install openSUSE TW with KDE desktop. STEPS TO REPRODUCE 1. Open System Monitor 2. Select "Processes" 3. Search for some process, kill a process. OBSERVED RESULT Some time randomly will crash and just disappear. EXPECTED RESULT Should always be running. Operating System: openSUSE Tumbleweed 20240423 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486153] New: monitor goes blank or to sleep after being turned on in dual monitor setup
https://bugs.kde.org/show_bug.cgi?id=486153 Bug ID: 486153 Summary: monitor goes blank or to sleep after being turned on in dual monitor setup Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I have a dual monitor setup. When I lock my system and turn off both monitor using power, then later turn them on and log back in, one of my monitor will go back to sleep as if it's not getting a signal. It just goes black and this is getting supper annoying. In the past I just had to turn the monitor off and on, then move the mouse cursor into the monitor area and move it around for a few seconds to prevent it from going back to sleep. Well today no suck luck it just kept turning off and I was unable to use the monitor. I was forced to reboot for this bug to go away. I don't know when this bug showed up, because before I just left this monitor always on. It's definite not lose cable, because then it would continue to happen after a fresh reboot, but it never gose to sleep. If this was my only single primary monitor, I would not be able to use my system. STEPS TO REPRODUCE 1. Need dual monitor setup 2. Lock computer 3. Turn both monitor off using their power button. 4. Later after sometime, turn both monitor on. 5. Log back in. OBSERVED RESULT One of the monitor will come out of sleep and then goes back to sleep. EXPECTED RESULT Both monitor stay awake. Operating System: openSUSE Tumbleweed 20240423 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 ## Other Info The monitor model going to sleep: HP L2445m -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484205] New: Login Screen Focus goes to wrong monitor
https://bugs.kde.org/show_bug.cgi?id=484205 Bug ID: 484205 Summary: Login Screen Focus goes to wrong monitor Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 167586 --> https://bugs.kde.org/attachment.cgi?id=167586=edit display setting showing primary monitor. SUMMARY I have a dual monitor setup, the monitor selected as primary never gets login focus, it always goes to the other monitor. STEPS TO REPRODUCE 1. Need dual monitor setup 2. Select one as the primary (switch them up) 3. Logout, login back in. OBSERVED RESULT Monitor selected as primary never gets login focus. EXPECTED RESULT Primary montir should have login focus. Operating System: openSUSE Tumbleweed 20240320 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483632] Spectacle shortcut "Capture win under cursor" shows crosshair
https://bugs.kde.org/show_bug.cgi?id=483632 --- Comment #3 from Rajinder Yadav --- One additional thing I like to add. Imagine the window is changing quickly and you want to quickly capture the changes. With just the hotkey, I can press it quickly multiple times. The "new way" I would have to press the hotkey and mouse click multiple times to try to keep up with changes. This is really cumbersom and you would not be able to capture rapidly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483632] Spectacle shortcut "Capture win under cursor" shows crosshair
https://bugs.kde.org/show_bug.cgi?id=483632 --- Comment #2 from Rajinder Yadav --- (In reply to Titouan Camus from comment #1) > I can reproduce. I am not sure it is a bug though, as it seems much more > convenient to me this way. This is not how it use to work before, also now I have to do an additional mouse click and is not efficent. Before I just move the mouse cursor over a window and use my hotkey. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483630] Pressing escape key doesn't close App launcher
https://bugs.kde.org/show_bug.cgi?id=483630 Rajinder Yadav changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Rajinder Yadav --- Seem like the previous update messed up the assigned shortcut for the "ESC" key and set it to the system toolbar. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483632] New: Spectacle shortcut "Capture win under cursor" shows crosshair
https://bugs.kde.org/show_bug.cgi?id=483632 Bug ID: 483632 Summary: Spectacle shortcut "Capture win under cursor" shows crosshair Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY When using the shortcut to capture screen under cursor, a crosshair showup and an additional click is required. Before the window under the cursor was immediately capture and saved by Spectacle. STEPS TO REPRODUCE 1. Set shortcut for Spectacle "Capture win under cursor" 2. Place cursor over a window 3. Press shortcut OBSERVED RESULT Crosshair shows up. EXPECTED RESULT Capture image of window under cursor. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240313 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483630] New: Pressing escape key doesn't close App launcher
https://bugs.kde.org/show_bug.cgi?id=483630 Bug ID: 483630 Summary: Pressing escape key doesn't close App launcher Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: devguy...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY Pressing escape key doesn't close App launcher, this use to work before. STEPS TO REPRODUCE 1. Open App Launcher 2. Type something 3. Press ESC key OBSERVED RESULT Some off focus happen in the listed apps. EXPECTED RESULT Close App Launcher SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240313 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483629] New: Opens off center
https://bugs.kde.org/show_bug.cgi?id=483629 Bug ID: 483629 Summary: Opens off center Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: devguy...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 167234 --> https://bugs.kde.org/attachment.cgi?id=167234=edit app launcher off centered SUMMARY Doesn't remember location, after closing it will open at an odd location. I have a dual monitor setup, and my taskbar width is reduced and appear at the bottom center. I would expect the App launcher is open just above it center but its off-center to the side. When I move it to reposition it, it doesn't remember it's previous location. STEPS TO REPRODUCE 1. Press win / meta key. 2. Move App launcher window 3. Close Al Launcher 4. Go back to step 1 OBSERVED RESULT EXPECTED RESULT Off center to left, location not rememberred. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240313 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477385] horizontrol scroll doesn't work as expected on dolphin
https://bugs.kde.org/show_bug.cgi?id=477385 --- Comment #1 from Rajinder Yadav --- Upon further investigation it seems this behaviour is mapped to ALT + mouse wheel, this is wrong and doesn't follow convention of what every other application is doing, using SHIFT + mouse wheel -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477385] New: horizontrol scroll doesn't work as expected on dolphin
https://bugs.kde.org/show_bug.cgi?id=477385 Bug ID: 477385 Summary: horizontrol scroll doesn't work as expected on dolphin Classification: Applications Product: dolphin Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Pressing SHIFT + mouse wheel, should perform horizontal scrolling. STEPS TO REPRODUCE 1. Open dolphin in a directory so that both hotizontal and vertial scrollbar are visible 2. Press SHIFT while scrolling mouse wheel OBSERVED RESULT Vertical scrolling EXPECTED RESULT Horizontal scrolling Operating System: openSUSE Tumbleweed 20231120 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.1-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475773] New: Shift mouse wheel horizontal scrolling broken
https://bugs.kde.org/show_bug.cgi?id=475773 Bug ID: 475773 Summary: Shift mouse wheel horizontal scrolling broken Classification: Applications Product: dolphin Version: 23.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Pressing shift while scrolling with the mouse wheel. Scrolling shoud be horizontal, not vertical. STEPS TO REPRODUCE 1. View folder where vertical scrolling is required. 2. Add columns and expand then so horizontal scrolling is enabled. 3. Scroll using mouse wheel while pressing SHIFT key OBSERVED RESULT Scrolling is vertical EXPECTED RESULT Horizontal scrolling SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231013 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.6-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463533] Dolphin, file not getting sorted correctly
https://bugs.kde.org/show_bug.cgi?id=463533 Rajinder Yadav changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #5 from Rajinder Yadav --- Awesome :-D Checked it out, working for me now! Version 23.08.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #62 from Rajinder Yadav --- I am still seeing this problem with Dolpin not showing new files. I have to hit F5 (refresh) multiple times and something this doesn't fails and I need to view another folder and come back to see new files. This bug has been around for a long while and doesn't seem to be getting any attention. Operating System: openSUSE Tumbleweed 20230318 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.6-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467526] New: dolphin crashes where deleting file and folder
https://bugs.kde.org/show_bug.cgi?id=467526 Bug ID: 467526 Summary: dolphin crashes where deleting file and folder Classification: Applications Product: dolphin Version: 22.12.3 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.4-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: This has occured 2 time, I self a group of folder to be delete, press the delete key and dolphin will crash The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f4b2fd3c77e in KFileItemModel::expandedParentsCount(KFileItemModel::ItemData const*) () from /lib64/libdolphinprivate.so.5 #5 0x7f4b2fd6ae39 in KItemListView::hasSiblingSuccessor(int) const () from /lib64/libdolphinprivate.so.5 #6 0x7f4b2fd6bcec in KItemListView::updateSiblingsInformation(int, int) () from /lib64/libdolphinprivate.so.5 #7 0x7f4b2fd7054e in KItemListView::slotItemsRemoved(KItemRangeList const&) () from /lib64/libdolphinprivate.so.5 #8 0x7f4b2dd1338d in ?? () from /lib64/libQt5Core.so.5 #9 0x7f4b2fd2a2b5 in KItemModelBase::itemsRemoved(KItemRangeList const&) () from /lib64/libdolphinprivate.so.5 #10 0x7f4b2fd43b87 in KFileItemModel::slotItemsDeleted(KFileItemList const&) () from /lib64/libdolphinprivate.so.5 #11 0x7f4b2dd1338d in ?? () from /lib64/libQt5Core.so.5 #12 0x7f4b2f8083d5 in KCoreDirLister::itemsDeleted(KFileItemList const&) () from /lib64/libKF5KIOCore.so.5 #13 0x7f4b2f80fd79 in ?? () from /lib64/libKF5KIOCore.so.5 #14 0x7f4b2f801f94 in ?? () from /lib64/libKF5KIOCore.so.5 #15 0x7f4b2f804a9a in ?? () from /lib64/libKF5KIOCore.so.5 #16 0x7f4b2dd1338d in ?? () from /lib64/libQt5Core.so.5 #17 0x7f4b2efd89b5 in KDirWatch::deleted(QString const&) () from /lib64/libKF5CoreAddons.so.5 #18 0x7f4b2dd07d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f4b2e9a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f4b2dcdc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f4b2dcdf181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #22 0x7f4b2dd34413 in ?? () from /lib64/libQt5Core.so.5 #23 0x7f4b2ba67a90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f4b2ba67e48 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7f4b2ba67edc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f4b2dd33c16 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f4b2dcdac5b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f4b2dce2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x558fd29d6719 in ?? () #30 0x7f4b2d42caf0 in __libc_start_call_main () from /lib64/libc.so.6 #31 0x7f4b2d42cbb9 in __libc_start_main_impl () from /lib64/libc.so.6 #32 0x558fd29d6d85 in ?? () [Inferior 1 (process 9390) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466379] New KDE is really sluggish
https://bugs.kde.org/show_bug.cgi?id=466379 Rajinder Yadav changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #8 from Rajinder Yadav --- Closing this and will create 2 new issues for krunner and spectacle -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466379] New KDE is really sluggish
https://bugs.kde.org/show_bug.cgi?id=466379 --- Comment #7 from Rajinder Yadav --- Created attachment 156982 --> https://bugs.kde.org/attachment.cgi?id=156982=edit atop display -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466379] New KDE is really sluggish
https://bugs.kde.org/show_bug.cgi?id=466379 --- Comment #6 from Rajinder Yadav --- I've attached a screen shot from atop, don't see anything off. I also notice now that spectacle also is a slight sluggish, because I could rapid hit my shortcuts and get screen captures. Now I notice, when I use my shortcut, there is a slight delay. So if I am fliping threw tab and capturing something. It will miss something, which was not the case before. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466379] New KDE is really sluggish
https://bugs.kde.org/show_bug.cgi?id=466379 --- Comment #4 from Rajinder Yadav --- I've checked my disk, memory and CPU. 12 core CPU is 1% load. 62 GB free ram. 4TB free disk space. I tired opening a few app they seem to be opening fine, much better than when I created this bug. Definitely KRunner, it's not as responsive as it was before. Maybe this is it. I use it to do spell checks, conversions and running apps. The typing just seems poor. Sometime it misses key-strokes, backspace at odd time are delayed. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466379] New KDE is really sluggish
https://bugs.kde.org/show_bug.cgi?id=466379 --- Comment #3 from Rajinder Yadav --- It's not the system, it's the KDE desktop it is just sluggish. I am doing nothing out of the ordinary, happens all the time after. I've done is after a fresh reboot. It is not as responsive as it was in the past, before all the recent upgrades? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466379] New: New KDE is really sluggish
https://bugs.kde.org/show_bug.cgi?id=466379 Bug ID: 466379 Summary: New KDE is really sluggish Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After the KDE update, I've notice a considerable overall sluggishness in opening application. Also opening krunner, even typing feel delayed and then hitting backspace. Everytime a charated is typed or deleting, I think a search operation is getting kicked off and this add to the delayed feeling. My java trading application also now takes longer to open and become ready. I am using KDE on openSUSE TW. Operating System: openSUSE Tumbleweed 20230223 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444712] dolphin sometime opens off monitor
https://bugs.kde.org/show_bug.cgi?id=444712 --- Comment #6 from Rajinder Yadav --- (In reply to mydarkstar from comment #5) > Hi Rajinder, > > Plasma 5.27 just landed with a huge multi-monitor overhaul > (https://kde.org/et/announcements/plasma/5/5.27.0/). > I've noticed that this also affects Dolphin's remembering of its last > position and size. > > Does the update fix this issue for you? A lot of multi-monitor issues were > addressed with this overhaul. > Hoping for better results now! :) That's awesome, I am on this version with OpenSUSE TW KDE :-D It looks like it's working, however I also got setting to open a new Window under the mouse cursor. I did change it to "center" and "top left" to quickly tested and this time dolphin was showing up correctly, in the right monitor. Great work! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464648] Bluetooth connected devices don't show up in Audio System settings as "Playback Devices"
https://bugs.kde.org/show_bug.cgi?id=464648 --- Comment #6 from Rajinder Yadav --- FYI when bluetooth device connects, it play the connection tone. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464648] Bluetooth connected devices don't show up in Audio System settings as "Playback Devices"
https://bugs.kde.org/show_bug.cgi?id=464648 Rajinder Yadav changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG |--- Status|VERIFIED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464648] Bluetooth connected devices don't show up in Audio System settings as "Playback Devices"
https://bugs.kde.org/show_bug.cgi?id=464648 Rajinder Yadav changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #5 from Rajinder Yadav --- Hello, the bluetooth device stop shoping up again under "Audio settings". I've reconnected and disconnected multiple times. This time it is just not working. Operating System: openSUSE Tumbleweed 20230125 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464881] background images not displayed set after reboot
https://bugs.kde.org/show_bug.cgi?id=464881 --- Comment #1 from Rajinder Yadav --- Created attachment 155689 --> https://bugs.kde.org/attachment.cgi?id=155689=edit desktop wallpaper -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464881] New: background images not displayed set after reboot
https://bugs.kde.org/show_bug.cgi?id=464881 Bug ID: 464881 Summary: background images not displayed set after reboot Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I've set background images to both my desktop of a dual monitor setup. After I reboot, the default background image is getting used. If I right-click on the desktop and select "config desktop wallpaper" it shows the correct image highlighted. Operating System: openSUSE Tumbleweed 20230125 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464648] Bluetooth connected devices don't show up in Audio System settings as "Playback Devices"
https://bugs.kde.org/show_bug.cgi?id=464648 Rajinder Yadav changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #4 from Rajinder Yadav --- OK that seem to have fixed it, I tired again. This time it auto-connected and showed up (was not doing this before). I then tired disconnecting and re-connecting and do see the device in audio setting. Closing as working. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464648] Bluetooth connected devices don't show up in Audio System settings as "Playback Devices"
https://bugs.kde.org/show_bug.cgi?id=464648 --- Comment #2 from Rajinder Yadav --- Created attachment 155500 --> https://bugs.kde.org/attachment.cgi?id=155500=edit Audio Playback Devices -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464648] Bluetooth connected devices don't show up in Audio System settings as "Playback Devices"
https://bugs.kde.org/show_bug.cgi?id=464648 --- Comment #1 from Rajinder Yadav --- Created attachment 155499 --> https://bugs.kde.org/attachment.cgi?id=155499=edit Bluetooth connect devices -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464648] New: Bluetooth connected devices don't show up in Audio System settings as "Playback Devices"
https://bugs.kde.org/show_bug.cgi?id=464648 Bug ID: 464648 Summary: Bluetooth connected devices don't show up in Audio System settings as "Playback Devices" Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I am unable to use my connected bluetooth ear phones as well as speakers to play audio because they are not showing up in Audio System setting as a playback device. STEPS TO REPRODUCE 1. Pair bluetooth audio device 2. Go to system setting for Audio 3. Paired device doesn't showup in "Playback Devices" Operating System: openSUSE Tumbleweed 20230119 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.6-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463984] On dual monitor, remember and open window where the mouse is
https://bugs.kde.org/show_bug.cgi?id=463984 --- Comment #7 from Rajinder Yadav --- Same problem with Libre Open office XCala, and guessing many more apps (OBS). So this KDE window placement it definitely broken and doesn't work as I would expect. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463984] On dual monitor, remember and open window where the mouse is
https://bugs.kde.org/show_bug.cgi?id=463984 --- Comment #6 from Rajinder Yadav --- Broken for brave browser, I removed its special win/position and size. Doesn't follow my mouse to open new browser window. It might be a Brave/Chorme thing, as I believe it remembers the last browser with the focus and then opens the window there, not sure if KDE should be able to override this or I need to open a bug with chrome to respect KDE placement rules? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463984] On dual monitor, remember and open window where the mouse is
https://bugs.kde.org/show_bug.cgi?id=463984 --- Comment #5 from Rajinder Yadav --- OK I did the following: I went to Settings > Window behaviour > Advanced Tab I selected "Window placement" as "Under mouse" I unchecked "Allow app to remember the position ..." I unchecked "Hide utility windows for inactive..." Hit apply. But discovered another annoying problem. In the past (for me), windows size + position were not working! So I went to a given windows titlebar then right clicked and selected: 1. More Action 1. Config special Window setting (or) 1. Config special Application setting (or) Now I have to remove all these rules. I mean this windows placement, size is a complete mess and a birds nest :-D haha, I'm sure something else will break or stop working with respect to windows size, placement. Now I need to ask. I have several browsers window opens, with size+position, and on different monitors + virtual desktop. What happens now? The system will remember, because this is currently broken for me, and kind of works. The virtual desktop might be remember, but size, position, monitor will not. As for your other question: "So do you want to new windows to open" Just treat each monitor as it's own desktop, make it work like a single monitor desktop. Whereever the mouse is, the monitor+desktop will remember its own postion and size for a window being opened. If it's a windows first time being opened there, just open it in the center or follow the setting rules. (Let me know if make sense). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463984] On dual monitor, remember and open window where the mouse is
https://bugs.kde.org/show_bug.cgi?id=463984 --- Comment #1 from Rajinder Yadav --- When is this dual monitor and window sizing, placement finally going to get fixed? Can 2023 be the year :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463984] New: On dual monitor, remember and open window where the mouse is
https://bugs.kde.org/show_bug.cgi?id=463984 Bug ID: 463984 Summary: On dual monitor, remember and open window where the mouse is Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- For a dual monitor setup, use the mouse as context to determine where a windows should open. Also remember its window size and placement on that monitor. Just makes sense to open a window where the mouse in on a given monitor. Why make the user travel all the way to the otherside just to grag the new window to the other monitor. Use case: I had a dual monitor setup, but also share the main screen with my laptop. When I am working on my laptop. I use the KVM switch to change keyboard focus and go to the other screen to open/do something quickly. However if I try to open something say like dolphin, it will mostly open in the main screen which is not visible. Since it's being used by a different computer. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463644] feature request: just show normal timestamps in created, modified columns
https://bugs.kde.org/show_bug.cgi?id=463644 --- Comment #2 from Rajinder Yadav --- Thank you Paul. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463644] New: feature request: just show normal timestamps in created, modified columns
https://bugs.kde.org/show_bug.cgi?id=463644 Bug ID: 463644 Summary: feature request: just show normal timestamps in created, modified columns Classification: Applications Product: dolphin Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 154917 --> https://bugs.kde.org/attachment.cgi?id=154917=edit timestamps SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I do not like seeing "Just now", "10 min ago", "Yesterday" for timestamps. I would like an option to disable this feature, it also seem to break sorting. See attached pic. Operating System: openSUSE Tumbleweed 20221228 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.1-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463533] Dolphin, file not getting sorted correctly
https://bugs.kde.org/show_bug.cgi?id=463533 --- Comment #3 from Rajinder Yadav --- Also I don't see any option to disable this style of date reporting, like "Just now" or "Yesterday". I personally find don't like and would like just dates reported. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463535] Open file dialog has missing "Filters" and doesn't show all the file in a folder.
https://bugs.kde.org/show_bug.cgi?id=463535 --- Comment #1 from Rajinder Yadav --- The same for "Import Image" dialog box. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463535] New: Open file dialog has missing "Filters" and doesn't show all the file in a folder.
https://bugs.kde.org/show_bug.cgi?id=463535 Bug ID: 463535 Summary: Open file dialog has missing "Filters" and doesn't show all the file in a folder. Classification: Applications Product: krita Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** The open dialog box filter field is empty, so not I need to type "*" to show all the file before being able to select it. Otherwise Only *.kra files are visible by default. Operating System: openSUSE Tumbleweed 20221225 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463533] Dolphin, file not getting sorted correctly
https://bugs.kde.org/show_bug.cgi?id=463533 --- Comment #2 from Rajinder Yadav --- In the screenshot, the file at the bottom should appear at the top. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463533] Dolphin, file not getting sorted correctly
https://bugs.kde.org/show_bug.cgi?id=463533 --- Comment #1 from Rajinder Yadav --- Created attachment 154855 --> https://bugs.kde.org/attachment.cgi?id=154855=edit File sort bug -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463533] New: Dolphin, file not getting sorted correctly
https://bugs.kde.org/show_bug.cgi?id=463533 Bug ID: 463533 Summary: Dolphin, file not getting sorted correctly Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** For newly created folder/files, Dolplin now tires to be "fancy" and show something else other than the timestamp. As a result soft by time is broken. Please see attachment. Operating System: openSUSE Tumbleweed 20221225 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 463380] Putting system to sleep hangs the system
https://bugs.kde.org/show_bug.cgi?id=463380 --- Comment #5 from Rajinder Yadav --- I don't have bumblebee installed, but I will install the kernel-debug module and go from there, thanks -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 463380] Putting system to sleep hangs the system
https://bugs.kde.org/show_bug.cgi?id=463380 --- Comment #3 from Rajinder Yadav --- I was able to suspend my system once, now when I try again after why it will not go into suspend mode and will after a little while present the login screen and I need to re-login backin to my running session. I've attached the dmesg log for you to view, but I did notice the section at the bottom stating some bug? [178099.490425] usb 1-2: USB disconnect, device number 2 [178106.473716] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 5 [178108.402907] PM: suspend entry (deep) [178108.424506] Filesystems sync: 0.021 seconds [178108.424627] BUG: unable to handle page fault for address: 0005d566c000 [178108.424650] #PF: supervisor instruction fetch in kernel mode [178108.424665] #PF: error_code(0x0010) - not-present page [178108.424679] PGD 0 P4D 0 [178108.424688] Oops: 0010 [#1] PREEMPT SMP NOPTI [178108.424700] CPU: 8 PID: 3172 Comm: systemd-sleep Tainted: P OE 6.0.12-1-default #1 openSUSE Tumbleweed 21b79504127c49fe5a884954af431438cb2057cc [178108.424734] Hardware name: Micro-Star International Co., Ltd. MS-7A38/B450M PRO-VDH MAX (MS-7A38), BIOS B.D0 01/11/2022 [178108.424760] RIP: 0010:0x5d566c000 [178108.424771] Code: Unable to access opcode bytes at RIP 0x5d566bfd6. [178108.424788] RSP: 0018:ae2b824e7d88 EFLAGS: 00010206 [178108.424802] RAX: 0005d566c000 RBX: RCX: [178108.424820] RDX: RSI: 0003 RDI: 9fdbfb978b78 [178108.424837] RBP: 0005d566d000 R08: bbdceff0 R09: ae2b824e7d18 [178108.424855] R10: R11: R12: [178108.424873] R13: 0003 R14: 000a R15: 0009 [178108.424890] FS: 7f375333cb00() GS:9fea3ec0() knlGS: [178108.424910] CS: 0010 DS: ES: CR0: 80050033 [178108.424925] CR2: 0005d566c000 CR3: 000a71e7a000 CR4: 00750ee0 [178108.424943] PKRU: 5554 [178108.424951] Call Trace: [178108.424960] [178108.424967] ? blocking_notifier_call_chain_robust+0x6e/0xd0 [178108.424985] ? pm_notifier_call_chain_robust+0x19/0x40 [178108.425000] ? pm_suspend.cold+0x16f/0x35e [178108.425012] ? state_store+0x68/0xd0 [178108.425024] ? kernfs_fop_write_iter+0x11e/0x1f0 [178108.425038] ? vfs_write+0x1f7/0x3b0 [178108.425050] ? ksys_write+0x63/0xe0 [178108.425061] ? do_syscall_64+0x5b/0x80 [178108.425074] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd [178108.425090] [178108.425097] Modules linked in: udp_diag tcp_diag inet_diag rfcomm veth xt_nat nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT xt_tcpudp overlay bridge stp llc af_packet nf_nat_ftp nf_nat_tftp nf_conntrack_ftp nft_objref nf_conntrack_tftp nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_mangle iptable_raw iscsi_ibft iscsi_boot_sysfs iptable_security ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter qrtr cmac algif_hash algif_skcipher af_alg nct6775 nct6775_core bnep hwmon_vid hid_generic usbhid squashfs nls_iso8859_1 nls_cp437 loop vfat binfmt_misc fat nvidia_drm(POE) nvidia_modeset(POE) intel_rapl_msr [178108.425126] nvidia_uvm(POE) btusb btrtl btbcm btintel snd_hda_codec_realtek btmtk snd_hda_codec_generic intel_rapl_common bluetooth ledtrig_audio uvcvideo snd_hda_codec_hdmi ecdh_generic videobuf2_vmalloc videobuf2_memops rfkill edac_mce_amd snd_hda_intel videobuf2_v4l2 snd_intel_dspcfg snd_intel_sdw_acpi videobuf2_common kvm_amd snd_hda_codec nvidia(POE) snd_usb_audio snd_hda_core videodev snd_usbmidi_lib kvm snd_rawmidi snd_seq_device r8169 snd_hwdep mc snd_pcm realtek snd_timer irqbypass mdio_devres snd wmi_bmof parport_pc libphy pcspkr efi_pstore i2c_piix4 soundcore k10temp ppdev parport gpio_amdpt gpio_generic acpi_cpufreq tiny_power_button fuse configfs dmi_sysfs ip_tables x_tables ext4 mbcache jbd2 uas usb_storage crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel xhci_pci xhci_pci_renesas xhci_hcd aesni_intel nvme crypto_simd usbcore cryptd ccp sp5100_tco nvme_core wmi button sg dm_multipath dm_mod [178108.425326] scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs [178108.427340] CR2: 0005d566c000 [178108.427970] ---[ end trace ]--- [178108.428602] RIP: 0010:0x5d566c000 [178108.429221] Code: Unable to access opcode bytes at RIP 0x5d566bfd6. [178108.429839] RSP: 0018:ae2b824e7d88 EFLAGS: 00010206 [178108.430442] RAX: 0005d566c000 RBX: RCX: [178108.431039] RDX: RSI: 0003 RDI
[Powerdevil] [Bug 463380] Putting system to sleep hangs the system
https://bugs.kde.org/show_bug.cgi?id=463380 --- Comment #2 from Rajinder Yadav --- Created attachment 154816 --> https://bugs.kde.org/attachment.cgi?id=154816=edit dmesh output -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 463380] New: Putting system to sleep hangs the system
https://bugs.kde.org/show_bug.cgi?id=463380 Bug ID: 463380 Summary: Putting system to sleep hangs the system Classification: Plasma Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: devguy...@gmail.com CC: m...@ratijas.tk Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When putting the system to sleep, at times it will hang, or crash, not sure exactly what is going on. This stop working for me months ago. STEPS TO REPRODUCE 1. Put system to sleep OBSERVED RESULT Hangs or crashes EXPECTED RESULT Put PC to sleep. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Operating System: openSUSE Tumbleweed 20221221 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.12-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463376] Toggle Present Windows (All Desktops) filter doesn't work for dual monitors
https://bugs.kde.org/show_bug.cgi?id=463376 --- Comment #1 from Rajinder Yadav --- This also happen for "Toggle Present Windows (Current desktop). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463376] New: Toggle Present Windows (All Desktops) filter doesn't work for dual monitors
https://bugs.kde.org/show_bug.cgi?id=463376 Bug ID: 463376 Summary: Toggle Present Windows (All Desktops) filter doesn't work for dual monitors Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** On a dual monitor, "Toggle Present Windows (All desktops)" fails to filter/find windows in the other monitor where the mouse cursor is not. STEPS TO REPRODUCE 1. Have windows open on both screens 2. Toggle present windows 3. Start typing window name in other monitor (without mouse cursor) OBSERVED RESULT It fails to find the other window, so as a result I can't quickly switch to it. EXPECTED RESULT Find and filter all windows in multiples monitors and multiple desktops. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20221221 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.12-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444712] dolphin sometime opens off monitor
https://bugs.kde.org/show_bug.cgi?id=444712 --- Comment #4 from Rajinder Yadav --- Moving dolphin and then closing it, when dolphin is opened again it fails to remember last window position. Also moving to 2nd monitor, close and reopens in the main monitor. Tested with version 22.08.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455274] Press F3 doesn't split evenly
https://bugs.kde.org/show_bug.cgi?id=455274 --- Comment #2 from Rajinder Yadav --- This seem to have been fixed in version 22.08.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457872] some custom shortcuts stop working
https://bugs.kde.org/show_bug.cgi?id=457872 --- Comment #11 from Rajinder Yadav --- If I look at the menu for how LibrOffice Cala is being called, the command has the following, "libreoffice --calc %U" Are you stay this is the same bug as in Kate? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457872] some custom shortcuts stop working
https://bugs.kde.org/show_bug.cgi?id=457872 --- Comment #9 from Rajinder Yadav --- I also need to mention I have another global shortcut to open LibreOffice Calc that also stop working at the same time, so this is not a Kate related bug and I would reopen this and not mark this is a dup. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453884] Krita 5.0.6 crashes during saving
https://bugs.kde.org/show_bug.cgi?id=453884 --- Comment #35 from Rajinder Yadav --- I've gotten a crash on undo as well. Operating System: openSUSE Tumbleweed 20220901 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.2-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457872] some custom shortcuts stop working
https://bugs.kde.org/show_bug.cgi?id=457872 --- Comment #8 from Rajinder Yadav --- I got 5.97 now, rebooted my system, delete the global shortcut to Kate, reapplied it, still broken. Operating System: openSUSE Tumbleweed 20220901 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.2-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457872] some custom shortcuts stop working
https://bugs.kde.org/show_bug.cgi?id=457872 --- Comment #6 from Rajinder Yadav --- Also yes kglobalaccel is running fine see it in System Activity, also my other shortcuts continue to work, including a custom shortcut to open Krita. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457872] some custom shortcuts stop working
https://bugs.kde.org/show_bug.cgi?id=457872 --- Comment #5 from Rajinder Yadav --- Hi Nate, on openSUSE TW I do not see any indication of Kate opening up from the desktop. I just tried now looking at the toolbar also, nothing is crashing on launch. I can open Kate fine from the terminal and run command. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457872] some custom shortcuts stop working
https://bugs.kde.org/show_bug.cgi?id=457872 --- Comment #2 from Rajinder Yadav --- All my shortcuts already existed and were working fine and then broke after an update. Go to system settings -> shortcuts Click Add application, select Kate, assign shortcut. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457872] New: some custom shortcuts stop working
https://bugs.kde.org/show_bug.cgi?id=457872 Bug ID: 457872 Summary: some custom shortcuts stop working Product: frameworks-kglobalaccel Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I have custom shortcuts that I created and some of them stop working. I've deleted the shortcut no working and recreated it and tried other key bindings and it still does not work. One of the binding not working is: WIN+ALT+T to bring Kate System info: Operating System: openSUSE Tumbleweed 20220812 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.19.0-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 $ uname -a Linux localhost.localdomain 5.19.0-1-default #1 SMP PREEMPT_DYNAMIC Tue Aug 9 16:38:40 UTC 2022 (8213b0c) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457033] Select all marks clean document as dirty
https://bugs.kde.org/show_bug.cgi?id=457033 --- Comment #4 from Rajinder Yadav --- Hi David, I had a feeling someone was going to say what you said haha. I just realize I can drag and drop another image as a layer or from the menu layer -> import and do what I was doing opening multiple files and then copying them over. Thanks for taking the time to explain what was going on and why! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457033] Select all marks clean document as dirty
https://bugs.kde.org/show_bug.cgi?id=457033 --- Comment #2 from Rajinder Yadav --- Why would selecting a image and also copying an image have to be stored in the current document. No other application has the behaviour. These are no destructive operations and it should not mark a document dirty, this is a design flaw and imho a bug. I can see this is getting saved to some undo buffer, but until a transformation operation is applied to the document. I should be able to close it with being asked to safe the file. As a result I am forced to do an addition mouse clicks or key press. The makes the under experience bad. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457033] New: Select all marks clean document as dirty
https://bugs.kde.org/show_bug.cgi?id=457033 Bug ID: 457033 Summary: Select all marks clean document as dirty Product: krita Version: 5.0.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When I open a new image file to copy and paste into another tabbed view, the copied file is marked dirty. As a result when I close the tab I get an annoying popup dialog asking me if I was to save the file. STEPS TO REPRODUCE 1. Open a image file 2. Press CTRL+A 3. Press CTRL+C 4. Press CTRL+W OBSERVED RESULT File is marked dirty when no changes have occured and dialog appear asking me if I want to save the file. EXPECTED RESULT File should close. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220719 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.11-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413862] Panel will not go into auto hide mode
https://bugs.kde.org/show_bug.cgi?id=413862 --- Comment #2 from Rajinder Yadav --- I just verified, looks like it's working fine now. Seems more responsive also. I might keep the setting :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455274] Press F3 doesn't split evenly
https://bugs.kde.org/show_bug.cgi?id=455274 --- Comment #1 from Rajinder Yadav --- Operating System: openSUSE Tumbleweed 20220613 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.18.2-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455274] New: Press F3 doesn't split evenly
https://bugs.kde.org/show_bug.cgi?id=455274 Bug ID: 455274 Summary: Press F3 doesn't split evenly Product: dolphin Version: 22.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When I press F3 to see side-by-side split view, the split doesn't happen evenly. Also I believe displaying & hiding the side panel by pressing F11 also messed up split. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454456] Spectacle does not open
https://bugs.kde.org/show_bug.cgi?id=454456 Rajinder Yadav changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Rajinder Yadav --- Hello Ömer Fadıl , The bug seems to have been corrected with openSUSE TW with latest update. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454456] Spectacle does not open
https://bugs.kde.org/show_bug.cgi?id=454456 --- Comment #2 from Rajinder Yadav --- I believe this bug has already been reported. $ spectacle spectacle: symbol lookup error: /lib64/libkImageAnnotator.so.0: undefined symbol: _ZN12kColorPicker12KColorPickerC1Ev -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454456] New: Does not open
https://bugs.kde.org/show_bug.cgi?id=454456 Bug ID: 454456 Summary: Does not open Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: devguy...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Application no longer opening. Operating System: openSUSE Tumbleweed 20220525 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.9-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453884] Krita 5.0.6 crashes during saving
https://bugs.kde.org/show_bug.cgi?id=453884 --- Comment #17 from Rajinder Yadav --- I can confirm 5.1.0-prealpha has fixed this bug, I am no longer seeing this crash. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454112] New: Crashes on loading a document from File open
https://bugs.kde.org/show_bug.cgi?id=454112 Bug ID: 454112 Summary: Crashes on loading a document from File open Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: krita-bugs-n...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Cashes every time I open a file to edit it. This just started happening 3 days ago, maybe with latest update? The files I tried are .png, .kra, not sure if the crash happens with other formats? Krita: 5.0.6 STEPS TO REPRODUCE 1. File -> Open 2. Select a .png or .kra image to load OBSERVED RESULT Crash EXPECTED RESULT Opens graphic file for editing. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220519 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.7-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447236] Entire desktop crashes and disappears
https://bugs.kde.org/show_bug.cgi?id=447236 --- Comment #8 from Rajinder Yadav --- This crash is happening more frequently, and I raise the severity to high, if not critical. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447236] Entire desktop crashes and disappears
https://bugs.kde.org/show_bug.cgi?id=447236 --- Comment #7 from Rajinder Yadav --- Here is another bt. #0 QSGAreaAllocatorNode::isLeaf (this=0x20001) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:93 #1 QSGAreaAllocator::deallocateInNode (this=this@entry=0x7f1e2c1394c0, pos=..., node=0x20001) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:170 #2 0x7f1ec4b10fb6 in QSGAreaAllocator::deallocate (this=this@entry=0x7f1e2c1394c0, rect=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:116 #3 0x7f1ec4b174df in QSGOpenGLAtlasTexture::AtlasBase::remove (this=0x7f1e2c1394b0, t=t@entry=0x7f1e2cc7beb0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:286 #4 0x7f1ec4b1762d in QSGOpenGLAtlasTexture::TextureBase::~TextureBase (this=0x7f1e2cc7beb0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:516 #5 QSGOpenGLAtlasTexture::Texture::~Texture (this=0x7f1e2cc7beb0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:543 #6 0x7f1ec4b17649 in QSGOpenGLAtlasTexture::Texture::~Texture (this=0x7f1e2cc7beb0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:543 #7 0x7f1eb42492bd in QScopedPointerDeleter::cleanup (pointer=) at /usr/include/qt5/QtCore/qscopedpointer.h:60 #8 QScopedPointer >::~QScopedPointer (this=, this=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #9 Plasma::WindowTextureProvider::~WindowTextureProvider (this=, this=) at /usr/src/debug/plasma-framework-5.89.0-1.1.x86_64/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/../../../../../../src/declarativeimports/core/windowthumbnail.h:149 #10 Plasma::WindowTextureProvider::~WindowTextureProvider (this=, this=) at /usr/src/debug/plasma-framework-5.89.0-1.1.x86_64/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/../../../../../../src/declarativeimports/core/windowthumbnail.h:149 #11 0x7f1ec4b61152 in QSGRenderThread::event (this=0x7f1eb800f510, e=0x55582e852c10) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:493 #12 0x7f1ec4b5ab3f in QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7f1eb800f510) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:937 #13 0x7f1ec4b5cfd9 in QSGRenderThread::run (this=0x7f1eb800f510) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1053 #14 0x7f1ec2ea4df1 in QThreadPrivate::start (arg=0x7f1eb800f510) at thread/qthread_unix.cpp:329 #15 0x7f1ec2a09427 in start_thread (arg=) at pthread_create.c:435 #16 0x7f1ec2a92810 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447236] Entire desktop crashes and disappears
https://bugs.kde.org/show_bug.cgi?id=447236 --- Comment #6 from Rajinder Yadav --- (gdb) bt #0 QSGAreaAllocatorNode::isLeaf (this=0x18) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:93 #1 QSGAreaAllocator::deallocateInNode (this=this@entry=0x7f4668139020, pos=..., node=0x18) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:170 #2 0x7f4703029fb6 in QSGAreaAllocator::deallocate (this=this@entry=0x7f4668139020, rect=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgareaallocator.cpp:116 #3 0x7f47030304df in QSGOpenGLAtlasTexture::AtlasBase::remove (this=0x7f4668139010, t=t@entry=0x7f4668a7e460) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:286 #4 0x7f470303062d in QSGOpenGLAtlasTexture::TextureBase::~TextureBase (this=0x7f4668a7e460, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:516 #5 QSGOpenGLAtlasTexture::Texture::~Texture (this=0x7f4668a7e460, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:543 #6 0x7f4703030649 in QSGOpenGLAtlasTexture::Texture::~Texture (this=0x7f4668a7e460, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/util/qsgopenglatlastexture.cpp:543 #7 0x7f46ee7442bd in QScopedPointerDeleter::cleanup (pointer=) at /usr/include/qt5/QtCore/qscopedpointer.h:60 #8 QScopedPointer >::~QScopedPointer (this=, this=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #9 Plasma::WindowTextureProvider::~WindowTextureProvider (this=, this=) at /usr/src/debug/plasma-framework-5.89.0-1.1.x86_64/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/../../../../../../src/declarativeimports/core/windowthumbnail.h:149 #10 Plasma::WindowTextureProvider::~WindowTextureProvider (this=, this=) at /usr/src/debug/plasma-framework-5.89.0-1.1.x86_64/build/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/../../../../../../src/declarativeimports/core/windowthumbnail.h:149 #11 0x7f470307a152 in QSGRenderThread::event (this=0x7f46f800d820, e=0x557ad0b12de0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:493 #12 0x7f4703073b3f in QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7f46f800d820) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:937 #13 0x7f4703075fd9 in QSGRenderThread::run (this=0x7f46f800d820) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1053 #14 0x7f47013bddf1 in QThreadPrivate::start (arg=0x7f46f800d820) at thread/qthread_unix.cpp:329 #15 0x7f4700f22427 in start_thread (arg=) at pthread_create.c:435 #16 0x7f4700fab810 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447236] Entire desktop crashes and disappears
https://bugs.kde.org/show_bug.cgi?id=447236 --- Comment #5 from Rajinder Yadav --- Suggestion helped, but no crash logs founds. I believe coredump needs to be enabled? $ coredumpctl Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No coredumps found. $ sudo coredumpctl [sudo] password for root: No coredumps found. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447236] Entire desktop crashes and disappears
https://bugs.kde.org/show_bug.cgi?id=447236 --- Comment #3 from Rajinder Yadav --- Hi I searched for coredumpctl and systemd-coredumpctl for opensuse tw, package not found. I was able to install valgrind, but you will need to provide the command syntax I should use with the name of the process. Also I believe I need to enable coredump to be saved? Please provide the steps needs to provide a crash log. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447236] Entire desktop crashes and disappears
https://bugs.kde.org/show_bug.cgi?id=447236 --- Comment #1 from Rajinder Yadav --- Anyone else coming across this bug, here is a temp workaround: https://askubuntu.com/questions/481329/can-i-restart-the-kde-plasma-desktop-without-logging-out I used the following to restart the plasma shell kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447236] New: Entire desktop crashes and disappears
https://bugs.kde.org/show_bug.cgi?id=447236 Bug ID: 447236 Summary: Entire desktop crashes and disappears Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** This has stated to happen randomly, in the past week for me. The entire desktop just goes back, the toolbar, background images, desktop icons disappear, leaving a black background, remain windows remain open and function with not error. I can still open new windows using open the command prompt and typing the application to open. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211215 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.7-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444712] dolphin sometime opens off monitor
https://bugs.kde.org/show_bug.cgi?id=444712 --- Comment #3 from Rajinder Yadav --- Hello the issue has occurred again, running dolphin from the terminal shows the following output $ dolphin Qt: Session management error: networkIdsList argument is NULL -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444712] dolphin sometime opens off monitor
https://bugs.kde.org/show_bug.cgi?id=444712 --- Comment #2 from Rajinder Yadav --- I am not able to reproduce it yet, but does this look right? $ dolphin Qt: Session management error: networkIdsList argument is NULL -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444712] New: dolphin sometime opens off monitor
https://bugs.kde.org/show_bug.cgi?id=444712 Bug ID: 444712 Summary: dolphin sometime opens off monitor Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I how a dual monitor setup and when I close dolphin on the small screen, when I open dolphin it will appear off screen. Unless you know to right-click on the toolbar of the app icon, and select "move", there is no way to correct this problem, it will leave the user baffled. STEPS TO REPRODUCE 1. open dolphin 2. move to smaller screen (in dual monitor setup) 3. close dolphin 4. open dolphin OBSERVED RESULT dolphin is not visible EXPECTED RESULT dolphin appear in the screen (monitor) where it is opened from. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211029 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443951] 5.23.0 Has Horrible Compositing Issues - Black Boxes and Flickering showing up
https://bugs.kde.org/show_bug.cgi?id=443951 --- Comment #50 from Rajinder Yadav --- I am on openSUSE TW, how can I check if this fix has made it is? I am still seeing this problem today, which seems to have shown up last week. I made a quick video, but unable to capture the flickering: https://www.youtube.com/watch?v=YMKQJ-kWfVg Something all I need to do is open a new window and both my monitor will go into rapid flickering which is really jarring! Operating System: openSUSE Tumbleweed 20211025 KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444463] odd window or desktop flickering
https://bugs.kde.org/show_bug.cgi?id=63 --- Comment #1 from Rajinder Yadav --- I rebooted the system and the steps outlined below no longer reproduce the flickering behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444463] New: odd window or desktop flickering
https://bugs.kde.org/show_bug.cgi?id=63 Bug ID: 63 Summary: odd window or desktop flickering Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY This has happened 3 times recently, when I open a new application, the window or background around it start to go into rapid flickering. I once has my 2nd monitor entire desktop go into a flickering, it will remain like this until you click on the desktop or move the window. I don't know what is causing this. Funny enough when I open "Info Center" it just happened now. OK it seems on openSUSE TW I can reproduce this with the following steps. 1. Open a few windows 1. Press ALT+SPACE, type, "info" to open Info Center. Flickering starts immediately! I'm wondering if this has anything to do with the latest NVidia RTX 3080 driver? Operating System: openSUSE Tumbleweed 20211021 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-2-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439815] Window randomly become transparent, when close ghost image remains
https://bugs.kde.org/show_bug.cgi?id=439815 --- Comment #19 from Rajinder Yadav --- Created attachment 142300 --> https://bugs.kde.org/attachment.cgi?id=142300=edit window with see through hole I disabled translucency from system setting and I am still having these problem, see this issues already 3 time in a week. I though it went away, this time please see attached pic, "win-with-hole.png" the window has a hole and when I mode it around the "see through hole" doesn't go away! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 442056] shortcut stop working
https://bugs.kde.org/show_bug.cgi?id=442056 --- Comment #9 from Rajinder Yadav --- Nate your call, if you can somehow reproduce this bug, you might be able to find a fix using your assumption of what happened. Shortcuts has been working fine for me, but this one seems like it was definitely an edge-case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443204] Window config missing option to set size and location
https://bugs.kde.org/show_bug.cgi?id=443204 --- Comment #2 from Rajinder Yadav --- Created attachment 142073 --> https://bugs.kde.org/attachment.cgi?id=142073=edit missing properties button -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443204] Window config missing option to set size and location
https://bugs.kde.org/show_bug.cgi?id=443204 --- Comment #1 from Rajinder Yadav --- See pic labeled, "win-config-bug" The 1st pic got confused and I clicked on Kate while someone ended showing the missing properties button. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443204] New: Window config missing option to set size and location
https://bugs.kde.org/show_bug.cgi?id=443204 Bug ID: 443204 Summary: Window config missing option to set size and location Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- Created attachment 142072 --> https://bugs.kde.org/attachment.cgi?id=142072=edit window config dialog SUMMARY Missing option to be able to selected position and location size for the window. I am seeing this in Blender and also Kate. STEPS TO REPRODUCE 1. Open Blender or Kate 2. rick-click on titlebar -> More Action -> Config Special Window OBSERVED RESULT See Picture EXPECTED RESULT Option to set location and size of window. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210927 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.6-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441516] filter toolbar icon missing and related issues
https://bugs.kde.org/show_bug.cgi?id=441516 --- Comment #4 from Rajinder Yadav --- Thanks for the tip! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 442056] shortcut stop working
https://bugs.kde.org/show_bug.cgi?id=442056 --- Comment #6 from Rajinder Yadav --- Not sure what caused the shortcut to break, it could have happened after LibreOffice update? I know the rest of my shortcut remained valid and and functioning. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 442056] shortcut stop working
https://bugs.kde.org/show_bug.cgi?id=442056 --- Comment #4 from Rajinder Yadav --- Hi Nate you can close this off, somehow my shortcut lost association with LibreOffice. A bug in it self. So I ended up deleting and re-assigning the shortcut and it's working fine now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441969] Window position and size not getting remember for special config
https://bugs.kde.org/show_bug.cgi?id=441969 --- Comment #3 from Rajinder Yadav --- Hi Nate, I noticed it was not pointing to the application, I ended up deleting it and then assigning it and it started to work. However I will also use your advice and ignore requested geometry, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 442056] shortcut stop working
https://bugs.kde.org/show_bug.cgi?id=442056 --- Comment #1 from Rajinder Yadav --- Created attachment 141321 --> https://bugs.kde.org/attachment.cgi?id=141321=edit shortcuts sys setting -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 442056] New: shortcut stop working
https://bugs.kde.org/show_bug.cgi?id=442056 Bug ID: 442056 Summary: shortcut stop working Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY Had application shortcut for "LibreOffice Calc" set to META+ALT+O, no longer works! I have reset it and it still doesn't work. This worked in the past with no issues. My other shortcut seem to be working ok. STEPS TO REPRODUCE 1. open sys setting 2. create shortcut for libreoffice calc 3. set shortcut to meta+alt+o (letter o) OBSERVED RESULT Fails to work EXPECTED RESULT Open app Operating System: openSUSE Tumbleweed 20210902 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.13-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441969] Window position and size not getting remember for special config
https://bugs.kde.org/show_bug.cgi?id=441969 --- Comment #1 from Rajinder Yadav --- This seems to be broken for Libre Office applications in general, the other windows like dolphin, konsole, kate seem to work fine with special window config. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441969] New: Window position and size not getting remember for special config
https://bugs.kde.org/show_bug.cgi?id=441969 Bug ID: 441969 Summary: Window position and size not getting remember for special config Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY Here is a quick video showing the problem along with other bugs which I am sure you are all well aware off. https://youtu.be/tAtFyETunZI Operating System: openSUSE Tumbleweed 20210901 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.13-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441516] filter toolbar icon missing and related issues
https://bugs.kde.org/show_bug.cgi?id=441516 --- Comment #1 from Rajinder Yadav --- Created attachment 141024 --> https://bugs.kde.org/attachment.cgi?id=141024=edit filter icon missing -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441516] New: filter toolbar icon missing and related issues
https://bugs.kde.org/show_bug.cgi?id=441516 Bug ID: 441516 Summary: filter toolbar icon missing and related issues Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: filter Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY This filter icon in the toolbar is no longer showing. I don't see any option in the file menu to toggle the filter input field visibility. Where I was able toggle the filter input field, locking it to remain open failed to work and I had to manually make the filter field visible. Operating System: openSUSE Tumbleweed 20210820 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.12-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440508] unable to move the window
https://bugs.kde.org/show_bug.cgi?id=440508 --- Comment #2 from Rajinder Yadav --- found the problem, something changed the, "Special windows setting" for "position" from remember to "force", as a result it was locking the window position. -- You are receiving this mail because: You are watching all bug changes.
