[Discover] [Bug 470270] New: KDE plasma desktop crashes after install, KALI linux
https://bugs.kde.org/show_bug.cgi?id=470270 Bug ID: 470270 Summary: KDE plasma desktop crashes after install, KALI linux Classification: Applications Product: Discover Version: 5.27.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: phoenixstor...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.2) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.0.0-kali6-amd64 x86_64 Windowing System: Wayland Distribution: Kali GNU/Linux Rolling DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: I installed kde-full using sudo apt install kde-full, on kali linux. Latest version at 5/25/2023. After install, it crashed. But it worked after the crash, just takes SUPER LONG to load.. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7fc0bec7a9ca in Category::name() const () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so #5 0x7fc0bec7e3e3 in Category::addSubcategory(QVector&, Category*) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so #6 0x7fc0bec7ed73 in Category::addSubcategory(QVector&, Category*) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so #7 0x7fc0bec80a47 in CategoryModel::populateCategories() () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so #8 0x7fc0bcae8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc0bcaecd6a in QTimer::timeout(QTimer::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc0bcadd50d in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fc0be562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fc0bcab16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fc0bcb08c31 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fc0bcb094fc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fc0bb25ceed in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fc0bb25d198 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fc0bb25d22c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fc0bcb09836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fc0bcab017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fc0bcab82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x55743dc8a2a7 in ?? () #22 0x7fc0bc64618a in __libc_start_call_main (main=main@entry=0x55743dc899b0, argc=argc@entry=3, argv=argv@entry=0x7ffc08c7dde8) at ../sysdeps/nptl/libc_start_call_main.h:58 #23 0x7fc0bc646245 in __libc_start_main_impl (main=0x55743dc899b0, argc=3, argv=0x7ffc08c7dde8, init=, fini=, rtld_fini=, stack_end=0x7ffc08c7ddd8) at ../csu/libc-start.c:381 #24 0x55743dc8a811 in ?? () [Inferior 1 (process 2520) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469242] New: Doplhin crashed while ejecting an encrypted USB Stick
https://bugs.kde.org/show_bug.cgi?id=469242 Bug ID: 469242 Summary: Doplhin crashed while ejecting an encrypted USB Stick Classification: Applications Product: dolphin Version: 23.04.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: fe...@feldspaten.org CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.0) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.12-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: When ejecting a LUKS encrypted USB Stick, Dolphin just crashed. I could not reproduce the issue when trying again, so this happens sometimes, but not always. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x560aaeab522d in TerminalPanel::sendCdToTerminal (this=0x560aaf8145f0, dir=..., addToHistory=TerminalPanel::HistoryPolicy::SkipHistory) at /usr/src/debug/dolphin-23.04.0/src/panels/terminal/terminalpanel.cpp:241 #5 0x560aaea941b9 in TerminalPanel::goHome (this=0x560aaf8145f0) at /usr/src/debug/dolphin-23.04.0/src/panels/terminal/terminalpanel.cpp:54 #6 DolphinMainWindow::slotStorageTearDownFromPlacesRequested (this=0x560aaf6fde40, mountPath=...) at /usr/src/debug/dolphin-23.04.0/src/dolphinmainwindow.cpp:1477 #7 0x7f4d81f25232 in QtPrivate::QSlotObjectBase::call (a=0x7fff3d3aa010, r=0x560aaf6fde40, this=0x560aaf824b30) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x560aaf801ae0, signal_index=24, argv=0x7fff3d3aa010) at kernel/qobject.cpp:3923 #9 0x7f4d81f1de2f in QMetaObject::activate (sender=sender@entry=0x560aaf801ae0, m=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff3d3aa010) at kernel/qobject.cpp:3983 #10 0x560aaeab435b in PlacesPanel::storageTearDownRequested (_t1=..., this=0x560aaf801ae0) at /usr/src/debug/dolphin-23.04.0/build/src/dolphinstatic_autogen/DIM5AXWM7T/moc_placespanel.cpp:256 #11 PlacesPanel::slotTearDownRequested (this=0x560aaf801ae0, index=...) at /usr/src/debug/dolphin-23.04.0/src/panels/places/placespanel.cpp:221 #12 0x7f4d83ea4ae3 in KFilePlacesViewPrivate::actionClicked (index=..., this=0x560aaf722eb0) at /usr/src/debug/kio-5.105.0/src/filewidgets/kfileplacesview.cpp:1938 #13 operator() (index=..., __closure=) at /usr/src/debug/kio-5.105.0/src/filewidgets/kfileplacesview.cpp:870 #14 QtPrivate::FunctorCall, QtPrivate::List, void, KFilePlacesView::KFilePlacesView(QWidget*):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #15 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #16 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #17 0x7f4d81f25232 in QtPrivate::QSlotObjectBase::call (a=0x7fff3d3aa190, r=0x560aaf801ae0, this=0x560aaf8d1ca0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate (sender=0x560aaf70f5f0, signal_index=8, argv=0x7fff3d3aa190) at kernel/qobject.cpp:3923 #19 0x7f4d81f1de2f in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7fff3d3aa190) at kernel/qobject.cpp:3983 #20 0x7f4d83e9eef5 in KFilePlacesEventWatcher::actionClicked (this=, _t1=...) at /usr/src/debug/kio-5.105.0/build/src/filewidgets/KF5KIOFileWidgets_autogen/include/moc_kfileplacesview_p.cpp:342 #21 0x7f4d83e9a2c9 in KFilePlacesEventWatcher::eventFilter (this=0x560aaf70f5f0, watched=, event=0x7fff3d3aa770) at /usr/src/debug/kio-5.105.0/src/filewidgets/kfileplacesview_p.h:263 #22 0x7f4d81eec6fb in QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x560aaf7846a0, event=event@entry=0x7fff3d3aa770) at kernel/qcoreapplication.cpp:1190 #23 0x7f4d82ba519e in QApplicationPrivate::notify_helper (this=this@entry=0x560aaf1d1350, receiver=receiver@entry=0x560aaf7846a0, e=e@entry=0x7fff3d3aa770) at kernel/qapplication.cpp:3634 #24 0x7f4d82bad5df in QApplication::notify (this=, receiver=, e=0x7fff3d3aa770) at kernel/qapplication.cpp:3084 #25 0x7f4d81eec978 in QCoreApplication::notifyInternal2 (receiver=0x560aaf7846a0, event=0x7fff3d3aa770) at kernel/qcoreapplication.cpp:1064 #26 0x7f4d82bab93e in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x560aaf7846a0, event=event@entry=0x7fff3d3aa770, alienWidget=, nativeWidget=0x560aaf6fde40, buttonDown=buttonDown@entry=0x7f4d830f2330 , lastMouseReceiver=..., spontaneous=true, onlyDispatc
[ghostwriter] [Bug 485962] New: ghostwriter segfaults
https://bugs.kde.org/show_bug.cgi?id=485962 Bug ID: 485962 Summary: ghostwriter segfaults Classification: Applications Product: ghostwriter Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: fe...@feldspaten.org Target Milestone: --- SUMMARY Running ghostwriter 24.02.2 on openSUSE Tumbleweed results in a segfault, already since before Plasma6. > $ ghostwriter SOMEFILE.md > QFontDatabase: Must construct a QGuiApplication before accessing QFontDatabase > [1]8613 IOT instruction (core dumped) ghostwriter SOMEFILE.md This is a follow-up of https://bugzilla.suse.com/show_bug.cgi?id=1215849, where someone has identified the problem as related to `libpbf.so`, where the QFontDatabase is accessed before creating the QGuiApplication (see https://bugzilla.suse.com/show_bug.cgi?id=1215849#c4). STEPS TO REPRODUCE 1. Run `ghostwriter` OBSERVED RESULT * `ghostwriter` crashes with SIGSEGV EXPECTED RESULT * ghostwriter starts without crashing SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.4 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 485962] ghostwriter segfaults
https://bugs.kde.org/show_bug.cgi?id=485962 --- Comment #1 from phoenix --- This might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=485691, however from the error message therein I cannot say for sure. -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 485962] ghostwriter segfaults
https://bugs.kde.org/show_bug.cgi?id=485962 --- Comment #2 from phoenix --- Backtrace: Thread 1 "ghostwriter" received signal SIGSEGV, Segmentation fault. 0x7fffec342307 in QKeySequence::operator=(QKeySequence const&) () from /lib64/libQt6Gui.so.6 (gdb) bt #0 0x7fffec342307 in QKeySequence::operator=(QKeySequence const&) () from /lib64/libQt6Gui.so.6 #1 0x7fffecac0eca in QAbstractButton::setShortcut(QKeySequence const&) () from /lib64/libQt6Widgets.so.6 #2 0x7fffecac0f61 in QAbstractButton::setText(QString const&) () from /lib64/libQt6Widgets.so.6 #3 0x555e0410 in ?? () #4 0x7fffeb7e8443 in ?? () from /lib64/libQt6Core.so.6 #5 0x555e981f in ?? () #6 0x7fffeca0e075 in QWidget::event(QEvent*) () from /lib64/libQt6Widgets.so.6 #7 0x7fffeca99532 in QFrame::event(QEvent*) () from /lib64/libQt6Widgets.so.6 #8 0x7fffec9c2f1e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt6Widgets.so.6 #9 0x7fffeb78f030 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt6Core.so.6 #10 0x7fffeca0985c in QWidgetPrivate::hide_helper() () from /lib64/libQt6Widgets.so.6 #11 0x7fffeca0b2aa in QWidgetPrivate::setVisible(bool) () from /lib64/libQt6Widgets.so.6 #12 0x55610aa3 in ?? () #13 0x5559da4e in ?? () #14 0x7fffeae2a1f0 in __libc_start_call_main () from /lib64/libc.so.6 #15 0x7fffeae2a2b9 in __libc_start_main_impl () from /lib64/libc.so.6 #16 0x5559df05 in ?? () -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483562] New: The behaviour of the pointer speed text input is weird
https://bugs.kde.org/show_bug.cgi?id=483562 Bug ID: 483562 Summary: The behaviour of the pointer speed text input is weird Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: fe...@feldspaten.org CC: natalie_clar...@yahoo.de Target Milestone: --- SUMMARY The behaviour of the pointer speed text input in the Mouse System Settings is weird and erratic: 1. Given the input `-0.65`, I'd like to change the 6 for a 7 When hitting backspace on the 6 the input becomes `-0.50` and the cursor moves all the way to the right. I would expect the input to be `-0.5` then and the cursor being between the dot and the 5 2. Given the input `-0.65`. If one removes the dot, the value becomes `-1.00`. I would expect that the text field allows temporarily values outside of the scope to help users type in values. 3. Starting from an empty text field, I would like to input the value `-0.65`. After typing `-0.6` the text field immediately completes to `-0.60`, even though I'm still typing. This results in the text value `-0.605` instead of `-0.65`. STEPS TO REPRODUCE See above OBSERVED RESULT See above EXPECTED RESULT See above SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed, Plasma (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.0.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #32 from phoenix. --- (In reply to Michail Vourlakos from comment #31) > If you increase the screen margin a lot, you get again blurred area for ALL > the screen margin? yes, sometimes. also, an interesting development, the blurred bar thing goes away on applications when using the breeze system theme but if "hide background when not needed" is enabled it comes back when the dock goes transparent/hides the background on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #34 from phoenix. --- (In reply to Michail Vourlakos from comment #33) > What is your Plasma theme in use? Here's a neofetch phoenix@manjaro --- OS: Manjaro Linux x86_64 Kernel: 5.10.19-1-MANJARO Uptime: 39 mins Packages: 1521 (pacman), 11 (flatpak), 9 (snap) Shell: zsh 5.8 Resolution: 1920x1080 DE: Plasma 5.21.2 WM: KWin WM Theme: WhiteSur-dark_x2.0 Theme: WhiteSurDark [Plasma], Breeze [GTK2/3] Icons: WhiteSur-dark [Plasma], WhiteSur-dark [GTK2/3] Terminal: konsole CPU: AMD Ryzen 5 3600X (12) @ 3.800GHz GPU: AMD ATI Radeon RX 470/480/570/570X/580/580X/590 Memory: 2674MiB / 15938MiB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493242] New: Window remains on disconnected monitor after waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=493242 Bug ID: 493242 Summary: Window remains on disconnected monitor after waking up from sleep Classification: Plasma Product: kwin Version: 6.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: fe...@feldspaten.org Target Milestone: --- SUMMARY If disconnecting a device from an external monitor while the device sleeps, the window remains on that screen, even if the screen is not present anymore. My laptop is connected to a docking station, which has two external monitors connected. If I open an application, e.g. Firefox on the external monitor, and then put the laptop to sleep, then disconnect it from the dock, then those windows remain on the virtual screen, but one cannot access them anymore. Plasma restricts itself to the laptop screen only, but the windows remain on the now disconnected screen, and cannot be moved nor restored. I tried to minimize the Firefox window and maximize it again to show up on the laptop screen but no success. One can see the maximize restore to move to where the external monitor was connected, but the window remains out of reach. I can only reproduce it when putting the laptop to sleep. STEPS TO REPRODUCE 1. Connect an external monitor, move Firefox on that display 2. Put computer to sleep 3. Disconnect the external monitor (or docking station) 4. Wake computer up 5. Firefox remains on the external monitor screen, no way to access it anymore OBSERVED RESULT After waking up from sleep, a window previously on an external monitor is not accessible anymore EXPECTED RESULT After waking up from sleeping, all windows will be moved to the remaining screens, if they are out of the available displays. It would be also a good idea to do the same check when maximising a window, so that minimizing and maximizing could become a last-resort option. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240915 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION In my setup the external monitors are connected through a docking station. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489904] New: New windows by default on wrong monitor
https://bugs.kde.org/show_bug.cgi?id=489904 Bug ID: 489904 Summary: New windows by default on wrong monitor Classification: Plasma Product: kwin Version: 6.1.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: fe...@feldspaten.org Target Milestone: --- SUMMARY After logging in, new windows appear on the first display but not on the main screen. When I open e.g. Konsole via Keyboard shortcut after logging in, the new Konsole window appears on the Laptop screen (which is the first screen from the left in my configuration) but not on the main screen, where the mouse and the taskbar are. I need to move the mouse around and click on the first screen to make new windows appear also on the main screen. The issue is only present before one moves the mouse. I can open and close the Konsole windows and they always appear on the first display BEFORE I do any mouse interaction. After moving the mouse on the main screen just a little, the Konsole window appears on the main window. STEPS TO REPRODUCE You need to have a multi-monitor setup. The first display must not be the main display. 1. Login to a new Plasma session 2. Open a application via keyboard shortcuts, do not move the mouse 3. New application will be opened on the first display OBSERVED RESULT New applications are opened on the first display EXPECTED RESULT New applications are opened on the main display, where also the mouse is located. SOFTWARE/OS VERSIONS openSUSE Tumbleweed 20240704 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490637] New: Kate displays newline at the end of file when there isn't
https://bugs.kde.org/show_bug.cgi?id=490637 Bug ID: 490637 Summary: Kate displays newline at the end of file when there isn't Classification: Applications Product: kate Version: 24.05.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: fe...@feldspaten.org Target Milestone: --- SUMMARY Kate displays a newline at the end of a file, even when there isn't one there. This is annoying when editing a yaml file where the linter expects you to have a newline at the end of the file. In kate the editor shows a newline at the end of the file, but the file contents don't have this newline. The annoying part is that even when adding a newline within kate, kate won't save it. So there is no way to make the yaml linter happy. The Setting "Append newline at end of file on save" In "Open/Save" does not seem to have an effect. STEPS TO REPRODUCE 1. Create new file with the following contents: ```yaml --- key: "value" ``` 2. Save the file 3. Kate will add a newline (Line 4) in the display 4. Check the file with any other editor, e.g. `vim`. The immaginary newline is not there 5. `yamllint` will complain about the missing newline OBSERVED RESULT * Newline is displayed but not saved * Enabling/Disabling the "Append newline at end of file on save" does not seem to have any effect on this issue EXPECTED RESULT * Newline is only displayed if present * If present, the newline character at the end of the file will be saved to disk SOFTWARE/OS VERSIONS openSUSE Tumbleweed 20240716 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490637] Kate displays newline at the end of file when there isn't
https://bugs.kde.org/show_bug.cgi?id=490637 phoenix changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from phoenix --- Sorry, this report was wrong. The "Append newline at end of file on save" does indeed work, the issue was on the side of a git hook that messed up the file before committing. Please ignore, Kate behaves just fine :-) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] New: Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 Bug ID: 434070 Summary: Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins. Product: lattedock Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: daksh...@gmail.com Target Milestone: --- Created attachment 136435 --> https://bugs.kde.org/attachment.cgi?id=136435&action=edit This is the layout I'm using. SUMMARY Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins. STEPS TO REPRODUCE 1. Get latte-dock 2. enable blur 3. make it a floating dock using screen margins OBSERVED RESULT It has a blurred bar kind of thing below the floating dock EXPECTED RESULT Floating dock with no blur inconsistencies SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Using kernel 5.10 and 5.11. RX590 if that helps. Dock layout in attachments. Using Official Community repository, package latte-dock-git -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 phoenix. changed: What|Removed |Added Alias||phoenix. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #1 from phoenix. --- Created attachment 136436 --> https://bugs.kde.org/attachment.cgi?id=136436&action=edit Demonstration This is a demonstration of what happens and what settings are there, even if I turn the background and blur off it still happens. P.S its a qr code ofr imgur, couldnt include links and video was too big. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #5 from phoenix. --- (In reply to Michail Vourlakos from comment #2) > 1. Where is the demonstration? no demonstration attached > 2. How will I reproduce in my system? the demonstration is attached, i put it as a qr code to scan as the video was too big. the qr code leads to imgur. i will put the url here for convenience. https://imgur.com/a/fTK4mZp -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #7 from phoenix. --- (In reply to Michail Vourlakos from comment #6) > (In reply to phoenix. from comment #5) > > (In reply to Michail Vourlakos from comment #2) > > > 1. Where is the demonstration? no demonstration attached > > > 2. How will I reproduce in my system? > > > > the demonstration is attached, i put it as a qr code to scan as the video > > was too big. the qr code leads to imgur. i will put the url here for > > convenience. > > https://imgur.com/a/fTK4mZp > > what is the bug in the video, I dont understand look at the bottom of the dock, when it is transparent, there's a bar with blur below it and when it has a background with blur it looks conjoined with the bar. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #8 from phoenix. --- (In reply to Michail Vourlakos from comment #4) > And please dont tell me you are using Manjaro package it is 8months old. Try > Latte git version from AUR. using package pulled from https://cgit.kde.org/latte-dock.git/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #10 from phoenix. --- (In reply to Michail Vourlakos from comment #9) > you mean the blur does not follow the background when sliding out? uhh no. there is a constant blurred bar when the dock is visible. i've included my layout so you could test. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #11 from phoenix. --- (In reply to phoenix. from comment #10) > (In reply to Michail Vourlakos from comment #9) > > you mean the blur does not follow the background when sliding out? > > uhh no. there is a constant blurred bar when the dock is visible. > i've included my layout so you could test. *blurred bar below the dock when the dock is visible -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 phoenix. changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #12 from phoenix. --- (In reply to phoenix. from comment #11) > (In reply to phoenix. from comment #10) > > (In reply to Michail Vourlakos from comment #9) > > > you mean the blur does not follow the background when sliding out? > > > > uhh no. there is a constant blurred bar when the dock is visible. > > i've included my layout so you could test. > > *blurred bar below the dock when the dock is visible if you look at the bottom bar on libreoffice around the part where it says "default page style" you can see it clearly. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 phoenix. changed: What|Removed |Added Version|unspecified |git (master) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 phoenix. changed: What|Removed |Added CC||daksh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #13 from phoenix. --- also another thing, the dock is hidden in this picture as well as it is transparent, this is the bar im talking about which shows up when youve left the dock hidden for some time (can fix by minimizing all windows and reaching the desktop with one windowed app open) and when you use the dock. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #14 from phoenix. --- (In reply to phoenix. from comment #13) > also another thing, the dock is hidden in this picture as well as it is > transparent, this is the bar im talking about which shows up when youve left > the dock hidden for some time (can fix by minimizing all windows and > reaching the desktop with one windowed app open) and when you use the dock. https://imgur.com/a/ORKJitf -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #15 from phoenix. --- another example - https://imgur.com/a/gwlZOlL -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #17 from phoenix. --- (In reply to Michail Vourlakos from comment #16) > 1. Please provide a full size video to understand what you are describing, > you can use Google Drive and DropBox to upload it and specify exactly the > second you observe the problem. The video is imgur is too low res and I can > not observe what you are describing. > 2. If you [disable] in Appearance advanced settings -> Hide background when > not needed, is it fixed for you? 1. yes i will 2. it does not. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #18 from phoenix. --- https://drive.google.com/file/d/1QzrdStlKki3RAaGhNIpiqJ7H_aWC3Znq/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #20 from phoenix. --- (In reply to Michail Vourlakos from comment #19) > Where did you find the package you installed for Latte git version? in Pacman, I installed using the terminal. when I see package details it is pulling the files from https://cgit.kde.org/latte-dock.git/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #22 from phoenix. --- (In reply to Michail Vourlakos from comment #21) > (In reply to phoenix. from comment #20) > > (In reply to Michail Vourlakos from comment #19) > > > Where did you find the package you installed for Latte git version? > > > > in Pacman, I installed using the terminal. when I see package details it is > > pulling the files from https://cgit.kde.org/latte-dock.git/ > > https://invent.kde.org/plasma/latte-dock this is the correct one, the > previous one I think is deprecated for more than five months for all kde > projects I'll try, if it still does the thing im gonna reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 phoenix. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 phoenix. changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #23 from phoenix. --- still happens, using aur git version. also tried kde gitlab version. still the same -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #25 from phoenix. --- (In reply to Michail Vourlakos from comment #24) > (In reply to phoenix. from comment #23) > > still happens, using aur git version. also tried kde gitlab version. still > > the same > > if you use Breeze as plasma theme is this reproducable? yes. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #26 from phoenix. --- (In reply to phoenix. from comment #25) > (In reply to Michail Vourlakos from comment #24) > > (In reply to phoenix. from comment #23) > > > still happens, using aur git version. also tried kde gitlab version. still > > > the same > > > > if you use Breeze as plasma theme is this reproducable? > > yes. you thing i wanted to ask though, can this be caused by kvantum? i think it might be registering the area where you hover to bring up the dock as a blur-able area of an application which in this case is latte -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #27 from phoenix. --- (In reply to phoenix. from comment #26) > (In reply to phoenix. from comment #25) > > (In reply to Michail Vourlakos from comment #24) > > > (In reply to phoenix. from comment #23) > > > > still happens, using aur git version. also tried kde gitlab version. > > > > still > > > > the same > > > > > > if you use Breeze as plasma theme is this reproducable? > > > > yes. > > you thing i wanted to ask though, can this be caused by kvantum? > i think it might be registering the area where you hover to bring up the > dock as a blur-able area of an application which in this case is latte *one -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #29 from phoenix. --- (In reply to Michail Vourlakos from comment #28) > (In reply to phoenix. from comment #26) > > (In reply to phoenix. from comment #25) > > > (In reply to Michail Vourlakos from comment #24) > > > > (In reply to phoenix. from comment #23) > > > > > still happens, using aur git version. also tried kde gitlab version. > > > > > still > > > > > the same > > > > > > > > if you use Breeze as plasma theme is this reproducable? > > > > > > yes. > > > > you thing i wanted to ask though, can this be caused by kvantum? > > i think it might be registering the area where you hover to bring up the > > dock as a blur-able area of an application which in this case is latte > > Oh... you could test this by changing to Breeze Application Style in plasma > systemsettings. I can understand now what is the issue but the thing is that > I can not reproduce it in my system... Let me see. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434070] Blurred bar at the bottom of the dock when blur is enabled and using "screen" margins.
https://bugs.kde.org/show_bug.cgi?id=434070 --- Comment #30 from phoenix. --- (In reply to phoenix. from comment #29) > (In reply to Michail Vourlakos from comment #28) > > (In reply to phoenix. from comment #26) > > > (In reply to phoenix. from comment #25) > > > > (In reply to Michail Vourlakos from comment #24) > > > > > (In reply to phoenix. from comment #23) > > > > > > still happens, using aur git version. also tried kde gitlab > > > > > > version. still > > > > > > the same > > > > > > > > > > if you use Breeze as plasma theme is this reproducable? > > > > > > > > yes. > > > > > > you thing i wanted to ask though, can this be caused by kvantum? > > > i think it might be registering the area where you hover to bring up the > > > dock as a blur-able area of an application which in this case is latte > > > > Oh... you could test this by changing to Breeze Application Style in plasma > > systemsettings. I can understand now what is the issue but the thing is that > > I can not reproduce it in my system... > > Let me see. still the same. also tried disabling kvantum. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493242] Window remains on disconnected monitor after waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=493242 --- Comment #3 from phoenix --- I just had this issue appear again, after disconnecting from the dock the Firefox window remained outside the laptop screen. After reconnecting the dock it was accessible again on the external monitor. After disconnecting the dock again, the window switched to the laptop screen. I observe that sleeping is not a requirement and this issue only happens occasionally. So far I cannot find a reliable reproducer, outside "it sometimes happens". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 493242] Window remains on disconnected monitor after waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=493242 --- Comment #2 from phoenix --- (In reply to Zamundaaa from comment #1) > Can't reproduce on git master. Does it happen 100% reliably for you? No, this appears to happen randomly. I just tried to reproduce this on two different laptops. On the first one where I first observed the issue, I could not reproduce the issue 4 times in a row. After almost giving up, I took the other laptop, that I just disconnected before from the dock, and there I could see it. So, this gives me a 1 out of 5 times. I've been trying the following approaches to rule out what the correct procedure could be, but so far none has shown consistency: * Have Firefox maximised or not * Putting laptop to sleep via closing the lid or via the menu * Locking the session before closing the lid Any ideas? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464903] Clipboard content gets automatically erased, when image is pasted to clipboard.
https://bugs.kde.org/show_bug.cgi?id=464903 --- Comment #6 from Phoenix Awakened --- (In reply to Nate Graham from comment #5) > Can you attach your /home/nate/.config/klipperrc file when you're using the > settings that you use to reproduce the bug? Sorry for responding late. I was out of station, for about a week for examination purposes, hence I didn't logged in to the PC. As soon as I opened the PC, I came here. See this : [General] IgnoreImages=true Version=5.26.90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464903] Clipboard content gets automatically erased, when image is pasted to clipboard.
https://bugs.kde.org/show_bug.cgi?id=464903 --- Comment #7 from Phoenix Awakened --- Also. If I select the option to "reset to default" , the bug was producible back then... -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] New: Gwenview opens through the panels.
https://bugs.kde.org/show_bug.cgi?id=458987 Bug ID: 458987 Summary: Gwenview opens through the panels. Product: gwenview Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: dewesh_2...@yahoo.in Target Milestone: --- Created attachment 151974 --> https://bugs.kde.org/attachment.cgi?id=151974&action=edit Screenshot of the Bug SUMMARY Gwenview opens out of the margins and panels on desktop STEPS TO REPRODUCE 1. Open any image( the first part of bug ). 2. Move the opened session of Gwenview with mouse to reduce the size, and then again maximize it. 3. Bug changes to another form. OBSERVED RESULT Gwenview opening out of the panels. EXPECTED RESULT It should fit in the panels. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS(x86_64) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Gwenview opens through the panels.
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #1 from Phoenix Awakened --- Created attachment 151975 --> https://bugs.kde.org/attachment.cgi?id=151975&action=edit Another form of the bug. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Gwenview opens through the panels.
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #3 from Phoenix Awakened --- (In reply to Nate Graham from comment #2) > A few questions: > 1. What is your screen resolution? 1360 x 780 > 2. Is your panel set to "Windows can Cover" mode? No, it is always visible. > 3. What window placement setting are you using? I don't know how to change > this, thus it should be in default state. > 4. What distro are you using? EndeavourOS. > 5. Does the issue happen if you use the default Breeze window decoration > theme? Yes. I had tried many themes. Also, I had tried 3-4 other image viewers, and had not encountered this bug with them. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Gwenview opens through the panels.
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #5 from Phoenix Awakened --- I thought I answered your questions by writing them in front of the questions ! Now I am pasting the answers along with the questions : > 1. What is your screen resolution? 1360 x 780. > 2. Is your panel set to "Windows can Cover" mode? No, it is set to "always > visible". > 3. What window placement setting are you using? I don't know how to change > this, thus it should be in default state. > 4. What distro are you using? EndeavourOS. > 5. Does the issue happen if you use the default Breeze window decoration > > theme? Yes. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Gwenview opens through the panels.
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #6 from Phoenix Awakened --- 1. What is your screen resolution? 1360 x 780. 2. Is your panel set to "Windows can Cover" mode? No, it is set to "always visible". 3. What window placement setting are you using? I don't know how to change this, thus it should be in default state. 4. What distro are you using? EndeavourOS. 5. Does the issue happen if you use the default Breeze window decoration theme? Yes. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Gwenview opens through the panels.
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #8 from Phoenix Awakened --- (In reply to Nate Graham from comment #7) What happens if you put your panel on the left or right side? Does the window open in a size that makes the bottom get cut off, or does the bottom of the window perfectly touch the bottom of the screen? If putting panel on left side, I had not seen Gwenview getting passed through that panel. But from the bottom side, some of the actions remain inaccessible, as I had described. And then everything is according to the detail I provided initially. Please see the attachment named as "Right Panel". It is how Gwenview looks as per your question. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Gwenview opens through the panels.
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #9 from Phoenix Awakened --- Created attachment 152207 --> https://bugs.kde.org/attachment.cgi?id=152207&action=edit Right Panel -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #11 from Phoenix Awakened --- (In reply to Nate Graham from comment #10) > Seems like the real issue is that Gwenview's minimum height is too tall. Can > reproduce that. Thanks for confirming the issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469492] Spectacle is failing to take screenshots of opened applications and other instances
https://bugs.kde.org/show_bug.cgi?id=469492 --- Comment #5 from Phoenix Awakened --- (In reply to Nate Graham from comment #4) > Looks like some kind of weird graphics glitch, maybe? The fact that the > overlay shows different content from what's on the screen is quite weird. Yes, this is what I wanted to show. It seems that the first screenshot is saved somewhere temporarily, despite the image is not saved in clipboard. I need to make 4-5 attempts in order to get the intended screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469492] New: Spectacle is failing to take screenshots of opened applications and other instances
https://bugs.kde.org/show_bug.cgi?id=469492 Bug ID: 469492 Summary: Spectacle is failing to take screenshots of opened applications and other instances Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: dewesh_2...@yahoo.in CC: k...@david-redondo.de Target Milestone: --- SUMMARY Today I was trying to take screenshots of my desktop's looks to share it with friend, but I was not able to take screenshots of the opened applications, as well as the application launcher and hidden icon collection, as Spectacle was only taking screenshot of the desktop only, and minimizing all the other tasks. STEPS TO REPRODUCE 1. Set the capture mode to "Rectangular Region" 2. Press the keybindings or PrtSc Key. 3. Open any application, but don't maximize them. 4. The resulted screenshot is of desktop only. 5. Tried the other capture modes, but still the same result. OBSERVED RESULT Screenshot of desktop only. EXPECTED RESULT Screenshot of all opened instances on desktop, including the elements like application launcher, tray icon's info page, etc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: CachyOS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Compositor: X11 Kernel: 6.3.0-5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #30 from Phoenix Awakened --- Created attachment 158802 --> https://bugs.kde.org/attachment.cgi?id=158802&action=edit Clear visibility of issue when panels are floating -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987 Phoenix Awakened changed: What|Removed |Added Attachment #158802|2023-05-09_20-38.png|abcd.png filename|| Attachment #158802|image/png |text/docx mime type|| -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987
--- Comment #31 from Phoenix Awakened ---
Comment on attachment 158802
--> https://bugs.kde.org/attachment.cgi?id=158802
Clear visibility of issue when panels are floating
>DOCX
>
>³.Þ£·k§ñ¨=¡oû YÙê
>ô~TÙ§§·Þö責ìÛå*É>t¤nY°ãxï^½ú
\(û+&n£jåÓæÙgCû8ÕÃGñ92Ru:.ª¶Mçý;Hü$ò¯GÉ7ÁûOëãlp>Ê«oé·NÿyäZOÿýÚ,+Úw6ýï}wËOÃE¡Äª¤óqÇËT";oÿö/ïÔF@ØwæSÊO¦oØt×É]Ò½_ïq²ØÄƸ¶5<Û¥¤
wm;T§.ÝMlâÐaÝsþëÖ³w;uFJÐzßè-«]ªþ½³ËǬÞó×®+ú[ÕÑ"']RºîÆ¥×SÃs_ß´ôìëð&7'EëR©¿÷»j©iòäèwvDÌðl[ìlÐÂíí·Î\,
>
ñö
¶Øxãa/÷ÿubwÝ·äî`îîyºIÎà{b:Ç¿vÎ1çÖ¦W°BLÐÒ2i¢*þZ^µ¿b±xf}(`C:'mêý¸#Df{ï1{ä±D+ïÀì£õ¬
ÀòúãȾëè®ýWàÙSFVkºé\!ò%2Ð
{Ó;Ôn§þ@YYé{ï.aУî3æËXóc¬ï*¢^ãG¼?Påäîêã,d»ý&xK´1Á{îìfðJ÷#ØÇ»Ìkp½Ô4 )6`Ö{pþ1ñD#0|¦a)ªÁf{j1ÖÙÀº
>óRÀ`]?4õ)&~¾ú*U
õÇ:À¾½ê*f,kÀ¸U{×Yk&j&OVf4½ñxkÐÉ68çÜ3ëXá\f
í Y°ààé|æ|®
¡!¬W°_f¯ãQ~Æû#-3Ø:Àä$·,rмa!4¦.ºg&°¯@Õ~é9mêzß1ªÎ¨Ú¥4_1o_OITûh&R++`Ç[ź7ö7¡AuÕ;üqiÉÃ÷öN
0ËM{ÌÐÆ,h¬r1pÚÔ[÷¼ßj6±MCu)c/õ×b5$ÓæèfÁf&Ö£×,~ÔßWç靈)wç͸A ã3
Yø²°`¥]\zÆYw
>ÀóÂk|õAqØ"Ps0L6çc»Í¡9¦îuܺhrÛg/kê!@Ó·{}SÀk]`SÅ)éÎ|Zc=8JÇ+æuÐ3$SWY`º>@³cõ)3ì
>³9.Kúµ+Pº3nùÞùlÊ:¶çõsÞY}
>À²LÎkÁ^~zÚGMκ
>ÌXæà/¨¤Öxæ2±ßP+±Ú»ßPõ/ùiZÐXóMðÒzczð©»fíjFOÓ²k3_À´ ²M©Y§øÀWÌ&ò3(Â0
aö}x,@S1ïCyÜöápÆPÇà©wrg챺Ï×4Ö>³Î¸¤?^±Ñ£
9ü"`"~fPz¾ÌѸ9Ú!ufÈjÑïkø)Ââñç,]
>À¬¡>§1°ÞßP»¿èZ];1¶®A-VW£öãð'`?d,LdJ$vðð1õi'0?űãuÁ2KMü×[Û4xbh¶&µqî¯au1Ø6X©Dø<ÿ,YlníSµûíuüòëo|}}5ί˰aVܤ®õ\2Ì°SSuwû
¼à×ùÙÕc°@«øO<|ìï#Ç÷ý}øÇ_6O:ÕF$dØEHÎÃìÝ;ÿ(,,`5BÞ³¼¶Y³dk¬IOмÏ_÷Zýç)&Ìç´LÅõ訨¯×
>½z¾üÚùyyÑ/3¬+^oØe:6ß7öÀÍæÿ°*I°(ÀÌxx(àÁÃÇtîÀ[ÀHhÈ4ÒÔ¼Ì{´Y-%\}ß«ukB½½Ã¬Ù³)
>¨è¨¨?vl+//éÚõ_öðWÈWb¢ûu³¯oEKüç³Õ
>lÅÊUîBsÊÛÿYó©>ýÌìa#F ÔåKQìø¼¼\ëã}Ö«õö̳ÄPÉúfÌÑ;pÃC
>@g¨oÙXz+p
CEBaïÐ>^ÞÞi)wÁô³;tX¶x¼Z¾xé²³fÿµûÏO?sþÜÙÇÚÚÚ¹{¸WUI몿·t)M»»ûû~øOä)¹L6gîAK¿%¯-^¶|æ¬Ù;¶ÿ¦R©Ø"6^Nÿ=uy5À
0pÇC
>@æúËoÈÞ¬fÏÒ`Øî}*''ç~L¾ìâÒªwhèÞ¿vBÎýûÏäiOÙì·ÍÏË0 ,5åNZjêìû²
>g?ó\fzÖ¥ç]BCûìÙýgM#gÿòÔSeeeZCÓxgbfÇ,öC
>Ï
>À\3á!ú5{Ñc¢/½nmÇN.|»²¢Ð´Xlëêê¶hñ7ßz"Ry¹ùÚúë¯#Gzgñ2itç¿'\×j*,<¢]`Û/¿øB®PÅbWW··,]¸hq]#B¡î?/&ÕÇä}Á?V49s-PãsG#L
ML¤Þ¹8uÆ¿û¦ºZV\\øÓ\ÓjòØçN6|ä˯½ñÅÕ§|ýü¦MùÇöß
>)Bª««úá÷ø¸XÝÃm4VÝ2=Ý®ÉYíÃæØ3é¡SÏl¢)<,oø4;f
R¢T*9Ô;´OyYiâõÉS¦zy{B]üýD"aûÀb±½B¡¼wïR¡
ê/¾ØNüìÜâcc¯_OP)/+»~ýÚä)Ó¼¼½Õøù0as|ÁjMøB`ÈÔYÓ&OPüfy`ÑÀèn´º|vvö
ÏL9óÖÍ[{ÿúkÚé_ü÷k'gç²²Òû÷äåå5jèð4M>.=x`ßÚµT·Ð©s>}ûUwï6bäHBHzVúÿ¾újïî¿1cíëÕØ·çAö}6²ðßÐ)&JÏ2~A÷¼Æ7¹<¢ºtéιrÝÝ~ÈçMYDütÝï,ÛÔ]6ÒÞÓ´±úÎè9Gë|i¤]ÚXýmê¹ÌZÓj¥¯ojúÕø¢uD©TÎßûÝöÙËd<`Uæí^¿uæb¡Ph
·o°ÅÆÐI³ô÷-c.E(ã|Ã
>únÎ÷çÙd¸#?>u䲿î:loïc:éLÚÀØE~æZ?NñÔ4ûv¨¿±©¨»
>eà¡ÃwÐ_í¥ÀÖ&âáZxÕXÞþåé±¥íìÇ££9C¬¿¯£wKÿ)3îo)À|?£¹P¼1i¥ëw:{iÂ{ÂæÀâù¬û2Ü«¹\7ÿ×[·÷á¢z°çíq£G7cRú"iÃócǽ¹óªi-ÛJpAZ¤+]3.®÷(ãÁ3<ú
>håíÖïOåýÃþÎR6õ0àÉ"jÑWãÀÏÜrcÔMX
>§nOËcò@UXÍÉgXØx±Ú¼\LfBÐ:¸4õöî-#>ëÙàôöÁï=ñ°HjãÙyð³ko§LÝöú[ûZ¿ôvÛÄ¿NßÈQxô¾ð9Ë[ÿ8O|Î}ïÝiAvÈr.þþóS׳Ëm¼BF<¿èÕâ&ú`¬~;@.(P|Ï`9ÍQC'ôáðéÌ`´]
> ³Ö3¾à
>$¤Îy®}Ù¿_-où»Êê6¦Ï?)Ptìûog׬¨º²õ§XÞCC[˲¯l_±øTÏCº»UdÛòÛ¿Å4%ÿþñ»â=ç¾³`GÆ¡¯>ÝqKÖ
¬XL4`¼´Ï nK ´ð°(å~M
% C¦{uzaÞé-Ý õß¾ÓVÿðÉÂçfÎzuî` ¥xS»Z@0õÝo.ü`Þ@{BD]ýèÝ7½7§§
å>,P)Ϲ/·ë7gÁSÃÇÌ;Ü~u9+
@ÿO°f¬g³Ü°Aq#E(ÐÀa«hÔSý~F!°ü4ÍJEÛÍ|eÌéGl>Ú!ĶöüÁÅ¿þuéÎÃJ¹\VIÓNõß¾~¾BBDv%òñuÊÉÉB«h¢(.,QyÔº§'®S§\©ZüÓÕz²Rj7y5ëCb®,Uñ³L0_Ñoj§%
вQ¡ÏÏxá«Ëþ^&&ÄBÝðå®»þ/¸*ÂóÞË¿8YQChSÎZ¡½ÐÕÍ¢ªû¿¶ú¹®6µÄoñ
_Ë_`9ü¬vÍ7PÑ|ãëæMîb0æ°Ù@WY=Ç0ùZ0ûeeÔ¬÷WÊäJB EiÞODZxL
Mȱím*®Ùs!)õîĨ'+íð/4µà»}õF&<Ïhm¤:UXîO¨]ÑXØl
À4À¼YfH0ùÕÉu÷ó)ÉÐç_ó]ÝòÅú=÷CçLôc1߶óók>7È9óøo?ý°y÷¿YÄÙÿz
*¤K÷¦A¦ÎçXföaCºêl6ðÎ`]½Ý:Ìä#é.ÅúqlS}¸¯oJúÆÍð/7'EëR©¿÷»í³5ÉxÀªÌÛ½~ëÌÅBíõz
xû[l<µàY&á>_WqÖÚ9ͱ7VÞG²¸oÏ|´`IHèÅû£MëÙÖe1rÆý¯%05fÐâS;ö¤5Âeá-úôôÆjÛ
«`}93¦(f_ÁG?úW«óòA8µÀn2Â,²î2yBã³]BB&Núõk9·_Yøg°A¤v:Ú4½-è«õ·bhm¬n¬TTósLcê,é'Ô%4u
YþÁG_ý÷sÛg¥)&èÎèîÁD-
¹Ü§¡u×ÓO¤'#ÂO@»ëM¬Rß¾}zÀZlllS¦¦Ôñ¿Î,ÀÊ÷ßM¾uËÄöù¢3xä=/
Â#"&LÜ.0¢99Ù;wì¸s[kCzYÂ2OÁ$gÀ6
{LFÐlágæ|hILJ¨çÿï?|Ls!úþ¿««õÄÿúÔåx2Á3G¿ó߯^R©H`ÀܹÚ÷²ÙtÆmQã|EUû³Ëö\Ï3
>Xÿóÿß²Ï4ÔþÓí;TJ+u~vGi3gîÛ³ká+¯äç?z}ᢼÜü×^·èWmD¶/¾üª
!ÄÙɹkî¶êÅçIºqãõ7ßriåªîíãöø|X
®òLª°{b¡fñl@Sñ0cüߨ_g'çÊJYµLÇiJxæä©ë×®UWKÛøHÜ$§Nªª.¯¨8zä`ûöAÞÞ)BT*å¹3gryä©b[q@@Û}°ýëhLÙX;}3á'`¡ø¿éî3鶬¼ÜÁÑA}?_R¡ÌÏÏS¿vrrªÉ¤Uê·¥¥eÐNRQQQ®>^UU%Ëì4G`ì>9·S:^1c<@é;a¤YU0?)frÿߤ±IÔý¬,'GçN;ë, Åй×Ýý{W¢£^zõ5[[ñõø8¹RéíÓº¨
P«Xö½{¹ù¹cÆOÜõ;D"ÑøS22ÓóórÅb{@8|Äèëñ×JKKG+feeé7dýÁùéÝ.þÆñÐ䫨δHTmlZ
*ª;¶äÌóÜ;ï.'4þóÿ+,(Ь(VþúóÏsç½ôËíØ«W¶mÙ"ÉÅbûêêê´®öjí±éçÊJktÙ
f¸3?£sÎô0BCãÖ2A"Àd
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987 Phoenix Awakened changed: What|Removed |Added Attachment #158802|text/docx |image/png mime type|| --- Comment #32 from Phoenix Awakened --- Comment on attachment 158802 --> https://bugs.kde.org/attachment.cgi?id=158802 Clear visibility of issue when panels are floating It seems that the Gwenview is not considering the panel is boundary for expansion. What if we make the editing options for Gwenview in Drop-down Menu ? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469492] Spectacle is failing to take screenshots of opened applications and other instances
https://bugs.kde.org/show_bug.cgi?id=469492 --- Comment #2 from Phoenix Awakened --- (In reply to Nate Graham from comment #1) > I'm having a hard time following your steps to reproduce. Could you rephrase > them, or else take a video that shows the issue happening? Thanks! Yes, it does need some rephrasing !! Actually issue is something like that spectacle is saving up the first screenshot temporarily, even though no content is pasted on clipboard. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469492] Spectacle is failing to take screenshots of opened applications and other instances
https://bugs.kde.org/show_bug.cgi?id=469492 --- Comment #3 from Phoenix Awakened --- Sorry @NateGraham Uploading video was not possible as it was 6.11 MB. So I am sharing a link on which I had uploaded the video. The website says that it will expire after 6 days. https://easyupload.io/jjzv29 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464556] Visual glitch when file/folder summary is viewed by hovering or when widows are stacked over each other
https://bugs.kde.org/show_bug.cgi?id=464556 --- Comment #2 from Phoenix Awakened --- I have a similar screenshot of it. I am attaching it for reference Version : 22.12.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464556] Visual glitch when file/folder summary is viewed by hovering or when widows are stacked over each other
https://bugs.kde.org/show_bug.cgi?id=464556 --- Comment #3 from Phoenix Awakened --- Created attachment 155560 --> https://bugs.kde.org/attachment.cgi?id=155560&action=edit Reference for the glitch -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464556] Visual glitch when file/folder summary is viewed by hovering or when widows are stacked over each other
https://bugs.kde.org/show_bug.cgi?id=464556 --- Comment #4 from Phoenix Awakened --- The glitch you can see there is the same like what I am able to see on the Dolphin. I tried to record the video by simplescreenrecorder before reporting, but it failed to create the video with some sort of error :-/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464556] Visual glitch when file/folder summary is viewed by hovering or when widows are stacked over each other
https://bugs.kde.org/show_bug.cgi?id=464556 --- Comment #5 from Phoenix Awakened --- Created attachment 155561 --> https://bugs.kde.org/attachment.cgi?id=155561&action=edit Latest Image -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464556] Visual glitch when file/folder summary is viewed by hovering or when widows are stacked over each other
https://bugs.kde.org/show_bug.cgi?id=464556 --- Comment #6 from Phoenix Awakened --- I tried to record the video from mobile, but size had exceeded 58 MB !! Though I managed to take a photo while recording, this clearly shows the glitch. It is named as latest. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464556] Visual glitch when file/folder summary is viewed by hovering or when widows are stacked over each other
https://bugs.kde.org/show_bug.cgi?id=464556 --- Comment #8 from Phoenix Awakened --- (In reply to Nate Graham from comment #7) > 23.04 release. Thanks for fixing it out. But what I am missing, because I am not able to fetch this version despite the fact that I had kept KDE-unstable repository enabled ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464886] New: Settings Tab of Konsole goes through the panel, due to which few options are not visible
https://bugs.kde.org/show_bug.cgi?id=464886 Bug ID: 464886 Summary: Settings Tab of Konsole goes through the panel, due to which few options are not visible Classification: Plasma Product: kwin Version: 5.26.90 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: dewesh_2...@yahoo.in Target Milestone: --- Created attachment 155692 --> https://bugs.kde.org/attachment.cgi?id=155692&action=edit Image of the bug SUMMARY Whenever I open the settings of Konsole, or any other application, then the appeared tab goes through the panel. STEPS TO REPRODUCE 1. Open Konsole 2. Select Settings Tab 3. Visible Bug OBSERVED RESULT Window goes through panel EXPECTED RESULT Normal Size SOFTWARE/OS VERSIONS Linux/KDE Plasma: CachyOS KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-1 Graphics Platform: X11 Screen Size: 1366x768 ADDITIONAL INFORMATION 1. Also I want to mention that I am also not able to resize the aspect ratio of the opened tabs. 2. This error occurs with other applications as well, but it is more prominent in Konsole. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 464886] Settings Tab of Konsole goes through the panel, due to which few options are not visible
https://bugs.kde.org/show_bug.cgi?id=464886 Phoenix Awakened changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |zrenf...@gmail.com Product|kwin|Active Window Control Version|5.26.90 |unspecified CC||plasma-b...@kde.org Component|compositing |General -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464886] Settings Tab of Konsole goes through the panel, due to which few options are not visible
https://bugs.kde.org/show_bug.cgi?id=464886 Phoenix Awakened changed: What|Removed |Added Target Milestone|--- |4.11 Version|unspecified |5.26.90 Assignee|zrenf...@gmail.com |kwin-bugs-n...@kde.org Product|Active Window Control |kwin Component|General |activities -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464903] New: Clipboard content gets automatically erased, when image is pasted to clipboard.
https://bugs.kde.org/show_bug.cgi?id=464903 Bug ID: 464903 Summary: Clipboard content gets automatically erased, when image is pasted to clipboard. Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dewesh_2...@yahoo.in Target Milestone: --- SUMMARY Clipboard content gets automatically erased, when image is pasted to clipboard. STEPS TO REPRODUCE 1. Copy some text to Clipboard. 2. Take a screenshot and paste it to clipboard. 3. Now again copy some text. 4. All Clipboard content is erased. OBSERVED RESULT No clipboard content. EXPECTED RESULT Availability of Clipboard contents. SOFTWARE/OS VERSIONS Linux/KDE Plasma: CachyOS KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The bug persists even with default settings. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464903] Clipboard content gets automatically erased, when image is pasted to clipboard.
https://bugs.kde.org/show_bug.cgi?id=464903 --- Comment #2 from Phoenix Awakened --- (In reply to Nate Graham from comment #1) > When you say "All Clipboard content is erased", did you mean that the image > was erased? Or was other text content erased too? Yes everything is erased. To verify its occurrence just now, firstly I took a screenshot of the desktop. Then, copied some text and all of sudden clipboard disappeared from the panel along with its content. One important point which I want to mention is, this error only happens if the first copied content is image via a screenshot only. If already something else is copied, then this does not occurs. So, if you take a screenshot and keep it in clipboard, and then copying text removes the entire clipboard. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464557] Konsole's setting menu too small to save the changes
https://bugs.kde.org/show_bug.cgi?id=464557 Phoenix Awakened changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Phoenix Awakened --- *** This bug has been marked as a duplicate of bug 464886 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464886] "Edit Profile" window's minimum height is too tall to fit within a 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=464886 --- Comment #2 from Phoenix Awakened --- *** Bug 464557 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464903] Clipboard content gets automatically erased, when image is pasted to clipboard.
https://bugs.kde.org/show_bug.cgi?id=464903 --- Comment #4 from Phoenix Awakened --- All of them were getting erased. But, I had pondered about you said last time for configuring the Clipboard settings. Therefore, I did the following 2 points as per your previous suggestion : 1. Text selection always save in history 2. Non-text selection always save in history. By enabling both of these altogether, the issue was fixed. But I wonder, why those options are not enabled by default ? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987 Phoenix Awakened changed: What|Removed |Added Target Milestone|--- |2.9 -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 461506] New: White Line in floating Panel.
https://bugs.kde.org/show_bug.cgi?id=461506 Bug ID: 461506 Summary: White Line in floating Panel. Classification: Plasma Product: plasma-integration Version: 5.26.2 Platform: Other OS: Other Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dewesh_2...@yahoo.in Target Milestone: --- Created attachment 153525 --> https://bugs.kde.org/attachment.cgi?id=153525&action=edit Image of the issue. Hello. I usually use dark themes, but recently I am using light themes which are translucent and I am getting white line in middle of the panel, when it is set to floating. In non-floating mode, it is normal. The attached image is of plasma theme named, " WhiteSur ", though any of other translucent theme result in same output. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461506] White Line in floating Panel.
https://bugs.kde.org/show_bug.cgi?id=461506 --- Comment #1 from Phoenix Awakened --- One more observation which I want to share is that : this thick bar only appears on panel height below 30. Above 30, it vanishes. And 30 is the last value for panel height where the bar appears. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461506] White Line in floating Panel.
https://bugs.kde.org/show_bug.cgi?id=461506 --- Comment #3 from Phoenix Awakened --- (In reply to veggero from comment #2) Oh. If this is the reason, then it might be applicable to other Plasma themes. Thanks for pointing out this to me. Also, can I link this with the stuttering which I get in translucent light themes ? I am not able to record it or capture it, as changing the task removes the flashes. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464556] New: Visual glitch when file/folder summary is viewed by hovering or when widows are stacked over each other
https://bugs.kde.org/show_bug.cgi?id=464556 Bug ID: 464556 Summary: Visual glitch when file/folder summary is viewed by hovering or when widows are stacked over each other Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dewesh_2...@yahoo.in Target Milestone: --- SUMMARY When I am trying to see the summary of the file/folders, the visual glitch is observed in form of distortion. It can be only viewed if the translucency is active over the Dolphin as well. STEPS TO REPRODUCE 1. Open Dolphin. 2. Hover the mouse over the desired file/folder 3. Start scrolling OBSERVED RESULT Glitch in the appearance, it can be removed if we minimize and maximize the file manager again. EXPECTED RESULT Normal appearance. SOFTWARE/OS VERSIONS Linux/KDE Plasma: CachyOS KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.12.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Kernel : 6.1.7-1 Graphics Platform : Wayland Screen Size : 1366 x 768 WM Theme : Breeze I also want to mention that the glitch is not present when we use X11 mode. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464557] New: Konsole's setting menu too small to save the changes
https://bugs.kde.org/show_bug.cgi?id=464557 Bug ID: 464557 Summary: Konsole's setting menu too small to save the changes Classification: Applications Product: konsole Version: 22.12.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: dewesh_2...@yahoo.in Target Milestone: --- Created attachment 155456 --> https://bugs.kde.org/attachment.cgi?id=155456&action=edit Appearance of problem. SUMMARY I am not able to see the options which are present at bottom side of Konsole's settings. This trouble is prominent in every other menu. STEPS TO REPRODUCE 1. Open Konsole. 2. open settings. 3. Visible error. OBSERVED RESULT Some component of settings are not visible for application(s). EXPECTED RESULT Normal appearance. SOFTWARE/OS VERSIONS Linux/KDE Plasma: CachyOS KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Screen Size : 1366 x 768 Graphics Platform : X11/Wayland Theme: Breeze -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461506] Visual glitch in floating panel when using small panel thickness and Plasma theme with extremely large corner radius
https://bugs.kde.org/show_bug.cgi?id=461506 --- Comment #8 from Phoenix Awakened --- (In reply to Nate Graham from comment #5) > A few questions for you: > 1. Does it happen if you make the panel non-floating? No. > 2. Does it happen with the Breeze Plasma theme? No. > 3. Was the a previous Plasma version (e.g. 5.25) where this worked properly > with WhiteSur? This issue happen with many Plasma themes which have increased Transparency/translucency. I usually see panels begin to flicker if I open multiple windows each over other in smaller size, in maximized mode it appears infrequently as flickers when scrolling. To check it even more, I also changed the window decorations to translucent one and even they were showing the flickering. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461506] Visual glitch in floating panel when using small panel thickness and Plasma theme with extremely large corner radius
https://bugs.kde.org/show_bug.cgi?id=461506 --- Comment #9 from Phoenix Awakened --- Also, sometimes I had seen that, those Plasma themes which light and translucent/transparent catches the impression of cursor, but it disappears if I open another window/task. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415875] System Setting crash
https://bugs.kde.org/show_bug.cgi?id=415875 Tidus Phoenix changed: What|Removed |Added CC||phoenix.ti...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369475] Resizing the Krita window hangs for about 10-20 seconds after a long period of not resizing the window
https://bugs.kde.org/show_bug.cgi?id=369475 --- Comment #5 from Phoenix Enero --- Hi, sorry for lack of responses. I have not encountered this bug in my work for the past several months. I think the version 4 update fixed it in general. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386977] New: Pen lag at the start and just after the end of each stroke
https://bugs.kde.org/show_bug.cgi?id=386977 Bug ID: 386977 Summary: Pen lag at the start and just after the end of each stroke Product: krita Version: 3.3.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: phoenix.en...@gmail.com Target Milestone: --- Created attachment 108891 --> https://bugs.kde.org/attachment.cgi?id=108891&action=edit Lag on the start of each stroke in a group I noticed this lag happens once and doesn't happen for succeeding strokes until I focus out or do any type of keyboard shortcut commands. This is especially noticeable with very fast strokes. Tablet: HUION H610 PRO @ version 12.3 drivers (latest from huiontablet.com) with "Support TabletPC" enabled (not like it does anything with or without it.) I'm using the default WinTab input and OpenGL canvas. You'll see in the attachment, the first stroke in each row has a straight line near the first. Even without smoothing the lag on the initial stroke is visibly longer than the rest of the segmented stroke. I tested on Photoshop and it doesn't have this problem. Another thing I noticed while drawing any stroke: the cursor freezes just after I finish it with or without smoothing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386977] Pen lag at the start and just after the end of each stroke
https://bugs.kde.org/show_bug.cgi?id=386977 --- Comment #1 from Phoenix Enero --- correction: "the first stroke in each row has a straight line near the beginning of the stroke" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386977] Pen lag at the start and just after the end of each stroke
https://bugs.kde.org/show_bug.cgi?id=386977 --- Comment #3 from Phoenix Enero --- Created attachment 108964 --> https://bugs.kde.org/attachment.cgi?id=108964&action=edit Opened Krita, drew several lines with couple of undoes. Here ya go. Opened Krita, drew several lines with couple of undoes. Strokes after each undo were jagged in the start of the stroke. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386977] Pen lag at the start and just after the end of each stroke
https://bugs.kde.org/show_bug.cgi?id=386977 Phoenix Enero changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Phoenix Enero --- Fixed. Seems to be a HUION issue as it appears on other programs (Photoshop just hides it better) Solution was unchecking `Support TabletPC` in the HUION Driver settings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 380069] New: [Brush-Presets-Docker] [Feature Request] No-thumbnail list view for brush presets docker
https://bugs.kde.org/show_bug.cgi?id=380069 Bug ID: 380069 Summary: [Brush-Presets-Docker] [Feature Request] No-thumbnail list view for brush presets docker Product: krita Version: 3.1.3 Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: phoenix.en...@gmail.com Target Milestone: --- I do not rely on the thumbnails much, so having no-thumbnail display allows you to display more brush presets at a time in the docker. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459441] New: KDE windows etc are still visible after resume, and before the screen is locked
https://bugs.kde.org/show_bug.cgi?id=459441 Bug ID: 459441 Summary: KDE windows etc are still visible after resume, and before the screen is locked Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: h...@webnet.org.uk Target Milestone: --- Not sure where this fits. SUMMARY When I close my laptop lid, the machine suspends. When I open it, all my windows are visible with potentially sensitive information for a second or so before the screen lock kicks in. STEPS TO REPRODUCE 1. Turn on the computer 2. Do something 3. Close the lid 4. Wait for the machine to suspend 5. Open the lid 6. Observe sensitive data OBSERVED RESULT The whole screen is visible for > 500ms before the lock screen kicks in. Someone not privileged to see that information could view some of that information, or if they've observed the effect a few times they could be prepared with a mobile phone or camera. EXPECTED RESULT The screen should be cleared (or overlaid with a black window) before the machine suspends, so that it's still clear inbetween resume and screen lock. I don't know if it's possible but it would be a good addition. This is not a new behaviour, so it's not practical to list all the versions of KDE with which this behaviour could be observed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486896] New: Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78
https://bugs.kde.org/show_bug.cgi?id=486896 Bug ID: 486896 Summary: Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78 Classification: Applications Product: dolphin Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: h...@webnet.org.uk CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install nvidia driver 550.78 2. Open Dolphin 3. Browse to SMB OBSERVED RESULT The Dolphin tab displays the message "The process for the smb://a.b.c.d protocol died unexpectedly." Crash report appears in systray: "kioslave5 Closed Unexpectedly." KDE Crash Handler reports this Developer Information: Application: kioslave5 (kioslave5), signal: Segmentation fault [KCrash Handler] #4 0x7a932e25c618 in ?? () from /lib/x86_64-linux-gnu/libnvidia-tls.so.550.78 #5 0x732e36312d465455 in ?? () #6 0x7a9331e3006f in __gconv_transform_internal_ascii (step=0xec81481574d3d1, data=0x48f0e08348ca2918, inptrp=0x8948098be8e7, inend=0x7ffc9caa2290 "@#\252\234\374\177", outbufstart=0x24b1e8e78948, irreversible=0x89482723e8c7, do_flush=1401505809, consume_incomplete=726164680) at ../iconv/skeleton.c:547 Backtrace stopped: previous frame inner to this frame (corrupt stack?) [Inferior 1 (process 1552475) detached] EXPECTED RESULT None of the above. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION libnvidia-tls.so is for Thread Local Storage. Renaming it to prevent it being loaded solves the problem, but why is it being loaded? This seems like a pretty terrible scenario. Some external component is causing undesirable behaviour, but when that component is unavailable, everything works. So literally anything has the potential to break kioslave5. Should kioslave5 be ignoring exceptions while trying to load libraries at this point? Is there a way to blacklist libraries so kioslave5 doesn't try to load them? (I doubt I can get away with removing the thread local storage lib systemwide - I could try it, but I don't expect it'll be pretty.) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486896] Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78
https://bugs.kde.org/show_bug.cgi?id=486896 Hugh Phoenix-Hulme changed: What|Removed |Added CC||h...@webnet.org.uk Platform|Other |Ubuntu -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #51 from Hugh Phoenix-Hulme --- Killing one is working for me, but it's not a great solution. To minimise hassle one could write a script to kill the first process if there are multiple and run it as a cron job every second, but that's obviously not ideal. I'm also seeing this on Ubuntu, not Arch. But generally only after resuming, not just from locking, and not consistently. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Hugh Phoenix-Hulme changed: What|Removed |Added CC||h...@webnet.org.uk --- Comment #49 from Hugh Phoenix-Hulme --- I'm getting this now, and I do see two instances of kscreenlocker_greet. I also see plasmashell and dolphin using high CPU at the same time. Next time it occurs I'll kill one and see if that solves for the other. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434586] New: PSD filters (Multiply, Screen) not working as expected in this very specific example
https://bugs.kde.org/show_bug.cgi?id=434586 Bug ID: 434586 Summary: PSD filters (Multiply, Screen) not working as expected in this very specific example Product: krita Version: 4.4.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: h...@webnet.org.uk Target Milestone: --- SUMMARY When loading a PSD file the output is completely different to PhotoShop (not just a bit different) STEPS TO REPRODUCE 1. Load the PSD (100MB): https://www-sub-etha-link.s3-eu-west-1.amazonaws.com/ascension+ebook+source.psd 2. Compare with the PNG (5.2MB): https://www-sub-etha-link.s3-eu-west-1.amazonaws.com/ascension-ebook-cover.png 3. Note that the PSD doesn't look right when loaded in Krita. OBSERVED RESULT Krita's representation of the PSD is much too bright and the vector objects are barely perceivable. EXPECTED RESULT Expected Krita's representation of the PSD to match the PNG output from PhotoShop. SOFTWARE/OS VERSIONS Windows: macOS: Big Sur 11.2.3 Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Both macOS and Linux information supplied because I've tried it on both. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434586] PSD filters (Multiply, Screen) not working as expected in this very specific example
https://bugs.kde.org/show_bug.cgi?id=434586 --- Comment #2 from Hugh Phoenix-Hulme --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417439] New: NVidia causes Plasma to crash while lockscreen is on
https://bugs.kde.org/show_bug.cgi?id=417439 Bug ID: 417439 Summary: NVidia causes Plasma to crash while lockscreen is on Product: plasmashell Version: 5.17.90 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: h...@webnet.org.uk CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.90) Qt Version: 5.12.5 Frameworks Version: 5.66.0 Operating System: Linux 5.4.0-12-generic x86_64 Windowing system: X11 Distribution: Ubuntu Focal Fossa (development branch) -- Information about the crash: - What I was doing when the application crashed: I had locked the screen and headed off to work. Upon returning, I had the screen that told me to log in with a tty and use loginctl to unlock the session. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55b40b578c44) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 [Current thread is 1 (Thread 0x7f06fbe93340 (LWP 3144))] Thread 28 (Thread 0x7f0666bfc700 (LWP 26921)): #0 0x7f06ff448c3f in __GI___poll (fds=0x7f06540038b0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f06dfa571c6 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f06dfa48831 in pa_mainloop_poll () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f06dfa48eb3 in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f06dfa48f60 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f06dfa5710d in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f06df7b736c in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.0.so #7 0x7f06fec72669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f06ff455333 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f06d1e10700 (LWP 25263)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f06f401e474) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f06f401e420, cond=0x7f06f401e448) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f06f401e448, mutex=0x7f06f401e420) at pthread_cond_wait.c:638 #3 0x7f06ff7cbb3f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f06ff7cbc31 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f07014bf0f9 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f07014bf39d in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f06ff7c5a02 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f06fec72669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f06ff455333 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f065700 (LWP 20747)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b40cda33b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b40cda3360, cond=0x55b40cda3388) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b40cda3388, mutex=0x55b40cda3360) at pthread_cond_wait.c:638 #3 0x7f06ff7cbb3f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f06ff7cbc31 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f06e8bca050 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f06e8bcdd4e in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f06e8bc9222 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f06e8bcbcb3 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f06ff7c5a02 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f06fec72669 in start_thread (arg=) at pthread_create.c:479 #11 0x7f06ff455333 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f0667fff700 (LWP 20746)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b40cda33b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b40cda3360, cond=0x55b40cda3388) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b40cda3388, mutex=0x55b40cda3360) at pthread_cond_wait.c:638 #3 0x7f06ff7cbb3f in QWaitCondition::wait(QMutex*, QDeadl
[dolphin] [Bug 486896] Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78
https://bugs.kde.org/show_bug.cgi?id=486896 --- Comment #11 from Hugh Phoenix-Hulme --- > consume_incomplete=726164680) at ../iconv/skeleton.c:547 This is the same call site, I guess we'll see if nvidia determine if it's their code or not. I can't tell if it's a glibc issue, an nvidia issue, or an alike issue in both kioslave and KiCad. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486896] Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78
https://bugs.kde.org/show_bug.cgi?id=486896 --- Comment #13 from Hugh Phoenix-Hulme --- (In reply to Emil from comment #12) > New response from the NVIDIA people: > > As a workaround, can you please try to set __GL_CONSTANT_FRAME_RATE_HINT=3 ? > Adding this to my `/etc/environment` file worked for me. Thanks for the update! That works for me for both Dolphin and KiCad. This should probably be closed but I don't know if there's a process. @TraceyC will know. There might be implications for it being closed when others could still experience and report the issue (until nvidia fix it) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486896] Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78
https://bugs.kde.org/show_bug.cgi?id=486896 --- Comment #4 from Hugh Phoenix-Hulme --- I don't get as far as credentials. For me this occurs with a Synology NAS (the same as the other referenced issue) but also with an Ubuntu server. Synology NAS allows guest on my LAN, Ubuntu server has my public key. Still occurs with nvidia 550.120. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486896] Browsing SMB causes kioslave5 to throw errors in libnvidia-tls.550.78
https://bugs.kde.org/show_bug.cgi?id=486896 --- Comment #8 from Hugh Phoenix-Hulme --- (In reply to Emil from comment #6) > I just encountered the very same backtrace when trying to launch KiCad. Also > with driver version 470 (and possibly others between 470 and 535, I only > tested 470 and 535 upwards) both this as well as the problem with KiCad > disappear. Nvidia seems to be at fault here. Was it still kioslave that threw the exception? When I try to run it KiCad throws a segfault with no stacktrace, unless I run it with `valgrind -v kicad` and then it doesn't segfault... > I reported this to NVIDIA (https://developer.nvidia.com/bugs/4887556). I'm > not sure if anyone except me and NVIDIA can access this though... I can't. It tells me that if I want to access it, I have to be a member of "one of the following programmes" but then lists nothing. -- You are receiving this mail because: You are watching all bug changes.
