[systemsettings] [Bug 485659] (Global) Shortcuts do not persist across sessions; unwanted shortcuts from old applications do
https://bugs.kde.org/show_bug.cgi?id=485659 Luca Weiss changed: What|Removed |Added CC||bugzi...@lucaweiss.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483115] Lost hotkey assignment and reappearing deleted hotkey entries in KDE 6
https://bugs.kde.org/show_bug.cgi?id=483115 Luca Weiss changed: What|Removed |Added CC||bugzi...@lucaweiss.eu --- Comment #8 from Luca Weiss --- I'm pretty sure I'm seeing this issue on one of my installs. I've had the shortcut Ctrl+Alt+T configured to launch Konsole but every time I reboot the shortcut gets lost. When I set the shortcut in the system settings this part gets added to ~/.config/kglobalshortcutsrc: [services][org.kde.konsole.desktop] _launch=Ctrl+Alt+T However on a different computer I do not see the same issue, the shortcut stays where it's supposed to. Both are running Arch Linux, currently Plasma 6.1.5 with Framewrks 6.6.0 and Qt 6.7.2. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 492408] Crash in KColorSchemeManager::indexForScheme
https://bugs.kde.org/show_bug.cgi?id=492408
Luca Beltrame changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
CC||lbeltr...@kde.org
--- Comment #1 from Luca Beltrame ---
Can reproduce. I had a localized color scheme in kontactrc ("Predefinito") and
that triggered the crash.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 424790] kpasswdserver not persisting AUTHINFO_EXTRAFIELD_DOMAIN in wallet
https://bugs.kde.org/show_bug.cgi?id=424790 Luca Manganelli changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #7 from Luca Manganelli --- Now with the new authentication window, it's working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492022] Plasmashell crashing
https://bugs.kde.org/show_bug.cgi?id=492022 Luca Manganelli changed: What|Removed |Added CC||luc...@gmail.com --- Comment #5 from Luca Manganelli --- It happens to me too. This since the update of KDE Neon from 6.1.3 to 6.1.4: simply if I click two consecutive times on an icon (i.e. google chrome) on the application task bar (on the bottom side of screen), plasmashell crashes. I've already sent all data through the crash handler window. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 491356] Unable to open files on Veracrypt encrypted volume in Dolphin
https://bugs.kde.org/show_bug.cgi?id=491356
--- Comment #1 from luca ---
It seems that Qt programs are killed by SIGPIPE
=
56137 write(2, "Qt: Session management error: No"..., 91) = -1 EPIPE (Pipe
interrotta)
56137 --- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=56137,
si_uid=1000} ---
56140 <... futex resumed>) = ?
56139 <... futex resumed>) = ?
56138 <... poll resumed> ) = ?
56140 +++ killed by SIGPIPE +++
56139 +++ killed by SIGPIPE +++
56138 +++ killed by SIGPIPE +++
56137 +++ killed by SIGPIPE +++
=
Prevent "Qt: Session management error: None of the authentication protocols
specified are supported" with unset SESSION_MANAGER helps.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 491356] New: Unable to open files on Veracrypt encrypted volume in Dolphin
https://bugs.kde.org/show_bug.cgi?id=491356 Bug ID: 491356 Summary: Unable to open files on Veracrypt encrypted volume in Dolphin Classification: Applications Product: dolphin Version: 23.08.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: luca.pedrie...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Veracrypt opens encrypted mounted volume in Dolphin. Using plasma apps(gwen, okular or dragon) to open files, bouncing icons appear next to the mouse pointer. But then nothing happens. Non-kde apps(feh, gimp, vlc) works. https://discuss.kde.org/t/gwenview-dragonplayer-cant-open-files-on-veracrypt-encrypted-volume-in-dolphin/17641 Is this the same issue? https://bugs.kde.org/show_bug.cgi?id=442210 Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.9.12-amd64 (64-bit) Graphics Platform: offscreen Processors: 8 × Intel® Core™ i3-10100 CPU @ 3.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the wrong screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 --- Comment #8 from Luca Saalfeld --- So I have new information: The new windows spawn above the window with the current focus, not on the screen where the mouse is. So the mouse position is only relevant *once* for new windows, after that the monitor on which the active window is, is prioritized. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the wrong screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 Luca Saalfeld changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Luca Saalfeld --- Should have updated title and status quite a bit before, but I just forgot to do that -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the wrong screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 Luca Saalfeld changed: What|Removed |Added Summary|Windows always open on the |Windows always open on the |left screen after reopening |wrong screen after |without moving the cursor |reopening without moving ||the cursor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the left screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 --- Comment #6 from Luca Saalfeld --- This also affects the task switcher. I think that this bug simply affects everything, that spawns a window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the left screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 Luca Saalfeld changed: What|Removed |Added Version|6.1.1 |6.1.2 --- Comment #5 from Luca Saalfeld --- There's apparently another version of this bug, where the right monitor is the one everything is placed on. That's at least what is happening right now. My guess is that's it's not monitor position specific (only the left monitor), but instead just choosing the wrong monitor to place new windows on. I could create a setup with more monitors to test this, but the other ones will have a lower resolution :/ -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486707] Playing videos on a Pixel 3A fails, failure to open VDPAU backend
https://bugs.kde.org/show_bug.cgi?id=486707 --- Comment #2 from Luca Weiss --- I was digging a bit and from https://invent.kde.org/multimedia/plasmatube/-/blob/v24.05.2/src/utils/mpvobject.cpp?ref_type=tags#L18 I was trying "mpv --hwdec=auto-safe bigbucksbunny.mov" and that prints similar messages but the video still plays, so these vdpau messages can probably be ignored. Failed to open VDPAU backend Error loading shared library libvdpau_nvidia.so: No such file or directory [ffmpeg] AVHWDeviceContext: VDPAU device creation on X11 display :0 failed. (minus any typos, I copied these messages manually) -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486707] Playing videos on a Pixel 3A fails, failure to open VDPAU backend
https://bugs.kde.org/show_bug.cgi?id=486707 Luca Weiss changed: What|Removed |Added CC||bugzi...@lucaweiss.eu --- Comment #1 from Luca Weiss --- Can confirm on Fairphone 4 phone (Qualcomm SM7225), also postmarketOS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the left screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 --- Comment #4 from Luca Saalfeld --- I just found it that this bug is not app specific. If a window launches on the left screen (i.e. the bug occurs), *all* windows launch on the left screen, no matter of what app it belongs to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the left screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 --- Comment #3 from Luca Saalfeld --- Yes, the bug still occurs. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the left screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 --- Comment #1 from Luca Saalfeld --- This also happens with the application launcher. https://bugs.kde.org/show_bug.cgi?id=487945 is essentially this bug, but only for the application dashboard. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] Windows always open on the left screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 Luca Saalfeld changed: What|Removed |Added CC||lulukl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489640] New: Windows always open on the left screen after reopening without moving the cursor
https://bugs.kde.org/show_bug.cgi?id=489640 Bug ID: 489640 Summary: Windows always open on the left screen after reopening without moving the cursor Classification: Plasma Product: kwin Version: 6.1.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: lulukl...@gmail.com Target Milestone: --- SUMMARY Windows always open on the left screen after reopening without moving the cursor STEPS TO REPRODUCE 1. Open any app 2. Close the app 3. Reopen the app without moving the cursor since step 2 OBSERVED RESULT App window opens on the left screen EXPECTED RESULT App window opens on the screen the cursor is on 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-zen1-1-zen (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION If I open something for the first time everything is fine. Every app opens on the monitor the cursor is on. Closing the app, then opening it again - without moving the cursor - opens them on my left screen. Any further launches also starts on the left screen. Moving the cursor after closing the app causes it to launch normally (normally as in the bug is still there. This single relaunch is fine. Reopen without moving the mouse again still causes the bug). -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 489283] Settings KRDP remote desktop are uneditable
https://bugs.kde.org/show_bug.cgi?id=489283 --- Comment #6 from Luca Manganelli --- (In reply to Dm from comment #4) > No, even the switch is unclickable (also in colors of unclickable items) confirming this behavior. -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 489283] New: Settings KRDP remote desktop are uneditable
https://bugs.kde.org/show_bug.cgi?id=489283 Bug ID: 489283 Summary: Settings KRDP remote desktop are uneditable Classification: Plasma Product: KRdp Version: 6.1.1 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: luc...@gmail.com CC: ahiems...@heimr.nl Target Milestone: --- SUMMARY Cannot modify any option of KRDP in system settings. After I updated KDE Neon from 6.1.0 to 6.1.1, I am not unable to edit users or modify any KRDP option. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 485799] Get a lot of `Failed to process EWS request: ` with empty details
https://bugs.kde.org/show_bug.cgi?id=485799 --- Comment #4 from Luca Beltrame --- The memory leak at least should be fixed (doesn't leak anymore in my tests) by https://invent.kde.org/pim/kdepim-runtime/-/commit/aacd0807f13d0694b2bde515964b5f081973da5f. The spam in the log is a different issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 486861] Memory leak in EWS resource
https://bugs.kde.org/show_bug.cgi?id=486861 --- Comment #3 from Luca Beltrame --- Git commit aacd0807f13d0694b2bde515964b5f081973da5f by Luca Beltrame, on behalf of Louis Moureaux. Committed on 26/06/2024 at 06:06. Pushed by lbeltrame into branch 'master'. Fix a memory leak in TransferJob TransferJob wasn't releasing its QNetworkReply upon deletion, which resulted in it and associated resources being leaked. With the many requests spotted in bug 485799 this leads to heavy resource usage. | Heaptrack Before | Heaptrack After | | -- | -- | |  |  | M +6-5resources/ews/ewsclient/transferjob.cpp M +3-1resources/ews/ewsclient/transferjob.h https://invent.kde.org/pim/kdepim-runtime/-/commit/aacd0807f13d0694b2bde515964b5f081973da5f -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 486861] Memory leak in EWS resource
https://bugs.kde.org/show_bug.cgi?id=486861 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #2 from Luca Beltrame --- For sure related to https://bugs.kde.org/show_bug.cgi?id=485799 (either this one or the other should be marked as duplicate) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 488666] New: Bogus "Continue playing" notifications
https://bugs.kde.org/show_bug.cgi?id=488666 Bug ID: 488666 Summary: Bogus "Continue playing" notifications Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: l...@z3ntu.xyz CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY When for example playing music on my laptop (Chromium, with the Plasma Integration extension), when the song switches to the next one the phone gets a notification "Continue playing $songname" which disappears again after a second. The same happens when just pausing the music manually, the phone gets a brief notification which disappears again. After a bit of searching I found the media plugin settings have a setting to disable "Continue playing" notifications, but if that's the expected behavior I'm not sure this setting should be on by default since it spams the phone quite a bit with (bogus) notifications. STEPS TO REPRODUCE 1. Play music in Chromium browser 2. Wait until current song ends and next one starts 3. Observe <1 second of "Continue playing" notification on the phone OBSERVED RESULT The notification appears for less than a second. EXPECTED RESULT Depending how this notification should normally behave, either stay there for longer? Or not appear in the first place? SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Android app version: 1.31.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485425] Running some Wine applications through Xwayland forces constant fullscreen repaints for the rest of the session
https://bugs.kde.org/show_bug.cgi?id=485425 --- Comment #21 from Luca Carlon --- Hello, I was affected by this issue as well. I could reproduce it by simply using VLC or Joplin. Approximately 10 days ago I read this discussion and I switched the effect from scale to fade. This immediately fixed the problem. Then I immediately switched back to scale and I've been testing for these 10 days. I was not able to reproduce this anymore. It seems 100% fixed so far. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488004] Plasma 6 doesn't remember multiple monitor layout on X11
https://bugs.kde.org/show_bug.cgi?id=488004 Luca Allulli changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Luca Allulli --- Possibly I was mislead by a different "issue": in the Display Configuration plasmoid, the behavior of "Extend to left" and "Extend to right" buttons is inverted with respect to Plasma 5. Thus, every time I select "Extend to right", my laptop monitor is placed to the left of my external monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488004] New: Plasma 6 doesn't remember multiple monitor layout on X11
https://bugs.kde.org/show_bug.cgi?id=488004 Bug ID: 488004 Summary: Plasma 6 doesn't remember multiple monitor layout on X11 Classification: Plasma Product: kwin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: l.allu...@gmail.com Target Milestone: --- On X11, in a multimonitor setting, Plasma doesn't remember the relative position of monitors. Every time I disconnect and connect again an external monitor, I have to open Display Configuration and rearrange my monitors to reflect their physical position on my desktop. SOFTWARE/OS VERSIONS Linux: Manjaro, Linux 6.6.32-1 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480032] Window is out of screen after unplugging external display
https://bugs.kde.org/show_bug.cgi?id=480032 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #5 from Luca Carlon --- This happens to me very frequently, without any user switch. Simply unplug a screen when multiple windows are open: some windows are moved from the unplugged screen to the visible one, others remain invisible. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486535] kwin_wayland starts consuming a high amount of CPU
https://bugs.kde.org/show_bug.cgi?id=486535 --- Comment #1 from Luca Carlon --- I can reproduce with other apps using XWayland. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 485799] Get a lot of `Failed to process EWS request: ` with empty details
https://bugs.kde.org/show_bug.cgi?id=485799 --- Comment #3 from Luca Beltrame --- (In reply to Luca Beltrame from comment #2) > I haven't found a way to debug *why* it's invalid. dd785b95af83fd74618b5e4ce2904fa86db771e3 in kdepim-runtime might be suspect, but I have no way of confirming it. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 485799] Get a lot of `Failed to process EWS request: ` with empty details
https://bugs.kde.org/show_bug.cgi?id=485799 Luca Beltrame changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||lbeltr...@kde.org Ever confirmed|0 |1 --- Comment #2 from Luca Beltrame --- This is because malformed data is sent, this is the reply from the server (you should set QT_LOGGING_RULES="*org.kde.pim.ews.client.proto*.debug=true" to have it dumped somewhere): http://schemas.xmlsoap.org/soap/envelope/";>http://schemas.microsoft.com/exchange/services/2006/types";>a:ErrorInvalidOperationId is malformed.http://schemas.microsoft.com/exchange/services/2006/errors";>ErrorInvalidOperationhttp://schemas.microsoft.com/exchange/services/2006/errors";>Id is malformed. I haven't found a way to debug *why* it's invalid. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486550] Wrong layout of the desktop folder settings window
https://bugs.kde.org/show_bug.cgi?id=486550 --- Comment #1 from Luca Carlon --- Created attachment 169178 --> https://bugs.kde.org/attachment.cgi?id=169178&action=edit Layout of the window after resizing it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486550] New: Wrong layout of the desktop folder settings window
https://bugs.kde.org/show_bug.cgi?id=486550 Bug ID: 486550 Summary: Wrong layout of the desktop folder settings window Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com CC: notm...@gmail.com, qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY Resizing the "Desktop Folder Settings" may lead to a wrong layout. STEPS TO REPRODUCE 1. Open the desktop folder settings window from the menu in the desktop. 2. Resize it. OBSERVED RESULT The window is clearly too small, it only shows two images (this should also be fixed). It is therefore necessary to always resize it. After resizing it, the layout typically breaks, and the bar containing the "add" and "get new" buttons is misplaced or even lost. EXPECTED RESULT The title bar containing the "add" and "get new" buttons should remain at the top. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.8.8-2-MANJARO (64-bit) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486535] New: kwin_wayland starts consuming a high amount of CPU
https://bugs.kde.org/show_bug.cgi?id=486535 Bug ID: 486535 Summary: kwin_wayland starts consuming a high amount of CPU Classification: Plasma Product: kwin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: carlon.l...@gmail.com Target Milestone: --- SUMMARY After a variable amount of time, kwin_wayland starts consuming a high amount of CPU. Typical CPU usage of kwin_wayland while system is idle is 0-2% on this machine. When the problem appears, consumption rises to 8-12% or even more. Framerate is lower and CPU fan accelerates. This only started to happen when I upgraded to Plasma 6. It never happened with Plasma 5. STEPS TO REPRODUCE After trying many things, I found a weird way to reproduce. It does not happen 100% of the times, but doesn't take much to reproduce here: 1. Close every application/window. 2. Open VLC and play a video (in Manjaro VLC 3 is using XWayland by default); 3. Seek a few times into the video or/and try to resize the window a bit. This makes kwin_wayland consume a bit more CPU, going above 20%, which may be normal; 4. wait a few seconds and close VNC. 5. In some cases, kwin_wayland goes back to 1% or less, which is OK. Go back to step 2 in this case and try again. In other cases, it remains at around 10% CPU or even more. OBSERVED RESULT System framerate lowers. It even affects video playback in VLC, making the system pretty bad to use. Fan accelerates, leading to higher battery consumption. The situation does not fix by itself, I need to reboot or logout/login. EXPECTED RESULT With the provided steps, I'd expect kwin_wayland to go back to the usual 0-2% CPU usage after VLC is closed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.8.8-2-MANJARO (64-bit) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFO: I tried to disable vaapi acceleration. Nothing changes. I tried to blacklist nvidia (I only use the Intel GPU anyway), nothing changed. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483625] The microphone icon is missing. Notifications flew to the corner of the screen
https://bugs.kde.org/show_bug.cgi?id=483625 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #10 from Luca Carlon --- I'm also experiencing this issue. I've never experienced this with Plasma 5. It only started with Plasma 6. I found a way to reproduce quickly: 1. setup the system to have two screens (I have the laptop screen and an external screen), and set the external screen to be the primary; 2. unplug the external screen; 3. wait for the system to adapt to the new setup; 4. plug the screen again; 5. try to set the volume; 6. you should see the volume window in the upper left corner of one screen. It won't even move to the other screen properly. It is also possible to simply turn off the screen by using the proper Plasma shortcut. To fix: logout and then login again. I can reproduce in a few seconds. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481000] Kicker not highlighting selection, neither via keyboard nor hover
https://bugs.kde.org/show_bug.cgi?id=481000 --- Comment #21 from Luca Carlon --- The problem did not appear again for me after what I explained above. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478157] Discover restarts your computer even if the update download was interrupted
https://bugs.kde.org/show_bug.cgi?id=478157 Luca Moscato changed: What|Removed |Added CC||luca.mosc...@gmail.com --- Comment #1 from Luca Moscato --- Issue found also on a fresh installation on Fedora 39, that received a number of packages to be updated higher than normal after xz vulnerabilty fixes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 483541] Running from the keyboard shortcut erases SSH_AUTH_SOCK from env
https://bugs.kde.org/show_bug.cgi?id=483541 --- Comment #9 from Luca Vallerini --- (In reply to Nicolas Fella from comment #7) > When you do "cat /proc/$(pidof kwin_wayland)/environ", does have > SSH_AUTH_SOCK have the right value there? This is the output: HOME=/home/lucaLANG=it_IT.UTF-8LC_ADDRESS=it_IT.UTF-8LC_IDENTIFICATION=it_IT.UTF-8LC_MEASUREMENT=it_IT.UTF-8LC_MONETARY=it_IT.UTF-8LC_NAME=it_IT.UTF-8LC_NUMERIC=it_IT.UTF-8LC_PAPER=it_IT.UTF-8LC_TELEPHONE=it_IT.UTF-8LC_TIME=it_IT.UTF-8LOGNAME=lucaPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/binSHELL=/bin/bashSYSTEMD_EXEC_PID=1311USER=lucaXDG_DATA_DIRS=/home/luca/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktopXDG_RUNTIME_DIR=/run/user/1000DEBUGINFOD_URLS=https://debuginfod.neon.kde.org/:QT_ACCESSIBILITY=1DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/busDESKTOP_SESSION=plasmaKCRASH_DUMP_ONLY=1KDE_APPLICATIONS_AS_SCOPE=1KDE_FORK_SLAVES=1KDE_FULL_SESSION=trueKDE_SESSION_UID=1000KDE_SESSION_VERSION=6MOZ_USE_XINPUT2=1PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socketPWD=/home/lucaQT_AUTO_SCREEN_SCALE_FACTOR=0QT_EXCLUDE_GENERIC_BEARER=1QT_WAYLAND_RECONNECT=1XDG_CONFIG_DIRS=/home/luca/.config/kdedefaults:/etc/xdgXDG_CURRENT_DESKTOP=KDEXDG_MENU_PREFIX=plasma-XDG_SEAT=seat0XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0XDG_SESSION_CLASS=userXDG_SESSION_DESKTOP=KDEXDG_SESSION_ID=3XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1XDG_SESSION_TYPE=waylandXDG_VTNR=1XKB_DEFAULT_LAYOUT=itXKB_DEFAULT_MODEL=pc105NOTIFY_SOCKET=/run/user/1000/systemd/notifyMANAGERPID=1252WATCHDOG_PID=1311WATCHDOG_USEC=1500INVOCATION_ID=c660a3af3b934a7695d24ed237c7b133JOURNAL_STREAM=8:7 The output above is the same when run on a Konsole instance launched with krunner, where however the SSH_AUTH_SOCKET is correctly set, in fact "env | grep SSH_AUTH_SOCKET" results in: SSH_AGENT_LAUNCHER=gnome-keyring SSH_AUTH_SOCK=/run/user/1000/keyring/ssh -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 483541] Running from the keyboard shortcut erases SSH_AUTH_SOCK from env
https://bugs.kde.org/show_bug.cgi?id=483541 --- Comment #6 from Luca Vallerini --- (In reply to Nicolas Fella from comment #5) > Are you using X11 or Wayland? Wayland. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 483541] Running from the keyboard shortcut erases SSH_AUTH_SOCK from env
https://bugs.kde.org/show_bug.cgi?id=483541 --- Comment #3 from Luca Vallerini --- (In reply to Nicolas Fella from comment #2) > How are you starting ssh-agent? In my case, it is automatically started by KeePassXC. The agent works as expected in every situation but when launching Konsole with the shortcut. I usually use Yakuake (automatically started after login) and works as expected there too. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 482733] yakuake remembers last screen resolution, have to open twice to get correct size
https://bugs.kde.org/show_bug.cgi?id=482733 Luca Vallerini changed: What|Removed |Added CC||lucaval...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 483541] Running from the keyboard shortcut erases SSH_AUTH_SOCK from env
https://bugs.kde.org/show_bug.cgi?id=483541 --- Comment #1 from Luca Vallerini --- I can reproduce it too. Just Konsole with the default Ctrl+Alt+T shortcut to see the ssh-add -l command fail, but this does not happen if Konsole is run from krunner. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 483541] Running from the keyboard shortcut erases SSH_AUTH_SOCK from env
https://bugs.kde.org/show_bug.cgi?id=483541 Luca Vallerini changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||lucaval...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 482084] Rainbow Parentheses plugin - memory access issues
https://bugs.kde.org/show_bug.cgi?id=482084 --- Comment #1 from Luca Giambonini --- Created attachment 166215 --> https://bugs.kde.org/attachment.cgi?id=166215&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.
[kate] [Bug 482084] New: Rainbow Parentheses plugin - memory access issues
https://bugs.kde.org/show_bug.cgi?id=482084 Bug ID: 482084 Summary: Rainbow Parentheses plugin - memory access issues Classification: Applications Product: kate Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: luc...@bluewin.ch Target Milestone: --- Application: kate (24.02.0) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.6-arch1-1 x86_64 Windowing System: Wayland Distribution: EndeavourOS DrKonqi: 6.0.0 [CoredumpBackend] -- Information about the crash: seems that the function existingColoredBracketForPos generate an memory error. When I disable the plugin Kate works as expected. Kate 24.02.0 with plasma 6.0 The crash can be reproduced every time. -- Backtrace (Reduced): #5 QExplicitlySharedDataPointer::QExplicitlySharedDataPointer (o=..., this=0x7ffce9bc1d30) at /usr/include/qt6/QtCore/qshareddata.h:158 #8 RainbowParenPluginView::rehighlight (this=0x623b63be12b0, view=) at /usr/src/debug/kate/kate-24.02.0/addons/rainbow-parens/rainbowparens_plugin.cpp:417 #9 0x7b0db6f90ca9 in QtPrivate::QSlotObjectBase::call (a=0x7ffce9bc1fd0, r=0x623b63be12b0, this=0x623b63be1880, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433 #10 doActivate (sender=0x623b63be1320, signal_index=3, argv=0x7ffce9bc1fd0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039 #11 0x7b0db6f98d64 in QTimer::timeout (_t1=..., this=0x623b63be1320) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qtimer.cpp:272 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481000] Kicker not highlighting selection, neither via keyboard nor hover
https://bugs.kde.org/show_bug.cgi?id=481000 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #19 from Luca Carlon --- I was also affected by this problem (on Manjaro). The problem started with the updates published the 22/2/2024. I tried to downgrade the packages starting with "k" one by one, but nothing changed. I then downgraded everything else and the problem was fixed. I then tried to upgrade again one by one, but I am now unfortunately unable to reproduce the problem. I can provide the pacman log of that day if needed, but there are more than 300 packages. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadow outlines have artifacts on HiDPI, especially with fractional scale factors
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #26 from Luca Carlon --- Hiding it would be useful for the systems where it is broken. Would it be possible to hide the broken feature for Plasma5, which is still what users will use for several months? For instance, would it be possible to simply not draw it when scaling != 1? I do not think users will complain for a missing broken feature. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadow outlines have artifacts on HiDPI, especially with fractional scale factors
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #24 from Luca Carlon --- Any way to, at least, hide it? It is of no practical use, so hiding it is perfectly acceptable. At least users will not remain with a broken feature for many other months. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462005] Window shadow outlines have artifacts on HiDPI, especially with fractional scale factors
https://bugs.kde.org/show_bug.cgi?id=462005 --- Comment #22 from Luca Carlon --- Can the fix be backported? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478741] ksystemstats daemon.cpp:32:10: fatal error: 'ksystemstatsadaptor.h' file not found
https://bugs.kde.org/show_bug.cgi?id=478741 Luca Beltrame changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/ksystemstats/-/commit/23 ||d32490d626eee8f7b2115b31146 ||fece21b5517 --- Comment #2 from Luca Beltrame --- Git commit 23d32490d626eee8f7b2115b31146fece21b5517 by Luca Beltrame. Committed on 20/12/2023 at 07:48. Pushed by lbeltrame into branch 'master'. Adjust naming of the generated classes Since the DBus interface file changed, the names of the generated classes also changed. Adjust accordingly. M +2-2src/daemon.cpp https://invent.kde.org/plasma/ksystemstats/-/commit/23d32490d626eee8f7b2115b31146fece21b5517 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457130] Bluetooth Remember Previous Status setting works on reboot, but not shutdown
https://bugs.kde.org/show_bug.cgi?id=457130 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 --- Comment #9 from Luca Beltrame --- I reverted the change and then reinstalled Akonadi. It did not crash, but it did not crash also when I went back again to master... @Robby: Can you try issuing "akonadictl fsck" and see whether this changes anything? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 --- Comment #8 from Luca Beltrame --- I wonder if it's related to 72af8c0b4b20813983a0ee0384ac248e097c4a21. I'll check... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Luca Beltrame changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org --- Comment #6 from Luca Beltrame --- The EWS resource fails for me in the same manner, for the record. The backtrace lacks some debug symbols, here's a more complete one: Thread 1 (Thread 0x7fcbac2de180 (LWP 5068)): [KCrash Handler] #4 0x7fcb845536de in attributesToProtocolImpl (ns=false, entity=...) at /usr/src/debug/akonadi-24.01.80git.20231210T222818~b1023dc/src/core/protocolhelper.cpp:93 #5 Akonadi::ProtocolHelper::attributesToProtocol(Akonadi::Item const&, bool) (ns=false, item=...) at /usr/src/debug/akonadi-24.01.80git.20231210T222818~b1023dc/src/core/protocolhelper.cpp:184 #6 Akonadi::ItemCreateJob::doStart() (this=) at /usr/src/debug/akonadi-24.01.80git.20231210T222818~b1023dc/src/core/jobs/itemcreatejob.cpp:158 #7 0x7fcb84559278 in Akonadi::JobPrivate::startQueued() (this=0x7fcba4055a20) at /usr/src/debug/akonadi-24.01.80git.20231210T222818~b1023dc/src/core/jobs/job.cpp:189 #8 0x7fcbc1bcb2ae in QObject::event(QEvent*) () at /lib64/libQt6Core.so.6 #9 0x7fcbc2dc094e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6 #10 0x7fcbc1b878b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #11 0x7fcbc1b87c17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt6Core.so.6 #12 0x7fcbc1dad9e3 in () at /lib64/libQt6Core.so.6 #13 0x7fcbb6861f30 in () at /lib64/libglib-2.0.so.0 #14 0x7fcbb6863b58 in () at /lib64/libglib-2.0.so.0 #15 0x7fcbb686420c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #16 0x7fcbc1dabc6c in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt6Core.so.6 #17 0x7fcbc1b9211b in QEventLoop::exec(QFlags) () at /lib64/libQt6Core.so.6 #18 0x7fcbc1b8bd46 in QCoreApplication::exec() () at /lib64/libQt6Core.so.6 #19 0x5607fa46041d in () #20 0x7fcbc12281b0 in __libc_start_call_main () at /lib64/libc.so.6 #21 0x7fcbc1228279 in __libc_start_main_impl () at /lib64/libc.so.6 #22 0x5607fa4609f5 in () -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477910] New: Cannot unpause VLC after pausing
https://bugs.kde.org/show_bug.cgi?id=477910 Bug ID: 477910 Summary: Cannot unpause VLC after pausing Classification: Applications Product: kdeconnect Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: carlon.l...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY It seems that I cannot unpause VLC after pausing it with kdeconnect. The play/resume button becomes disabled. I found this https://code.videolan.org/videolan/vlc/-/issues/21419, but it seems a bit different. In my case it only happens with kdeconnect, and not with the Plasma controls. It only happens with VLC though. Other media players, like with the Brave browser, do not show the same problem, kdeconnect can resume properly. STEPS TO REPRODUCE 1. Start a video with VLC (version 3.0.20). 2. Select it with kdeconnect. 3. Pause it. OBSERVED RESULT The play/resume button is visible, but it is disabled. EXPECTED RESULT After pausing the video, the play/resume button should be visible and enabled. Pressing it should resume playback. SOFTWARE/OS VERSIONS Linux: 6.6.3 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476666] Widgets based on System Monitor Sensor are all broken out of the box
https://bugs.kde.org/show_bug.cgi?id=47 Luca Beltrame changed: What|Removed |Added CC||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476501] Plasmashell crashes immediately at start
https://bugs.kde.org/show_bug.cgi?id=476501 --- Comment #2 from Luca Carlon --- The problems with pipewire are probably simply related to the fact that I did not configure it in any way. I simply installed it so I could build Plasma 6. I do not need it to work for the moment. Are you saying I built something incorrectly? Or are you saying the problem is in some pipewire library? Cause I do not see anything specifically related to pipewire in the stack trace. I only see the registration of a QQuickItem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476501] New: Plasmashell crashes immediately at start
https://bugs.kde.org/show_bug.cgi?id=476501 Bug ID: 476501 Summary: Plasmashell crashes immediately at start Classification: Plasma Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY Built Plasma 6 with kdesrc-build. Plasmashell immediately crashes. This is what I could get with gdb: #0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:287 #1 0x74b4430e in QMetaObject::indexOfClassInfo(char const*) const () at /usr/lib/libQt6Core.so.6 #2 0x76acc438 in QQmlMetaType::registerType(QQmlPrivate::RegisterType const&) () at /usr/lib/libQt6Qml.so.6 #3 0x76a5bc20 in QQmlPrivate::qmlregister(QQmlPrivate::RegistrationType, void*) () at /usr/lib/libQt6Qml.so.6 #4 0x7fff9405d95b in qmlRegisterType(char const*, int, int, char const*) (qmlName=0x7fff940616fc "PipeWireSourceItem", versionMinor=1, versionMajor=0, uri=0x7fff9c5f6e10 "org.kde.taskmanager") at /usr/include/qt6/QtQml/qqml.h:328 #5 TaskManager::TaskManagerPlugin::registerTypes(char const*) (this=, uri=0x7fff9c5f6e10 "org.kde.taskmanager") at /home/lucadev/kde/src/plasma-workspace/libtaskmanager/declarative/taskmanagerplugin.cpp:37 #6 0x76acdabd in QQmlMetaType::registerPluginTypes(QObject*, QString const&, QString const&, QString const&, QTypeRevision, QList*) () at /usr/lib/libQt6Qml.so.6 #7 0x76af7e03 in () at /usr/lib/libQt6Qml.so.6 #8 0x76aaf168 in QQmlImports::importExtension(QString const&, QTypeRevision, QQmlImportDatabase*, QQmlTypeLoaderQmldirContent const*, QList*) () at /usr/lib/libQt6Qml.so.6 #9 0x76ab9dbd in QQmlImports::addLibraryImport(QQmlImportDatabase*, QString const&, QString const&, QTypeRevision, QString const&, QString const&, QFlags, unsigned short, QList*) () at /usr/lib/libQt6Qml.so.6 #10 0x76b4c814 in () at /usr/lib/libQt6Qml.so.6 #11 0x76b49d66 in QQmlTypeLoader::Blob::addLibraryImport(std::shared_ptr const&, QList*) () at /usr/lib/libQt6Qml.so.6 #12 0x76b4b379 in QQmlTypeLoader::Blob::addImport(QV4::CompiledData::Import const*, QFlags, QList*) () at /usr/lib/libQt6Qml.so.6 #13 0x76b42071 in () at /usr/lib/libQt6Qml.so.6 #14 0x76b4554a in QQmlTypeLoader::setData(QQmlRefPointer const&, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt6Qml.so.6 #15 0x76b45aa1 in QQmlTypeLoader::setData(QQmlRefPointer const&, QString const&) () at /usr/lib/libQt6Qml.so.6 #16 0x76b486ea in QQmlTypeLoader::loadThread(QQmlRefPointer const&) () at /usr/lib/libQt6Qml.so.6 #17 0x76b4d559 in () at /usr/lib/libQt6Qml.so.6 #18 0x76a54dcb in () at /usr/lib/libQt6Qml.so.6 #19 0x75f7134b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6 #20 0x74b3ba98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6 #21 0x74b3be1b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6 #22 0x74d3dd34 in () at /usr/lib/libQt6Core.so.6 #23 0x73c40f19 in () at /usr/lib/libglib-2.0.so.0 #24 0x73c9f2b7 in () at /usr/lib/libglib-2.0.so.0 #25 0x73c3f112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #26 0x74d3bd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt6Core.so.6 #27 0x74b45953 in QEventLoop::exec(QFlags) () at /usr/lib/libQt6Core.so.6 #28 0x74c2f43f in QThread::run() () at /usr/lib/libQt6Core.so.6 #29 0x74c74932 in () at /usr/lib/libQt6Core.so.6 #30 0x744aa9eb in start_thread (arg=) at pthread_create.c:444 #31 0x7452e7cc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 These are the logs printer by plasmashell: kf.svg: The theme "breath-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.svg: The theme "breath-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.plasma.core: The theme "breath-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. kf.plasma.core: The theme "breath-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format. KPackageStructure of KPluginMetaData(pluginId:"org.kde.kdeconnect", fileName: "/usr/share/plasma/plasmoids/org.kde.kdeconnect/metadata.json") does not match requested format "Plasma/Applet" KPackageStructure of KPluginMetaData
[Discover] [Bug 475429] Discover Crash
https://bugs.kde.org/show_bug.cgi?id=475429 --- Comment #2 from Luca --- Created attachment 162694 --> https://bugs.kde.org/attachment.cgi?id=162694&action=edit New crash information added by DrKonqi plasma-discover (5.27.4) using Qt 5.15.8 prima ho tentato di disinstallare Price; non ci sono riuscito perche il sistema non ha dato il minimo segnale di avviamento di discover; infine ho lanciato discover manualmente, ma da quel momento si blocca -- Backtrace (Reduced): #5 0x7f2bfffc6c00 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so [...] #8 0x7f2c0d8e7de0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2c0f36bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f2c0d8bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2c0d8bdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 475429] Discover Crash
https://bugs.kde.org/show_bug.cgi?id=475429 Luca changed: What|Removed |Added CC||lucavampa.es...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 471979] plasma-systemmonitor: graphical artefacts with nouveau kernel module
https://bugs.kde.org/show_bug.cgi?id=471979 luca changed: What|Removed |Added CC||luca.pedrie...@gmail.com --- Comment #4 from luca --- I can confirm. Same behavior in plasma-nm/speed charts. The system crashes and the only solution is magic SysRq. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #245 from Luca --- (In reply to Aaron Wolf from comment #244) > However, such *front-end* features (which are appropriate to KDE's ethos > IMO) seem like they should be opened for specific front-end use cases. > This ticket here (340982) does seem to be pretty broad and > system-level request to customize Locale overall (which I personally *also* > think should be possible btw). Thank you for clarifying this ticket's topic to me, I obviously misunderstood! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #243 from Luca --- To be honest I don't understand some of the logic in this discussion. Are we really asking that KDE changes system's locales, making up some customized/able version? Personally I don't think so. Several KDE apps provide a kind of TIME INFORMATION. I think we're asking to make this "time information" customizable. As I see it, this doesn't imply any POSIX changes. The system's locales offer several fine-grained variables, like month number or minutes. We're asking that KDE apps allow the users to combine these pieces of time information from the locale in ways that can be convenient for different apps. For instance, I might want the system-tray clock to show "month-day/hour" with particular separators. Or I might want – for whatever reason – Dolphin to display the time-information column about files only with "year-day". It's only natural that different apps, for their very nature, may require different choices and display of time information. And the user may want to customize this even more depending on professional use or whatever. So I don't understand when Nate (https://bugs.kde.org/show_bug.cgi?id=340982#c235) says "However at the moment KDE's developers do in fact want to have KDE's apps play nicely with the world around them." What does "play nicely" mean? I don't think we're asking that KDE apps internally store – or share with other apps – locales in any strange ways. We're asking for customizability of how locales info is combined and displayed. Thunderbird, for example, allows users to display time information in the "Date" column in a user-defined way (https://support.mozilla.org/en-US/kb/customize-date-time-formats-thunderbird). Or, as a different example on the same concept, Emacs let me customize how to display the file-name information, for example displaying "file-name/[last folder in folder tree]". This doesn't mean that Emacs is changing the internal file system. Why is there so much hang-up about "short-date" and "long-date"? Just let me customize which time data from the locales I want displayed on a Dolphin "Modified" column, for instance. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434932] Emoji Selector should enter the selected Emojis directly
https://bugs.kde.org/show_bug.cgi?id=434932 Luca Happel changed: What|Removed |Added CC||lucahappe...@gmx.de --- Comment #9 from Luca Happel --- I am unsure how feasible the following proposal would be: 1. When the emoji-picker starts and we are on Wayland, create a new "virtual keyboard device" [^1] 2. When the user presses on an emoji, the "virtual keyboard device" issues a sequence of key presses which enters the desired emoji [^2] 3. The application exists For this to work, I used the following assumptions: [^1]: There exists such a thing as "virtual keyboard devices". IMO sounds reasonable though, right? [^2]: For all emojis, there exists a sequence of key presses which enters this emoji. For [^2] I suppose pressing ctrl+shift+u+XYZ (where XYZ is the unicode-codepoint(?) of the emoji) should work at least in Firefox for me. I doubt it all applications will work with that tough...🤔 -- You are receiving this mail because: You are watching all bug changes.
[plasma-disks] [Bug 470363] devices, smart state, disk, wrong temperature
https://bugs.kde.org/show_bug.cgi?id=470363 Luca Manganelli changed: What|Removed |Added CC||luc...@gmail.com --- Comment #1 from Luca Manganelli --- Confirming. When I go to see the SMART values, the window is never refreshed. I.e. it states that the my NVME disk temperature is at 84, but the actual is 54... -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 474281] kgapi gets token expired and retries indefinitely
https://bugs.kde.org/show_bug.cgi?id=474281
--- Comment #1 from Luiz Angelo De Luca ---
The PID 13483 is:
/lib/x86_64-linux-gnu/libexec/kf5/kioslave5
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so gdrive
local:/run/user/1000/dolphinKfTdSY.4.kioworker.socket
It didn't stop even after I removed the account. If it helps, after I removed
the account, this is the strace I got from that process (it repeates these
lines):
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, 0) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\2\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd9f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, 0) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\2\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd7f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
fcntl(36, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=124, l_len=1}) =
0
fcntl(36, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=124, l_len=1}) =
0
newfstatat(AT_FDCWD, "/home/luizluca/.local/share/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/plasma/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/plasma/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/gnome/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/gnome/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/local/share/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/local/share/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/usr/share/accounts/services/.service", 0x7fff8e8fd360,
0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/var/lib/snapd/desktop/accounts/services/kde/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/var/lib/snapd/desktop/accounts/services/.service",
0x7fff8e8fd360, 0) = -1 ENOENT (No such file or directory)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, -1) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\1\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd7f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x7fb998d60910, FUTEX_WAKE_PRIVATE, 1) = 1
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x7fff8e8fd000, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, 0) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\3\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd7f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x558d84659f30, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, events=POLLIN},
{fd=33, events=POLLIN}], 4, 0) = 1 ([{fd=11, revents=POLLIN}])
read(11, "\3\0\0\0\0\0\0\0", 8) = 8
read(11, 0x7fff8e8fd7f0, 8) = -1 EAGAIN (Resource temporarily
unavailable)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x7fff8e8fcfe0, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
futex(0x7fff8e8fcfe0, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource
temporarily unavailable)
write(13, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
write(11, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=30, eve
[libkgapi] [Bug 474281] New: kgapi gets token expired and retries indefinitely
https://bugs.kde.org/show_bug.cgi?id=474281 Bug ID: 474281 Summary: kgapi gets token expired and retries indefinitely Classification: Frameworks and Libraries Product: libkgapi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: dvra...@kde.org Reporter: luizl...@gmail.com Target Milestone: --- SUMMARY I noticed that my HDD was emitting a sound in at a specific rate (4/s). Checking logs, I noticed: ... set 07 23:15:44 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. set 07 23:15:45 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. set 07 23:15:45 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. set 07 23:15:45 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. set 07 23:15:45 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. set 07 23:15:46 bob plasmashell[13483]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. ... Besides being annoying, this type of HDD exercise might not help extend its lifetime. After I get Gmail authenticated, it is too easy to get this error. I don't believe google actually expired the token as it might happen even in less than a day. I have already reconfigured the google account dozens of times. STEPS TO REPRODUCE 1. Configure google account 2. Use for a couple of days 3. Check logs OBSERVED RESULT 4. Endless sequence of the same error message EXPECTED RESULT 4. If it is really an expired token, it should desist and ask the user for a new token. However, it might be a different type of error. I don't see google token expire as fast as this. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I'm only using packages from official ubuntu repo. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463126] Many bells with sound notification slows terminal
https://bugs.kde.org/show_bug.cgi?id=463126 --- Comment #3 from Luiz Angelo De Luca --- (In reply to Kurt Hindenburg from comment #2) > Currently Konsole sends a notification every 500ms. Perhaps that needs > increased at the minimum. That does not seem to be what I experience. I almost hear a constant noise (about 700 bpm or less than 0.01s), even getting faster (about 1500 bpm) when I open the Audio panel in traybar. The main issue is not the noise but the fact that it hangs the main thread. It should not freeze the GUI because there are a large queue of notifications. It should simply discard them (maybe with a follow-up notification saying it missed some notifications like kernel does). I still don't know why it bells (a lot) when I paste a large file. It is just text, with more data. Maybe the large paste warning dialog is related? As a workaround, you can speed up things enabling the "Do not disturb" mode from notification panel in the tray icon (you may need to do it twice). Muting the app is not enough. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473646] New: Plasma crashed immediately after first login after bootup
https://bugs.kde.org/show_bug.cgi?id=473646 Bug ID: 473646 Summary: Plasma crashed immediately after first login after bootup Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: luca.coron...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.7) (Compiled from sources) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.11-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: Nothing else, simply crashed on startup and restart itself automatically The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1927 (plasmashell) UID: 1000 (luca) GID: 1000 (luca) Signal: 11 (SEGV) Timestamp: Tue 2023-08-22 18:51:55 CEST (58min ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (luca) Boot ID: 5e696f3cd7ae45e38863d73d4502c3b0 Machine ID: 57ccdfbccb3541f8822c4d2be34665bf Hostname: PC-LUCA Storage: /var/lib/systemd/coredump/core.plasmashell.1000.5e696f3cd7ae45e38863d73d4502c3b0.1927.169272311500.zst (present) Size on Disk: 18.4M Message: Process 1927 (plasmashell) of user 1000 dumped core. Stack trace of thread 1927: #0 0x7f7d91097308 pthread_sigmask@GLIBC_2.2.5 (libc.so.6 + 0x97308) #1 0x7f7d9103f40d sigprocmask (libc.so.6 + 0x3f40d) #2 0x7f7d93caf8db _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x58db) #3 0x7f7d93cb1d93 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d93) #4 0x7f7d9103f1f0 __restore_rt (libc.so.6 + 0x3f1f0) #5 0x7f7d91aed4e0 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed4e0) #6 0x7f7d385e6c64 n/a (libtrianglemousefilterplugin.so + 0x6c64) #7 0x7f7d385e7487 n/a (libtrianglemousefilterplugin.so + 0x7487) #8 0x7f7d91b25812 n/a (libQt5Core.so.5 + 0x325812) #9 0x7f7d91b295ea _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x3295ea) #10 0x7f7d91b1922b _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x31922b) #11 0x7f7d927a519e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1a519e) #12 0x7f7d91aed568 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed568) #13 0x7f7d91b45899 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x345899) #14 0x7f7d91b4617c n/a (libQt5Core.so.5 + 0x34617c) #15 0x7f7d905379b8 g_main_context_dispatch (libglib-2.0.so.0 + 0x5d9b8) #16 0x7f7d90537dc8 n/a (libglib-2.0.so.0 + 0x5ddc8) #17 0x7f7d90537e5c g_main_context_iteration (libglib-2.0.so.0 + 0x5de5c) #18 0x7f7d91b464a6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3464a6) #19 0x7f7d91aebffb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ebffb) #20 0x7f7d91af4490 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2f4490) #21 0x556dce814a91 n/a (plasmashell + 0x29a91) #22 0x7f7d910281f0 __libc_start_call_main (libc.so.6 + 0x281f0) #23 0x7f7d910282b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x282b9) #24 0x556dce814e25 n/a (plasmashell + 0x29e25) Stack trace of thread 1950: #0 0x7f7d9108c54e __futex_abstimed_wait_common (libc.so.6 + 0x8c54e) #1 0x7f7d9108f290 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8f290) #2 0x7f7d856c7f2b n/a (radeonsi_dri.so + 0xc7f2b) #3 0x7f7d8577 n/a (radeonsi_dri.so + 0x17) #4 0x7f7d9108ffa4 start_thread (libc.so.6 + 0x8ffa4) #5 0x7f7d911187fc __clone3 (libc.so.6 + 0x1187fc) Stack trace of thread 1959: #0 0x7f7d9108c54e __futex_abstimed_w
[plasma-browser-integration] [Bug 473015] New: Google chat call does not stop ringing when kde plasma integration is enabled
https://bugs.kde.org/show_bug.cgi?id=473015 Bug ID: 473015 Summary: Google chat call does not stop ringing when kde plasma integration is enabled Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: luizl...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Enable plasma integration in a google-chrome 2. open chat.google.com 3. call any contact OBSERVED RESULT 4. No matter what happens (hang up, answer, cancel), the ringing sound keeps going forever EXPECTED RESULT 4. The ringing should stop SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed 20230801 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Google chrome 115.0.5790.110 -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 472020] New: Missing features for certain tablets
https://bugs.kde.org/show_bug.cgi?id=472020 Bug ID: 472020 Summary: Missing features for certain tablets Classification: Plasma Product: wacomtablet Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: lucamilo123...@gmail.com Target Milestone: --- SUMMARY Some tablets, such as huion ones, in the left-hand mode mirror the screen (so that the connector is not in between the tablet and your arm) but not pen input. This last thing is done manually by checking an option in the software (by rotating the input by 180°). In the official windows huion drivers and in OpenTabletDriver the feature to rotate the input is present, but in KDE is not. This makes the tablet unusable by left-handed people. Please add the option to also rotate the pen input! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471085] Date Format for de_DE.UTF8 should follow the German Standard DIN 5008:2020-03
https://bugs.kde.org/show_bug.cgi?id=471085 Luca changed: What|Removed |Added CC||pg...@duralexnonlex.org --- Comment #3 from Luca --- (In reply to Tobias Fella from comment #1) > DD.MM. is significantly more common in germany than -MM-DD and we Verifiable statistics, please. Otherwise I can just say the exact opposite. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 --- Comment #24 from Luca Manganelli --- (In reply to Sergey Popov from comment #23) > OMG, never thought that Docker would be culprit here! > I confirm that issue is no longer persist after stopping Docker daemon. > Thank you! At least we have workaround for now... For curiosity, what docker container are you using? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 --- Comment #22 from Luca Manganelli --- Created attachment 159472 --> https://bugs.kde.org/attachment.cgi?id=159472&action=edit Video demonstrating the bug with Docker Hi, I've attached a video showing the bug and how stopping docker, it disappears -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 --- Comment #21 from Luca Manganelli --- I think I finally found the cause of this bug! I have Docker that generates continuously (ever second) a file called /tmp/runc-* and deletes it. This prevents the editing ability on the location bar. Stoppoing Docker fixes this problem. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 470577] [feature request] 7z additional options
https://bugs.kde.org/show_bug.cgi?id=470577 --- Comment #2 from Luca --- (In reply to 2wxsy58236r3 from comment #1) > Also, even though some distros have switched to the new p7zip fork (which > supports those new compression methods), I wonder whether distros will > eventually switch to the official 7-Zip, since it now also supports Linux. I've seen some discussion on the fedora repos and I think honestly that every distro will eventually switch to the new fork since it includes all the changes included in the official 7-zip Linux tool. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 250790] Support for zpaq
https://bugs.kde.org/show_bug.cgi?id=250790 Luca changed: What|Removed |Added CC||lucamilo123...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 470577] [feature request] 7z additional options
https://bugs.kde.org/show_bug.cgi?id=470577 Luca changed: What|Removed |Added CC||lucamilo123...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 --- Comment #18 from Luca Manganelli --- After updating to Fedora 38 and Dolphin 23.04.1, the problem disappeared. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #261 from Luca Carlon --- I sent a few patches: https://invent.kde.org/utilities/konsole/-/commit/87c895cf9759e64829e7a4b7d117b810a0da4da8 https://invent.kde.org/utilities/konsole/-/commit/d747635ce1f542bd0e3e278f1f1b95b8b462500d https://invent.kde.org/utilities/konsole/-/commit/1f0cefa40815b00c2ba05453f8774ced180ca113 https://invent.kde.org/utilities/konsole/-/commit/fe46ddc09a59141b1c80c4d588df050151dc47a4 with these patches applied, I cannot reproduce the problem anymore in the Konsole terminal view (I can still see horizontal lines elsewhere in Plasma though). Hope this helps. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #260 from Luca Carlon --- Git commit 1f0cefa40815b00c2ba05453f8774ced180ca113 by Luca Carlon. Committed on 09/05/2023 at 21:57. Pushed by hindenburg into branch 'master'. Invalidate a slightly larger area when scheduling a repaint In highdpi with fractional scaling factor some lines appear in the terminal area. This may be the result of areas that should be refreshed with new content that are not included in the invalidated area. This commit increases the invalidated area a bit to ensure the missing area is included. M +21 -13 src/terminalDisplay/TerminalDisplay.cpp M +19 -0src/terminalDisplay/TerminalDisplay.h M +1-0src/terminalDisplay/TerminalPainter.cpp https://invent.kde.org/utilities/konsole/commit/1f0cefa40815b00c2ba05453f8774ced180ca113 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422265] 1px wide notification
https://bugs.kde.org/show_bug.cgi?id=422265 Luca Weiss changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Luca Weiss --- I don't recall seeing this for a long time so I will assume it was fixed at some point. Also been using the Wayland session for like a year now but I think that was later. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #258 from Luca Carlon --- This is another related patch for the underline: https://invent.kde.org/utilities/konsole/-/merge_requests/843. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #257 from Luca Carlon --- I can still see the horizontal lines. Is my configuration not sufficiently up to date? Konsole 22.12.3 Plasma: 5.27.4 Qt: 5.15.8 Wayland I also tried Konsole master with the same result. This issue is pretty frequent with fractional scaling, so I took 5 minutes to apply a quick patch: https://invent.kde.org/lcarlon/konsole/-/commit/eb11d4fd92996f92d9b37e997f74ec7ac08c25fa. I'm unable to reproduce the issue with it so far. That is clearly not fixing the bug, it is fixing the result though. Please note that, even with my patch, I could reproduce a slight issue with underlined font. I had a look and, from what I understand, that may have a different cause. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #32 from Luca Bacci --- Alright! May I ask how did you set the DPI value for Qt / Plasma applications? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #30 from Luca Bacci --- Ok, things look good there. Can you also have a look in System Settings > Appearance > Fonts > Force Font DPI. Is that set to 96 DPI or some other value? Luca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466463] Different scaling on HiDpi display for applications in 5.27.1
https://bugs.kde.org/show_bug.cgi?id=466463 --- Comment #28 from Luca Bacci --- Hello, Michal! Is it on a Wayland session or X11 session? Can you post the output of: dump_xsettings ps aux | grep -iE 'xsettings|kded' Also, what scaling settings do you have in System Settings > Display and Monitor Thank you, Luca -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 --- Comment #4 from Luca Carlon --- (In reply to Nate Graham from comment #3) > Are you using a fractional scale factor, by any chance? I'm sorry, I forgot the obvious detail: fractional scaling set to 1.5 in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467259] autoconnecting to captive portal enabled network makes session unuseable
https://bugs.kde.org/show_bug.cgi?id=467259 --- Comment #5 from Luca Mignatti --- I got this bug again, however i was unable to open a terminal window as none of the plasma stuff worked. attempting to kill plasmashell in a tty did not work as plasmashell was not running. i loaded an x11 session for the first time on this computor and added konsole to autostart so i could not have this issue, but it now no longer happens. it also did not happen when i loaded the x11 session. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Luca Carlon changed: What|Removed |Added Attachment #157756|VLC looks reasonable. |vlc.png description|| -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Luca Carlon changed: What|Removed |Added Attachment #157755|Different look of the |konversation.png description|outline on two sides of a | |window. | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 --- Comment #2 from Luca Carlon --- Created attachment 157757 --> https://bugs.kde.org/attachment.cgi?id=157757&action=edit settings.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 --- Comment #1 from Luca Carlon --- Created attachment 157756 --> https://bugs.kde.org/attachment.cgi?id=157756&action=edit VLC looks reasonable. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468020] New: Window outline inconsistent between windows and sides of the same window and mispositioned
https://bugs.kde.org/show_bug.cgi?id=468020 Bug ID: 468020 Summary: Window outline inconsistent between windows and sides of the same window and mispositioned Classification: Plasma Product: Breeze Version: 5.27.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Created attachment 157755 --> https://bugs.kde.org/attachment.cgi?id=157755&action=edit Different look of the outline on two sides of a window. SUMMARY The new outline feature in 5.27 may be appreciated or not, but I would like to point out a couple of things that made me think that it was a bug at first. I attached a few images to show what I see. If you zoom in a lot you'll clearly see the problems. 1. konversation.png: this image shows the bottom left corner of konversation. As you can see the left border has an outline, the bottom border does not seem to have the outline. The result is bad and seems buggy. 2. vlc.png: in this image, the outline looks identical on all sides. This does not seem buggy. 3. settings.png: the outline on the left and at the top is not contiguous to the window. There is a transparent line between the window and the outline. I do not clearly understand if this is expected, I do not think so, but in any case it does not seem to be consistent with what I see in other windows (like in vlc.png), and it is not even consistent with the outline at the bottom. This can also be seen in konversation.png. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Outline is missing or mispositioned, inconsistent between different windows and even between sides of the same window. EXPECTED RESULT I am not sure what the expected result was. According to some images I saw online, like these https://invent.kde.org/plasma/breeze/uploads/2eeb591d95a296adfa2daee4a985351e/Screenshot_20230302_181452.png, I guess there shouldn't be a transparent line and the outline should be identical on all sides. I'd also expect it to be identical for all windows. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Linux: 6.1.21-1-MANJARO (64-bit) Wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 Luca Bacci changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kscreen/commit/8f5fc7400 ||65e38dd37cbd966a5abebfaecca ||a495 --- Comment #9 from Luca Bacci --- Git commit 8f5fc740065e38dd37cbd966a5abebfaeccaa495 by Luca Bacci. Committed on 26/03/2023 at 10:18. Pushed by davidedmundson into branch 'master'. OSD: Do not connect to member QObject's destroyed signal We're keeping a strong reference to it M +0-1osd/osd.cpp https://invent.kde.org/plasma/kscreen/commit/8f5fc740065e38dd37cbd966a5abebfaeccaa495 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464824] GTK don't follow global font configuration
https://bugs.kde.org/show_bug.cgi?id=464824 --- Comment #17 from Luca Bacci --- > By the way, in the case of vscode, even if you configure a non-default font, > there are still parts of the interface which use the default GTK font, which > up to a few months ago (in debian at least) would have corresponded with the > KDE configuration. Indeed, that should work! (and does work, here) Can you check if XSettingsd and / or KDED are running? Open a terminal and post the output of: ps aux | grep -Ei 'xsettingsd|kded' Thanks! Luca -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 --- Comment #7 from Luca Bacci --- Observing the member output object for destruction was done as part of https://invent.kde.org/plasma/kscreen/-/commit/071282f545, which sends to https://phabricator.kde.org/D9414 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466914] Kded5 crash when switchin between monitor and tv
https://bugs.kde.org/show_bug.cgi?id=466914 --- Comment #6 from Luca Bacci --- Thanks for the report, Bucior! Seems to be a different issue according to the stacktrace, most probably in KScreen. The stacktrace is very useful! :) KScreen::Osd keeps a reference to a LibKScreen::Output. When Osd instances are destroyed, their references to LibKScreen::Output instances are dropped, and that can cause their immediate destruction. Osd also subscribes as an observeer for its member LibKScreen::Output's destruction: https://invent.kde.org/plasma/kscreen/-/blob/v5.27.2/osd/osd.cpp#L33. The handler method is Osd::hideOsd() is executed, but at that time Osd is already in the process of being destructed... As for fixes, we may ::disconnect() in Osd's destructor. However I don't get why Osd observes its member object for destruction if it keeps a reference to it? -- You are receiving this mail because: You are watching all bug changes.
