[KScreen] [Bug 486328] External screens switch off when laptop lid is closed with USB-C dock with dual monitor (single monitor works)
https://bugs.kde.org/show_bug.cgi?id=486328 Gábor Katona changed: What|Removed |Added Version|6.0.4 |6.1.0 --- Comment #2 from Gábor Katona --- This problem is still present, but as I have tested it only affects Wayland session. If using X session everything work fine. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 489356] New: Windows restore to secondary screen in dual display setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=489356 Bug ID: 489356 Summary: Windows restore to secondary screen in dual display setup under Wayland Classification: Plasma Product: KScreen Version: 6.1.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kato...@gmail.com Target Milestone: --- SUMMARY When connecting a dual screen external dock after a single external screen session, windows are displayed on secondary (which is not marked as primary) screen. This problem is only on Wayland, X session works as expected. STEPS TO REPRODUCE 1. Connect to a dock with single external screen, have some windows open 2. Send the system to sleep 3. Connect to a dock with dual external screens 4. Wake up, login OBSERVED RESULT The windows are displayed on the secondary (not primary) screen EXPECTED RESULT Windows should be on the primary screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240619 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION I use 4 activities with 4 desktop each. Maybe connected to bug 486328. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 489356] Windows restore to secondary screen in dual display setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=489356 Gábor Katona changed: What|Removed |Added Version|6.1.0 |6.1.1 --- Comment #1 from Gábor Katona --- Just updated to 6.1.1 and it is still there. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 485865] New: Sharing from Krusader results in “org.kde.kdeconnect” is not installed error
https://bugs.kde.org/show_bug.cgi?id=485865 Bug ID: 485865 Summary: Sharing from Krusader results in “org.kde.kdeconnect” is not installed error Classification: Applications Product: krusader Version: 2.8.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: kato...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY When trying to share a file to KDEConnect from Krusader the following message appears: Failed to load the configuration page for this action: file:///usr/share/purpose/kdeconnectplugin_config.qml:11 module “org.kde.kdeconnect” is not installed. Sharing works fine from Dolphin. Using Tumbleweed with KDE6 STEPS TO REPRODUCE 1. Right click on a file 2. Go to Share, select KDE Connect SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240418 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] New: Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 Bug ID: 485971 Summary: Keepass tray icon breaks nearby icon, also tooltip is messed up Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kato...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 168805 --> https://bugs.kde.org/attachment.cgi?id=168805&action=edit Bad tooltip in upper left screen corner SUMMARY I use keepass2 under wine (not mono). Keepass2 has a minimize to tray option and it works (and worked in KDE5) fine. Since KDE6 however the tray icon is somehow broken: 1. After it is first started the tooltip of any window or desktop icon in the upper left corner of the screen will be the tooltip of Keepass (see keepass1.jpg). When Keepass is maximized and minimized it resolves. 2. The tray icon (the padlock) affects the nearby systray-x (Thunderbird) icon: hoovering over the systray-x icon the tooltip of keepass appears (keepass2.jpg) and clicking the icon act as clicking on keepass2 icon. However this does not always happen, because in some cases only some part of the systray-x icon is not clickable at all while other parts function normally. Some the keepass icon extends over the systray-x icon. STEPS TO REPRODUCE 1. Run Thunderbird with systray-x, so we have a tray icon for it 2. Run keepass with wine 3. Hover to the upper left corner after starting 4. Hover over Tb icon and try to click different parts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240418 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #1 from Gábor Katona --- Created attachment 168806 --> https://bugs.kde.org/attachment.cgi?id=168806&action=edit Broken tooltip over nerby icon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 Gábor Katona changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Gábor Katona --- (In reply to David Edmundson from comment #2) > Whilst this is open can you run > > systemctl --user stop plasma-xembedsniproxy.service > > > and confirm if the icon goes away? Yes, the keepass icon goes away when running this and restores if using start. Additional info that the non responding parts of the nearby systray-x icon seem to have some strange shape. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #5 from Gábor Katona --- Created attachment 168807 --> https://bugs.kde.org/attachment.cgi?id=168807&action=edit Output of xwininfo -tree -root Attached the output of xwininfo -tree -root. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #6 from Gábor Katona --- What do you mean by full xprop? I got the window id of the tray icon by running xwininfo and clicking on the icon than xprop -id -root said: _NET_SHOWING_DESKTOP(CARDINAL) = 0 _QT_GET_TIMESTAMP(INTEGER) = GDK_VISUALS(INTEGER) = 1022, 857 _NET_WORKAREA(CARDINAL) = 0, 0, 1920, 1036, 0, 0, 1920, 1036, 0, 0, 1920, 1036, 0, 0, 1920, 1036 RESOURCE_MANAGER(STRING) = "Xcursor.size:\t24\nXcursor.theme:\tbreeze_cursors\nXft.antialias:\t1\nXft.dpi:\t96\nXft.hinting:\t-1\nXft.rgba:\tnone\n" _KDE_NET_WM_BACKGROUND_CONTRAST_REGION(_KDE_NET_WM_BACKGROUND_CONTRAST_REGION) = 0x0 _KDE_NET_WM_BLUR_BEHIND_REGION(_KDE_NET_WM_BLUR_BEHIND_REGION) = 0x0 _KDE_WINDOW_HIGHLIGHT(_KDE_WINDOW_HIGHLIGHT) = 0x0 _KDE_SLIDE(_KDE_SLIDE) = 0x0 _NET_CLIENT_LIST_STACKING(WINDOW): window id # 0x107, 0x0, 0x0, 0x0, 0x0, 0x23a, 0x1ec, 0x0, 0x0 _NET_CLIENT_LIST(WINDOW): window id # 0x107, 0x23a, 0x1ec _NET_DESKTOP_GEOMETRY(CARDINAL) = 1920, 1080 _NET_ACTIVE_WINDOW(WINDOW): window id # 0x0 _NET_DESKTOP_NAMES(UTF8_STRING) = "Desktop 1", "Desktop 2", "Desktop 3", "Desktop 4" _NET_CURRENT_DESKTOP(CARDINAL) = 2 _NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0, 0, 0, 0, 0, 0, 0 _NET_NUMBER_OF_DESKTOPS(CARDINAL) = 4 _NET_DESKTOP_LAYOUT(CARDINAL) = 0, 2, 2, 0 _NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x21 _NET_SUPPORTED(ATOM) = _NET_SUPPORTED, _NET_SUPPORTING_WM_CHECK, _NET_CLIENT_LIST, _NET_CLIENT_LIST_STACKING, _NET_NUMBER_OF_DESKTOPS, _NET_DESKTOP_GEOMETRY, _NET_CURRENT_DESKTOP, _NET_DESKTOP_NAMES, _NET_ACTIVE_WINDOW, _NET_WORKAREA, _NET_DESKTOP_LAYOUT, _NET_CLOSE_WINDOW, _NET_RESTACK_WINDOW, _NET_SHOWING_DESKTOP, _NET_WM_MOVERESIZE, _NET_MOVERESIZE_WINDOW, _NET_WM_NAME, _NET_WM_VISIBLE_NAME, _NET_WM_DESKTOP, _NET_WM_WINDOW_TYPE, _NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_DESKTOP, _NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_TOOLBAR, _NET_WM_WINDOW_TYPE_MENU, _NET_WM_WINDOW_TYPE_DIALOG, _NET_WM_WINDOW_TYPE_UTILITY, _NET_WM_WINDOW_TYPE_SPLASH, _KDE_NET_WM_WINDOW_TYPE_OVERRIDE, _NET_WM_STATE, _NET_WM_STATE_MODAL, _NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ, _NET_WM_STATE_SHADED, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_SKIP_PAGER, _KDE_NET_WM_STATE_SKIP_SWITCHER, _NET_WM_STATE_HIDDEN, _NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_ABOVE, _NET_WM_STATE_STAYS_ON_TOP, _NET_WM_STATE_BELOW, _NET_WM_STATE_DEMANDS_ATTENTION, _NET_WM_STATE_FOCUSED, _NET_WM_STRUT, _NET_WM_STRUT_PARTIAL, _NET_WM_ICON_GEOMETRY, _NET_WM_ICON, _NET_WM_PID, _NET_WM_PING, _NET_WM_USER_TIME, _NET_STARTUP_ID, _NET_WM_WINDOW_OPACITY, _NET_WM_FULLSCREEN_MONITORS, _NET_WM_ALLOWED_ACTIONS, _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_FRAME_EXTENTS, _KDE_NET_WM_FRAME_STRUT, _NET_WM_FULL_PLACEMENT, _KDE_NET_WM_ACTIVITIES, _KDE_NET_WM_SHADOW, _NET_WM_OPAQUE_REGION, _GTK_FRAME_EXTENTS, _GTK_SHOW_WINDOW_MENU _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", "" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485971] Keepass tray icon breaks nearby icon, also tooltip is messed up
https://bugs.kde.org/show_bug.cgi?id=485971 --- Comment #7 from Gábor Katona --- Created attachment 168808 --> https://bugs.kde.org/attachment.cgi?id=168808&action=edit xprop output for keepass window Attached the output of xprop for the visible keepass window. (sorry, the previous xprop output should have been attached also) Or do you need other info? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 486328] New: External screens switch off when laptop lid is closed with USB-C dock with dual monitor (single monitor works)
https://bugs.kde.org/show_bug.cgi?id=486328 Bug ID: 486328 Summary: External screens switch off when laptop lid is closed with USB-C dock with dual monitor (single monitor works) Classification: Plasma Product: KScreen Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kato...@gmail.com Target Milestone: --- SUMMARY Using openSUSE Tumbleweed on a Lenovo X1 Carbon Gen9. I have a setup with a Lenovo USB-C dock with two external screens connected. It is configured to have only the external screens when connected (built-in screen disabled). When I close the lid of the laptop all external screens switch off since probably last week. Before it was not happening and nothing was changed in settings. When doing a fresh boot with lid closed the login screen is on both external screens but after login they switch off. Opening the lid switches on external screens as expected (built-in screen is disabled as set). Additionally after closing and opening the lid some windows are shifted halfway off the screen (see attachment). If I disconnect one of the monitors physically, it works as expected. Connecting immediately results in switch off of both external screens if lid is closed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed 20240428 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 486328] External screens switch off when laptop lid is closed with USB-C dock with dual monitor (single monitor works)
https://bugs.kde.org/show_bug.cgi?id=486328 --- Comment #1 from Gábor Katona --- Created attachment 169030 --> https://bugs.kde.org/attachment.cgi?id=169030&action=edit Window shifted halfway off screen after opening lid -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 484808] Unresponsive black screen when disconnecting external monitor with laptop lid closed
https://bugs.kde.org/show_bug.cgi?id=484808 Gábor Katona changed: What|Removed |Added Version|6.0.3 |6.0.4 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 484808] Unresponsive black screen when disconnecting external monitor with laptop lid closed
https://bugs.kde.org/show_bug.cgi?id=484808 --- Comment #2 from Gábor Katona --- I also have the following experience: Same laptop, USB-C dock with dual monitors connected. I send the laptop to sleep. After wakeup ALL screens are black and disconnecting the dock does not bring back the built-in screen. I think this is the same bug, since sleep is essentially disconnecting the external monitor. This practically renders sleep broken. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 --- Comment #17 from Gábor Katona --- The same bug is still present in KDE6, as I reported in 484806 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 --- Comment #18 from Gábor Katona --- bug 484806 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469264] New: KDE applications (krusader, kile, okular, etc) crash when connecting usb-c dock with external screen
https://bugs.kde.org/show_bug.cgi?id=469264 Bug ID: 469264 Summary: KDE applications (krusader, kile, okular, etc) crash when connecting usb-c dock with external screen Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-multiscreen Assignee: plasma-b...@kde.org Reporter: kato...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY When connecting or disconnecting my laptop to/from a usb-c dock, sometimes (I would estimate a 30-40% rate) one or more KDE application crashes. These include krusade, kile, okular. Sometimes no crash, sometimes only one application crashes, but in some cases 2 or more just crashes. I have already submitted some bugreports through drkonqi: https://bugs.kde.org/show_bug.cgi?id=465077 https://bugs.kde.org/show_bug.cgi?id=465146 and others also did: https://bugs.kde.org/show_bug.cgi?id=467419 STEPS TO REPRODUCE This bug does not happen always, however the trigger is simply the connection of the usb-c dock with external screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20230425 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469264] KDE applications (krusader, kile, okular, etc) crash when connecting usb-c dock with external screen
https://bugs.kde.org/show_bug.cgi?id=469264 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465077] QtWidgets-based apps crash in QXcbBackingStoreImage::flushPixmap when connecting/disconnecting external screen
https://bugs.kde.org/show_bug.cgi?id=465077 --- Comment #6 from Gábor Katona --- Thank you for checking. Should I file a Qt bug report, or is it better, if you or someone similarly competent file the bug based on the crash reports? If needed, I can produce such crash reports several times a week. Unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469256] Icons on my desktop got rearranged after switching screens
https://bugs.kde.org/show_bug.cgi?id=469256 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469256] Icons on my desktop got rearranged after switching screens
https://bugs.kde.org/show_bug.cgi?id=469256 --- Comment #1 from Gábor Katona --- Previously I have reported bug 464873 which was resolved and I was indeed not experiencing the problem for some time. But after a short time it started again. Now it again happens on a daily basis as I connect my laptop at home and at work to usb-c docks with external screen(s). I am on openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465077] QtWidgets-based apps crash in QXcbBackingStoreImage::flushPixmap when connecting/disconnecting external screen
https://bugs.kde.org/show_bug.cgi?id=465077 --- Comment #7 from Gábor Katona --- I think this Qt bug is the same: https://bugreports.qt.io/browse/QTBUG-109226 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465146] Okular crashes when connecting to usb-c dock with external monitor
https://bugs.kde.org/show_bug.cgi?id=465146 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 484162] New: Keyboard brightness OSD always shows up on activity change
https://bugs.kde.org/show_bug.cgi?id=484162 Bug ID: 484162 Summary: Keyboard brightness OSD always shows up on activity change Classification: Plasma Product: kactivitymanagerd Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: kato...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** When changing activity the keyboard brightness OSD always shows up for a few seconds. *** STEPS TO REPRODUCE 1. Change activity OBSERVED RESULT The keyboard brightness OSD always shows up for a few seconds. EXPECTED RESULT It should not show up. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20240319 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483770] Icons position on the desktop get scrambled with multimonitor
https://bugs.kde.org/show_bug.cgi?id=483770 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com --- Comment #1 from Gábor Katona --- I have the same problem with openSUSE Tumbleweed, KDE 6.0.2. This was a log staying problem with KDE 5 but it was mostly solved for the last half year or so. But now it seems back to the starting point. Additionally there are bugs in multi-monitor handling which were already solved in KDE5, and also new ones. I will report these separately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484806] New: Desktop icons rearrange when disconnecting and reconnecting external screen
https://bugs.kde.org/show_bug.cgi?id=484806 Bug ID: 484806 Summary: Desktop icons rearrange when disconnecting and reconnecting external screen Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: kato...@gmail.com CC: h...@kde.org Target Milestone: 1.0 SUMMARY The desktop icon rearrange when connecting/disconnecting an external screen (set as only screen) connected to a USB-C dock. If the icons are arranged with the external screen connected then after disconnecting the screen some icons will be placed randomly. After reconnecting the same screen, the icons are now sorted by name. If the icons are arranged with only the laptop screen then after connecting the external screen some icons get randomly placed. Disconnecting the external screen makes other icons to move around and after reconnecting the external screen they are again sorted by name. Switching between screen by software has the same result and in this I have realized that probably plasmashell is restarting (the panel disappeared and reappeared. Similar bug were in 5.27, but it was mostly resolved. STEPS TO REPRODUCE 1. Arrange icons with external screen connected 2. Disconnect external screen 3. Reconnect external screen OBSERVED RESULT The icons move around and at the end sorted by name. EXPECTED RESULT Icon arrangement should not change. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240326 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION see e.g.: bug464873, bug469256 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 484808] New: Unresponsive black screen when disconnecting external monitor with laptop lid closed
https://bugs.kde.org/show_bug.cgi?id=484808 Bug ID: 484808 Summary: Unresponsive black screen when disconnecting external monitor with laptop lid closed Classification: Plasma Product: KScreen Version: 6.0.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kato...@gmail.com Target Milestone: --- SUMMARY I have my laptop connected to a USB-C dock with an external screen. When I disconnect the laptop from the dock with the laptop lid closed (so the external is the only screen) very often the result is a totally black screen on the laptop (without even mouse) and the laptop is totally unresponsive. Reconnecting to the hub does not solve, only long press power button helps. In some cases the result is only a black screen with mouse, when I can start a console and start plasmashell. Yes, it has to be started, because it is not running, at least kquitapp6 says this. STEPS TO REPRODUCE 1. Disconnect the external screen with laptop lid closed. OBSERVED RESULT Unresponsive black screen or black screen with only mouse EXPECTED RESULT It should work normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: oopenSUSE Tumbleweed 20240326 (available in About System) KDE Plasma Version: 6.0.3. KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION seems very similar to bug476340 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484806] Desktop icons rearrange when disconnecting and reconnecting external screen
https://bugs.kde.org/show_bug.cgi?id=484806 --- Comment #1 from Gábor Katona --- More info: issuing kquitapp6 plasmashell && kstart plasmashell restores the set order. But disconnecting the screen again destroys. This is exactly the same that was observed in bug464873 more than a year ago. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452083] New: KWin crashes when connecting Displayport monitor via usb-c dock
https://bugs.kde.org/show_bug.cgi?id=452083
Bug ID: 452083
Summary: KWin crashes when connecting Displayport monitor via
usb-c dock
Product: kwin
Version: 5.24.3
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: kato...@gmail.com
Target Milestone: ---
Application: kwin_x11 (5.24.3)
Qt Version: 5.15.2
Frameworks Version: 5.92.0
Operating System: Linux 5.16.15-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.3 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed: I have connected my USB-C dock
to the laptop. The USB-C dock has a monitor connected to Displayport. After
connection the external screen is activated and KWin cracsh is reported. The
crash result is versatile, sometimes nothing strange is visible, but it also
happens, that the panel is not at the bottom of the screen but somewhere above.
In other cases windows loose activity binding and appear on all activities.
These effects are random, however the crash is permanent. In case of the
current report the panel moved from the bottom.
The crash can be reproduced every time.
-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x in ()
#7 0x7fdc979685a2 in KWin::Toplevel::isOnOutput(KWin::AbstractOutput*)
const (this=0x55f11bac1450, output=) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/toplevel.cpp:423
#8 0x7fdc979a0b29 in KWin::Workspace::activeOutput() const
(this=0x55f11b71e580) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/workspace.cpp:2419
#9 0x7fdc979adc5f in KWin::X11Client::manage(unsigned int, bool)
(this=0x55f11ba98370, w=, isMapped=) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/workspace.h:811
#10 0x7fdc97993843 in KWin::Workspace::createClient(unsigned int, bool)
(this=0x55f11b71e580, w=37749093, is_mapped=) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/workspace.cpp:654
#11 0x7fdc978cbb1d in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
(this=0x55f11b71e580, e=0x7fdc8800a220) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/events.cpp:223
#12 0x7fdc95dba3cf in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
(this=, eventType=..., message=message@entry=0x7fdc8800a220,
result=result@entry=0x7ffe66c2d2f8) at kernel/qabstracteventdispatcher.cpp:495
#13 0x7fdc902cd491 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
(this=this@entry=0x55f11b46c270, event=event@entry=0x7fdc8800a220) at
qxcbconnection.cpp:536
#14 0x7fdc902ceb96 in
QXcbConnection::processXcbEvents(QFlags)
(this=0x55f11b46c270, flags=...) at qxcbconnection.cpp:1020
#15 0x7fdc902f51bc in
QXcbUnixEventDispatcher::processEvents(QFlags)
(this=0x55f11b533d30, flags=...) at qxcbeventdispatcher.cpp:61
#16 0x7fdc95dbb83b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffe66c2d440, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#17 0x7fdc95dc3b10 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#18 0x7fdc9620d25c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1867
#19 0x7fdc953729f5 in QApplication::exec() () at
kernel/qapplication.cpp:2824
#20 0x55f119ec2509 in main(int, char**) (argc=,
argv=0x7ffe66c2d708) at
/usr/src/debug/kwin5-5.24.3-1.2.x86_64/src/main_x11.cpp:482
[Inferior 1 (process 5626) detached]
Possible duplicates by query: bug 451972, bug 450954, bug 450924, bug 450337,
bug 448064.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 452083] KWin crashes when connecting Displayport monitor via usb-c dock
https://bugs.kde.org/show_bug.cgi?id=452083 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452083] KWin crashes when connecting Displayport monitor via usb-c dock
https://bugs.kde.org/show_bug.cgi?id=452083 --- Comment #1 from Gábor Katona --- Created attachment 147847 --> https://bugs.kde.org/attachment.cgi?id=147847&action=edit New crash information added by DrKonqi kwin_x11 (5.24.3) using Qt 5.15.2 - What I was doing when the application crashed: I have reported this crash. This time the panel stayed in place but open windows lost their activity binding and appeared on all activities. -- Backtrace (Reduced): #6 0x7f197154e59c in KWin::Toplevel::isOnOutput(KWin::AbstractOutput*) const (this=0x5607efda1190, output=0x5607efc48f10) at /usr/src/debug/kwin5-5.24.3-2.1.x86_64/src/toplevel.cpp:423 #7 0x7f1971586b29 in KWin::Workspace::activeOutput() const (this=0x5607efa03a60) at /usr/src/debug/kwin5-5.24.3-2.1.x86_64/src/workspace.cpp:2419 #8 0x7f1971593c5f in KWin::X11Client::manage(unsigned int, bool) (this=0x5607efda4e50, w=, isMapped=) at /usr/src/debug/kwin5-5.24.3-2.1.x86_64/src/workspace.h:811 #9 0x7f1971579843 in KWin::Workspace::createClient(unsigned int, bool) (this=0x5607efa03a60, w=37748931, is_mapped=) at /usr/src/debug/kwin5-5.24.3-2.1.x86_64/src/workspace.cpp:654 #10 0x7f19714b1b1d in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x5607efa03a60, e=0x7f1964006c70) at /usr/src/debug/kwin5-5.24.3-2.1.x86_64/src/events.cpp:223 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452083] KWin crashes when connecting Displayport monitor via usb-c dock
https://bugs.kde.org/show_bug.cgi?id=452083 --- Comment #2 from Gábor Katona --- As I can recall this crashing behavior appeared with the 5.24 branch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452083] KWin crashes when connecting Displayport monitor via usb-c dock
https://bugs.kde.org/show_bug.cgi?id=452083 Gábor Katona changed: What|Removed |Added Component|general |multi-screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 Gábor Katona changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #14 from Gábor Katona --- It is partly offtopic, but could you advise me where to report screen detection issues? The screens connected to usb-c dock are not detected reliably. Maybe it is also connected to KDE screen management, because I feel like it became worse since 5.27, but not sure. I feel more like a hardware detection issue (sometimes even the screen EDIDs are mixed up) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] New: Icons on active activity reorder after logout or screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 Bug ID: 464873 Summary: Icons on active activity reorder after logout or screen connect/disconnect Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: kato...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY I am using activities and with 5.26.90 I have realized that while the old screen management issues are gone, a new issue appeared. I have different set of icons on the desktop for each activity. When I log out and log in again the icons on the activity I was at when logging out are reordered by name and moved to the upper left edge. The other activities are not affected. If I log out from another activity, then that will be affected, so it is not linked to a specific activity, always the active suffers. It also happens when I disconnect and connect a screen, however in this case after disconnection only some of the icons change position and after re-connection they are moved to the upper left edge and ordered by name. STEPS TO REPRODUCE 1. Setup more than one activity 2. Arrange the icons on each activity so that they re not ordered by name. 3. Log out and log in OBSERVED RESULT The icons change their position and order. EXPECTED RESULT The icons should stay in place. SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed 20230123 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Using a Lenovo laptop with 1920x1200 resolution with an external screen with 1920x1080. Only one screen is active at a time. The issue also happens when manually switching the screens without physical disconnection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after logout or screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 Gábor Katona changed: What|Removed |Added Summary|Icons on active activity|Icons on active activity |reorder after logout or |reorder after screen |screen connect/disconnect |connect/disconnect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 --- Comment #1 from Gábor Katona --- I have just made further tests. It seems that log out and log in is not affected in reality. The case is that when I logged out, there was screen change (the built-in screen is activated). When logging out without external screen attached the issue does not happen. So it is connected to screen management, maybe the component should be changed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 Gábor Katona changed: What|Removed |Added CC||aleix...@kde.org Component|Desktop Containment |Multi-screen support -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873
--- Comment #3 from Gábor Katona ---
Definitely great progress so far, although I still have problems with detecting
the screens attached to docking station, but I think this is hardware detection
problem.
I guess (maybe) launcher widgets for apps, for me these are just icons to start
a program: I have set the desktop to show a folder, which contains .desktop
files to start applications.
This is from plasma-org.kde.plasma.desktop-appletsrc
positions={"1920x1080":["1"\\,"20"\\,"file:///home/katonag/.Desktop/Firefox"\\,"0"\\,"0"\\,"file:///home/katonag/.Desktop/Krusader"\\,"0"\\,"1"\\,"file:///home/katonag/.Desktop/Thunderbird"\\,"0"\\,"2"\\,"file:///home/katonag/.Desktop/Windows10"\\,"0"\\,"3"]\\,"1920x1200":["4"\\,"20"\\,"file:///home/katonag/.Desktop/Windows10"\\,"3"\\,"5"\\,"file:///home/katonag/.Desktop/Firefox"\\,"3"\\,"8"\\,"file:///home/katonag/.Desktop/Thunderbird"\\,"3"\\,"6"\\,"file:///home/katonag/.Desktop/Krusader"\\,"3"\\,"7"]\\,"0x0":["1"\\,"20"\\,"file:///home/katonag/.Desktop/Firefox"\\,"0"\\,"0"\\,"file:///home/katonag/.Desktop/Krusader"\\,"0"\\,"1"\\,"file:///home/katonag/.Desktop/Thunderbird"\\,"0"\\,"2"\\,"file:///home/katonag/.Desktop/Windows10"\\,"0"\\,"3"]}
Originally Firefox was the last entry in a row at the top left edge.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 --- Comment #4 from Gábor Katona --- More info: issuing kquitapp5 plasmashell && kstart plasmashell restores the set order -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 465077] New: Krusader crashes when connecting/disconnecting external screen
https://bugs.kde.org/show_bug.cgi?id=465077 Bug ID: 465077 Summary: Krusader crashes when connecting/disconnecting external screen Classification: Applications Product: krusader Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: kato...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.8.0 "A New Day") Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.8-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.90 [KCrashBackend] -- Information about the crash: When I connect or disconnect an external screen via a USB-C hub to my laptop put to sleep and wake it up, Krusader crashes. The crash happens in about 70-80% of connection changes. As I remember it also happened when the laptop was not sleeping. The crash can be reproduced every time. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault [KCrash Handler] #4 0x7ff6d6b7aa0d in __memmove_evex_unaligned_erms () from /lib64/libc.so.6 #5 0x7ff6d30ed3ba in memmove (__len=262112, __src=0x7ff2119fe810, __dest=) at /usr/include/bits/string_fortified.h:36 #6 copy_unswapped (rect=..., img=warning: RTTI symbol for class 'QImage' is not a type ..., dstBytesPerLine=262112, dst=) at qxcbbackingstore.cpp:547 #7 native_sub_image (swap=false, rect=..., src=warning: RTTI symbol for class 'QImage' is not a type ..., dstStride=262112, buffer=0x556c0a822500) at qxcbbackingstore.cpp:590 #8 QXcbBackingStoreImage::flushPixmap (this=0x556c0a822480, region=..., fullRegion=) at qxcbbackingstore.cpp:669 #9 0x7ff6d30ed9b9 in QXcbBackingStoreImage::flushPixmap (fullRegion=false, region=..., this=0x556c0a822480) at qxcbbackingstore.cpp:627 #10 QXcbBackingStoreImage::put (this=0x556c0a822480, dst=96469013, region=..., offset=...) at qxcbbackingstore.cpp:741 #11 0x7ff6d30ee2f9 in QXcbBackingStore::flush (this=this@entry=0x7ff6c4009830, window=window@entry=0x556c0ab0e8f0, region=..., offset=...) at /usr/src/debug/qtbase-everywhere-src-5.15.8+kde160/src/plugins/platforms/xcb/qxcbwindow.h:120 #12 0x7ff6d794d462 in QBackingStore::flush (this=this@entry=0x556c0a972960, region=..., window=0x556c0ab0e8f0, offset=...) at painting/qbackingstore.cpp:252 #13 0x7ff6d7fb2a7f in QWidgetRepaintManager::flush (this=this@entry=0x556c0a7eba00, widget=0x556c0a7b4630, region=..., widgetTextures=) at kernel/qwidgetrepaintmanager.cpp:1198 #14 0x7ff6d7fb4609 in QWidgetRepaintManager::flush (this=0x556c0a7eba00) at kernel/qwidgetrepaintmanager.cpp:1096 #15 0x7ff6d7fb6688 in QWidgetRepaintManager::paintAndFlush (this=0x556c0a7eba00) at kernel/qwidgetrepaintmanager.cpp:1028 #16 0x7ff6d7fff3e1 in QWidgetWindow::handleResizeEvent (this=0x556c0ab0e8f0, event=0x7ffe1bab5990) at kernel/qwidgetwindow.cpp:841 #17 0x7ff6d800334b in QWidgetWindow::event (this=0x556c0ab0e8f0, event=0x7ffe1bab5990) at kernel/qwidgetwindow.cpp:322 #18 0x7ff6d7fa544e in QApplicationPrivate::notify_helper (this=, receiver=0x556c0ab0e8f0, e=0x7ffe1bab5990) at kernel/qapplication.cpp:3640 #19 0x7ff6d72dc138 in QCoreApplication::notifyInternal2 (receiver=0x556c0ab0e8f0, event=0x7ffe1bab5990) at kernel/qcoreapplication.cpp:1064 #20 0x7ff6dccc in QGuiApplicationPrivate::processGeometryChangeEvent (e=) at kernel/qguiapplication.cpp:2610 #21 0x7ff6d774f26c in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #22 0x7ff6d30f814a in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:105 #23 0x7ff6d5c6ea90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7ff6d5c6ee48 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7ff6d5c6eedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7ff6d7333b66 in QEventDispatcherGlib::processEvents (this=0x556c0a59ab10, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #27 0x7ff6d72dabab in QEventLoop::exec (this=this@entry=0x7ffe1bab5c10, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #28 0x7ff6d72e2d16 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #29 0x7ff6d776ed3c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870 #30 0x7ff6d7fa53c5 in QApplication::exec () at kernel/qapplication.cpp:2832 #31 0x556c09d467d3 in main (argc=, argv=) at /usr/src/debug/krusader-2.8.0/app/main.cpp:307 [Inferior 1 (process 3896) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 465077] Krusader crashes when connecting/disconnecting external screen
https://bugs.kde.org/show_bug.cgi?id=465077 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 465077] Krusader crashes when connecting/disconnecting external screen
https://bugs.kde.org/show_bug.cgi?id=465077 Gábor Katona changed: What|Removed |Added Version|unspecified |2.8.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465146] New: Okular crashes when connecting to usb-c dock with external monitor
https://bugs.kde.org/show_bug.cgi?id=465146 Bug ID: 465146 Summary: Okular crashes when connecting to usb-c dock with external monitor Classification: Applications Product: okular Version: 22.12.1 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kato...@gmail.com Target Milestone: --- Application: okular (22.12.1) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.8-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.90 [KCrashBackend] -- Information about the crash: When connecting my laptop to a usb-c dock with external monitor connected to the dock, okular somatimes crashes. The crash can be reproduced sometimes. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7f7cd6d7aa0d in __memmove_evex_unaligned_erms () from /lib64/libc.so.6 #5 0x7f7cd2d0e3ba in memmove (__len=262112, __src=0x7f77ad9fe810, __dest=) at /usr/include/bits/string_fortified.h:36 #6 copy_unswapped (rect=..., img=warning: RTTI symbol for class 'QImage' is not a type ..., dstBytesPerLine=262112, dst=) at qxcbbackingstore.cpp:547 #7 native_sub_image (swap=false, rect=..., src=warning: RTTI symbol for class 'QImage' is not a type ..., dstStride=262112, buffer=0x565536aa2de0) at qxcbbackingstore.cpp:590 #8 QXcbBackingStoreImage::flushPixmap (this=0x565536aa2d60, region=..., fullRegion=) at qxcbbackingstore.cpp:669 #9 0x7f7cd2d0e9b9 in QXcbBackingStoreImage::flushPixmap (fullRegion=false, region=..., this=0x565536aa2d60) at qxcbbackingstore.cpp:627 #10 QXcbBackingStoreImage::put (this=0x565536aa2d60, dst=96469004, region=..., offset=...) at qxcbbackingstore.cpp:741 #11 0x7f7cd2d0f2f9 in QXcbBackingStore::flush (this=this@entry=0x5655361f2df0, window=window@entry=0x5655361f2d90, region=..., offset=...) at /usr/src/debug/qtbase-everywhere-src-5.15.8+kde160/src/plugins/platforms/xcb/qxcbwindow.h:120 #12 0x7f7cd7b4d462 in QBackingStore::flush (this=this@entry=0x5655362c96f0, region=..., window=0x5655361f2d90, offset=...) at painting/qbackingstore.cpp:252 #13 0x7f7cd81b2a7f in QWidgetRepaintManager::flush (this=this@entry=0x5655362bcff0, widget=0x565536095790, region=..., widgetTextures=) at kernel/qwidgetrepaintmanager.cpp:1198 #14 0x7f7cd81b4609 in QWidgetRepaintManager::flush (this=0x5655362bcff0) at kernel/qwidgetrepaintmanager.cpp:1096 #15 0x7f7cd81b6688 in QWidgetRepaintManager::paintAndFlush (this=0x5655362bcff0) at kernel/qwidgetrepaintmanager.cpp:1028 #16 0x7f7cd81ff3e1 in QWidgetWindow::handleResizeEvent (this=0x5655361f2d90, event=0x7ffc5c6116e0) at kernel/qwidgetwindow.cpp:841 #17 0x7f7cd820334b in QWidgetWindow::event (this=0x5655361f2d90, event=0x7ffc5c6116e0) at kernel/qwidgetwindow.cpp:322 #18 0x7f7cd81a544e in QApplicationPrivate::notify_helper (this=, receiver=0x5655361f2d90, e=0x7ffc5c6116e0) at kernel/qapplication.cpp:3640 #19 0x7f7cd74dc138 in QCoreApplication::notifyInternal2 (receiver=0x5655361f2d90, event=0x7ffc5c6116e0) at kernel/qcoreapplication.cpp:1064 #20 0x7f7cd7977ccc in QGuiApplicationPrivate::processGeometryChangeEvent (e=) at kernel/qguiapplication.cpp:2610 #21 0x7f7cd794f26c in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #22 0x7f7cd2d1914a in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:105 #23 0x7f7cd5b1ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f7cd5b1be48 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7f7cd5b1bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f7cd7533b66 in QEventDispatcherGlib::processEvents (this=0x565535f13440, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #27 0x7f7cd74dabab in QEventLoop::exec (this=this@entry=0x7ffc5c611960, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #28 0x7f7cd74e2d16 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #29 0x5655356e61f6 in ?? () #30 0x7f7cd6c2c5b0 in __libc_start_call_main () from /lib64/libc.so.6 #31 0x7f7cd6c2c679 in __libc_start_main_impl () from /lib64/libc.so.6 #32 0x5655356e6d05 in ?? () [Inferior 1 (process 2164) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 --- Comment #6 from Gábor Katona --- Sorry for the late reply. I have tested it by creating a fresh user. I have logged in, the desktop had Trash and Home as default. I have added Firefox and System setting simply by copying from the panel. Ordered them (see fig 1.png) in reverse alphabetical order and Trash moved away. After disconnecting the external screen the icons were reordered in some random way (2.png). Reconnecting the external screen resulted again in reordering (3.png), now in alphabetical order, except Trash, which is moved to the top left corner, where it was originally. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 --- Comment #7 from Gábor Katona --- Created attachment 156021 --> https://bugs.kde.org/attachment.cgi?id=156021&action=edit Desktop icons arranged originally -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 --- Comment #8 from Gábor Katona --- Created attachment 156022 --> https://bugs.kde.org/attachment.cgi?id=156022&action=edit Desktop icons afre disconnecting external screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 --- Comment #9 from Gábor Katona --- Created attachment 156023 --> https://bugs.kde.org/attachment.cgi?id=156023&action=edit Desktop icons after reconnecting external screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464873] Icons on active activity reorder after screen connect/disconnect
https://bugs.kde.org/show_bug.cgi?id=464873 Gábor Katona changed: What|Removed |Added Attachment #156022|Desktop icons afre |Desktop icons after description|disconnecting external |disconnecting external |screen |screen -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 465077] Krusader crashes when connecting/disconnecting external screen
https://bugs.kde.org/show_bug.cgi?id=465077 --- Comment #1 from Gábor Katona --- Created attachment 156084 --> https://bugs.kde.org/attachment.cgi?id=156084&action=edit New crash information added by DrKonqi krusader (2.8.0 "A New Day") using Qt 5.15.8 Krusader crash when connecting external screen via usb-c dock -- Backtrace (Reduced): #5 0x7efe206373ba in memmove (__len=262112, __src=0x7ef95d9fe810, __dest=) at /usr/include/bits/string_fortified.h:36 #8 QXcbBackingStoreImage::flushPixmap (this=0x55ea709d3e60, region=..., fullRegion=) at qxcbbackingstore.cpp:669 #9 0x7efe206379b9 in QXcbBackingStoreImage::flushPixmap (fullRegion=false, region=..., this=0x55ea709d3e60) at qxcbbackingstore.cpp:627 #10 QXcbBackingStoreImage::put (this=0x55ea709d3e60, dst=79691797, region=..., offset=...) at qxcbbackingstore.cpp:741 #11 0x7efe206382f9 in QXcbBackingStore::flush (this=this@entry=0x7efe10009c60, window=window@entry=0x55ea70836e30, region=..., offset=...) at /usr/src/debug/qtbase-everywhere-src-5.15.8+kde160/src/plugins/platforms/xcb/qxcbwindow.h:120 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460977] New: One pixel line below and above panel
https://bugs.kde.org/show_bug.cgi?id=460977 Bug ID: 460977 Summary: One pixel line below and above panel Classification: Plasma Product: plasmashell Version: 5.26.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kato...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 153191 --> https://bugs.kde.org/attachment.cgi?id=153191&action=edit Image showing the onepixel lines SUMMARY There is a one pixel line above and below the panel, and also on the right side. This appeared recently, I guess with 5.26 STEPS TO REPRODUCE After an update the pixel lines appeared. OBSERVED RESULT There is a one pixel line above and below the panel, and also on the right side. See attached image. EXPECTED RESULT There should not be one pixel line around the panel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20221022 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460977] One pixel line below and above panel
https://bugs.kde.org/show_bug.cgi?id=460977 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460977] One pixel line around panel
https://bugs.kde.org/show_bug.cgi?id=460977 Gábor Katona changed: What|Removed |Added Summary|One pixel line below and|One pixel line around panel |above panel | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460977] One pixel line around panel
https://bugs.kde.org/show_bug.cgi?id=460977 --- Comment #1 from Gábor Katona --- I have just noticed that this one pixel line is around the panel, it was not visible because of the background image set. So it is like a 1 pixel wide frame or margin. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461008] New: Desktop icon position and desktop setup partially lost when changing screen setup
https://bugs.kde.org/show_bug.cgi?id=461008 Bug ID: 461008 Summary: Desktop icon position and desktop setup partially lost when changing screen setup Classification: Plasma Product: KScreen Version: 5.26.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kato...@gmail.com Target Milestone: --- SUMMARY My laptop is either used on it own or connected to a dock having two monitors connected. When connected to the dock I setup the desktop by setting the desktop folder for each screen and arrange the icons. First it should be noted that I cannot use the same folder for both screens, because setting the same folder for the second screen results in empty desktop. I do not know if it is a bug or on purpose, but it required me to make a symbolic link to the desktop folder and use that for the second screen. After I have setup the desktop I lock icons. When I disconnect it from the dock, the desktop sometimes (!) becomes empty. Only reconnecting to the dock or restarting plasmashell gets back the icons, however now the positions of the icons are lost and they are ordered by name. In other cases the desktop is not empty but the icon positions are lost (become ordered by name), and it also happens, that everything is fine but after reconnecting to the dock the icon positions are lost (become ordered by name) on one or both screens. It also happened that the second screen was totally fresh; i.e. default background, default folder, no panel, etc. It seems that somehow kscreen cannot correctly deal with screen setup changes or plasmashell does not understand what kscreen says and incorrectly restores the desktop. Maybe some setup files should be deleted and recreated, but I do not know which, and nevertheless, this should not happen. I am happy to do any test, report log, just tell what you need. STEPS TO REPRODUCE 1. Setup a two screen layout with a dock, position icons on both screens (the desktop folder for the second screen is a symlink to the desktop folder of the first screen, so we have the same icons, but position can be different), add panel setup background 2. Disconnect the dock either with the laptop running or with sent to sleep 3. Check the desktop on the laptop screen 4. Reconnect to the dock OBSERVED RESULT The desktop setup is not kept. Sometimes just the icon positions change and they become sorted by name, in other cases no icons are show at all. It is not predictable. Seems that it depends on the moment of disconnection. EXPECTED RESULT The desktop setup, icons arrangement should be kept SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20221022 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461008] Desktop icon position and desktop setup partially lost when changing screen setup
https://bugs.kde.org/show_bug.cgi?id=461008 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 --- Comment #83 from Gábor Katona --- Which Plasma version will contain the fix? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 --- Comment #15 from Gábor Katona --- Opensuse Tumbleweed is still on 5.12.3 which still has the issue. Maybe in a few days they will release 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375341] Screen lock freezes after removing external screens
https://bugs.kde.org/show_bug.cgi?id=375341 --- Comment #4 from Gábor Katona --- Now using Plasma 5.16.5 and the bug is not present -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388250] Device notifier pops up in double instance after disconnecting external screens
https://bugs.kde.org/show_bug.cgi?id=388250 --- Comment #2 from Gábor Katona --- No. At the moment it works as expected with Plasma 5.17.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388250] Device notifier pops up in double instance after disconnecting external screens
https://bugs.kde.org/show_bug.cgi?id=388250 Gábor Katona changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388250] Device notifier pops up in double instance after disconnecting external screens
https://bugs.kde.org/show_bug.cgi?id=388250 Gábor Katona changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] New: Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 Bug ID: 389745 Summary: Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen Product: plasmashell Version: 5.11.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: kato...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 openSUSE Tumbleweed KDE Plasma: 5.11.95 KDE Frameworks: 5.42.0 Qt: 5.10.0 I use the folderview desktop mode with custom desktop folders for each of my activities. I have two screens, the problem is not present when using only one screen. After yesterdays update (after about two weeks without update) the icons were not shown after restart. Then they appeared on one activity, but only on first screen. Trying to add a new item resulted in adding it to the set folder, but it was not shown (just as the others), or it was shown alone, without the rest. After restarting plasmashell the icons sometimes appear, but only on the first screen. After several restart now the icons seem stable on the first screen, but the second screen does not show anything apart from wallpaper. Changing the folder to be shown does not do anything. Changing to show own folder works on one activity but does not on the other. It seems to be a big mess between activities, multi screen and folderview -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 --- Comment #2 from Gábor Katona --- I use my laptop with a docking station. The docking station has two screens connected. When docked only the two external screens are active, the laptop screen is off. I have 4 activities all having 4 desktops. All activities are set to folder view. The folders are .Desktop.1 .Desktop.2 and so on. Currently I have icons on all activities on one of the screens (the same for all activities), however I only have icons on activity 1 and 3 for the other screen. Now I have tried to change the folder for screen2 on activity1. The result is empty desktop. Changing back to .Desktop.1 still empty. BUT! On screen2 activity4 the icons appeared (corresponding to the set folder). Now changing the folder on activity4 screen2 the icons disappear, but they appear on activity1 screen2. Changing folder on activity1 screen1 results in icons disappearing from activity1 screen2, but appearing on activity4 screen2. Selecting show desktop folder does not work on activity 1 and 4, but works on activity 2 and 3. Selecting Location however works on activity 1 and 4, but not on 2 and 3. But this is not true for all screens, but I haven't test all possible combinations. Maybe I should remove all activities and set everything from scratch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 --- Comment #4 from Gábor Katona --- I have removed all activities, even removed plasma-org.kde.plasma.desktop-appletsrc and plasmashellrc. The behavior is strange: Now I have only one activity. Screen1 can be set to show desktop folder (.Desktop) or .Desktop.1 folder. Nothing else works. Screen2 can be set to anything EXCEPT .Desktop.1 However, if I set Screen to .Desktop.1 (resulting in empty desktop) and now setting Screen1 to show desktop folder and immediately back to .Desktop.1, then Screen1 will be empty, and Screen2 will show .Desktop.1. If now I set Screen2 to show desktop folder and after this to .Desktop.1, the result is .Desktop.1 is shown on Screen1. Removing the external screens returns normal operation. Maybe it is a multi-screen issue. Maybe it is something really mixed within the corresponding setting. What should I remove besides the mentioned files? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 --- Comment #5 from Gábor Katona --- After further testing I have found, that I cannot set the same folder for different screens. Not even if one screen is the laptop screen. Moreover, if I rename the folder set, the desktop will still show the content of the folder and reflects any changes. This is true even if the laptop screen is the only one. The folder in the settings remain the old one. I do not know whether it is the usual behavior, but it is quite strange. It seems that some internal reference is stored instead of the folder name. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 --- Comment #6 from Gábor Katona --- The rename anomaly stay until restart of KDE. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 --- Comment #8 from Gábor Katona --- Created attachment 110447 --> https://bugs.kde.org/attachment.cgi?id=110447&action=edit plasma-org.kde.plasma.desktop-appletsrc Here is my current plasma-org.kde.plasma.desktop-appletsrc. At the moment I have .Desktop.1 to .Desktop.4 and these are set for activity1-activity4 screen1, and .Desktop.11 to .Desktop.41 linked to the previous set and configured for screen2. This works for now with one small issue. On activity1 screen2 one icon is missing after moving the same icon on screen1. X-files. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 --- Comment #9 from Gábor Katona --- After today's reboot there are no icons on activities except the original one. And nothing can be set, neither desktop folder neither any place -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389745] Folderview on desktop erratically does not show icons from custom desktop folder with multi-screen
https://bugs.kde.org/show_bug.cgi?id=389745 --- Comment #10 from Gábor Katona --- After login-logout 3 out of 4 activities returned to life. After next login-logout all activities are working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386109] truncated panel after disconnecting an external display
https://bugs.kde.org/show_bug.cgi?id=386109 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com --- Comment #1 from Gábor Katona --- Created attachment 109530 --> https://bugs.kde.org/attachment.cgi?id=109530&action=edit Screenshot of truncated panel I confirm this bug on Opensuse Tumbleweed, KDE Plasma 5.11.4, Frameworks 5.40.0, Qt 5.9.3. The only difference is that no unifying of outputs is needed. I use two external display with docking station and the notebook screen disabled. After disconnecting the external displays sometimes the bottom and right part of the panel is missing. This does not always happen. Issuing kquitapp5 plasmashell && kstart5 plasmashell restores panel. Maybe it is a multiscreen issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388250] New: Device notifier pops up in double instance after disconnecting external screens
https://bugs.kde.org/show_bug.cgi?id=388250 Bug ID: 388250 Summary: Device notifier pops up in double instance after disconnecting external screens Product: plasmashell Version: 5.11.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: kato...@gmail.com Target Milestone: 1.0 Created attachment 109531 --> https://bugs.kde.org/attachment.cgi?id=109531&action=edit Screenshot of double pop up of device notifier I am using my notebook with external screens (two external displays, notebook screen disabled) and also with the notebook screen alone. I have a full panel on both external screens, when connected. After disconnecting the external screens and connecting e.g. an usb drive the device notifier pops up at the correct place (lower right) but also in the top left corner (see attachment). It seems that the device notifier still thinks there are two panels available. My system is Opensuse Tumbleweed, KDE Plasma 5.11.4, Frameworks 5.40.0, Qt 5.9.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching
https://bugs.kde.org/show_bug.cgi?id=342186 --- Comment #30 from Gábor Katona --- Wow, thanks! It works like charm. But if it is so simple, why it is still broken? Nevertheless, now it works. Thank you once more. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380463] New: After switching to dual external monitor one of the screens are not refreshed
https://bugs.kde.org/show_bug.cgi?id=380463 Bug ID: 380463 Summary: After switching to dual external monitor one of the screens are not refreshed Product: plasmashell Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: kato...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 105844 --> https://bugs.kde.org/attachment.cgi?id=105844&action=edit Screen record of the problem I use my notebook either with its own screen, or with two external screens with the own display switched off. When I connect the two external monitors, the system changes to the correct setup (side by side screens), but one of the screens do not refresh, the windows are shown as they were on the notebook screen (both the notebook screen and the bad screen are FHD), but the screen is practically frozen. However not fully, since the mouse pointer is visible and moves, and it can also interact with screen elements and windows, but the screen is not refreshed at all. I can even grab a window and move it to the other screen, which results in a strange layout of having the live window on the good screen, while having the original window on the bad screen. I have tried to make a screen record with SimpleScreenRecorder. The recording is also strange, because it shows that the screen is somehow refreshed, but sometimes it flickers back to the frozen state. This strange behavior can be solved by either switching to a terminal screen and back, or by disabling the bad screen and re-enabling it. When everything is ok, the screen recording is fine, no flickers (thus it is not a software effect), so I attach the recording to illustrate the problem. This whole problem started a few weeks ago, but do not know exactly which KDE version is the starting point. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380463] After switching to dual external monitor one of the screens are not refreshed
https://bugs.kde.org/show_bug.cgi?id=380463 --- Comment #1 from Gábor Katona --- Maybe it is also related, that even after getting beck to work the bad screen, the Task managers only current screen filter does not work on this screen. It works perfectly on the other screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373075] Changing Resolution hides programs in task manager
https://bugs.kde.org/show_bug.cgi?id=373075 --- Comment #20 from Gábor Katona --- The problem is still present in 5.9.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375341] New: Screen lock freezes after removing external screens
https://bugs.kde.org/show_bug.cgi?id=375341 Bug ID: 375341 Summary: Screen lock freezes after removing external screens Product: plasmashell Version: 5.8.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: kato...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I use my laptop either with two external screens connected to a docking station while the laptop screen is disabled (lid is closed) or only on laptop screen. When I remove the computer from the docking (thus the external screens are disconnected) while the screen is locked and after this I open the lid, the screen is black, only the mouse pointer is visible (it can be moved) and the screen cannot be unlocked. The only way to unlock the screen is to go to a terminal screen and issue loginctl unlock-sessions After this the screen is back and everything works normal. This seems to be a major issue, since the user is practically locked out of the computer, and for most users the only solution is hard reset. This also happens when I suspend the laptop with the screens connected and resume it after removing it from the docking. In some cases I even cannot switch to the terminal screen. This bug appeared in 5.8.5. Maybe it is connected to bug 371734 and it's fix. I guessed it is a multiscreen issue rather than kscreenlocker. My system is Opensuse Tumbleweed, Plasma 5.8.5, Frameworks 5.29.0, Qt 5.7.1, kernel 4.9.3 64bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375343] New: Task manager only current screen filter is broken after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=375343 Bug ID: 375343 Summary: Task manager only current screen filter is broken after disconnecting external monitor Product: plasmashell Version: 5.8.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: kato...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I use my laptop either with two external screens connected to a docking station while the laptop screen is disabled (lid is closed) or only on laptop screen. I have panel on both screens (and of course when using only the laptop screen) with a task manager widget. The task managers are set to display apps only from current screen, desktop and activity. After I remove the computer from the docking (thus the external screens are disconnected) no apps are shows by the remaining task manager. However, if I disable the show apps from current screen filter, the apps are shown again. Enabling the filter hides them again. It seems, that the apps are somehow stuck on the disconnected screen, at least for task manager, because otherwise the are perfectly shown. This bug appeared in 5.8.5 as I remember. Maybe it is connected to bug 371734 and it's fix. Maybe it is a multi screen issue also. My system is Opensuse Tumbleweed, Plasma 5.8.5, Frameworks 5.29.0, Qt 5.7.1, kernel 4.9.3 64bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching
https://bugs.kde.org/show_bug.cgi?id=342186 --- Comment #28 from Gábor Katona --- Is there any hope it will be fixed in the near future? In KDE4 it was fine and I really miss it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375341] Screen lock freezes after removing external screens
https://bugs.kde.org/show_bug.cgi?id=375341 Gábor Katona changed: What|Removed |Added Version|5.8.5 |5.9.0 --- Comment #1 from Gábor Katona --- The problem is still here with Plasma 5.9.0. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 373910] kgpg crash when changing key trust
https://bugs.kde.org/show_bug.cgi?id=373910 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com --- Comment #3 from Gábor Katona --- Kgpg 16.12.2 also has this problem on openSUSE Tumbleweed (Qt: 5.7.1, frameworks: 5.30.0). The crash only occurs if setting Ultimate trust level. Any other level can be set. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376788] New: Attaching external screen while suspended results in kernel panic on resume
https://bugs.kde.org/show_bug.cgi?id=376788 Bug ID: 376788 Summary: Attaching external screen while suspended results in kernel panic on resume Product: plasmashell Version: 5.9.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: kato...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I use my Dell E7470 either with its own screen or with a port replicator having two screens attached to it (internal screen disabled). Before connecting to the port replicator the laptop is in sleep mode, put there using only the internal screen. After connecting and resuming the result is sometimes a kernel panic. It happens erratically, but it is present at least in the previous 2 months (but maybe even earlier). I do not see any info in systemd journal. Maybe with some guide I can give more info. The system is openSUSE Tumbleweed, currently running plasma 4.9.1, frameworks 5.30.0, kernel 4.9.9. But this happened with previous plasma versions also. This bug is related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589397 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 76380] Moving to trash shouldn't move across partitions
https://bugs.kde.org/show_bug.cgi?id=76380 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com --- Comment #53 from Gábor Katona --- Using Opensuse Tumbleweed with Plasma 5.8.4, Frameworks 5.29.0 the bug is still present. And quite annoying. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 76380] Moving to trash shouldn't move across partitions
https://bugs.kde.org/show_bug.cgi?id=76380 --- Comment #54 from Gábor Katona --- (In reply to andreluizromano from comment #32) > WORKAROUND (for NTFS-3G filesystem mount procedure): > > Use options UID=USERID, GID=USERGROUPID, FMASK=177, DMASK=077 (or use the > options UID=USERID, GID=USERGROUPID, UMASK=077) > How can I set this as default mount option with KDE device notifier for ALL devices? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching
https://bugs.kde.org/show_bug.cgi?id=342186 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com --- Comment #26 from Gábor Katona --- (In reply to Marco Parillo from comment #22) I also have this problem on Opensuse Tumbleweed running Plasma 5.8.4, Frameworks 5.28.0, Qt 5.7.0. The Meta+Tab for switching activity, and the Meta+Q for the activity manager DO work, but assigning a shortcut to the activities doesn't have effect. Moreover, I have the following finding maybe related to the hotkey problem. I had 3 activities, deleted them (because of not working shortcuts) and created again. After this I have 6 activities in the global shortcuts menu, 3 for the old, deleted ones and 3 for the new. There should be some information exchange problem between the activity manager and the shortcut management. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 306238] Thunderbird compose mail window opens on wrong activity
https://bugs.kde.org/show_bug.cgi?id=306238 Gábor Katona changed: What|Removed |Added CC||plasma-b...@kde.org Version|4.8.5 |5.8.4 Target Milestone|--- |1.0 Product|plasma4 |plasmashell Component|activities |Activity Switcher --- Comment #2 from Gábor Katona --- This bug is still present in KDE Plasma 5.8.4, Frameworks 5.28.0, using Opensuse Tumbleweed with Thunderbird 45.5.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362812] Desktop resets to regular desktop when using Folder View
https://bugs.kde.org/show_bug.cgi?id=362812 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com --- Comment #3 from Gábor Katona --- I also have this, or a very similar problem. Running Opensuse Tumbleweed with Plasma 5.8.4, Frameworks 5.28.0. The symptoms are the same, I have folder view set up for the desktop, and it resets itself back to desktop view. However I use different monitor setups and I suspect that, at least in my case, the reset is connected to switching between the different setups. I use a notebook, sometimes on its own, sometimes using a dock with 2 monitors connected (the notebook screen is switched off) and sometimes with a projector with the notebook screen on. I noticed, that changing the monitor settings, which happens automatically upon connection of the projector or docking he notebook, sometimes resets back the primary screen (!) to the default desktop view with the default wallpaper. But only the primary screen. Also when I try to set up folder view again, the icons are not in the arranged order, and moreover, in some cases I simply cannot change the layout to folder view. This latter only happens on activities that were created by me, never with the original activity. I have tried deleting plasma-org.kde.plasma.desktop-appletsrc and plasmashellrc, but the problem stays. I would suggest reassigning it to Desktop Containment and/or Multi-screen support. Alternatively I should file a new bug, it the others doesn't use different screen setups. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362812] Desktop resets to regular desktop when using Folder View
https://bugs.kde.org/show_bug.cgi?id=362812 --- Comment #4 from Gábor Katona --- Additionally plasmashell crashes occasionally when disconnecting monitors -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371734] Multiscreen lost configuration of the desktop
https://bugs.kde.org/show_bug.cgi?id=371734 Gábor Katona changed: What|Removed |Added CC||kato...@gmail.com --- Comment #16 from Gábor Katona --- I think my problem, commented to bug #362812 has the same origin. My comment from that bug: I also have this, or a very similar problem. Running Opensuse Tumbleweed with Plasma 5.8.4, Frameworks 5.28.0. The symptoms are the same, I have folder view set up for the desktop, and it resets itself back to desktop view. However I use different monitor setups and I suspect that, at least in my case, the reset is connected to switching between the different setups. I use a notebook, sometimes on its own, sometimes using a dock with 2 monitors connected (the notebook screen is switched off) and sometimes with a projector with the notebook screen on. I noticed, that changing the monitor settings, which happens automatically upon connection of the projector or docking he notebook, sometimes resets back the primary screen (!) to the default desktop view with the default wallpaper. But only the primary screen. Also when I try to set up folder view again, the icons are not in the arranged order, and moreover, in some cases I simply cannot change the layout to folder view. This latter only happens on activities that were created by me, never with the original activity. I have tried deleting plasma-org.kde.plasma.desktop-appletsrc and plasmashellrc, but the problem stays. If my problem seems different, I will file a new bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373569] New: Plasmashell crashes when changing activities after switching to multi screen setup
https://bugs.kde.org/show_bug.cgi?id=373569 Bug ID: 373569 Summary: Plasmashell crashes when changing activities after switching to multi screen setup Product: plasmashell Version: 5.8.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kato...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Connected the notebook to docking station with 2 screens. The desktops are set to folder view. After connection changing activity results in losing folder view on screen 0. Changing back to the original activity sometimes results in plasmashell crash. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbc1d7638c0 (LWP 4675))] Thread 7 (Thread 0x7fbb51305700 (LWP 4687)): #0 0x7fbc16e0068d in poll () from /lib64/libc.so.6 #1 0x7fbc11e9a876 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbc11e9a98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fbc1771f79b in QEventDispatcherGlib::processEvents (this=0x7fbb4c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fbc176c91ea in QEventLoop::exec (this=this@entry=0x7fbb51304cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7fbc174f78b3 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fbb5382fdf7 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #7 0x7fbc174fc558 in QThreadPrivate::start (arg=0x4b9a840) at thread/qthread_unix.cpp:344 #8 0x7fbc16602454 in start_thread () from /lib64/libpthread.so.0 #9 0x7fbc16e0939f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fbb64509700 (LWP 4683)): #0 0x7fbc11edfec4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fbc11e9a71d in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fbc11e9a98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fbc1771f79b in QEventDispatcherGlib::processEvents (this=0x7fbb5c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fbc176c91ea in QEventLoop::exec (this=this@entry=0x7fbb64508c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7fbc174f78b3 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fbc1b3b6646 in ?? () from /usr/lib64/libQt5Quick.so.5 #7 0x7fbc174fc558 in QThreadPrivate::start (arg=0x189c020) at thread/qthread_unix.cpp:344 #8 0x7fbc16602454 in start_thread () from /lib64/libpthread.so.0 #9 0x7fbc16e0939f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fbbf35a4700 (LWP 4682)): #0 0x7fbc1660810f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbc1ce3a834 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fbc1ce3a879 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7fbc16602454 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbc16e0939f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fbbf956d700 (LWP 4681)): #0 std::__atomic_base::compare_exchange_strong (__m2=, __m1=, __p2=, __p1=, this=) at /usr/include/c++/6/bits/atomic_base.h:752 #1 std::atomic::compare_exchange_strong (__m=, __p2=, __p1=, this=) at /usr/include/c++/6/atomic:475 #2 QAtomicOps::testAndSetAcquire (currentValue=, newValue=, expectedValue=, _q_value=...) at ../../src/corelib/arch/qatomic_cxx11.h:165 #3 QBasicAtomicPointer::testAndSetAcquire (currentValue=, newValue=, expectedValue=, this=) at ../../src/corelib/thread/qbasicatomic.h:259 #4 QBasicMutex::fastTryLock (current=, this=) at thread/qmutex.h:89 #5 QMutex::lock (this=this@entry=0xfeecb0) at thread/qmutex.cpp:225 #6 0x7fbc1771ef0f in QMutexLocker::QMutexLocker (m=0xfeecb0, this=) at ../../src/corelib/thread/qmutex.h:137 #7 QThreadData::canWaitLocked (this=0xfeec80) at ../../src/corelib/thread/qthread_p.h:253 #8 postEventSourcePrepare (s=0x7fbbec0012d0, timeout=0x7fbbf956cb14) at kernel/qeventdispatcher_glib.cpp:259 #9 0x7fbc11e99d79 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #10 0x7fbc11e9a79b in ?? () from /usr/lib64/libglib-2.0.so.0 #11 0x7fbc11e9a98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #12 0x7fbc1771f79b in QEventDispatcherGlib::processEvents (this=0x7fbbec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7fbc176c91ea in QEventLoop::exec (this=this@entry=0x7fbbf956cc
[plasmashell] [Bug 373569] Plasmashell crashes when changing activities after switching to multi screen setup
https://bugs.kde.org/show_bug.cgi?id=373569 --- Comment #1 from Gábor Katona --- Bug #362812 and bug #371734 are probably related to the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373700] New: Plasmashell crashes after resuming from dual screen setup to single screen
https://bugs.kde.org/show_bug.cgi?id=373700 Bug ID: 373700 Summary: Plasmashell crashes after resuming from dual screen setup to single screen Product: plasmashell Version: 5.8.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kato...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.13-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: The laptop was suspended using 2 external screens while the internal screen was disabled. Later it was resumed, but without external screens, only the laptop screen was active. Plasmashell crashed immediately after login. After the crash (or before crash, I do not know) the destop reset to the default one as described in comment 16 of bug #371734. I suspect that bug #371734, bug #373569, bug #369537 and maybe bug #362812 are somehow connected to this problem. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9cfa5b68c0 (LWP 3599))] Thread 7 (Thread 0x7f9c2eaea700 (LWP 3713)): #0 0x7f9ceed32ea9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f9ceececd85 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9ceeced79b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9ceeced98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f9cf457279b in QEventDispatcherGlib::processEvents (this=0x7f9c280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f9cf451c1ea in QEventLoop::exec (this=this@entry=0x7f9c2eae9cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f9cf434a8b3 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f9c31017df7 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #8 0x7f9cf434f558 in QThreadPrivate::start (arg=0x5ad7530) at thread/qthread_unix.cpp:344 #9 0x7f9cf3455454 in start_thread () from /lib64/libpthread.so.0 #10 0x7f9cf3c5c39f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f9c41339700 (LWP 3708)): #0 0x7f9ceed32ec4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f9ceeced204 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9ceeced814 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9ceeced98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f9cf457279b in QEventDispatcherGlib::processEvents (this=0x7f9c3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f9cf451c1ea in QEventLoop::exec (this=this@entry=0x7f9c41338c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f9cf434a8b3 in QThread::exec (this=this@entry=0x2caf1d0) at thread/qthread.cpp:507 #7 0x7f9cf8209646 in QQuickPixmapReader::run (this=0x2caf1d0) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/util/qquickpixmapcache.cpp:823 #8 0x7f9cf434f558 in QThreadPrivate::start (arg=0x2caf1d0) at thread/qthread_unix.cpp:344 #9 0x7f9cf3455454 in start_thread () from /lib64/libpthread.so.0 #10 0x7f9cf3c5c39f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f9cc700 (LWP 3707)): #0 0x7f9cf345b10f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9cf9c8d834 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f9cf9c8d879 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f9cf3455454 in start_thread () from /lib64/libpthread.so.0 #4 0x7f9cf3c5c39f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f9cd63a4700 (LWP 3706)): #0 0x7f9cf3c5368d in poll () from /lib64/libc.so.6 #1 0x7f9ceeced876 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9ceeced98c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9cf457279b in QEventDispatcherGlib::processEvents (this=0x7f9cc80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f9cf451c1ea in QEventLoop::exec (this=this@entry=0x7f9cd63a3ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f9cf434a8b3 in QThread::exec (this=this@entry=0x235ddf0) at thread/qthread.cpp:507 #6 0x7f9cf767ba75 in QQmlThreadPrivate::run (this=0x235ddf0) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/ftw/qqmlthread.cpp:147 #7 0x7f9cf434f558 in QThreadPrivate::start (arg=0x235ddf0) at thread/qthread_unix.cpp:344 #8 0x7f9cf3455454 in start_thread () from /lib64/libpthread.so.0 #9 0x0
[plasmashell] [Bug 373705] New: Allow different panel configuration for activities
https://bugs.kde.org/show_bug.cgi?id=373705 Bug ID: 373705 Summary: Allow different panel configuration for activities Product: plasmashell Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kato...@gmail.com Target Milestone: 1.0 Activities are perfect way for managing different workflows and customizing the environment for that. However it would be great to have the possibility of configuring different panel for different activities; e.g. the programs pinned to the panel, or the favorite programs on application menu can be quite different for workflows, which is not possible at the moment. -- You are receiving this mail because: You are watching all bug changes.
