[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 Jaroslav Reznik <jrez...@redhat.com> changed: What|Removed |Added CC||jrez...@redhat.com --- Comment #18 from Jaroslav Reznik <jrez...@redhat.com> --- (In reply to Dennis Schridde from comment #12) > (In reply to Mahendra Tallur from comment #11) > > Also sometimes the mouse cursor gets stuck in an incorrect state (for > > instance, is show as a resizing cursor even when the mouse has left the edge > > of a window). > > This might not be Wayland related, as I also see this on X11 with certain > applications (e.g. Firefox). In any case I believe this should be tracked > as a separate bug. Initially I've seen this only in Wayland session but after playing with additional cursor themes, it indeed looks like it's not Wayland specific (or just caused by changing settings under Wayland session?) but for me it looks like some caching issue. Breeze first used under X11 - ok under X11, I'm seeing this behavior under Wayland. Adwaita theme first used under Wayland - I can now see the same behavior under X11. I can try it with clean account and with and without 2560x1440 external display connected. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371655] No configuration change reflected when disconnecting docking station with external displays
https://bugs.kde.org/show_bug.cgi?id=371655 --- Comment #4 from Jaroslav Reznik <jrez...@redhat.com> --- Well, the other way stopped working (when docking station is connected). I'll try to collect logs and I'll open the new bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371655] No configuration change reflected when disconnecting docking station with external displays
https://bugs.kde.org/show_bug.cgi?id=371655 --- Comment #2 from Jaroslav Reznik <jrez...@redhat.com> --- It works now after 5.8.4 update, not sure what has changed. It still takes some time before Plasma panel moves to the internal display but it does and opened apps moves immediately. I think this bug could be closed. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371655] New: No configuration change reflected when disconnecting docking station with external displays
https://bugs.kde.org/show_bug.cgi?id=371655 Bug ID: 371655 Summary: No configuration change reflected when disconnecting docking station with external displays Product: KScreen Version: 5.8.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kded Assignee: se...@kde.org Reporter: jrez...@redhat.com Setup: internal laptop screen (eDP1) two external displays (DP2-1 and DP2-2) connected via OneLink Pro docking station with Plasma shell panel on the DP2-1 (as a primary display) KScreen works correctly when docking station is connected - both external displays are turned on, panel is properly moved to DP2-1 display (see http://rezza.hofyland.cz/kde/kscreen.log.1). When docking station is disconnected, nothing happens. Cursor stays on the external display, same as for panel and windows (see http://rezza.hofyland.cz/kde/kscreen.log.2). When I connect docking station again, nothing happens either. Without docking station, it's possible to run xrandr without any command line option and it properly moves panel to internal screen, same for windows (see http://rezza.hofyland.cz/kde/kscreen.log.3). I can provide more details if needed. Just a note - it works in other X11 based DEs (aka GNOME Shell) on Fedora 25 and it worked before in 5.7 release. And KScreen is aware of the change as the new kscreen.log is created. Reproducible: Always Steps to Reproduce: 1. docking station with two external displays connected 2. disconnect docking station Actual Results: Configuration change is not reflected, panel and windows stays on the second screen until xrandr command is executed. Expected Results: Configuration change is properly reflected when docking station is disconnected without the need to type xrandr command. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 Jaroslav Reznik <jrez...@redhat.com> changed: What|Removed |Added CC||jrez...@redhat.com --- Comment #7 from Jaroslav Reznik <jrez...@redhat.com> --- I can see this on KF5 5.27/Plasma 5.8.1 - it does not happen as often as in the past but the bug is still there. Restarting Plasma usually helps. I can provide config files if needed but it's difficult to explain the behavior aka what I did. It's just not there. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 370358] GIve sddm user home folder and .face.icon ACL rights in order to load the avatar
https://bugs.kde.org/show_bug.cgi?id=370358 Jaroslav Reznik <jrez...@redhat.com> changed: What|Removed |Added CC||jrez...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370648] New: SDDM Breeze theme hardly usable on multiscreen set up with different DPIs
https://bugs.kde.org/show_bug.cgi?id=370648 Bug ID: 370648 Summary: SDDM Breeze theme hardly usable on multiscreen set up with different DPIs Product: Breeze Version: 5.8.0 Platform: Fedora RPMs URL: http://rezza.hofyland.cz/kde/sddm-breeze-multiscreen.j pg OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: jrez...@redhat.com I have a multiscreen set up with different DPIs - internal laptop's resolution is 2560x1440 with two external Full HD monitors. When only internal is used, all looks good but when external (docked) are used, theme is hardly usable. On internal monitor it's messed up (see URL attachment), on external monitors, everything is tiny (I can provide picture if needed). Reproducible: Always Steps to Reproduce: 1. multimonitor set up with different DPIs 2. use sddm Actual Results: Hardly usable theme Expected Results: It just works. I even don't need proper scaling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Jaroslav Reznik <jrez...@redhat.com> changed: What|Removed |Added CC||jrez...@redhat.com --- Comment #152 from Jaroslav Reznik <jrez...@redhat.com> --- I'm hitting strange issues regarding panel moving to the wrong screen with 5.7.1 (but I had very similar issues with 5.6, both with Qt 5.6.1) and it's actually difficult to explain it in the bug or reproduce it reliably at all. Just a few notes: sometimes I see what is described in comment #144 - screen flickers, I can see panel on the correct screen and then it moves to wrong one. When I add another default panel (mouse is on the screen I'd like to add it) Plasma starts consuming CPU and it leads to the whole desktop freeze). One workaround that works sometimes is to select different monitor as primary in Display Settings. Aka my setup is eDP, HDMI1 and DP2-2 - if I want HDMI1 as primary, I have to select DP2-2 as primary. This could be fixed by a few Plasma restarts (at the moment of writing, I can see panel on HDMI1 with HDMI1 set as primary). Kscreen configuration looks correct. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 351256] Way to distinguish more monitors with the same vendor/model label
https://bugs.kde.org/show_bug.cgi?id=351256 --- Comment #2 from Jaroslav Reznik <jrez...@redhat.com> --- (In reply to Jason Tibbitts from comment #1) > I have this problem, too. At work I have three Dell U2412M monitors; at > home I have three U2415s. Due to other kscreen issues, I have to take them > out of clone mode and arrange them every time I log in, and this isn't > particularly easy because they all appear identical in the positioning > window. Click on each monitor and you will see output under the monitor's layout editor. At least this way it's possible to identify which monitor is which. But I'd still like to see in the layout editor too :). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 360482] Importing an OpenVPN configuration with embedded certificates yields a defect connection due to SELinux
https://bugs.kde.org/show_bug.cgi?id=360482 Jaroslav Reznik <jrez...@redhat.com> changed: What|Removed |Added CC||jrez...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360889] New: Graphic artifacts on the panel's pop-ups
https://bugs.kde.org/show_bug.cgi?id=360889 Bug ID: 360889 Summary: Graphic artifacts on the panel's pop-ups Product: plasmashell Version: 5.5.95 Platform: Fedora RPMs URL: http://rezza.hofyland.cz/kde/plasma-artifacts.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jrez...@redhat.com When moving cursor over panel on the components that contains pop-up, graphic artifacts appears - see screenshot in the URL field. It's not very visible when movement is slow but faster breaks screen a lot. Even on other non-primary displays. When moving faster, pop-ups are even shown on different displays and animated. It happens on task manager, systray etc. Seems like the first release I realized this is 5.5.95. It doesn't matter what compositor method is selected - OpenGL (GLX, EGL), XRender. Reproducible: Always Steps to Reproduce: 1. select some component/widget on the panel that shows pop-up (task, systray icon etc) 2. wait for pop-up to appear 3. move quickly over other components that has pop-up (but the same type) Actual Results: Graphic artifacts, even on other displays (not only primary) Expected Results: No graphic artifacts cat /etc/fedora-release Fedora release 23 (Twenty Three) rpm -q plasma-desktop plasma-desktop-5.5.95-1.fc23.x86_64 rpm -q qt5-qtbase qt5-qtbase-5.6.0-7.fc23.x86_64 (same result on qt 5.5 though) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) rpm -q xorg-x11-drv-intel xorg-x11-drv-intel-2.99.917-19.20151206.fc23.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357063] New konsole uses desktop for background; echoing command input/out NOT displaying
https://bugs.kde.org/show_bug.cgi?id=357063 Jaroslav Reznik <jrez...@redhat.com> changed: What|Removed |Added CC||jrez...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356866] New: Plasmashell crashes when running on top of Qt 5.6 Beta
https://bugs.kde.org/show_bug.cgi?id=356866 Bug ID: 356866 Summary: Plasmashell crashes when running on top of Qt 5.6 Beta Product: plasmashell Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jrez...@redhat.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.0) Qt Version: 5.6.0 Operating System: Linux 4.4.0-0.rc5.git0.1.fc24.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: After update to Qt 5.6 Beta (on Fedora from @kdesig/Qt5 repo) Plasma is crashing on start up. It may or may not be related to moc issues Fedora hits with Qt 5.6 but it was crashing with developer build too (that wasn't affected by moc issue). Works perfectly with Qt 5.5.1. qt5-qtbase-5.6.0-0.15.fc23.x86_64 plasma-desktop-5.5.0-4.fc23.x86_64 Steps to reproduce: - update to Qt 5.6 Beta Expected results: No crash on startup The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f86075940 (LWP 4556))] Thread 9 (Thread 0x7f1f7d6a3700 (LWP 4559)): #0 0x7f1f94aefffd in poll () at /lib64/libc.so.6 #1 0x7f1f9a238272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f1f9a239ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f1f7ed59ea9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f1f957017d8 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f1f93e3360a in start_thread () at /lib64/libpthread.so.0 #6 0x7f1f94afba9d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1f77fff700 (LWP 4561)): #0 0x7f1f94aefffd in poll () at /lib64/libc.so.6 #1 0x7f1f903d016c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f1f903d027c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f1f95927d6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f1f958d075a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f1f956fc864 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f1f962bd1c5 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f1f957017d8 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f1f93e3360a in start_thread () at /lib64/libpthread.so.0 #9 0x7f1f94afba9d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1f767c3700 (LWP 4577)): #0 0x7f1f94b0959f in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7f1f94aebbd2 in read () at /lib64/libc.so.6 #2 0x7f1f90413390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #3 0x7f1f903cfc64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #4 0x7f1f903d0110 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #5 0x7f1f903d027c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #6 0x7f1f95927d6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f1f958d075a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #8 0x7f1f956fc864 in QThread::exec() () at /lib64/libQt5Core.so.5 #9 0x7f1f98cdcb15 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #10 0x7f1f957017d8 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #11 0x7f1f93e3360a in start_thread () at /lib64/libpthread.so.0 #12 0x7f1f94afba9d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f1f67fff700 (LWP 4587)): #0 0x7f1f90414734 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f1f903d008e in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f1f903d027c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f1f95927d6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f1f958d075a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f1f956fc864 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f1f98cdcb15 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f1f957017d8 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f1f93e3360a in start_thread () at /lib64/libpthread.so.0 #9 0x7f1f94afba9d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1f6641c700 (LWP 4589)): #0 0x7f1f94aefffd in poll () at /lib64/libc.so.6 #1 0x7f1f903d016c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f1f903d027c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f1f95927d6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f1f958d075a in QEventLoop::exec(QFlags)
