[plasma-nm] [Bug 469519] WLAN connection menu shows all available WiFi networks as connected
https://bugs.kde.org/show_bug.cgi?id=469519 Nicolas Fella changed: What|Removed |Added Product|kded-appmenu|plasma-nm Component|Titlebar menu button/popup |general CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463089] macOS (and Windows?): Kdenlive UI does not show all localized strings from po files (especially in Preferences)
https://bugs.kde.org/show_bug.cgi?id=463089 mi...@filmsi.net changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REOPENED --- Comment #8 from mi...@filmsi.net --- This bug is still open and I am still waiting for an answer which of the other po files contains these "untranslated" strings. My fear is these files are not up-to-date, as KDE is fully localized into Slovenian (except for documentation). See for yourself: Kf5-stable https://l10n.kde.org/stats/gui/stable-kf5/team/sl/ Kf5-trunk https://l10n.kde.org/stats/gui/trunk-kf5/team/sl/ Kf6 https://l10n.kde.org/stats/gui/trunk-kf6/team/sl/ So there is just no way to get "Cancel" and such buttons in the interface in English. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467835] On login, containment for left-most screen is placed on right-most screen overlapping its containment, and left-most screen gets a black background
https://bugs.kde.org/show_bug.cgi?id=467835 Samuel Suther changed: What|Removed |Added CC||s.sut...@gmx.de Platform|Archlinux |Manjaro Version|5.27.3 |5.27.4 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #12 from Samuel Suther --- plasmashell 5.27.4 Same here since some weeks. After startup left screen is black. Right-Mouseclick on it, don't show any context... seems plasmashell is fully broken for it. I've made a little script to reload it... after running it, it work. But that is only an unsatisfying workaround. Hope it will be fixed soon. ``` #!/bin/bash killall plasmashell plasmashell > /dev/null 2>&1 & disown ``` -- You are receiving this mail because: You are watching all bug changes.
[calindori] [Bug 469521] New: Calindori does not use the correct month between views.
https://bugs.kde.org/show_bug.cgi?id=469521 Bug ID: 469521 Summary: Calindori does not use the correct month between views. Classification: Applications Product: calindori Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jazanat...@gmail.com Target Milestone: --- Created attachment 158791 --> https://bugs.kde.org/attachment.cgi?id=158791&action=edit This is a brief screen recording of the bug. SUMMARY Calindori does not use the correct month between views. In this case, it's May in week view, but June in Month view. STEPS TO REPRODUCE 1. Set system date to 9th of May 2023 2. Click On Week view 3. Click On Month View OBSERVED RESULT The month switched to June. EXPECTED RESULT The month stays on May, same as the week. 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.
[calindori] [Bug 469521] Calindori does not use the correct month between views.
https://bugs.kde.org/show_bug.cgi?id=469521 --- Comment #1 from Jazztache --- Distro: Arch Linux 6.3.1-arch1-1 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5..15.9 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 469519] WLAN connection menu shows all available WiFi networks as connected
https://bugs.kde.org/show_bug.cgi?id=469519 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.24.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #36 from Matthias Dahl --- With the limited man power KWin has and this being a rather nasty problem (and not a priority), I wouldn't hold my breath for this to get fixed any time soon, I am afraid. I spent a few weeks trying to fix it, deep diving in kwin internals but at the end, I came to the conclusion that there is (imho) no way to make it work with all the floating point numbers and rounding. You have damage events in logical coordinates that are just one pixel in height... after scaling both coordinates and size, they have to perfectly fit where the damage is in device coordinates or you will end up with graphical glitches. That is extremely hard, if not impossible, to do right all the time. I shared my findings and tried to suggest a possible solution I called "fuzzy repaint". Basically you add a few pixel in each direction to the damage event to account for possible floating point/rounding errors. Even a very basic PoC on my end, fixed all glitches and worked fine. It would have required my work and thought to make it safe and sound, but it was better than what we have now and did not require a full repaint or anything else expensive. Unfortunately I was ignored (which is absolutely fine!), so I called it a day and moved on to different shores... :-( It's a pity really. On the surface, with KDE and KWin, you get pretty much everything you wished for with their handling of Wayland/Xwayland, scaling and HiDPI, but it has also has to work properly which is where it falls short. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #37 from Nate Graham --- Matthias, did you submit that work for consideration anywhere? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #38 from Matthias Dahl --- I posted a (lengthy) comment on the 3236 merge request with my findings and suggestion, but after being ignored, I felt somewhat stupid/embarrassed, so I deleted it. The code itself was only a few lines that I never posted because it was just a PoC on my end. I wanted to get a discussion going if this would be a possible solution and where the best place would be, to extend the damage event and how, so I could have come up with a proper implementation that could have been merged eventually. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469522] New: Minimizing a subwindow in windows mode does not activate the next window
https://bugs.kde.org/show_bug.cgi?id=469522 Bug ID: 469522 Summary: Minimizing a subwindow in windows mode does not activate the next window Classification: Applications Product: krita Version: 5.1.4 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ha...@valdyas.org Target Milestone: --- * Open two images * Select the second one * Press the minimize button * The first image is shown * But the second one is still active Note: QMDIArea, argh. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468408] On Wayland with Plasma 6, plasmashell sometimes fails to load with "The Wayland connection experienced a fatal error: Resource temporarily unavailable"
https://bugs.kde.org/show_bug.cgi?id=468408 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-integration/-/merge_requests/86 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 469491] https://kde.org/nl/announcements/gear/23.04.0/ Who is responsable for this?
https://bugs.kde.org/show_bug.cgi?id=469491 --- Comment #4 from Freek de Kruijf --- Ik doe al 18 jaar mijn best om KDE te vertalen (met een beetje hulp van een paar anderen) en heb daarbij eigenlijk alleen de lezer die geen of weinig kennis heeft van de Engelse taal in het oog. Als er hele kleine wijzigingen gevraagd worden die weinig tijd kosten doe ik die. Maar een wijziging als deze doe ik alleen als ik een .po bestand aangeleverd krijg, dat alleen met controle programmatuur wordt gecontroleerd en verder ongewijzigd door mij, als coördinator, wordt aangebracht. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #37 from Zamundaaa --- I've seen glitches similar to that before, they were caused by sort of broken hardware acceleration. Can you check if playing a video without hardware acceleration triggers the glitches and/or the freeze? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #39 from Nate Graham --- Darn, I'm sorry that you didn't get a good response. Any chance you could post the code in the form of a merge request for KWin? I'm actually at a Plasma sprint right now and I'm sitting by a KWin developer, and I might be able to help get a conversation started. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424525] Wrong behavior of blending modes in CMYK
https://bugs.kde.org/show_bug.cgi?id=424525 --- Comment #12 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1796 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468408] On Wayland with Plasma 6, plasmashell sometimes fails to load with "The Wayland connection experienced a fatal error: Resource temporarily unavailable"
https://bugs.kde.org/show_bug.cgi?id=468408 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.5 Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-integration/commi ||t/058ae55b7980eacaecf6ed3c3 ||7c050a10cf1a6a0 Resolution|--- |FIXED --- Comment #4 from Nate Graham --- Git commit 058ae55b7980eacaecf6ed3c37c050a10cf1a6a0 by Nate Graham, on behalf of David Redondo. Committed on 09/05/2023 at 08:27. Pushed by davidre into branch 'master'. wayland: Only set decoration palette once for each change Because we filter events on the app, we receive palette change events for every widget and item, each causing a setPalette call for every window which can eventually overflow the wayland connection buffer. FIXED-IN:5.27.5 M +3-0src/platformtheme/kwaylandintegration.cpp https://invent.kde.org/plasma/plasma-integration/commit/058ae55b7980eacaecf6ed3c37c050a10cf1a6a0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468408] On Wayland with Plasma 6, plasmashell sometimes fails to load with "The Wayland connection experienced a fatal error: Resource temporarily unavailable"
https://bugs.kde.org/show_bug.cgi?id=468408 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-integration/commi |ma/plasma-integration/commi |t/058ae55b7980eacaecf6ed3c3 |t/2b04981039bbd0fd2ee8303d0 |7c050a10cf1a6a0 |d4539208f651b0a --- Comment #5 from Nate Graham --- Git commit 2b04981039bbd0fd2ee8303d0d4539208f651b0a by Nate Graham, on behalf of David Redondo. Committed on 09/05/2023 at 08:43. Pushed by ngraham into branch 'Plasma/5.27'. wayland: Only set decoration palette once for each change Because we filter events on the app, we receive palette change events for every widget and item, each causing a setPalette call for every window which can eventually overflow the wayland connection buffer. FIXED-IN:5.27.5 (cherry picked from commit 058ae55b7980eacaecf6ed3c37c050a10cf1a6a0) M +3-0src/platformtheme/kwaylandintegration.cpp https://invent.kde.org/plasma/plasma-integration/commit/2b04981039bbd0fd2ee8303d0d4539208f651b0a -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 420169] KScreen does not change the screen resolution of QEMU/QXL/Spice VM
https://bugs.kde.org/show_bug.cgi?id=420169 --- Comment #10 from tagwer...@innerjoin.org --- See also: https://bugzilla.redhat.com/show_bug.cgi?id=2196435 For Fedora 38, you additionally need to edit /etc/sddm.conf and add: [General] DisplayServer=x11 to "push" SDDM to use X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469523] New: Rule for window position under wayland with (changing) multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=469523 Bug ID: 469523 Summary: Rule for window position under wayland with (changing) multi-monitor setup Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: bartos.p...@gmail.com CC: isma...@gmail.com Target Milestone: --- SUMMARY *** Hi, under wayland, rule for window position seems not to be applied in scope of required monitor, but absolutely spanned across all connected monitors. Is this bug or intentional behaviour? In my case, problem is i am moving with notebook between multiple workplaces where external monitors are placed differently - left, right, even above where notebook is placed. So under wayland i am not able to create rule so that some window always appears in bottom right corner of primary monitor (in "notification area"). *** STEPS TO REPRODUCE 1. Create rule to force window to appear on monitor 0 (primary), positioned e.g. at 1600x820 (somewhere at bottom right) 2. Connect secondary monitor placed either left or above primary 3. Open window matching created rule OBSERVED RESULT Window is displayed on secondary monitor despite being forced to be displayed on primary monitor EXPECTED RESULT Window position given in rule should be calculated relative to the selected monitor -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417572] vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xED 0xC5 0xF9 0x51
https://bugs.kde.org/show_bug.cgi?id=417572 masterch...@gmail.com changed: What|Removed |Added Platform|Other |Ubuntu Version|3.15 SVN|3.21 GIT Component|memcheck|vex --- Comment #2 from masterch...@gmail.com --- In latest git this is still the same problem. It is coming from a common _mm_loadl_epi64 intrinsic. I compiled the source with both g++ 11.3.0 and 12.1.0, same results. When compiling with -O0 this does not occur. vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xD3 0xC5 0x79 0xD6 0xE0 0xC5 0x7A vex amd64->IR: REX=0 REX.W=0 REX.R=1 REX.X=0 REX.B=0 vex amd64->IR: VEX=1 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==14165== valgrind: Unrecognised instruction at address 0x5cf15c1. ==14165==at 0x5CF15C1: _mm_set_epi64x (emmintrin.h:592) ==14165==by 0x5CF15C1: _mm_set_epi64 (emmintrin.h:598) ==14165==by 0x5CF15C1: _mm_loadl_epi64 (emmintrin.h:709) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469522] Minimizing a subwindow in windows mode does not activate the next window
https://bugs.kde.org/show_bug.cgi?id=469522
--- Comment #1 from Halla Rempt ---
Hm, Qt's internal processing suggests it might actually be intentional?
void QMdiAreaPrivate::_q_processWindowStateChanged(Qt::WindowStates oldState,
Qt::WindowStates newState)
{
if (ignoreWindowStateChange)
return;
Q_Q(QMdiArea);
QMdiSubWindow *child = qobject_cast(q->sender());
if (!child)
return;
// windowActivated
if (!(oldState & Qt::WindowActive) && (newState & Qt::WindowActive))
emitWindowActivated(child);
// windowDeactivated
else if ((oldState & Qt::WindowActive) && !(newState & Qt::WindowActive))
resetActiveWindow(child);
// windowMinimized
if (!(oldState & Qt::WindowMinimized) && (newState & Qt::WindowMinimized))
{
isSubWindowsTiled = false;
arrangeMinimizedSubWindows();
// windowMaximized
} else if (!(oldState & Qt::WindowMaximized) && (newState &
Qt::WindowMaximized)) {
internalRaise(child);
// windowRestored
} else if (!(newState & (Qt::WindowMaximized | Qt::WindowMinimized))) {
internalRaise(child);
if (oldState & Qt::WindowMinimized)
arrangeMinimizedSubWindows();
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 453129] Painting very thin lines will become dashed.
https://bugs.kde.org/show_bug.cgi?id=453129 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/4130e84fc ||5ede6bd6f9105b4d06f0830ba3d ||e994 --- Comment #4 from Dmitry Kazakov --- Git commit 4130e84fc5ede6bd6f9105b4d06f0830ba3de994 by Dmitry Kazakov, on behalf of Tom Tom Tom. Committed on 09/05/2023 at 08:56. Pushed by dkazakov into branch 'master'. Double supersampling factor when brush size is lower than 1 px Increasing supersampling factor from 3 to 6 smooths out the dashed effect of sub-1px strokes to almost invisible levels. M +5-0libs/image/kis_base_mask_generator.cpp M +2-0libs/image/kis_base_mask_generator.h M +5-4libs/image/kis_brush_mask_scalar_applicator.h https://invent.kde.org/graphics/krita/commit/4130e84fc5ede6bd6f9105b4d06f0830ba3de994 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417572] vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xED 0xC5 0xF9 0x51
https://bugs.kde.org/show_bug.cgi?id=417572 Tom Hughes changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Tom Hughes --- That is an AVX512 instruction, or at least uses EVEX encoding, which means it is dependent on AVX512 support being added. Until then you will need to compile to target an architecture that does not support AVX512. *** This bug has been marked as a duplicate of bug 383010 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Tom Hughes changed: What|Removed |Added CC||arnaud.desit...@gmail.com --- Comment #89 from Tom Hughes --- *** Bug 417572 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339416] unhandled instruction bytes 0xC5 0xF1 0xEF 0xC9 [AVX]
https://bugs.kde.org/show_bug.cgi?id=339416 Tom Hughes changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||t...@compton.nu --- Comment #1 from Tom Hughes --- That is an AVX512 instruction, or at least uses EVEX encoding, which means it is dependent on AVX512 support being added. *** This bug has been marked as a duplicate of bug 383010 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 --- Comment #90 from Tom Hughes --- *** Bug 339416 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339416] unhandled instruction bytes 0xC5 0xF1 0xEF 0xC9 [AVX]
https://bugs.kde.org/show_bug.cgi?id=339416 Tom Hughes changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Tom Hughes --- Scratch that I'm talking nonsense - that is VEX encoding. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417572] vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xED 0xC5 0xF9 0x51
https://bugs.kde.org/show_bug.cgi?id=417572 Tom Hughes changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #4 from Tom Hughes --- Scratch that I'm talking nonsense - that is VEX encoding. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417572] vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xED 0xC5 0xF9 0x51
https://bugs.kde.org/show_bug.cgi?id=417572 --- Comment #5 from Tom Hughes --- I believe the instruction is: VEX.128.66.0F.WIG D6 /r VMOVQ xmm1/m64, xmm2 Move quadword from xmm2 register to xmm1/m64. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420757] Empty OSD when I switch virtual desktop for the first time after login
https://bugs.kde.org/show_bug.cgi?id=420757 soredake changed: What|Removed |Added CC|broaden_acid002@simplelogin | |.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469470] kwin does not remember screen order after turning on/off tv screen
https://bugs.kde.org/show_bug.cgi?id=469470 Eric Armbruster changed: What|Removed |Added Summary|kwin does not remember |kwin does not remember |screen order after reboot, |screen order after turning |with TV screen |on/off tv screen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469470] kwin does not remember screen order after turning on/off tv screen
https://bugs.kde.org/show_bug.cgi?id=469470 --- Comment #2 from Eric Armbruster --- Correction: its enough to simply turn on/off the TV screen. After that my screen order is scrambled. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 469131] t PC, plasmoid kdeconnect, burger menu does not work
https://bugs.kde.org/show_bug.cgi?id=469131 Johannes Studt changed: What|Removed |Added Ever confirmed|0 |1 CC||demofr...@gmx.de Status|REPORTED|CONFIRMED --- Comment #1 from Johannes Studt --- Same here. All apps (kdeconnect-cli, kdeconnect-app, kdeconnect-sms) are working, but clicking the hamburger menu in systray widget does nothing. Kdeconnect: 23.04.0 Operating System: openSUSE Tumbleweed 20230502 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467617] Application freezes after media playback
https://bugs.kde.org/show_bug.cgi?id=467617 Shubham Arora changed: What|Removed |Added CC||shubhamar...@protonmail.com --- Comment #15 from Shubham Arora --- I have experienced this crash with gst-plugins-good installed. This is required for other apps such as audiotube. Without it I this error and gifs and videos don't work. At least it doesn't crash after a while. Warning: "No decoder available for type 'video/quicktime, variant=(string)iso'." Error: "Your GStreamer installation is missing a plug-in." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468837] Kwin stops working after 2 days of uptime (forcing a reboot)
https://bugs.kde.org/show_bug.cgi?id=468837 --- Comment #1 from Paul Stansell --- This issue may be caused by the bug reported here https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2018671 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 468929] Kalendar crashes when tasks are edited
https://bugs.kde.org/show_bug.cgi?id=468929 Achilleas Koutsou changed: What|Removed |Added CC||achillea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 390109] Meta+é etc. hotkeys not working on French AZERTY keyboards
https://bugs.kde.org/show_bug.cgi?id=390109 Thomas Cochat changed: What|Removed |Added CC||thomas.coc...@gmail.com --- Comment #8 from Thomas Cochat --- Hi. I tried to change my keyboard layout with xmodmap to get some key to become É (notice the capital !) and the shortcut works. So this issue might be related to some upper case conversion issue for non ascii character. Most shortcuts will display the upper case letter ( Meta + a displayed as Meta + A). You can also see it in the ".config/kglobalshortcutsrc" file. I'm not sure why Meta + A works with its lower case equivalent but Meta + É doesn't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454353] [WAYLAND] Cannot copy string from clipboard to color field of solid color wallpaper
https://bugs.kde.org/show_bug.cgi?id=454353 --- Comment #4 from Dipta Biswas --- Hi, sorry for the delay. The mail thread regarding this bug report was hidden beneath piles of other mail in KMail. I'm on Fedora now and the bug is no longer reproducible. Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.14-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 2 × AMD E2-9000e RADEON R2, 4 COMPUTE CORES 2C+2G Memory: 3.7 GiB of RAM Graphics Processor: AMD Radeon R2 Graphics Manufacturer: HP Product Name: HP Laptop 14-bw0xx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454353] [WAYLAND] Cannot copy string from clipboard to color field of solid color wallpaper
https://bugs.kde.org/show_bug.cgi?id=454353 --- Comment #5 from Dipta Biswas --- I'll look into reporting to Qt once I have gone through their userbase or techbase wiki regarding bugs. Never been in that territory before -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 timadams changed: What|Removed |Added CC||timothyad...@ymail.com --- Comment #39 from timadams --- I also have this problem with Plasma 5.27.4 on Tumbleweed, on a computer running nouveau and on another with the nvidia driver. Normal shutdown with X-11, 90 second delay with Wayland. Wayland runs perfectly in other respects. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 467123] When Raise maximum sound is turned on, sound OSD can show wrong volume level depending on the audio profile used and audio hardware configuration
https://bugs.kde.org/show_bug.cgi?id=467123 ak...@iname.com changed: What|Removed |Added CC||ak...@iname.com --- Comment #16 from ak...@iname.com --- For me "raise maximum volume" keeps the max volume level at 100%, not 150% like it used to. I can still raise the volume with "pactl set-sink-volume @DEFAULT_SINK@ 150%" but the level meter stays at 100%. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 467123] When Raise maximum sound is turned on, sound OSD can show wrong volume level depending on the audio profile used and audio hardware configuration
https://bugs.kde.org/show_bug.cgi?id=467123 --- Comment #17 from ak...@iname.com --- Forgot to add that this is on Fedora 37, Plasma 5.27.4. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 469326] Green/white tick are too far in activity "Letter in which word"
https://bugs.kde.org/show_bug.cgi?id=469326 anim...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/educ ||ation/gcompris/commit/b8144 ||221c210077be018e6d7f7d1efc9 ||fa6d16fd --- Comment #2 from anim...@gmail.com --- Git commit b8144221c210077be018e6d7f7d1efc9fa6d16fd by Timothée Giet. Committed on 09/05/2023 at 11:44. Pushed by timotheegiet into branch 'master'. letter-in-word, fix selection marker too far from word Replace tick selection marker (which was too far from the word) with an orange border highlight. Adjust cards size and spacing to avoid overlap and improve readability. M +11 -13 src/activities/letter-in-word/Card.qml M +2-1src/activities/letter-in-word/LetterInWord.qml https://invent.kde.org/education/gcompris/commit/b8144221c210077be018e6d7f7d1efc9fa6d16fd -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 432816] Failed to get D-Bus interface of mailfilteragent.
https://bugs.kde.org/show_bug.cgi?id=432816 Vaclav Masin changed: What|Removed |Added CC||vaclav.ma...@atlas.cz --- Comment #1 from Vaclav Masin --- I've run into this issue the other day for the first after many (mostly trouble-free) years with kmail + akonadi. What I had to do in the end to resolve it was starting up "akonadiconsole", switching to the "Browser" tab, opening the "outbox" folder on the left and then in the right pane deleting the "unsendable" message. It's been a few days since then and so far all seems to be good. So I'm just letting others known of a potential fix if needed. This was on KMail Version 5.23.0 (23.04.0) (copied from the About dialogue window) + Frameworks 5.105.0 + Plasma 5.27.4. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 469326] Green/white tick are too far in activity "Letter in which word"
https://bugs.kde.org/show_bug.cgi?id=469326 --- Comment #3 from anim...@gmail.com --- Actually, after looking at the attached screenshot, it shows a different issue: there should be images on top of the words, and the tick is on the top-left corner of the images... I guess the package in Devuan testing is missing the dependency to load webp images (qt5-image-formats-plugins in debian), you should report that issue to the packager of that distribution. Anyway I've changed the tick with an orange border highlight around the text background, which looks better in any case. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382034] Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 Alexander Kanavin changed: What|Removed |Added CC||alex.kana...@gmail.com --- Comment #16 from Alexander Kanavin --- Created attachment 158792 --> https://bugs.kde.org/attachment.cgi?id=158792&action=edit Add missing includes to avoid 'SYS_modify_ldt is undefined' errors -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382034] Testcases build fixes for musl
https://bugs.kde.org/show_bug.cgi?id=382034 Alexander Kanavin changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #17 from Alexander Kanavin --- There's one more fix needed (add needed includes on musl), I've attached the patch for it. Hope you don't mind reusing this ticket, which I'll reopen. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 469413] Cannot filter book titles for strings containing an ü
https://bugs.kde.org/show_bug.cgi?id=469413 Mark Reidel changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Mark Reidel --- I think you're mixing this up with the "Group by" dropdown. I'm searching for and grouping the results by Author. But I found the error when using a binary editor. It depends on how the ü is saved: "ü" or "ü" (actual ü, or u+ ̈). And of course you can't see that in a KDE application. Doh ;o) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464760] Not possible to overlap screens anymore on multiscreen setups.
https://bugs.kde.org/show_bug.cgi?id=464760 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469524] New: It becomes possible to configure screens to overlap with at least 3 screens activated
https://bugs.kde.org/show_bug.cgi?id=469524 Bug ID: 469524 Summary: It becomes possible to configure screens to overlap with at least 3 screens activated Classification: Plasma Product: KScreen Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 158793 --> https://bugs.kde.org/attachment.cgi?id=158793&action=edit kWin Support Info SUMMARY As of #464760 it is no longer possible for good reasons to let screens overlap. This works fine in case of 2 screens, however, when I enable a third screen, screens can freely be moved around again in KScreen and configured in a way that they overlap. I attached kwin support info, where I had configured 3 screens to overlap in some way. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230507 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-1-default (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 275078] Fit to window size not working if image is smaller then window size. Add a new option for zooming in preview [patch]
https://bugs.kde.org/show_bug.cgi?id=275078 Evert Vorster changed: What|Removed |Added CC||evors...@protonmail.com --- Comment #17 from Evert Vorster --- Created attachment 158794 --> https://bugs.kde.org/attachment.cgi?id=158794&action=edit Gwenview Not Fitted Screenshot of Gwenview with fit image not clicked -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 275078] Fit to window size not working if image is smaller then window size. Add a new option for zooming in preview [patch]
https://bugs.kde.org/show_bug.cgi?id=275078 --- Comment #18 from Evert Vorster --- Created attachment 158795 --> https://bugs.kde.org/attachment.cgi?id=158795&action=edit Gwenview Fitted Screenshot of Gwenview with "Fit" clicked -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 469413] Cannot filter book titles for strings containing an ü
https://bugs.kde.org/show_bug.cgi?id=469413 --- Comment #4 from Robby Stephenson --- (In reply to Mark Reidel from comment #3) > I think you're mixing this up with the "Group by" dropdown. I'm searching > for and grouping the results by Author. > But I found the error when using a binary editor. It depends on how the ü is > saved: "ü" or "ü" (actual ü, or u+ ̈). And of course you can't see that in > a KDE application. Doh ;o) Oh you're right about my mix-up. Sorry. Glad it's resolved, though. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 275078] Fit to window size not working if image is smaller then window size. Add a new option for zooming in preview [patch]
https://bugs.kde.org/show_bug.cgi?id=275078 --- Comment #19 from Evert Vorster --- Created attachment 158796 --> https://bugs.kde.org/attachment.cgi?id=158796&action=edit Digikam Fit This is what the image looks like in DigiKam, whether fit has been clicked or not. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 275078] Fit to window size not working if image is smaller then window size. Add a new option for zooming in preview [patch]
https://bugs.kde.org/show_bug.cgi?id=275078 --- Comment #20 from Evert Vorster --- This IS a VERY old discussion, but as screen resolutions keep increasing, it only becomes more relevant, instead of less relevant. Gwenview now assumes that "Fit" means fit the image to the window, which means that it would scale larger images smaller to fit, as well as scale smaller images larger to fit. (attached screenshots to show) For DigiKam, there is already a "Zoom to 100%" button, that would make small images appear small, and large images appear large. It would only make sense to now make "Fit to window" to actually make small images fit to larger windows as well. This issue has been bugging me for a long time, as it's really annoying to have to set the zoom scale for small images. Because people have been asking for this for a long time, it is a requested feature. Of course some people don't want small images enlarged, and that's fine too. Why not simply have a configuration option in settings that states "Enlarge smaller images to fit window"? People who don't like to see small images enlarged can leave it off, and people who would want their images enlarged can switch it on. This would satisfy both use cases for minimum effort. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469525] New: After enabling 2nd screen, KScreen positions the screen automatically with huge gap to the other
https://bugs.kde.org/show_bug.cgi?id=469525 Bug ID: 469525 Summary: After enabling 2nd screen, KScreen positions the screen automatically with huge gap to the other Classification: Plasma Product: KScreen Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 158797 --> https://bugs.kde.org/attachment.cgi?id=158797&action=edit Screenshot STEPS TO REPRODUCE 1. Have three screens: One activated, two deactivated 2. Enable the 2nd screen in KScreen OBSERVED RESULT KScreen positions this screen far away from the other screen as if it left some space for the 3rd screen. KScreen then complains in an inline notification that having a gap between two screens is not allowed. EXPECTED RESULT KScreen always positions screens adjacent to each other. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230507 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-1-default (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 275078] Fit to window size not working if image is smaller then window size. Add a new option for zooming in preview [patch]
https://bugs.kde.org/show_bug.cgi?id=275078 --- Comment #21 from Evert Vorster --- Created attachment 158798 --> https://bugs.kde.org/attachment.cgi?id=158798&action=edit Gwenview Settings Screenshot of the Gwenview settings dialog, which has exactly this setting suggested in my comment -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469526] New: no matadata when exporting in AVIF
https://bugs.kde.org/show_bug.cgi?id=469526 Bug ID: 469526 Summary: no matadata when exporting in AVIF Classification: Applications Product: digikam Version: 8.1.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: betamax...@gmail.com Target Milestone: --- Hello, I'using a beta 8.1.0 (digiKam-8.1.0-20230504T052816-x86-64) When I export a JPEG image in AVIF, (after edited by F4), all exif metadata are not preserved, so, no metadata in the new AVIF file. Note that I'don't know if this is a bug or normal action for AVIF but when I export the same image in HEIC, all metadata are preserved in the new HEIC image. SOFTWARE/OS VERSIONS Kubuntu 23.04 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469526] no matadata when exporting in AVIF
https://bugs.kde.org/show_bug.cgi?id=469526 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Metadata-Exif |Metadata-Engine --- Comment #1 from caulier.gil...@gmail.com --- Hi, AVIF is not yet supported to write metadata by Exiv2 shared lib. Use XMP sidecar instead. Look in Setup Metadata for details : https://docs.digikam.org/en/setup_application/metadata_settings.html#sidecars-settings Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469527] New: Spectacle crashed when disabling screen where Spectacle is opened and took a rectangular region screenshot
https://bugs.kde.org/show_bug.cgi?id=469527 Bug ID: 469527 Summary: Spectacle crashed when disabling screen where Spectacle is opened and took a rectangular region screenshot Classification: Applications Product: Spectacle Version: 23.04.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: pos...@posteo.eu CC: k...@david-redondo.de Target Milestone: --- SUMMARY Spectacle crashed when disabling screen where Spectacle is opened and took a rectangular region screenshot STEPS TO REPRODUCE 1. Have two screens 2. Open Spectacle on your 2nd screen 3. Take a rectengular region screenshot 4. Disable this screen in kscreen OBSERVED RESULT Spectacle crashes. Reproducible: Always ``` (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f7684a94993 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f7684a43196 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f76855ddd3a in KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kcrash-5.105.0/src/kcrash.cpp:626 #4 #5 0x0320 in ?? () #6 0x7f7685325232 in QtPrivate::QSlotObjectBase::call (a=0x7fff7dd679e0, r=0x7fff7dd68410, this=0x55f87f19a110) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x7fff7dd683c0, signal_index=10, argv=0x7fff7dd679e0) at kernel/qobject.cpp:3923 #8 0x7f768531de2f in QMetaObject::activate (sender=, m=m@entry=0x7f7685d15fa0, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff7dd679e0) at kernel/qobject.cpp:3983 #9 0x7f768576e8f2 in QGuiApplication::screenRemoved (this=, _t1=, _t1@entry=0x55f87ed37780) at .moc/moc_qguiapplication.cpp:396 #10 0x7f76857a5df8 in QScreen::~QScreen (this=0x55f87ed37780, __in_chrg=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:116 #11 0x7f76857a5f69 in QScreen::~QScreen (this=0x55f87ed37780, __in_chrg=) at kernel/qscreen.cpp:178 #12 0x7f768574f247 in QWindowSystemInterface::handleScreenRemoved (platformScreen=0x55f87ed98a90) at kernel/qwindowsysteminterface.cpp:844 #13 0x7f76872a5c02 in QtWaylandClient::QWaylandDisplay::registry_global_remove (this=0x55f87ed7a260, id=70) at qwaylanddisplay.cpp:571 #14 0x7f76862a58d2 in ffi_call_unix64 () at ../src/x86/unix64.S:104 #15 0x7f76862a224f in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=) at ../src/x86/ffi64.c:673 #16 0x7f76862a4e96 in ffi_call (cif=cif@entry=0x7fff7dd67cc0, fn=, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7fff7dd67d90) at ../src/x86/ffi64.c:710 #17 0x7f768792ca23 in wl_closure_invoke (closure=closure@entry=0x7f766c002c40, target=, target@entry=0x55f87ed7e830, opcode=opcode@entry=1, data=, flags=1) at ../src/connection.c:1025 #18 0x7f768792d203 in dispatch_event (display=display@entry=0x55f87ed7e6b0, queue=0x55f87ed7e7a0) at ../src/wayland-client.c:1631 #19 0x7f768792d494 in dispatch_queue (queue=0x55f87ed7e7a0, display=0x55f87ed7e6b0) at ../src/wayland-client.c:1777 #20 wl_display_dispatch_queue_pending (display=0x55f87ed7e6b0, queue=0x55f87ed7e7a0) at ../src/wayland-client.c:2019 #21 0x7f76872a2a12 in QtWaylandClient::QWaylandDisplay::flushRequests (this=) at qwaylanddisplay.cpp:255 #22 0x7f7685318c50 in QObject::event (this=0x55f87ed7a260, e=0x7f766c001ee0) at kernel/qobject.cpp:1347 #23 0x7f7686ba51ae in QApplicationPrivate::notify_helper (this=, receiver=0x55f87ed7a260, e=0x7f766c001ee0) at kernel/qapplication.cpp:3640 #24 0x7f76852ec978 in QCoreApplication::notifyInternal2 (receiver=0x55f87ed7a260, event=0x7f766c001ee0) at kernel/qcoreapplication.cpp:1064 #25 0x7f76852eff71 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55f87ed71230) at kernel/qcoreapplication.cpp:1821 #26 0x7f7685346713 in postEventSourceDispatch (s=0x55f87ed952a0) at kernel/qeventdispatcher_glib.cpp:277 #27 0x7f7682d028d8 in g_main_dispatch (context=0x7f7674000ee0) at ../glib/gmain.c:3460 #28 g_main_context_dispatch (context=context@entry=0x7f7674000ee0) at ../glib/gmain.c:4200 #29 0x7f7682d02ce8 in g_main_context_iterate (context=context@entry=0x7f7674000ee0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4276 #30 0x7f7682d02d7c in g_main_context_iteration (context=0x7f7674000ee0, may_block=1) at ../glib/gmain.c:4343 #31 0x7f7685345f26 in QEventDispatcherGlib::processEvents (this=0x55f87ed36d30, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #32 0x7f76852eb40b in QEventLoop::exec (this=this@entry=0x7fff7dd682e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #33 0x7f7
[Spectacle] [Bug 469527] Spectacle crashed when disabling screen where Spectacle is opened and took a rectangular region screenshot
https://bugs.kde.org/show_bug.cgi?id=469527 postix changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354662] "Display configuration" allows overlapping screens
https://bugs.kde.org/show_bug.cgi?id=354662 postix changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #2 from postix --- This issue has actually been resolved in 5.27. See https://bugs.kde.org/show_bug.cgi?id=464760#c1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 374703] Positioning monitors should be without overlapping and without gaps
https://bugs.kde.org/show_bug.cgi?id=374703 postix changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #2 from postix --- This issue has actually been resolved in 5.27. See https://bugs.kde.org/show_bug.cgi?id=464760#c1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467762] Parts of the UI like the Clip Monitor on startup are glitched with Wayland
https://bugs.kde.org/show_bug.cgi?id=467762 iodream...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469528] New: Dolphin crashes on root access to conf file
https://bugs.kde.org/show_bug.cgi?id=469528 Bug ID: 469528 Summary: Dolphin crashes on root access to conf file Classification: Applications Product: dolphin Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kingto...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.3) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.14-300.fc38.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: dolphin freezes everytime i try to access a root folder/file : etc/samba/smb.conf or other conf file for example and hangs and crashes Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7fc14c285092 in QVector::realloc(int, QFlags) () from /lib64/libKF5KIOCore.so.5 #5 0x7fc14c288097 in KIO::Connection::send(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #6 0x7fc14c2c3ca9 in KIO::SlaveBase::send(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #7 0x7fc14c2bea17 in KIO::SlaveBase::mimeType(QString const&) () from /lib64/libKF5KIOCore.so.5 #8 0x7fc14a6e8651 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7fc12c149506 in OrgKdeKioAdminGetCommandInterface::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/qt5/plugins/kf5/kio/admin.so #10 0x7fc12c149782 in OrgKdeKioAdminGetCommandInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/qt5/plugins/kf5/kio/admin.so #11 0x7fc14b98544b in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5 #12 0x7fc14a6df73b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7fc14b3aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7fc14a6b3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7fc14a6b71f5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #16 0x7fc14a706e2f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #17 0x7fc14831339c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7fc148371438 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #19 0x7fc148310a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7fc14a706919 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7fc14a6b270b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7fc12c142cf7 in AdminWorker::get(QUrl const&) () from /usr/lib64/qt5/plugins/kf5/kio/admin.so #23 0x7fc14c2c6ff7 in KIO::WorkerSlaveBaseBridge::get(QUrl const&) () from /lib64/libKF5KIOCore.so.5 #24 0x7fc14c2c382d in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #25 0x7fc14c2bbb4d in KIO::SlaveBase::dispatchLoop() () from /lib64/libKF5KIOCore.so.5 #26 0x7fc14c337b34 in KIO::WorkerThread::run() () from /lib64/libKF5KIOCore.so.5 #27 0x7fc14a4f556d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #28 0x7fc149eae907 in start_thread () from /lib64/libc.so.6 #29 0x7fc149f34870 in clone3 () from /lib64/libc.so.6 Thread 4 (Thread 0x7fc1213fb6c0 (LWP 15255) "QThread"): #1 0x7fc1483712a0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fc148310a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fc14a706936 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fc14a6b270b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fc14a4f4160 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fc14a4f556d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fc149eae907 in start_thread () from /lib64/libc.so.6 #8 0x7fc149f34870 in clone3 () from /lib64/libc.so.6 Thread 3 (Thread 0x7fc1351ff6c0 (LWP 15250) "dolphin"): #1 0x7fc14860f0cc in usbmuxd_listen_inotify () from /lib64/libusbmuxd-2.0.so.6 #2 0x7fc14860fdc2 in device_monitor () from /lib64/libusbmuxd-2.0.so.6 #3 0x7fc149eae907 in start_thread () from /lib64/libc.so.6 #4 0x7fc149f34870 in clone3 () from /lib64/libc.so.6 Thread 2 (Thread 0x7fc1379bb6c0 (LWP 15248) "QDBusConnection"): #1 0x7fc1483713a9 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fc148310a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fc14a706919 in QEventDispat
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #40 from Matthias Dahl --- Thanks for looking into this-- very much appreciated! :-) Here you go: https://invent.kde.org/plasma/kwin/-/merge_requests/4080 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469529] New: Wayland: set some windows to be at the top always
https://bugs.kde.org/show_bug.cgi?id=469529 Bug ID: 469529 Summary: Wayland: set some windows to be at the top always Classification: Plasma Product: kwin Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY Examples: - Polkit auth window - KVault auth window - error windows These should be defaulted to be on top. I think there is a way to set it manually, but having it default would be a great benefit. When having the dialog and for example Firefox opens on top of it, the Passwort input stops and you have to reenter/continue after manually switching to the window. --- Software --- OS: Fedora Linux 38.20230508.0 (Kinoite) KDE Plasma: 5.27.4 KDE Frameworks: 5.105.0 Qt: 5.15.9 Kernel: 6.2.14-300.fc38.x86_64 Compositor: Wayland --- Hardware --- CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx RAM: 13.5 GB GPU: AMD Radeon Vega 8 Graphics Video memory: 2048MB -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467499] kdenlive can´t install openai-whisper python module
https://bugs.kde.org/show_bug.cgi?id=467499 jdl <677ee...@duck.com> changed: What|Removed |Added CC||677ee...@duck.com --- Comment #1 from jdl <677ee...@duck.com> --- I don't think this is an error due to kdenlive, because the highest python version supported by some of the whisper dependencies, is 3.10. I also experienced this error on Fedora Linux 38, and fixed it by installing python3.10 and moving the 'python' and 'python3' aliases to point to python3.10. Maybe kdenlive should declare python3.10 as a whisper dependency? And definitely check for and choose supported python version in the whisper install script -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469530] New: Arrow keys fail to focus windows in present-window mode launched from the taskbar icons
https://bugs.kde.org/show_bug.cgi?id=469530 Bug ID: 469530 Summary: Arrow keys fail to focus windows in present-window mode launched from the taskbar icons Classification: Plasma Product: kwin Version: 5.27.4 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: al.neo...@gmail.com Target Milestone: --- Created attachment 158799 --> https://bugs.kde.org/attachment.cgi?id=158799&action=edit Demo of arrow key failure to select window Clicking on a taskbar icon of an app (chrome in this case) present-window is launched but arrow keys are unresponsive. See attached demo: note screenkey capture afterward. Instead of windows in present-mode actual windows handle keystrokes, like they don't loose focus at all. Kubuntu: 23.04 KDE Plasma: 5.27.4 libqt5core5a: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 452553] Monitor instantly wakes up from energy saving in Wayland
https://bugs.kde.org/show_bug.cgi?id=452553 Dmitry Misharov changed: What|Removed |Added CC||quarcks...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379474] KWin wakes up the monitor right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=379474 Dmitry Misharov changed: What|Removed |Added CC||quarcks...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446895] Desktop SMS Unresponsive
https://bugs.kde.org/show_bug.cgi?id=446895 Garry Williams changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|NEEDSINFO |REOPENED --- Comment #6 from Garry Williams --- Just tested again and same result. After re-opening the SMS application, I cannot type in another message. Furthermore, I see a message on my phone: "This paired device is not reachable. Make sure it is connected to your same network." The SMS application works until closing and reopening on my KDE desktop. kdeconnectd-23.04.0-1.fc38.x86_64 kde-connect-libs-23.04.0-1.fc38.x86_64 kde-connect-23.04.0-1.fc38.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469029] Cant Drag and Drop ANY Clips to Timeline
https://bugs.kde.org/show_bug.cgi?id=469029 --- Comment #6 from ponslle...@gmail.com --- Kdenlive 23.04.0 I work fine in Ubuntu 22.04.02 but not in Ubuntu 23.04. Ubuntu 22.04 is an official stable release, but 23.04 is a non-stable pre-beta release. Now I am working on a laptop with Ubuntu 22.04, and another tower with Ubuntu 22.04 and I stopped working with the computer running ubuntu 23.04, on which I will install the stable version of Ubuntu 22.04, but first I will wait some time to see if the problem can be fixed. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 469531] New: Crash on startup in latest master
https://bugs.kde.org/show_bug.cgi?id=469531
Bug ID: 469531
Summary: Crash on startup in latest master
Classification: Applications
Product: NeoChat
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: c...@carlschwan.eu
CC: c...@carlschwan.eu
Target Milestone: ---
SUMMARY
Cras
STEPS TO REPRODUCE
1. Open NeoChat
OBSERVED RESULT
Crash
EXPECTED RESULT
No crash :p
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.27
KDE Frameworks Version: 5.105
Qt Version: 5.15
ADDITIONAL INFORMATION
the crash
Application: NeoChat (neochat), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 0x7f845cd91844 in __pthread_kill_implementation () from
/lib64/libc.so.6
#6 0x7f845cd40abe in raise () from /lib64/libc.so.6
#7 0x7f845cd2987f in abort () from /lib64/libc.so.6
#8 0x0069ea07 in messageHandler (type=QtFatalMsg, context=...,
message=...) at /home/carl/kde/src/neochat/src/logger.cpp:186
#9 0x7f845d328bd8 in qt_message_print(QtMsgType, QMessageLogContext
const&, QString const&) () from /lib64/libQt5Core.so.5
#10 0x7f845d328cfe in qt_message(QtMsgType, QMessageLogContext const&, char
const*, __va_list_tag*) () from /lib64/libQt5Core.so.5
#11 0x7f845d2ed86d in QMessageLogger::fatal(char const*, ...) const () from
/lib64/libQt5Core.so.5
#12 0x7f845d2ec9f5 in qt_assert(char const*, char const*, int) () from
/lib64/libQt5Core.so.5
#13 0x0077aa1f in Quotient::EventStats::updateOnMarkerMove
(this=0x61e5b38, room=0x61e4760, oldMarker=..., newMarker=...) at
/home/carl/kde/src/libQuotient/Quotient/eventstats.cpp:58
#14 0x0072ace4 in Quotient::Room::Private::setFullyReadMarker
(this=0x61e5a10, eventId=...) at
/home/carl/kde/src/libQuotient/Quotient/room.cpp:898
#15 0x0072b417 in Quotient::Room::Private::markMessagesAsRead
(this=0x61e5a10, upToMarker=...) at
/home/carl/kde/src/libQuotient/Quotient/room.cpp:933
#16 0x0072b692 in Quotient::Room::markAllMessagesAsRead
(this=0x61e4760) at /home/carl/kde/src/libQuotient/Quotient/room.cpp:957
#17 0x00722f12 in Quotient::Room::qt_static_metacall (_o=0x61e4760,
_c=QMetaObject::InvokeMetaMethod, _id=97, _a=0x7ffe88782e40) at
/home/carl/kde/src/libQuotient/build/Quotient_autogen/include/moc_room.cpp:1197
#18 0x00726378 in Quotient::Room::qt_metacall (this=0x61e4760,
_c=QMetaObject::InvokeMetaMethod, _id=97, _a=0x7ffe88782e40) at
/home/carl/kde/src/libQuotient/build/Quotient_autogen/include/moc_room.cpp:1857
#19 0x0046d2b8 in NeoChatRoom::qt_metacall (this=0x61e4760,
_c=QMetaObject::InvokeMetaMethod, _id=102, _a=0x7ffe88782e40) at
/home/carl/kde/build/neochat/src/neochat_autogen/EWIEGA46WW/moc_neochatroom.cpp:1184
#20 0x7f846012544a in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const () from /lib64/libQt5Qml.so.5
#21 0x7f845fff6b70 in CallPrecise(QQmlObjectOrGadget const&,
QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*,
QMetaObject::Call) () from /lib64/libQt5Qml.so.5
#22 0x7f845fff9e02 in QV4::QObjectMethod::callInternal(QV4::Value const*,
QV4::Value const*, int) const () from /lib64/libQt5Qml.so.5
#23 0x7f846002a841 in
QV4::Runtime::CallPropertyLookup::call(QV4::ExecutionEngine*, QV4::Value
const&, unsigned int, QV4::Value*, int) () from /lib64/libQt5Qml.so.5
#24 0x7f8410320c56 in ?? ()
#25 0x in ?? ()
[Inferior 1 (process 46581) detached]
--
You are receiving this mail because:
You are watching all bug changes.
[NeoChat] [Bug 469531] Crash on startup in latest master
https://bugs.kde.org/show_bug.cgi?id=469531 --- Comment #1 from Carl Schwan --- actually looking at the bug in more details, this seems to be a quotient bug :( -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469532] New: KDE laggs horrible when io is active
https://bugs.kde.org/show_bug.cgi?id=469532 Bug ID: 469532 Summary: KDE laggs horrible when io is active Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bixi...@bixilon.de Target Milestone: --- Created attachment 158800 --> https://bugs.kde.org/attachment.cgi?id=158800&action=edit System monitor SUMMARY KDE is lagging horrible on all sorts of io events. It also affects other applications. STEPS TO REPRODUCE 1. Copy files from one drive to another (or extract an archive, ...) OBSERVED RESULT KDE is lagging as hell EXPECTED RESULT Working fine, no lag spikes SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION I do have an NVME SSD installed, I can also see this on a lot of other devies that run KDE software. I am observing this for years, but now (I am just copying 50 GB over the network) it is really REALLY annoying. See the system monitor attachment. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469532] KDE laggs horrible when io is active
https://bugs.kde.org/show_bug.cgi?id=469532 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469526] no matadata when exporting in AVIF
https://bugs.kde.org/show_bug.cgi?id=469526 --- Comment #2 from Maxime --- Hi, ok thanks ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466597] [NVIDIA] Popup windows sometimes glitch desktop background as content when appearing
https://bugs.kde.org/show_bug.cgi?id=466597 dsyrzm...@mozmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from dsyrzm...@mozmail.com --- I just noticed that this does no longer seem to happen. Maybe it was fixed with the upgrade to 23.04, not sure exactly when it stopped, but it's a lot smoother now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of image properties sidebar tab.
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #43 from caulier.gil...@gmail.com --- Note : It's very difficult to create a Photograph Properties view as data are really not homogeneous for one camera to another one. Strings can be very large and impossible to synthesis in this kind of camera panel. It's the same for the Video Properties view. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 --- Comment #56 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/powerdevil/-/merge_requests/173 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469533] New: Dolphin freezes and eventually crashes when I am conntected to a network without internet
https://bugs.kde.org/show_bug.cgi?id=469533 Bug ID: 469533 Summary: Dolphin freezes and eventually crashes when I am conntected to a network without internet Classification: Applications Product: dolphin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bixi...@bixilon.de CC: kfm-de...@kde.org Target Milestone: --- Created attachment 158801 --> https://bugs.kde.org/attachment.cgi?id=158801&action=edit backtrace SUMMARY I recently was on the ICE and while I was connected to the hotspot but did not authenticate through their captive web portal, I started dolphin and it pretty much instantly froze and eventually crashed. Disconnecting from the network/logging in solved that problem and it seemed to work fine again. STEPS TO REPRODUCE 1. Run `sudo iptables -A INPUT -i wlp2s0 -j DROP` (adjust your interface name) 2. Start dolphin (To remove the rule again, run `sudo iptables -D INPUT -i wlp2s0 -j DROP` or reboot your computer) OBSERVED RESULT Work normal EXPECTED RESULT Frozen SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION It seems like it tries to connect to a samba share, but I do not have any mounted/trying to access it. I do use it from time to time (accessing a smb:// domain). Found it in a previous stack trace, not this one. Might be a complete wrong guess gdb backtrace (and px -aux) is attached, can not post it directly...blocked because of spam -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469533] Dolphin freezes and eventually crashes when I am conntected to a network without internet
https://bugs.kde.org/show_bug.cgi?id=469533 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987 --- Comment #30 from Phoenix Awakened --- Created attachment 158802 --> https://bugs.kde.org/attachment.cgi?id=158802&action=edit Clear visibility of issue when panels are floating -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of image properties sidebar tab.
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #44 from José Oliver-Didier --- Gilles: 8.1.0 screenshot of the properties looks great! I can see it as a good quick glace panel and launching pad for any metadata modifications. Some thoughs- 1. Will the timezone value, if available, be displayed in the datetime value? 2. The location fields displayed are the IPTC location info? 3. Rights metadata is often overlooked by other apps, it is nice it is well displayed. For reference, here is a link to from IPTC on how Google Images reads and displays image right info. https://iptc.org/standards/photo-metadata/quick-guide-to-iptc-photo-metadata-and-google-images/ 4. Some apps try to mimic the LCD screen of a pro camera (Ref: https://www.neocamera.com/articles/dam_software/idimager/idimager_info.png). I believe it looks nice up to a point. I belive that's the idea behind the previous proposal mockup images attached to this bug - Ref https://bugsfiles.kde.org/attachment.cgi?id=135665 and https://bugsfiles.kde.org/attachment.cgi?id=115333 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987 Phoenix Awakened changed: What|Removed |Added Attachment #158802|2023-05-09_20-38.png|abcd.png filename|| Attachment #158802|image/png |text/docx mime type|| -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469534] New: Crash on startup when offline
https://bugs.kde.org/show_bug.cgi?id=469534 Bug ID: 469534 Summary: Crash on startup when offline Classification: Applications Product: Discover Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: alicehar...@murena.io CC: aleix...@kde.org Target Milestone: --- Created attachment 158803 --> https://bugs.kde.org/attachment.cgi?id=158803&action=edit Output of gdb debugging SUMMARY When disconnected from the internet, opening Discover will result in a segmentation fault. If Discover has recently opened while connected to the internet, it will not crash again, even when disconnected. However, given enough time between opening, this behaviour returns. STEPS TO REPRODUCE 1. Turn internet off 2. Open Discover OBSERVED RESULT Discover crashes EXPECTED RESULT Discover displays its cached apps, the same as if it had been loaded online recently and then reopened when offline. Note: The crash handler only displayed "The crash information could not be generated". The attached trace is from running `gdb plasma-discover` and downloading debug symbols. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Running a slightly odd kernel (6.2.8-eupnea, from the Depthboot project). I don't think this would cause an issue(?), but figured it would be polite to mention. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987
--- Comment #31 from Phoenix Awakened ---
Comment on attachment 158802
--> https://bugs.kde.org/attachment.cgi?id=158802
Clear visibility of issue when panels are floating
>DOCX
>
>³.Þ£·k§ñ¨=¡oû YÙê
>ô~TÙ§§·Þö責ìÛå*É>t¤nY°ãxï^½ú
\(û+&n£jåÓæÙgCû8ÕÃGñ92Ru:.ª¶Mçý;Hü$ò¯GÉ7ÁûOëãlp>Ê«oé·NÿyäZOÿýÚ,+Úw6ýï}wËOÃE¡Äª¤óqÇËT";oÿö/ïÔF@ØwæSÊO¦oØt×É]Ò½_ïq²ØÄƸ¶5<Û¥¤
wm;T§.ÝMlâÐaÝsþëÖ³w;uFJÐzßè-«]ªþ½³ËǬÞó×®+ú[ÕÑ"']RºîÆ¥×SÃs_ß´ôìëð&7'EëR©¿÷»j©iòäèwvDÌðl[ìlÐÂíí·Î\,
>
ñö
¶Øxãa/÷ÿubwÝ·äî`îîyºIÎà{b:Ç¿vÎ1çÖ¦W°BLÐÒ2i¢*þZ^µ¿b±xf}(`C:'mêý¸#Df{ï1{ä±D+ïÀì£õ¬
ÀòúãȾëè®ýWàÙSFVkºé\!ò%2Ð
{Ó;Ôn§þ@YYé{ï.aУî3æËXóc¬ï*¢^ãG¼?Påäîêã,d»ý&xK´1Á{îìfðJ÷#ØÇ»Ìkp½Ô4 )6`Ö{pþ1ñD#0|¦a)ªÁf{j1ÖÙÀº
>óRÀ`]?4õ)&~¾ú*U
õÇ:À¾½ê*f,kÀ¸U{×Yk&j&OVf4½ñxkÐÉ68çÜ3ëXá\f
í Y°ààé|æ|®
¡!¬W°_f¯ãQ~Æû#-3Ø:Àä$·,rмa!4¦.ºg&°¯@Õ~é9mêzß1ªÎ¨Ú¥4_1o_OITûh&R++`Ç[ź7ö7¡AuÕ;üqiÉÃ÷öN
0ËM{ÌÐÆ,h¬r1pÚÔ[÷¼ßj6±MCu)c/õ×b5$ÓæèfÁf&Ö£×,~ÔßWç靈)wç͸A ã3
Yø²°`¥]\zÆYw
>ÀóÂk|õAqØ"Ps0L6çc»Í¡9¦îuܺhrÛg/kê!@Ó·{}SÀk]`SÅ)éÎ|Zc=8JÇ+æuÐ3$SWY`º>@³cõ)3ì
>³9.Kúµ+Pº3nùÞùlÊ:¶çõsÞY}
>À²LÎkÁ^~zÚGMκ
>ÌXæà/¨¤Öxæ2±ßP+±Ú»ßPõ/ùiZÐXóMðÒzczð©»fíjFOÓ²k3_À´ ²M©Y§øÀWÌ&ò3(Â0
aö}x,@S1ïCyÜöápÆPÇà©wrg챺Ï×4Ö>³Î¸¤?^±Ñ£
9ü"`"~fPz¾ÌѸ9Ú!ufÈjÑïkø)Ââñç,]
>À¬¡>§1°ÞßP»¿èZ];1¶®A-VW£öãð'`?d,LdJ$vðð1õi'0?űãuÁ2KMü×[Û4xbh¶&µqî¯au1Ø6X©Dø<ÿ,YlníSµûíuüòëo|}}5ί˰aVܤ®õ\2Ì°SSuwû
¼à×ùÙÕc°@«øO<|ìï#Ç÷ý}øÇ_6O:ÕF$dØEHÎÃìÝ;ÿ(,,`5BÞ³¼¶Y³dk¬IOмÏ_÷Zýç)&Ìç´LÅõ訨¯×
>½z¾üÚùyyÑ/3¬+^oØe:6ß7öÀÍæÿ°*I°(ÀÌxx(àÁÃÇtîÀ[ÀHhÈ4ÒÔ¼Ì{´Y-%\}ß«ukB½½Ã¬Ù³)
>¨è¨¨?vl+//éÚõ_öðWÈWb¢ûu³¯oEKüç³Õ
>lÅÊUîBsÊÛÿYó©>ýÌìa#F ÔåKQìø¼¼\ëã}Ö«õö̳ÄPÉúfÌÑ;pÃC
>@g¨oÙXz+p
CEBaïÐ>^ÞÞi)wÁô³;tX¶x¼Z¾xé²³fÿµûÏO?sþÜÙÇÚÚÚ¹{¸WUI몿·t)M»»ûû~øOä)¹L6gîAK¿%¯-^¶|æ¬Ù;¶ÿ¦R©Ø"6^Nÿ=uy5À
0pÇC
>@æúËoÈÞ¬fÏÒ`Øî}*''ç~L¾ìâÒªwhèÞ¿vBÎýûÏäiOÙì·ÍÏË0 ,5åNZjêìû²
>g?ó\fzÖ¥ç]BCûìÙýgM#gÿòÔSeeeZCÓxgbfÇ,öC
>Ï
>À\3á!ú5{Ñc¢/½nmÇN.|»²¢Ð´Xlëêê¶hñ7ßz"Ry¹ùÚúë¯#Gzgñ2itç¿'\×j*,<¢]`Û/¿øB®PÅbWW··,]¸hq]#B¡î?/&ÕÇä}Á?V49s-PãsG#L
ML¤Þ¹8uÆ¿û¦ºZV\\øÓ\ÓjòØçN6|ä˯½ñÅÕ§|ýü¦MùÇöß
>)Bª««úá÷ø¸XÝÃm4VÝ2=Ý®ÉYíÃæØ3é¡SÏl¢)<,oø4;f
R¢T*9Ô;´OyYiâõÉS¦zy{B]üýD"aûÀb±½B¡¼wïR¡
ê/¾ØNüìÜâcc¯_OP)/+»~ýÚä)Ó¼¼½Õøù0as|ÁjMøB`ÈÔYÓ&OPüfy`ÑÀèn´º|vvö
ÏL9óÖÍ[{ÿúkÚé_ü÷k'gç²²Òû÷äåå5jèð4M>.=x`ßÚµT·Ð©s>}ûUwï6bäHBHzVúÿ¾újïî¿1cíëÕØ·çAö}6²ðßÐ)&JÏ2~A÷¼Æ7¹<¢ºtéιrÝÝ~ÈçMYDütÝï,ÛÔ]6ÒÞÓ´±úÎè9Gë|i¤]ÚXýmê¹ÌZÓj¥¯ojúÕø¢uD©TÎßûÝöÙËd<`Uæí^¿uæb¡Ph
·o°ÅÆÐI³ô÷-c.E(ã|Ã
>únÎ÷çÙd¸#?>u䲿î:loïc:éLÚÀØE~æZ?NñÔ4ûv¨¿±©¨»
>eà¡ÃwÐ_í¥ÀÖ&âáZxÕXÞþåé±¥íìÇ££9C¬¿¯£wKÿ)3îo)À|?£¹P¼1i¥ëw:{iÂ{ÂæÀâù¬û2Ü«¹\7ÿ×[·÷á¢z°çíq£G7cRú"iÃócǽ¹óªi-ÛJpAZ¤+]3.®÷(ãÁ3<ú
>håíÖïOåýÃþÎR6õ0àÉ"jÑWãÀÏÜrcÔMX
>§nOËcò@UXÍÉgXØx±Ú¼\LfBÐ:¸4õöî-#>ëÙàôöÁï=ñ°HjãÙyð³ko§LÝöú[ûZ¿ôvÛÄ¿NßÈQxô¾ð9Ë[ÿ8O|Î}ïÝiAvÈr.þþóS׳Ëm¼BF<¿èÕâ&ú`¬~;@.(P|Ï`9ÍQC'ôáðéÌ`´]
> ³Ö3¾à
>$¤Îy®}Ù¿_-où»Êê6¦Ï?)Ptìûog׬¨º²õ§XÞCC[˲¯l_±øTÏCº»UdÛòÛ¿Å4%ÿþñ»â=ç¾³`GÆ¡¯>ÝqKÖ
¬XL4`¼´Ï nK ´ð°(å~M
% C¦{uzaÞé-Ý õß¾ÓVÿðÉÂçfÎzuî` ¥xS»Z@0õÝo.ü`Þ@{BD]ýèÝ7½7§§
å>,P)Ϲ/·ë7gÁSÃÇÌ;Ü~u9+
@ÿO°f¬g³Ü°Aq#E(ÐÀa«hÔSý~F!°ü4ÍJEÛÍ|eÌéGl>Ú!ĶöüÁÅ¿þuéÎÃJ¹\VIÓNõß¾~¾BBDv%òñuÊÉÉB«h¢(.,QyÔº§'®S§\©ZüÓÕz²Rj7y5ëCb®,Uñ³L0_Ñoj§%
вQ¡ÏÏxá«Ëþ^&&ÄBÝðå®»þ/¸*ÂóÞË¿8YQChSÎZ¡½ÐÕÍ¢ªû¿¶ú¹®6µÄoñ
_Ë_`9ü¬vÍ7PÑ|ãëæMîb0æ°Ù@WY=Ç0ùZ0ûeeÔ¬÷WÊäJB EiÞODZxL
Mȱím*®Ùs!)õîĨ'+íð/4µà»}õF&<Ïhm¤:UXîO¨]ÑXØl
À4À¼YfH0ùÕÉu÷ó)ÉÐç_ó]ÝòÅú=÷CçLôc1߶óók>7È9óøo?ý°y÷¿YÄÙÿz
*¤K÷¦A¦ÎçXföaCºêl6ðÎ`]½Ý:Ìä#é.ÅúqlS}¸¯oJúÆÍð/7'EëR©¿÷»í³5ÉxÀªÌÛ½~ëÌÅBíõz
xû[l<µàY&á>_WqÖÚ9ͱ7VÞG²¸oÏ|´`IHèÅû£MëÙÖe1rÆý¯%05fÐâS;ö¤5Âeá-úôôÆjÛ
«`}93¦(f_ÁG?úW«óòA8µÀn2Â,²î2yBã³]BB&Núõk9·_Yøg°A¤v:Ú4½-è«õ·bhm¬n¬TTósLcê,é'Ô%4u
YþÁG_ý÷sÛg¥)&èÎèîÁD-
¹Ü§¡u×ÓO¤'#ÂO@»ëM¬Rß¾}zÀZlllS¦¦Ôñ¿Î,ÀÊ÷ßM¾uËÄöù¢3xä=/
Â#"&LÜ.0¢99Ù;wì¸s[kCzYÂ2OÁ$gÀ6
{LFÐlágæ|hILJ¨çÿï?|Ls!úþ¿««õÄÿúÔåx2Á3G¿ó߯^R©H`ÀܹÚ÷²ÙtÆmQã|EUû³Ëö\Ï3
>Xÿóÿß²Ï4ÔþÓí;TJ+u~vGi3gîÛ³ká+¯äç?z}ᢼÜü×^·èWmD¶/¾üª
!ÄÙɹkî¶êÅçIºqãõ7ßriåªîíãöø|X
®òLª°{b¡fñl@Sñ0cüߨ_g'çÊJYµLÇiJxæä©ë×®UWKÛøHÜ$§Nªª.¯¨8zä`ûöAÞÞ)BT*å¹3gryä©b[q@@Û}°ýëhLÙX;}3á'`¡ø¿éî3鶬¼ÜÁÑA}?_R¡ÌÏÏS¿vrrªÉ¤Uê·¥¥eÐNRQQQ®>^UU%Ëì4G`ì>9·S:^1c<@é;a¤YU0?)frÿߤ±IÔý¬,'GçN;ë, Åй×Ýý{W¢£^zõ5[[ñõø8¹RéíÓº¨
P«Xö½{¹ù¹cÆOÜõ;D"ÑøS22ÓóórÅb{@8|Äèëñ×JKKG+feeé7dýÁùéÝ.þÆñÐ䫨δHTmlZ
*ª;¶äÌóÜ;ï.'4þóÿ+,(Ь(VþúóÏsç½ôËíØ«W¶mÙ"ÉÅbûêêê´®öjí±éçÊJktÙ
f¸3?£sÎô0BCãÖ2A"Àd
[kdenlive] [Bug 463089] macOS (and Windows?): Kdenlive UI does not show all localized strings from po files (especially in Preferences)
https://bugs.kde.org/show_bug.cgi?id=463089 --- Comment #9 from emohr --- Created attachment 158804 --> https://bugs.kde.org/attachment.cgi?id=158804&action=edit Kdenlive_QT-icon I can confirm that on Slovenian the Qt-Icons are not translated on Mac and Windows (as you show on your screenshot) . But Italian and Hebrew (for example), the Qt-Icons are translated. Maybe some Qt settings are not proper done: sl,Slovenian? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458987] Minimum window height is too tall for 780px tall screens
https://bugs.kde.org/show_bug.cgi?id=458987 Phoenix Awakened changed: What|Removed |Added Attachment #158802|text/docx |image/png mime type|| --- Comment #32 from Phoenix Awakened --- Comment on attachment 158802 --> https://bugs.kde.org/attachment.cgi?id=158802 Clear visibility of issue when panels are floating It seems that the Gwenview is not considering the panel is boundary for expansion. What if we make the editing options for Gwenview in Drop-down Menu ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440397] Plasma fails to launch with Wayland and NVidia (kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface failed")
https://bugs.kde.org/show_bug.cgi?id=440397 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED CC||xaver.h...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #11 from Zamundaaa --- (In reply to jamesilmarimakela from comment #9) > (In reply to Nate Graham from comment #8) > > Can we ask you to please check if this is still an issue with Plasma 5.27? > > Thanks! > > Still an issue for me with plasma 5.27. I have attached the output I receive > when I run the command `kwin_wayland --xwayland` from a terminal in an X11 > session. > > > No backend specified, automatically choosing X11 because DISPLAY is set > > kwin_wayland_x11windowed: X server supports SHM extension but not shared > > pixmaps > > kf.globalaccel.kglobalacceld: Failed to register service > > org.kde.kglobalaccel > > OpenGL vendor string: NVIDIA Corporation > > OpenGL renderer string: NVIDIA GeForce GTX 1070/PCIe/SSE2 > > OpenGL version string: 3.1.0 NVIDIA 530.41.03 > > OpenGL shading language version string: 1.40 NVIDIA via Cg compiler > > Driver: NVIDIA > > Driver version: 530.41.3 > > GPU class: Unknown > > OpenGL version: 3.1 > > GLSL version: 1.40 > > Linux kernel version: 6.2.12 > > Requires strict binding:no > > GLSL shaders: yes > > Texture NPOT support: yes > > Virtual Machine:no > > kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface > > failed" > > kwin_core: The used windowing system requires compositing > > kwin_core: We are going to quit KWin now as it is broken That's an unrelated error, for the nested session only. The feature causing the error you're running into has been removed for Plasma 6; if it still happens with Plasma 6, please make a separate bug report about this. As the original author hasn't answered, I'm closing this. If it's still happening with Plasma 5.27, just reopen it again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469535] New: No Documentation For DigiKam Command Line Options
https://bugs.kde.org/show_bug.cgi?id=469535 Bug ID: 469535 Summary: No Documentation For DigiKam Command Line Options Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: digikam-bugs-n...@kde.org Reporter: michael2macdon...@gmail.com Target Milestone: --- SUMMARY Running an application like DigiKam from the command line and passing options can be a very useful tool for power users and users with a very integrated workflow. Personally, I need it so that I can maintain two separate DigiKam databases (One shared DB for my family photos on a NAS, and a local DB for local files so that I can work without internet or slowdowns). Currently, I can not find any documentation for supported DigiKam command line options in the documentation or after a quick Google search. ADDITIONAL INFORMATION If I am missing something and the documentation does exist, please point it out. If it still seems hard to find even after you point it out, then maybe I can suggest ways to improve its visibility. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 469347] Itinerary on Android mix up multiple ticket from the same file
https://bugs.kde.org/show_bug.cgi?id=469347 Volker Krause changed: What|Removed |Added Version Fixed In||23.04.2 Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||itinerary/commit/a90d36abdc ||3ac1109279578528ebdcfe7d5e9 ||408 Resolution|--- |FIXED --- Comment #3 from Volker Krause --- Git commit a90d36abdc3ac1109279578528ebdcfe7d5e9408 by Volker Krause. Committed on 09/05/2023 at 15:29. Pushed by vkrause into branch 'release/23.04'. Fix attaching documents on multi-traveler reservations This was previously overwriting all subsequent reservations with the one of the first traveler. FIXED-IN: 23.04.2 M +2-2src/app/applicationcontroller.cpp https://invent.kde.org/pim/itinerary/commit/a90d36abdc3ac1109279578528ebdcfe7d5e9408 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 --- Comment #13 from michael2macdon...@gmail.com --- (In reply to Maik Qualmann from comment #2) > This is a bug that we probably won't be able to fix. It's a problem between > Qt and Wayland. Here on openSUSE (I use X11 by default) when I start a > native Wayland session I can't reproduce the problem. > > Maik Thanks for your help so far. I just wanted to understand the exact state of this issue. Is the consensus that this is an upstream bug with Qt and Wayland? Or are you still working on fixing the issue? I understand if you have not made progress or if it is a low-priority bug, I just want to make sure I am on the same page as you guys. I have done a little bit of research and I found one similar bug online. Here is the KDE fix with links to KDE bug reports if you are still working on it and think this might help: https://invent.kde.org/graphics/gwenview/-/commit/7ed543b53a9fb6d11ef95e439425ed71f952e66b -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 469347] Itinerary on Android mix up multiple ticket from the same file
https://bugs.kde.org/show_bug.cgi?id=469347 --- Comment #4 from Volker Krause --- Thank you for the documents and the detailed information on how to reproduce this, that helped a lot! Since we had already fixed the problem with corrupted filenames during the initial import it became much harder to spot that attaching extra documents to a multi-traveler trip is what broke things here. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469533] Dolphin freezes and eventually crashes when I am conntected to a network without internet
https://bugs.kde.org/show_bug.cgi?id=469533 Bug Janitor Service changed: What|Removed |Added Severity|grave |crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of image properties sidebar tab.
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #45 from MarcP --- I'm glad to see that the Properties tab is getting some love! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468778] Add screen recording options to "no screenshot taken on launch" window
https://bugs.kde.org/show_bug.cgi?id=468778 Luis B changed: What|Removed |Added CC||luis.bue...@server23.cc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469536] New: Freeze when disconnecting from networks
https://bugs.kde.org/show_bug.cgi?id=469536 Bug ID: 469536 Summary: Freeze when disconnecting from networks Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.26 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bixi...@bixilon.de CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Sometimes when disconnecting from networks, plasma shell freezes for a couple of seconds. It does not matter what network, it is random imho. But for every wireguard connection it happens. STEPS TO REPRODUCE 1. Connect to a network 2. Add a wireguard network 3. Conenct to the wireguard vpn 4. Disconenct from vpn via gui OBSERVED RESULT Normal disconenct or loading bar EXPECTED RESULT Freeze SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.0.19-060019-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 17.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82KC System Version: Lenovo V14 G2 ALC ADDITIONAL INFORMATION Backtrace: Thread 1 (Thread 0x7ff25ad0e9c0 (LWP 170313) "plasmashell"): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55a2a045ae30) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55a2a045ae30) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55a2a045ae30, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7ff25ea93ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55a2a045ade0, cond=0x55a2a045ae08) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x55a2a045ae08, mutex=0x55a2a045ade0) at ./nptl/pthread_cond_wait.c:627 #5 0x7ff25f2d476b in QWaitConditionPrivate::wait (deadline=..., deadline=..., this=0x55a2a045ade0) at thread/qwaitcondition_unix.cpp:146 #6 QWaitCondition::wait (this=this@entry=0x7ff25409cb20, mutex=mutex@entry=0x7ff25409cb18, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7ff25ffdf656 in QDBusPendingCallPrivate::waitForFinished (this=this@entry=0x7ff25409cae0) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #8 0x7ff25ff9af12 in QDBusConnectionPrivate::sendWithReply (this=0x7ff254006820, message=..., sendMode=1, timeout=) at ./src/dbus/qdbusintegrator.cpp:2088 #9 0x7ff25ff86a0b in QDBusConnection::call (this=this@entry=0x55a2a026a448, message=..., mode=mode@entry=QDBus::Block, timeout=) at ./src/dbus/qdbusconnection.cpp:680 #10 0x7ff25ffa3f5b in QDBusAbstractInterfacePrivate::property (this=this@entry=0x55a2a026a3f0, mp=..., returnValuePtr=returnValuePtr@entry=0x7fff1e69d090) at ./src/dbus/qdbusabstractinterface.cpp:179 #11 0x7ff25ffa6719 in QDBusAbstractInterfacePrivate::property (returnValuePtr=0x7fff1e69d090, mp=..., this=0x55a2a026a3f0) at ./src/dbus/qdbusabstractinterface.cpp:154 #12 QDBusAbstractInterfaceBase::qt_metacall (this=this@entry=0x55a2a021de00, _c=_c@entry=QMetaObject::ReadProperty, _id=, _a=_a@entry=0x7fff1e69d0d0) at ./src/dbus/qdbusabstractinterface.cpp:290 #13 0x7ff25ffa689b in QDBusAbstractInterface::qt_metacall (this=this@entry=0x55a2a021de00, _c=_c@entry=QMetaObject::ReadProperty, _id=, _a=_a@entry=0x7fff1e69d0d0) at .moc/moc_qdbusabstractinterface.cpp:104 #14 0x7ff1cc3bdffa in OrgFreedesktopNetworkManagerDeviceInterface::qt_metacall (this=0x55a2a021de00, _c=QMetaObject::ReadProperty, _id=, _a=0x7fff1e69d0d0) at ./obj-x86_64-linux-gnu/src/KF5NetworkManagerQt_autogen/KS3UX4TNHX/moc_deviceinterface.cpp:294 #15 0x7ff25f4c99fa in QMetaProperty::read (this=this@entry=0x7fff1e69d130, object=object@entry=0x55a2a021de00) at kernel/qmetaobject.cpp:3198 #16 0x7ff25f4efe1c in QObject::property (this=this@entry=0x55a2a021de00, name=name@entry=0x7ff1cc460124 "ActiveConnection") at kernel/qobject.cpp:4140 #17 0x7ff1cc3dfc4a in OrgFreedesktopNetworkManagerDeviceInterface::activeConnection (this=0x55a2a021de00) at ./obj-x86_64-linux-gnu/src/KF5NetworkManagerQt_autogen/EWIEGA46WW/../../../../src/dbus/deviceinterface.h:48 #18 NetworkManager::DevicePrivate::propertyChanged (this=0x55a2a021ddf0, property=..., value=...) at ./src/device.cpp:236 #19 0x7ff1cc3d97b2 in NetworkManager::DevicePrivate::propertiesChanged (this=0x55a2a021ddf0, properties=...) at ./src/device.cpp:620 #20 0x7ff1cc3c7861 in NetworkManager::DevicePrivate::qt_static_metacall (_a=0x7fff1e69d3a0, _id=1, _c=QMetaObject::InvokeMetaMethod, _o=0x55a2a021ddf0)
[plasmashell] [Bug 469536] Freeze when disconnecting from networks
https://bugs.kde.org/show_bug.cgi?id=469536 Moritz changed: What|Removed |Added CC||bixi...@bixilon.de -- You are receiving this mail because: You are watching all bug changes.
