[neon] [Bug 449049] New: Default resolution should not be set to the highest resolution available
https://bugs.kde.org/show_bug.cgi?id=449049 Bug ID: 449049 Summary: Default resolution should not be set to the highest resolution available Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: loudsq...@tutanota.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I've been using the LiveUSB on a few different machines in order to resize partitions and I've noticed that it defaults to the highest resolution available. My laptop is 3200x1800 and my HTPC is 4096x2160 both of these resolutions make the text too small to read. It's a pain having to set these back to something human readable like 1920x1080 every single time I boot up the LiveUSB. I think it's awesome that out of the box KDE can apply super high resolutions but it's more of a hindrance than a help. Is it possible to have set the resolution to a readable default and allow the user to change it if they want it higher? Defaulting to the highest isn't the best. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449050] New: System settings flickering when quickly moving mouse cursor over the window
https://bugs.kde.org/show_bug.cgi?id=449050 Bug ID: 449050 Summary: System settings flickering when quickly moving mouse cursor over the window Product: systemsettings Version: 5.23.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrea.i...@gmail.com Target Milestone: --- SUMMARY As per title. This seems to affect System settings only, as I have yet to encounter this behavior in other KDE apps. Video attached. I am using openSuse Tumbleweed with Wayland and pipewire (I thought pipewire was sth for audio only, but once I saw it showing up in OBS Studio for video capture, I'm no longer sure, hence I'm mentioning it). I am using a custom font (Poppins) instead of the default, and scaling at 200%. STEPS TO REPRODUCE 1. open System Settings (Wayland session) 2. Go to any appearance category and quickly move the mouse cursor back and forth over the available options (e.g. in the Colors section move over the previous quickly and for a few seconds. Also happens often when hovering over Global Theme previews). Also in Fonts it's visible. OBSERVED RESULT no UI flickering EXPECTED RESULT UI flickering - check video attached. See how all the UI widgets in the Fonts panel are "refreshed" causing flickering (including the "Fonts" title in the header section). Same goes for Colors (2nd part of the video) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449050] System settings flickering when quickly moving mouse cursor over the window
https://bugs.kde.org/show_bug.cgi?id=449050 --- Comment #1 from andrea.i...@gmail.com --- Sorry, I dunno how to edit. ADDITIONAL INFORMATION Could not reproduce on X11. Could not reproduce on Kubuntu 21.10 live media (logged out of the default X11 session and logged in to a Wayland one - works fine) --> Kubuntu doesn't seem to apply scaling on neither X11 or Wayland sessions - wonder if scaling somehow plays a role in this issue Could reproduce on fedora 35 KDE live media (logs into Wayland by default). --> fedora auto scales to 200% I think when starting the live media Could reproduce on my openSuse Tumbleweed install by booting read-only snapshot of 18Jan (although I think that it's still on KDE 5.23.5) I wonder if this is somehow related to a recent version of Qt? On the other hand, I haven't encountered this issue on any other KDE apps, so far. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 85624] idea: "web scraping" support (support script output as feed source)
https://bugs.kde.org/show_bug.cgi?id=85624 Alberto Cavalin changed: What|Removed |Added CC||steelgunbl...@yahoo.it --- Comment #8 from Alberto Cavalin --- Thank you, but in the meantime I managed to wrote my own feed aggregator with full scraping support :-D If someone is interested here it is: https://github.com/acavalin/rrss -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 449054] New: Should file checking be an option in GRUB instead of the default boot?
https://bugs.kde.org/show_bug.cgi?id=449054 Bug ID: 449054 Summary: Should file checking be an option in GRUB instead of the default boot? Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: loudsq...@tutanota.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I use the LiveUSB quite often it's a fantastic tool for troubleshooting and diagnostics. However each time I'm prompted to do a file check. Cancelling the file check allows the LiveUSB to boot faster and it's never come up with any problems. I understand the usefulness of having a file check but does it need to run every single time? I would image that it should be an option if your LiveUSB fails to boot in GRUB but by default the LiveUSB should attempt to boot without it. I'm considering this from a first impressions type-of-view. Without the check it boots in seconds which is really impressive for a first-time user. Also for troubleshooting purposes you may be rebooting multiple times and having to skip it is annoying. I know the LiveUSB works so running the file check every boot is pointless and I'd like the option to just boot normally. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 449052] New: KWave crashes/locks up When trying to "record" speech from USB headset. Software says unsupported recording method (0)
https://bugs.kde.org/show_bug.cgi?id=449052
Bug ID: 449052
Summary: KWave crashes/locks up When trying to "record" speech
from USB headset. Software says unsupported recording
method (0)
Product: kwave
Version: 21.12.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: thomas.eschenbac...@gmx.de
Reporter: wb7odyf...@yahoo.com
Target Milestone: ---
Created attachment 145839
--> https://bugs.kde.org/attachment.cgi?id=145839=edit
Just an error mesage that says it can not find the encoder. This must be from
NOT selecting settings before pressing record??
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
from a Logitech H390 USB headphone with stereo headphones and stereo mike.
Using Sound volume to set configuration to mono audio record.
STEPS TO REPRODUCE
1. Menu --> Multimedia --> Kwave comes up as application with buttons
"File", "Record" , "Settings", "Help"
2. Hit the Record button. The app locks up, and freezes the 2 windows. 1 in
front, and 1 behind. Click the upper right
hand close button to regain control.
3.
OBSERVED RESULT
The application locks up until, you hit the upper right close button, several
times. Then answer, "terminate application"
I realize now, that You have to select a FILE first, set the source settings,
before hitting the record button.
EXPECTED RESULT
First time use of Kwave. After trying "gnome sound recorder". Hit record
"first time" before setting up a filename.
Kwave: Set up a file name and source settings before hitting record for the
"first" time. Internal Kwave should check if filename exists, or NO FILENAME
entered and print error message and other variables are set before , executing
the "record" function to save the sound into a file.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Manjaro Linux
(available in About System)
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
kwave
This is kwave v21.12.1 (compiled with KDE Frameworks 5.89.0)
Benchmarking memcpy methods (smaller is better):
libc : 42028108
linux kernel : 26678089
MMX : 31107491
MMXEXT : 51619633
SSE : 47768481
AVX : 47092468
using -> 'linux kernel'
uname -a inux kliktel-pc 5.10.93-1-MANJARO #1 SMP PREEMPT Thu Jan 20 09:46:07
UTC 2022 x86_64 GNU/Linux
codec_ascii 2.3 written by Thomas Eschenbacher
codec_audiofile 2.3 written by Thomas Eschenbacher
sonagram 2.3 written by Thomas Eschenbacher
newsignal 2.3 written by Thomas Eschenbacher
saveblocks 2.4 written by Thomas Eschenbacher
normalize 2.3 written by Thomas Eschenbacher
about 2.3 written by Ralf Waspe & Gilles Caulier
reverse 2.3 written by Thomas Eschenbacher
samplerate 2.3 written by Thomas Eschenbacher
stringenter 2.3 written by Thomas Eschenbacher
goto 2.3 written by Thomas Eschenbacher
record 2.6 written by Thomas Eschenbacher
fileinfo 2.3 written by Thomas Eschenbacher
codec_wav 2.3 written by Thomas Eschenbacher
noise 2.3 written by Thomas Eschenbacher
notch_filter 2.3 written by Dave Flogeras
lowpass 2.3 written by Thomas Eschenbacher
codec_mp3 2.3 written by Thomas Eschenbacher
amplifyfree 2.3 written by Thomas Eschenbacher
selectrange 2.3 written by Thomas Eschenbacher
codec_flac 2.3 written by Thomas Eschenbacher
export_k3b 2.3 written by Thomas Eschenbacher
codec_ogg 2.3 written by Thomas Eschenbacher
insert_at 2.3 written by Thomas Eschenbacher
playback 2.4 written by Thomas Eschenbacher
zero 2.3 written by Thomas Eschenbacher
band_pass 2.3 written by Dave Flogeras
pitch_shift 2.3 written by Thomas Eschenbacher
debug 2.3 written by Thomas Eschenbacher
volume 2.3 written by Thomas Eschenbacher
---
found 30 plugins
# plugin:setup(record)
RecordPlugin::setup()
kf.i18n: "0 instead of 1 arguments to message {%1 samples} supplied before
conversion."
RecordPlugin::setMethod(0)
unsupported recording method (0)
unsupported recording method (1)
unsupported recording method - trying next (2)
RecordPlugin::setDevice('')
RecordPlugin::setDevice() -> fallback to 'alsa_input.hw_0_0|sound_note'
RecordPlugin::setDevice('alsa_input.hw_0_0|sound_note')
Killed
Operating System: Manjaro Linux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.10.93-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 kortra...@gmail.com changed: What|Removed |Added CC||kortra...@gmail.com --- Comment #28 from kortra...@gmail.com --- Same issue: Garuda linux. Added more screenshots for verification. System informations: Monitor size: 1920x1080 Operating System: Garuda Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-zen1-1-zen (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #29 from kortra...@gmail.com --- Created attachment 145842 --> https://bugs.kde.org/attachment.cgi?id=145842=edit Sizzling hot corners (Way too big) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447650] Eraser part of the pen for Wacom Cintiq 16 does not work, had to go back to Krita 4.4.5
https://bugs.kde.org/show_bug.cgi?id=447650 Know Zero changed: What|Removed |Added CC||knowz...@pokemail.net --- Comment #2 from Know Zero --- I can confirm this bug on my old Wacom Graphics with both KDE OpenSuse and Linux Mint. Krita 4.4.8 appimage works, but 5.0.2 does not. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447868] krita crashing from opening pop-up palette due to a C++ exception handling exception
https://bugs.kde.org/show_bug.cgi?id=447868 Alvin Wong changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/45c009358 |hics/krita/commit/1a8161714 |1ccc7c5cef9a15103cb8e65b96e |e9a3c746f6faae312fdfd2f0d03 |67de|2152 --- Comment #10 from Alvin Wong --- Git commit 1a8161714e9a3c746f6faae312fdfd2f0d032152 by Alvin Wong. Committed on 24/01/2022 at 08:23. Pushed by alvinwong into branch 'krita/5.0'. Fix blocking SmallColorSelector on OpenGL 2.1, possibly other errors (cherry picked from commit 45c0093581ccc7c5cef9a15103cb8e65b96e67de) M +0-2libs/ui/opengl/kis_opengl.cpp https://invent.kde.org/graphics/krita/commit/1a8161714e9a3c746f6faae312fdfd2f0d032152 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447868] krita crashing from opening pop-up palette due to a C++ exception handling exception
https://bugs.kde.org/show_bug.cgi?id=447868 Alvin Wong changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/45c009358 ||1ccc7c5cef9a15103cb8e65b96e ||67de --- Comment #9 from Alvin Wong --- Git commit 45c0093581ccc7c5cef9a15103cb8e65b96e67de by Alvin Wong. Committed on 23/01/2022 at 17:05. Pushed by alvinwong into branch 'master'. Fix blocking SmallColorSelector on OpenGL 2.1, possibly other errors M +0-2libs/ui/opengl/kis_opengl.cpp https://invent.kde.org/graphics/krita/commit/45c0093581ccc7c5cef9a15103cb8e65b96e67de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 375529] Indentation broken if automatic brackets is used
https://bugs.kde.org/show_bug.cgi?id=375529 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/267 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 367966] [PATCH] Auto bracket on if statements not indenting properly
https://bugs.kde.org/show_bug.cgi?id=367966 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #10 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/267 -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 449052] KWave crashes/locks up When trying to "record" speech from USB headset. Software says unsupported recording method (0)
https://bugs.kde.org/show_bug.cgi?id=449052 Fred Finster changed: What|Removed |Added CC||wb7odyf...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Unable to use scrollwheel on desktop to change Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=419867 --- Comment #59 from Reziac --- More info: Have Bug: These are all within a minor revision of the same version. PCLinuxOS, Fedora, Mageia KDE Plasma version 5.23.5 kernel 5.15.14 Does not have Bug: Debian KDE Plasma version 5.14.5 (apparently borrowed from Mageia) kernel 4.19.1-10 All tell me they're up-to-date. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 448782] I cannot unpack file into NTFS file system
https://bugs.kde.org/show_bug.cgi?id=448782 --- Comment #4 from ironman...@naver.com --- Created attachment 145838 --> https://bugs.kde.org/attachment.cgi?id=145838=edit my hardware info It should contain all the information needed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #33 from Aleksey Zagorodnikov --- Hi folks, I don't know is it make sense for investigation, but for my curiosity I was tried to research it myself. I've using desktop Intel UHD630 with two monitors, primary on DP and secondary on HDMI. And on my setup I need often to effectively unplug-plug DP monitor via KVM switch, while HDMI connected permanently, so I experiencing this kind of bugs a lot during work. Maybe this bug related to "Primary Monitor" feature? If I remove Q_EMIT primaryOutputChanged(primary); in Platform::setPrimaryOutput I can switch monitor back and forth and plasmashell doesn't loose containment on secondary monitor. I've spot another strange behavior with Primary Monitor feature and commented this https://invent.kde.org/plasma/kwin/-/commit/f91ae3e97584767d273479c4013a43e279d77f40#note_383499 but not really sure is it related or not. PS: A bit off-topic, but can we introduce settings for ignoring hot-plug events from monitors? I actually can use wayland only after removing updateOutputs from DrmBackend::handleUdevEvent, otherwise after switching KVM back and forth some windows on desktop changes their positions, a bit annoying. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406602] Crash with using QML open dialog
https://bugs.kde.org/show_bug.cgi?id=406602 Alvin Wong changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Alvin Wong --- Now I cannot reproduce it on 5.0.2, but I tried 4.2.0 again and it is still reproducible there, so I think it can be considered fixed now, probably by newer version of Qt. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449053] Disks and devices: Wrong size if added as standalone applet to top bar
https://bugs.kde.org/show_bug.cgi?id=449053 --- Comment #1 from kortra...@gmail.com --- Created attachment 145841 --> https://bugs.kde.org/attachment.cgi?id=145841=edit Correct size for disks and devices applet. This occurs when adding it to system tray. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #30 from kortra...@gmail.com --- Created attachment 145843 --> https://bugs.kde.org/attachment.cgi?id=145843=edit >From a fresh garuda install: Way too big! (bug) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 449055] New: Allow the user to erase the disk if the partition contain an OS
https://bugs.kde.org/show_bug.cgi?id=449055 Bug ID: 449055 Summary: Allow the user to erase the disk if the partition contain an OS Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: loudsq...@tutanota.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- When using the Install System program, you have the option to select which disk to install the OS on. The option to erase the disk disappears if an OS is detected on the disk. This may be a feature to prevent accidental wiping, however there should be an 'advanced' checkbox which would give you the option to wipe the disk. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 449058] New: Any downloaded files' names with Japanese characters are considered invalid
https://bugs.kde.org/show_bug.cgi?id=449058 Bug ID: 449058 Summary: Any downloaded files' names with Japanese characters are considered invalid Product: frameworks-kio Version: 5.90.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: eddy...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 145845 --> https://bugs.kde.org/attachment.cgi?id=145845=edit "save as" window when trying to save a file with Japanese characters in the file name. SUMMARY Unable to save files that contain Japanese characters in their file name. This is not only limited to Japanese characters (字,か,ム, ...）but also full width alphabet/numerical characters (１２３ＡＢＣ) used in Japanese writing. Note that there aren't any problems when trying to name files that are already on your system with those characters. STEPS TO REPRODUCE 1. Download a file online that contains any of the aforementioned characters in its file name 2. Attempt to choose a saving location OBSERVED RESULT The "save as" window is greyed with three identical notifications stacked on top of each other stating that the file has an invalid file name. After closing those notifications, the save button is greyed out, making it impossible to save unless the file name is changed. In addition, each time a character in the file name is deleted, a new notification identical to the previous ones pops up. Only if it is renamed without the aforementioned characters can the file be downloaded. EXPECTED RESULT The "save as" window appears and I am free to choose the saving location without changing the file's name. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220122 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.1-1-default (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449050] System settings flickering when quickly moving mouse cursor over the window
https://bugs.kde.org/show_bug.cgi?id=449050 --- Comment #2 from andrea.i...@gmail.com --- (In reply to andrea.ippo from comment #0) > SUMMARY > As per title. > This seems to affect System settings only, as I have yet to encounter this > behavior in other KDE apps. > Video attached. > I am using openSuse Tumbleweed with Wayland and pipewire (I thought pipewire > was sth for audio only, but once I saw it showing up in OBS Studio for video > capture, I'm no longer sure, hence I'm mentioning it). > I am using a custom font (Poppins) instead of the default, and scaling at > 200%. > > STEPS TO REPRODUCE > 1. open System Settings (Wayland session) > 2. Go to any appearance category and quickly move the mouse cursor back and > forth over the available options (e.g. in the Colors section move over the > previous quickly and for a few seconds. Also happens often when hovering > over Global Theme previews). Also in Fonts it's visible. > > OBSERVED RESULT > no UI flickering > > EXPECTED RESULT > UI flickering - check video attached. See how all the UI widgets in the > Fonts panel are "refreshed" causing flickering (including the "Fonts" title > in the header section). Same goes for Colors (2nd part of the video) > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > ADDITIONAL INFORMATION Couldn't upload video as it's too big. Find it here: https://photos.app.goo.gl/j1ddT769mzwGACUX8 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 449051] New: Latte is too late for global menu (follow up of bug 186 applet-window-appmenu)
https://bugs.kde.org/show_bug.cgi?id=449051 Bug ID: 449051 Summary: Latte is too late for global menu (follow up of bug 186 applet-window-appmenu) Product: lattedock Version: 0.10.7 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jannowa...@protonmail.com Target Milestone: --- SUMMARY I don't know what KDE changed in their code but it seems that the KDE applications now check if there is a recipient of global menu export at start of application. This has unfortunate side-effect of applet-window-appmenu applet breaking with KDE applications that are restored (I did not check if GTK based applications work same way) or they start at launch but not from typical auto-start like kwalletmanager5. This seems to stem from fact that restored applications (and kwalletmanager5) seem to start up before KDE auto-start (or they start in different threads thus introducing race condition). What effectively happens is latte starts too latte to give response to application that asks for the availability of menu recipient. Why here (applet-window-menu and Latte) - I don't know where this implementation of KDE appmenu is. STEPS TO REPRODUCE A) 1. Use applet-window-appmenu with latte dock (remove any other recipient) 2. Select restore applications 3. Open Dolphin 4. Restart B) 1. Use applet-window-appmenu with latte dock (remove any other recipient) 2. Select open wallet at start 3. Restart OBSERVED RESULT A) Restored applications don't follow up global menu. B) Wallet manager doesn't follow up global menu. EXPECTED RESULT Applications follow up global menu. TEMPORARY "FIX": restart applications (Wallet Manager need manual SIGINT or SIGTERM) - that however does defeat the point of "restore applications" option. SOFTWARE/OS VERSIONS Linux: Garuda/Arch Linux (current) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90 Qt Version: 5.15.2 (KDE) X11 ADDITIONAL INFORMATION This is follow up of https://github.com/psifidotos/applet-window-appmenu/issues/186 in "applet-window-appmenu". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448874] Clipboard - selecting number of entries to keep in clipboard will crash the entire plasma session
https://bugs.kde.org/show_bug.cgi?id=448874 --- Comment #12 from andrea.i...@gmail.com --- (In reply to Nate Graham from comment #11) > plasma packages are fine to start with, and we can go from there. > > Side note: Even a backtrace with no symbols is more usefu than none at all. > It's not helpful for determining where exactly the bug is, but it can > sometimes be used to identify that the crash is the same as a > previously-reported one. Hello Nate, thanks for the info, I followed opensuse's guide for fetching traces and this is what I could get by doing: gdb /usr/bin/plasmashell Starting program: /usr/bin/plasmashell [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x70de3640 (LWP 4900)] [New Thread 0x7fffe44cf640 (LWP 4902)] [New Thread 0x7fffe3cce640 (LWP 4903)] [New Thread 0x7fffe34cd640 (LWP 4904)] [New Thread 0x7fffe2ccc640 (LWP 4905)] [New Thread 0x7fffe24cb640 (LWP 4906)] [New Thread 0x7fffe1cca640 (LWP 4907)] [New Thread 0x7fffe14c9640 (LWP 4908)] [New Thread 0x7fffe0c74640 (LWP 4909)] [New Thread 0x7fffc3fff640 (LWP 4910)] [Thread 0x7fffe0c74640 (LWP 4909) exited] [Thread 0x7fffc3fff640 (LWP 4910) exited] [New Thread 0x7fffc3fff640 (LWP 4911)] [New Thread 0x7fffe0c74640 (LWP 4912)] [New Thread 0x7fffb7916640 (LWP 4913)] [Thread 0x7fffb7916640 (LWP 4913) exited] [Thread 0x7fffe0c74640 (LWP 4912) exited] [New Thread 0x7fffe0c74640 (LWP 4914)] [New Thread 0x7fffb7916640 (LWP 4915)] [New Thread 0x7fffb6b63640 (LWP 4916)] [New Thread 0x7fffb4877640 (LWP 4917)] [Detaching after fork from child process 4918] [Thread 0x7fffb4877640 (LWP 4917) exited] [New Thread 0x7fffb4877640 (LWP 4920)] [New Thread 0x7fffacb40640 (LWP 4921)] [New Thread 0x7fffa3fff640 (LWP 4922)] [New Thread 0x7fffa14de640 (LWP 4926)] [New Thread 0x7fffa0c8d640 (LWP 4927)] [Thread 0x7fffa14de640 (LWP 4926) exited] [Thread 0x7fffa0c8d640 (LWP 4927) exited] [New Thread 0x7fffa0c8d640 (LWP 4928)] [New Thread 0x7fffa14de640 (LWP 4929)] [New Thread 0x7fffae794640 (LWP 4930)] [New Thread 0x7fffadf93640 (LWP 4931)] [New Thread 0x7fffad792640 (LWP 4932)] [New Thread 0x7fff87fff640 (LWP 4933)] [New Thread 0x7fffb5165640 (LWP 4934)] [Detaching after fork from child process 4935] [New Thread 0x7fff84ffe640 (LWP 4942)] [Detaching after fork from child process 4948] [New Thread 0x7fffaffb8640 (LWP 4950)] [New Thread 0x7fffaf765640 (LWP 4951)] [New Thread 0x7fff6e3ff640 (LWP 4952)] [Detaching after fork from child process 4953] [Detaching after fork from child process 4955] [Detaching after fork from child process 4957] [Thread 0x7fff87fff640 (LWP 4933) exited] [Thread 0x7fffadf93640 (LWP 4931) exited] [Thread 0x7fffa0c8d640 (LWP 4928) exited] [Thread 0x7fffb7916640 (LWP 4915) exited] [Thread 0x7fffad792640 (LWP 4932) exited] [Thread 0x7fffae794640 (LWP 4930) exited] [Thread 0x7fffa14de640 (LWP 4929) exited] [Thread 0x7fffe0c74640 (LWP 4914) exited] [Thread 0x7fff6e3ff640 (LWP 4952) exited] [Thread 0x7fffaf765640 (LWP 4951) exited] [Thread 0x7fffaffb8640 (LWP 4950) exited] [Thread 0x7fff84ffe640 (LWP 4942) exited] [Thread 0x7fffb5165640 (LWP 4934) exited] [Thread 0x7fffa3fff640 (LWP 4922) exited] [Thread 0x7fffacb40640 (LWP 4921) exited] [Thread 0x7fffb4877640 (LWP 4920) exited] [Thread 0x7fffb6b63640 (LWP 4916) exited] [Thread 0x7fffc3fff640 (LWP 4911) exited] [Thread 0x7fffe14c9640 (LWP 4908) exited] [Thread 0x7fffe1cca640 (LWP 4907) exited] [Thread 0x7fffe24cb640 (LWP 4906) exited] [Thread 0x7fffe2ccc640 (LWP 4905) exited] [Thread 0x7fffe34cd640 (LWP 4904) exited] [Thread 0x7fffe44cf640 (LWP 4902) exited] [Thread 0x70de3640 (LWP 4900) exited] [Thread 0x7311a980 (LWP 4891) exited] [Inferior 1 (process 4891) exited with code 01] This last line is logged when plasmashell crashes. It also happens when selecting the number in the Timeout for action popup selection. I feel like this is not useful tho. Please let me know how I can provide logs with a line number, an exception, etc... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449053] New: Disks and devices: Wrong size if added as standalone applet to top bar
https://bugs.kde.org/show_bug.cgi?id=449053 Bug ID: 449053 Summary: Disks and devices: Wrong size if added as standalone applet to top bar Product: plasmashell Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Disks & Devices Assignee: plasma-b...@kde.org Reporter: kortra...@gmail.com Target Milestone: 1.0 Created attachment 145840 --> https://bugs.kde.org/attachment.cgi?id=145840=edit Incorrect size for disks and devices applet. Applet MUST be added by itself for this to happen SUMMARY Kde's "Disks and Devices" applet is the wrong size if added by itself to a top status bar. See screenshots for details. It is the correct size if added via the system tray STEPS TO REPRODUCE 1. Enter top panel edit mode 2. Add widget "disks and devices" 3. Attempt to view connected disks OBSERVED RESULT Size is correct as observed when added via system tray Size is incorrect; text and icons are impossible to read when added by itself EXPECTED RESULT Size is correct as observed when added via system tray System Informations: Operating System: Garuda Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-zen1-1-zen (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 449057] New: [Minor issue] Spectacle sends duplicate notifications after taking a screenshot. Probably an easy fix.
https://bugs.kde.org/show_bug.cgi?id=449057 Bug ID: 449057 Summary: [Minor issue] Spectacle sends duplicate notifications after taking a screenshot. Probably an easy fix. Product: Spectacle Version: 21.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: kortra...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 145844 --> https://bugs.kde.org/attachment.cgi?id=145844=edit Incorrect notifications SUMMARY *** Spectacle sends 2 notifications after taking a screenshot. 1 with a preview (correct) and a duplicate with this message: image "" saved to "". See screenshot for more details. *** STEPS TO REPRODUCE 1. Take a screenshot 2. Observe bug 3. OBSERVED RESULT Duplicate notifications occur EXPECTED RESULT Only the first (correct) notification should appear Operating System: Garuda Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-zen1-1-zen (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449056] New: In system settings, the icon used for "pointing devices" is a graphics tablet, which is unknown to most users
https://bugs.kde.org/show_bug.cgi?id=449056
Bug ID: 449056
Summary: In system settings, the icon used for "pointing
devices" is a graphics tablet, which is unknown to
most users
Product: systemsettings
Version: 5.23.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: mako...@hotmail.com
Target Milestone: ---
SUMMARY
In system settings, the icon used for "pointing devices" ("Périphériques
d'entrée" in french) is a graphics tablet, which is unknown to most users. So
this icon doesn't fullfil its function which is helping the users find what
they are looking for.
A keyboard/mouse icon would be better i think.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-pa] [Bug 440536] Allow playing a stream on multiple outputs
https://bugs.kde.org/show_bug.cgi?id=440536 kortra...@gmail.com changed: What|Removed |Added CC||kortra...@gmail.com --- Comment #7 from kortra...@gmail.com --- This is most likely a problem surrounding pipewire not having support implemented in kde for multi-output devices. KDE DEVS: please see this website. module-combine-sinks is what we are looking for here. It is marked as supported! https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Migrate-PulseAudio#module-combine-sink -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 114417] Use Qt5.15 LTS source code from KDE git collection patch repository to compile AppImage bundle
https://bugs.kde.org/show_bug.cgi?id=114417 --- Comment #8 from caulier.gil...@gmail.com --- Git commit 332ac3bd39e779666eb74348b3690c40c64cce01 by Gilles Caulier. Committed on 24/01/2022 at 09:37. Pushed by cgilles into branch 'master'. prepare libs info dialog to show MANIFEST file contents with all git revisions from upstream code as QT5.15 LTS M +74 -33 core/app/views/utils/componentsinfodlg.cpp M +111 -52 core/libs/dialogs/libsinfodlg.cpp M +6-0core/libs/dialogs/libsinfodlg.h https://invent.kde.org/graphics/digikam/commit/332ac3bd39e779666eb74348b3690c40c64cce01 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 261634] Use Qt6 source code from KDE git repository to compile AppImage bundle
https://bugs.kde.org/show_bug.cgi?id=261634 --- Comment #8 from caulier.gil...@gmail.com --- Git commit 332ac3bd39e779666eb74348b3690c40c64cce01 by Gilles Caulier. Committed on 24/01/2022 at 09:37. Pushed by cgilles into branch 'master'. prepare libs info dialog to show MANIFEST file contents with all git revisions from upstream code as QT5.15 LTS M +74 -33 core/app/views/utils/componentsinfodlg.cpp M +111 -52 core/libs/dialogs/libsinfodlg.cpp M +6-0core/libs/dialogs/libsinfodlg.h https://invent.kde.org/graphics/digikam/commit/332ac3bd39e779666eb74348b3690c40c64cce01 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Corentin Girard changed: What|Removed |Added CC||corentingirard@gmail.co ||m --- Comment #66 from Corentin Girard --- I have the same problems. This one exactly: https://bugs.kde.org/show_bug.cgi?id=442826 And the desktop settings: wallpapers and widgets. Operation System: Manjaro Linux 21.2.2 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449061] New: In adding widgets panel, with the french translation, title and text button are mixed together
https://bugs.kde.org/show_bug.cgi?id=449061 Bug ID: 449061 Summary: In adding widgets panel, with the french translation, title and text button are mixed together Product: plasmashell Version: 5.23.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: mako...@hotmail.com Target Milestone: 1.0 Created attachment 145848 --> https://bugs.kde.org/attachment.cgi?id=145848=edit screenshot SUMMARY In adding widgets panel, with the french translation, title and text button are mixed together (cf screenshot) STEPS TO REPRODUCE 1. Display the adding widgets panel 2. 3. OBSERVED RESULT text are mixed together on the top of the panel EXPECTED RESULT texts are elegantly displayed ;-) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.23.5 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448994] when taskbar is at top, programs don't snap to it (using effect)
https://bugs.kde.org/show_bug.cgi?id=448994 --- Comment #3 from Vlad Zahorodnii --- what's the snap effect? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448943] Night color not enabled auto after log in
https://bugs.kde.org/show_bug.cgi?id=448943 --- Comment #9 from galdera --- Hello Tony, thanks for testing it. Unfortunately I can not reproduce this issue on my system. Using Kubuntu 21,10 5.23.5, night color works as expected in x11. I just need to activated once and it enables automatically depending on the day time. Is set to "sunset to sunrise at current location". Right now is off because the day time but if I "set to "always on" it will warm up the colors automatically. Once I set back "current location is set back off. When I reboot my system works fine, I don't need to activate again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Vlad Zahorodnii --- updating the bug report status to waitingforinfo -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441080] neon unstable asks for password to read smart data of SSD after login to X11
https://bugs.kde.org/show_bug.cgi?id=441080 --- Comment #7 from Kai Uwe Broulik --- Downgrading to 0.8.1 provided by ubunth solved the issue for me however -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Anubhav Kini changed: What|Removed |Added CC||anubhavk...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449043] underline
https://bugs.kde.org/show_bug.cgi?id=449043 Oliver Sander changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- Indeed, I can confirm that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448694] X-Server crashes some time after waking on NVidia card
https://bugs.kde.org/show_bug.cgi?id=448694 Vlad Zahorodnii changed: What|Removed |Added Flags||NVIDIA+ Component|core|compositing -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 449067] New: Sound device is not detected on x11
https://bugs.kde.org/show_bug.cgi?id=449067 Bug ID: 449067 Summary: Sound device is not detected on x11 Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: bugsefor...@gmx.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 145849 --> https://bugs.kde.org/attachment.cgi?id=145849=edit screenshot SUMMARY Sound device of my laptop is detected on Wayland, but it is not on X11. Please see the attached screenshot. STEPS TO REPRODUCE 1. start X11 session 2. click on sound icon in system tray 3. EXPECTED RESULT sound device should be detected SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 444605] Default focus is put on button "Close": hitting ENTER closes the program
https://bugs.kde.org/show_bug.cgi?id=444605 --- Comment #12 from EnzoR --- Window button can be removed and shortcuts redefined. Explicit button is the only guaranteed way of closing it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448981] Delay window placement and audio profile selection after multiple monitor resume from standby mode
https://bugs.kde.org/show_bug.cgi?id=448981 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Vlad Zahorodnii --- With some drivers or hardware, changing the dpms mode results in hotplug events. Making kwin delay processing output changes would be difficult (for example, what should kwin do if a new window shows up while there are unprocessed output changes and the window wants to be placed on a screen which kwin is unaware yet? etc) and it could still result in some windows being mis-placed. Can you report this issue to the developers of the video driver you use please? If it's amd, https://gitlab.freedesktop.org/drm/amd/; if it's intel, https://gitlab.freedesktop.org/drm/intel/; if it's nvidia, you would need to file a bug report on their forum. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447116] kwin crashes after pressing alt-tab twice
https://bugs.kde.org/show_bug.cgi?id=447116 --- Comment #10 from matteomartel...@gmail.com --- (In reply to matteomartelli3 from comment #9) > (In reply to hellmade from comment #5) > > got a work around: > > I went to: System Control / window behavior / App Switcher > > (sorry, just have the german version and hope my translations match) > > > > In Display I deselected the switcher App or chagend it to big symbols and > > the crashing went away. > > I played a bit with this config and found out that the Breeze options do > > crash as well as preview images > > The other options I tested work fine. > > Same issue here and your work around works for me too. > To be more specific I can reproduce the issue with these visualization > effects: Breeze, Grid, Thumbnail Grid, Thumbnails. With the other effects > the Task Switcher works fine. What those effects have in common is that they > display the content of the task window, so I guess the problem is there. > Also, the issue can't be reproduced with the compositor disabled because in > that case those visualization effects just display the task icon instead of > the window content, as the other visualization effects do. My system settings are: Distro: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel version: 5.16.1-arch-1 (64-bit) Graphics: X11, NVIDIA GeForce GTX 1060 with drivers nvidia 495.46 Processors: Intel Core i7-6700K Memory: 16GB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449059] New: USe both port and name when manipulating plasma layouts
https://bugs.kde.org/show_bug.cgi?id=449059 Bug ID: 449059 Summary: USe both port and name when manipulating plasma layouts Product: plasmashell Version: 5.23.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: tomash...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 145846 --> https://bugs.kde.org/attachment.cgi?id=145846=edit Display Configuration uses port and name Recently, a dialog to manage containments when in edit mode was added (more details here: https://bugs.kde.org/show_bug.cgi?id=447044 ) It refers to screens by their port alone. Both Display Configuration and Screen Sharing (see attachments). It would be better if it used name of the monitor when available too. Based on discussion here: https://pointieststick.com/2022/01/21/this-week-in-kde-you-wanted-stability-heres-some-stability/#comment-26112 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449026] When moving a new panel to vertical side, some buttons in Edit Mode toolbar are "out of screen"
https://bugs.kde.org/show_bug.cgi?id=449026 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Radovan Skolnik changed: What|Removed |Added CC||rado...@skolnik.info --- Comment #32 from Radovan Skolnik --- Same for me. Didn't use Contacts but recently Calendar got lost. I can see it Google Groupware in Akonadi Console agent list, nothing in Browser. In Korganizer I can see the Google Groupware in Seetings -> Genral -> Calendars but there is no Google Calendar in calendar view :( -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448216] User friendly names should be used for HDMI/DP devices
https://bugs.kde.org/show_bug.cgi?id=448216 kortra...@gmail.com changed: What|Removed |Added CC||kortra...@gmail.com --- Comment #4 from kortra...@gmail.com --- For some inspiration on this: Windows uses a complicated long name like "Realtek HD audio built in line..." Mac uses the monitor name which I like. I feel like audio outputs should be labelled like this: Examples: Display audio out: HSG1074 Display audio out: Sony TV*00 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445069] Web apps don't open in different windows (Chromium browser)
https://bugs.kde.org/show_bug.cgi?id=445069 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Vlad Zahorodnii --- setting status to waitingforinfo -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449062] New: google groupware - cannot add calendar
https://bugs.kde.org/show_bug.cgi?id=449062 Bug ID: 449062 Summary: google groupware - cannot add calendar Product: korganizer Version: 5.19.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: groupware Assignee: kdepim-b...@kde.org Reporter: gerald.driss...@gmail.com Target Milestone: --- SUMMARY *** I am trying to get my google calendar events in Korganizer, but I am unable to do so with google groupware. After I add the google groupware from settings > calendar > add google groupware > configure I am able to see the calendars and they are selected automatically. But, after I close the window the main settings window shows that it is trying to retrieve the tasks but I don't see any message about calendars. Then It says its ready, but no google calendars are visible in the main korganizer window. *** STEPS TO REPRODUCE 1. Add Google Groupware -> successful 2. It shows all calendars, but when I press ok, the calendars are not retrieved 3. No caledar shows. OBSERVED RESULT I cannot add any google calendar as they are not showing up (despite a successful connection and restart) EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 261634] Use Qt6 source code from KDE git repository to compile AppImage bundle
https://bugs.kde.org/show_bug.cgi?id=261634 --- Comment #9 from caulier.gil...@gmail.com --- Git commit 7613ada0bbe789e44e185e70035445a828778dc3 by Gilles Caulier. Committed on 24/01/2022 at 10:10. Pushed by cgilles into branch 'master'. Add support of MANIFEST.txt file with all git revisions from upstream components Related: bug 114417 M +50 -0core/libs/dialogs/libsinfodlg.cpp https://invent.kde.org/graphics/digikam/commit/7613ada0bbe789e44e185e70035445a828778dc3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 114417] Use Qt5.15 LTS source code from KDE git collection patch repository to compile AppImage bundle
https://bugs.kde.org/show_bug.cgi?id=114417 --- Comment #9 from caulier.gil...@gmail.com --- Git commit 7613ada0bbe789e44e185e70035445a828778dc3 by Gilles Caulier. Committed on 24/01/2022 at 10:10. Pushed by cgilles into branch 'master'. Add support of MANIFEST.txt file with all git revisions from upstream components Related: bug 261634 M +50 -0core/libs/dialogs/libsinfodlg.cpp https://invent.kde.org/graphics/digikam/commit/7613ada0bbe789e44e185e70035445a828778dc3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448994] when taskbar is at top, programs don't snap to it (using effect)
https://bugs.kde.org/show_bug.cgi?id=448994 --- Comment #5 from Vlad Zahorodnii --- Despite its name, that effect doesn't actually snap windows. It only draws a window outline. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 --- Comment #3 from Vlad Zahorodnii --- > The jumping window case only happens in the current testing version of KDE. this should be fixed > The Problem with the jumping mouse pointer first occured mid-2021 if I > remember correctly just to clarify, this bug can't be reproduced on wayland, right? only x11? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 446121] C++ problems with LSP highlighting
https://bugs.kde.org/show_bug.cgi?id=446121 --- Comment #3 from Waqar Ahmed --- > I am a little confused. On the one hand, you say that "Kate has no idea > about the text its editing" > but then you also say "We ignore a lot of > information sent to us by the LSP" and "we do lack a couple of things" and > then even "For some themes I hardcoded the colors". Let me try to clarify. In a more pedantic sense, kate has very little idea about the text its editing. It does know about comments, strings, keywords. This is basic stuff, so any decent syntax highlighter will be able to parse a document and collect this information. But slightly more complex things such as ... a function, or scope, or what kind of a variable do we have are usually not handled and even if they are, the results might not be very accurate. The information we ignore is the things we know for sure we already have => language keywords, comments, strings. This is just for efficiency reasons. The things we lack are - modifier coloring support. LSP can send info about modifiers which you can use to color things differently. - some clangd specific things IIRC > This makes it super-difficult for me to actually figure out if > 1) the LSP is sending the wrong information; or > 2) Kate's handling of the LSP information is wrong; or > 3) The actual *theme* is overwriting something. What I mean is that the colors you will see depend on the theme you are using. If a theme is bad, you will not see good semantic highlighting colors. And *some* themes work better, because more effort was put into those themes to make them look better. > I am aware that Kate's syntax highlighting is a lot older than the LSP code, > and that it might be difficult to create 1-to-1 mappings for > everything, but with LSP being so common nowadays, wouldn't it make sense to > adopt the categories (type, variable...) that LSP uses? It is not that different, and our themes already support the basic semantic highlighting spec pretty well. Some things are missing (for e.g parameter colors) that we can support. So, if a theme doesn't look good, what you can do is modify the colors and see the effect. But it will be a bit annoying to do this with LSP semantic highlighting because you will need to restart Kate to see the newly applied colors for semantic highlighting. If you want to see which themes colors get mapped to what LSP information, check the file semantic_tokens_legend.cpp in the Kate repo. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 441080] neon unstable asks for password to read smart data of SSD after login to X11
https://bugs.kde.org/show_bug.cgi?id=441080 --- Comment #6 from Patrick Silva --- My neon unstable runs sddm 0.19.0+p20.04+tunstable+git20220122.0034-0 and I can't reproduce this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449027] Crash when clicking on application dashboard icon on panel
https://bugs.kde.org/show_bug.cgi?id=449027 --- Comment #2 from Jan Rathmann --- Would it help to make the full coredump avaiable? (37.4M in size) -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 444605] Default focus is put on button "Close": hitting ENTER closes the program
https://bugs.kde.org/show_bug.cgi?id=444605 --- Comment #10 from EnzoR --- Maybe I am wrong, but the "Close" button should stay there. It simply should never get focus automatically: the user is the only one who knows whether the task is over or not. And she/he can communicate this by explicitly clicking on the "Close" button. IMHO, there should be no automatic focus or focus shift. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442846] Blocking calls to Xwayland can make kwin freeze
https://bugs.kde.org/show_bug.cgi?id=442846 Vlad Zahorodnii changed: What|Removed |Added Keywords||wayland Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Summary|Plasma Wayland Freezes upon |Blocking calls to Xwayland |unlocking screen after |can make kwin freeze |leaving laptop with intel | |graphics idle for long time | |when using Firefox in | |XWayland mode | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448694] X-Server crashes some time after waking on NVidia card
https://bugs.kde.org/show_bug.cgi?id=448694 --- Comment #6 from Vlad Zahorodnii --- If Xorg crashes, the issue might be elsewhere. Can you report this issue to Xorg developers please? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448573] Overview effect selection background does not move or scale with window that is being dragged
https://bugs.kde.org/show_bug.cgi?id=448573 Vlad Zahorodnii changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448573] Overview effect selection background does not move or scale with window that is being dragged
https://bugs.kde.org/show_bug.cgi?id=448573 --- Comment #2 from Vlad Zahorodnii --- Yeah, it should disappear. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #7 from Vlad Zahorodnii --- Most likely, kwin overwrites the data it shouldn't. It would be great if you could run kwin with valgrind, but it can make the computer very unusable. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449070] New: Places panel is too wide
https://bugs.kde.org/show_bug.cgi?id=449070 Bug ID: 449070 Summary: Places panel is too wide Product: dolphin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de CC: kfm-de...@kde.org Target Milestone: --- As found by openQA, the places panel is too wide, at least on 1024x768: https://openqa.opensuse.org/tests/2152778#step/dolphin/5 With 21.12, it's smaller: https://openqa.opensuse.org/tests/2152783#step/dolphin/4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449069] Icons on desktop sorted by name, aligned to right side and arranged in columns are sorted from right to left
https://bugs.kde.org/show_bug.cgi?id=449069 --- Comment #1 from Patrick Silva --- Created attachment 145851 --> https://bugs.kde.org/attachment.cgi?id=145851=edit expcted - icons are sorted from left to right -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449026] When moving a new panel to vertical side, some buttons in Edit Mode toolbar are "out of screen"
https://bugs.kde.org/show_bug.cgi?id=449026 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/818 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443294] Using "Screen Edge" to change its position from vertical to horizontal will cause incorrect position of controls
https://bugs.kde.org/show_bug.cgi?id=443294 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/818 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448818] Wayland display image freezes on multi-GPU VA-API usage
https://bugs.kde.org/show_bug.cgi?id=448818 Vlad Zahorodnii changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Vlad Zahorodnii --- Okay, it looks like XR24 and linear modifier are in IN_FORMATS. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Michael D changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #2 from Michael D --- Same issue on Manjaro testing. I've tried removing and adding the calendar to no avail. Calendars don't show in korganizer, kalendar, or the pim plug-in for the digital clock, so it's not really a korganizer bug, but seems an akonadi bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 449071] New: Saving rectangle tool setup in editor
https://bugs.kde.org/show_bug.cgi?id=449071
Bug ID: 449071
Summary: Saving rectangle tool setup in editor
Product: Spectacle
Version: 21.12.1
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: General
Assignee: m...@baloneygeek.com
Reporter: baras...@gmail.com
CC: k...@david-redondo.de
Target Milestone: ---
SUMMARY
It would be nice if all Editor's tools settings (such as Rectangle Color, fill
mode) were saved between sessions.
STEPS TO REPRODUCE
1. Take screenshot
2. Open editor ("add comments...")
3. Choose rectangle tool
4. Change color to Red and mode Only Borders
5. Edit screenshot
6. Save and exit
7. Create new screenshot
8. Open editor
9. Choose rectangle tool
OBSERVED RESULT
Default color and fill mode will be set
EXPECTED RESULT
Color and fill mode are saved from last session
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Maybe some of menu items were wrongly translated - I'm using non-english
version of KDE.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 447116] kwin crashes after pressing alt-tab twice
https://bugs.kde.org/show_bug.cgi?id=447116 matteomartel...@gmail.com changed: What|Removed |Added CC||matteomartel...@gmail.com --- Comment #9 from matteomartel...@gmail.com --- (In reply to hellmade from comment #5) > got a work around: > I went to: System Control / window behavior / App Switcher > (sorry, just have the german version and hope my translations match) > > In Display I deselected the switcher App or chagend it to big symbols and > the crashing went away. > I played a bit with this config and found out that the Breeze options do > crash as well as preview images > The other options I tested work fine. Same issue here and your work around works for me too. To be more specific I can reproduce the issue with these visualization effects: Breeze, Grid, Thumbnail Grid, Thumbnails. With the other effects the Task Switcher works fine. What those effects have in common is that they display the content of the task window, so I guess the problem is there. Also, the issue can't be reproduced with the compositor disabled because in that case those visualization effects just display the task icon instead of the window content, as the other visualization effects do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436555] kmail app (and others) flickering on Nvidia Hardware
https://bugs.kde.org/show_bug.cgi?id=436555 Vlad Zahorodnii changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #15 from Vlad Zahorodnii --- Thanks for the update. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448920] kwin_wayland crashed in KWin::Xwl::WlSource::checkStartTransfer() when I tried to drag a screenshot from Spectacle to Discord
https://bugs.kde.org/show_bug.cgi?id=448920 Vlad Zahorodnii changed: What|Removed |Added Keywords||wayland --- Comment #2 from Vlad Zahorodnii --- It looks like WlSource::m_dsi gets deleted while dnd is active. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449059] USe both port and name when manipulating plasma layouts
https://bugs.kde.org/show_bug.cgi?id=449059 --- Comment #1 from tomash...@gmail.com --- Created attachment 145847 --> https://bugs.kde.org/attachment.cgi?id=145847=edit Screen sharing also uses both -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449060] New: Keyboard shortcut for adding widgets doesn't work
https://bugs.kde.org/show_bug.cgi?id=449060 Bug ID: 449060 Summary: Keyboard shortcut for adding widgets doesn't work Product: plasmashell Version: 5.23.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: mako...@hotmail.com CC: butir...@gmail.com Target Milestone: 1.0 SUMMARY The Alt+D shortcut pour adding plasma widgets do nothing STEPS TO REPRODUCE 1. alt+D OBSERVED RESULT nothing EXPECTED RESULT adding widgets panel appears SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90 Qt Version: 5.13.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442826] After cold boot one of multiple monitors stays black, no menu, no wallpaper, no mouse response
https://bugs.kde.org/show_bug.cgi?id=442826 Corentin Girard changed: What|Removed |Added CC||corentingirard@gmail.co ||m --- Comment #3 from Corentin Girard --- (In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 427861 *** I think this is **not** a duplicate. Bug 427861 is "just" a reset of settings. Your settings go back to default but at least, the desktop works, it has a (default) wallpaper and you can have a context menu when you right-click. Here in this bug, what we call a "zombie" desktop screen is a desktop where the wallpaper is unset (black), without any trace of Plasma Desktop. You can't even right click on the desktop. You can just drag windows on the "zombie" desktop. I'm not even sure the "zombie" desktop loses its settings, we would have to investigate. But it seems to be a temporary glitch because it does that one out of 5 startups. Also, for me it only does that on my second monitor. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439833] LSP-Client does not work
https://bugs.kde.org/show_bug.cgi?id=439833 --- Comment #8 from Hannes --- I am currently not working on REHL7 with the AppImage anymore, but I will try to get access to the machine again to double-check. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429211] Digital clock/whole panel sometimes stops updating until there is user interaction with Plasma
https://bugs.kde.org/show_bug.cgi?id=429211 Jakub changed: What|Removed |Added CC||jaburek.ja...@gmail.com --- Comment #13 from Jakub --- I started to experience a similar issue since a few days ago. The whole taskbar freezes after about an hour after starting the desktop session. No hover effects are displayed, the clock is frozen, opening new applications doesn’t show them in the taskbar and switching workspaces is not reflected on the taskbar. However, I can still click on the taskbar to open the application launcher, switch workspace, open calendar, etc. and it works. But unlike the original report, it does not unfreeze the taskbar, the only solution is to kquitapp5 plasmashell. SYSTEM INFORMATION: Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 Vlad Zahorodnii changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from Vlad Zahorodnii --- Okay, that looks like a different issue, maybe the pointer is warped? Can you file a different bug report to make it easier to track issues. This one (Window jumps to differnet location when dragging it by the menu bar) should be already fixed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449064] New: Program very slow to launch first time; no splash screen or spinning circle
https://bugs.kde.org/show_bug.cgi?id=449064 Bug ID: 449064 Summary: Program very slow to launch first time; no splash screen or spinning circle Product: okular Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: greenandpleasant2000-supp...@yahoo.co.uk Target Milestone: --- SUMMARY *** Okular takes at least 15 seconds to launch first time (from the menu). Subsequent launchings in the same session are OK, however, taking only 2 seconds. This compares very unfavourably with Xreader, say which takes only 3 secs to launch first time from the menu. Another issue is the lack of any splash screen, or spinning circle on the screen. This is especially important when you are launching by double-clicking on a pdf file, say, to tell the user that the double-click has worked. On a good few ocasions I have accidentally launched two verions of Okular or else waited for a program launch that didn't happen because of a "mis-click". SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mint 20.1 / Cinnamon 4.8.6 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449026] When moving a new panel to vertical side, some buttons in Edit Mode toolbar are "out of screen"
https://bugs.kde.org/show_bug.cgi?id=449026 Fushan Wen changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 --- Comment #7 from Philipp Maierhöfer --- Thanks, that was quick! The jumping mouse pointer only occurs on 5.23.5, but is fixed in 5.23.90 (to me it looked like the jumping pointer bug may have evolved into the jumping window bug, hence the historic information). Does it make sense to file a bug that has already been fixed in a newer version (if the old version is not LTS)? But if you say "just do it", I'll do it. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 --- Comment #8 from Vlad Zahorodnii --- Okay, if the issue comes back in 5.24, please file a bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449069] Icons on desktop sorted by name, aligned to right side and arranged in columns are sorted from right to left
https://bugs.kde.org/show_bug.cgi?id=449069 Patrick Silva changed: What|Removed |Added Attachment #145851|expcted - icons are sorted |expected - icons are sorted description|from left to right |from left to right -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449069] Icons on desktop sorted by name and aligned to right side are sorted from right to left
https://bugs.kde.org/show_bug.cgi?id=449069 Patrick Silva changed: What|Removed |Added Summary|Icons on desktop sorted by |Icons on desktop sorted by |name, aligned to right side |name and aligned to right |and arranged in columns are |side are sorted from right |sorted from right to left |to left --- Comment #2 from Patrick Silva --- The same happens if the icons on desktop are arranged in rows. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 446923] Dolphin and file pickers have a 5-10 second lag when first opened
https://bugs.kde.org/show_bug.cgi?id=446923 --- Comment #10 from Mike Lothian --- I've rebuilt kio with debugging to get a better backtrace #0 0x758ef14d in ppoll () from /lib64/libc.so.6 #1 0x75ee5065 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib64/libQt5Core.so.5 #2 0x75e2c2ca in QProcess::waitForFinished(int) () from /usr/lib64/libQt5Core.so.5 #3 0x7778a3bf in KSambaSharePrivate::runProcess (progName=..., args=..., stdOut=..., stdErr=...) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/ksambashare.cpp:112 f46 in KSambaSharePrivate::getNetUserShareInfo (this=0x55f1bfa0) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/ksambashare.cpp:195 #5 0x77789bf7 in KSambaSharePrivate::KSambaSharePrivate (this=0x55f1bfa0, parent=0x7793a0b0 <(anonymous namespace)::Q_QGS__instance::innerFunction()::holder>) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/ksambashare.cpp:54 #6 0x7778d2d1 in KSambaShare::KSambaShare (this=0x7793a0b0 <(anonymous namespace)::Q_QGS__instance::innerFunction()::holder>) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/ksambashare.cpp:479 #7 0x7778e43a in KSambaShareSingleton::KSambaShareSingleton (this=0x7793a0b0 <(anonymous namespace)::Q_QGS__instance::innerFunction()::holder>) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/ksambashare.cpp:556 #8 0x7778d805 in (anonymous namespace)::Q_QGS__instance::Holder::Holder (this=0x7793a0b0 <(anonymous namespace)::Q_QGS__instance::innerFunction()::holder>) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/ksambashare.cpp:562 #9 0x7778d87e in (anonymous namespace)::Q_QGS__instance::innerFunction () at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/ksambashare.cpp:562 #10 0x7778dc04 in QGlobalStatic::operator() (this=0x7793a0d0 <_instance>) at /usr/include/qt5/QtCore/qglobalstatic.h:136 #11 0x7778d8cd in KSambaShare::instance () at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/ksambashare.cpp:566 #12 0x77796bad in KFileItem::overlays (this=0x7fffc458) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/kfileitem.cpp:1172 #13 0x77ee8d94 in KFileItemModelRolesUpdater::rolesData(KFileItem const&) () from /usr/lib64/libdolphinprivate.so.5 #14 0x77eeab42 in KFileItemModelRolesUpdater::applyResolvedRoles(int, KFileItemModelRolesUpdater::ResolveHint) () from /usr/lib64/libdolphinprivate.so.5 #15 0x77eead64 in KFileItemModelRolesUpdater::slotPreviewFailed(KFileItem const&) () from /usr/lib64/libdolphinprivate.so.5 #16 0x75ed2dfb in ?? () from /usr/lib64/libQt5Core.so.5 #17 0x77a8c7c0 in KIO::PreviewJob::failed (this=0x55ed0c90, _t1=...) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0_build/src/widgets/KF5KIOWidgets_autogen/include/moc_previewjob.cpp:205 #18 0x77a87db1 in KIO::PreviewJobPrivate::determineNextFile (this=0x55e4c2f0) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/widgets/previewjob.cpp:534 #19 0x77a88721 in KIO::PreviewJob::slotResult (this=0x55ed0c90, job=0x56016960) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/widgets/previewjob.cpp:637 #20 0x75ed2dfb in ?? () from /usr/lib64/libQt5Core.so.5 #21 0x76fed883 in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib64/libKF5CoreAddons.so.5 #22 0x76ff1c9b in KJob::finishJob(bool) () from /usr/lib64/libKF5CoreAddons.so.5 #23 0x778005ff in KIO::SimpleJob::slotFinished (this=0x56016960) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/simplejob.cpp:233 #24 0x7780d099 in KIO::TransferJob::slotFinished (this=0x56016960) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/transferjob.cpp:158 #25 0x7780073c in KIO::SimpleJob::slotError (this=0x56016960, err=104, errorText=...) at /var/tmp/portage/kde-frameworks/kio-5.90.0/work/kio-5.90.0/src/core/simplejob.cpp:246 #26 0x77803299 in QtPrivate::FunctorCall, QtPrivate::List, void, void (KIO::SimpleJob::*)(int, QString const&)>::call (f= (void (KIO::SimpleJob::*)(KIO::SimpleJob * const, int, const QString &)) 0x77800626 , o=0x56016960, arg=0x7fffcc60) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #27 0x778030c5 in QtPrivate::FunctionPointer::call, void> (f= (void (KIO::SimpleJob::*)(KIO::SimpleJob * const, int, const QString &)) 0x77800626 , o=0x56016960, arg=0x7fffcc60) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #28 0x77802e0f in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x56009460, r=0x56016960, a=0x7fffcc60, ret=0x0) at
[systemsettings] [Bug 448216] User friendly names should be used for HDMI/DP devices
https://bugs.kde.org/show_bug.cgi?id=448216 --- Comment #5 from kortra...@gmail.com --- (In reply to kortrax11 from comment #4) > For some inspiration on this: > Windows uses a complicated long name like "Realtek HD audio built in line..." > Mac uses the monitor name which I like. > > I feel like audio outputs should be labelled like this: > > Examples: Display audio out: HSG1074 > Display audio out: Sony TV*00 Also for built in audio we should name like this Onboard audio: Line out Onboard audio: Digital audio out -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 446121] C++ problems with LSP highlighting
https://bugs.kde.org/show_bug.cgi?id=446121 --- Comment #2 from Hannes --- Thank you for your response, and sorry for my late reply. I am a little confused. On the one hand, you say that "Kate has no idea about the text its editing" but then you also say "We ignore a lot of information sent to us by the LSP" and "we do lack a couple of things" and then even "For some themes I hardcoded the colors". This makes it super-difficult for me to actually figure out if 1) the LSP is sending the wrong information; or 2) Kate's handling of the LSP information is wrong; or 3) The actual *theme* is overwriting something. What is the recommended procedure for me to figure this out? I am aware that Kate's syntax highlighting is a lot older than the LSP code, and that it might be difficult to create 1-to-1 mappings for everything, but with LSP being so common nowadays, wouldn't it make sense to adopt the categories (type, variable...) that LSP uses? Thank you for your help on this! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449047] Fullscreen firefox locks screen refresh
https://bugs.kde.org/show_bug.cgi?id=449047 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|NEEDSINFO Component|compositing |platform-drm Resolution|--- |WAITINGFORINFO --- Comment #3 from Vlad Zahorodnii --- Can you attach the session logs `~/.local/share/sddm/wayland-session.log` after making firefox fullscreen and the output of the following command `qdbus org.kde.KWin /KWin supportInformation` to this bug report please? and do you have a laptop with a discrete gpu? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448994] when taskbar is at top, programs don't snap to it (using effect)
https://bugs.kde.org/show_bug.cgi?id=448994 --- Comment #4 from David Chmelik --- Only one effect name starts with snap, so shouldn't be too hard for you to find. (snap helper) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 449063] New: Screenshot is impossible when context menu is displayed
https://bugs.kde.org/show_bug.cgi?id=449063 Bug ID: 449063 Summary: Screenshot is impossible when context menu is displayed Product: Spectacle Version: 21.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: mako...@hotmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Screenshot is impossible when context menu is displayed STEPS TO REPRODUCE 1. right-click on plasma desktop or in Dolphin 2. tap screenshot key in keyboard OBSERVED RESULT nothing EXPECTED RESULT screenshot is taken with the menu displayed SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.23.5 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449060] Keyboard shortcut for adding widgets doesn't work
https://bugs.kde.org/show_bug.cgi?id=449060 --- Comment #1 from mako...@hotmail.com --- Actually, in plasma context menu,I see that there is 4 actions activated by the alt+D shortcut !! Unfortunately I can't take a screenshot of the menu (I just created a bug report about it). I never changed the default keyboard shortcuts... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448961] Window jumps to differnet location when dragging it by the menu bar
https://bugs.kde.org/show_bug.cgi?id=448961 --- Comment #5 from Philipp Maierhöfer --- Yes, on wayland the problem can't be reproduced. Only on X11. At least according to my tests. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448917] NVIDIA/Wayland - Breeze Theme Has No Blur And Random Shapes Appear
https://bugs.kde.org/show_bug.cgi?id=448917 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #6 from Vlad Zahorodnii --- It looks like a driver issue, the contents of buffers become invalid after closing a window. Can you report this issue to nvidia developers please? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448945] Mouse Mark effect should allow marking shortcut configuration
https://bugs.kde.org/show_bug.cgi?id=448945 Vlad Zahorodnii changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448934] Unusual Cursor behaviour while dragging
https://bugs.kde.org/show_bug.cgi?id=448934 Vlad Zahorodnii changed: What|Removed |Added CC||kfm-de...@kde.org Component|wayland-generic |general Keywords||wayland Version|5.23.90 |unspecified Product|kwin|dolphin Assignee|kwin-bugs-n...@kde.org |dolphin-bugs-n...@kde.org --- Comment #1 from Vlad Zahorodnii --- Moving the bug report to dolphin as it might be updating the cursor. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 449065] New: Show desktop while screen is locked
https://bugs.kde.org/show_bug.cgi?id=449065 Bug ID: 449065 Summary: Show desktop while screen is locked Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: he...@junglenut.net CC: bhus...@gmail.com Target Milestone: --- I have some system resources widgets on my desktop. It would be good if the desktop could be seen even if the screen is locked. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 440066] Remote places not showing label in Places Panel when mounted through terminal
https://bugs.kde.org/show_bug.cgi?id=440066 --- Comment #4 from LapiXo --- (In reply to Nate Graham from comment #1) > Does this affect the file open/save dialogs too? Yes, it does. No happening when using gtk apps using own dialogs. Only with Dolphin. Even installed Thunar to verify. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449066] New: PDF files: first-page thumbnail is missing; only the generic pdf thumbnail is visible
https://bugs.kde.org/show_bug.cgi?id=449066 Bug ID: 449066 Summary: PDF files: first-page thumbnail is missing; only the generic pdf thumbnail is visible Product: okular Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: greenandpleasant2000-supp...@yahoo.co.uk Target Milestone: --- SUMMARY *** After uninstalling Xreader, I installed Okular for the first time on my system. However, now, after this date, any PDF files created by LibreOffice Write fail to show the first-page thumbnail on the pdf file. Existing PDF files, created before the uninstall of Xreader and the install of OKULAR, are not affected. *** STEPS TO REPRODUCE 1. Need to have OKULAR uninstalled and all dependencies, configuration files etc. removed. 2. Install Xreader. 3. In LibreOffice Writer, generate a PDF from a file with a distinctive, large image on the first page (to create an easily-visible first-page thumbnail on the pdf icon). 4. Create a pdf. EXPECTED / OBSERVED RESULT: The PDF should have a thumbnail of the first page clearly visible on it. 5. Uninstall Xreader and install Okular. 6. Now repeat step 3, above. OBSERVED RESULT: The first-page thumbnail does not appear; only the generic PDF thumbnail. EXPECTED RESULT; The first-page thumbnail should be on the first page of the PDF doc. 7. Install Xreader (keep Okular) and repeat step 3. EXPECTED / OBSERVED RESULT: The PDF should have a thumbnail of the book-cover clearly visible on it. *** SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mint 20.1 / Cinnamon 4.8.6 KDE Plasma Version: KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 444605] Default focus is put on button "Close": hitting ENTER closes the program
https://bugs.kde.org/show_bug.cgi?id=444605 --- Comment #11 from Kåre Särs --- This bug is really strange! Me and Alexander, cannot reproduce... I have tested both on Wayland and X11 Are there any Archlinux specific patches? The button removal is mainly to get it more in line with Spectacle's UI. Alt-F4 and Ctrl-Q quits the application and you have the normal close button on the Window, so you might not really need the separate close-button. -- You are receiving this mail because: You are watching all bug changes.
