[kaffeine] [Bug 485395] New: Kaffeine crash while Steam client window is visible and/or overlapping with Kaffeine's window.
https://bugs.kde.org/show_bug.cgi?id=485395 Bug ID: 485395 Summary: Kaffeine crash while Steam client window is visible and/or overlapping with Kaffeine's window. Classification: Applications Product: kaffeine Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mche...@kernel.org Reporter: raulvior@gmail.com Target Milestone: --- Application: kaffeine (2.0.18) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.4-rc1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: If I run Kaffeine with the Steam client window visible Kaffeine crashes. I'm running GNOME Desktop under a Wayland session. The windowing system reported by About Kaffeine dialog is xcb. The crash can be reproduced every time. -- Backtrace: Application: Kaffeine (kaffeine), signal: Segmentation fault [KCrash Handler] #4 __memset_avx2_unaligned_erms () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:170 #5 0x7f3bdf0b62c4 in () at /usr/lib64/dri/radeonsi_drv_video.so #6 0x7f3bdee6d716 in () at /usr/lib64/dri/radeonsi_drv_video.so #7 0x7f3c26a5fa4d in vaEndPicture () at /lib64/libva.so.2 #8 0x7f3c19565e6a in () at /lib64/libavcodec.so.58.134 #9 0x7f3c195705fa in () at /lib64/libavcodec.so.58.134 #10 0x7f3c1973ecf5 in () at /lib64/libavcodec.so.58.134 #11 0x7f3c192e52cf in () at /lib64/libavcodec.so.58.134 #12 0x7f3c194aa7f7 in () at /lib64/libavcodec.so.58.134 #13 0x7f3c55292bb2 in start_thread (arg=) at pthread_create.c:447 #14 0x7f3c5531400c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 15 (Thread 0x7f3c4d8ff6c0 (LWP 7038) "kaffeine"): #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7f3bd8035e90, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7f3c5528f09f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f3bd8035e90, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7f3c55291d40 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f3bd8035e40, cond=0x7f3bd8035e68) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x7f3bd8035e68, mutex=0x7f3bd8035e40) at pthread_cond_wait.c:618 #5 0x7f3c54ffc9f0 in () at /lib64/libvlccore.so.9 #6 0x7f3c55292bb2 in start_thread (arg=) at pthread_create.c:447 #7 0x7f3c5531400c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 14 (Thread 0x7f3c46a006c0 (LWP 7037) "threaded-ml"): #1 __GI___libc_read (fd=49, buf=0x7f3c469ff9ce, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f3c4de5f78f in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-17.0.so #3 0x7f3c4dee7d7e in pa_mainloop_prepare () at /lib64/libpulse.so.0 #4 0x7f3c4dee80c8 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #5 0x7f3c4dee8180 in pa_mainloop_run () at /lib64/libpulse.so.0 #6 0x7f3c4def7e19 in () at /lib64/libpulse.so.0 #7 0x7f3c4de9589f in () at /usr/lib64/pulseaudio/libpulsecommon-17.0.so #8 0x7f3c55292bb2 in start_thread (arg=) at pthread_create.c:447 #9 0x7f3c5531400c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 13 (Thread 0x7f3c4da006c0 (LWP 7036) "kaffeine"): #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7f3b80010870, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7f3c5528f09f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f3b80010870, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7f3c55291d40 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f3b800108d0, cond=0x7f3b80010848) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x7f3b80010848, mutex=0x7f3b800108d0) at pthread_cond_wait.c:618 #5 0x7f3c19203c73 in () at /lib64/libavcodec.so.58.134 #6 0x7f3c19203ec8 in avcodec_send_packet () at /lib64/libavcodec.so.58.134 #7 0x7f3c2c1d0b84 in () at /usr/lib64/vlc/plugins/codec/libavcodec_plugin.so #8 0x7f3c54ffc457 in () at /lib64/libvlccore.so.9 #9 0x7f3c54ffbf16 in () at /lib64/libvlccore.so.9 #10 0x7f3c54ffc94b in () at /lib64/libvlccore.so.9 #11 0x7f3c55292bb2 in start_thread (arg=) at pthread_create.c:447 #12 0x7f3c5531400c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 12
[kaffeine] [Bug 479663] New: Kaffeine crashes when closing the DVB-T EPG dialog.
https://bugs.kde.org/show_bug.cgi?id=479663 Bug ID: 479663 Summary: Kaffeine crashes when closing the DVB-T EPG dialog. Classification: Applications Product: kaffeine Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mche...@kernel.org Reporter: raulvior@gmail.com Target Milestone: --- Application: kaffeine (2.0.18) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: Linux 6.6.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I'm running Kaffeine under a Wayland session with Gnome in OpenSuse Tumbleweed. Kaffeine itself is running under the xcb windowing system as per the "About Kaffeine" window. Sometimes when I click on the close button of the EPG window Kaffeine crashes. The crash can be reproduced sometimes. -- Backtrace: Application: Kaffeine (kaffeine), signal: Segmentation fault [KCrash Handler] #4 0x7f171188c08c in QAbstractItemModelPrivate::removePersistentIndexData(QPersistentModelIndexData*) () at /lib64/libQt5Core.so.5 #5 0x7f171188c559 in QPersistentModelIndex::~QPersistentModelIndex() () at /lib64/libQt5Core.so.5 #6 0x7f17118a4a50 in () at /lib64/libQt5Core.so.5 #7 0x7f1711896f99 in QItemSelectionModel::~QItemSelectionModel() () at /lib64/libQt5Core.so.5 #8 0x7f171191728e in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #9 0x7f17125e2686 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #10 0x7f1712880c09 in QTreeView::~QTreeView() () at /lib64/libQt5Widgets.so.5 #11 0x7f171191728e in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #12 0x7f17125e2686 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #13 0x55c3dd72bc15 in DvbEpgDialog::~DvbEpgDialog() (this=0x55c3e02d41a0, this=) at /usr/src/debug/kaffeine-2.0.18git.20230531T022124~afc6c12/src/dvb/dvbepgdialog.cpp:171 #14 DvbEpgDialog::~DvbEpgDialog() (this=0x55c3e02d41a0, this=) at /usr/src/debug/kaffeine-2.0.18git.20230531T022124~afc6c12/src/dvb/dvbepgdialog.cpp:171 #15 0x7f17119194b7 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7f17125a51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #17 0x7f17118ed938 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #18 0x7f17118f0f31 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #19 0x7f1711947063 in () at /lib64/libQt5Core.so.5 #20 0x7f170ff13f30 in () at /lib64/libglib-2.0.so.0 #21 0x7f170ff15b58 in () at /lib64/libglib-2.0.so.0 #22 0x7f170ff1620c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #23 0x7f1711946876 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #24 0x7f17118ec3cb in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #25 0x7f17118f4860 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #26 0x55c3dd6e9830 in main(int, char**) (argc=, argv=) at /usr/src/debug/kaffeine-2.0.18git.20230531T022124~afc6c12/src/main.cpp:238 [Inferior 1 (process 5194) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 447112] Very low framerate (fps) in kamoso
https://bugs.kde.org/show_bug.cgi?id=447112 Marcos Raul Carot changed: What|Removed |Added CC||marcos.ca...@gmail.com --- Comment #5 from Marcos Raul Carot --- I have the same issue and I think that, at least for my webcam it is because Kamoso sets the Pixel Format to YUYV when the native mode of my camera is MJPG. In other webcam software that lets me choose the format, in YUYV shows the same slownes, but changing it to MJPG works fine. There should be an option in Kamoso to set it, and ideally that would be saved in the config file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 --- Comment #67 from Raul José Chaves --- > I didn't see any indication that this bug is exclusive to AMD, and bug > 469016 is not exclusive to NVIDIA either, but I'll follow up there. For me, it actually seems related to NVIDIA, I was having this issue with my 1660s all the time, after I switched to my 6700XT without changing any other component the issue was gone, with the same setup, on manjaro, using the classic task manager ungrouped. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459137] Sometimes my mouse cursor start to move very slow and flinch
https://bugs.kde.org/show_bug.cgi?id=459137 Raul José Chaves changed: What|Removed |Added CC||rjchave...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459137] Sometimes my mouse cursor start to move very slow and flinch
https://bugs.kde.org/show_bug.cgi?id=459137 --- Comment #1 from Raul José Chaves --- Some info I forgot to mention, I'm using 2 monitors with different refresh rates and I'm using this workaround https://bugs.kde.org/show_bug.cgi?id=433094#c15 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459137] New: Sometimes my mouse cursor start to move very slow and flinch
https://bugs.kde.org/show_bug.cgi?id=459137 Bug ID: 459137 Summary: Sometimes my mouse cursor start to move very slow and flinch Product: kwin Version: 5.25.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: rjchave...@gmail.com Target Milestone: --- SUMMARY Sometimes my mouse cursor starts to move very slow and flinch, I'm now sure how to reproduce since this happens at random, I think it happens about 1 time per hour for 10 or 20 seconds and every time this happens I find the log below on journalctl set 15 02:26:35 user kwin_x11[727]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 50694, resource id: 16941108, major code: 14 (GetGeometry), minor code: 0 set 15 02:26:35 user kwin_x11[727]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50693, resource id: 16941108, major code: 3 (GetWindowAttributes), minor code: 0 set 15 02:26:35 user kwin_x11[727]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 50690, resource id: 16941108, major code: 14 (GetGeometry), minor code: 0 set 15 02:26:35 user kwin_x11[727]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50689, resource id: 16941108, major code: 3 (GetWindowAttributes), minor code: 0 SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.15.65-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 I will try to downgrade to check if I'm able to reproduce this in older versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Raul José Chaves changed: What|Removed |Added CC||rjchave...@gmail.com --- Comment #38 from Raul José Chaves --- I'm having the exactly same symptoms right now, I'm not sure the issue was resolved. Operating System: Manjaro Linux KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.15.52-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450914] Wayland, games on Nvidia are force vsynced
https://bugs.kde.org/show_bug.cgi?id=450914 Raul José Chaves changed: What|Removed |Added CC||rjchave...@gmail.com --- Comment #21 from Raul José Chaves --- (In reply to Samuel from comment #7) > I also noticed something interesting. In Fullscreen and Borderless modes, > VSync is being forced in Plasma while the Windowed mode doesnt have this > problem. Windowed mode has uncapped FPS similar to other compositors. I'm not experiencing this, Guild Wars 2 is locking my fps both in windowed and full screen mode. KDE on Xorg and Gnome on Wayland are working with uncapped FPS -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 397594] Kaffeine plays video in a separate window under Wayland
https://bugs.kde.org/show_bug.cgi?id=397594 Raul changed: What|Removed |Added CC||raulvior@gmail.com --- Comment #13 from Raul --- This bug persists in Ubuntu 22.04 LTS with QT_QPA_PLATFORM=wayland. Kaffeine 2.0.18 GNOME 42.1 libVLC 3.0.16 Wayland Qt 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449222] SystemSettings5 Crashes in KCMPlymouth::save()
https://bugs.kde.org/show_bug.cgi?id=449222 --- Comment #2 from Raul Perez --- Created attachment 146233 --> https://bugs.kde.org/attachment.cgi?id=146233=edit New crash information added by DrKonqi systemsettings5 (5.23.5) using Qt 5.15.3 - What I was doing when the application crashed: I was changing the plymouth theme for my KDE Neon System -- Backtrace (Reduced): #4 doActivate(QObject*, int, void**) (sender=0x56472d1d77b0, signal_index=20, argv=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:132 [...] #6 0x7fabea21d117 in KCMPlymouth::busyChanged() (this=this@entry=0x56472d1d77b0) at ./obj-x86_64-linux-gnu/src/kcm_plymouth_autogen/EWIEGA46WW/moc_kcm.cpp:299 #7 0x7fabea21e993 in KCMPlymouth::setBusy(bool const&) (busy=, this=0x56472d1d77b0) at ./src/kcm.cpp:165 #8 KCMPlymouth::save() (this=0x56472d1d77b0) at ./src/kcm.cpp:208 #9 0x7fac30347d46 in KCModuleQml::save() (this=0x56472e2b3650) at /usr/include/c++/9/bits/unique_ptr.h:360 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449222] SystemSettings5 Crashes in KCMPlymouth::save()
https://bugs.kde.org/show_bug.cgi?id=449222 Raul Perez changed: What|Removed |Added CC||raulytstat...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 383929] KMail crash when using Configuration tool
https://bugs.kde.org/show_bug.cgi?id=383929 --- Comment #5 from Raul Pavel --- Created attachment 146019 --> https://bugs.kde.org/attachment.cgi?id=146019=edit New crash information added by DrKonqi kmail (5.19.1 (21.12.1)) using Qt 5.15.3 - What I was doing when the application crashed: entered Configuration menu, selected the last 2 plugins and clicked `Apply` -- Backtrace (Reduced): #4 0x7fd005b36458 in ConfigurePluginsListWidget::changeAgentActiveState (this=0x555df62d1be0, agentIdentifier=..., path=..., enable=false) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1078 #5 0x7fd005b36864 in ConfigurePluginsListWidget::saveAkonadiAgent (this=0x555df62d1be0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:570 #6 0x7fd005b36dbb in ConfigurePluginsListWidget::save (this=0x555df62d1be0) at ./src/configuredialog/configureplugins/configurepluginslistwidget.cpp:148 #7 0x7fcffaa930bf in KCModuleProxy::save (this=this@entry=0x555df660d8d0) at ./src/kcmoduleproxy.cpp:281 #8 0x7fcffaa97430 in KCMultiDialogPrivate::apply (this=) at ./src/kcmultidialog.cpp:382 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 383929] KMail crash when using Configuration tool
https://bugs.kde.org/show_bug.cgi?id=383929 Raul Pavel changed: What|Removed |Added CC||pavel.sebast...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441528] New: Ability to chose profile when using the "Load a new tab with..."
https://bugs.kde.org/show_bug.cgi?id=441528 Bug ID: 441528 Summary: Ability to chose profile when using the "Load a new tab with..." Product: konsole Version: 21.08.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: marcos.ca...@gmail.com Target Milestone: --- Created attachment 141033 --> https://bugs.kde.org/attachment.cgi?id=141033=edit Current menu under "New Tab" that would be great to have under the other menues When you have many profiles you may want to use the (awesome) tab bar options to "Load a new tab with layout x" with different profiles. A drop-down menu like the one for "New Tab" showing the profiles would be nice if added to the "Load a new tab with layout x" buttons as well. Attached is a screenshot of the current menu under "New Tab" that would be great to have under the other menues. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 350732] windows, activated from krunner, doesn't get focus
https://bugs.kde.org/show_bug.cgi?id=350732 Raul changed: What|Removed |Added CC||raul.chelegu...@gmail.com --- Comment #10 from Raul --- Just wanted to leave a workaround here for readers, AndydeCleyre mentioned in reddit and it seems to work: try to set System Settings > Window Behavior > Focus stealing prevention: None. -- You are receiving this mail because: You are watching all bug changes.
[kcron] [Bug 432679] New: Kcron misinterprets certain crontab comments as jobs
https://bugs.kde.org/show_bug.cgi?id=432679 Bug ID: 432679 Summary: Kcron misinterprets certain crontab comments as jobs Product: kcron Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: g...@meyer.net Reporter: 1000.onther...@gmail.com Target Milestone: --- SUMMARY Kcron misinterprets some crontab comments as jobs, ignoring the hash character. STEPS TO REPRODUCE 1. Close Kcron/System Settings if it's already running. 2. Using the command line, edit your user's crontab (crontab -e). 3. Write this comment at the end of the file: # - - - * randomtext 4. Close the editor, wait for your crontab to be updated and open Kcron. OBSERVED RESULT In Kcron, the comment appears as a disabled job, with "- - - *" as scheduling and "randomtext" as command. It completely ignores the # hash character. EXPECTED RESULT As any comment, it should never be shown as a job, but ignored or used as "description" if it's right above a given job. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo (profile default/linux/amd64/17.1/desktop/plasma stable, kernel 5.4.92) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kcron version (as shown in package manager): 20.08.3:5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427454] ksystemstats spam the logs
https://bugs.kde.org/show_bug.cgi?id=427454 Marcos Raul Carot Collins changed: What|Removed |Added CC||marcos.ca...@gmail.com --- Comment #1 from Marcos Raul Carot Collins --- I have the same issue -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425385] Desktop freezes after taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=425385
Raul <1000.onther...@gmail.com> changed:
What|Removed |Added
CC||1000.onther...@gmail.com
--- Comment #10 from Raul <1000.onther...@gmail.com> ---
I can confirm this. Same steps as @Nick Stefanov did and it freezes for 2-4
seconds (though cursor does move), and also can confirm @Antonio's workaround
works. Thanks!
Launched from a terminal, no message shows up until I hit the "Save as.."
button. Then, these warnings:
kf.kio.core: "Could not enter folder tags:/."
kf.kio.widgets.kdirmodel: No node found for item that was just removed:
QUrl("file:///tmp/somerandomfileofmine")
libpng warning: iCCP: known incorrect sRGB profile
kf.kio.widgets.kdirmodel: protocol mismatch: "" vs "file"
Last line, the protocol mismatch one, repeats every 3-4 seconds even if I don't
click "Save". After that, Spectacle closes normally.
There is no high CPU usage, no visible time_wait (after all, I'm saving my
screenshots into /tmp and that directory is a TMPFS) and, after doing a PERF
(record and report), nothing relevant shows up there.
System: Gentoo stable
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Spectacle Version: 20.04.3
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation
https://bugs.kde.org/show_bug.cgi?id=422050 --- Comment #10 from Raul Laasner --- Here's a another merge request that fixes the issue: https://invent.kde.org/graphics/okular/-/merge_requests/242 It's been waiting for a few weeks now. Here's my own solution which makes kinetic scrolling optional: https://invent.kde.org/raullaasner/okular/-/commit/bb921dfbc64c691ef4575587a15a94234b197234 It's similar to the another ones so I didn't start another merge request. Just using it until the official fix comes out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423301] SDDM shows no blur and the account picture is not rounded after waking up the computer
https://bugs.kde.org/show_bug.cgi?id=423301 Raul changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #9 from Raul --- This bug affects KDE 5.18.5 and I can't upgrade it since newer versions aren't available in Kubuntu Backports -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423873] New: Display resolution
https://bugs.kde.org/show_bug.cgi?id=423873 Bug ID: 423873 Summary: Display resolution Product: systemsettings Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ragaggi...@yahoo.com.ar Target Milestone: --- SUMMARY i can't change monitor resolution STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423679] Breeze Dark is not displaying text correctly in open window dialog for GTK applications
https://bugs.kde.org/show_bug.cgi?id=423679 --- Comment #1 from Raul --- Sorry, the steps to reproduce are wrong! STEPS TO REPRODUCE 1. Change to Breeze Dark in Settings > Plasma theme (GTK2/GTK3 theme settings doesn't affect this) 2. Open a GTK application > Open File 3. Go to a folder that has files (it can't be just folders) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423679] New: Breeze Dark is not displaying text correctly in open window dialog for GTK applications
https://bugs.kde.org/show_bug.cgi?id=423679 Bug ID: 423679 Summary: Breeze Dark is not displaying text correctly in open window dialog for GTK applications Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cosmic-e...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 129777 --> https://bugs.kde.org/attachment.cgi?id=129777=edit breeze dark wrong text color SUMMARY STEPS TO REPRODUCE 1. Change GTK2/GTK3 to Breeze Dark in Settings > Plasma Theme > GTK2/GTK3 theme settings 2. Open a GTK application > Open File 3. Go to a folder that has files (it can't be just folders) OBSERVED RESULT Filenames being displayed in the wrong color. EXPECTED RESULT Filenames being displayed in the correct color. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423604] System Settings doesn't open after installing an icon pack from the repository
https://bugs.kde.org/show_bug.cgi?id=423604 --- Comment #1 from Raul --- Created attachment 129735 --> https://bugs.kde.org/attachment.cgi?id=129735=edit settings not opening Just individual sections open. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423604] New: System Settings doesn't open after installing an icon pack from the repository
https://bugs.kde.org/show_bug.cgi?id=423604 Bug ID: 423604 Summary: System Settings doesn't open after installing an icon pack from the repository Product: systemsettings Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: cosmic-e...@outlook.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install an icon pack, like sudo apt-get install papirus-icon-theme 2. Try to launch System Settings OBSERVED RESULT Settings opening. EXPECTED RESULT Settings doesn't open. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423371] After pressing log out from Kickoff, the logout executes after several seconds of delay
https://bugs.kde.org/show_bug.cgi?id=423371 --- Comment #2 from Raul --- But the bug also happens when I close all windows -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423370] After pressing log out from Kickoff, the system takes a lot of time to log out
https://bugs.kde.org/show_bug.cgi?id=423370 --- Comment #5 from Raul --- since I couldn't* -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423370] After pressing log out from Kickoff, the system takes a lot of time to log out
https://bugs.kde.org/show_bug.cgi?id=423370 --- Comment #4 from Raul --- I filed a new one, seems I couldn't find a edit option: https://bugs.kde.org/show_bug.cgi?id=423371 SUMMARY STEPS TO REPRODUCE I haven't be able to reproduce. It seems to happen when a lot of Chrome/Chromium tabs are opened or possibly more than one program opened. The bug happens when logging out without closing the any window opened. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423371] New: After pressing log out from Kickoff, the logout executes after several seconds of delay
https://bugs.kde.org/show_bug.cgi?id=423371 Bug ID: 423371 Summary: After pressing log out from Kickoff, the logout executes after several seconds of delay Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cosmic-e...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE I haven't be able to reproduce. It seems to happen when a lot of Chrome/Chromium tabs are opened or possibly more than one program opened. The bug happens when logging out without closing the any window opened. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423370] After pressing log out from Kickoff, the system takes a lot of time to log out
https://bugs.kde.org/show_bug.cgi?id=423370 --- Comment #3 from Raul --- Ops, sorry! Can I deleted this? I pasted the content from my other bug report, but for some reason the s KDE site didn't write my changes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423370] After pressing log out from Kickoff, the logout executes after several seconds of delay
https://bugs.kde.org/show_bug.cgi?id=423370 --- Comment #2 from Raul --- Ops, sorry. The system takes a lot of time to log out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423370] After pressing log out from Kickoff, the system takes a lot of time to log out
https://bugs.kde.org/show_bug.cgi?id=423370 Raul changed: What|Removed |Added Summary|After pressing log out from |After pressing log out from |Kickoff, the logout |Kickoff, the system takes a |executes after several |lot of time to log out |seconds of delay| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423370] New: After pressing log out from Kickoff, the logout executes after several seconds of delay
https://bugs.kde.org/show_bug.cgi?id=423370 Bug ID: 423370 Summary: After pressing log out from Kickoff, the logout executes after several seconds of delay Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cosmic-e...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE I haven't be able to reproduce. The bug seems to happen when multiple tabs of Google Chrome/Chromium are opened. OBSERVED RESULT Window's content is transparent/glitched. EXPECTED RESULT Make the content to not be transparent. Maybe adding a "loading" text is a solution. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423369] New: Sometimes keyboard keys hangs on the pressed state, causing unwanted behaviors in the system
https://bugs.kde.org/show_bug.cgi?id=423369 Bug ID: 423369 Summary: Sometimes keyboard keys hangs on the pressed state, causing unwanted behaviors in the system Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cosmic-e...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE Unfortunately I haven't able to reproduce it. It happens occasionally. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION This seems to not be a problem with my computer. I bought it recently and this bug goes away after logging out. The keyboard keys get pressed in the point that I can't even use Control+Alt+Backspace because there is another key being "pressed". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421937] In GTK applications that use CSD, pointing the cursor to the top right edge of the window doesn't select the close button
https://bugs.kde.org/show_bug.cgi?id=421937 --- Comment #1 from Raul --- Is there anyone who has this bug? I'm not seeing anyway to fix it ): -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 423366] New: Spectable doesn't copy the screenshot to the clipboard when pressing Meta + Printscreen
https://bugs.kde.org/show_bug.cgi?id=423366 Bug ID: 423366 Summary: Spectable doesn't copy the screenshot to the clipboard when pressing Meta + Printscreen Product: Spectacle Version: 20.04.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: cosmic-e...@outlook.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Make sure Spectacle windows is closed 2. Open a window and press Meta + Printscreen 3. Hit Control + V in a program that supports pasting pictures like WhatsApp/Telegram web, etc. OBSERVED RESULT The last screenshot will be copied or the last screenshot will be pasted from the last time Spectacle was opened EXPECTED RESULT The last/correct screenshot image being copied to the clipboard. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: KDE 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423301] SDDM shows no blur and the account picture is not rounded after waking up the computer
https://bugs.kde.org/show_bug.cgi?id=423301 --- Comment #6 from Raul --- It only showed this packages: The following packages will be upgraded: kde-spectacle libokular5core9 okular okular-extra-backends I'm using Kubuntu 20.04, what's wrong? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423301] SDDM shows no blur and the account picture is not rounded after waking up the computer
https://bugs.kde.org/show_bug.cgi?id=423301 --- Comment #5 from Raul --- Wow, I can't believe this!! I can have the latest KDE without breaking my system!!! Thanks, I'm gonna test it! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423301] SDDM shows no blur and the account picture is not rounded after waking up the computer
https://bugs.kde.org/show_bug.cgi?id=423301 --- Comment #3 from Raul --- Thanks for the response* -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423301] SDDM shows no blur and the account picture is not rounded after waking up the computer
https://bugs.kde.org/show_bug.cgi?id=423301 --- Comment #2 from Raul --- No, I use Kubuntu and I don't want to break my system. Is this PPA official from the KDE team? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 423301] New: SDDM shows no blur and the account picture is not rounded after waking up the computer
https://bugs.kde.org/show_bug.cgi?id=423301 Bug ID: 423301 Summary: SDDM shows no blur and the account picture is not rounded after waking up the computer Product: kde Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: indigowaterf...@outlook.com Target Milestone: --- Created attachment 129559 --> https://bugs.kde.org/attachment.cgi?id=129559=edit no blur no rounded account picture SUMMARY STEPS TO REPRODUCE Unfortunately I'm not able to reproduce. I happens "randomly" after waking up the computer, when it's locked and when it's inactive for a few minutes. OBSERVED RESULT No blur and no rounded account picture. EXPECTED RESULT Blurred background and rounded account picture. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422602] In Kickoff favorites section, after right clicking on a item, there is a delay to show the menu
https://bugs.kde.org/show_bug.cgi?id=422602 --- Comment #3 from Raul --- @Alexander Lohnau Yes, the bug always happens in the first open (in start of the session). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422927] The window to select devices to share files via bluetooth is showing with an incorrect size
https://bugs.kde.org/show_bug.cgi?id=422927 --- Comment #2 from Raul --- I'm using Breeze, but with Layan colour scheme. Don't think colour schemes affect this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422992] If the SDDM theme installation is cancelled, a blank window appears with no message
https://bugs.kde.org/show_bug.cgi?id=422992 --- Comment #2 from Raul --- Created attachment 129369 --> https://bugs.kde.org/attachment.cgi?id=129369=edit installation cancelled, but no message is shown -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422992] If the SDDM theme installation is cancelled, a blank window appears with no message
https://bugs.kde.org/show_bug.cgi?id=422992 --- Comment #1 from Raul --- This also happens if a theme installation is from a tar.gz file, I forgot to mention that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422992] New: If the SDDM theme installation is cancelled, a blank window appears with no message
https://bugs.kde.org/show_bug.cgi?id=422992 Bug ID: 422992 Summary: If the SDDM theme installation is cancelled, a blank window appears with no message Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: raul94go...@outlook.com.br CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Go to Settings > Global Theme 2. Install a theme that also includes a SDDM theme, like McMojave 3. When the admin password is asked, press cancel OBSERVED RESULT A blank window will appear, with no message, only with a exclamation icon. EXPECTED RESULT A message being shown. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: KDE 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422936] New: When the window is maximized, the close button doesn't hover when pointing the cursor to the top right edge of the screen
https://bugs.kde.org/show_bug.cgi?id=422936 Bug ID: 422936 Summary: When the window is maximized, the close button doesn't hover when pointing the cursor to the top right edge of the screen Product: kwin Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: raul94go...@outlook.com.br Target Milestone: --- Created attachment 129326 --> https://bugs.kde.org/attachment.cgi?id=129326=edit close button not being hovered SUMMARY STEPS TO REPRODUCE 1. Install a custom window decoration theme like Arc, McMojave, Layan or Sweet Dark 2. Maximize the window 3. Point the cursor to the top right of the screen OBSERVED RESULT The close button isn't in the hover state when pointing the mouse the to the top right edge of the screen. EXPECTED RESULT The close button being in the hover state when pointing the mouse the to the top right edge of the screen. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Only Breeze default window decoration doesn't have this problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422927] New: The window to select devices to share files via bluetooth is showing with an incorrect size
https://bugs.kde.org/show_bug.cgi?id=422927 Bug ID: 422927 Summary: The window to select devices to share files via bluetooth is showing with an incorrect size Product: dolphin Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: raul94go...@outlook.com.br CC: kfm-de...@kde.org Target Milestone: --- Created attachment 129320 --> https://bugs.kde.org/attachment.cgi?id=129320=edit wrong size SUMMARY STEPS TO REPRODUCE 1. Open Dolphin 2. Right click on a file > share > send via bluetooth; OBSERVED RESULT Wrong window side, is cropping the header text. Resizing doesn't help, after closing the window and reopening, the size is not even remembered. EXPECTED RESULT Correct window size. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: KDE 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422144] Clock and system tray icons are misaligned in the left of the taskbar, for a short moment, after logging in
https://bugs.kde.org/show_bug.cgi?id=422144 --- Comment #2 from Raul --- (In reply to Konrad Materka from comment #1) > Is this really a problem? It is a part of booting process, elements are > loaded and starts in parallel, it takes only fraction of second. At the end > all elements are there correctly placed. It depends. KDE emphasizes animations a lot, so this looks a bit unpolished -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421937] In GTK applications that use CSD, pointing the cursor to the top right edge of the window doesn't select the close button
https://bugs.kde.org/show_bug.cgi?id=421937 Raul changed: What|Removed |Added Summary|In applications that use|In GTK applications that |CSD, pointing cursor to the |use CSD, pointing the |top right edge of the |cursor to the top right |window doesn't select the |edge of the window doesn't |close button|select the close button -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422602] In Kickoff favorites section, after right clicking on a item, there is a delay to show the menu
https://bugs.kde.org/show_bug.cgi?id=422602 Raul changed: What|Removed |Added Summary|In KLauncher favorites |In Kickoff favorites |section, after right|section, after right |clicking on a item, there |clicking on a item, there |is a delay to show the menu |is a delay to show the menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422602] In Kickoff favorites section, after right clicking on a item, there is a delay to show the menu
https://bugs.kde.org/show_bug.cgi?id=422602 --- Comment #1 from Raul --- I meant Kickoff, not KLauncher. Sorry! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422602] New: In KLauncher favorites section, after right clicking on a item, there is a delay to show the menu
https://bugs.kde.org/show_bug.cgi?id=422602 Bug ID: 422602 Summary: In KLauncher favorites section, after right clicking on a item, there is a delay to show the menu Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: raul94go...@outlook.com.br CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY - STEPS TO REPRODUCE 1. Logout and login 2. Open KLauncher 3. Right click in a item in the favorites section OBSERVED RESULT The menu will show with a delay. EXPECTED RESULT Menu not delaying after right clicking. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION I've encountered this bug after several minutes after being logged in, but I wasn't able to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 422596] Discover window's content is transparent at startup
https://bugs.kde.org/show_bug.cgi?id=422596 --- Comment #1 from Raul --- Also, maximizing the window after opening Discover makes the shadow of the previous window state to appear. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 422596] New: Discover window's content is transparent at startup
https://bugs.kde.org/show_bug.cgi?id=422596 Bug ID: 422596 Summary: Discover window's content is transparent at startup Product: Discover Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: raul94go...@outlook.com.br CC: aleix...@kde.org Target Milestone: --- Created attachment 129128 --> https://bugs.kde.org/attachment.cgi?id=129128=edit discover bug SUMMARY STEPS TO REPRODUCE 1. Open Discover OBSERVED RESULT Window's content is transparent/glitched. EXPECTED RESULT Make the content to not be transparent. Maybe adding a "loading" text is a solution. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422144] New: Clock and system tray icons are misaligned in the left of the taskbar, for a short moment, after logging in
https://bugs.kde.org/show_bug.cgi?id=422144 Bug ID: 422144 Summary: Clock and system tray icons are misaligned in the left of the taskbar, for a short moment, after logging in Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: raul94go...@outlook.com.br Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Set the taskbar to "icons-only task manager" (I have only two icons pinned, don't know if this makes a difference) 2. Restart the computer 3. Login 4. Look at the taskbar OBSERVED RESULT The clock and systray icons are momentarily going to be misaligned at the left of the screen. After a millisecond or so, the systray and clock goes to the right of the screen. EXPECTED RESULT Correct spacing between systray and clock and the taskbar items. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: KDE 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation
https://bugs.kde.org/show_bug.cgi?id=422050
Raul Laasner changed:
What|Removed |Added
CC||raullaas...@gmail.com
--- Comment #1 from Raul Laasner ---
The following fix worked for me:
diff --git a/ui/pageview.cpp b/ui/pageview.cpp
index 50f8073ec..9bdb778ec 100644
--- a/ui/pageview.cpp
+++ b/ui/pageview.cpp
@@ -5375,7 +5376,7 @@ void PageView::slotScrollUp( int nSteps )
d->scroller->scrollTo(d->scroller->finalPosition() +
QPoint(0,-100*nSteps), 0);
}else{
if(d->scroller->finalPosition().y() >
verticalScrollBar()->minimum())
-d->scroller->scrollTo(d->scroller->finalPosition() + QPoint(0,
-verticalScrollBar()->rect().height() ));
+d->scroller->scrollTo(d->scroller->finalPosition() + QPoint(0,
-verticalScrollBar()->rect().height() ), 0);
}
}
else if ( d->document->currentPage() > 0 )
@@ -5403,7 +5404,7 @@ void PageView::slotScrollDown( int nSteps )
d->scroller->scrollTo(d->scroller->finalPosition() +
QPoint(0,100*nSteps), 0);
}else{
if(d->scroller->finalPosition().y() <
verticalScrollBar()->maximum())
-d->scroller->scrollTo(d->scroller->finalPosition() + QPoint(0,
verticalScrollBar()->rect().height() ));
+d->scroller->scrollTo(d->scroller->finalPosition() + QPoint(0,
verticalScrollBar()->rect().height() ), 0);
}
}
else if ( (int)d->document->currentPage() < d->items.count() - 1 )
The second argument of scrollTo is the animation speed, which I've set to zero.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 420824] Zoom in over "Fit Width" in two page mode
https://bugs.kde.org/show_bug.cgi?id=420824 --- Comment #3 from Raul Laasner --- I tested the fix and it works for me. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421937] New: In applications that use CSD, pointing cursor to the top right edge of the window doesn't select the close button
https://bugs.kde.org/show_bug.cgi?id=421937 Bug ID: 421937 Summary: In applications that use CSD, pointing cursor to the top right edge of the window doesn't select the close button Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: raul94go...@outlook.com.br CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 128702 --> https://bugs.kde.org/attachment.cgi?id=128702=edit Close button not being in the hover state. SUMMARY In applications that use CSD, pointing cursor to the top right edge of the window doesn't select the close button. STEPS TO REPRODUCE 1. Install a Gnome application that uses CSD, like Firefox (with no titlebar setting enabled, Totem video player, gnome-disk-utility); 2. Maximize the window; 3. Pointer the cursor to the top right edge of the screen. OBSERVED RESULT The close button will not be in the hover state. EXPECTED RESULT The close button being in the hover state when pointing the cursor to the top right edge of the screen like in native KDE apps. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420824] Zoom in over "Fit Width" in two page mode
https://bugs.kde.org/show_bug.cgi?id=420824 Raul Laasner changed: What|Removed |Added CC||raullaas...@gmail.com --- Comment #1 from Raul Laasner --- I'm facing exactly the same problem. It has appeared within the last week or so. I tried downloading and compiling an older version of Okular (1.8.70) but the problem persists, which makes me think it is related to something else. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 Raul <1000.onther...@gmail.com> changed: What|Removed |Added Alias||Angry, Tomato CC||1000.onther...@gmail.com --- Comment #8 from Raul <1000.onther...@gmail.com> --- I can confirm Johann Höchtl's workaround fixes this annoying behavior in Gentoo + Plasma + Wayland, Spanish language. Thanks a lot! Surprisingly, I've got this other PC with Arch + Plasma + Wayland and dead keys have been working fine from the beginning. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 414018] New: Global menu with Firefox isn't working
https://bugs.kde.org/show_bug.cgi?id=414018 Bug ID: 414018 Summary: Global menu with Firefox isn't working Product: kde Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: raulcrave...@gmail.com Target Milestone: --- Created attachment 123833 --> https://bugs.kde.org/attachment.cgi?id=123833=edit The attachment shows the empty space on the top of Firefox SUMMARY When I use the Global Menu widget with Firefox without title bar, it shows an empty space on the top of the browser where it should be the global menu. I've tried both in Firefox Developer and Chrome and this doesn't happen, only in the "regular" Firefox. STEPS TO REPRODUCE 1. Activate Global Menu Widget 2. Disable Title Bar on Firefox OBSERVED RESULT It shows an empty space on the top of the browser. EXPECTED RESULT This space shouldn't appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Raul Laasner changed: What|Removed |Added CC||raullaas...@gmail.com --- Comment #40 from Raul Laasner --- (In reply to Joel Teixeira from comment #38) > For the time being IMO the best option is to use > default theme on GTK application setting. Thank you for the suggestion! I was seriously considering giving up Firefox for Chrome. The most annoying thing for me was not the faulty coloring but how much narrower the scroll bars were. That made web surfing much harder. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 412772] New: KRDC crashes when it tries to connect to tigervnc server
https://bugs.kde.org/show_bug.cgi?id=412772 Bug ID: 412772 Summary: KRDC crashes when it tries to connect to tigervnc server Product: krdc Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: 1000.onther...@gmail.com Target Milestone: --- Application: krdc (19.04.3) (Compiled from sources) Qt Version: 5.12.3 Frameworks Version: 5.60.0 Operating System: Linux 4.19.72-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Got this "server 1", a new Arch Linux instalation. I've installed *tigervnc* server and run it the simplest way: vncserver :1 Once entered a password, server creates default files into ~/.vnc and starts listening. >From "client 1", Gentoo Linux, I start KRDC client and try to connect to "server 1". It pops-up the usual dialog inviting me to enter network quality, save to Wallet, etc. When I finish, application crashes. The same KRDC client works fine connecting with "server 2", a Debian installation. But its VNC server is *tightvncserver*. Using Vinagre client in "client 1", it connects to "server 1" without issues. I can attach the compile log if it's needed. The crash can be reproduced every time. -- Backtrace: Application: KRDC (krdc), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f655b731780 (LWP 9263))] Thread 16 (Thread 0x7f64f3fff700 (LWP 9837)): [KCrash Handler] #6 0x7f6552208662 in () at /usr/lib64/libvncclient.so.1 #7 0x7f6552208e3e in HandleVeNCryptAuth () at /usr/lib64/libvncclient.so.1 #8 0x7f6552203da8 in InitialiseRFBConnection () at /usr/lib64/libvncclient.so.1 #9 0x7f65522067f8 in rfbInitClient () at /usr/lib64/libvncclient.so.1 #10 0x7f6558025077 in () at /usr/lib64/qt5/plugins/krdc/libkrdc_vncplugin.so #11 0x7f655802589d in () at /usr/lib64/qt5/plugins/krdc/libkrdc_vncplugin.so #12 0x7f65622c5c71 in () at /usr/lib64/libQt5Core.so.5 #13 0x7f6560a42508 in start_thread () at /lib64/libpthread.so.0 #14 0x7f6561f31bff in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f6513fff700 (LWP 9277)): #0 0x7f6560a4939c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6551607f8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6551607ba7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6560a42508 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6561f31bff in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f6538ff9700 (LWP 9276)): #0 0x7f6560a4939c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6551607f8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6551607ba7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6560a42508 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6561f31bff in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f65397fa700 (LWP 9275)): #0 0x7f6560a4939c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6551607f8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6551607ba7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6560a42508 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6561f31bff in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f6539ffb700 (LWP 9274)): #0 0x7f6560a4939c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6551607f8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6551607ba7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6560a42508 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6561f31bff in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f653a7fc700 (LWP 9273)): #0 0x7f6560a4939c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6551607f8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6551607ba7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6560a42508 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6561f31bff in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f653affd700 (LWP 9272)): #0 0x7f6560a4939c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6551607f8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6551607ba7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6560a42508 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6561f31bff in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f653b7fe700 (LWP 9271)): #0 0x7f6560a4939c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6551607f8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6551607ba7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6560a42508 in start_thread () at /lib64/libpthread.so.0 #4
[kwin] [Bug 401227] Global hotkey resets with each restart
https://bugs.kde.org/show_bug.cgi?id=401227 --- Comment #9 from Raul Laasner --- Thanks, although for me killing kglobalaccel5 kills too much. I'd still like to use some other shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401535] New: group windows with tabs
https://bugs.kde.org/show_bug.cgi?id=401535 Bug ID: 401535 Summary: group windows with tabs Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: raul_kde_bugzi...@dias.com.br Target Milestone: --- This is a very interesting function. To group windows with tabs as a browser do. There is a software that does that for windows, which looks very nice: Groupy -> https://www.stardock.com/products/groupy/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401227] Global hotkey resets with each restart
https://bugs.kde.org/show_bug.cgi?id=401227 --- Comment #4 from Raul Laasner --- Not sure if it means anything but if I switch to Plasma (Wayland), the problem disappears. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401227] Global hotkey resets with each restart
https://bugs.kde.org/show_bug.cgi?id=401227 --- Comment #2 from Raul Laasner --- Thank you, this helped! If I run xev -root, then part of the output reads PropertyNotify event, serial 18, synthetic NO, window 0x1c9, atom 0x152 (CLIP_TEMPORARY), time 8285578, state PropertyNewValue which suggests it has something to do with copying text. Indeed, if I select some text in a text editor, press Alt+=, and then press the middle button, that text is pasted. I don't have an immediate solution here but I can probably figure it out. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401227] New: Global hotkey resets with each restart
https://bugs.kde.org/show_bug.cgi?id=401227 Bug ID: 401227 Summary: Global hotkey resets with each restart Product: kwin Version: 5.14.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: raullaas...@gmail.com Target Milestone: --- SUMMARY KWin seems to steal focus when the key combination Alt+= is pressed, but I can't figure out what it does exactly. This is a problem for me because I typically use this hotkey in Emacs to do a specific task. However, since KWin steals the focus every time Alt+= is pressed, I can't use it in Emacs. STEPS TO REPRODUCE Open xev and press Alt+=. The following is a commented output from my machine: # Alt pressed: KeyPress event, serial 40, synthetic NO, window 0x581, root 0x1c9, subw 0x0, time 3737607, (61,104), root:(1461,133), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False # = pressed: FocusOut event, serial 40, synthetic NO, window 0x581, mode NotifyGrab, detail NotifyAncestor FocusOut event, serial 40, synthetic NO, window 0x581, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 40, synthetic NO, window 0x581, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 40, synthetic NO, window 0x0, keys: 4294967241 0 32 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 # = released: KeyRelease event, serial 40, synthetic NO, window 0x581, root 0x1c9, subw 0x0, time 3738919, (61,104), root:(1461,133), state 0x8, keycode 21 (keysym 0x3d, equal), same_screen YES, XLookupString gives 1 bytes: (3d) "=" XFilterEvent returns: False # Alt released: KeyRelease event, serial 40, synthetic NO, window 0x581, root 0x1c9, subw 0x0, time 3739829, (61,104), root:(1461,133), state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False You can see things like FocusIn and FocusOut, which means that a KDE process is invoked by the key combination. I believe this is related to KWin because when I close KWin, killall kwin_x11 the shortcut becomes available in Emacs and other applications (it's not intercepted by KWin). If I then start KWin, kwin_x11 & the shortcut becomes again bound to a KWin and is not available by other applications. I went through all the global and standard shortcuts but nothing seems to be bound to Alt+=. The only way I can fix this is by assigning Alt+= to some action and then removing it which frees up the key combination. However, after a restart Alt+= is again bound to some unknown action. EXPECTED RESULT When this shortcut is disabled, it should stay disabled even after KWin restarts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION This issue emerged about week ago. First reported here: https://forum.kde.org/viewtopic.php?f=66=155962. A similar issue reported here: https://forum.kde.org/viewtopic.php?f=63=155960. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 345774] KTorrent crashed after download started (Gigabit speed)
https://bugs.kde.org/show_bug.cgi?id=345774 Raul Malea changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Raul Malea --- Sorry, for now I used openSUSE Leap 15. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 339879] KTP-Telepathy not connected with Yahoo IM account
https://bugs.kde.org/show_bug.cgi?id=339879 Raul Malea changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Raul Malea --- Because Yahoo closed YMmessenger, I closed this bug. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396878] New: Display scaling does not work when going back to 1
https://bugs.kde.org/show_bug.cgi?id=396878 Bug ID: 396878 Summary: Display scaling does not work when going back to 1 Product: systemsettings Version: 5.12.6 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: raul_kde_bugzi...@dias.com.br CC: unassigned-b...@kde.org Target Milestone: --- Under System Setings -> Display and Monitor -> Display -> Scale Display. If I change it from 1, when I want to reset to 1, it will behave as a 2. I can see that changing here, seems to be the same as changing SS -> Fonts -> Force fonts DPI. It will be enabled and changed to a 96 factor (192 in 2x). When I go back to 1x, this option will be unchecked and the default should be 96, which is not applied. I have to force 96 dpi in order to get what I had in the first place. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396814] New: Yakuake does not like scaled display
https://bugs.kde.org/show_bug.cgi?id=396814 Bug ID: 396814 Summary: Yakuake does not like scaled display Product: yakuake Version: 3.0.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: raul_kde_bugzi...@dias.com.br Target Milestone: --- Created attachment 114094 --> https://bugs.kde.org/attachment.cgi?id=114094=edit yakuake white lines on scale I have my display scaled to 1.3. This makes yakuake get its position wrong - on a dual head, it aligns left on the right head and aligns right on the left head, where should it be centered. Most of time it display a few white lines in the terminal, as if it has lost a pixel in the scaling process. I know kde scaling is far from optimal, however this behaviour is not shown in Konsole. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394534] kcminit crash on startup
https://bugs.kde.org/show_bug.cgi?id=394534 Raul Malea changed: What|Removed |Added CC||raul.ma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 395482] KDEInit crash on login
https://bugs.kde.org/show_bug.cgi?id=395482 Raul Malea changed: What|Removed |Added Platform|unspecified |openSUSE RPMs Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Raul Malea --- OS: openSUSE Leap 15.0. Kernel: 4.12.14-lp150.12.4-default Qt Version: 5.11.0 Frameworks Version: 5.47.0 Kde 5.13, 18.04.02 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 395482] KDEInit crash on login
https://bugs.kde.org/show_bug.cgi?id=395482 --- Comment #2 from Raul Malea --- Created attachment 113388 --> https://bugs.kde.org/attachment.cgi?id=113388=edit Crash report KdeInit5 Crash report -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 395482] KDEInit crash on login
https://bugs.kde.org/show_bug.cgi?id=395482 Raul Malea changed: What|Removed |Added CC||raul.ma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389622] can't switch output over multiple HDMIs/DPs
https://bugs.kde.org/show_bug.cgi?id=389622 Raul Kde Bugzilla <raul_kde_bugzi...@dias.com.br> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389622] New: can't switch output over multiple HDMIs/DPs
https://bugs.kde.org/show_bug.cgi?id=389622 Bug ID: 389622 Summary: can't switch output over multiple HDMIs/DPs Product: plasma-pa Version: 5.11.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: now...@gmail.com Reporter: raul_kde_bugzi...@dias.com.br CC: plasma-b...@kde.org Target Milestone: --- When there are more than one HDMI or Display Port display connected, plasma-pa does not let you switch which HDMI/DP should receive the audio stream. Using other frontends this can be done fine. e.g. on pavucontrol-qt, I can go to Configuration tab and switch the profile over all available ports. In case this is a video card specific bug, mine is a Nvidia 1080 GTX. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387587] Logout is cancelling by launched Steam app
https://bugs.kde.org/show_bug.cgi?id=387587 Marcos Raul Carot Collins <marcos.ca...@gmail.com> changed: What|Removed |Added CC||marcos.ca...@gmail.com --- Comment #2 from Marcos Raul Carot Collins <marcos.ca...@gmail.com> --- I have the same issue. There is also a Steam bug: https://github.com/ValveSoftware/steam-for-linux/issues/3301 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386717] New: Panel stops updating when running Coutner-Strike: Global Offensive in the background
https://bugs.kde.org/show_bug.cgi?id=386717 Bug ID: 386717 Summary: Panel stops updating when running Coutner-Strike: Global Offensive in the background Product: plasmashell Version: 5.11.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: raul_kde_bugzi...@dias.com.br Target Milestone: 1.0 When running CS:GO (fullscreen), if I ALT-TAB it to the desktop, the panel is does not update. However it still works. Mouse over, tooltips still responds fine. The displayed data is the same as the time the game started. If I close the game, the panel comes back to updating itself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386411] New: Application specific task switcher not working properly
https://bugs.kde.org/show_bug.cgi?id=386411 Bug ID: 386411 Summary: Application specific task switcher not working properly Product: kwin Version: 5.11.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: raullaas...@gmail.com Target Milestone: --- Created attachment 108659 --> https://bugs.kde.org/attachment.cgi?id=108659=edit Screenshot of task switcher in action Application specific task switcher, by default bound to Alt+`, does not work for certain applications. In the attachment, I have two Dolphin windows open, I press Alt+`, but the task switcher only register one of the Dolphins. This is not the case with GTK applications. For instance, I can have two instances of Firefox open, and Alt+` works fine. Also, Alt+Tab works without problems no matter which windows are open. It is specifically Alt+` on KDE applications that seems to have a bug. I'm using Arch Linux and this issue emerged after an update at around Oct 11. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380349] Some remote (sftp) files are opened via temp-file instead of remote URL although command is "kwrite %u"
https://bugs.kde.org/show_bug.cgi?id=380349 Raul Kde Bugzilla <raul_kde_bugzi...@dias.com.br> changed: What|Removed |Added CC||raul_kde_bugzi...@dias.com. ||br --- Comment #3 from Raul Kde Bugzilla <raul_kde_bugzi...@dias.com.br> --- This bug has being around for a long time. Since kde 4 if I am not mistaken. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384437] New: Dolphin does not respect Command arguments for opening remote file types
https://bugs.kde.org/show_bug.cgi?id=384437 Bug ID: 384437 Summary: Dolphin does not respect Command arguments for opening remote file types Product: dolphin Version: 16.12.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: raul_kde_bugzi...@dias.com.br CC: elvis.angelac...@kde.org Target Milestone: --- This might be owned by kio sftp or some other generic component. When opening a remote ssh text file (sftp) in dolphin: 1 - Right click on the file 2 - Open With... (or other if there is an association already) 3 - type: kate %U 4 - Mark the checkbox "Remember application " 5 - OK The file will open in kate and kate will know it is a remote file and save it thru sftp as expected. e.g. [10.1.2.3]folder\_file Now with the association, there is a context menu "Open with kate". When using it it shows as: 14213_0\_file As I understand, in this case is the same behaviour as not using %U in the kate call. Dolphin/kio copies the file to some temporary folder and then passes to kate. If I enter the file association in Properties -> File Type Options -> Application Preference Order -> kate -> Edit -> Application: The command is "kate %U" as expected. So, Dolphin does not respect the %U argument in the associated call. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383005] New: line-height smaller than font size
https://bugs.kde.org/show_bug.cgi?id=383005 Bug ID: 383005 Summary: line-height smaller than font size Product: kate Version: 16.12 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: raul_kde_bugzi...@dias.com.br Target Milestone: --- When using HiDPI with dpi set to 120, the line height of the text becomes too small to acommodate the text heigh. When this happens, some parts of the text are cropped. If there is some ""_"" (underlines) in the text, it is shown as blanks. On dpi 96 this does not happen. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 382277] New: Scale display below 1
https://bugs.kde.org/show_bug.cgi?id=382277 Bug ID: 382277 Summary: Scale display below 1 Product: KScreen Version: 5.10.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: raul_kde_bugzi...@dias.com.br Target Milestone: --- The scale in Scale display option should allow for values below 1. Without it, we are only able to work around with the xrand option --scale which is not optimal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382276] Plasma does not detect total display area when scaling
https://bugs.kde.org/show_bug.cgi?id=382276 --- Comment #2 from Raul Kde Bugzilla <raul_kde_bugzi...@dias.com.br> --- The display card is a NVidia. Driver: nvidia-375 Kubuntu (ubuntu + kubuntu backports) 17.04 About the Screenshot, the black area in the left is where plasma fails to see and use. Note the "add widgets" button on the top right, not being in the top right. Also note that I am able to use this space fine, as I placed a konsole terminal in there. The black area in the top of the right display is correct, as there is an height offset between the two displays to match the physical position. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382276] Plasma does not detect total display area when scaling
https://bugs.kde.org/show_bug.cgi?id=382276 --- Comment #1 from Raul Kde Bugzilla <raul_kde_bugzi...@dias.com.br> --- raul@nostromo:~$ xrandr --verbose Screen 0: minimum 8 x 8, current 5440 x 1740, maximum 32767 x 32767 HDMI-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x1be Timestamp: 594350 Subpixel: unknown Clones: CRTCs: 0 1 2 3 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 BorderDimensions: 4 supported: 4 Border: 0 0 0 0 range: (0, 65535) SignalFormat: TMDS supported: TMDS ConnectorType: HDMI ConnectorNumber: 2 _ConnectorLocation: 2 DP-0 connected primary 2560x1440+2880+300 (0x1c0) normal (normal left inverted right x axis y axis) 382mm x 214mm Identifier: 0x1bf Timestamp: 594350 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 2 3 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 Backlight: 100 range: (0, 100) EDID: 000006af9610e426e270 001a0104a52615780230c0a556559e26 0d4f560001010101010101010101 01010101010128c300a0a0a05a503020 35007ed6101828c300a0a0a05456 302035007ed6101800fe0041 554f0a20202020202020202000fe 004231373351544e30312e30200a0060 BorderDimensions: 4 supported: 4 Border: 0 0 0 0 range: (0, 65535) SignalFormat: DisplayPort supported: DisplayPort ConnectorType: Panel ConnectorNumber: 3 _ConnectorLocation: 3 2560x1440 (0x1c0) 499.600MHz -HSync -VSync *current +preferred h: width 2560 start 2608 end 2640 total 2720 skew0 clock 183.68KHz v: height 1440 start 1443 end 1448 total 1530 clock 120.05Hz 2560x1440 (0x1c1) 499.600MHz -HSync -VSync h: width 2560 start 2608 end 2640 total 2720 skew0 clock 183.68KHz v: height 1440 start 1443 end 1448 total 3060 clock 60.02Hz DP-1 disconnected (normal left inverted right x axis y axis) Identifier: 0x1c2 Timestamp: 594350 Subpixel: unknown Clones: CRTCs: 0 1 2 3 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 BorderDimensions: 4 supported: 4 Border: 0 0 0 0 range: (0, 65535) SignalFormat: DisplayPort supported: DisplayPort ConnectorType: DisplayPort ConnectorNumber: 4 _ConnectorLocation: 4 DP-2 connected 2880x1620+0+0 (0x1c4) normal (normal left inverted right x axis y axis) 477mm x 268mm Identifier: 0x1c3 Timestamp: 594350 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 1 CRTCs: 0 1 2 3 Transform: 1.50 0.00 0.00 0.00 1.50 0.00 0.00 0.00 1.00 filter: CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 EDID: 000010ac72a04d5a5731 1616010380301b78ea01f5a257529f27 0a5054a54b00714f8180d1c001010101 010101010101023a801871382d40582c 4500dd0c111e00ff004e3846 334d32354f31575a4d0a00fc0044 454c4c204532323131480a2000fd 00384c1e5311000a202020202020001f BorderDimensions: 4 supported: 4 Border: 0 0 0 0 range: (0, 65535) SignalFormat: TMDS supported: TMDS ConnectorType: DisplayPort ConnectorNumber: 4 _ConnectorLocation: 4 1920x1080 (0x1c4) 148.500MHz +HSync +VSync *current +preferred h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1280x1024 (0x1c5) 135.000MHz +HSync +VSync h: width 1280 start 1296 end 1440 total 1688 skew0 clock 79.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 75.02Hz 1280x1024 (0x1c6) 108.000MHz
[plasmashell] [Bug 382276] New: Plasma does not detect total display area when scaling
https://bugs.kde.org/show_bug.cgi?id=382276 Bug ID: 382276 Summary: Plasma does not detect total display area when scaling Product: plasmashell Version: 5.10.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: raul_kde_bugzi...@dias.com.br CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 106583 --> https://bugs.kde.org/attachment.cgi?id=106583=edit Screenshot of plasma not detecting full display scaled When rescaling one monitor in a dual-head setup, plasma does not detect to new display area and leave it blank (black). In this sample the display on the left is a 1920x1080 and the one on the right is 2560x1440 (notebook). This is the xrandr line to set it up: xrandr --output DP-2 --mode 1920x1080 --scale 1.5x1.5 --output DP-0 --pos 2880x300 I will post the output of xrandr --verbose in the next comment. Attached is a screenshot of the effect. It is important to note that this would not be necessary if the Scale (in System Settings -> Display and Monitor -> Scale Display) accepted values below 1. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 376310] New: KDE crash when computer was awaking from sleep mode
https://bugs.kde.org/show_bug.cgi?id=376310 Bug ID: 376310 Summary: KDE crash when computer was awaking from sleep mode Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: frtorr...@gmail.com Target Milestone: --- Application: kdeinit5 () (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.1.36-44-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: KDE crashed when the compunter was awoken from sleep mode. This does happen some times -- Backtrace: Application: kdeinit5 (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f659c20a780 (LWP 1238))] Thread 6 (Thread 0x7f657176e700 (LWP 1349)): #0 0x7f65970b8506 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f65970b8d80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f65970b8f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f659a904d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f659a8abd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f659a6cd61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f659a6d232f in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f659a36402d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f6573fff700 (LWP 1264)): #0 0x7f659a357ccd in read () from /lib64/libc.so.6 #1 0x7f65970f9b60 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f65970b8999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f65970b8df8 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f65970b8f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f659a904d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f659a8abd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f659a6cd61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f659a6d232f in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f659a36402d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f6578e29700 (LWP 1263)): #0 0x7f659a35bbfd in poll () from /lib64/libc.so.6 #1 0x7f65970b8e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f65970b8f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f659a904d8b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f659a8abd53 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f659a6cd61a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f657b4aecf7 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #7 0x7f659a6d232f in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f659a36402d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f657c0f5700 (LWP 1250)): #0 0x7f65970facf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f65970b8d55 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f65970b919a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #3 0x7f657cc30426 in ?? () from /usr/lib64/libgio-2.0.so.0 #4 0x7f65970ddf65 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f659a36402d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f6586d2a700 (LWP 1240)): #0 0x7f659a35bbfd in poll () from /lib64/libc.so.6 #1 0x7f659b680422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f659b68200f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f658907f3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f659a6d232f in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f6597d7d0a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f659a36402d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f659c20a780 (LWP 1238)): [KCrash Handler] #6 0x7f659a2faf54 in free () from /lib64/libc.so.6 #7 0x7f6588e393f1 in XIQueryDevice () from /usr/lib64/libXi.so.6 #8 0x7f65890a00bf in QXcbConnection::handleEnterEvent(xcb_enter_notify_event_t const*) () from /usr/lib64/libQt5XcbQpa.so.5 #9 0x7f65890917df in QXcbWindow::handleEnterNotifyEvent(xcb_enter_notify_event_t const*) () from /usr/lib64/libQt5XcbQpa.so.5 #10 0x7f658907d515 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib64/libQt5XcbQpa.so.5 #11 0x7f658907f01b in
[kscreenlocker] [Bug 374289] multiscreen locks stealing focus
https://bugs.kde.org/show_bug.cgi?id=374289 Raul Kde Bugzilla <raul_kde_bugzi...@dias.com.br> changed: What|Removed |Added CC||raul_kde_bugzi...@dias.com. ||br -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374289] New: multiscreen locks stealing focus
https://bugs.kde.org/show_bug.cgi?id=374289 Bug ID: 374289 Summary: multiscreen locks stealing focus Product: kscreenlocker Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: raul_kde_bugzi...@dias.com.br CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- kscreenlocker is 5.8.4. Not in bugzilla version list. Using more than one head (2 or 3) with a notebook. After screens are off, waking up the system, like with a key press, the displays turns on in very slow way. This is probably xorg, xrandr, prime issue. The primary display (LVDS1) turns on very fast, the others about 3s-5s each (serialized). The problem with this is that each screen has its one locker password widgets. And each time one screen comes on, it will steal the focus from the previous. So, If it is a 3-head, and the password is "foobaragain", I might get "foo" in the first head, "bar" in the second and "again" in the 3rd. This is very annoying, btw. I understand what is going on. Each screen have different resolution, DPI, etc. So each needs each on control set. The first one needs to steal the focus as it could be with any application. However, this is not true for the 2nd and 3rd controls. At least the controls should be able to sync the input and then wouldn't matter who really have the focus. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 371710] New: About KDE Menu entry does not show verions
https://bugs.kde.org/show_bug.cgi?id=371710 Bug ID: 371710 Summary: About KDE Menu entry does not show verions Product: kde Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: raul_kde_bugzi...@dias.com.br Target Milestone: --- Using KDE 4.7.5 in Kubuntu 16.10. First, notice that the version in bugzilla stops at 4.14.1!! Using the Menu: Help -> About KDE It is expected to see which version KDE is running (at least this particular application was compiled against). This is specially important on upgrades and multiple versions concurrent. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 366087] yakuake should have an option to be centered in a specific DISPLAY
https://bugs.kde.org/show_bug.cgi?id=366087 Raul Kde Bugzilla <raul_kde_bugzi...@dias.com.br> changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 366087] yakuake should have an option to be centered in a specific DISPLAY
https://bugs.kde.org/show_bug.cgi?id=366087 Raul Kde Bugzilla <raul_kde_bugzi...@dias.com.br> changed: What|Removed |Added CC||raul_kde_bugzi...@dias.com. ||br -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 366087] New: yakuake should have an option to be centered in a specific DISPLAY
https://bugs.kde.org/show_bug.cgi?id=366087 Bug ID: 366087 Summary: yakuake should have an option to be centered in a specific DISPLAY Product: yakuake Version: 2.9.9 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: raul_kde_bugzi...@dias.com.br Yakuake is a great Terminal. However, it is not obvious (probably), but it should have an option to be centered/aligned in relation to a specfic DISPLAY. This can be done (faked), by setting the Left/Right position in the options. The problem is that this method uses the whole Framebuffer size and not indivudual displays. The incovenience arises, for example, in a notebook that has different display configurations at different locations. The worst thing that can happen to a Terminal application is to be divided between 2 displays of different sizes. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
