[plasmashell] [Bug 493386] New: clipboard history window leaks input to previously focused application
https://bugs.kde.org/show_bug.cgi?id=493386 Bug ID: 493386 Summary: clipboard history window leaks input to previously focused application Classification: Plasma Product: plasmashell Version: 6.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: descartav...@gmail.com Target Milestone: 1.0 SUMMARY Often, when using the clipboard history, invoked via keyboard shortcut, the inputs it receive (and processes) will also show up on the previous selected application (now behind the clipboard history window), cause major havoc. I've noticed this happen on QT applications (e.g. dolphin), GTK (e.g. firefox), X (e.g. xterm). STEPS TO REPRODUCE 1. while working on an application (e.g. vim, under Xterm, under plasmasession) 2. press the klipper shortcut for history (default meta+v) 3. press up/down to select the entry and Return to select it. OBSERVED RESULT the up/down/Return keys where passed to the previously focused application! EXPECTED RESULT Nothing to have changed on the application under the history window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 6650U with Radeon Graphics ADDITIONAL INFORMATION Happens on two system. One have default KDE upstream settings. Another have focus-follow-mouse (medium focus stealing prevention) It usually happens a couple times early in the session. And the stops. Haven't noticed it return after stopping. No clue on root cause. Tried all sorts of carefully windows focus control. Clicking the clipboard history before key presses, etc. Nothing changes. But I also cannot say what triggers it to stop happening. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457266] When using "Keep the selection and clipboard the same", selecting everything with Ctrl+A puts the entire selection in the clipboard
https://bugs.kde.org/show_bug.cgi?id=457266 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #10 from Gabriel Barros --- One thing i noticed: When editing fields under kde settings>network, when I focus some field, it will (always, infuriatingly) select the entire contents every single time, no matter if i just placed the cursor somewhere before focusing kate to copy some IP address, when i move back, the previous field is select-all'd... BUT, it never places the selection in the clipboard when selecting the text that way. just thought it is relevant here. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 492337] New: Tries to generate preview(?) when all preview options are disabled
https://bugs.kde.org/show_bug.cgi?id=492337 Bug ID: 492337 Summary: Tries to generate preview(?) when all preview options are disabled Classification: Applications Product: dolphin Version: 24.08.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: descartav...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin tries to parse .theme files when it shouldn't (maybe others filetypes too, but .theme ones are the only ones i get errors in the logs) STEPS TO REPRODUCE 1. disable all preview options 2. open a directory containing a .theme file OBSERVED RESULT my system logs will be full of errors: > dolphin[5842]: kf.config.core: KConfigIni: In file /home/me/somefile.theme, > line 27: Invalid escape sequence: «\W» around 30lines per file. EXPECTED RESULT Dolphin should not read random files. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 446628] Spectacle : Screenshot request failed: "The process is not authorized to take a screenshot"
https://bugs.kde.org/show_bug.cgi?id=446628 --- Comment #12 from Gabriel Barros --- commented on the wrong tab... but the point about firejail is valid. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 446628] Spectacle : Screenshot request failed: "The process is not authorized to take a screenshot"
https://bugs.kde.org/show_bug.cgi?id=446628 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #11 from Gabriel Barros --- (In reply to hasindu from comment #7) > File : ~/.local/share/applications/org.kde.spectacle.desktop > # converted by firecfg > [Desktop Entry] This is not the same issue discussed here (also, pls, try not to post long comments. attach file or remove the unnecessary info like the translations). In your case, Firejail (and bublewrap) will not work with wayland and screenshot... https://github.com/netblue30/firejail/issues/5127 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490332] crash when disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=490332
--- Comment #2 from Gabriel Barros ---
Most of the time i have only VLC window on the extended screen. here are the
system logs around the time i turned off the extended monitor:
```
Jul 15 22:16:45 host vlc[3041]: [7a7830001200] mkv demux error: Dummy
Element at unexpected position... corrupted file?
Jul 15 22:16:45 host vlc[3041]: [7a7830001200] mkv demux error: Dummy
element too large or misplaced at 7837824730... skipping to next upper element
Jul 15 22:17:52 host kernel: amdgpu :03:00.0: [drm] REG_WAIT timeout 1us *
10 tries - optc1_wait_for_state line:839
Jul 15 22:17:52 host kernel: amdgpu :03:00.0: [drm] REG_WAIT timeout 1us *
10 tries - optc1_wait_for_state line:839
Jul 15 22:17:52 host kernel: amdgpu :03:00.0: [drm] REG_WAIT timeout 1us *
10 tries - optc1_wait_for_state line:839
Jul 15 22:17:52 host plasmashell[1127]: KCrash: Application 'plasmashell'
crashing... crashRecursionCounter = 2
Jul 15 22:17:52 host systemd-coredump[6047]: Process 1127 (plasmashell) of user
1000 terminated abnormally with signal 11/SEGV, processing...
Jul 15 22:17:52 host systemd[1]: Created slice Slice
/system/drkonqi-coredump-processor.
Jul 15 22:17:52 host systemd[1]: Created slice Slice /system/systemd-coredump.
Jul 15 22:17:52 host systemd[1]: Started Process Core Dump (PID 6047/UID 0).
Jul 15 22:17:52 host systemd[1]: Started Pass systemd-coredump journal entries
to relevant user for potential DrKonqi handling.
Jul 15 22:17:53 host org_kde_powerdevil[1164]: Sleep event.
connector=card1-HDMI-A-1, dref not set
Jul 15 22:17:53 host org_kde_powerdevil[1164]: Delaying 6 seconds to avoid a
false disconnect/connect sequence...
Jul 15 22:17:54 host systemd-coredump[6048]: [🡕] Process 1127 (plasmashell) of
user 1000 dumped core.
Jul 15 22:17:54 host systemd[1]: systemd-coredump@0-6047-0.service: Deactivated
successfully.
Jul 15 22:17:54 host systemd[892]: plasma-plasmashell.service: Main process
exited, code=dumped, status=11/SEGV
Jul 15 22:17:54 host systemd[892]: plasma-plasmashell.service: Failed with
result 'core-dump'.
Jul 15 22:17:55 host drkonqi-coredump-processor[6049]: "/usr/bin/plasmashell"
1127
"/var/lib/systemd/coredump/core.plasmashell.1000.283ea22436244a888946b7f65a9ba1fb.1127.172109267200.zst"
Jul 15 22:17:55 host systemd[892]: Started Launch DrKonqi for a
systemd-coredump crash (PID 6049/UID 0).
Jul 15 22:17:55 host systemd[1]: drkonqi-coredump-processor@0-6047-0.service:
Deactivated successfully.
Jul 15 22:17:55 host systemd[892]: plasma-plasmashell.service: Scheduled
restart job, restart counter is at 1.
Jul 15 22:17:55 host systemd[892]: Starting KDE Plasma Workspace...
...
««i've been seeing this C locale errors.. my system should be all UTF8»»
Jul 15 22:17:55 host drkonqi[6084]: Detected locale "C" with character encoding
"ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has
switched to "C.UTF-8" instead.
If this causes problems, reconfigure your
locale. See the locale(1) manual
for more information.
...
Jul 15 22:17:55 host plasmashell[6083]:
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:195:25:
QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding
loop detected for property "minimumWidth"
...
Jul 15 22:17:55 host plasmashell[6083]: Toolbox not loading, toolbox package is
either invalid or disabled.
Jul 15 22:17:55 host systemd[1]: Started Hostname Service.
...
Jul 15 22:17:57 host drkonqi-coredump-launcher[6268]: boot_time =
datetime.utcfromtimestamp(psutil.boot_time()).strftime('%Y-%m-%dT%H:%M:%S')
Jul 15 22:17:57 host systemd[1]: Starting Time & Date Service...
Jul 15 22:17:57 host systemd[1]: Started Time & Date Service.
Jul 15 22:17:57 host plasmashell[6083]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.keyboardindicator/contents/ui/main.qml:61:13:
Unable to assign [undefined] to bool
Jul 15 22:17:57 host drkonqi-coredump-launcher[6268]:
/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py:532: DeprecationWarning:
datetime.datetime.utcnow() is deprecated and scheduled for removal in a future
version. Use timezone-aware objects to represent datetimes in UTC:
datetime.datetime.now(datetime.UTC).
...
Jul 15 22:17:57 host drkonqi-coredump-launcher[6268]: 'timestamp':
datetime.utcnow().isoformat(),
Jul 15 22:18:00 host org_kde_powerdevil[1164]: DRM connectors with newly
disconnected displays: card1-HDMI-A-1
Jul 15 22:18:00 host org_kde_powerdevil[1164]: Removing connected display with
bus Display_Path[/dev/i2c-4], drm connector card1-HDMI-A-1
Jul 15 22:18:02 host org_kde_powerdevil[1164]: Emitting
DDCA_Display_Status_Event( 8064.216: DDCA_EVENT_DPMS_ASLEEP, card1-HDMI-A-1,
dref: Display_Ref[NULL], io_path
[plasmashell] [Bug 490332] crash when disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=490332 --- Comment #1 from Gabriel Barros --- Created attachment 171696 --> https://bugs.kde.org/attachment.cgi?id=171696&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490332] New: crash when disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=490332 Bug ID: 490332 Summary: crash when disconnecting external monitor Classification: Plasma Product: plasmashell Version: 6.1.2 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: descartav...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.1.2) Qt Version: 6.7.2 Frameworks Version: 6.4.0 Operating System: Linux 6.9.9-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.1.2 [CoredumpBackend] -- Information about the crash: Adding external monitor after system is running (laptop with external HDMI port via APU) As soon as external monitor is turned off, or cable is removed, this crash occurs. Have been happening for a while (~4 months on rolling update distro which tracks close to upstream) The crash can be reproduced every time. -- Backtrace (Reduced): #5 QtWaylandClient::QWaylandWindow::waylandScreen (this=0x5c95df680f70) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:956 #6 QtWaylandClient::QWaylandWindow::devicePixelRatio (this=0x5c95df680f70) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:1521 #7 0x7c07d5406f0c in QtWaylandClient::QWaylandEglWindow::updateSurface (this=0x5c95df680f70, create=true) at /usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:70 #8 0x7c07d5407905 in QtWaylandClient::QWaylandGLContext::makeCurrent (this=this@entry=0x7c06a852b260, surface=) at /usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:318 #9 0x7c07dc0adc28 in QOpenGLContext::makeCurrent (this=0x7c06a8697ad0, surface=0x5c95df8d6700) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:664 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489638] Plasma crashed in QWindowPrivate::connectToScreen() when trying to open Klipper paste menu with keyboard shortcut Meta+V
https://bugs.kde.org/show_bug.cgi?id=489638 --- Comment #11 from Gabriel Barros --- (In reply to thePanz from comment #9) > Might be related to: https://bugs.kde.org/show_bug.cgi?id=489259 ? Do not think so. I can hold Meta+V and the window keeps flashing forever. I cannot make it crash this way alone. I also never saw the log-off like Eduard (and from other reporters also not seeing it, I think Eduard might be tying their xsession to kwin somehow so the session is lost when it restart? is that even possible?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489638] Plasma crashed in QWindowPrivate::connectToScreen() when trying to open Klipper paste menu with keyboard shortcut Meta+V
https://bugs.kde.org/show_bug.cgi?id=489638 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #10 from Gabriel Barros --- Happens from time to time. Usually after copying a URL from firefox addressbar, but I cannot reproduce. It only happens after i've been copying and pasting for a while. I think sleeping and restoring have something to do with it, but again, cannot reproduce. I do use a external monitor from time to time, but I do not think that is related as I happens when i haven't touched the hdmi cable for days. I have never saw drKonqui noticing it! kwin just restart. Operating System: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland $ pacman -Ss plasma | g installed 3:extra/bluedevil 1:6.1.2-1 (plasma) [installed] 5:extra/breeze 6.1.2-1 (plasma) [installed] 7:extra/breeze-gtk 6.1.2-1 (plasma) [installed] 13:extra/discover 6.1.2-1 (plasma) [installed] 15:extra/drkonqi 6.1.2-1 (plasma) [installed] 19:extra/kaccounts-integration 24.05.2-1 [installed] 21:extra/kactivitymanagerd 6.1.2-1 (plasma) [installed] 23:extra/kclock 24.05.2-1 (kde-applications kde-utilities) [installed] 25:extra/kde-cli-tools 6.1.2-1 (plasma) [installed] 27:extra/kde-gtk-config 6.1.2-1 (plasma) [installed] 29:extra/kdecoration 6.1.2-1 (plasma) [installed] 31:extra/kdeplasma-addons 6.1.2-1 (plasma) [installed] 33:extra/keysmith 24.05.2-1 (kde-applications kde-utilities) [installed] 35:extra/kgamma 6.1.2-1 (plasma) [installed] 37:extra/kglobalacceld 6.1.2-1 (plasma) [installed] 39:extra/kinfocenter 6.1.2-1 (plasma) [installed] 41:extra/kmenuedit 6.1.2-1 (plasma) [installed] 43:extra/kpipewire 6.1.2-1 (plasma) [installed] 45:extra/krdp 6.1.2-1 (plasma) [installed] 47:extra/krecorder 24.05.2-1 (kde-applications kde-utilities) [installed] 49:extra/kscreen 6.1.2-1 (plasma) [installed] 51:extra/kscreenlocker 6.1.2-1 (plasma) [installed] 53:extra/ksshaskpass 6.1.2-1 (plasma) [installed] 55:extra/ksystemstats 6.1.2-1 (plasma) [installed] 59:extra/kwallet-pam 6.1.2-1 (plasma) [installed] 61:extra/kwayland 6.1.2-1 (plasma) [installed] 63:extra/kweather 24.05.2-1 (kde-applications kde-utilities) [installed] 65:extra/kwin 6.1.2-1 (plasma) [installed] 67:extra/kwrited 6.1.2-1 (plasma) [installed] 69:extra/layer-shell-qt 6.1.2-1 (plasma) [installed] 71:extra/libkscreen 6.1.2-1 (plasma) [installed] 73:extra/libksysguard 6.1.2-1 (plasma) [installed] 75:extra/libplasma 6.1.2-1 (plasma) [installed] 79:extra/milou 6.1.2-1 (plasma) [installed] 81:extra/ocean-sound-theme 6.1.2-1 (plasma) [installed] 83:extra/oxygen 6.1.2-1 (plasma) [installed] 85:extra/oxygen-sounds 6.1.2-1 (plasma) [installed] 87:extra/plasma-activities 6.1.2-1 (plasma) [installed] 89:extra/plasma-activities-stats 6.1.2-1 (plasma) [installed] 93:extra/plasma-browser-integration 6.1.2-1 (plasma) [installed] 95:extra/plasma-desktop 6.1.2-1 (plasma) [installed] 97:extra/plasma-disks 6.1.2-1 (plasma) [installed] 99:extra/plasma-firewall 6.1.2-1 (plasma) [installed] 103:extra/plasma-integration 6.1.2-1 (plasma) [installed] 105:extra/plasma-meta 6.1-1 [installed] 107:extra/plasma-nm 6.1.2-1 (plasma) [installed] 109:extra/plasma-pa 6.1.2-1 (plasma) [installed] 115:extra/plasma-systemmonitor 6.1.2-1 (plasma) [installed] 117:extra/plasma-thunderbolt 6.1.2-1 (plasma) [installed] 119:extra/plasma-vault 6.1.2-1 (plasma) [installed] 123:extra/plasma-welcome 6.1.2-1 (plasma) [installed] 125:extra/plasma-workspace 6.1.2-1 (plasma) [installed] 127:extra/plasma-workspace-wallpapers 6.1.2-1 (plasma) [installed] 131:extra/plasma5support 6.1.2-1 (plasma) [installed] 137:extra/polkit-kde-agent 6.1.2-1 (plasma) [installed] 139:extra/powerdevil 6.1.2-1 (plasma) [installed] 141:extra/print-manager 1:6.1.2-1 (plasma) [installed] 145:extra/qqc2-breeze-style 6.1.2-1 (plasma) [installed] 147:extra/sddm-kcm 6.1.2-1 (plasma) [installed] 149:extra/systemsettings 6.1.2-1 (plasma) [installed] 155:extra/xdg-desktop-portal-kde 6.1.2-1 (plasma) [installed] -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 435603] Cannot connect to WiFi after restart, if VPN (wireguard) tries to connect simultaneously
https://bugs.kde.org/show_bug.cgi?id=435603 Gabriel Barros changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Platform|Manjaro |unspecified Version|5.21.3 |6.1.1 CC||descartav...@gmail.com --- Comment #7 from Gabriel Barros --- Confirming this still happens on 6.1.1 STEPS 1. create one wireguard connection 2. bring that connection up to confirm it is working fine 3. add a wifi|wired connection, mark "General Configuration > Automatically connect to VPN" and select connection from step 1. 4. bring wifi|wired connection up. WHAT HAPPENS notification saying both connections failed MORE INFO log for NetworkManager shows policy: secondary connection 'my_wg_connection (uid...)' auto-activation failed: The connection is not a VPN. libnm 1.48.2-1 networkmanager 1.48.2-1 networkmanager-qt 6.3.0-1 plasma-nm 6.1.1-1 Operating System: Arch Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 489739] Do not filter out wireguard vpn when they are valid.
https://bugs.kde.org/show_bug.cgi?id=489739 --- Comment #1 from Gabriel Barros --- > WORKAROUND > use the settings app or nmcli. correction: nmcli only. `nmcli connection up my_wg_connection` (before using the applet to start wifi|wired connection) Ooops. I've been using the nmcli, just tested the settings app, and there's no way to connect from there, as I wrongly assumed. It just list all connections and right-clicking them will only display "- Delete" or "Disconnect" (if appropriate). There's no "connect" option. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 489739] New: Do not filter out wireguard vpn when they are valid.
https://bugs.kde.org/show_bug.cgi?id=489739 Bug ID: 489739 Summary: Do not filter out wireguard vpn when they are valid. Classification: Plasma Product: plasma-nm Version: 6.1.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: descartav...@gmail.com Target Milestone: --- SUMMARY Before connecting to wired|wifi all the wireguard endpoints are hidden on the applet. It is actually recommended to bring wireguard interfaces up before the real interface. STEPS TO REPRODUCE 1. click applet while disconnected OBSERVED RESULT no wireguard connection are listed. EXPECTED RESULT See physical and wireguard connections. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION libnm 1.48.2-1 plasma-nm 6.1.1-1 networkmanager-qt 6.3.0-1 networkmanager 1.48.2-1 WORKAROUND use the settings app or nmcli. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 419002] Feature request: Wireguard informations
https://bugs.kde.org/show_bug.cgi?id=419002 Gabriel Barros changed: What|Removed |Added Resolution|--- |FIXED CC||descartav...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Gabriel Barros --- not sure which version is plasma on debian stable, but 6.1 already provides that. It shows a padlock on top of the connection icon (wired/wifi). And the more info expanded box will show wireguard device and IP(4/6) address. regarding notification, it already generates a notification for all interfaces, wireguard or otherwise, changing state. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488450] Plasma sometimes crashes in Plasma::Theme::~Theme() after interacting with panel contents
https://bugs.kde.org/show_bug.cgi?id=488450 --- Comment #5 from Gabriel Barros --- It was always default plasma themes, i believe only Fonts were ever changed from the default install (as provided by the arch packages) But, since 6.1 these went away. I guess it's "fixed"? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488450] panel crash if interacted with on long runtimes.
https://bugs.kde.org/show_bug.cgi?id=488450 --- Comment #1 from Gabriel Barros --- Created attachment 170467 --> https://bugs.kde.org/attachment.cgi?id=170467&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488450] New: panel crash if interacted with on long runtimes.
https://bugs.kde.org/show_bug.cgi?id=488450 Bug ID: 488450 Summary: panel crash if interacted with on long runtimes. Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: descartav...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.0.5) Qt Version: 6.7.1 Frameworks Version: 6.3.0 Operating System: Linux 6.9.3-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.0.5 [CoredumpBackend] -- Information about the crash: I did not notice if widgets like "system monitor" stop updating, but sometimes the panel will crash as soon as I interact with it after long runtimes. usually this happens when the system is left online overnight. Then mousing over the panel is already enough to cause this crash. The crash does not seem to be reproducible. -- Backtrace (Reduced): #5 std::__atomic_base::fetch_sub (this=0xdff0001c40, __i=1, __m=std::memory_order::acq_rel, this=, __i=, __m=) at /usr/include/c++/14.1.1/bits/atomic_base.h:639 #6 QAtomicOps::deref (_q_value=, _q_value=) at /usr/include/qt6/QtCore/qatomic_cxx11.h:266 [...] #8 Plasma::Theme::~Theme (this=this@entry=0x641464d550d8, this=) at /usr/src/debug/libplasma/libplasma-6.0.5/src/plasma/theme.cpp:85 #9 0x7adff5025d25 in PlasmaTheme::~PlasmaTheme (this=0x641464d550c0, this=) at /usr/src/debug/libplasma/libplasma-6.0.5/src/declarativeimports/kirigamiplasmastyle/plasmatheme.cpp:58 #10 PlasmaTheme::~PlasmaTheme (this=0x641464d550c0, this=) at /usr/src/debug/libplasma/libplasma-6.0.5/src/declarativeimports/kirigamiplasmastyle/plasmatheme.cpp:58 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421018] Window size for barcode (QR code) is too small, so the bar code is hidden
https://bugs.kde.org/show_bug.cgi?id=421018 --- Comment #4 from Gabriel Barros --- the fix is probably changing one `height` to `implicitHeight` or something, but I am not smart enough to navigate plasma source. Failed to even find mentions of the barcode feature. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421018] Window size for barcode (QR code) is too small, so the bar code is hidden
https://bugs.kde.org/show_bug.cgi?id=421018 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #3 from Gabriel Barros --- I think on plasma 6 this was made un-workaroundable. This feature is now integrated in plasmashell own "mobile barcode" function (which i can only seem to reach via the shortcut "show barcode" under plasmashell, it is impossible to create a window rule since then all other applets (e.g. wifi panel when you click the wifi icon in notification area) will also inherit that size/position from the rule. The barcode window class is "plasmashell org.kde.plasmashell" -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #65 from Gabriel Barros --- (In reply to Gabriel Barros from comment #63) > maybe a regression, but now happening on X11 with 6.0.4 > > Was all good under wayland, and ironically, under X11 on 6.0.2! > > Operating System: Arch Linux > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Kernel Version: 6.8.7-arch1-2 (64-bit) > Graphics Processor: AMD Radeon Graphics more details: backlight do turn off when screen locks. moving the mouse turn it on but only show mouse cursor. pressing ESC moves back to screen off. pressing ESC again turns backlight with only mouse cursor again. Sometimes moving to another tty and back shows the image, sometimes it does not. (it seems that changing tty first thing and back, works. but if you cycle ESC then it won't work. but reproduction is not 100%) unlocking by typing password blind or using fingerprint touch do resume image fine on unlocked desktop. regarding the previous comment about > Ironically, this behavior would occur specifically when the DPMS > action (a.k.a. "When locked, turn screen off") was disabled. systems on 6.0.4 do not have this option as they have the new Energy Saving screen design. Maybe those upgraded systems have left over values somewhere? All my 6.0.4 systems on X11 do it immediately without animation! on wayland they respect the timer and show fadeout animation, even if the timer is zero (then it immediately shows the lockscreen and fade it) On both type of systems the setting shows on the UI as "When locked, turn off screen in: after 60 sec" -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #63 from Gabriel Barros --- maybe a regression, but now happening on X11 with 6.0.4 Was all good under wayland, and ironically, under X11 on 6.0.2! Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-2 (64-bit) Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486340] Failure to show firewalld status
https://bugs.kde.org/show_bug.cgi?id=486340 --- Comment #1 from Gabriel Barros --- $ systemsettings Using fontconfig file: "/home/user/.config/fontconfig/fonts.conf" (clicking connections) qrc:/qt/qml/org/kde/kcmutils/SimpleKCM.qml:94: ReferenceError: footerParent is not defined qrc:/qt/qml/org/kde/systemsettings/CategoryItem.qml:33:13: Unable to assign IconPropertiesGroup_QMLTYPE_28 to IconPropertiesGroup_QMLTYPE_28 qrc:/qt/qml/org/kde/systemsettings/CategoryItem.qml:33:13: Unable to assign IconPropertiesGroup_QMLTYPE_28 to IconPropertiesGroup_QMLTYPE_28 qrc:/qt/qml/org/kde/systemsettings/CategoryItem.qml:33:13: Unable to assign IconPropertiesGroup_QMLTYPE_28 to IconPropertiesGroup_QMLTYPE_28 qrc:/qt/qml/org/kde/systemsettings/CategoryItem.qml:33:13: Unable to assign IconPropertiesGroup_QMLTYPE_28 to IconPropertiesGroup_QMLTYPE_28 qml: Page SubCategoryPage_QMLTYPE_111(0x618902039f00) is already in the PageRow qml: Pushed pages do not conform to the rules. Please check the documentation. qml: push (file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:223) onActiveSubCategoryRowChanged (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:175) expression for onClicked (qrc:/qt/qml/org/kde/systemsettings/CategoriesPage.qml:192) kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" (clicking firewall) qrc:/qt/qml/org/kde/kcmutils/SimpleKCM.qml:48: TypeError: Cannot read property 'name' of null ufw.client: Ufw is loaded? false firewalld.client: Firewalld is loaded? 0 qml: services available: [] qrc:/kcm/kcm_firewall/main.qml:29:5: QML OverlaySheet: Binding loop detected for property "implicitHeight" firewalld.job: firewalld direct: "getAllRules" QList() firewalld.job: firewalld zone interface: "getServices" QList(QVariant(QString, "")) qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qrc:/kcm/kcm_firewall/main.qml:29:5: QML OverlaySheet: Binding loop detected for property "y" qrc:/kcm/kcm_firewall/main.qml:29:5: QML OverlaySheet: Binding loop detected for property "implicitHeight" qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qml: Page SubCategoryPage_QMLTYPE_111(0x618902039f00) is already in the PageRow qml: Pushed pages do not conform to the rules. Please check the documentation. qml: push (file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:223) onActiveSubCategoryRowChanged (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:175) expression for onClicked (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:197) qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString firewalld.job: job error message: "Not Authorized(polkit): org.fedoraproject.FirewallD1.config.info" firewalld.client: Query rules job error: 100 "Not Authorized(polkit): org.fedoraproject.FirewallD1.config.info" (opening about box) qrc:/kcm/kcm_firewall/main.qml:468:9: QML About: Binding loop detected for property "implicitHeight" qrc:/kcm/kcm_firewall/main.qml:468:9: QML About: Binding loop detected for property "implicitHeight" a few seconds running: $ top PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 24658 user 20 0 3009360 264068 170964 R 99.7 0.8 10:42.78 systemsettings (not sure if better to open another ticket about this last bit? or might be related?), leaving the ksettings open on the firewall screen (showing "disabled". no action was taken). CPU was stuck at 99% usage by the process. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 486294] Better PAM recommendations to distributions (no nologin).
https://bugs.kde.org/show_bug.cgi?id=486294 --- Comment #2 from Gabriel Barros --- Last comment was typed in the wrong tab. apologies. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 486294] Better PAM recommendations to distributions (no nologin).
https://bugs.kde.org/show_bug.cgi?id=486294 --- Comment #1 from Gabriel Barros --- further (not sure if better to open another ticket?), leaving the ksettings open on the firewall screen (showing "disabled". no action was taken). CPU was stuck at 99% usage by the process. $ systemsettings Using fontconfig file: "/home/user/.config/fontconfig/fonts.conf" (clicking connections) qrc:/qt/qml/org/kde/kcmutils/SimpleKCM.qml:94: ReferenceError: footerParent is not defined qrc:/qt/qml/org/kde/systemsettings/CategoryItem.qml:33:13: Unable to assign IconPropertiesGroup_QMLTYPE_28 to IconPropertiesGroup_QMLTYPE_28 qrc:/qt/qml/org/kde/systemsettings/CategoryItem.qml:33:13: Unable to assign IconPropertiesGroup_QMLTYPE_28 to IconPropertiesGroup_QMLTYPE_28 qrc:/qt/qml/org/kde/systemsettings/CategoryItem.qml:33:13: Unable to assign IconPropertiesGroup_QMLTYPE_28 to IconPropertiesGroup_QMLTYPE_28 qrc:/qt/qml/org/kde/systemsettings/CategoryItem.qml:33:13: Unable to assign IconPropertiesGroup_QMLTYPE_28 to IconPropertiesGroup_QMLTYPE_28 qml: Page SubCategoryPage_QMLTYPE_111(0x618902039f00) is already in the PageRow qml: Pushed pages do not conform to the rules. Please check the documentation. qml: push (file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:223) onActiveSubCategoryRowChanged (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:175) expression for onClicked (qrc:/qt/qml/org/kde/systemsettings/CategoriesPage.qml:192) kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" (clicking firewall) qrc:/qt/qml/org/kde/kcmutils/SimpleKCM.qml:48: TypeError: Cannot read property 'name' of null ufw.client: Ufw is loaded? false firewalld.client: Firewalld is loaded? 0 qml: services available: [] qrc:/kcm/kcm_firewall/main.qml:29:5: QML OverlaySheet: Binding loop detected for property "implicitHeight" firewalld.job: firewalld direct: "getAllRules" QList() firewalld.job: firewalld zone interface: "getServices" QList(QVariant(QString, "")) qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qrc:/kcm/kcm_firewall/main.qml:29:5: QML OverlaySheet: Binding loop detected for property "y" qrc:/kcm/kcm_firewall/main.qml:29:5: QML OverlaySheet: Binding loop detected for property "implicitHeight" qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString qml: Page SubCategoryPage_QMLTYPE_111(0x618902039f00) is already in the PageRow qml: Pushed pages do not conform to the rules. Please check the documentation. qml: push (file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:223) onActiveSubCategoryRowChanged (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:175) expression for onClicked (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:197) qrc:/qt/qml/org/kde/desktop/HorizontalHeaderView.qml:38:9: Unable to assign [undefined] to QString firewalld.job: job error message: "Not Authorized(polkit): org.fedoraproject.FirewallD1.config.info" firewalld.client: Query rules job error: 100 "Not Authorized(polkit): org.fedoraproject.FirewallD1.config.info" (opening about box) qrc:/kcm/kcm_firewall/main.qml:468:9: QML About: Binding loop detected for property "implicitHeight" qrc:/kcm/kcm_firewall/main.qml:468:9: QML About: Binding loop detected for property "implicitHeight" a few seconds running: $ top PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 24658 user 20 0 3009360 264068 170964 R 99.7 0.8 10:42.78 systemsettings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486340] New: Failure to show firewalld status
https://bugs.kde.org/show_bug.cgi?id=486340 Bug ID: 486340 Summary: Failure to show firewalld status Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_firewall Assignee: plasma-b...@kde.org Reporter: descartav...@gmail.com CC: lucas.bia...@kde.org, tcanabr...@kde.org Target Milestone: --- SUMMARY Firewall status show as disabled when it is enabled. STEPS TO REPRODUCE 1. `firewall-cmd --state` shows "running" 2. `systemctl status firewalld.service` shows "active"/"enabled". 3. Open the KDE settings, connection, firewall. 4. type in user password OBSERVED RESULT status is disabled EXPECTED RESULT correct status and rules shown. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-2 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 6650U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 845 14 inch G9 Notebook PC System Version: SBKPF ADDITIONAL INFORMATION ``` ● firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; preset: disabled) Active: active (running) since Tue 2024-04-30 05:59:04 -03; 2h 24min ago Docs: man:firewalld(1) Main PID: 715 (firewalld) Tasks: 2 (limit: 37657) Memory: 55.8M (peak: 57.4M) CPU: 346ms CGroup: /system.slice/firewalld.service └─715 /usr/bin/python /usr/bin/firewalld --nofork --nopid Apr 30 05:59:03 systemd[1]: Starting firewalld - dynamic firewall daemon... Apr 30 05:59:04 systemd[1]: Started firewalld - dynamic firewall daemon. ``` no other backends available ``` # systemctl status ufw.service Unit ufw.service could not be found. ``` about screen for firewall settings panel shows: Backend: firewalld Version: 2.1.1 nft frontends installed on system: iptables-nft, nftables, firewalld. $ iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination $ firewall-cmd --get-active-zones public (default) interfaces: wifi $ firewall-cmd --info-zone=public public (default, active) target: default ingress-priority: 0 egress-priority: 0 icmp-block-inversion: no interfaces: wlp1s0 sources: services: dhcpv6-client ssh portknock exitlesstornode wg8 ports: protocols: forward: yes masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 486294] Better PAM recommendations to distributions (no nologin).
https://bugs.kde.org/show_bug.cgi?id=486294 Gabriel Barros changed: What|Removed |Added CC||aro...@archlinux.org -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 486294] New: Better PAM recommendations to distributions (no nologin).
https://bugs.kde.org/show_bug.cgi?id=486294 Bug ID: 486294 Summary: Better PAM recommendations to distributions (no nologin). Classification: Plasma Product: kscreenlocker Version: git-master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: descartav...@gmail.com Target Milestone: --- following recommendations on https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/163 my distro adopted these files[0] in place of what was being shipped before[1]. One downside of the recommendation is that *unlocking* the desktop is now prevented if there's a shutdown scheduled (or other reason to have the `nologin` file present). because of the line `auth requisite pam_nologin.so`. It is very frustrating if you get a notification on your lock screen about the system going down in 5min and all you can do is nervously wait to lose your work. Are there good reasons to have the auth nologin module there? Can we recommend without it? Should we have sample files in this upstream distribution and avoid the communication issues? most packages i've seen just added the recommended text to their packaging script, and now you don't know if they are following upstream or not. Specially now that we cannot build without PAM? (https://bugs.kde.org/show_bug.cgi?id=455303) -- [0] https://gitlab.archlinux.org/archlinux/packaging/packages/kscreenlocker/-/commit/7fd674f638497ba84e788118d3bbc524691974f0#6d3349510821738885fce1ed921375cb34e361f1 -- [1] https://wiki.archlinux.org/index.php?title=SDDM&oldid=805510#Using_a_fingerprint_reader ``` #/etc/pam.d/kde authsufficient pam_unix.so try_first_pass likeauth nullok authsufficient pam_fprintd.so ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484069] New: Panel unresponsive after extending desktop to multi-monitor
https://bugs.kde.org/show_bug.cgi?id=484069 Bug ID: 484069 Summary: Panel unresponsive after extending desktop to multi-monitor Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: descartav...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 After plugging another monitor (doesn't matter if first time or a known screen) the panel will only respond to right click. And even then, the right click will ignore the "widget" and show the right click for the panel itself. (i.e. only shows the "add widget" and "Enter edit mode" in the menu) STEPS TO REPRODUCE 1. Move panel to left of screen (i.e. vertical) 2. Attach another monitor (in extend screen mode) 3. easier to reproduce if it's a known secondary screen, to the top of the main one. OBSERVED RESULT No clicks on any of the panels work. Right click anywhere on the panel will show the few option menu as if rigth-clicking an empty panel area. Removing external screen doesn't solve the problem, still unresponsive. Things I cannot click: clock, quick launch icons, systemtray icons (wifi, battery, etc), launcher button. EXPECTED RESULT I could still click panel items. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 6650U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 845 14 inch G9 Notebook PC ADDITIONAL INFORMATION Workaround: right-click, enter edit mode, exit edit mode. Everything works again just fine. with or without external monitor attached. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430210] Font previews do not show up on Wayland
https://bugs.kde.org/show_bug.cgi?id=430210 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 479054] UDP port keeps changing
https://bugs.kde.org/show_bug.cgi?id=479054 --- Comment #2 from Gabriel Barros --- Correct. Happens with both "ok" and "appply". Still using release 23.08.4, the UDP port change does work depending on the network i'm at. I looked at the code and it should not make any difference. I do not have any pnp plugin enabled! (only plugin enabled is "information widget" which is included with the regular release) only thing that could be impacting my settings is https://invent.kde.org/network/ktorrent/-/blob/master/libktcore/interfaces/functions.cpp#L89 but it doesn't seem to be the case. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 479054] New: UDP port keeps changing
https://bugs.kde.org/show_bug.cgi?id=479054 Bug ID: 479054 Summary: UDP port keeps changing Classification: Applications Product: ktorrent Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: descartav...@gmail.com Target Milestone: --- SUMMARY My settings UDP port keeps changing. And it refuses to change after I start the application. Already tried to stop all torrents before making changes etc. The help tooltip mentions upnp, but i don't see options to disable or use that. STEPS TO REPRODUCE 1. open Ktorrent. Set "UDP tracker port" to 1234 2. close it. 3. open again OBSERVED RESULT UDP port changes to something random, like 57733 EXPECTED RESULT UDP port setting remain the same 1234. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479029] Improper behavior on shutdown leading to data loss
https://bugs.kde.org/show_bug.cgi?id=479029
--- Comment #2 from Gabriel Barros ---
Also noticed that on wayland I do not get a close dialog for a unsaved `kate`
buffer. I'm knew about Sessions Errata, but did I read that wrong? Does that
errata also cause loss of data on shutdown and not just failure to save/restore
open windows?
I think for Konsole I've found the root cause (and will probably quit using it
ASAP)
https://invent.kde.org/utilities/konsole/-/blob/master/src/MainWindow.cpp?ref_type=heads#L674
```
bool MainWindow::queryClose()
{
// Do not ask for confirmation during log out and power off
// TODO: rework the dealing of this case to make it has its own
confirmation
// dialog.
if (qApp->isSavingSession()) {
return true;
}
```
But that still doesn't explain improper shutdown of things like Ktorrent and
Kate on my wayland/systemd system
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 465242] Partition restore fails with misleading message about unavailable space
https://bugs.kde.org/show_bug.cgi?id=465242 --- Comment #6 from Gabriel Barros --- Reading the whole history again, i do think it is confusing i said: > > 2. click the unallocated space and from context menu select "Restore" and you explained my mistake as: > Message is a bit misleading, but what you are trying to do is not a valid > operation. You are trying to restore disk image into a partition (i.e. > restore /dev/sda into /dev/sda1). So, when i click the "unallocated" I'm clicking "sda1"? that is confusing, yes. What do you suggest we change the text to? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479029] Improper behavior on shutdown leading to data loss
https://bugs.kde.org/show_bug.cgi?id=479029 --- Comment #1 from Gabriel Barros --- Oops, meant to link to this bug on the ktorrent example https://bugs.kde.org/show_bug.cgi?id=415580 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479029] New: Improper behavior on shutdown leading to data loss
https://bugs.kde.org/show_bug.cgi?id=479029 Bug ID: 479029 Summary: Improper behavior on shutdown leading to data loss Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: descartav...@gmail.com Target Milestone: --- Created attachment 164449 --> https://bugs.kde.org/attachment.cgi?id=164449&action=edit sudo journalctl -b -1 SUMMARY Improper shutdown of everything under the kwin shell. I suspect this is a combination of moving to incomplete features on systemd, wayland and QTdBus. STEPS TO REPRODUCE 1. Start KDE 2. Open terminal or other applications that can spawn other processes 2.1 start application that saves a PID file and remove them on exit, e.g. `qemu` 3. Open "regular" kde applications 3.1 pay attention to things that are only save on application exit, e.g. ktorrent magnet list 4. click shutdown OBSERVED RESULT System shutdowns extremely fast. PID files from terminal applications are still laying around. Data from KDE applications are lost: e.g. https://bugs.kde.org/show_bug.cgi?id=425898 EXPECTED RESULT System sends and wait for applications to exit SOFTWARE/OS VERSIONS Linux: 6.6.8-arch1-1 (64-bit) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION logs for spawned process under kterminal being killed: ``` systemd[735]: Stopped Firefox Web Browser - Web Browser. systemd[735]: app-org.kde.konsole-123.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-123.scope, ignoring: Operation not permitted systemd[735]: app-org.kde.konsole-123.scope: Killing process 13618 (qemu-system-x86) with signal SIGKILL. systemd[735]: app-org.kde.konsole-123.scope: Killing process 13622 (kvm-nx-lpage-recovery-13618) with signal SIGKILL. systemd[735]: app-org.kde.konsole-123.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-123.scope, ignoring: Operation not permitted systemd[735]: Stopped Konsole - Terminal. systemd[735]: app-org.kde.konsole-123.scope: Consumed 7min 31.417s CPU time. systemd[735]: Removed slice User Background Tasks Slice. systemd[735]: background.slice: Consumed 5min 46.912s CPU time. ``` logs i believe are relevant to kde applications being killed ``` 10:03:01 systemd[1048]: Stopped KDE Session Management Server. 10:03:01 systemd[1048]: Stopping KDE Window Manager... 10:03:01 systemd[1048]: Stopped Konsole - Terminal. 10:03:01 systemd[1048]: app-org.kde.konsole-ab0f9c53c82946e98f088cbe397d3678.scope: Consumed 1.930s CPU time. 10:03:01 kwin_wayland[1092]: kwin_core: Failed to open /dev/input/event8 device (Message recipient disconnected from message bus without replying) 10:03:01 dbus-daemon[909]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.26' (uid=1000 pid=1092 comm="/usr/bin/kwin_wayland --wayland-fd 7 --socket wayl") 10:03:01 dbus-daemon[909]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.login1.service': Refusing activation, D-Bus is shutting down. 10:03:01 polkitd[933]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.37, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* 10:03:01 kded5[1201]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointe
[ktorrent] [Bug 415580] KTorrent does not save magnets unless properly shut down
https://bugs.kde.org/show_bug.cgi?id=415580 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #2 from Gabriel Barros --- Confirmed on 23.08.4 Also ask to increase importance/severity as a regular KDE shutdown lately will send SIGHUP in the same split second as SIGTERM, resulting on everything being improperly killed. (lots of bugs from the mix of systemd, QTDBus, wayland being worked on). -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 377349] QFileDialog (using KDEs file dialog): open/save button is enabled even if no file is selected
https://bugs.kde.org/show_bug.cgi?id=377349 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #4 from Gabriel Barros --- isn't this expected behaviour. The current dir is "selected" and will be returned if you press open/save. i believe you have to pass options such as QFileDialog::AnyFile to force one file selection. I might be wrong. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 441665] Button "Setup a NAP network" in bluetooth connection settings does nothing.
https://bugs.kde.org/show_bug.cgi?id=441665 --- Comment #6 from Gabriel Barros --- > networkmanager notification icon meant, "network connections" widget. I guess it can also be setup via Settings > connection -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 441665] Button "Setup a NAP network" in bluetooth connection settings does nothing.
https://bugs.kde.org/show_bug.cgi?id=441665 --- Comment #5 from Gabriel Barros --- workaround: 1. setup the bluetooth connection using this dialog. 2. ignore the network button 3. click the netmanager notification icon 4. click "connect" next to the newly available bluetooth device item. networkmanager notification icon turns into a connected bluetooth icon (kinda confusing as now you have two bluetooth connected icons there), and a NAP device shows up for me on `ip` command outout: `enp3s0f3u3` -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 441665] Button "Setup a NAP network" in bluetooth connection settings does nothing.
https://bugs.kde.org/show_bug.cgi?id=441665 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #4 from Gabriel Barros --- Confirmed. Starting `/usr/bin/systemsettings kcm_bluetooth` also does not show any output when clicking that button. nothing my bluetoothd logs either ``` Mar 16 16:10:36 elite bluetoothd[669]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink/sbc Mar 16 16:10:36 elite bluetoothd[669]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/sbc Mar 16 16:10:36 elite bluetoothd[669]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Mar 16 16:10:36 elite bluetoothd[669]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Mar 16 16:10:36 elite bluetoothd[669]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Mar 16 16:10:36 elite bluetoothd[669]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Mar 16 16:10:36 elite bluetoothd[669]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Mar 16 16:10:36 elite bluetoothd[669]: Endpoint registered: sender=:1.55 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Mar 16 16:10:37 elite bluetoothd[669]: Failed to set mode: Failed (0x03) Mar 16 16:13:28 elite bluetoothd[669]: /org/bluez/hci0/dev_0C_C4_13_27_43_74/sep1/fd0: fd(39) ready ``` (button was clicked on 16:30... timestamp. nothing on any logs) Operating System: Arch Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 PRO 6650U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 845 14 inch G9 Notebook PC -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 402542] Failed copy from mtp with large number of files and large amount of data
https://bugs.kde.org/show_bug.cgi?id=402542 --- Comment #7 from Gabriel Barros --- I'm still having trouble to see anything anormal in logs etc. and to figure out the exact way to reproduce. One thing i noted but is not 100%, is that copying multiple folders at once on the root of the operation (i.e. select multiple folders and hit Ctrl+c as opposed to a single folder with lots of subfolders) seems to caus the bug more often than copying a single root folder with much more files inside. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 402542] Failed copy from mtp with large number of files and large amount of data
https://bugs.kde.org/show_bug.cgi?id=402542 Gabriel Barros changed: What|Removed |Added Resolution|WORKSFORME |--- CC||descartav...@gmail.com Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #6 from Gabriel Barros --- still happens on 22.12.2 I was about to create a dup: SUMMARY Dolphin holds the MTP queue when copying large directories from Android phones. Nothing works until reconnect. All file operations via Dolphin that happens after trying to copy a large directory (anything that shows the enumeration notification before the overwrite dialogs/progress notification) Dolphin doesn't seem to know it is holding the connection open, as all file operations that is not moving directories will also fail after that bug triggers. It shows the "access denied" dialog error. running `mtp-detect` while dolphin is idle but holding that ghost connection shows """ Attempting to connect device(s) libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device Unable to open raw device 0 """ STEPS TO REPRODUCE 1. open a MTP listing with a directory that contais several files (TBD minimal number of files) 2. hit Ctrl+C/Copy on that directory 3. move to a regular FS directory and hit Ctrl+v/Paste OBSERVED RESULT Dolphin counts the files correctly, but then every single read operation from MTP shows the "access denied" error dialog. Retries always fail. Going trhu the file list (either via ignore or ignore all) will execute over the correct file list, but show access denied for each file. EXPECTED RESULT Dolphin will count the files, and execute the copy operation. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.11-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 PRO 6650U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 845 14 inch G9 Notebook PC -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 437204] changelogs are out of date
https://bugs.kde.org/show_bug.cgi?id=437204 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #3 from Gabriel Barros --- (In reply to Carl Schwan from comment #2) > I started something a few days ago: > https://invent.kde.org/sysadmin/release-tools/-/merge_requests/16 This will > allows to put the list of bug fixed in the AppStream data and then display > them in apps.kde.org/konsole for example. Making the data also available in > konsole.kde.org and usable as fallback should be doable once it's available. tried to follow that lead. Shocked how complex the infrastructure is. Still not 100pct clear how things are sourced and where they ultimately ends up at. But i see that they went a different direction. I actually liked the simplification, but i'm just a passer-by. I also see the "lag" on the release version is just a couple minor version now. so maybe things improved elsewhere? still not up-to-date tho. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 465242] Partition restore fails with misleading message about unavailable space
https://bugs.kde.org/show_bug.cgi?id=465242 --- Comment #4 from Gabriel Barros --- > these menu entries are in "Partition". All operations in it are partition > specific. There is also device menu for device-wide things. makes sense for the menus. In the "devices" menu i see "restore partion table" On the partition menu there's only "restore" and that do make sense in that menu as you mention. I think my confusion is when you right click an empty drive's empty space. is that showing me the menu for partition or device (since there's no partition) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436336] last lines on screen doesn't render correctly
https://bugs.kde.org/show_bug.cgi?id=436336 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #2 from Gabriel Barros --- Not seeing this on 22.12.2 anymore. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 465242] Partition restore fails with misleading message about unavailable space
https://bugs.kde.org/show_bug.cgi?id=465242 --- Comment #2 from Gabriel Barros --- I see. Thank you. The manual does say it works on a empty region, so I assumed wrong. Guess the feature is not well named either, not just the error. Menu items should be called "restore partition" not just "restore"/"backup". -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 378906] Ktorrent disables automatic screen lock
https://bugs.kde.org/show_bug.cgi?id=378906 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #19 from Gabriel Barros --- i think everyone agrees that having an option to prevent sleep, but still locking the screen is the most desirable and common sense option. Can we open a blocker ticket on KScreenLocker(?) to have this alternative? I'm not familiar with the current KDE ecosystem to understand where the new blocker should live, but happy to do the leg work after i'm pointed in the right direction. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 465242] New: Partition restore fails with misleading message about unavailable space
https://bugs.kde.org/show_bug.cgi?id=465242 Bug ID: 465242 Summary: Partition restore fails with misleading message about unavailable space Classification: Applications Product: partitionmanager Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: descartav...@gmail.com Target Milestone: --- SUMMARY When trying to restore a 800Mb ISO image to a 120Gb empty drive, I get an error about space not being enough. STEPS TO REPRODUCE 1. Insert a clean pen drive. (tried: a. no partition table; b. with clean MBR; c. with clean GPT) 2. click the unallocated space and from context menu select "Restore" 3. Select a ISO file (e.g. arch install media) Confirm defaults on next dialog. file used: https://america.mirror.pkgbuild.com/iso/2023.02.01/archlinux-2023.02.01-x86_64.iso OBSERVED RESULT I get an error: """ It is not possible to create the target partition large enough to hold the source. This may happen if not all partitions on a device are correctly aligned or when copying a primary partition into an extended partition. """ EXPECTED RESULT I expect the target partition created. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 PRO 6650U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP EliteBook 845 14 inch G9 Notebook PC ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464472] crash on enablig firewall in settings
https://bugs.kde.org/show_bug.cgi?id=464472 --- Comment #2 from Gabriel Barros --- Created attachment 155481 --> https://bugs.kde.org/attachment.cgi?id=155481&action=edit New crash information added by DrKonqi systemsettings (5.26.5) using Qt 5.15.8 fresh install. all packages up to date. no custom setting. Entirely defaults. simply clicking the "view connections" causes the crash all the time. -- Backtrace (Reduced): #5 0x7efcb1d60f81 in QString::split(QChar, QFlags, Qt::CaseSensitivity) const () at /usr/lib/libQt5Core.so.5 [...] #8 0x7efcb1e184bd in QProcess::finished(int, QProcess::ExitStatus) () at /usr/lib/libQt5Core.so.5 [...] #12 0x7efcb1ec07e4 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #13 0x7efcb1ec0928 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7efcb2b78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464472] crash on enablig firewall in settings
https://bugs.kde.org/show_bug.cgi?id=464472 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
