[lattedock] [Bug 452203] Settings window makes no use of the global menu
https://bugs.kde.org/show_bug.cgi?id=452203 --- Comment #5 from Michail Vourlakos --- no idea why -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 450836] No comets visible in Desktop or find , upgrade comets very short , no effect
https://bugs.kde.org/show_bug.cgi?id=450836 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450858] Add Configuration to Adjust Timeout
https://bugs.kde.org/show_bug.cgi?id=450858 Justin Zobel changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Justin Zobel --- If a user (maybe a corporate user) clicks to reboot their PC but forgets to click the OK button there's 30 seconds for another user to walk up, click cancel and use their session. A shorter timeout would increase security in that scenario. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451213] Uhhh... Speech
https://bugs.kde.org/show_bug.cgi?id=451213 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450858] Add Configuration to Adjust Timeout
https://bugs.kde.org/show_bug.cgi?id=450858 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450782] Plasma crashes when using global menu search in system settings
https://bugs.kde.org/show_bug.cgi?id=450782 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 450774] Weather applet keeps showing "?" icon after computer restart
https://bugs.kde.org/show_bug.cgi?id=450774 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450119] Plasma slow/freezes on resume - possible memory leak?
https://bugs.kde.org/show_bug.cgi?id=450119 --- Comment #12 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450801] Many complaints of taskbar/application menu freezing, workflow is totally disrupted, users are really frustrated; only rebooting can restore functionality.
https://bugs.kde.org/show_bug.cgi?id=450801 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 378577] Power Management doesn't reset battery power status after suspend
https://bugs.kde.org/show_bug.cgi?id=378577 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443706] Crash in WindowShadowTile::~WindowShadowTile()
https://bugs.kde.org/show_bug.cgi?id=443706 Nate Graham changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m --- Comment #15 from Nate Graham --- *** Bug 450506 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450506] panel freezes plasmashell on wayland crashes
https://bugs.kde.org/show_bug.cgi?id=450506 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #7 from Nate Graham --- *** This bug has been marked as a duplicate of bug 443706 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 398934] cannot pair Android to Debian desktop
https://bugs.kde.org/show_bug.cgi?id=398934 Howard changed: What|Removed |Added Blocks||452250 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=452250 [Bug 452250] cannot pair Android to Debian desktop -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 452250] New: cannot pair Android to Debian desktop
https://bugs.kde.org/show_bug.cgi?id=452250 Bug ID: 452250 Summary: cannot pair Android to Debian desktop Product: kdeconnect Version: 1.3.3 Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: xyzzy54...@protonmail.com CC: albertv...@gmail.com, justin.zo...@gmail.com, wrinn...@web.de Depends on: 398934 Target Milestone: --- +++ This bug was initially created as a clone of Bug #398934 +++ SUMMARY Can't connect phone to desktop PC with KDEconnect STEPS TO REPRODUCE 1. I have KDEconnect v1.3.3 up and running on the desktop PC 2. I have installed Android KDEconnect v1.19.1 from Google Play store on Android Both devices are connected to the same router, both have 192.168.11.* IPs. Android has a working wireless connection to the router. Ubuntu has a working wired ethernet connection to the router. I can ping the Android device from Ubuntu, and can copy files in both directions using app Wifi File Transger The router is running DD-WRT, Firmware: DD-WRT v3.0-r41057 std (09/18/19) OBSERVED RESULT Neither device's KDEconnect application can see the other device. Entering the Ubuntu IP address into Android's KDEconnect app doesn't help EXPECTED RESULT I would expect KDEconnect on each device to list the other device by IP or name SOFTWARE/OS VERSIONS Ubuntu 18.04.6 Motorola Moto X Style XT1575 / Android 7.0 Nougat ADDITIONAL INFORMATION *** Cloned from bug follows *** SUMMARY STEPS TO REPRODUCE 1. I have KDE up and running on the desktop PC. kdeconnect v1.3.1 2. I have installed Android KDEconnect from Google. On the Android (Samsung Galaxy Note 3 Neo) the desktop is offered for connection. Both devices are connected to the same router, both have 192.168.2.* IPs. Android has a working wireless connection to the router. Debian has a working ethernet connection to the router. The router is running DD-WRT. EXPECTED RESULT I do not know what a successful connection looks like. Hopefully I would be able to recognize it. ACTUAL RESULT When trying to pair, Android says, "Abbruch durch Gegenstelle" (interrupted by peer). In the desktop /var/log/syslog I find: "Peer 192.168.2.24:n is not from a LAN" (many times), where n is the varying port number. SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Maybe a specific setting in the router could help?! Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=398934 [Bug 398934] cannot pair Android to Debian desktop -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452024] Date Format when using CSV Importer --> Make QIF File
https://bugs.kde.org/show_bug.cgi?id=452024 --- Comment #12 from mrbee --- I am now able to select a profile, thanks for that. Unfortunately the exported QIF file is still always in the format DD.MM. no matter what I define in the QIF profile. %d/%m/%yy --> DD.MM. %d/%m/% --> DD.MM. %m-%d-% --> DD.MM. %mmm/%d/% --> DD.MM. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452249] Configuring pattern scale is unintuitive as the "true" max range is dependent on texture size, and also min value produces misleading results
https://bugs.kde.org/show_bug.cgi?id=452249 tomtomtomreportin...@gmail.com changed: What|Removed |Added Platform|Other |Appimage Version|nightly build (please |5.0.2 |specify the git hash!) | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452249] New: Configuring pattern scale is unintuitive as the "true" max range is dependent on texture size, and also min value produces misleading results
https://bugs.kde.org/show_bug.cgi?id=452249 Bug ID: 452249 Summary: Configuring pattern scale is unintuitive as the "true" max range is dependent on texture size, and also min value produces misleading results Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY Configuring the pattern scale is quirky due to two reasons: * The practical max range of the scale value is dependent on the size of the texture. For example, the actual max scale for a 512x512 pattern is ~.40 while the actual max scale for a 20x20 pattern is ~10.0. * Sliding the scale down to 0.00 seems to produce an unexpected visual of a significantly large-scaled texture that doesn't seem to be achievable with the current "true" ranges. STEPS TO REPRODUCE 1. Select Basic 2 Opacity. 2. Enable Pattern option. 3. With 01_canvas.png (512x512) as the default pattern, observe the stroke at when the pattern scale is at 0.00 and when increasing it past .40. OBSERVED RESULT 0.00 produces an unexpected result while going past .40 on the slider does nothing. EXPECTED RESULT Ideally there should be no invisible limit to the scale value besides what the slider designates. 0.00 shouldn't produce a largely scaled texture. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.12.12 (appimage) ADDITIONAL INFORMATION This does not seem to be a regression. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 452060] plasma-integration commit 2b406a9df triggers a konsole segfault
https://bugs.kde.org/show_bug.cgi?id=452060 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-integration/commi ||t/8a36a5b46f7464f7c8e5f8048 ||2c4a796f7bdfcbc --- Comment #3 from David Edmundson --- Git commit 8a36a5b46f7464f7c8e5f80482c4a796f7bdfcbc by David Edmundson. Committed on 04/04/2022 at 01:40. Pushed by davidedmundson into branch 'master'. Initialise globals on startup Even though use of QWaylandClientExtension has the registry initialsed on startup, there's a quirk of extension that it doesn't create itself right away. We've seen that windows can change palettes on startup before the event loop has run. M +16 -0src/platformtheme/kwaylandintegration.cpp https://invent.kde.org/plasma/plasma-integration/commit/8a36a5b46f7464f7c8e5f80482c4a796f7bdfcbc -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 452248] New: Some autostarted applications do not have their icon and proper name shown in the Applications table/view (instead just the .desktop file name is used)
https://bugs.kde.org/show_bug.cgi?id=452248 Bug ID: 452248 Summary: Some autostarted applications do not have their icon and proper name shown in the Applications table/view (instead just the .desktop file name is used) Product: plasma-systemmonitor Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: putr...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY On my system I noticed that Kalendar's reminder daemon is shown as "org.kde.kalendarac" despite `/etc/xdg/autostart/org.kde.kalendarac.desktop` having a proper name and icon. EasyEffects is similarly affected if its autostart option is enabled within the app, with it showing as "easyeffects-service", again despite `~/.config/autostart/easyeffects-service.service` having a proper name and icon. I noticed that the key difference between those two and other autostarted apps on my system that look fine is that those two do not have a corresponding .desktop file in either `/usr/share/applications` or `~/.local/share/applications`, so I tried copying the problematic autostart .desktop files to `~/.local/share/applications` and adding `NoDisplay=true` to them as a workaround, and restarting System Monitor afterwards made them appear correctly, with the right name and icon. I do have systemd startup enabled, not sure if that's relevant or not. STEPS TO REPRODUCE 1. Install Kalendar (which on Arch at least includes the `/etc/xdg/autostart/org.kde.kalendarac.desktop` file) 2. Reboot 3. Open System Monitor and look at the Applications table OBSERVED RESULT "org.kde.kalendarac" is present in the table with no icon. EXPECTED RESULT "Kalendar Reminder Client" (or the translated name I guess) should be present instead, with the Kalendar icon. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.17.1-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452247] Window is placed on wrong screen after monitors power on
https://bugs.kde.org/show_bug.cgi?id=452247 r...@alum.mit.edu changed: What|Removed |Added CC||r...@alum.mit.edu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452247] New: Window is placed on wrong screen after monitors power on
https://bugs.kde.org/show_bug.cgi?id=452247 Bug ID: 452247 Summary: Window is placed on wrong screen after monitors power on Product: kwin Version: 5.24.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: r...@alum.mit.edu Target Milestone: --- SUMMARY *** When I resume a session with two monitors after screens have been powered down by power management, a window on the second monitor comes back on the first monitor even with an explicit rule placing the window on the second monitor. To correctly place the window, I need to make any change to the window rule (e. g. change Initial placement from Force Temporarily to Do Not Affect or vice versa -- that's the one I toggle, so I alternate which setting gets used), and the window is then placed correctly on the second monitor. This started some time within the past few months; I'm not sure exactly what Plasma version is involved. *** STEPS TO REPRODUCE 1. Place a window on the second monitor (I use a window rule forcing screen 1 with Apply initially -- it doesn't matter whether I use Apply initially, Force, or any other setting). The window in question is a full-screen VNC viewer, but I believe I've seen it with other windows. 2. Allow the power saving to turn on (I use screen energy saving at 120 minutes). 3. Move the mouse or press a key and wait for the screen to power on. OBSERVED RESULT VNC window in question is placed on the first screen of my 2-monitor setup; I have to minimize it, since it's full screen. If I then make any change to the window settings for the window in question and restore the window, it comes back on the second monitor. The change must be to a rule affecting the window in question; changing a different rule does not resolve the problem. EXPECTED RESULT Window should display on the display it was previously on. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE 15.3 (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version 5.3.18-150300.59.54-preempt (64 bit) Graphics Platform: X11 ADDITIONAL INFORMATION Primary display (screen 0): Dell U2718Q, positioned at left, portrait mode (3840x2160) Secondary display (screen 1): Dell P2715Q, positioned at right, same -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 452246] New: 'Reformat or edit with Partition Manager' option from 'Disks & Devices" applet is pointless with devices that can not be formatted nor edited (optical discs and mo
https://bugs.kde.org/show_bug.cgi?id=452246 Bug ID: 452246 Summary: 'Reformat or edit with Partition Manager' option from 'Disks & Devices" applet is pointless with devices that can not be formatted nor edited (optical discs and mounted ISO images, for example) Product: partitionmanager Version: 22.03.80 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 147950 --> https://bugs.kde.org/attachment.cgi?id=147950=edit screenshot STEPS TO REPRODUCE 1. mount an ISO image via 'Mount' option from context menu of Dolphin or insert a cd/dvd/bd disc 2. click on 'Disks & Devices" applet in system tray and click on your mounted ISO image or inserted cd/dvd/bd 3. click on 'Reformat or edit with Partition Manager' device action 4. enter your password to open KDE Partition Manager OBSERVED RESULT KDE Partition Manager opens and shows an error. Please see the attached screenshot showing the error that occurs when I reproduce the bug with an ISO image. EXPECTED RESULT 'Disks & Devices' applet should not offer 'Reformat or edit with Partition Manager' device action for devices that can not be formatted nor edited . SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Graphics Platform: Wayland ADDITIONAL INFORMATION possibly this bug affects other devices like cameras and phones. Not tested with these devices. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 452245] New: Audio control buttons don't work at all
https://bugs.kde.org/show_bug.cgi?id=452245 Bug ID: 452245 Summary: Audio control buttons don't work at all Product: Bluedevil Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: piotr.mierzwin...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY After connection to my device, so ATH-ANC900BT, I can see it was recognized as "Audio device". I can see also audio control buttons line (play, pause, etc.). It doesn't work even I link this device to play audio for given application, for example Firefox, Clementine. When I click onto "Pause" button then happens nothing I tried also turn on "Media Player" in Task Bar, but it didn't help STEPS TO REPRODUCE 1. connect audio device via bluetooth 2. link it with source of sound, for example Firefox 3. start playing sound in given application 4. open proper device in Bluetooth and click "Pause" button OBSERVED RESULT clicking onto buttons doesn't bring any effect EXPECTED RESULT clicking onto buttons should allow control of audio, so i.e. pause of it SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 452244] Isn't shown battery level for my headset (ATH-ANC900BT)
https://bugs.kde.org/show_bug.cgi?id=452244 --- Comment #4 from Piotr Mierzwinski --- ADDITIONAL INFORMATION $ pacman -Q bluez bluez 5.64-2 UPDATE of DESCRIPTION The issue is that when I connect my headset manually using bluetoothctl then I get battery level, but using kde wizard, doesn't. Please check attached screenshots. Manually I do it like this: bluetoothctl Agent registered AdvertisementMonitor path registered [bluetooth]# power on Changing power on succeeded [bluetooth]# agent on Agent is already registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on ... [CHG] Device 00:0A:45:0D:F0:6B Name: BLE_ATH-ANC900BT [CHG] Device 00:0A:45:0D:F0:6B Alias: BLE_ATH-ANC900BT .. [bluetooth]# pair 00:0A:45:0D:F0:6B Attempting to pair with 00:0A:45:0D:F0:6B [CHG] Device 00:0A:45:0D:F0:6B Connected: yes [CHG] Device 00:0A:45:0D:F0:6B Name: BLE_ATH-ANC900BT [CHG] Device 00:0A:45:0D:F0:6B Alias: BLE_ATH-ANC900BT [NEW] Primary Service (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0001 1801--1000-8000-00805f9b34fb Generic Attribute Profile [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0001/char0002 2a05--1000-8000-00805f9b34fb Service Changed [NEW] Descriptor (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0001/char0002/desc0004 2902--1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Primary Service (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service000a 1804--1000-8000-00805f9b34fb Tx Power [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service000a/char000b 2a07--1000-8000-00805f9b34fb Tx Power Level [NEW] Primary Service (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service000d 1802--1000-8000-00805f9b34fb Immediate Alert [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service000d/char000e 2a06--1000-8000-00805f9b34fb Alert Level [NEW] Primary Service (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0010 1803--1000-8000-00805f9b34fb Link Loss [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0010/char0011 2a06--1000-8000-00805f9b34fb Alert Level [NEW] Primary Service (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0013 180d--1000-8000-00805f9b34fb Heart Rate [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0013/char0014 2a37--1000-8000-00805f9b34fb Heart Rate Measurement [NEW] Descriptor (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0013/char0014/desc0016 2902--1000-8000-00805f9b34fb Client Characteristic Configuration [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0013/char0017 2a38--1000-8000-00805f9b34fb Body Sensor Location [NEW] Primary Service (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019 180a--1000-8000-00805f9b34fb Device Information [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char001a 2a29--1000-8000-00805f9b34fb Manufacturer Name String [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char001c 2a24--1000-8000-00805f9b34fb Model Number String [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char001e 2a25--1000-8000-00805f9b34fb Serial Number String [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char0020 2a27--1000-8000-00805f9b34fb Hardware Revision String [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char0022 2a26--1000-8000-00805f9b34fb Firmware Revision String [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char0024 2a28--1000-8000-00805f9b34fb Software Revision String [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char0026 2a23--1000-8000-00805f9b34fb System ID [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char0028 2a2a--1000-8000-00805f9b34fb IEEE 11073-20601 Regulatory Cert. Data List [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service0019/char002a 2a50--1000-8000-00805f9b34fb PnP ID [NEW] Primary Service (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service002c 1100-d102-11e1-9b23-00025b00a5a5 Vendor specific [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service002c/char002d 1101-d102-11e1-9b23-00025b00a5a5 Vendor specific [NEW] Characteristic (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service002c/char002f 1102-d102-11e1-9b23-00025b00a5a5 Vendor specific [NEW] Descriptor (Handle 0x) /org/bluez/hci0/dev_00_0A_45_0D_F0_6B/service002c/char002f/desc0031
[Bluedevil] [Bug 452244] Isn't shown battery level for my headset (ATH-ANC900BT)
https://bugs.kde.org/show_bug.cgi?id=452244 --- Comment #3 from Piotr Mierzwinski --- Created attachment 147949 --> https://bugs.kde.org/attachment.cgi?id=147949=edit bluetooth_connection_made_manually -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 452244] Isn't shown battery level for my headset (ATH-ANC900BT)
https://bugs.kde.org/show_bug.cgi?id=452244 --- Comment #2 from Piotr Mierzwinski --- Created attachment 147948 --> https://bugs.kde.org/attachment.cgi?id=147948=edit bluetooth_connection_made_by_kde -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 452244] Isn't shown battery level for my headset (ATH-ANC900BT)
https://bugs.kde.org/show_bug.cgi?id=452244 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- ADDITIONAL INFORMATION $ pacman -Q | grep pulse libpulse 15.0-4 projectm-pulseaudio 3.1.12-3 pulseaudio 15.0-4 pulseaudio-alsa 1:1.2.6-3 pulseaudio-bluetooth 15.0-4 pulseaudio-equalizer 15.0-4 pulseaudio-qt 1.3-1 pulsemixer 1.5.1-3 $ lsmod | grep bt btusb 65536 0 btrtl 28672 1 btusb btbcm 20480 1 btusb btintel45056 1 btusb btmtk 16384 1 btusb bluetooth 851968 59 btrtl,hidp,btmtk,btintel,btbcm,bnep,btusb,rfcomm $ pacman -Q | grep blue bluedevil 1:5.24.4-1 bluez 5.64-2 bluez-hid2hci 5.64-2 bluez-libs 5.64-2 bluez-qt 5.92.0-1 bluez-tools 0.2.0-5 bluez-utils 5.64-2 gnome-bluetooth 3.34.5-2 pulseaudio-bluetooth 15.0-4 python-pybluez 0.23-4 Not sure if this is related, because I use Bluez, but I tried also this (without success): I start daeamon with experimental function like this: ExecStart=/usr/lib/bluetooth/bluetoothd -E And in configuration file: /etc/bluetooth/main.conf I have line: Experimental = true in section "General" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447937] Flatpak runtime version numbers are nonsensical on update page
https://bugs.kde.org/show_bug.cgi?id=447937 --- Comment #4 from Prajna Sariputra --- I cherrypicked the commit from master into this MR for the Plasma/5.24 branch: https://invent.kde.org/plasma/discover/-/merge_requests/287 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 452244] New: Isn't shown battery level for my headset (ATH-ANC900BT)
https://bugs.kde.org/show_bug.cgi?id=452244 Bug ID: 452244 Summary: Isn't shown battery level for my headset (ATH-ANC900BT) Product: Bluedevil Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: system tray Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY I have headset Audio Technica model ANC900BT connecting to my PC via Bluetooth. Unfortunately after proper connection (I can listen sound via this device) I don't see battery level in applet of system tray. It is is connected by BLE_ATH-ANC900BT (Bluetooth Low Energy way). STEPS TO REPRODUCE 1. Pair headset ATH-ANC900BT 2. Connect it to host 3. Open Bluetooth and unfold entry: BLE_ATH-ANC900BT OBSERVED RESULT No battery level EXPECTED RESULT Battery level should appear SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92 Qt Version: 5.15.3 (with recent kde patches) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452203] Settings window makes no use of the global menu
https://bugs.kde.org/show_bug.cgi?id=452203 --- Comment #4 from ryu.ketsu...@outlook.com --- Created attachment 147947 --> https://bugs.kde.org/attachment.cgi?id=147947=edit A screenshot of the settings window not using the global menu For some reason it's not for me. -- You are receiving this mail because: You are watching all bug changes.
[kpdf] [Bug 101648] image link don't work
https://bugs.kde.org/show_bug.cgi?id=101648 --- Comment #2 from Albert Astals Cid --- Created attachment 147946 --> https://bugs.kde.org/attachment.cgi?id=147946=edit The file for posterity -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452243] New: Programs running on Xwayland randomly crash and Xwayland stops working
https://bugs.kde.org/show_bug.cgi?id=452243 Bug ID: 452243 Summary: Programs running on Xwayland randomly crash and Xwayland stops working Product: kwin Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: dbeka...@ee.ethz.ch Target Milestone: --- Created attachment 147945 --> https://bugs.kde.org/attachment.cgi?id=147945=edit excerpt from system logs during time of crash SUMMARY While using the wayland session X11 programs running via Xwayland(such as STM32CubeIDE and Xilinx Vivado) randomly crash with no useful information in logs. After this happens, the session continues to work without any issues but X11 programs are not displayed anymore. They do run in the background but aren't displayed. This can only be fixed by logging out and in. Unfortunately no core dumps are generated and the logs only tell that Xwayland/the X11 server has died. Unfortunately I don't have much than can be useful for identifying the cause but I would be more than happy to perform troubleshooting if anyone has any suggestions. STEPS TO REPRODUCE 1. Run any X11 program via Xwayland 2. Wait for an indeterminate/seemingly random amount of time OBSERVED RESULT Xwayland(and thus the program) crashes and afterwards all X11 programs aren't being displayed anymore until the session gets restarted EXPECTED RESULT The program continues to run without issues SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.17.1-zen1-1-zen (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442549] "RGB Range" feature's UI is confusing
https://bugs.kde.org/show_bug.cgi?id=442549 Nate Graham changed: What|Removed |Added Version Fixed In||5.25 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 452201] Okular crash when edit highlighter's color
https://bugs.kde.org/show_bug.cgi?id=452201 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #6 from Albert Astals Cid --- Yes, those logs are relatively useful. They show the crash is happening in libqgnomeplatformtheme.so which is something outside of Okular's control. Basically we say "show a color dialog" and then every platform can decide what you show, and libqgnomeplatformtheme.so is crashing there. This is either a bug in gtkj, a bug in libqgnomeplatformtheme.so itself or a bug in manjaro that needs to recompile qgnomeplatform. Oh qgnomeplatform is in AUR... i then would guess you shot yourself in the foot for using that and potentially need to recompile it yourself, anyhow nothing we can do to fix this problem since it's not Okular's problem. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447937] Flatpak runtime version numbers are nonsensical on update page
https://bugs.kde.org/show_bug.cgi?id=447937 --- Comment #3 from Nate Graham --- Please feel free to submit a merge request with that patch targeted at the Plasma/5.24 branch! 5.24 is an LTS release so it would be a good thing to have fixed there too. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 447897] Add units with SI prefixes to Bit Rate and Sample Rate
https://bugs.kde.org/show_bug.cgi?id=447897 Nate Graham changed: What|Removed |Added Version Fixed In||22.04 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451592] KDE Plasma Wayland shows no display output after SDDM autologin
https://bugs.kde.org/show_bug.cgi?id=451592 --- Comment #5 from Nate Graham --- Sounds like it could be an issue in SDDM itself. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 447897] Add units with SI prefixes to Bit Rate and Sample Rate
https://bugs.kde.org/show_bug.cgi?id=447897 Jack Hill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/mult ||imedia/elisa/commit/be01acf ||1ca870cab159d0fc6e8fa1bafcd ||4deb6a --- Comment #1 from Jack Hill --- Git commit be01acf1ca870cab159d0fc6e8fa1bafcd4deb6a by Jack Hill. Committed on 03/04/2022 at 21:11. Pushed by ngraham into branch 'release/22.04'. Add SI units to bit rate and sample rate Format bit rate as "kbps" with no decimal places Format sample rate as "kHz" with one decimal place M +6-2src/models/trackmetadatamodel.cpp https://invent.kde.org/multimedia/elisa/commit/be01acf1ca870cab159d0fc6e8fa1bafcd4deb6a -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442549] "RGB Range" feature's UI is confusing
https://bugs.kde.org/show_bug.cgi?id=442549 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kscreen/commit/275cdc0d3 ||548a006ec6a4c9796392bb2c86a ||ba2a Resolution|--- |FIXED --- Comment #4 from Zamundaaa --- Git commit 275cdc0d3548a006ec6a4c9796392bb2c86aba2a by Xaver Hugl. Committed on 03/04/2022 at 21:46. Pushed by ngraham into branch 'master'. KCM: Explain what overscan and rgb range do M +37 -20 kcm/package/contents/ui/OutputPanel.qml https://invent.kde.org/plasma/kscreen/commit/275cdc0d3548a006ec6a4c9796392bb2c86aba2a -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 452242] New: Support for Google's event colors
https://bugs.kde.org/show_bug.cgi?id=452242 Bug ID: 452242 Summary: Support for Google's event colors Product: korganizer Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: drokerg...@gmail.com Target Milestone: --- Request for adding support for Google Calendar's colors in it's events, created through the website, or other apps that supports this (android ones and such) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 377154] Changing Color of Birthday and Anniversary calendar
https://bugs.kde.org/show_bug.cgi?id=377154 gjditchfi...@acm.org changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 377154] Changing Color of Birthday and Anniversary calendar
https://bugs.kde.org/show_bug.cgi?id=377154 gjditchfi...@acm.org changed: What|Removed |Added CC||boven...@bovender.de --- Comment #1 from gjditchfi...@acm.org --- *** Bug 402084 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 402084] Color of "Birthdays & Anniversaries" cannot be changed by user
https://bugs.kde.org/show_bug.cgi?id=402084 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|RESOLVED CC||gjditchfi...@acm.org Resolution|--- |DUPLICATE --- Comment #3 from gjditchfi...@acm.org --- *** This bug has been marked as a duplicate of bug 377154 *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 335893] coloring of events in month view is unclear
https://bugs.kde.org/show_bug.cgi?id=335893 --- Comment #3 from gjditchfi...@acm.org --- (In reply to drokergeek from comment #1) > I suppose it is related but i cannot choose to view events by it's specific > color (set inside google calendar) but all events from the google calendar > are painted with the folder color, losing information Support for Google Calendar's colors is a different issue, since it is not clear how they relate to tag colors. If you are interested, please create a separate "wishlist" bug. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 335893] coloring of events in month view is unclear
https://bugs.kde.org/show_bug.cgi?id=335893 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||gjditchfi...@acm.org Resolution|--- |WAITINGFORINFO --- Comment #2 from gjditchfi...@acm.org --- (In reply to tony den haan from comment #0) > Most of the the event is determined by category, while a rather narrow > border indicates the calender this event belongs to. When using multiple > calendars this is hard to handle, it would even seem more useful to reverse > the coloring, category is way less significant than the person/calender the > entry is for. Maybe make this behaviour optional? > > Reproducible: Always Modern versions of KOrganizer support this: in the settings for the Agenda and Month views, you can choose "Calendar inside, tag outside". Does this satisfy your wish? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447498] Minor issue, Android app says battery information not available
https://bugs.kde.org/show_bug.cgi?id=447498 Paralel changed: What|Removed |Added CC||paralel.nonrecurently@aleea ||s.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 448714] No battery reporting on Windows
https://bugs.kde.org/show_bug.cgi?id=448714 Paralel changed: What|Removed |Added CC||paralel.nonrecurently@aleea ||s.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452241] New: Pan is not working after ctrl+z
https://bugs.kde.org/show_bug.cgi?id=452241 Bug ID: 452241 Summary: Pan is not working after ctrl+z Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: spikestherac...@gmail.com Target Milestone: --- SUMMARY *** Sometimes pan shortcut stop working after using ctrl+z(not always). It happens with both keyboard and tablet. Possibly dublicate 438784. *** STEPS TO REPRODUCE 1. paint for a while 2. use ctrl+z 3. try to pan (space) OBSERVED RESULT pan shortcut is not working EXPECTED RESULT call pan shortcut SOFTWARE/OS VERSIONS Windows: 10 Tablet : Wacom intuos pro s Krita version : krita-nightly-x64-5.0.2-alpha-ddc2bf7fd6 ADDITIONAL INFORMATION i can't reproduce this bug right away, the bug happens after a while -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452234] Impossible to have 2 top panels when 1 monitor is above the other
https://bugs.kde.org/show_bug.cgi?id=452234 --- Comment #4 from Michail Vourlakos --- (In reply to Jocelyn Thode from comment #3) > I'm using i3 and not kwin. Oh, if you set visibility mode to Windows go below, for the panel in the middle, is it fixed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452240] wayland: "No titlebar and frame" rule doesn't force SSDs
https://bugs.kde.org/show_bug.cgi?id=452240 Subramaniyam Raizada changed: What|Removed |Added CC||k...@subraizada.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452240] New: wayland: "No titlebar and frame" rule doesn't force SSDs
https://bugs.kde.org/show_bug.cgi?id=452240 Bug ID: 452240 Summary: wayland: "No titlebar and frame" rule doesn't force SSDs Product: kwin Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: k...@subraizada.com CC: isma...@gmail.com Target Milestone: --- SUMMARY I use the "No titlebar and frame": Force to "No" window rule to have KWin force server side decorations on some applications which use CSD by default. My rules were working in X11 - KWin would draw the titlebar above the application's CSD and would draw the Breeze theme's window shadows around the edges of the application. But the rules no longer work in Wayland. I've tested that the "Keep above other windows" rule is still applying properly to these applications in Wayland, so there's no issue with window matching. I can apply the rule in the opposite direction to remove SSDs on normal Qt/GTK applications like Konsole, Dolphin, Qalculate. That works fine in all scenarios. So force-removing SSDs works, but force-adding them doesn't. STEPS TO REPRODUCE 1. For an application which uses CSD, add a rule which has "No titlebar and frame" set to "Force: No" 2. Run the application under an X11 session or in XWayland: the rule works. Run the application under native Wayland: the rule has no effect. OBSERVED RESULT When the application is running under native Wayland, the application does not have SSD applied by KWin. SSDs are drawn in X11 or when using XWayland. EXPECTED RESULT The application has server side decorations applied by KWin even in native Wayland. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I tested this with Gnome's Simple-Scan (any other CSD-using Gnome application should also reproduce) and also with some Electron applications. Electron applications will run under XWayland by default, so this needs to be added to the Exec line in their .desktop files to have them use native Wayland: " --enable-features=UseOzonePlatform --ozone-platform=wayland". Possibly related: https://bugs.kde.org/show_bug.cgi?id=429171 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451153] Incomplete Mariadb PrivCheck delete causes digiKam fail to start.
https://bugs.kde.org/show_bug.cgi?id=451153 --- Comment #19 from bugskde...@goland.org --- (In reply to Maik Qualmann from comment #18) > Try running the following commands in the database (mysql) if it works > normally: > > USE digikam; > CREATE TABLE IF NOT EXISTS PrivCheck (id INT) ENGINE InnoDB; > DROP TABLE PrivCheck; > > Maik MariaDB [(none)]> USE digikam; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [digikam]> CREATE TABLE IF NOT EXISTS PrivCheck (id INT) ENGINE InnoDB; ERROR 1813 (HY000): Tablespace for table '`digikam`.`PrivCheck`' exists. Please DISCARD the tablespace before IMPORT MariaDB [digikam]> DROP TABLE PrivCheck; ERROR 1051 (42S02): Unknown table 'digikam.PrivCheck' MariaDB [digikam]> So I tried: MariaDB [digikam]> ALTER TABLE PrivCheck DISCARD TABLESPACE; ERROR 1146 (42S02): Table 'digikam.PrivCheck' doesn't exist MariaDB [digikam]> CREATE TABLE IF NOT EXISTS PrivCheck (id INT) ENGINE InnoDB; ERROR 1813 (HY000): Tablespace for table '`digikam`.`PrivCheck`' exists. Please DISCARD the tablespace before IMPORT But that didn't seem to do anything either. Thoughts? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452239] Selection tool not working properly
https://bugs.kde.org/show_bug.cgi?id=452239 bloodyrainr...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from bloodyrainr...@gmail.com --- Sorry for disturbing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443129] 'Closeable' window rule does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=443129 Subramaniyam Raizada changed: What|Removed |Added CC||k...@subraizada.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 334460] Korganizer displays "Reminder: 1 minute before the start" when the reminder is actually set to a different number of minutes
https://bugs.kde.org/show_bug.cgi?id=334460 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||gjditchfi...@acm.org --- Comment #4 from gjditchfi...@acm.org --- I can't reproduce this problem with the corrent version, 5.19.3. Does it still affect you? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452239] New: Selection tool not working properly
https://bugs.kde.org/show_bug.cgi?id=452239 Bug ID: 452239 Summary: Selection tool not working properly Product: krita Version: 5.0.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: bloodyrainr...@gmail.com Target Milestone: --- Created attachment 147944 --> https://bugs.kde.org/attachment.cgi?id=147944=edit logs and kritarc 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 *** STEPS TO REPRODUCE 1. Import attached kritarc 2. Try using selection tool without pressing ctrl OBSERVED RESULT Selection tool is not working, unless used through ctrl EXPECTED RESULT Selection tool working properly SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION If remove kritarc from %appdata%/local, krita will recreate it and selection tool starts working properly. The cause of problem is unknown, it just stopped working -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452187] Wrong Meta+(Number) behaviour using "Shows tooltip window thumbnails" setting on grouped task
https://bugs.kde.org/show_bug.cgi?id=452187 --- Comment #2 from Aurora Robb Kristiansen --- I just performed another test on this, and found out that the task manager simply attempts to create a preview window where there last was one. This means that, if you hover your mouse over a different application on the task manager and let the tooltip window thumbnail appear, pressing Meta+(Number) on a grouped task will re-spawn the window thumbnail you just created with your mouse. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353654] Extend Kate's session to stash unsaved documents/changes on quit
https://bugs.kde.org/show_bug.cgi?id=353654 Ganton changed: What|Removed |Added CC||ku...@gmx.com --- Comment #14 from Ganton --- There are unsaved changes when using Kate 21.08.1 if you open a session, create a new file, write something, wait two minutes and (for example) execute: killall -9 kate Note: No data was lost when I used Kate 21.08.1, I opened a session, wrote something on an existing tab, waited two minutes and executed: killall -9 kate Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 452238] New: Asciidoc highlighting of sub-documents
https://bugs.kde.org/show_bug.cgi?id=452238 Bug ID: 452238 Summary: Asciidoc highlighting of sub-documents Product: kate Version: 21.08.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: marcelo.esco...@gmail.com Target Milestone: --- SUMMARY I have a master document that includes "sub-documents". The syntax highlighting only works if the document begins with "Level" 1: = Titile of the document but my "sub-documents" begin with level 2 == Chapetr and the syntax hightlighting does not work. STEPS TO REPRODUCE 1. Create asciidoc master document that includes a sub-document 2. Create subdocument that begins with title level > 1 3. Edit the subdocument in kate OBSERVED RESULT Headings aren't highlighted EXPECTED RESULT Headings should be highlighted regardless of the level at the beginning of the document SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #24 from vindicator --- One more correction (I hope), it wasn't vscode, but rather a hidden issue (much like the "SUnreclaim" from long ago)... https://www.reddit.com/r/archlinux/comments/tv9d8j/memory_available_unaccounted_for/ The short of that is "Unevictable" memory climbed (3GB) and wasn't showing associated with any process. When I came across a post about Intel's IGP leak(?), I remembered that issue was brought up regarding "notifications". I restarted the plasmashell service, and Unevictable dropped to 1GB (still way too high, given only konsole was open). I have yet to find out how to associate Unevictable memory with the related process(es), so I would know which one needs to be addressed accordingly. -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 452237] New: kTimeTracker crashes when Continue or Revert buttons are pressed
https://bugs.kde.org/show_bug.cgi?id=452237 Bug ID: 452237 Summary: kTimeTracker crashes when Continue or Revert buttons are pressed Product: ktimetracker Version: 5.0.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: i...@coders.kiwi.nz Target Milestone: --- Application: ktimetracker (5.0.1) Qt Version: 5.15.2 Frameworks Version: 5.92.0 Operating System: Linux 5.17.1-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: The issue is when the desktop goes from idle to active. KTimeTracker asks if time should be continued or reverted. The application crashes when either button is pressed. The crash can be reproduced every time. -- Backtrace: Application: KTimeTracker (ktimetracker), signal: Segmentation fault [KCrash Handler] #4 QHashData::nextNode (node=node@entry=0x5589e7f59c80) at tools/qhash.cpp:591 #5 0x7f676ed6a9a0 in QHash::const_iterator::operator++ (this=) at /usr/include/qt5/QtCore/qhash.h:425 #6 KIdleTimePrivate::timeoutReached (msec=, this=0x5589e3b8ecf0) at /usr/src/debug/kidletime-5.92.0-1.1.x86_64/src/kidletime.cpp:291 #7 operator() (msec=, __closure=) at /usr/src/debug/kidletime-5.92.0-1.1.x86_64/src/kidletime.cpp:88 #8 QtPrivate::FunctorCall, QtPrivate::List, void, KIdleTime::KIdleTime():: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #9 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #10 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl (which=, r=, ret=, a=, this_=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #11 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:436 #12 0x7f676d754503 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8bb49480, r=0x5589e3ab29e0, this=0x5589e3aef300) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x5589e3ad79f0, signal_index=4, argv=0x7ffc8bb49480) at kernel/qobject.cpp:3886 #14 0x7f676d74d9cf in QMetaObject::activate (sender=sender@entry=0x5589e3ad79f0, m=m@entry=0x7f676ed71d00 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc8bb49480) at kernel/qobject.cpp:3946 #15 0x7f676ed6a741 in AbstractSystemPoller::timeoutReached (this=this@entry=0x5589e3ad79f0, _t1=) at /usr/src/debug/kidletime-5.92.0-1.1.x86_64/build/src/KF5IdleTime_autogen/EWIEGA46WW/moc_abstractsystempoller.cpp:189 #16 0x7f676204aa5b in XSyncBasedPoller::xcbEvent (event=0x7f676401aff0, this=0x5589e3ad79f0) at /usr/src/debug/kidletime-5.92.0-1.1.x86_64/src/plugins/xsync/xsyncbasedpoller.cpp:295 #17 XSyncBasedPoller::xcbEvent (event=0x7f676401aff0, this=0x5589e3ad79f0) at /usr/src/debug/kidletime-5.92.0-1.1.x86_64/src/plugins/xsync/xsyncbasedpoller.cpp:279 #18 XSyncBasedPollerHelper::nativeEventFilter (result=, message=0x7f676401aff0, eventType=..., this=0x7f676204f240 <(anonymous namespace)::Q_QGS_s_globalXSyncBasedPoller::innerFunction()::holder>) at /usr/src/debug/kidletime-5.92.0-1.1.x86_64/src/plugins/xsync/xsyncbasedpoller.cpp:44 #19 XSyncBasedPollerHelper::nativeEventFilter (this=0x7f676204f240 <(anonymous namespace)::Q_QGS_s_globalXSyncBasedPoller::innerFunction()::holder>, eventType=..., message=0x7f676401aff0, result=) at /usr/src/debug/kidletime-5.92.0-1.1.x86_64/src/plugins/xsync/xsyncbasedpoller.cpp:39 #20 0x7f676d71b3cf in QAbstractEventDispatcher::filterNativeEvent (this=, eventType=..., message=message@entry=0x7f676401aff0, result=result@entry=0x7ffc8bb49518) at kernel/qabstracteventdispatcher.cpp:495 #21 0x7f6768fb1491 in QXcbConnection::handleXcbEvent (this=this@entry=0x5589e3822c40, event=event@entry=0x7f676401aff0) at qxcbconnection.cpp:536 #22 0x7f6768fb2b96 in QXcbConnection::processXcbEvents (this=0x5589e3822c40, flags=...) at qxcbconnection.cpp:1020 #23 0x7f6768fd8e03 in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:103 #24 0x7f676bcee122 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x7f676bcee4b8 in ?? () from /lib64/libglib-2.0.so.0 #26 0x7f676bcee56f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x7f676d775384 in QEventDispatcherGlib::processEvents (this=0x5589e39b1080, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f676d71c83b in QEventLoop::exec (this=this@entry=0x7ffc8bb497a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f676d724b10 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30
[okular] [Bug 452201] Okular crash when edit highlighter's color
https://bugs.kde.org/show_bug.cgi?id=452201 --- Comment #5 from Ricardo --- (In reply to Albert Astals Cid from comment #2) > Can you reproduce the crash? If so with any file or just with one in > particular? > > Can you attach a backtrace with debug symbols? Hello, yes the program crashes all the time and witch any document. I attached a video and a gnome-logs file. I hope It can help. Thanks -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 328976] Importing an exported VCS file fails when merging into an existing calendar (at least with caldav backend)
https://bugs.kde.org/show_bug.cgi?id=328976 --- Comment #16 from gjditchfi...@acm.org --- Git commit a1dc439862a3c0170540869ac3f1e79c4d05f8e3 by Glen Ditchfield. Committed on 03/04/2022 at 19:33. Pushed by gditchfield into branch 'master'. Adjust the error messages for failed imports @winterz M +6-4src/icalimporter.cpp https://invent.kde.org/pim/akonadi-calendar/commit/a1dc439862a3c0170540869ac3f1e79c4d05f8e3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #7 from Paul Floyd --- Just scalar and fexecve, the other fexecve tests were OK. The diffs look reasonable (just extra errors for argv/argv[0] like on Linux) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 452201] Okular crash when edit highlighter's color
https://bugs.kde.org/show_bug.cgi?id=452201 --- Comment #4 from Ricardo --- Created attachment 147943 --> https://bugs.kde.org/attachment.cgi?id=147943=edit Registry of the error, generated by Gnome-logs I hope this registry will be helpful. I am not familiarized witch debugs. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 332208] Crop with Ratio setting is bad implemented
https://bugs.kde.org/show_bug.cgi?id=332208 Daniel Roschka changed: What|Removed |Added CC||danielroschka@phoenitydawn. ||de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 450437] Warn for execve syscall with argv or argv[0] being NULL.
https://bugs.kde.org/show_bug.cgi?id=450437 --- Comment #6 from Mark Wielaard --- So do I assume correctly that the generic none/tests/execve, memcheck/tests/execve1 and memchck/tests/execve2 tests PASS with this patch on freebsd, but that the freebsd specific memcheck/tests/freebsd/scalar.vgtest fails and needs updates to memcheck/tests/freebsd/scalar.stderr.exp and /memcheck/tests/freebsd/scalar.stderr.exp-x86? Also how many/which of the freebsd specific fexecve tests fail? memcheck/tests/freebsd/fexecve.vgtest none/tests/freebsd/fexecve_hw1.vgtest none/tests/freebsd/fexecve_txt.vgtest none/tests/freebsd/fexecve_script2.vgtest none/tests/freebsd/fexecve_hw2.vgtest none/tests/freebsd/fexecve_script1.vgtest Are these failures that look "reasonable" and need updates to the .exp files for the new warnings or are they bugs? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 333066] Incorrect behaviour of "today" button in month view during first week of month
https://bugs.kde.org/show_bug.cgi?id=333066 gjditchfi...@acm.org changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||korganizer/commit/c8809c2dc ||0be2c48eedd956620a8c48e483f ||11b9 --- Comment #5 from gjditchfi...@acm.org --- Git commit c8809c2dc0be2c48eedd956620a8c48e483f11b9 by Glen Ditchfield, on behalf of Glen Ditchfield. Committed on 02/04/2022 at 19:05. Pushed by gditchfield into branch 'release/22.04'. Today button moves Month view to today's month If the date navigator has selected a week or a work week, the `Today` button switches the Month view to the month containing the first day of the selected period containing "today". On April 2 2022 it showed March, because the week started on March 28. This patch uses the "preferred month" infrastructure. On March 31 it would show March, and on April 1 it would show April. M +2-2src/datenavigator.cpp https://invent.kde.org/pim/korganizer/commit/c8809c2dc0be2c48eedd956620a8c48e483f11b9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449454] [Nouveau/X11] Using "adjust all fonts" in kcm_fonts causes plasmashell visual corruption
https://bugs.kde.org/show_bug.cgi?id=449454 --- Comment #5 from Nate Graham --- Oh ok. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449454] [Nouveau/X11] Using "adjust all fonts" in kcm_fonts causes plasmashell visual corruption
https://bugs.kde.org/show_bug.cgi?id=449454 Ahmad Samir changed: What|Removed |Added Summary|[NVIDIA] Using "adjust all |[Nouveau/X11] Using "adjust |fonts" in kcm_fonts causes |all fonts" in kcm_fonts |plasmashell visual |causes plasmashell visual |corruption |corruption -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449454] [NVIDIA] Using "adjust all fonts" in kcm_fonts causes plasmashell visual corruption
https://bugs.kde.org/show_bug.cgi?id=449454 Ahmad Samir changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #4 from Ahmad Samir --- I think it's not a duplicate, since I am using X11 and the nouveau driver not the nvidia proprietary one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449429] [NVIDIA] Panel and dialog rendering display graphical corruption under wayland
https://bugs.kde.org/show_bug.cgi?id=449429 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=449454| CC||a.samir...@gmail.com --- Comment #9 from Nate Graham --- *** Bug 449454 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449454] [NVIDIA] Using "adjust all fonts" in kcm_fonts causes plasmashell visual corruption
https://bugs.kde.org/show_bug.cgi?id=449454 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=449429| Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 449429 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449429] [NVIDIA] Panel and dialog rendering display graphical corruption under wayland
https://bugs.kde.org/show_bug.cgi?id=449429 Nate Graham changed: What|Removed |Added Component|Panel |general Ever confirmed|0 |1 Summary|[NVIDIA] Panel rendering|[NVIDIA] Panel and dialog |broken under wayland|rendering display graphical ||corruption under wayland Status|REPORTED|CONFIRMED Keywords||wayland CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 --- Comment #56 from Nate Graham --- Those are separate issues. Can you please open new bug reports for them? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447498] Minor issue, Android app says battery information not available
https://bugs.kde.org/show_bug.cgi?id=447498 --- Comment #3 from Tux --- Comment on attachment 147941 --> https://bugs.kde.org/attachment.cgi?id=147941 connect indicator screenshot (no data, -1% reported) Operating System: Arch KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-1-lts (64-bit) Graphics Platform: X11 Processors: 4 × AMD Ryzen 3 2200G with Radeon Vega Graphics Memory: 19,5 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 332048] Opening an existing To-do item for editing results in both the "Start" and "Due" times (yyyy MM dd hh mm ss) changing
https://bugs.kde.org/show_bug.cgi?id=332048 --- Comment #9 from gjditchfi...@acm.org --- *** Bug 345380 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345380] edit an exisiting todo that was created with a template changes the exisiting due date to the current date
https://bugs.kde.org/show_bug.cgi?id=345380 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |DUPLICATE CC||gjditchfi...@acm.org Status|REPORTED|RESOLVED --- Comment #4 from gjditchfi...@acm.org --- *** This bug has been marked as a duplicate of bug 332048 *** -- You are receiving this mail because: You are watching all bug changes.
[KOpeningHours] [Bug 452236] New: normalizeExpression output on monthday_range is simplified
https://bugs.kde.org/show_bug.cgi?id=452236 Bug ID: 452236 Summary: normalizeExpression output on monthday_range is simplified Product: KOpeningHours Version: 21.12.3 Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: normalization Assignee: fa...@kde.org Reporter: fam@live.nl Target Milestone: --- >From https://github.com/osm-fr/osmose-backend/pull/1424#issuecomment-1086725579 STEPS TO REPRODUCE 1. call normalizedExpression() on "2099 May 22-2099 Oct 07" OBSERVED RESULT normalizedExpression() produces "2099 May 22-Oct 07" EXPECTED RESULT No change for normalizedExpression, i.e. output equals input Per https://wiki.openstreetmap.org/wiki/Key:opening_hours/specification#selector:month , gives [ ] - [ ], and are defined as (a.o.) [ ] Unrelated, but for simplifiedExpression() the output is expected to be simplified to 2099 May 22-Oct 07 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447498] Minor issue, Android app says battery information not available
https://bugs.kde.org/show_bug.cgi?id=447498 --- Comment #2 from Tux --- Comment on attachment 147941 --> https://bugs.kde.org/attachment.cgi?id=147941 connect indicator screenshot (no data, -1% reported) Same thing here with Android 10 (Oppo Color OS flavour, unsure if that is the cause or not, I can't change or try any other phone OS right now) and KDEConnect on Arch on the other side. So far the same notification appears on the phone and and no battery usage % is displayed at all on the computer side, neither on the qt app, kde cli or Gconnect (which doesn't really matter here, but I tested it too). https://i.imgur.com/s4qFxO6.png d’abr. 03 20:45:31 honk-a-tron kdeconnectd[1827]: no pair requests to accept! d’abr. 03 20:46:06 honk-a-tron kdeconnectd[1827]: kdeconnect.plugin.contacts: handleResponseVCards: Unable to open "/home/tux/.local/share/kpeoplevcard/kdeconnect-009186294aa5a9f4/3047i55a861> d’abr. 03 20:46:28 honk-a-tron kdeconnectd[1827]: kdeconnect.plugin.battery: No Primary Battery detected on this system. This may be a bug. d’abr. 03 20:46:28 honk-a-tron kdeconnectd[1827]: kdeconnect.plugin.battery: Total quantity of batteries found: 0 d’abr. 03 20:46:28 honk-a-tron kdeconnectd[1827]: kdeconnect.plugin.contacts: handleResponseVCards: Unable to open "/home/tux/.local/share/kpeoplevcard/kdeconnect-009186294aa5a9f4/3047i55a861> d’abr. 03 20:46:36 honk-a-tron kcmshell5[197882]: qt.svg: Cannot open file ':/icons/kdeconnect/kdeconnect.svg', because: No such file or directory d’abr. 03 20:46:36 honk-a-tron kcmshell5[197882]: qt.svg: Cannot open file ':/icons/kdeconnect/kdeconnect.svg', because: No such file or directory d’abr. 03 20:46:54 honk-a-tron drkonqi[197949]: QSystemTrayIcon::setVisible: No Icon set -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 452201] Okular crash when edit highlighter's color
https://bugs.kde.org/show_bug.cgi?id=452201 --- Comment #3 from Ricardo --- Created attachment 147942 --> https://bugs.kde.org/attachment.cgi?id=147942=edit A video showing the okular crash -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 451509] Disabling the Help Runner plugin does not hide the question mark button
https://bugs.kde.org/show_bug.cgi?id=451509 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||ae89638eef8d2bcd1e06e8a8335 ||7f309c2ca1b58 --- Comment #2 from Nate Graham --- Git commit ae89638eef8d2bcd1e06e8a83357f309c2ca1b58 by Nate Graham, on behalf of Alexander Lohnau. Committed on 03/04/2022 at 18:41. Pushed by ngraham into branch 'master'. KRunner: Disable help button when runner is disabled M +2-0krunner/view.cpp M +10 -0krunner/view.h M +1-0lookandfeel/contents/runcommand/RunCommand.qml https://invent.kde.org/plasma/plasma-workspace/commit/ae89638eef8d2bcd1e06e8a83357f309c2ca1b58 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447498] Minor issue, Android app says battery information not available
https://bugs.kde.org/show_bug.cgi?id=447498 Tux changed: What|Removed |Added CC||not-a-peng...@tutanota.com --- Comment #1 from Tux --- Created attachment 147941 --> https://bugs.kde.org/attachment.cgi?id=147941=edit connect indicator screenshot (no data, -1% reported) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447797] Mouse cursor glitching upon switching states in the Wayland session
https://bugs.kde.org/show_bug.cgi?id=447797 Timothy B changed: What|Removed |Added CC||yule2...@live.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355588] Switching between alternative widgets makes them lose settings
https://bugs.kde.org/show_bug.cgi?id=355588 Stefano changed: What|Removed |Added CC||stefano.dave...@gmail.com --- Comment #12 from Stefano --- Not sure if it is just related or the same bug: Switching global themes make you lose your config. There's more: you might break the default config as well: -Switch to a theme without the default launcher on the 'meta' key -Switch back to default theme Your meta shortcut is now broken, it doesn't open the launcher anymore, even if you select the option to reset to defaults in the GUI. I could even be ok with losing your customizations when you switch to another global theme, but resetting everything to default should give you back the original behaviour -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452181] singleclick-mode multi-select w/ Ctrl+Left Click is broken
https://bugs.kde.org/show_bug.cgi?id=452181 --- Comment #4 from Nate Graham --- Can confirm that. Probably worth a ping to sysadmins or Harald directly, as IIRC he's the one who implemented it. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 447897] Add units with SI prefixes to Bit Rate and Sample Rate
https://bugs.kde.org/show_bug.cgi?id=447897 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 CC||n...@kde.org Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] All windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 Nate Graham changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #4 from Nate Graham --- Since it affects non-KDE windows, I think it's not a weird interaction having to do with the built-in code to remember window positions, since that only affects KDE app windows. Seems to be related instead to KWin's own window positioning behavior when going from a multi-screen setup to a single-screen setup. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452234] Impossible to have 2 top panels when 1 monitor is above the other
https://bugs.kde.org/show_bug.cgi?id=452234 --- Comment #3 from Jocelyn Thode --- I'm using i3 and not kwin. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 452235] New: Option to use shift+scroll to scroll horizontally
https://bugs.kde.org/show_bug.cgi?id=452235 Bug ID: 452235 Summary: Option to use shift+scroll to scroll horizontally Product: okular Version: 21.12.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kdeident...@firebox.anonaddy.com Target Milestone: --- SUMMARY In other programs (see Libreoffice and Chromium for examples), holding shift while scrolling scrolls horizontally. In Okular, holding shift and scrolling scrolls vertically, while holding alt and scrolling scrolls horizontally. It'd be nice if there were a way in the settings (possibly in keybinds) to switch these. STEPS TO REPRODUCE 1. Hold shift 2. Scroll up and down OBSERVED RESULT The page scrolls faster vertically EXPECTED RESULT There should be an option to scroll horizontally SOFTWARE/OS VERSIONS Windows 11 21H2 KDE Frameworks Version: Version 5.91.0 Qt Version: Version 5.15.2 (built against 5.15.2) ADDITIONAL INFORMATION Thanks for all the work y'all do on Okular! I use it all of the time instead of Adobe! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452230] Krita crashes when trying to create two imaged "from clipboard" sequentially
https://bugs.kde.org/show_bug.cgi?id=452230 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Dmitry Kazakov --- Yes, the bug is fixed in bcff23b8f01e483fdde3807cb19eef6ad7ea4eca . Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405087] Request: (Option to) replace icon with that of active window, if a window is active
https://bugs.kde.org/show_bug.cgi?id=405087 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/48 ||a0fc3719de3a87c394af905b16f ||8cedb9b6c08 --- Comment #2 from Nate Graham --- Git commit 48a0fc3719de3a87c394af905b16f8cedb9b6c08 by Nate Graham, on behalf of Jan Blackquill. Committed on 03/04/2022 at 17:49. Pushed by ngraham into branch 'master'. applets/windowlist: rewrite This rewrites the Window List applet, in order to have simpler code, as well as having a more useful design that tells the user what app is in focus. Related: bug 387582 A +74 -0applets/window-list/contents/ui/MenuButton.qml [License: GPL(v2.0+)] M +64 -242 applets/window-list/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/48a0fc3719de3a87c394af905b16f8cedb9b6c08 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387582] Window List lacks keyboard usability
https://bugs.kde.org/show_bug.cgi?id=387582 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/48 ||a0fc3719de3a87c394af905b16f ||8cedb9b6c08 Resolution|--- |FIXED --- Comment #5 from Nate Graham --- Git commit 48a0fc3719de3a87c394af905b16f8cedb9b6c08 by Nate Graham, on behalf of Jan Blackquill. Committed on 03/04/2022 at 17:49. Pushed by ngraham into branch 'master'. applets/windowlist: rewrite This rewrites the Window List applet, in order to have simpler code, as well as having a more useful design that tells the user what app is in focus. Related: bug 405087 A +74 -0applets/window-list/contents/ui/MenuButton.qml [License: GPL(v2.0+)] M +64 -242 applets/window-list/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/48a0fc3719de3a87c394af905b16f8cedb9b6c08 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452233] Plasma is inconsistent with respecting the initial sizes of applets
https://bugs.kde.org/show_bug.cgi?id=452233 Nate Graham changed: What|Removed |Added Component|general |Desktop Containment Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|normal |minor CC||n...@kde.org, ||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452234] Impossible to have 2 top panels when 1 monitor is above the other
https://bugs.kde.org/show_bug.cgi?id=452234 --- Comment #2 from Michail Vourlakos --- probably kwin bug and nothing related to Latte -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452234] Impossible to have 2 top panels when 1 monitor is above the other
https://bugs.kde.org/show_bug.cgi?id=452234 --- Comment #1 from Jocelyn Thode --- Created attachment 147940 --> https://bugs.kde.org/attachment.cgi?id=147940=edit panel_setup Add panel setup screenshot -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452234] Impossible to have 2 top panels when 1 monitor is above the other
https://bugs.kde.org/show_bug.cgi?id=452234 Jocelyn Thode changed: What|Removed |Added CC||jocelyn.th...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452234] New: Impossible to have 2 top panels when 1 monitor is above the other
https://bugs.kde.org/show_bug.cgi?id=452234 Bug ID: 452234 Summary: Impossible to have 2 top panels when 1 monitor is above the other Product: lattedock Version: 0.10.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: jocelyn.th...@gmail.com Target Milestone: --- Created attachment 147939 --> https://bugs.kde.org/attachment.cgi?id=147939=edit monitor_setup SUMMARY When having two monitors on top of each other like in the attached screenshot and setting 2 panels to sit on the top side of the screen. The panel of the bottom monitor is shifted to the bottom of the screen. This behavior is not reproducible when for example setting both on the left side and having one screen on the left of the primary. STEPS TO REPRODUCE 1. Have 2 monitor configured with one above the other one 2. Setup 2 panels (one for each screen) on the top edge OBSERVED RESULT The panel of the lower monitor is shifted to the bottom instead of being on the top edge EXPECTED RESULT Both panels should sit at the top of their respective monitors SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.24.24 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel: 5.17.1-arch1-1 (64 bit) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 332048] Opening an existing To-do item for editing results in both the "Start" and "Due" times (yyyy MM dd hh mm ss) changing
https://bugs.kde.org/show_bug.cgi?id=332048 gjditchfi...@acm.org changed: What|Removed |Added CC||jfl...@bigpond.net.au --- Comment #8 from gjditchfi...@acm.org --- *** Bug 367910 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 367910] Editting an existing todo resets the due date (possibly start date as well) to current date
https://bugs.kde.org/show_bug.cgi?id=367910 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from gjditchfi...@acm.org --- *** This bug has been marked as a duplicate of bug 332048 *** -- You are receiving this mail because: You are watching all bug changes.
