[plasmashell] [Bug 483199] Plasmashell crashes in KKeySequenceRecorder::~KKeySequenceRecorder() when assigning a shortcut (that is already assigned) to sth like a panel
https://bugs.kde.org/show_bug.cgi?id=483199 Vorpal changed: What|Removed |Added CC||kdeb...@vorpal.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482828] Task Manager icons disappear/move to the left when mouse is moved over them
https://bugs.kde.org/show_bug.cgi?id=482828 --- Comment #6 from Vorpal --- (In reply to Vorpal from comment #5) > The issue seems to have stopped happening (I switched to Cinnamon for a > couple of days and switched back to run nvidia-report-bug.sh). Oh the ups > and downs of a rolling release distro like Arch Linux. By the way it doesn't > seem like I have a nvidia-report-bug.sh in PATH on my system? > > I'll keep an eye out and report it upstream to Nvidia if it happens again. > If someone else is still having the issue when using nvidia 550.54.14-4 > please make sure to report it to nvidia as suggested by Nate Graham in > comment 3. Oh it is nvidia-bug-report.sh, my bad. Word order matters. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482828] Task Manager icons disappear/move to the left when mouse is moved over them
https://bugs.kde.org/show_bug.cgi?id=482828 --- Comment #5 from Vorpal --- The issue seems to have stopped happening (I switched to Cinnamon for a couple of days and switched back to run nvidia-report-bug.sh). Oh the ups and downs of a rolling release distro like Arch Linux. By the way it doesn't seem like I have a nvidia-report-bug.sh in PATH on my system? I'll keep an eye out and report it upstream to Nvidia if it happens again. If someone else is still having the issue when using nvidia 550.54.14-4 please make sure to report it to nvidia as suggested by Nate Graham in comment 3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 --- Comment #3 from Vorpal --- Actually there is one difference, when my screen is black (but on, backlight still on) I don't see a cursor either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Vorpal changed: What|Removed |Added CC||kdeb...@vorpal.se --- Comment #2 from Vorpal --- This happens for me on my laptop too. X11 session (because nvidia). Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20L5CT01WW System Version: ThinkPad T480 NOTE: Switchable nvidia/intel graphics. NVIDIA GeForce MX150. I'm running in hybrid mode (which doesn't work on Wayland). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482828] New: Task bar/panel icons disappear when mouse is moved over them
https://bugs.kde.org/show_bug.cgi?id=482828 Bug ID: 482828 Summary: Task bar/panel icons disappear when mouse is moved over them Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kdeb...@vorpal.se Target Milestone: --- SUMMARY Icons disappear and appear in the right corner of the dock as you move the mouse over them. This makes using the taskbar largely unusable. Note: I coudn't find a "dock" or "taskbar" product/component to file this bug against, so I gussed kwin/general. Please move if incorrect. STEPS TO REPRODUCE 1. Boot my desktop (this doesn't happen on my laptop) and log into the new fancy KDE. Doesn't matter if it is wayland or X11, happens for both 2. Move mouse over icons in dock. Icons all move to the upper left corner of the dock OBSERVED RESULT Icons disappear and appear in the right corner of the dock as you move the mouse over them. The same also happens to icons in the "system tray" part on the right, except for the clock, the up arrow and KDE connect. Everything else gets erased. EXPECTED RESULT As on my laptop, where this doesn't happen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION * nVidia GeForce 1070, driver version 550.54.14 (the open source drivers don't support this card) * Kernel 6.7.8-arch1-1 * Multi-head setup, one 16:9 and one 16:10 monitor (1080p and 1200p respectively). Unplugging one monitor does not fix the issue however. * I have uploaded a video I recorded of OBS of the bug: https://youtu.be/aRW5JWQHBr8 -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 481485] New: [Feature request] Add support for rust demangling (using rustc-demangle C library probably)
https://bugs.kde.org/show_bug.cgi?id=481485 Bug ID: 481485 Summary: [Feature request] Add support for rust demangling (using rustc-demangle C library probably) Classification: Applications Product: Heaptrack Version: 1.5.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: m...@milianw.de Reporter: kdeb...@vorpal.se Target Milestone: --- SUMMARY Hi I couldn't find a separate location to file feature requests so I hope this it the right location. Currently when looking at Rust binaries I get some partially demangled names. Presumably it is close enough to C++ to get some demangling. Unfortunately that is probably the worst option, as I can't just copy paste the half-demangled name into a proper rust demangler (like https://github.com/luser/rustfilt). I would thus appreciate if you either didn't demangle rust symbols at all, or used https://github.com/rust-lang/rustc-demangle#usage-from-non-rust-languages to do it fully. I know that hotspot by KDAB (which seems very closely related to this GUI-wise) already has support for rust demangling, so maybe it wouldn't be too difficult to add here as well. STEPS TO REPRODUCE 1. Profile a rust binary 2. Open in heaptrack_gui 3. Be met with confusing partially demangled names OBSERVED RESULT Partially demangled names EXPECTED RESULT Preferably fully demangled (otherwise not demangled at all) SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473043] Embedded Konsole crash on command execution
https://bugs.kde.org/show_bug.cgi?id=473043 --- Comment #17 from Vorpal --- (In reply to tcanabrava from comment #12) > I can reproduce. I'll try to fix this tomorrow. > Vorpal: no one works to develop for konsole and we use our free time to it. > sometimes bugs happen, and we need to do the best we can. Indeed, I wasn't asking why it wasn't being fixed. Just why it wasn't marked confirmed. Seems to be about as much work as marking duplicates to mark it as confirmed after, say, 5 duplicates. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473043] Embedded Konsole crash on command execution
https://bugs.kde.org/show_bug.cgi?id=473043 --- Comment #11 from Vorpal --- (sorry, make that "almost a month", misread) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473043] Embedded Konsole crash on command execution
https://bugs.kde.org/show_bug.cgi?id=473043 --- Comment #10 from Vorpal --- Given the large number of duplicate reports it seems to affect a lot of users. And the bug has been open for more than a month? And is not yet marked as CONFIRMED. I'm confused here: Do you need any additional input from users or what is the holdup? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473795] After updating to 23.08.0 dolphin crashes on launch (Konsole::Screen::setReplMode)
https://bugs.kde.org/show_bug.cgi?id=473795 --- Comment #2 from Vorpal --- Downgrading to dolphin to 23.04.3 didn't fix it. I instead had to downgrade the konsole package. But launching konsole itself on the newer version works. So I'm not sure what is going on. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473795] After updating to 23.08.0 dolphin crashes on launch (Konsole::Screen::setReplMode)
https://bugs.kde.org/show_bug.cgi?id=473795 --- Comment #1 from Vorpal --- Arch Linux bug: https://bugs.archlinux.org/task/79485 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473795] New: After updating to 23.08.0 dolphin crashes on launch (Konsole::Screen::setReplMode)
https://bugs.kde.org/show_bug.cgi?id=473795 Bug ID: 473795 Summary: After updating to 23.08.0 dolphin crashes on launch (Konsole::Screen::setReplMode) Classification: Applications Product: dolphin Version: 23.08.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kdeb...@vorpal.se CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Using command line gdb to get this with debug symbols (drkonqi doesn't seem to be able to use debuginfod correctly?): (gdb) bt #0 QAction::setVisible(bool) (this=0x0, b=true) at kernel/qaction.cpp:1051 #1 0x7fffdc0d3144 in Konsole::Screen::setReplMode(int) (this=0x5615fe30, mode=1) at /usr/src/debug/konsole/konsole-23.08.0/src/Screen.cpp:2395 #2 0x7fffdc0ee095 in Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int) (this=, tokenSize=, terminator=7) at /usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:1071 #3 0x7fffdc0df290 in Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates, unsigned int) (this=this@entry=0x561e6f70, newState=newState@entry=Konsole::Vt102Emulation::Ground, cc=cc@entry=7) at /usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:434 #4 0x7fffdc0df61c in Konsole::Vt102Emulation::receiveChars(QVector const&) (this=0x561e6f70, chars=) at /usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:900 #5 0x7fffdc0b9bea in Konsole::Emulation::receiveData(char const*, int) (this=0x561e6f70, text=0x56383eb8 "^E\b \b\b \b cd /home/arvid\r\n clear\r\n\033[0m\033[49m\033[39m\033[27m\033[24m\r\033[K\r\n\033[1A\0337\033[0m\033[49m\033[39m\033]133;A\a\033[0m\033[49m\033[38;5;31m\033[1m\033[38;5;31m\033[38;5;39m~\033[0m\033[38;5;39m\033[49m\033[38;5;31m\033[0m\033[38;5;31m\033[49m\033[38;5;31m\033[0m\033[3"..., length=2613) at /usr/src/debug/konsole/konsole-23.08.0/src/Emulation.cpp:233 #6 0x75cd1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffcf60, r=, this=0x561ecbe0, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x561e9fe0, signal_index=17, argv=0x7fffcf60) at kernel/qobject.cpp:3925 #8 0x7fffdc0a793b in Konsole::Pty::receivedData(char const*, int) (this=, _t1=, _t2=) at /usr/src/debug/konsole/build/src/konsoleprivate_autogen/EWIEGA46WW/moc_Pty.cpp:154 #9 0x7fffdc0bf7c9 in Konsole::Pty::dataReceived() (this=0x561e9fe0) at /usr/src/debug/konsole/konsole-23.08.0/src/Pty.cpp:101 #10 0x75cd1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffd030, r=, this=0x561ecaa0, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate(QObject*, int, void**) (sender=0x561ea210, signal_index=3, argv=0x7fffd030) at kernel/qobject.cpp:3925 #12 0x7fffe406e0c7 in KPtyDevicePrivate::_k_canRead() (this=0x561dd0f0) at /usr/src/debug/kpty/kpty-5.109.0/src/kptydevice.cpp:291 #13 0x7fffe406e369 in KPtyDevice::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_c=, _a=0x7fffd1c0, _id=, _o=) at /usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:84 #14 KPtyDevice::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=0x7fffd1c0) at /usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:77 #15 0x75cd17f3 in doActivate(QObject*, int, void**) (sender=0x561ec330, signal_index=5, argv=0x7fffd1c0) at kernel/qobject.cpp:3937 #16 0x75cd2ea9 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (this=this@entry=0x561ec330, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:185 #17 0x75cd2f9b in QSocketNotifier::event(QEvent*) (this=0x561ec330, e=) at kernel/qsocketnotifier.h:115 #18 0x7697893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x561ec330, e=0x7fffd2d0) at kernel/qapplication.cpp:3640 #19 0x75c9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x561ec330, event=0x7fffd2d0) at kernel/qcoreapplication.cpp:1064 #20 0x75cea276 in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x557b5fc0) at kernel/qeventdispatcher_glib.cpp:107 #21 0x73d0fa31 in g_main_dispatch (context=0x7fffe8000ee0) at ../glib/glib/gmain.c:3460 #22 g_main_context_dispatch (context=0x7fffe8000ee0) at ../glib/glib/gmain.c:4200 #23 0x73d6ccc9 in g_main_context_iterate.isra.0 (context=context@entry=0x7fffe8000ee0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276 #24
[KScreen] [Bug 466516] Since Plasma 5.27, Plasma no longer remembers which display is "primary"
https://bugs.kde.org/show_bug.cgi?id=466516 Vorpal changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Vorpal --- Hm, the issue of the screen not being detected automatically appears to have fixed itself. Such is the life of rolling release distros, oh well. However, now "extend to right" and "extend to left" appears to have swapped meaning. Now it indicates which side the laptop monitor goes of the main screen! I don't know if it is useful any more, but here is the output you asked for: $ kscreen-doctor -o # Laptop only Output: 540 DP-0.2 disabled disconnected priority 0 Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 563 DP-0 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 564 DP-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 565 DP-2 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 566 HDMI-0 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 567 DP-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 601 eDP-1-1 enabled connected priority 1 Panel Modes: 541:2560x1440@60 547:1600x1200@60 549:1280x1024@60 555:1024x768@60 557:800x600@60 561:640x480@60 608:3840x2160@60! 609:3840x2160@60 610:3840x2160@60 611:3200x1800@60 612:3200x1800@60 613:2880x1620@60 614:2880x1620@60 615:2560x1600@60 616:2560x1600@60 617:2560x1440@60 618:2560x1440@60 619:2560x1440@60 620:2048x1536@60 621:1920x1440@60 622:1856x1392@60 623:1792x1344@60 624:2048x1152@60 625:2048x1152@60 626:2048x1152@60 627:2048x1152@60 628:1920x1200@60 629:1920x1200@60 630:1920x1080@60* 631:1920x1080@60 632:1920x1080@60 633:1920x1080@60 634:1680x1050@60 635:1680x1050@60 636:1400x1050@60 637:1600x900@60 638:1600x900@60 639:1600x900@60 640:1600x900@60 641:1400x900@60 642:1400x900@60 643:1280x960@60 644:1440x810@60 645:1440x810@60 646:1368x768@60 647:1368x768@60 648:1280x800@60 649:1280x800@60 650:1280x800@60 651:1280x800@60 652:1280x720@60 653:1280x720@60 654:1280x720@60 655:1280x720@60 656:1024x768@60 657:960x720@60 658:928x696@60 659:896x672@60 660:1024x576@60 661:1024x576@60 662:1024x576@60 663:1024x576@60 664:960x600@60 665:960x600@60 666:960x540@60 667:960x540@60 668:960x540@60 669:960x540@60 670:800x600@60 671:800x600@56 672:840x525@60 673:840x525@60 674:864x486@60 675:864x486@60 676:700x525@60 677:800x450@60 678:800x450@60 679:640x512@60 680:700x450@60 681:700x450@60 682:640x480@60 683:720x405@60 684:720x405@59 685:684x384@60 686:684x384@60 687:640x400@60 688:640x400@60 689:640x360@60 690:640x360@60 691:640x360@60 692:640x360@59 693:512x384@60 694:512x288@60 695:512x288@60 696:480x270@60 697:480x270@60 698:400x300@60 699:400x300@56 700:432x243@60 701:432x243@60 702:320x240@60 703:360x202@60 704:360x202@59 705:320x180@60 706:320x180@59 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 602 DP-1-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 603 HDMI-1-1 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 604 DP-1-2 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 605 HDMI-1-2 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 606 DP-1-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown $ kscreen-doctor -o # External monitor plugged in (DP into dock connected via thunderbolt) Output: 540 DP-0.2 enabled connected priority 1 DisplayPort Modes: 541:2560x1440@60*! 542:2048x1080@60 543:2048x1080@24 544:1920x1080@60 545:1920x1080@60 546:1920x1080@50 547:1600x1200@60 548:1280x1024@75 549:1280x1024@60 550:1280x720@60 551:1280x720@60 552:1280x720@50 553:1152x864@75 554:1024x768@75 555:1024x768@60 556:800x600@75 557:800x600@60 558:720x576@50 559:720x480@60 560:640x480@75 561:640x480@60 562:640x480@60 Geometry: 1920,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 563 DP-0 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Oversc
[KScreen] [Bug 466516] Since Plasma 5.27, Plasma no longer remembers which display is "primary"
https://bugs.kde.org/show_bug.cgi?id=466516 --- Comment #3 from Vorpal --- (In reply to Nate Graham from comment #2) > Can you paste the output of `kscreen-doctor -o` before plugging in the > external screen, and afterwards? > > Also, when the external screen is plugged in, can you run `kscreen-console > bug` and paste the contents of the "EDID" sections for each detected screen? > Thanks! I will do so next time I'm at work and using that dock. Auto detection seems to work fine when connecting directly to the built in HDMI (like I do at home), rather than through the dock. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466516] Since Plasma 5.27, Plasma no longer remembers which display is "primary"
https://bugs.kde.org/show_bug.cgi?id=466516 --- Comment #1 from Vorpal --- I forgot to mention, this is a ThinkPad P15 Gen1 with a Quadro RTX 3000 GPU and Intel i9-10885H CPU. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466516] New: Since Plasma 5.27, Plasma no longer remembers which display is "primary"
https://bugs.kde.org/show_bug.cgi?id=466516 Bug ID: 466516 Summary: Since Plasma 5.27, Plasma no longer remembers which display is "primary" Classification: Plasma Product: KScreen Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kdeb...@vorpal.se Target Milestone: --- SUMMARY After updating to KDE 5.27, Plasma no longer remembers which monitor is supposed to be the primary display when I connect an external monitor. Instead it is always the internal monitor that is set to primary. STEPS TO REPRODUCE 1. Connect external monitor (I'm using DisplayPort via the Thinkpad Thunderbolt Dock). 2. Press Fn+F7 to bring up OSD and select extend to right (this laptop never auto-enables external displays for some reason). 3. Observe that the setting of which display was primary has been forgotten since last time. OBSERVED RESULT Primary display forgotten even though I checked to save display properties "for any display arrangement". EXPECTED RESULT Like with Plasma 5.26, it should remember which display is primary since last time I used this setup. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Nvidia drivers used as external displays are connected directly to the nvidia card (not to the intel card). Thus I can only test this in nvidia or hybrid mode. And hybrid mode is super-laggy and unstable, so I'm not using that. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461068] kscreen_osd_ser coredumps when pressing Fn+F7 (monitor config key)
https://bugs.kde.org/show_bug.cgi?id=461068 Vorpal changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #2 from Vorpal --- (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports. > > Can you please attach one? Thanks! Hi! Did you even look in the attached gdb_session.log? I ran bt. What other sort of backtrace do you want? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461102] Thunderbolt settings side panel has invisible content for large window sizes
https://bugs.kde.org/show_bug.cgi?id=461102 --- Comment #1 from Vorpal --- Created attachment 153256 --> https://bugs.kde.org/attachment.cgi?id=153256=edit Results with small window size (works as expected) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461102] New: Thunderbolt settings side panel has invisible content for large window sizes
https://bugs.kde.org/show_bug.cgi?id=461102 Bug ID: 461102 Summary: Thunderbolt settings side panel has invisible content for large window sizes Classification: Applications Product: systemsettings Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_thunderbolt Assignee: dvra...@kde.org Reporter: kdeb...@vorpal.se Target Milestone: --- Created attachment 153255 --> https://bugs.kde.org/attachment.cgi?id=153255=edit Result on large monitor SUMMARY When resizing or maximising the Thunderbolt settings to be large, the details in the side panel become invisible. See attached screenshots comparing small and large. I have also uploaded a short video showing what happens when I resize it: https://www.youtube.com/watch?v=pd8xVbrNJ_Q STEPS TO REPRODUCE 1. Open Thunderbolt settings 2. Click on a paired device to open the side panel. 3. Notice that the text is cut off, how much depend on the size of the settings window, with more cut off the larger the window is. OBSERVED RESULT Can't see the text or the "Revoke Trust" button. EXPECTED RESULT Layout should be done such that all content is visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461068] New: kscreen_osd_ser coredumps when pressing Fn+F7 (monitor config key)
https://bugs.kde.org/show_bug.cgi?id=461068 Bug ID: 461068 Summary: kscreen_osd_ser coredumps when pressing Fn+F7 (monitor config key) Classification: Plasma Product: KScreen Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: OSD Assignee: kscreen-bugs-n...@kde.org Reporter: kdeb...@vorpal.se Target Milestone: --- Created attachment 153236 --> https://bugs.kde.org/attachment.cgi?id=153236=edit gdb_session.log SUMMARY plasma-kscreen-osd.service crashes when activating the monitor configuration key on a laptop. All functionality seems to still work, which seems to be because it crashes in the destructor. This is fully reproducible. A log of the coredumpctl session is attached. STEPS TO REPRODUCE 1. On a Lenovo Thinkpad P15 Gen1, press Fn+F7. This brings up a OSD display to change the external display config (mirror, extend left, ...). This appears to work correctly. 2. Notice how the systemd user service plasma-kscreen-osd.service is now crashed. OBSERVED RESULT A crashed systemd unit, plus a core dump in /var/lib/systemd/coredump/. EXPECTED RESULT No crash? I mean, that is what I usually expect at least! SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION The laptop has nvidia graphics and is running in nvidia mode (not intel or hybrid). I don't know if this makes a difference. I can't test that however, as the external monitors are connected directly to the nvidia GPU and thus won't work in intel mode. Additionally, hybrid mode is very unstable and crashy preventing testing that entirely. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 Vorpal changed: What|Removed |Added CC|kdeb...@vorpal.se | -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 456928] New: Unreadable text on buttons when using breeze dark and starting ksystemlog from KDE menu
https://bugs.kde.org/show_bug.cgi?id=456928 Bug ID: 456928 Summary: Unreadable text on buttons when using breeze dark and starting ksystemlog from KDE menu Product: KSystemLog Version: 22.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.ternis...@gmail.com Reporter: kdeb...@vorpal.se Target Milestone: --- Created attachment 150749 --> https://bugs.kde.org/attachment.cgi?id=150749=edit Screenshot showing broken and working instance (elevated privileges on left, non-elevated on right) SUMMARY When starting ksystemlog from the KDE menu (where it asks for password to run as root), the text on the toolbar buttons is unreadable. See left instance in screenshot. When starting ksystemlog from the command line (no elevated privileges) the text on the button is readable (see right instance in screenshot). STEPS TO REPRODUCE 1. Use breeze theme in dark variant in KDE. 2. Run ksystemlog from KDE menu 3. Authenticate to elevate privileges 4. Look at toolbars OBSERVED RESULT Black text on dark grey background. Unreadable. EXPECTED RESULT Readable text colours. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 Vorpal changed: What|Removed |Added Keywords|regression | --- Comment #15 from Vorpal --- (In reply to Vorpal from comment #14) > (In reply to Nate Graham from comment #13) > > Can you try again once you get the re-spun version of plasma-workspace? It > > had a regression in it that caused issues, and the fix for it may have fixed > > this issue too. > > Sure, I can try if it is available by tomorrow. Actually it just showed up in the mirror I use so I was able to test it. Updating plasma-workspace to 5.25.3.1-1 seems to fix this in that I don't see the unlock button and multi screen unlock works. Works with both the password and fingerprint. I have the following fragment in /etc/pam.d/kde: authsufficient pam_unix.so try_first_pass likeauth nullok -auth sufficient pam_fprintd.so max_tries=1 timeout=10 I assume this bug could still trigger for someone who uses a password less account and still has the unlock button though? Presumably that needs to be tested too. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455712] Unlock button even with password user
https://bugs.kde.org/show_bug.cgi?id=455712 --- Comment #21 from Vorpal --- (In reply to sid8tive from comment #20) > (arch) Updated to 5.25.3.1-1 (plasma-wayland-session, plasma-workspace) and > its fixed for me! Updating plasma-workspace to 5.25.3.1-1 seems to fix this in that I don't see the unlock button and multi screen unlock works. Works with both the password and fingerprint. I have the following fragment in /etc/pam.d/kde: authsufficient pam_unix.so try_first_pass likeauth nullok -auth sufficient pam_fprintd.so max_tries=1 timeout=10 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 Vorpal changed: What|Removed |Added Keywords|regression | --- Comment #14 from Vorpal --- (In reply to Nate Graham from comment #13) > Can you try again once you get the re-spun version of plasma-workspace? It > had a regression in it that caused issues, and the fix for it may have fixed > this issue too. Sure, I can try if it is available by tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455712] Unlock button even with password user
https://bugs.kde.org/show_bug.cgi?id=455712 --- Comment #19 from Vorpal --- (In reply to darcagn from comment #15) > (In reply to Vorpal from comment #12) > > (In reply to Nate Graham from comment #11) > > > > Same problem with 5.25.3, clicking unlock button does nothing. > > > That's a different issue; see Bug 456639. This bug report is about the > > > "Unlock" button appearing unnecessarily, not it being broken. > > > > It is kind of hard to tell these bugs apart. I seem to be having a > > combination of Bug 456210 and this or bug 456639. > > > > I see an unlock button after entering my password. Said button doesn't work > > unless I unplug the external monitor. Downgrading to any 5.25.x release does > > not fix it. Only going back to 5.24.x works. > > Do you see a password prompt on all of your displays? > In my situation, the lock screen appears on all monitors and the password > entry prompt appears only on monitors the cursor has moved onto. > In my case, I have 3 displays, and if I move the cursor on all 3 displays to > show a prompt on all 3 displays, the "unlock" button appears and when > clicked, I can get into my session. > If I _do not_ move the cursor around to all 3 displays first before entering > the password, the "unlock" button appears but does not function and I cannot > get into my session. I did not try this. I do believe I saw a password prompt on multiple displays and was not able to get in. I don't have time to test this further today though unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455712] Unlock button even with password user
https://bugs.kde.org/show_bug.cgi?id=455712 --- Comment #18 from Vorpal --- (In reply to Antonio Rojas from comment #14) > (In reply to Vorpal from comment #12) > > For anyone on Arch Linux running into these issues I suggest for now > > downgrading using: > > > > sudo pacman -U > > https://archive.archlinux.org/packages/k/kscreenlocker/kscreenlocker-5.24.90- > > 1-x86_64.pkg.tar.zst > > Please don't suggest doing partial upgrades on Arch, this is totally > unsupported and has a high chance of totally breaking your system. This is true. However: * being able to unlock the screen but a slightly no standard and unsupported setup vs * having a completely useless system where I can't use suspend in any meaningful way. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #11 from Vorpal --- I see this, in combination the spurious unlock button bugs (either bug 455712 or bug 456639, not sure which). I get the unlock button after entering my password, but the button does nothing unless I unplug the external monitor. Arch Linux. All kscreenlocker 5.25.x seem to be affected. Downgrading to 5.24.90 fixes both this issue and removes the spurious button for me. Or maybe it only hides this issue? Lenovo Thinkpad T480 with switchable graphics (intel + nvidia), though running in intel-only mode. External monitor uses displayport, connected via USB-C -> DP adapter. Arch Linux, as I said earlier. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455712] Unlock button even with password user
https://bugs.kde.org/show_bug.cgi?id=455712 --- Comment #12 from Vorpal --- (In reply to Nate Graham from comment #11) > > Same problem with 5.25.3, clicking unlock button does nothing. > That's a different issue; see Bug 456639. This bug report is about the > "Unlock" button appearing unnecessarily, not it being broken. It is kind of hard to tell these bugs apart. I seem to be having a combination of Bug 456210 and this or bug 456639. I see an unlock button after entering my password. Said button doesn't work unless I unplug the external monitor. Downgrading to any 5.25.x release does not fix it. Only going back to 5.24.x works. For anyone on Arch Linux running into these issues I suggest for now downgrading using: sudo pacman -U https://archive.archlinux.org/packages/k/kscreenlocker/kscreenlocker-5.24.90-1-x86_64.pkg.tar.zst -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 Vorpal changed: What|Removed |Added CC||kdeb...@vorpal.se -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 455712] Unlock button even with password user
https://bugs.kde.org/show_bug.cgi?id=455712 Vorpal changed: What|Removed |Added CC||kdeb...@vorpal.se --- Comment #9 from Vorpal --- This happens for me too. Arch Linux. What is worse is that the unlock button actually only works on one of my computer (desktop). On my laptop the button does nothing making it impossible to get back into the session without logging into a vt and using loginctl to unlock the session that way! The laptop with that issue is running hybrid graphics (but they are in intel-only mode). Happens with kscreenlocker 5.25.3-1 package as well as older 5.25.x versions too. Downgrading to kscreenlocker-5.24.90-1 fixes the issue. I'm using X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455842] Focus issues in PyCharm IDE when using kwin (works fine under Cinnamon)
https://bugs.kde.org/show_bug.cgi?id=455842 Vorpal changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #2 from Vorpal --- My bad. This seems to be an arch linux packaging issue. Upstream tar ball of PyCharm works just fine. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-attica] [Bug 453841] Discover crashes in Attica::Provider::Provider(Attica::Provider const&) when clicking on a font.
https://bugs.kde.org/show_bug.cgi?id=453841 --- Comment #1 from Vorpal --- This still happens with version 5.25.1 by the way. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455842] Focus issues in PyCharm IDE when using kwin (works fine under Cinnamon)
https://bugs.kde.org/show_bug.cgi?id=455842 --- Comment #1 from Vorpal --- Note: PyCharm is installed as a native Arch Linux package. I have not tried sandboxed versions (as that is pretty silly for IDEs anyway). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455842] New: Focus issues in PyCharm IDE when using kwin (works fine under Cinnamon)
https://bugs.kde.org/show_bug.cgi?id=455842 Bug ID: 455842 Summary: Focus issues in PyCharm IDE when using kwin (works fine under Cinnamon) Product: kwin Version: 5.25.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: kdeb...@vorpal.se Target Milestone: --- SUMMARY Certain popups in PyCharm Community Edition (and the Professional Edition too) do not recieve focus properly. I have recorded a short screen capture to demonstrate this: https://www.youtube.com/watch?v=cZikxxSN-Bs This popup receives proper focus in Cinnamon at least. I tried turning off "Focus stealing prevention" (setting it to None). That has no effect. STEPS TO REPRODUCE 1. Launch PyCharm Community Edition. Create a new project if needed. 2. Right click in project file tree and select New -> File. 3. Try to type in file name in popup. OBSERVED RESULT Text you type ends up in document behind popup EXPECTED RESULT Text should end up in popup as expected (and this is how it works under other tested DEs such as MATE and Cinnamon). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I'm using X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455141] With Systemd boot, log out followed by login no longer applies changes from /etc/groups
https://bugs.kde.org/show_bug.cgi?id=455141 --- Comment #7 from Vorpal --- (In reply to David Edmundson from comment #6) > I don't think there's much we can do our end. If so, you would expect that gnome has the same issue? I can certainly install it and test it. Also, shouldn't this at least be added to known caveats at https://invent.kde.org/plasma/plasma-workspace/-/wikis/Plasma-and-the-systemd-boot ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455141] [systemd] When enabling experimental systemdBoot, log out followed by login no longer applies changes from /etc/groups
https://bugs.kde.org/show_bug.cgi?id=455141 --- Comment #4 from Vorpal --- (In reply to Nate Graham from comment #1) > Can you upgrade to 5.25 and see if that fixes it for your log out+log in > scenario? I updated to 5.25.0. That did not fix the issue. Perhaps David Edmundson is correct. -- You are receiving this mail because: You are watching all bug changes.
