[valgrind] [Bug 489338] arm64: Instruction fcvtas should round 322.5 to 323, but result is 322.
https://bugs.kde.org/show_bug.cgi?id=489338 --- Comment #1 from Bernhard Übelacker --- Created attachment 171102 --> https://bugs.kde.org/attachment.cgi?id=171102=edit 0001-arm64-Fix-fcvtas-instruction.patch I tried to look into it and I think the issue is the `fcvtas` gets stored in the intermediate representation with Irrm_NEAREST. When this gets translated back to the native instruction i guess it results in a `fcvtns`. Attached patch tries to preserve this difference by using Irrm_NEAREST_TIE_AWAY_0, at least the reproducer shows with it no longer a difference. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 489338] New: arm64: Instruction fcvtas should round 322.5 to 323, but result is 322.
https://bugs.kde.org/show_bug.cgi?id=489338 Bug ID: 489338 Summary: arm64: Instruction fcvtas should round 322.5 to 323, but result is 322. Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: bernha...@mailbox.org Target Milestone: --- Created attachment 171101 --> https://bugs.kde.org/attachment.cgi?id=171101=edit Minimal reproducer: fp-valgrind-test.c Hello, I was investigating a debian bug, where the continuous integration failed because it receives a different value when running with valgrind. [1071656] I could track it down to a fcvtas instruction. => 0x4948 : fcvtas w5, d8 (With $d8=322.5) With plain GDB: (gdb) print $w5 $2 = 323 With valgrind+GDB: (gdb) print $w5 $2 = 322 Attached is a minimal reproducer. [1071656] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071656 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 484580] No access to webdavs since plasma6
https://bugs.kde.org/show_bug.cgi?id=484580 Bernhard Breinbauer changed: What|Removed |Added CC||bernh...@breinbauer.net --- Comment #9 from Bernhard Breinbauer --- I also can't connect to webdav servers since Plasma 6. I tried to produce a test case today with a public webdav server at https://www.dlp-test.com/webdav_pub/ I noticed the following: When I enter the URL webdav://www.dlp-test.com/webdav/ in dolphin, the connection works. When I change the URL to webdavs://www.dlp-test.com/webdav/ it loads forever, but the connection is never established. So it seems related to the secure connection. Can't see any useful information in journalctl. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483779] KMail hangs when invoking "Configure KMail..."
https://bugs.kde.org/show_bug.cgi?id=483779 --- Comment #4 from Bernhard E. Reiter --- As this also affects settings for crypto, I've created a sister report at https://dev.gnupg.org/T7081 . -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 485308] Public keys for encryption will be shown as "bad" in the composer, even if they can be used for encryption
https://bugs.kde.org/show_bug.cgi?id=485308 --- Comment #3 from Bernhard E. Reiter --- There is a sister report at https://dev.gnupg.org/T7075 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483779] KMail hangs when invoking "Configure KMail..."
https://bugs.kde.org/show_bug.cgi?id=483779 Bernhard E. Reiter changed: What|Removed |Added Status|REPORTED|CONFIRMED Priority|NOR |HI Ever confirmed|0 |1 Severity|normal |major --- Comment #2 from Bernhard E. Reiter --- Hello, I can confirm that there is a defect with the configuration of Kmail2 in kontact-24.02.1-kf.236.3.x86_64 (which I have noticed after a move from Qt5 to Qt6 and thus Plasma5 to Plasma6 on GNU/Linux Opensuse Leap + Stable KDE repos.) I notice a long delay in opening the configuration dialog (like 8 seconds) then I often get dialogs about to confirm a change in the configuration (which does not make sense as I did not yet do a change). Additionally changes are not recorded, as I wanted to make the change that is shown here: https://wiki.gnupg.org/EMailClients/KMail and closing the dialogs for good, after I open them again, the change was lost. Once I've got a crash as well. I raise the priority because and email client where configuration cannot be done or is lost is hard to impossible to use. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483779] KMail hangs when invoking "Configure KMail..."
https://bugs.kde.org/show_bug.cgi?id=483779 Bernhard E. Reiter changed: What|Removed |Added CC||bernh...@intevation.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 485308] Public keys for encryption will be shown as "bad" in the composer, even if they can be used for encryption
https://bugs.kde.org/show_bug.cgi?id=485308 --- Comment #2 from Bernhard E. Reiter --- Okay, listing both packages: kontact-24.02.1-kf.236.3.x86_64 kmail-24.02.1-kf.265.4.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 485308] Public keys for encryption will be shown as "bad" in the composer, even if they can be used for encryption
https://bugs.kde.org/show_bug.cgi?id=485308 Bernhard E. Reiter changed: What|Removed |Added Version|5.24.2 |6.0.1 --- Comment #1 from Bernhard E. Reiter --- the about dialog of Kontact says 6.0.1, while the package is 24.02.1-kf.265.4. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483779] KMail hangs when invoking "Configure KMail..."
https://bugs.kde.org/show_bug.cgi?id=483779 Bernhard E. Reiter changed: What|Removed |Added Version|6.0.0 |6.0.1 --- Comment #3 from Bernhard E. Reiter --- the about dialog of Kontact says 6.0.1, while the package is 24.02.1-kf.265.4. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 485308] New: Public keys for encryption will be shown as "bad" in the composer, even if they can be used for encryption
https://bugs.kde.org/show_bug.cgi?id=485308 Bug ID: 485308 Summary: Public keys for encryption will be shown as "bad" in the composer, even if they can be used for encryption Classification: Applications Product: kmail2 Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: bernh...@intevation.de Target Milestone: --- Created attachment 168332 --> https://bugs.kde.org/attachment.cgi?id=168332=edit showing the composer and kleopatra displaying the problem Recipients that the user wants to encrypt to are shown as red while the"validity" of a corresponding public key is just "unknown". This is a regression from a previous version and inconsistent with the display of the same public key in Kleopatra. STEPS TO REPRODUCE 1. Make sure to have an email address with a public key in GnuPG that is not fully "valid" for encryption. E.g. by calling `LANG=C gpg --locate-external-keys christoph.klas...@intevation.de` to get the pubkey via WKD, see something like `pub rsa3072/BA842B59E4A30D2F 2021-09-27 [SC] [expires: 2026-07-30] 978EE1FDE4F929229B3207CBBA842B59E4A30D2F uid [ unknown] Christoph Klassen sub rsa3072/11CD70D4D6223146 2021-09-27 [E] [expires: 2026-07-30]` 2. Open the composer, enter the email address. 3. Select "encrypt" 4. (optional) Send the email, and observe a dialog where you can okay the pubkey and encryption, showing that this can be done. 5. (optional) click on the icon to open Kleopatra and see that the pubkey has a validity of unknown. OBSERVED RESULT There is an icon shown left to the address that is a red square with a white cross. If you click on it, you see Kleopatra where there is a purple square with a white question mark. See kontact-24.02.1-pubkey-selection-problem-1.png EXPECTED RESULT As in previous versions the icon should be neutral to indicate that encryption is possible while there is not much trust that the pubkey belongs to the owner of the email address. (Ideally a pubkey fetched via WKD should have enough trust to allow encryption directly, because kmail does not know (yet?) that the pubkey has been fetched via WKD, it must chose an icon that stand for both situations, fully unknown and basic validity.) SOFTWARE/OS VERSIONS rpm -qa | grep kontact- kontact-lang-24.02.1-kf.236.3.noarch Operating System: openSUSE Leap 15.5 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485134] New: vgcore files unusable in gdb / does not load debug symbols
https://bugs.kde.org/show_bug.cgi?id=485134 Bug ID: 485134 Summary: vgcore files unusable in gdb / does not load debug symbols Classification: Developer tools Product: valgrind Version: 3.16.1 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: bernha...@mailbox.org Target Milestone: --- Created attachment 168219 --> https://bugs.kde.org/attachment.cgi?id=168219=edit add_auxiliary_vector_to_vgcore_files.patch It seems gcc defaults now quite some time to create pie executables. And gdb seems to rely for core files of such executables to contain an auxv section. This was found in this Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993018 There are more details about reproducing it. I investigated back then and came up with an patch which makes valgrind write the auxv section into the core file. Unfortuantely forgot about it and now trying to upstream this. Would such a patch be acceptable? If yes, how should I proceed? Patch is attached and it seems still to apply to current valgrind 3.20.0 in Debian Trixie/testing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481952] On X11, panels are hidden after minimizing Dolphin window
https://bugs.kde.org/show_bug.cgi?id=481952 Bernhard Rosenkränzer changed: What|Removed |Added CC||b...@lindev.ch --- Comment #39 from Bernhard Rosenkränzer --- Fix cherry-picked into OpenMandriva packages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481506] [X11, qt 6.7 beta 3 ] Open Terminal Here in Dolphin crashes konsole
https://bugs.kde.org/show_bug.cgi?id=481506 Bernhard Rosenkränzer changed: What|Removed |Added CC||b...@lindev.ch --- Comment #5 from Bernhard Rosenkränzer --- This is caused by KTerminalLauncherJob launching konsole with an empty environment (causing the DISPLAY variable to go missing, causing the connection to the X server to fail). It has already been fixed in git (and in OpenMandriva packages). https://invent.kde.org/frameworks/kio/-/commit/6e7775d315f389df0a440ed62b842ce83dc9a27e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481380] Docked floating panel obscures adjacent screen with its blurred background
https://bugs.kde.org/show_bug.cgi?id=481380 --- Comment #8 from Bernhard --- It did come back for me too, but it seems to be intermittent and I have no idea how to trigger it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477835] After re-arranging a screen in a multi-monitor setup, OSDs appear at wrong position on that screen until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=477835 Bernhard changed: What|Removed |Added CC||micraf...@gmail.com --- Comment #8 from Bernhard --- I can reproduce this on Plasma 6.0.1. Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.21-1-lts (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 6600 XT -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482809] New: SDR Color Intensity only applies if SDR Brightness is changed
https://bugs.kde.org/show_bug.cgi?id=482809 Bug ID: 482809 Summary: SDR Color Intensity only applies if SDR Brightness is changed Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: micraf...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY If the SDR Color Intensity is changed the colors on screen don't change until SDR Brightness is also changed. I've tried to determine if this is a problem with kscreen or the kcm, but I can't figure out what the kscreen option is to set it manually, if there even is one... For what it's worth, it worked for me back when I used qt6.7 on some plasma 6.0 beta. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.21-1-lts (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 6600 XT ADDITIONAL INFORMATION Output: 2 DP-2 enabled connected priority 1 DisplayPort Modes: 0:3840x2160@60! 1:3840x2160@144* [...] Geometry: 1200,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown HDR: enabled SDR brightness: 658 nits SDR gamut wideness: 50% Peak brightness: 1037 nits Max average brightness: 800 nits Min brightness: 0.0517 nits Wide Color Gamut: enabled ICC profile: none -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #9 from Bernhard --- (In reply to Zamundaaa from comment #8) > Interesting, that means KWin's internal state considers the mode to be > 120Hz... What does drm_info say? It should have a "MODE_ID" field where it > states the exact refresh rate that the driver is actually trying to drive. Oof, that one also states says 120Hz when my monitor reports 144Hz ├───CRTCs │ ├───CRTC 0 │ │ ├───Object ID: 85 │ │ ├───Legacy info │ │ │ ├───Mode: 3840x2160@120.02 driver phsync pvsync │ │ │ └───Gamma size: 256 │ │ └───Properties │ │ ├───"ACTIVE" (atomic): range [0, 1] = 1 │ │ ├───"MODE_ID" (atomic): blob = 150 │ │ │ └───3840x2160@120.02 driver phsync pvsync │ │ ├───"OUT_FENCE_PTR" (atomic): range [0, UINT64_MAX] = 0 │ │ ├───"VRR_ENABLED": range [0, 1] = 0 │ │ ├───"DEGAMMA_LUT": blob = 0 │ │ ├───"DEGAMMA_LUT_SIZE" (immutable): range [0, UINT32_MAX] = 4096 │ │ ├───"CTM": blob = 0 │ │ ├───"GAMMA_LUT": blob = 0 │ │ └───"GAMMA_LUT_SIZE" (immutable): range [0, UINT32_MAX] = 4096 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #7 from Bernhard --- (In reply to Zamundaaa from comment #6) > Okay, that looks correct. Does it change after the screen turns off and on > again? No, it does not, it always says 120Hz. The file is in fact identical when diffed. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467
--- Comment #5 from Bernhard ---
(In reply to Zamundaaa from comment #4)
> Please check the ~/.config/kwinoutputconfig.json file for your output
> config. What does the "refreshRate" key say for your screen, after changing
> the setting, and after rebooting?
Sorry, rebooting was a red herring. It happens every time the screen turns
off, like just from being idle and waiting. I'm testing now by setting "When
locked, turn of screen = 5s" in Energy Saving, then locking. It happens about
80% of the time.
In any case, there is only one entry for the 4k VRR screen:
{
"autoRotation": "InTabletMode",
"connectorName": "DP-2",
"edidHash": "778c61b12a29b15f7932a423b63aa9a2",
"edidIdentifier": "GBT 17152 16843009 41 2021 0",
"highDynamicRange": false,
"iccProfilePath": "",
"mode": {
"height": 2160,
"refreshRate": 120018,
"width": 3840
},
"overscan": 0,
"rgbRange": "Automatic",
"scale": 1,
"sdrBrightness": 400,
"sdrGamutWideness": 0,
"transform": "Normal",
"vrrPolicy": "Automatic",
"wideColorGamut": false
},
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied when screen turn on after idle
https://bugs.kde.org/show_bug.cgi?id=481467 Bernhard changed: What|Removed |Added Summary|Set refresh rate not|Set refresh rate not |applied after reboot|applied when screen turn on ||after idle -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied after reboot
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #3 from Bernhard --- Also I thought this might be a seperate issue, but I suspect it's not: My other display (output 2) often doesn't receive a signal after idle/suspend, but still shows as enabled. It only works again after either physically or in the KCM turning it off and on again. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied after reboot
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #2 from Bernhard --- It definitely still happens now that I don't have any other (obvious) problems, but I can't tell what triggers it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] Set refresh rate not applied after reboot
https://bugs.kde.org/show_bug.cgi?id=481467 --- Comment #1 from Bernhard --- Okay this issue has made a liar out of me. It's not reproducible every time, and it might be related to some other issues I've been having with bad cables on my second monitor. I'll report back when I know more. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481467] New: Set refresh rate not applied after reboot
https://bugs.kde.org/show_bug.cgi?id=481467 Bug ID: 481467 Summary: Set refresh rate not applied after reboot Classification: Plasma Product: KScreen Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: micraf...@gmail.com Target Milestone: --- SUMMARY When I set my monitor to 120Hz and reboot, it still shows 120Hz after reboot kscreen-doctor and the kcm, but my monitor reports 144Hz. VRR is set to automatic (and does not seem to be used for the desktop). Reproducible every time on this setup. STEPS TO REPRODUCE 1. Set screen to lower than max refresh rate 2. Reboot system 3. Screen receives max refresh rate OBSERVED RESULT The monitor receives a different refresh than is set. Changing the Adaptive Sync mode does not seem correct the refresh rate. To get back to 120Hz, I need to set it to something else first, pressing Apply twice. `kscreen-doctor -o` ouput remains exactly identical (as checked by diff) EXPECTED RESULT The monitor should receive the refresh rate I set. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 beta3 Kernel Version: 6.6.16-1-lts (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT ADDITIONAL INFORMATION We're talking Output 1 here. $ kscreen-doctor -o Output: 1 DP-2 enabled connected priority 1 DisplayPort Modes: 0:3840x2160@60! 1:3840x2160@144 2:3840x2160@120* 3:3840x2160@120 4:3840x2160@96 5:3840x2160@72 6:3840x2160@60 7:3840x2160@60 8:3840x2160@60 9:3840x2160@50 10:3840x2160@48 11:3840x2160@24 12:3840x2160@24 13:2560x1440@144 14:2560x1440@120 15:2560x1440@60 16:1920x1200@60 17:1920x1080@144 18:1920x1080@120 19:1920x1080@120 20:1920x1080@60 21:1920x1080@60 22:1920x1080@60 23:1920x1080@24 24:1920x1080@24 25:1600x1200@60 26:1680x1050@60 27:1280x1024@60 28:1440x900@60 29:1280x800@60 30:1280x720@120 31:1280x720@120 32:1280x720@100 33:1280x720@60 34:1280x720@60 35:1280x720@50 36:1024x768@75 37:1024x768@60 38:800x600@75 39:800x600@60 40:720x576@50 41:720x576@50 42:720x480@60 43:720x480@60 44:720x480@60 45:720x480@60 46:640x480@75 47:640x480@60 48:640x480@60 49:1600x1200@60 50:1280x1024@60 51:1024x768@60 52:2560x1600@60 53:1920x1200@60 54:1280x800@60 55:3840x2160@60 56:3200x1800@60 57:2880x1620@60 58:2560x1440@60 59:1920x1080@60 60:1600x900@60 61:1368x768@60 62:1280x720@60 Geometry: 1280,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown HDR: disabled Wide Color Gamut: disabled ICC profile: none Output: 2 DP-3 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60*! 1:1920x1200@60 2:2048x1080@60 3:2048x1080@24 4:1920x1080@60 5:1920x1080@60 6:1920x1080@60 7:1920x1080@50 8:1600x1200@60 9:1680x1050@60 10:1280x1024@75 11:1280x1024@60 12:1440x900@60 13:1280x800@60 14:1152x864@75 15:1280x720@60 16:1280x720@60 17:1280x720@60 18:1280x720@50 19:1024x768@75 20:1024x768@60 21:800x600@75 22:800x600@60 23:720x576@50 24:720x576@50 25:720x480@60 26:720x480@60 27:720x480@60 28:720x480@60 29:640x480@75 30:640x480@60 31:640x480@60 32:640x480@60 33:720x400@70 34:1600x1200@60 35:1280x1024@60 36:1024x768@60 37:1920x1200@60 38:1280x800@60 39:1920x1080@60 40:1600x900@60 41:1368x768@60 42:1280x720@60 Geometry: 0,0 1280x2276 Scale: 1.125 Rotation: 2 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none $ kscreen-doctor -i Environment: * KSCREEN_BACKEND : [not set] * KSCREEN_BACKEND_INPROCESS : [not set] * KSCREEN_LOGGING : [not set] Logging to: [logging disabled] Preferred KScreen backend : KSC_KWayland.so Available KScreen backends: * KSC_Fake.so: /usr/lib/qt6/plugins/kf6/kscreen/KSC_Fake.so * KSC_KWayland.so: /usr/lib/qt6/plugins/kf6/kscreen/KSC_KWayland.so * KSC_QScreen.so: /usr/lib/qt6/plugins/kf6/kscreen/KSC_QScreen.so * KSC_XRandR.so: /usr/lib/qt6/plugins/kf6/kscreen/KSC_XRandR.so -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481380] Docked floating panel obscures adjacent screen with its blurred background
https://bugs.kde.org/show_bug.cgi?id=481380 Bernhard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from Bernhard --- I can't reproduce this anymore with Qt 6.7 beta3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481380] Docked floating panel obscures adjacent screen with its blurred background
https://bugs.kde.org/show_bug.cgi?id=481380 --- Comment #3 from Bernhard --- Might be worth mentioning that Alacrity (the terminal) is also set to use plasma background blur effect (in case there is some strange interaction) On Fri, 16 Feb 2024, 23:17 Niccolò Venerandi, wrote: > https://bugs.kde.org/show_bug.cgi?id=481380 > > Niccolò Venerandi changed: > >What|Removed |Added > > > CC||nicc...@venerandi.com > > --- Comment #2 from Niccolò Venerandi --- > (This seems to be the contrast effect) > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481380] New: Docked floating panel obscures adjacent screen with its blurred background
https://bugs.kde.org/show_bug.cgi?id=481380 Bug ID: 481380 Summary: Docked floating panel obscures adjacent screen with its blurred background Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: micraf...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 165840 --> https://bugs.kde.org/attachment.cgi?id=165840=edit panel obscuring adjacent screen SUMMARY When a floating panel on the edge between two screens "docks" because a window is pushing it to the side, part of it's transparent background is visible on an adjacent screen. See attached video SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.6.16-1-lts (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION In case it is important, here is my screen configuration: $ kscreen-doctor -o | grep -e Geometry -e Scale -e Modes Modes: [...] 2:3840x2160@120* [...] Geometry: 1280,0 3840x2160 Scale: 1 Modes: 0:2560x1440@60*! [...] Geometry: 0,0 1280x2276 Scale: 1.125 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481379] New: Panel continuously floats/defloats when window is in the wrong spot
https://bugs.kde.org/show_bug.cgi?id=481379 Bug ID: 481379 Summary: Panel continuously floats/defloats when window is in the wrong spot Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: micraf...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 165839 --> https://bugs.kde.org/attachment.cgi?id=165839=edit panel doing its thing SUMMARY When a window is positioned on the first pixel where where the panel unfloats, it will try to float again, continuously. STEPS TO REPRODUCE 1. Have a floating panel 2. Move a window into the position where the panel starts to unfloat OBSERVED RESULT See attached video EXPECTED RESULT Panel should decide on one position SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.6.16-1-lts (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION In case it is important, here my scree configuration: $ kscreen-doctor -o | grep -e Geometry -e Scale -e Modes Modes: [...] 2:3840x2160@120* [...] Geometry: 1280,0 3840x2160 Scale: 1 Modes: 0:2560x1440@60*! [...] Geometry: 0,0 1280x2276 Scale: 1.125 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481307] crash after apply on unchanged keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=481307 --- Comment #2 from Bernhard --- Created attachment 165837 --> https://bugs.kde.org/attachment.cgi?id=165837=edit reproducible crash (In reply to Nate Graham from comment #1) > Could not reproduce the crash with those steps. Qt 6.6.0. The backtrace > suggests it's related to removing the item from the list view. Do you > remember which exact item was selected in the list at the moment you pressed > the Apply button? I tried a few and it didn't make a difference. The removed item was selected. It is reproducible, I've attached a recording. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 481301] Decrease connection speed precision
https://bugs.kde.org/show_bug.cgi?id=481301 Bernhard changed: What|Removed |Added Summary|Increase connection speed |Decrease connection speed |precision |precision -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481307] New: crash after apply on unchanged keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=481307
Bug ID: 481307
Summary: crash after apply on unchanged keyboard shortcuts
Classification: Applications
Product: systemsettings
Version: 5.93.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: micraf...@gmail.com
Target Milestone: ---
Application: systemsettings (5.93.0)
Qt Version: 6.7.0
Frameworks Version: 5.249.0
Operating System: Linux 6.6.16-1-lts x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.93.0 [CoredumpBackend]
-- Information about the crash:
1. I added steam as an application for shortcuts
2. set a shortcut
3. removed steam
4. pressed apply
Running kde-unstable with qt 6.7
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[New LWP 88406]
[New LWP 88407]
[New LWP 88410]
[New LWP 88413]
[New LWP 88408]
[New LWP 88412]
[New LWP 88429]
[New LWP 88431]
[New LWP 88432]
[New LWP 88409]
[New LWP 88433]
[New LWP 88435]
[New LWP 88442]
[New LWP 88411]
[New LWP 88443]
[New LWP 88444]
[New LWP 88414]
[New LWP 88434]
[New LWP 88445]
[New LWP 88415]
[New LWP 88446]
[New LWP 88447]
Downloading separate debug info for /usr/lib/libb2.so.1...
Downloading separate debug info for /usr/lib/libpsl.so.5...
Downloading separate debug info for /usr/lib/libunistring.so.5...
Downloading separate debug info for /usr/lib/libvorbisfile.so.3...
Downloading separate debug info for /usr/lib/libvorbis.so.0...
Downloading separate debug info for /usr/lib/libogg.so.0...
Downloading separate debug info for system-supplied DSO at 0x7fff7819d000...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/systemsettings kcm_keys'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x72c20d29c9c0 (LWP 88406))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x72c20d29c9c0 (LWP 88406))]
Thread 22 (Thread 0x72c1a3fff6c0 (LWP 88447)):
#0 0x72c211ea5ebe in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x634c9c6f35c4) at
futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x634c9c6f35c4,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x72c211ea5f3f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x634c9c6f35c4, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3 0x72c211ea8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x634c9c6f3568, cond=0x634c9c6f3598) at pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x634c9c6f3598, mutex=0x634c9c6f3568) at
pthread_cond_wait.c:618
#5 0x72c204913a1c in cnd_wait () at
../mesa-23.3.5/src/c11/impl/threads_posix.c:135
#6 util_queue_thread_func () at ../mesa-23.3.5/src/util/u_queue.c:290
#7 0x72c20490ad5c in impl_thrd_routine () at
../mesa-23.3.5/src/c11/impl/threads_posix.c:67
#8 0x72c211ea955a in start_thread (arg=) at
pthread_create.c:447
#9 0x72c211f26a3c in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 21 (Thread 0x72c1bcbf96c0 (LWP 88446)):
#0 0x72c211ea5ebe in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x634c9c6bf280) at
futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x634c9c6bf280,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x72c211ea5f3f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x634c9c6bf280, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3 0x72c211ea8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x634c9c6bf228, cond=0x634c9c6bf258) at pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x634c9c6bf258, mutex=0x634c9c6bf228) at
pthread_cond_wait.c:618
#5 0x72c204913a1c in cnd_wait () at
../mesa-23.3.5/src/c11/impl/threads_posix.c:135
#6 util_queue_thread_func () at ../mesa-23.3.5/src/util/u_queue.c:290
#7 0x72c20490ad5c in impl_thrd_routine () at
[plasma-nm] [Bug 481301] connection speed precision
https://bugs.kde.org/show_bug.cgi?id=481301 Bernhard changed: What|Removed |Added Summary|connection speed rounding |connection speed precision -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 481301] New: connection speed rounding
https://bugs.kde.org/show_bug.cgi?id=481301 Bug ID: 481301 Summary: connection speed rounding Classification: Plasma Product: plasma-nm Version: 5.27.9 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: micraf...@gmail.com Target Milestone: --- SUMMARY WiFi connection speed is typically rounded to full MBit/s. The bitrate shown as "1.2009 GBit/s" would usually be reported as 1200 MBit/s or 1.2 GBit/s by most tools. For example, `nmcli -f CAPABILITIES.SPEED dev show wlan0` reports 1200 Mb/s. STEPS TO REPRODUCE 1. Check details of a connected wifi network in the applet SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.6.16-1-lts (64-bit) ADDITIONAL INFORMATION Also I had a look in UiUtils::connectionSpeed and I think there is something wrong with the (not kilo)bits si-prefix -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 --- Comment #25 from Bernhard E. Reiter --- > Any idea where this fundamental discussion about the change culture of KDE > should be started? (bug reports is the wrong place, IMHO) True, this problem report and the tracker is suboptimal for the topic. For while it would have been one of the mailinglists, but I am not sure about this anymore. KDE e.V. maybe a place to ask about a good channel. However it is most helpful to understand that there are many volunteers that work on KDE's software products. While the whole process may have its downsides and bad outcomes, any volunteer time and effort is appreciated. -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 --- Comment #23 from Bernhard E. Reiter --- > You can easily rebuild a patch akonadi-calendar package even right now. It also maybe an option on OpenSuse to use one of the https://en.opensuse.org/SDB:KDE_repositories that is providing newer KDE Application revision to stable Opensuse Leap. Thanks David for any work on the issue! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 --- Comment #14 from Bernhard E. Reiter --- Two other potential "workarounds" for you (just for completion): * Stay on the elder version temporarily (to buy more time for a solution) * Go to Kontact from Trinity. It is still maintained > Bernhard, I know you once were well-connected into the upper tiers of KDE. > If this still holds true Unfortunately I do not know (anymore) whom to approach in this case. David of course used to be well connected as well. (*wave*) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 --- Comment #10 from Bernhard E. Reiter --- I also find that the regression is a major one. (I've reported this in https://bugs.kde.org/show_bug.cgi?id=452264 among other significant usability problems.). To add more use cases: ### saving working time shortly before a meeting * I have many meetings where the reminder is 15 minutes, so I can prepare. * When this is checked I delay up to 2 minutes before the appointment, * and then I have the remaining minutes to completely concentrate on something else until the alarm rings when I get up and walk to the meeting room. * This I gain 12-8 minutes of working time. ### using several computers * I have at least three computers with Kontact, that all sync their appontments (using the stone-old Kolab 2 format for historical reasons). * When working from home once a week, I have to click away all appointments that have been there since last starting kontact on this machine. (This is not a delay use case, but... I mention it because:) The old kontact/korgac saved the delay in the internal memory and did not sync it on the machine. A property what would really improve the situation would be to sync the fire time of reminders to the servers and thus also record a potential new delay . So in @Flossy Cat's use case a delay for 3 days or so would be in the backup and also working across synced machines. I am not sure if the current status of the iCalender format - which is often used nowadays - allows it. It might. ## User Interface What about if the desktop notifications bring up a special korganizer/kontact view that holds all fired alarms for appointments, tasks and so on with options that allow at least what the old overview did and a compact overview? (Just an idea.) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 481024] The loss of user-defined snoozing for calendar and todo reminders is a massive functional regression and actually a hard show-stopper for my kontact usage
https://bugs.kde.org/show_bug.cgi?id=481024 Bernhard E. Reiter changed: What|Removed |Added CC||bernh...@intevation.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480896] New: Wenn ich die Gesichter Manuell zuordnen will stürzt das Programm permanent ab.
https://bugs.kde.org/show_bug.cgi?id=480896 Bug ID: 480896 Summary: Wenn ich die Gesichter Manuell zuordnen will stürzt das Programm permanent ab. Classification: Applications Product: digikam Version: 8.2.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Database-Faces Assignee: digikam-bugs-n...@kde.org Reporter: bernhard-f...@t-online.de Target Milestone: --- 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. 2. 3. OBSERVED RESULT 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.
[kmail2] [Bug 479851] Allow for a single text/html part to be saved decoded (as html file)
https://bugs.kde.org/show_bug.cgi?id=479851 --- Comment #3 from Bernhard E. Reiter --- (In reply to Paul Schwabauer from comment #2) > Currently, it is possible to save emails as mbox files by right-clicking on > the message → "Save message". > This opens a file dialog with the only possibility to filter for `.mbox` > files. My proposal is to extend the filter to `.html` files and save the > HTML part if the file extension is `.html`. But won't this be a different semantic, saving a full email against saving just one body part? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 479851] Allow for a single text/html part to be saved decoded (as html file)
https://bugs.kde.org/show_bug.cgi?id=479851 --- Comment #1 from Bernhard E. Reiter --- A sister case is https://bugs.kde.org/show_bug.cgi?id=126130 for exporting a full email including everything as html. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 126130] [feature-request] add ability to save-as HTML
https://bugs.kde.org/show_bug.cgi?id=126130 --- Comment #13 from Bernhard E. Reiter --- Split out the save text/html part into https://bugs.kde.org/show_bug.cgi?id=479851 (Still this stays "confirmed" for kmail2 as I found no way to _export_ a full email as html.) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 479851] New: Allow for a single text/html part to be saved decoded (as html file)
https://bugs.kde.org/show_bug.cgi?id=479851 Bug ID: 479851 Summary: Allow for a single text/html part to be saved decoded (as html file) Classification: Applications Product: kmail2 Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: bernh...@intevation.de Target Milestone: --- The use case is: Robin wants to save an HTML email to a file to open it with their favourite web browser, either to be more secure or to profit from the credentials saved in the particular browser. With an email with a single main Content-type: text/html, there is no way (I could find) to save this content as HTML file. Right now there is no attachment shown in the header and even in the email structure view there is no context menu (and thus no "save as" entry in the contect menu). Also the "Save attachments" functionality on the email does not work as it says: There is no attachment. How to reproduce: * Get hold of an email with only one Content-Type: text/html as main contents. * Display it with Kmail (reproduced with kmail2 5.24.4 (23.08.4)) * Try right click on the message, "Save Attachments". -> Observed: does not work with a message: there is no attachment Expected: Should work and ask for a .html filename. * Enable email structure view * right click on the main part -> Observed: no context menu -> expected: context menu that offers working "open" and "save-as" menu entries beside the common ones -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 126130] [feature-request] add ability to save-as HTML
https://bugs.kde.org/show_bug.cgi?id=126130 --- Comment #12 from Bernhard E. Reiter --- Okay, I start wondering, maybe I am in the wrong use case here. If the original reported wanted an export for the full email as HTML then it would include headers and different MIME parts. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 126130] [feature-request] add ability to save-as HTML
https://bugs.kde.org/show_bug.cgi?id=126130 --- Comment #11 from Bernhard E. Reiter --- With 5.24.4 it is still a problem. With an email with Content-type: text/html, there is no way (I could find) to save this as HTML file. The use case is: Robin wants to save an HTML email to a file to open it with their favourite web browser, either to be more secure or to profit from the credentials saved in the particular browser. Right now there is no attachment shown and even in the email structure view there is no context menu (and this no save as entry in the contect menu). Also the "Save attachments" functionality does not work as it says: There is no attachment. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 126130] [feature-request] add ability to save-as HTML
https://bugs.kde.org/show_bug.cgi?id=126130 Bernhard E. Reiter changed: What|Removed |Added Version|4.9.3 |5.24.4 CC||bernh...@intevation.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476047] New: Ctrl+Meta zooming broken with touchpads
https://bugs.kde.org/show_bug.cgi?id=476047 Bug ID: 476047 Summary: Ctrl+Meta zooming broken with touchpads Classification: Plasma Product: kwin Version: 5.27.9 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: micraf...@gmail.com Target Milestone: --- SUMMARY When using a "pixel scrolling"[0] touchpad zooming in/magnifying your desktop is pretty much broken STEPS TO REPRODUCE 1. Get a touchpad with pixel scrolling, or a mouse with high-res scrolling 2. Hold Ctrl+Meta 3. Try zooming in OBSERVED RESULT If you scroll slowly it does not zoom in. You have to scroll really fast, to the point where you pretty much have no control anymore. I'm pretty sure this is caused by ignoring the distance value of the scroll events, I've seen very similar bug in other apps before. I don't know if this is caused by running on wayland, but it didn't happen in the past when I was on xorg. EXPECTED RESULT It should zoom in "pixel by pixel", just like it does for scrolling in applications. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.1.59-1-lts (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP ENVY x360 Convertible 15-ee0xxx System Version: Type1ProductConfigId [0] https://community.kde.org/Get_Involved/Design/Frequently_Discussed_Topics#Names_of_different_scrolling_effects -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432121] fast scrolling on page number glitches/does not scroll at all
https://bugs.kde.org/show_bug.cgi?id=432121 --- Comment #4 from Bernhard --- I just want to throw in that that the problem still exists, and is much worse with most modern high-res touchpads (which support pixel scrolling), because it's almost impossible to "scroll slowly". Touchpads continuously generates scrolling events, they should instead be accumulated until a full "line" has been scrolled instead of trying to scroll a full page for each pixel scrolled -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390082] Application Dashboard leaks graphics memory (glitched background) with multiple displays
https://bugs.kde.org/show_bug.cgi?id=390082 Bernhard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Bernhard --- Seems fixed -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 432130] high-res/non-integer scrolling clashes BAD with font hinting/icons
https://bugs.kde.org/show_bug.cgi?id=432130 Bernhard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Bernhard --- This seems fixed now (and for a while) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473602] Konsole crashing when coming back from sleep (upon switching computers on KVM)
https://bugs.kde.org/show_bug.cgi?id=473602
Bernhard Übelacker changed:
What|Removed |Added
Product|konsole |kwin
Assignee|konsole-de...@kde.org |kwin-bugs-n...@kde.org
Version|23.04.3 |5.27.5
Component|general |general
--- Comment #3 from Bernhard Übelacker ---
Hello, I hope it is ok to change this bug to kwin.
Bottom line is:
kwin_x11 creates from this geometry {xp = 4, yp = 28, w = -8, h = -32} an event
with dimensions 65528 x 65504.
Would following modification be acceptable?
> --- kwin-5.27.5.orig/src/x11window.cpp
> +++ kwin-5.27.5/src/x11window.cpp
> @@ -3786,8 +3786,8 @@ void X11Window::sendSyntheticConfigureNo
> -u.event.width = Xcb::toXNative(m_clientGeometry.width());
> -u.event.height = Xcb::toXNative(m_clientGeometry.height());
> +u.event.width = Xcb::toXNative(std::max(0.0, m_clientGeometry.width()));
> +u.event.height = Xcb::toXNative(std::max(0.0,
> m_clientGeometry.height()));
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 461723] konsole (or other applications) crash at disabling second screen
https://bugs.kde.org/show_bug.cgi?id=461723 --- Comment #13 from Bernhard Übelacker --- Hello, unfortunately this Qt upstream modifiction seems not to avoid this issue. Further debugging leads to kwin_x11 as causing this, details added in https://bugs.kde.org/show_bug.cgi?id=473602 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463475] Konsole crashes when monitor goes to sleep
https://bugs.kde.org/show_bug.cgi?id=463475 --- Comment #29 from Bernhard Übelacker --- Added some details about the possible source of this problematic huge dimensions to https://bugs.kde.org/show_bug.cgi?id=473602. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473602] Konsole crashing when coming back from sleep (upon switching computers on KVM)
https://bugs.kde.org/show_bug.cgi?id=473602
Bernhard Übelacker changed:
What|Removed |Added
CC||bernha...@mailbox.org
--- Comment #1 from Bernhard Übelacker ---
Hello,
I receive this fault every now and then.
I just found fullscreen processes crashing, therefore as a workaround it helps
to not make windows fullscreen,
instead leave it a little smaller.
I received these crashes either when enabling or disabling one of my two
screens, or when screens wakeup after energy saving.
My setup are two screens of different brand, therefore maybe different reaction
times. Different size but same resolution.
The right screen is the main one, the left currently disabled.
I report this issue some time ago in #461723 and brought this to the attention
of Qt developers
in https://bugreports.qt.io/browse/QTBUG-109226 .
They fixed some flaw, but this issue unfortunately remained active.
I found now again some time for a deeper look and found following before the
crash:
(with modified Qt library to output details of XCB_CONFIGURE_NOTIFY)
> export QT_LOGGING_RULES=qt.qpa.*=true
> gwenview picture.png
> ...
> qt.qpa.events: Event | XCB_CONFIGURE_NOTIFY(22) | sequence: 961 |
> 4-28-65528-65504
> qt.qpa.xcb: [ QWidgetWindow(0x556124696730, name="MainWindow#1Window") ]
> creating shared memory 17169384448 bytes for QSize(65528, 65504) depth 24
> bits 32
> qt.qpa.xcb: xcb_shm_create_segment() can't be called for size 17169384448,
> maximumallowed size is 4294967295
> ...
> 10 -- signal=11
> ...
> KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
This huge resolution of 65528 width and 65504 height I could follow back to an
event XCB_CONFIGURE_NOTIFY
read from the X11 socket /tmp/.X11-unix/X0 in _xcb_in_read.
I suspected this might originate from kwin_x11 - and there function
X11Window::sendSyntheticConfigureNotify could fit.
And below I found m_clientGeometry got negative values for width and heigth,
which looks like it gets interpreted as a 16-bit unsigned int. (-32 == 0xffe0
== 65504).
Should therefore this issue be reassigned to kwin?
> Thread 1 hit Breakpoint 3, KWin::X11Window::sendSyntheticConfigureNotify
> (this=this@entry=0x557d9d033db0) at ./src/x11window.cpp:3791
> 3791u.event.border_width = 0;
> (rr) bt
> #0 KWin::X11Window::sendSyntheticConfigureNotify()
> (this=this@entry=0x557d9d033db0) at ./src/x11window.cpp:3791
> #1 0x7f9ffab7b961 in KWin::X11Window::updateServerGeometry()
> (this=this@entry=0x557d9d033db0) at ./src/x11window.cpp:4270
> #2 0x7f9ffab7fdf9 in KWin::X11Window::moveResizeInternal(QRectF const&,
> KWin::Window::MoveResizeMode) (this=0x557d9d033db0, rect=,
> mode=KWin::Window::MoveResizeMode::MoveResize) at ./src/x11window.cpp:4215
> #3 0x7f9ffaa8626c in KWin::PlacementTracker::restore(QString const&)
> (this=this@entry=0x7f9fd4011660, key=...) at ./src/placementtracker.cpp:110
> #4 0x7f9ffab6165a in KWin::Workspace::desktopResized()
> (this=this@entry=0x557d95264b30) at ./src/workspace.cpp:2251
> ...
> (rr) print this->m_clientGeometry
> $5 = {xp = 4, yp = 28, w = -8, h = -32}
> (rr) print u.event.width
> $6 = 65528
> (rr) print u.event.height
> $7 = 65504
> (rr) list
> 3784u.event.response_type = XCB_CONFIGURE_NOTIFY;
> 3785u.event.event = window();
> 3786u.event.window = window();
> 3787u.event.x = Xcb::toXNative(m_clientGeometry.x());
> 3788u.event.y = Xcb::toXNative(m_clientGeometry.y());
> 3789u.event.width = Xcb::toXNative(m_clientGeometry.width());
> 3790u.event.height = Xcb::toXNative(m_clientGeometry.height());
> 3791u.event.border_width = 0;
> 3792u.event.above_sibling = XCB_WINDOW_NONE;
> 3793u.event.override_redirect = 0;
> 3794xcb_send_event(kwinApp()->x11Connection(), true, c.event,
> XCB_EVENT_MASK_STRUCTURE_NOTIFY, reinterpret_cast());
I suspect #464967 and #463475 are open duplicates to this bug.
Another small note: also non-Qt applications like gitk are sometimes affected
and crash with an X error.
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 473292] New: Installing with KDE_INSTALL_USE_QT_SYS_PATHS=ON with both BUILD_QT5 and BUILD_QT6 installs to wrong locations
https://bugs.kde.org/show_bug.cgi?id=473292 Bug ID: 473292 Summary: Installing with KDE_INSTALL_USE_QT_SYS_PATHS=ON with both BUILD_QT5 and BUILD_QT6 installs to wrong locations Classification: Plasma Product: Breeze Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: b...@lindev.ch CC: uhh...@gmail.com Target Milestone: --- SUMMARY Installing Breeze (master as of 2023/08/11) with KDE_INSTALL_USE_QT_SYS_PATHS=ON and both BUILD_QT5 and BUILD_QT6 enabled installs qt6 plugins to qt5's plugin directories STEPS TO REPRODUCE 1. Install Qt5 and Qt6, in different prefixes (e.g. /usr/lib64/qt5 and /usr/lib64/qt6) 2. Build breeze with -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DBUILD_QT5=ON -DBUILD_QT6=ON 3. make install OBSERVED RESULT Qt6 plugins are installed into qt5 library directories, e.g. /usr/lib64/qt5/plugins/org.kde.kdecoration2.kcm/kcm_breezedecoration.so /usr/lib64/qt5/plugins/org.kde.kdecoration2/org.kde.breeze.so /usr/lib64/qt5/plugins/styles/breeze5.so /usr/lib64/qt5/plugins/styles/breeze6.so Qt5 plugins are installed into the correct directory. EXPECTED RESULT Qt5 plugins are installed into Qt5 directories, Qt6 plugins into Qt6 directories. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenMandriva Cooker (available in About System) KDE Plasma Version: Plasma 5 5.27.7 and Plasma 6 git snapshot from today KDE Frameworks Version: KF5 5.108 and KF6 snapshot from today Qt Version: 5.15.10 with KDE patches and 6.6.0-beta1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472426] Enable checking if OpenPGP encryption is possible by default
https://bugs.kde.org/show_bug.cgi?id=472426 --- Comment #1 from Bernhard E. Reiter --- Maybe the label of the option "Automatically encrypt messages when possible" is suboptimal because it does not mention the checking part (like trying to get the pubkey in the local storage via WKD or otherwise). Maybe it is an improvement to say: "Check if we can encrypt to recipients and enable encryption for an email if possible for all." or "Check if recipients offer to encrypt to them. Suggest to encrypt for an email automatically if possible". Both would explain better that there are two steps and that the suggestion can be ignored, by deselecting the encryption setting later. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472426] Enable checking if OpenPGP encryption is possible by default
https://bugs.kde.org/show_bug.cgi?id=472426 Bernhard E. Reiter changed: What|Removed |Added Summary|Enable OpenPGP encryption |Enable checking if OpenPGP |by default |encryption is possible by ||default -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 452296] Email won't be encrypted automatically
https://bugs.kde.org/show_bug.cgi?id=452296 --- Comment #2 from Bernhard E. Reiter --- I think maybe https://bugs.kde.org/show_bug.cgi?id=472426 (Enable OpenPGP encryption by default) is better aiming in what this issues was intended to do. :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472426] New: Enable OpenPGP encryption by default
https://bugs.kde.org/show_bug.cgi?id=472426 Bug ID: 472426 Summary: Enable OpenPGP encryption by default Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: bernh...@intevation.de Target Milestone: --- KMail shall enable encryption in the default configuration if my recipients want to get emails encrypted to them by OpenPGP/MIME. Many recipients that want to receive encrypted emails, publish their public OpenPGP via the web key directory standard (WKD). KMail shall check if they did. The can be enabled by the identity option: Automatically encrypt messages when possible" as shown with: https://wiki.gnupg.org/EMailClients/KMail STEPS TO REPRODUCE 1. on a fresh account start kmail with vanilla settings, add an email account. be online. 2. open an new email 3. enter an email address for someone that has their OpenPGP pubkey published via WKD (e.g. mine at bernhard.rei...@intevation.de) Variant for 1: use an old account with a newer kmail. Expectation: KMail asks the user once that it enables the option during migration. OBSERVED RESULT Encryption is not enabled, it is not shown that this recipient offers to send them encrypted email. EXPECTED RESULT The indicator before the email address shows the public keys indication by the little icons. The encrypt button is enabled. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 428373] "Examining (Failed)" notifications some times when trying to save in folders with many files.
https://bugs.kde.org/show_bug.cgi?id=428373 Bernhard Lindner changed: What|Removed |Added CC||priv...@bernhard-lindner.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463475] Konsole crashes when monitor goes to sleep
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #28 from Bernhard Übelacker ---
Some short additions:
- I am getting this with X server.
The resize event way up in the stack looks like
the new width should change from 1920 to 65528 and the height from 996 to
65504.
With 4 bytes per pixel this would explain the later `dstBytesPerLine=262112`.
Having a buffer with this dimensions in memory would need ~16 GB.
#8 copy_unswapped (..., dstBytesPerLine=262112, ...) at
./src/plugins/platforms/xcb/qxcbbackingstore.cpp:547
...
#18 0x7fa7f3bbd421 in QWidgetWindow::handleResizeEvent () at
kernel/qwidgetwindow.cpp:841
(gdb) print event->s
$4 = {wd = 65528, ht = 65504}
(gdb) print event->olds
$5 = {wd = 1920, ht = 996}
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 463475] Konsole crashes when monitor goes to sleep
https://bugs.kde.org/show_bug.cgi?id=463475 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #27 from Bernhard Übelacker --- The same crash I reported already in: https://bugs.kde.org/show_bug.cgi?id=461723 Which led to this Qt bug report: https://bugreports.qt.io/browse/QTBUG-109226 Unfortunately this change in Qt did not reach the 5.15 branch? https://code.qt.io/cgit/qt/qtbase.git/commit/src/plugins/platforms/xcb/qxcbwindow.cpp?id=6a3627b6c5aa5109a80024f3d7b0f938504f7ffe But it made it at least into the Debian package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025997 https://sources.debian.org/src/qtbase-opensource-src/5.15.10%2Bdfsg-1/debian/patches/qxcbwindow_set_geometry.diff/ But the bad thing is, I still receive this crash with the Debian package (yesterday with kate). Therefore this patch is not sufficient. Other notes: - This happens for me just for just for maximized windows. As a workaround having them just near full screen seems avoiding the crash. - My last crash was with two monitors connected, but one was switched off. (Monitors of different brand, different size, same resolution.) - Initially I reported it when doing explicit changes to dual monitor setup, but the last crash was when monitor just went to standby and woke up again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465858] shift + drag does not interact with the tiling layout if Both Shifts together enable Caps Lock
https://bugs.kde.org/show_bug.cgi?id=465858 Bernhard Scheirle changed: What|Removed |Added CC||bernhard+...@scheirle.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466544] New: Natural sorting of numbes does not work in folderview
https://bugs.kde.org/show_bug.cgi?id=466544 Bug ID: 466544 Summary: Natural sorting of numbes does not work in folderview Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: micraf...@gmail.com CC: h...@kde.org Target Milestone: 1.0 SUMMARY Folderview doesn't use natural sorting STEPS TO REPRODUCE 1. Rename >=10 files in dolphin simultaneously 2. Create a folderview of the parent dir (sort by name) OBSERVED RESULT Numbers are not sorted consecutively (1, 10, 2, ...) EXPECTED RESULT Sorting should match dolphin exactly, which does have natural sorting Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-60-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 466401] New: Reproducable crash when typing in search field
https://bugs.kde.org/show_bug.cgi?id=466401 Bug ID: 466401 Summary: Reproducable crash when typing in search field Classification: Applications Product: amarok Version: 2.9.71 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: kdeb...@pohl-eifel.de Target Milestone: kf5 Application: amarok (2.9.71) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: PC booted, Amarok started, try to search in local media collection -> crash The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault [KCrash Handler] #4 0x7f3712e4001e in CollectionTreeItem::row() const () at /lib64/libamaroklib.so.1 #5 0x7f3712e4e850 in CollectionTreeItemModelBase::itemIndex(CollectionTreeItem*) const () at /lib64/libamaroklib.so.1 #6 0x7f3712e43340 in CollectionTreeItemModelBase::parent(QModelIndex const&) const () at /lib64/libamaroklib.so.1 #7 0x7f37118b09b1 in () at /lib64/libQt5Core.so.5 #8 0x7f371191360c in () at /lib64/libQt5Core.so.5 #9 0x7f371187628c in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /lib64/libQt5Core.so.5 #10 0x7f3712e50103 in CollectionTreeItemModelBase::tracksLoaded(AmarokSharedPointer const&, QModelIndex const&, QList > const&) () at /lib64/libamaroklib.so.1 #11 0x7f3711907d00 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #12 0x7f37125a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f37118dc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7f37118df181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #15 0x7f3711934413 in () at /lib64/libQt5Core.so.5 #16 0x7f370e71ba90 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #17 0x7f370e71be48 in () at /lib64/libglib-2.0.so.0 #18 0x7f370e71bedc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #19 0x7f3711933c16 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #20 0x7f37118dac5b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #21 0x7f37118e2dc6 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #22 0x55f9cda3ff76 in () #23 0x7f371102caf0 in __libc_start_call_main () at /lib64/libc.so.6 #24 0x7f371102cbb9 in __libc_start_main_impl () at /lib64/libc.so.6 #25 0x55f9cda40805 in () [Inferior 1 (process 2662) detached] The reporter indicates this bug may be a duplicate of or related to bug 440801. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 465105] New: Reminding an hour off (for recurring events)
https://bugs.kde.org/show_bug.cgi?id=465105 Bug ID: 465105 Summary: Reminding an hour off (for recurring events) Classification: Frameworks and Libraries Product: Reminder Daemon Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bernh...@intevation.de Target Milestone: --- For some appointements I get reminded an hour off. My guess is that those are recurring events that have been created in a different daylight saving time and they cross the daylight saving date. The events are shown with their correct time in Kontact(Korganizer). Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 rpm -qa | grep korganizer- korganizer-22.12.0-lp153.210.1.x86_64 korganizer --version korganizer 5.22.0 (22.12.0) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464855] Search function sometimes has erratic behavior.
https://bugs.kde.org/show_bug.cgi?id=464855 Bernhard Kölbl changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464855] New: Search function sometimes has erratic behavior.
https://bugs.kde.org/show_bug.cgi?id=464855 Bug ID: 464855 Summary: Search function sometimes has erratic behavior. Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: bese...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY When searching in the application launcher, the selected entry sometimes makes erratic jumps to some lower listed entries. STEPS TO REPRODUCE 1. Press meta key. 2. Start searching for, for example Discord, or Firefox. 3. The behavior is usually experienced after 3-5 key presses. OBSERVED RESULT The first few keypresses still highlight the topmost result, but after 3-5 keystrokes the search usually jumps to a way lower listed result. EXPECTED RESULT The topmost result should stay selected except you press the arrow keys. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82RA System Version: IdeaPad Flex 5 16ALC7 ADDITIONAL INFORMATION Sadly, this bug isn't really easy to reproduce. Many times it seems to happen when external drives are being indexed / shortly after mounting them. Like today the launcher would usually jump to files form an encrypted drive I mounted right before searching. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 463576] "Check For update" cause the crash for kded5 under Debian testing branch (apper segfault in Transaction::role() )
https://bugs.kde.org/show_bug.cgi?id=463576 --- Comment #4 from Bernhard Übelacker --- Bug #462706 states this to be no issue in kded framework and closed RESOLVED UPSTREAM. Therefore this issue was opened: https://github.com/PackageKit/PackageKit-Qt/issues/42 There it was stated that "TransactionWatcher.cpp comes from apper". And the events described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026062#35 might boil down to this question: Is it allowed for packagekit-qt to call deleteLater while still in the constructor (as far as I see it fails because it has role Transaction::RoleUnknown), or has TransactionWatcher to cope with this and e.g. not store such a "failed" Transaction in m_transactions? -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 463576] "Check For update" cause the crash for kded5 under Debian testing branch (apper segfault in Transaction::role() )
https://bugs.kde.org/show_bug.cgi?id=463576 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #3 from Bernhard Übelacker --- > #4 0x7f555e391f90 in () at > /lib/x86_64-linux-gnu/libc.so.6 > #5 0x7f5508377ba4 in PackageKit::Transaction::role() const () at > ./src/transaction.cpp:297 > #6 0x7f550880daae in > TransactionWatcher::watchTransaction(QDBusObjectPath const&, bool) () at > ./apperd/TransactionWatcher.cpp:104 > #7 0x7f550880db99 in > TransactionWatcher::transactionListChanged(QStringList const&) () at > ./apperd/TransactionWatcher.cpp:85 > ... That backtrace looks similar to bug #462706 or bug #463626. And at Debian side: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026062 -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 463626] KDED: Job Failed
https://bugs.kde.org/show_bug.cgi?id=463626 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #1 from Bernhard Übelacker --- This might be a duplicate of bug #462706 ? -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 462706] Since updating to 5.100 kded segfaults in Packagekit (likely during update check)
https://bugs.kde.org/show_bug.cgi?id=462706 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #3 from Bernhard Übelacker --- I tried to bring this to the attention of packagekit-qt developers in this bug report: https://github.com/PackageKit/PackageKit-Qt/issues/42 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463052] Krita crashes on double free when closing application
https://bugs.kde.org/show_bug.cgi?id=463052 --- Comment #1 from Bernhard Übelacker --- Overnight a local Debian package built of 5.1.3 finished with my mentioned change, and this one does really no longer crashes. For some reason also this night, the Debian Maintainer uploaded a new version 5.1.4, which states to fix this bug, too. This is really the case in my test environment. I failed to add in my previous information the output to stdout, especially important because of the "Duplicated profile" messages in 5.1.3, which are no longer visible with this new 5.1.4. 5.1.3: $ krita $ krita Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' krita.lib.pigment: Duplicated profile "Artifex PS CMYK Profile" "/usr/share/color/icc/ghostscript/gray_to_k.icc" "" Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' krita.lib.pigment: Duplicated profile "Artifex PS CMYK Profile" "/usr/share/color/icc/ghostscript/ps_cmyk.icc" "/usr/share/color/icc/ghostscript/gray_to_k.icc" Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' krita.lib.pigment: Duplicated profile "Artifex Software sRGB ICC Profile" "/usr/share/color/icc/ghostscript/srgb.icc" "/usr/share/color/icc/ghostscript/default_rgb.icc" krita.lib.pigment: Replacing color space factory "LABA" "L*a*b*/Alpha (16-bit integer/channel)" with "LABA" "L*a*b* (16-bit integer/channel, unmanaged)" krita.lib.pigment: Replacing color space factory "RGBA" "RGB/Alpha (8-bit integer/channel)" with "RGBA" "RGB (8-bit integer/channel, unmanaged)" krita.lib.pigment: Replacing color space factory "RGBA16" "RGB/Alpha (16-bit integer/channel)" with "RGBA16" "RGB (16-bit integer/channel, unmanaged)" QObject::startTimer: Timers cannot have negative intervals /usr/lib/x86_64-linux-gnu/krita-python-libs/krita added to PYTHONPATH Lcms2 error: 13 LUT is not suitable to be saved as LutBToA Lcms2 error: 7 Couldn't write type 'mBA ' 19 -- exe=/usr/bin/krita 14 -- appname=krita 17 -- apppath=/usr/bin 10 -- signal=11 10 -- pid=42710 12 -- startupid=0 KCrash: crashing... crashRecursionCounter = 2 ... $ 5.1.4: $ krita QObject::startTimer: Timers cannot have negative intervals /usr/lib/x86_64-linux-gnu/krita-python-libs/krita added to PYTHONPATH $ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463052] New: Krita crashes on double free when closing application
https://bugs.kde.org/show_bug.cgi?id=463052
Bug ID: 463052
Summary: Krita crashes on double free when closing application
Classification: Applications
Product: krita
Version: 5.1.3
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: * Unknown
Assignee: krita-bugs-n...@kde.org
Reporter: bernha...@mailbox.org
Target Milestone: ---
I tried investigating on Debian Bug https://bugs.debian.org/1025104.
And I could reproduce it in a i386 and amd64 VM.
The crash happens when main is already left and the exit handlers get executed:
Thread 1 received signal SIGSEGV, Segmentation fault.
0x7fd65c0bef73 in KoColorProfileStorage::Private::~Private
(this=0x557d2d687090, __in_chrg=) at
./libs/pigment/KoColorProfileStorage.cpp:42
42 delete p;
1: x/i $pc
=> 0x7fd65c0bef73 <_ZN21KoColorProfileStorage7PrivateD2Ev+787>: call
*0x8(%rax)
(rr) bt
#0 0x7fd65c0bef73 in KoColorProfileStorage::Private::~Private()
(this=0x557d2d687090, __in_chrg=) at
./libs/pigment/KoColorProfileStorage.cpp:42
#1 0x7fd65c0bcf71 in
QScopedPointerDeleter::cleanup(KoColorProfileStorage::Private*)
(pointer=0x557d2d687090) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:60
#2
QScopedPointerDeleter::cleanup(KoColorProfileStorage::Private*)
(pointer=0x557d2d687090) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:52
#3 QScopedPointer >::~QScopedPointer()
(this=, __in_chrg=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:107
#4 KoColorProfileStorage::~KoColorProfileStorage() (this=,
__in_chrg=) at ./libs/pigment/KoColorProfileStorage.cpp:56
#5 0x7fd65c0b531d in KoColorSpaceRegistry::Private::~Private()
(this=0x557d2d563d40, __in_chrg=) at
./libs/pigment/KoColorSpaceRegistry.cpp:42
#6 KoColorSpaceRegistry::~KoColorSpaceRegistry() (this=0x7fd65c3841f0
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>,
__in_chrg=) at ./libs/pigment/KoColorSpaceRegistry.cpp:232
#7 0x7fd65c0b5519 in Holder::~Holder() (this=,
__in_chrg=) at ./libs/pigment/KoColorSpaceRegistry.cpp:39
#8 0x7fd65e2fa435 in __run_exit_handlers (status=0, listp=0x7fd65e48e820
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:113
#9 0x7fd65e2fa5aa in __GI_exit (status=) at
./stdlib/exit.c:143
#10 0x7fd65e2e3191 in __libc_start_call_main
(main=main@entry=0x557d2c4544c0 , argc=argc@entry=1,
argv=argv@entry=0x7ffdc9b620f8) at ../sysdeps/nptl/libc_start_call_main.h:74
#11 0x7fd65e2e3245 in __libc_start_main_impl (main=0x557d2c4544c0
, argc=1, argv=0x7ffdc9b620f8, init=,
fini=, rtld_fini=, stack_end=0x7ffdc9b620e8) at
../csu/libc-start.c:381
#12 0x557d2c458271 in _start ()
(rr) list
30 ~Private()
31 {
32 Q_FOREACH (KoColorProfile *p, profileMap) {
33 profileUniqueIdMap.remove(p->uniqueId());
34 delete p;
35 }
36 profileMap.clear();
37 Q_FOREACH (KoColorProfile *p, profileUniqueIdMap) {
38 delete p;
39 }
40 profileUniqueIdMap.clear();
41 Q_FOREACH(KoColorProfile *p, duplicates) {
42 delete p;
43 }
44 duplicates.clear();
45 }
Valgrind brought this to the point as double free:
==6079== Invalid read of size 4
==6079==at 0x7AC33A8: KoColorProfileStorage::Private::~Private()
(KoColorProfileStorage.cpp:42)
==6079==by 0x7AC12D2: cleanup (qscopedpointer.h:60)
==6079==by 0x7AC12D2: cleanup (qscopedpointer.h:52)
==6079==by 0x7AC12D2: ~QScopedPointer (qscopedpointer.h:107)
==6079==by 0x7AC12D2: KoColorProfileStorage::~KoColorProfileStorage()
(KoColorProfileStorage.cpp:56)
==6079==by 0x7AB8CE6: ~Private (KoColorSpaceRegistry.cpp:42)
==6079==by 0x7AB8CE6: KoColorSpaceRegistry::~KoColorSpaceRegistry()
(KoColorSpaceRegistry.cpp:232)
==6079==by 0x7AB8F07: (anonymous
namespace)::Q_QGS_s_instance::innerFunction()::Holder::~Holder()
(KoColorSpaceRegistry.cpp:39)
==6079==by 0x70D7B5A: __run_exit_handlers (exit.c:89)
==6079==by 0x70D7CB0: exit (exit.c:143)
==6079==by 0x70BF2A0: (below main) (libc_start_call_main.h:74)
==6079== Address 0xdfb8a18 is 0 bytes inside a block of size 8 free'd
==6079==at 0x48436C7: operator delete(void*, unsigned int)
(vg_replace_malloc.c:929)
==6079==by 0x7C6A74B: KoDummyColorProfile::~KoDummyColorProfile()
(KoDummyColorProfile.cpp:16)
==6079==by 0x7AC314B: KoColorProfileStorage::Private::~Private()
(KoColorProfileStorage.cpp:34)
==6079==by 0x7AC12D2: cleanup (qscopedpointer.h:60)
==6079==by 0x7AC12D2: cleanup (qscopedpointer.h:52)
==6079==by 0x7AC12D2: ~QScopedPointer (qscopedpointer.h:107)
==6079==by 0x7AC12D2:
[yakuake] [Bug 462487] Crash after terminal show
https://bugs.kde.org/show_bug.cgi?id=462487 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #1 from Bernhard Übelacker --- Backtrace looks similar to bug #461723. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462022] Konsole (first time) suddenly crashes when aligning to the right of my second monitor
https://bugs.kde.org/show_bug.cgi?id=462022 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #1 from Bernhard Übelacker --- Backtrace looks similar to bug #461723. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451110] Apps crash when I minimize windows to latte
https://bugs.kde.org/show_bug.cgi?id=451110 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #1 from Bernhard Übelacker --- Backtrace looks similar to bug #461723. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461723] konsole (or other applications) crash at disabling second screen
https://bugs.kde.org/show_bug.cgi?id=461723 --- Comment #3 from Bernhard Übelacker --- Hello, upstream bug QTBUG-109226 got closed now with a commit: qtbase/dev: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=6a3627b6c5aa5109a80024f3d7b0f938504f7ffe qtbase/6.4: https://code.qt.io/cgit/qt/qtbase.git/commit/?h=6.4=003d30fac2a75ee5f942917dbd4901536a742cbc Unfortunately it looks like the qt-5.15 cerry-pick is not publicly visible ... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461723] konsole (or other applications) crash at disabling second screen
https://bugs.kde.org/show_bug.cgi?id=461723 --- Comment #2 from Bernhard Übelacker --- Hello Nate, thanks for looking into this report. I opened now https://bugreports.qt.io/browse/QTBUG-109226 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399029] unwanted replacement for my identity in header view of message list
https://bugs.kde.org/show_bug.cgi?id=399029 --- Comment #5 from Bernhard Schiffner --- Thanks Justin for touching this old bug. It is per today (2022-12-05) still active / reproduceable / annoying. The main problem occurs when copying (^C) an email into an other document. You can't see on later reading who (the long identity) wrote the mail in question. I usea quite recent KDE NEON on different PC with different accounts and it happens regularily. In the time since, I digged into the code of kmail, but with no success ... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399029] unwanted replacement for my identity in header view of message list
https://bugs.kde.org/show_bug.cgi?id=399029 Bernhard Schiffner changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #25 from Bernhard Übelacker --- (In reply to Bernhard Übelacker from comment #24) > Thread 1 in each process seem to be middle in some processing, plasmashell > waiting for some mutex, kwin_x11 for some xcb request. Tried to look a little further in plasmashell process. It looks like thread 1 is inside some QSGThreadedRenderLoop and is waiting to be woken by some other thread: Thread 1 (Thread 0x7fd89f10aa00 (LWP 1857)): ... #4 ___pthread_cond_wait (cond=0x7fd87006c068, mutex=0x7fd87006c040) at ./nptl/pthread_cond_wait.c:618 #5 0x7fd8a3cd199b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x7fd87006c040) at thread/qwaitcondition_unix.cpp:146 #6 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x7fd87008b428, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7fd8a5a0b968 in QSGThreadedRenderLoop::polishAndSync(QSGThreadedRenderLoop::Window*, bool) (this=this@entry=0x7fd898007220, w=w@entry=0x7fd8980319a0, inExpose=inExpose@entry=true) at scenegraph/qsgthreadedrenderloop.cpp:1603 #8 0x7fd8a5a0cc23 in QSGThreadedRenderLoop::handleExposure(QQuickWindow*) (this=0x7fd898007220, window=) at scenegraph/qsgthreadedrenderloop.cpp:1374 ... https://sources.debian.org/src/qtdeclarative-opensource-src/5.15.6%2Bdfsg-2/src/quick/scenegraph/qsgthreadedrenderloop.cpp/#L1603 1603 w->thread->waitCondition.wait(>thread->mutex); https://sources.debian.org/src/qtdeclarative-opensource-src/5.15.6%2Bdfsg-2/src/quick/scenegraph/qsgthreadedrenderloop.cpp/#L1374 1374 polishAndSync(w, true); There are a few other threads executing below `QSGRenderThread::run()` and also waiting ... : ... #6 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x7fd870082768, mutex=mutex@entry=0x7fd870082760, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7fd8a5a07c95 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x7fd870082758) at scenegraph/qsgthreadedrenderloop.cpp:257 #8 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x7fd8700826c0) at scenegraph/qsgthreadedrenderloop.cpp:935 #9 0x7fd8a5a0a0c1 in QSGRenderThread::run() (this=0x7fd8700826c0) at scenegraph/qsgthreadedrenderloop.cpp:1052 ... But there is one thread that seems waiting in plasmashell process also for some xcb reply: (gdb) bt #0 0x7fd8a3b1afef in __GI___poll (fds=fds@entry=0x7fd72e7fa7a8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd8a61a4d12 in poll (__timeout=-1, __nfds=1, __fds=0x7fd72e7fa7a8) at /usr/include/x86_64-linux-gnu/bits/poll2.h:47 #2 _xcb_conn_wait (c=c@entry=0x56038ce45910, cond=cond@entry=0x7fd7180e71c8, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:508 #3 0x7fd8a61a716a in xcb_wait_for_special_event (c=0x56038ce45910, se=0x7fd7180e71a0) at ../../src/xcb_in.c:806 #4 0x7fd89ddf1465 in dri3_wait_for_event_locked (draw=draw@entry=0x7fd7180f5798, full_sequence=full_sequence@entry=0x0) at ../src/loader/loader_dri3_helper.c:584 #5 0x7fd89ddf22a4 in dri3_find_back (draw=draw@entry=0x7fd7180f5798, prefer_a_different=) at ../src/loader/loader_dri3_helper.c:726 #6 0x7fd89ddf3da1 in dri3_get_buffer (format=format@entry=4099, buffer_type=buffer_type@entry=loader_dri3_buffer_back, draw=draw@entry=0x7fd7180f5798, driDrawable=) at ../src/loader/loader_dri3_helper.c:2030 #7 0x7fd89ddf40d3 in loader_dri3_get_buffers (driDrawable=, format=4099, stamp=0x7fd718088720, loaderPrivate=0x7fd7180f5798, buffer_mask=, buffers=0x7fd72e7fab00) at ../src/loader/loader_dri3_helper.c:2255 #8 0x7fd8966ae13f in dri_image_drawable_get_buffers (drawable=drawable@entry=0x7fd718088720, images=images@entry=0x7fd72e7fab00, statts=statts@entry=0x7fd71816ce78, statts_count=statts_count@entry=2) at ../src/gallium/frontends/dri/dri2.c:289 #9 0x7fd8966ae27f in dri2_allocate_textures (ctx=0x56038d312f10, drawable=0x7fd718088720, statts=0x7fd71816ce78, statts_count=2) at ../src/gallium/frontends/dri/dri2.c:458 #10 0x7fd8966b1265 in dri_st_framebuffer_validate (stctx=, stfbi=, statts=0x7fd71816ce78, count=2, out=0x7fd72e7face0) at ../src/gallium/frontends/dri/dri_drawable.c:82 #11 0x7fd896784d62 in st_framebuffer_validate (stfb=stfb@entry=0x7fd71816ca20, st=st@entry=0x56039097e4f0) at ../src/mesa/state_tracker/st_manager.c:238 #12 0x7fd896785405 in st_manager_validate_framebuffers (st=0x56039097e4f0) at ../src/mesa/state_tracker/st_manager.c:1333 #13 0x7fd89675f6ed in st_validate_state (st=st@entry=0x56039097e4f0, pipeline=pipeline@entry=ST_PIPELINE_CLEAR) at ../src/mesa/state_tracker/st_atom.c:231 #14 0x7fd896933314 in st_Clear (ctx=0x5603916d9e70, mask=50) at ../src/mesa/state_tracker/st_cb_clear.c:432 #15 0x7fd8a59af885 in QSGBatchRenderer::Renderer::renderBatches() (this=this@entry=0x7fd7180c23a0) at scenegraph/coreapi/qsgbatchrenderer.cpp:4022 #16
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #24 from Bernhard Übelacker --- Created attachment 153835 --> https://bugs.kde.org/attachment.cgi?id=153835=edit plasmashell_and_kwin_x11_thread-apply-bt.txt I notice also such a hang. I left today at 12:05 the system. When I came back at 13:45 the time was stuck at 12:15, and three notifications from kdeconnect where still visible. To me it looks like this hang is likely to happen if kdeconnect is producing multiple notifications fast in a row. I assume this is the case when I changed WLAN accesspoints in this time and my phone is connecting to the new acesspoint. I gathered core dumps of kwin_x11 and plasmashell. Attached is a `thread apply all bt`, but there are many threads in each and am not sure which one is supposed to do something. Most of them are waiting for something, but I cannot say for what. If wanted, I can add more debug symbols. Thread 1 in each process seem to be middle in some processing, plasmashell waiting for some mutex, kwin_x11 for some xcb request. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461723] New: konsole (or other applications) crash at disabling second screen
https://bugs.kde.org/show_bug.cgi?id=461723 Bug ID: 461723 Summary: konsole (or other applications) crash at disabling second screen Classification: I don't know Product: kde Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bernha...@mailbox.org Target Milestone: --- Hello, I received a crash of konsole when I disabled a second screen via systemsettings. This screen is left of my main screen and has a lower resolution. The crash looks like caused by a calculation in copy_unswapped, which does some pointer arithmetic, but unfortunately the offset gets negative, and therefore unmapped memory is tried to be accessed. Otherwise it looks like yy might be related to a pixel resolution, but my screens are nowhere near a height of 8256 pixel. I received this crash two weeks ago also in konsole and dolphin. This bug might be a duplicate of Bug 461563 and/or Bug 451110. I collected the cores of the three crashes, so I can lookup somthing if needed. STEPS TO REPRODUCE Unfortunately I did not yet try to reproduce it this time. Last time I could not get it crash when I tried to reproduce it. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-2-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 460 Graphics ADDITIONAL INFORMATION (gdb) bt #0 0x7f009bcfe32f in __GI___poll (fds=0x7ffc26bb9058, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f009d975160 in ?? () from /lib/x86_64-linux-gnu/libKF5Crash.so.5 #2 0x7f009d975b67 in KCrash::defaultCrashHandler(int) () from /lib/x86_64-linux-gnu/libKF5Crash.so.5 #3 #4 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:228 #5 0x7f00962f142a in memmove (__len=262112, __src=0x7efb8bbe8810, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:36 #6 copy_unswapped (rect=..., img=..., dstBytesPerLine=262112, dst=) at ./src/plugins/platforms/xcb/qxcbbackingstore.cpp:547 #7 native_sub_image (swap=false, rect=..., src=..., dstStride=262112, buffer=0x5557a9af9130) at ./src/plugins/platforms/xcb/qxcbbackingstore.cpp:590 #8 QXcbBackingStoreImage::flushPixmap (this=0x5557a9af90b0, region=..., fullRegion=) at ./src/plugins/platforms/xcb/qxcbbackingstore.cpp:669 #9 0x7f00962f1a29 in QXcbBackingStoreImage::flushPixmap (fullRegion=false, region=..., this=0x5557a9af90b0) at ./src/plugins/platforms/xcb/qxcbbackingstore.cpp:627 #10 QXcbBackingStoreImage::put (this=0x5557a9af90b0, dst=85983245, region=..., offset=...) at ./src/plugins/platforms/xcb/qxcbbackingstore.cpp:741 #11 0x7f00962f2369 in QXcbBackingStore::flush (this=this@entry=0x5557a9a3b4d0, window=window@entry=0x5557a98d7c10, region=..., offset=...) at ./src/plugins/platforms/xcb/qxcbwindow.h:128 #12 0x7f009cd017b2 in QBackingStore::flush (this=this@entry=0x5557a9a4f510, region=..., window=0x5557a98d7c10, offset=...) at painting/qbackingstore.cpp:252 #13 0x7f009d37059f in QWidgetRepaintManager::flush (this=this@entry=0x5557a9d8fad0, widget=0x5557a98df320, region=..., widgetTextures=) at kernel/qwidgetrepaintmanager.cpp:1184 #14 0x7f009d372129 in QWidgetRepaintManager::flush (this=0x5557a9d8fad0) at kernel/qwidgetrepaintmanager.cpp:1082 #15 0x7f009d374270 in QWidgetRepaintManager::paintAndFlush (this=0x5557a9d8fad0) at kernel/qwidgetrepaintmanager.cpp:1014 #16 0x7f009d3bd341 in QWidgetWindow::handleResizeEvent (this=0x5557a98d7c10, event=0x7ffc26bba560) at kernel/qwidgetwindow.cpp:841 #17 0x7f009d3c10db in QWidgetWindow::event (this=0x5557a98d7c10, event=0x7ffc26bba560) at kernel/qwidgetwindow.cpp:322 #18 0x7f009d362f5e in QApplicationPrivate::notify_helper (this=, receiver=0x5557a98d7c10, e=0x7ffc26bba560) at kernel/qapplication.cpp:3637 #19 0x7f009c6b1718 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f009cb39bac in QGuiApplicationPrivate::processGeometryChangeEvent (e=) at kernel/qguiapplication.cpp:2610 #21 0x7f009cb11e1c in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #22 0x7f00962fc0fa in xcbSourceDispatch (source=) at ./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:105 #23 0x7f009a9da799 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f009a9daa28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f009a9daabc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f009c7094b6 in
[plasmashell] [Bug 461654] New: Taskbar disappears onto non-existent screen after disconnecting secondary screens
https://bugs.kde.org/show_bug.cgi?id=461654 Bug ID: 461654 Summary: Taskbar disappears onto non-existent screen after disconnecting secondary screens Classification: Plasma Product: plasmashell Version: 5.26.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: bernhard.schert...@pm.me Target Milestone: 1.0 STEPS TO REPRODUCE 1. Connect at least 2 screens (in this case laptop + 2 screens) 2. Set one of the screens as primary, but move the taskbar to another screen 3. Disconnect secondary screen(s) OBSERVED RESULT Taskbar running as normal, but not being displayed on the only connected display. Restarting does not fix the issue, only fix I have found is reconnecting the external display(s) and moving the taskbar to the primary screen again. EXPECTED RESULT Taskbar being visible on the only connected display (laptop screen) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.7-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Latitude 5590 ADDITIONAL INFORMATION Bug exists on both Wayland and X11 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461598] scripter doesn't work with python 3.11
https://bugs.kde.org/show_bug.cgi?id=461598 --- Comment #2 from Bernhard Rosenkränzer --- This patch works for me with 3.11 https://github.com/OpenMandrivaAssociation/krita/blob/master/krita-5.1.3-python-3.11.patch Haven't tried with any older versions, but don't see why it wouldn't work. (MR 1604 doesn't have anything related to this, @asyncio.coroutine is still present in 3.11) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461598] New: scripter doesn't work with python 3.11
https://bugs.kde.org/show_bug.cgi?id=461598 Bug ID: 461598 Summary: scripter doesn't work with python 3.11 Classification: Applications Product: krita Version: 5.1.3 Platform: OpenMandriva OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: b...@lindev.ch Target Milestone: --- SUMMARY Starting Krita 5.1.3 on a system with python 3.11 results in error messages on stderr: /usr/lib64/krita-python-libs/krita added to PYTHONPATH krita.scripting: "Traceback (most recent call last):" krita.scripting: " File \"/usr/share/krita/pykrita/scripter/__init__.py\", line 6, in " krita.scripting: "from .scripter import *" krita.scripting: " File \"/usr/share/krita/pykrita/scripter/scripter.py\", line 8, in " krita.scripting: "from . import uicontroller, documentcontroller, debugcontroller" krita.scripting: " File \"/usr/share/krita/pykrita/scripter/debugcontroller.py\", line 6, in " krita.scripting: "from .debugger_scripter import debugger" krita.scripting: " File \"/usr/share/krita/pykrita/scripter/debugger_scripter/debugger.py\", line 16, in " krita.scripting: "class Debugger(bdb.Bdb):" krita.scripting: " File \"/usr/share/krita/pykrita/scripter/debugger_scripter/debugger.py\", line 86, in Debugger" krita.scripting: "@asyncio.coroutine" krita.scripting: " ^" krita.scripting: "AttributeError: module 'asyncio' has no attribute 'coroutine'" krita.scripting: "Could not import scripter" krita.scripting: Error loading plugin "scripter" @asyncio.coroutine has been deprecated since python 3.5 and finally removed in 3.11. STEPS TO REPRODUCE 1. Install python 3.11 2. Build scripter's dependencies with python 3.11 3. Build and launch krita OBSERVED RESULT Scripter crashes on startup EXPECTED RESULT Scripter works SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7+KDE patches ADDITIONAL INFORMATION The fix is simply replacing @asyncio.coroutine with the async keyword, but that will break some ancient python versions (3.3 and 3.4). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350555] Unable to handle quotation marks in »To« field.
https://bugs.kde.org/show_bug.cgi?id=350555 Bernhard Scheirle changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Version|5.5.2 |5.21.2 --- Comment #8 from Bernhard Scheirle --- Reproduced with kmail2 5.21.2 (22.08.2) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 454122] neofetch and right mouse button menu at the same time will cause a crash
https://bugs.kde.org/show_bug.cgi?id=454122
--- Comment #7 from Bernhard Übelacker ---
A short addition: I could reproduce it inside a rr-debugger recording.
It looks to me like updateForegroundProcessInfo (which sets
_foregroundProcessInfo)
was called the last time even before the neofetch process got started.
Therefore _foregroundProcessInfo contains that old "state" while
isForegroundProcessActive is returning the current "state".
Another place which calls isForegroundProcessActive
is calling updateForegroundProcessInfo immediately after it.
Therefore maybe this change might be considered?
-if (isForegroundProcessActive() && _foregroundProcessInfo->isValid())
{
+if (isForegroundProcessActive() && updateForegroundProcessInfo() &&
_foregroundProcessInfo && _foregroundProcessInfo->isValid()) {
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 454122] neofetch and right mouse button menu at the same time will cause a crash
https://bugs.kde.org/show_bug.cgi?id=454122
Bernhard Übelacker changed:
What|Removed |Added
CC||bernha...@mailbox.org
--- Comment #6 from Bernhard Übelacker ---
I received this crash too with current Debian testing.
Below the top of the backtrace without and the full backtrace with debug
symbols installed.
While in my first crash I think I had also a ssh connection open, I could
reproduce the issue
- with installing neofetch
- starting a new konsole
- starting inside neofetch
- right click while neofetch was still running.
Interesting looks the call to `Konsole::ProcessInfo::isValid` with this=0x0.
I assume these bugs are duplicates to this one: 458157 460764
And bug 391447 seems also kind of related, while it was closed with a commit
changing this:
-if (isForegroundProcessActive()) {
+if (isForegroundProcessActive() && _foregroundProcessInfo->isValid())
{
Maybe extend this check by following:
-if (isForegroundProcessActive() && _foregroundProcessInfo->isValid())
{
+if (isForegroundProcessActive() && _foregroundProcessInfo &&
_foregroundProcessInfo->isValid()) {
Kind regards,
Bernhard
Application: Konsole (konsole), signal: Segmentation fault
[KCrash Handler]
#4 0x7f85356d0ad0 in Konsole::ProcessInfo::isValid() const () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#5 0x7f85357609f4 in Konsole::Session::getUrl() () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#6 0x7f8535768b71 in Konsole::SessionController::url() const () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#7 0x7f8535776bdc in
Konsole::SessionController::showDisplayContextMenu(QPoint const&) () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.1
...
konsole-dbgsym 4:22.08.1-1
konsole-kpart-dbgsym 4:22.08.1-1
libqt5core5a-dbgsym 5.15.6+dfsg-2
libqt5gui5-dbgsym 5.15.6+dfsg-2
libqt5widgets5-dbgsym 5.15.6+dfsg-2
libglib2.0-0-dbgsym 2.74.1-1
Application: Konsole (konsole), signal: Segmentation fault
[KCrash Handler]
#4 Konsole::ProcessInfo::isValid (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:151
#5 0x7f85357609f4 in Konsole::Session::getUrl (this=0x5646bfb35520) at
./src/session/Session.cpp:1232
#6 0x7f8535768b71 in Konsole::SessionController::url (this=) at ./src/session/SessionController.cpp:379
#7 0x7f8535776bdc in Konsole::SessionController::showDisplayContextMenu
(this=0x5646bf563fb0, position=...) at ./src/session/SessionController.cpp:1891
#8 0x7f85340e8caf in QtPrivate::QSlotObjectBase::call (a=0x7ffe7043e5c0,
r=0x5646bf563fb0, this=0x5646bfbdbce0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9 doActivate (sender=0x5646bf95cea0, signal_index=12,
argv=0x7ffe7043e5c0) at kernel/qobject.cpp:3919
#10 0x7f85340e1f4f in QMetaObject::activate
(sender=sender@entry=0x5646bf95cea0, m=m@entry=0x7f8535803be0
,
local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7ffe7043e5c0)
at kernel/qobject.cpp:3979
#11 0x7f85356ba575 in Konsole::TerminalDisplay::configureRequest
(this=this@entry=0x5646bf95cea0, _t1=...) at
./obj-x86_64-linux-gnu/src/konsoleprivate_autogen/DRAQINE3W2/moc_TerminalDisplay.cpp:398
#12 0x7f853573fc8f in Konsole::TerminalDisplay::mousePressEvent
(this=0x5646bf95cea0, ev=0x7ffe7043eb10) at
./src/terminalDisplay/TerminalDisplay.cpp:1168
#13 0x7f8534da4ce8 in QWidget::event (this=0x5646bf95cea0,
event=0x7ffe7043eb10) at kernel/qwidget.cpp:9034
#14 0x7f8534d62f5e in QApplicationPrivate::notify_helper
(this=this@entry=0x5646bf4211d0, receiver=receiver@entry=0x5646bf95cea0,
e=e@entry=0x7ffe7043eb10) at kernel/qapplication.cpp:3637
#15 0x7f8534d6b502 in QApplication::notify (this=,
receiver=0x5646bf95cea0, e=) at kernel/qapplication.cpp:3081
#16 0x7f85340b1718 in QCoreApplication::notifyInternal2
(receiver=0x5646bf95cea0, event=0x7ffe7043eb10) at
kernel/qcoreapplication.cpp:1064
#17 0x7f8534d6960e in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x5646bf95cea0, event=event@entry=0x7ffe7043eb10,
alienWidget=, nativeWidget=0x5646bf74f790,
buttonDown=buttonDown@entry=0x7f85352a69f0 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
kernel/qapplication.cpp:2619
#18 0x7f8534dbdaf8 in QWidgetWindow::handleMouseEvent (this=0x5646bf779c80,
event=0x7ffe7043edc0) at kernel/qwidgetwindow.cpp:683
#19 0x7f8534dc0e80 in QWidgetWindow::event (this=0x5646bf779c80,
event=0x7ffe7043edc0) at kernel/qwidgetwindow.cpp:300
#20 0x7f8534d62f5e in QApplicationPrivate::notify_helper (this=, receiver=0x5646bf779c80, e=0x7ffe7043edc0) at
kernel/qapplication.cpp:3637
#21 0x7f85340b1718 in QCoreApplication::notifyInternal2
(receiver=0x5646bf779c80, event=0x7ffe7043edc0) at
kernel/qcoreapplication.cpp:1064
#22 0x7f853453d6bd in
[kmail2] [Bug 331891] Broken references-chain (email header) leads to new Thread
https://bugs.kde.org/show_bug.cgi?id=331891 Bernhard Scheirle changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Version|5.2.1 |5.21.1 --- Comment #5 from Bernhard Scheirle --- Still reproducible with kmail2 5.21.1 (22.08.1) -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 367603] Type of email addresses is case-sensitive.
https://bugs.kde.org/show_bug.cgi?id=367603 Bernhard Scheirle changed: What|Removed |Added Status|NEEDSINFO |REPORTED Version|unspecified |5.21.1 Resolution|WAITINGFORINFO |--- Platform|Neon|Manjaro --- Comment #2 from Bernhard Scheirle --- Can still be reproduced in kaddressbook 5.21.1 (22.08.1) -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 331976] Wrong error message on "address rejected" error.
https://bugs.kde.org/show_bug.cgi?id=331976 Bernhard Scheirle changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Bernhard Scheirle --- Error message seems to be fixed in at least "kmail2 5.21.1 (22.08.1)": Fehler beim Übertragen der Nachricht. Serverfehler: 5.7.1 : Sender address rejected: not owned by user sen...@host.de Translation: Error transferring message. Server Error: 5.7.1 : Sender address rejected: not owned by user sen...@host.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460692] Canceling a wallpaper change does not revert to the original image
https://bugs.kde.org/show_bug.cgi?id=460692 --- Comment #2 from Bernhard --- Created attachment 153020 --> https://bugs.kde.org/attachment.cgi?id=153020=edit relevant section of plasmashell log Obtained from "journalctl /usr/bin/plasmashell -f". Please let me know if you need something else -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460692] New: Canceling a wallpaper change does not revert to the original image
https://bugs.kde.org/show_bug.cgi?id=460692 Bug ID: 460692 Summary: Canceling a wallpaper change does not revert to the original image Classification: Plasma Product: plasmashell Version: 5.26.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: plasma-b...@kde.org Reporter: micraf...@gmail.com CC: notm...@gmail.com, qydwhotm...@gmail.com Target Milestone: 1.0 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. Context Menu > Configure Desktop and Wallpaper 2. Select different wallpaper 3. Press Cancel, Discard OBSERVED RESULT Wallpaper changes when selecting one - does not change back after Cancel + Discard EXPECTED RESULT Wallpaper changes to the original wallpaper SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.15.74-1-lts (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Layout is set to Desktop The change does not seem to get written to config as "plasmashell --replace" reverts it. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 370524] Scrolling artifacts in pages using CommandOutputKCM
https://bugs.kde.org/show_bug.cgi?id=370524 --- Comment #4 from Bernhard --- (In reply to Nate Graham from comment #3) > The issue you're seeing is a different bug compared to the one Nur Muhammed > was seeing, but as that bug is no longer possible to see, we can use this > bug report for your issue. > > It's almost certainly caused by an issue outside of KInfoCenter--likely in > qqc2-desktop style, Qt, or your graphics drivers. > > What graphics hardware are you using and are you using any scaling? And are > you using X11 or Wayland? I was using X11, but this particular instance was fixed it seems (as well as in the network applet). The same thing still occurs when dragging down on the text in "About this System" Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.70-1-lts (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: HP Product Name: HP ENVY x360 Convertible 15-ee0xxx System Version: Type1ProductConfigId No scaling (set to 100%) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459025] Adding/Removing a favorite from Kicker only takes effect after restarting it
https://bugs.kde.org/show_bug.cgi?id=459025 Bernhard Rosenkränzer changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Version|5.25.5 |5.25.90 Status|NEEDSINFO |REPORTED --- Comment #2 from Bernhard Rosenkränzer --- 5.25.90 behaves the same way. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446963] KDEconnect v1.18 on Android12: TCP connection to server port 1716 violates TCP rules for segment size and termination sequence
https://bugs.kde.org/show_bug.cgi?id=446963 --- Comment #2 from Riegler Bernhard --- you are correct. I was tricked by looking at the data content in wireshark, which is the same as UDP just before. the TCP segments are correct just after the 3-way handshake. (MSS=1460) I cannot tell if the wireshark config was wrong or the TCP-offloading to HW was switched on (LRO) but the TCP finish behaviour is still valid. the android side (KDEconnect) send TCP ACK flag, but no FIN or RST flag. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 454062] Installing plasma-framework breaks qmlplugindump on kde modules
https://bugs.kde.org/show_bug.cgi?id=454062 Bernhard Rosenkränzer changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #7 from Bernhard Rosenkränzer --- Confirmed fixed with https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/600 -- You are receiving this mail because: You are watching all bug changes.
