[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta
https://bugs.kde.org/show_bug.cgi?id=483805 --- Comment #19 from Louis Moureaux --- Powersave icons -> https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/376 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta
https://bugs.kde.org/show_bug.cgi?id=483805 --- Comment #17 from Louis Moureaux --- The status quo is quite bad for me because I keep my system in power saving mode most of the time, so I can no longer see the battery level. But I appreciate having a status icon for power profiles as well. There are icons in 4 sizes (16/22/24/32) for 11 charge levels (000 to 100) and charging/not charging variants. All others are symbolic links. The way I made the icon is fairly straightforward: 1. Took one of the normal battery icon 2. Drew a simplified 8x8 leaf icon 3. Made a clipping shape by extruding the leaf by 1px 4. Subtracted the clipping shape from the normal battery icon Then I hand-tuned one node to avoid a weird shape but a better clipping path would do the job as well. I could automate this procedure to generate as many icons as needed from the emblems and clipping paths. I'd just have to draw 8 shapes and write a small script (hopefully the renderer supports clipping?), which is quite in the realm of feasibility. Creating the icons for Breeze is not an issue. The same logic could probably be implemented in QML, reducing the total number of icons but some of them would become quite technical. Switching to per-profile icons would send users back to the previous status quo. Whether this is an acceptable regression is IMHO something the maintainers should arbitrate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta
https://bugs.kde.org/show_bug.cgi?id=483805 --- Comment #15 from Louis Moureaux --- Created attachment 169735 --> https://bugs.kde.org/attachment.cgi?id=169735=edit Rendering of the proposed icon (32px) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta
https://bugs.kde.org/show_bug.cgi?id=483805 --- Comment #14 from Louis Moureaux --- Created attachment 169734 --> https://bugs.kde.org/attachment.cgi?id=169734=edit Rendering of the proposed icon (24px) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta
https://bugs.kde.org/show_bug.cgi?id=483805 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com --- Comment #13 from Louis Moureaux --- Created attachment 169733 --> https://bugs.kde.org/attachment.cgi?id=169733=edit Proposed icon design I think the performance mode could be shown as a small emblem on top of the battery icon. I quickly crammed something up in Inkscape to show what I mean. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 463303] Unplugging power cord wakes the computer from sleep
https://bugs.kde.org/show_bug.cgi?id=463303 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com --- Comment #4 from Louis Moureaux --- Experiencing the same issue (system info below). Plugging AC in or out always wakes up the system, even if the lid is closed. There is an EFI/BIOS setting to disable this behavior, but it has no effect. Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-10310U CPU @ 1.70GHz Memory: 15.3 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Latitude 7410 -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 475223] Access your keys or generate new QR codes
https://bugs.kde.org/show_bug.cgi?id=475223 --- Comment #4 from Louis Moureaux --- > I agree that this is needed. Also, other apps (e.g. andOTP) provide such > functionality. Also for GDPR compliance - right to access and right to data portability. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 486861] New: Memory leak in EWS resource
https://bugs.kde.org/show_bug.cgi?id=486861 Bug ID: 486861 Summary: Memory leak in EWS resource Classification: Frameworks and Libraries Product: Akonadi Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: EWS Resource Assignee: kdepim-b...@kde.org Reporter: m_loui...@yahoo.com CC: c...@carlschwan.eu, kri...@op.pl Target Milestone: --- SUMMARY The memory usage of the EWS resource keeps growing until I kill the process. STEPS TO REPRODUCE 1. Configure an EWS resources 2. Sync it 3. Wait a few hours OBSERVED RESULT The akonadi_ews_resource process uses all available RAM and renders the system unusable. On my system, the resource leaks about 1MB/s so I need to restart it after ~1h. EXPECTED RESULT Memory usage is roughly constant. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Memory: 15.3 Gio of RAM ADDITIONAL INFORMATION My mailbox contains thousands of emails totaling about 1GB. The akonadi log gets filled quickly with the following message: org.kde.pim.ews.client: Failed to process EWS request: I'm willing to investigate more (and find the leak) if someone would tell me how to start an agent manually. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 484579] Cannot create EWS Account Resource
https://bugs.kde.org/show_bug.cgi?id=484579 Louis Moureaux changed: What|Removed |Added Version|unspecified |6.0.1 CC||m_loui...@yahoo.com --- Comment #1 from Louis Moureaux --- I get the same behavior since today with a similar assert in a different location: ASSERT: "responses.size() == itemsToDo" in file ./resources/ews/ewsabstractchunkedjob.h, line 87 Both seem related to not receiving as many responses as expected. Relevant part of the log: == org.kde.pim.ews.client: Failed to process EWS request: org.kde.pim.ews: "Invalid number of responses received" org.kde.pim.ews: requestAuthFailed - going offline org.kde.pim.ews: reauthenticate: trying to refresh org.kde.pim.ews.client: Starting OAuth2 authentication org.kde.pim.kimap: sasl_client_start failed with: -4 "SASL(-4): no mechanism available: No worthy mechs found" org.kde.pim.ews.client: Failed to process EWS request: ASSERT: "responses.size() == itemsToDo" in file ./resources/ews/ewsabstractchunkedjob.h, line 87 org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_ews_resource" stopped unexpectedly ( "Le processus a planté" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_ews_resource' crashed! 1 restarts left. == Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-26-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 477908] Yakuake not working correctly after KWin Wayland crash
https://bugs.kde.org/show_bug.cgi?id=477908 --- Comment #5 from Louis Moureaux --- > Yakuake uses the KWayland library to do Wayland things. It doesn't handle > compositor restarts properly, likely causing this bug. Sounds like something I could look at if you have a more precise pointer (no promise though, especially on a timeline). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=385882 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 477908] Yakuake not working correctly after KWin Wayland crash
https://bugs.kde.org/show_bug.cgi?id=477908 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com --- Comment #3 from Louis Moureaux --- Related to https://bugs.kde.org/show_bug.cgi?id=385882 ? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 479384] External screen turning off when closing the laptop lid despite configured to stay enabled
https://bugs.kde.org/show_bug.cgi?id=479384 --- Comment #2 from Louis Moureaux --- Created attachment 167480 --> https://bugs.kde.org/attachment.cgi?id=167480=edit Relevant energy saving settings Adding a screenshot of the relevant energy saving settings -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 479384] External screen turning off when closing the laptop lid despite configured to stay enabled
https://bugs.kde.org/show_bug.cgi?id=479384 Louis Moureaux changed: What|Removed |Added Summary|energy settings not |External screen turning off |honered?|when closing the laptop lid ||despite configured to stay ||enabled -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 479384] energy settings not honered?
https://bugs.kde.org/show_bug.cgi?id=479384 Louis Moureaux changed: What|Removed |Added Product|neon|Powerdevil Assignee|neon-b...@kde.org |plasma-b...@kde.org Component|Packages Unstable Edition |general Version|unspecified |6.0.2 CC||m...@ratijas.tk, ||m_loui...@yahoo.com, ||natalie_clar...@yahoo.de --- Comment #1 from Louis Moureaux --- I can confirm on a DELL Latitude 7410 with a monitor connected via DisplayPort over USB-C, resembling the configuration of the original poster. I think this is more likely a Powerdevil bug than a Neon bug so I'm switching the Product category accordingly. Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-25-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-10310U CPU @ 1.70GHz Memory: 15.3 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Latitude 7410 $ 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/x86_64-linux-gnu/qt6/plugins/kf6/kscreen/KSC_Fake.so * KSC_KWayland.so: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kscreen/KSC_KWayland.so * KSC_QScreen.so: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kscreen/KSC_QScreen.so * KSC_XRandR.so: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kscreen/KSC_XRandR.so $ kscreen-doctor -o Output: 1 eDP-1 enabled connected priority 2 Panel Modes: 0:1920x1080@60*! 1:1920x1080@48 2:1280x1024@60 3:1024x768@60 4:1280x800@60 5:1920x1080@60 6:1600x900@60 7:1368x768@60 8:1280x720@60 Geometry: 0,1440 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic HDR: incapable Wide Color Gamut: incapable ICC profile: none Output: 2 DP-3 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@75! 1:2560x1440@60* 2:1920x1080@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1680x1050@60 7:1600x900@60 8:1280x1024@75 9:1280x1024@60 10:1440x900@60 11:1280x800@60 12:1152x864@75 13:1280x720@60 14:1280x720@60 15:1280x720@60 16:1280x720@50 17:1024x768@75 18:1024x768@70 19:1024x768@60 20:832x624@75 21:800x600@75 22:800x600@72 23:800x600@60 24:800x600@56 25:720x576@50 26:720x480@60 27:720x480@60 28:640x480@75 29:640x480@73 30:640x480@67 31:640x480@60 32:640x480@60 33:720x400@70 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic HDR: incapable Wide Color Gamut: incapable ICC profile: none -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 478669] New: FindLibGit2 checks the wrong pkgconfig library name
https://bugs.kde.org/show_bug.cgi?id=478669 Bug ID: 478669 Summary: FindLibGit2 checks the wrong pkgconfig library name Classification: Frameworks and Libraries Product: extra-cmake-modules Version: 5.246.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ecm-bugs-n...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- SUMMARY The FindLibGit2 module queries pkgconfig for the "git2" module. The actual module is called "libgit2", at least on Kde Neon and Fedora 40. This can be verified by checking the name of the ".pc" file. STEPS TO REPRODUCE 1. Use FindLibGit2 with a custom build of libgit2, not in the system library path 2. Provide the correct path to pkg-config by setting CMAKE_PREFIX_PATH appropriately 3. find_package(LibGit2) fails to find libgit2 4. Change the module name to "libgit2" in FindLibGit2.cmake 5. find_package(LibGit2) finds libgit2 correctly OBSERVED RESULT find_package(LibGit2) cannot find the custom libgit2. EXPECTED RESULT find_package(LibGit2) finds the custom libgit2. SOFTWARE/OS VERSIONS Linux: Custom environment used by the CMS Experiment at CERN KDE Frameworks Version: Find module copied from current master -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403309] akregator crash when switching to it in Kontact
https://bugs.kde.org/show_bug.cgi?id=403309 --- Comment #2 from Louis Moureaux --- Created attachment 163542 --> https://bugs.kde.org/attachment.cgi?id=163542=edit New crash information added by DrKonqi kontact (5.24.2 (23.08.2)) using Qt 5.15.11 Akregator sometimes crashes Kontact when switching to it. This is the first time I see this bug but looking at bug 378513 (and its duplicates) it looks like it might have been around for a while. -- Backtrace (Reduced): #8 0x7f85c0235e2c in qobject_cast (object=0x561d4aae2300) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:519 #9 Akregator::FrameManager::saveProperties (this=0x561d4a2ff3f0, config=...) at ./src/frame/framemanager.cpp:250 #10 0x7f85cc0ec83e in Akregator::MainWidget::saveProperties (this=0x561d4cb05050, config=...) at ./src/mainwidget.cpp:1224 #11 0x7f85cc0defa4 in Akregator::Part::saveProperties (config=..., this=0x561d4a2a6fa0) at ./src/akregator_part.cpp:347 #12 Akregator::Part::saveCrashProperties (this=0x561d4a2a6fa0) at ./src/akregator_part.cpp:723 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403309] akregator crash when switching to it in Kontact
https://bugs.kde.org/show_bug.cgi?id=403309 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 475223] Access your keys or generate new QR codes
https://bugs.kde.org/show_bug.cgi?id=475223 --- Comment #2 from Louis Moureaux --- > I believe it's intentional for Keysmith not to reveal the TOTP secrets for > security reasons. I'd be glad to hear the reasons... If an attacker has access to the 2FA device then the account is already compromised... -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 475223] New: Access your keys or generate new QR codes
https://bugs.kde.org/show_bug.cgi?id=475223 Bug ID: 475223 Summary: Access your keys or generate new QR codes Classification: Applications Product: Keysmith Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: bhus...@gmail.com Reporter: m_loui...@yahoo.com Target Milestone: --- SUMMARY I would like to use a TOTP from multiple apps and devices. This could be enabled by generating a new QR code from data saved by Keysmith. Similarly, it would be nice to have access to my saved secrets. STEPS TO REPRODUCE 1. Add a TOTP key 2. Try to find your secret again to use it on another device OBSERVED RESULT The secret cannot be displayed. EXPECTED RESULT Users are in control of their data, which includes displaying it. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 474299] Typing long text in PDF forms extremely slow
https://bugs.kde.org/show_bug.cgi?id=474299 Louis Moureaux changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Louis Moureaux --- Duh just checked 23.08 and it's fixed there. Thank you for this and sorry for the noise! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 474299] New: Typing long text in PDF forms extremely slow
https://bugs.kde.org/show_bug.cgi?id=474299 Bug ID: 474299 Summary: Typing long text in PDF forms extremely slow Classification: Applications Product: okular Version: 23.04.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- Created attachment 161510 --> https://bugs.kde.org/attachment.cgi?id=161510=edit Profile SUMMARY When editing a (specific) PDF form with a "free text" field, typing is extremely slow with okular at 100% CPU usage (multiple seconds per character). A quick profile shows Poppler::FormFieldText::setText(QString) as the main culprit, apparently reloading fonts and querying FontConfig in the process. Okular shouldn't call this function on every edit (and I suspect even for every letter in the text, else it wouldn't be so slow). STEPS TO REPRODUCE 1. Open a PDF form with a multiline text field (I can test patches/share mine privately if needed) 2. Try to type some text OBSERVED RESULT Wait for 5 seconds per letter you type EXPECTED RESULT Editing test is instant SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.2.0-31-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429665] Touchpad Tap-to-click should be enabled by default in System Settings
https://bugs.kde.org/show_bug.cgi?id=429665 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com --- Comment #7 from Louis Moureaux --- This is one of the few settings that I consistently change when installing a new Kde on a laptop. On the touchpads I've used so far, there is no way of positioning my hand so I can do all types of clicks without moving my wrist significantly. Without touch-to-click, I need to give up on either moving the pointer, left clicking, or right clicking. To give an idea, if the touch sensitive area is the JKL; row of a US keyboard, left click is the B key, and right click is the right CTRL key (or if you're left-handed, it would be be ASDF/meta key/B key respectively). As Tyson noted, pressing the mouse click areas requires a lot of force, more than pressing a key on the keyboard. The same usability issue arises in SDDM, for which there is no nice configuration GUI, so maybe it needs to be fixed at the distro or libinput level indeed. It was mentioned in #436077 that libinput wouldn't change their default (https://wayland.freedesktop.org/libinput/doc/latest/tapping.html#tap-to-click-default-setting). Maybe they will agree to reconsider a 9-years-old decision in the light of market changes: most laptops sold today no longer even have a visual hint that there are buttons hidden under the touchpad. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461887] libpoppler-glib8 as shipped in Neon breaks Inkscape PDF import
https://bugs.kde.org/show_bug.cgi?id=461887 --- Comment #7 from Louis Moureaux --- I'm afraid this will never be fixed, it's apparently a policy that breaking Gtk apps is fine. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 467734] New: Automatic detection of email providers using Office 365
https://bugs.kde.org/show_bug.cgi?id=467734 Bug ID: 467734 Summary: Automatic detection of email providers using Office 365 Classification: Applications Product: kmail2 Version: 5.22.3 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- Microsoft provides many organization emails around the world through its Office 365 product so it would be good to have first-class support in KMail. KMail already features EWS support, but setting it up for O365 is far from intuitive [1]. Fortunately, detecting O365 emails is easy. If the address is u...@example.com: 1. Perform a MX DNS lookup for example.com 2. Look at the first exchange record. The provider uses Office 365 if the exchange is of the form: example-com.mail.protection.outlook.com One can then reasonably assume that Office 365 EWS is supported. Adding this simple check to the account setup wizard could enhance its results for a large number of (corporate) domains. Saving the users from the hassle of setting up EWS all resources (incoming, outgoing, contacts, calendar) by hand would be a significant improvement. [1] https://userbase.kde.org/Kmail/Configuring_Kmail/Accounts/Office_365 ADDITIONAL INFORMATION Office 365 setup instructions with MX record details: https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider?view=o365-worldwide#add-an-mx-record-for-email-outlook-exchange-online Some example domains using O365 (as of 2023): ulb.be, student.uclouvain.be, cern.ch In my testing, QDnsLookup did the MX lookups perfectly well. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep due to kwin_x11 abort
https://bugs.kde.org/show_bug.cgi?id=463379 --- Comment #21 from Louis Moureaux --- Created attachment 156960 --> https://bugs.kde.org/attachment.cgi?id=156960=edit Stack trace of crashing kwin_x11 So it happened again and I was able to gdb in and grab a stack trace of crashing kwin_x11. It looks completely different from the symptoms I described yesterday, not sure why. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463379] Double Monitor: Lock-screen, after some indefinite amount of time, will fail to actually display when the machine is taken out of sleep due to kwin_x11 abort
https://bugs.kde.org/show_bug.cgi?id=463379 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com --- Comment #20 from Louis Moureaux --- I ran into a similar issue today that eventually degenerated into a total breakdown of the system. I was able to get a stack trace but it was lost when I had to reboot. It all started with a wakeup from sleep with an external screen. Restarting kwin_x11 seemed to have solved the issue, but one day later it started again. The main symptom was kwin_x11 exiting with code 1 (hence no DrKonqi like in the original report). I recall the stack trace being in the default X11 error handler and seeing error messages about the X11 connection being lost. X11 was still running and other applications working properly. I also recall seeing effect classes and GL functions in the last levels of the trace (I know this is very unspecific but that's what I have). At first the issue seemed to be related to a window being activated in fullscreen (both my own Qt app and Zoom). Eventually even notifications coming on top of a fullscreen window appeared to trigger a crash. It even crashed on alt-tabbing. Towards the end (after many kwin restarts) the system also prompted me to increase the inotify limit, but this may be unrelated. I tried upgrading KWin and other packages on the unstable system but it didn't seem to help. I'm now running 5.27.2. System info (after upgrade): === Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-32-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-10310U CPU @ 1.70GHz Memory: 15.3 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Latitude 7410 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461887] libpoppler-glib8 as shipped in Neon breaks Inkscape PDF import
https://bugs.kde.org/show_bug.cgi?id=461887 --- Comment #4 from Louis Moureaux --- The problematic package isn't needed by any Kde app: libpoppler-glib8 Reverse Depends: inkscape ...no kde software... Now I understand that libpoppler-glib8 is built from the poppler source package, for which there are Qt and Kde reverse deps. Not building libpoppler-glib8 (and libpoppler-cil) for Neon would help, since Inkscape would then use the one from Ubuntu built against libpoppler118 (which is perfectly co-installable with libpoppler126). A more elegant and work-intensive option would be to use versioned libpoppler126-* packages just like the base libpoppler package does. Please reconsider, this affects a flagship free software project that Kde doesn't have a viable alternative for. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 464562] KWrite resets the shown toolbars after restart
https://bugs.kde.org/show_bug.cgi?id=464562 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com --- Comment #1 from Louis Moureaux --- I'm affected by the same issue in Kate. Only the hamburger toolbar seems to be affected, the other one doesn't reappear. This is most likely related to using the app with the menu bar disabled (and thus the hamburger toolbar wanting to be shown). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 465295] New: The KWrite text area can be resized inside its window
https://bugs.kde.org/show_bug.cgi?id=465295 Bug ID: 465295 Summary: The KWrite text area can be resized inside its window Classification: Applications Product: kate Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- Created attachment 155946 --> https://bugs.kde.org/attachment.cgi?id=155946=edit Screenshot of a resized KWrite text area SUMMARY In KWrite, one can grab invisible handles next to the window edges to resize the text area. I suspect this is inherited from Kate's panel resizing feature, just without the panels. STEPS TO REPRODUCE 1. Open KWrite 2. Grab an invisible (with Breeze) handle close to a window edge or the border between the toolbar and the text area. For this, act as if you wanted to resize the window but grab the edge a little bit to the inside (the active area is large enough that this isn't very hard) 3. Move the handle to the inside of the window OBSERVED RESULT The text area gets resized, with empty content on the sides. See screenshot EXPECTED RESULT The invisible handles are disabled in KWrite mode/when there isn't any plugin. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 335932] DrKonqi cannot file bugs against kdeinit5
https://bugs.kde.org/show_bug.cgi?id=335932 Louis Moureaux changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Louis Moureaux --- Thanks Justin for the reminder! I no longer have a running kdeinit5 process in recent Plasma versions (on both Arch and Neon). I don't know what happens now when kdeinit crashes, but I don't have an easy way to trigger it. Setting as WORKSFORME since I can no longer easily trigger a kdeinit crash and hence cannot reproduce... -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 464380] Connect to WiFi
https://bugs.kde.org/show_bug.cgi?id=464380 --- Comment #4 from Louis Moureaux --- Thanks! I could add a few extra SSIDs to this file, most of them without any restricted API (that I know of): - "_WIFI_LYRIA" for TGV Lyria between France and Switzerland, likely using some variant of the SNCF API - "RRX Hotspot" for Rhein Ruhr Express trains - "FreeWifi-NmbsSncb" for Belgian railway stations - "wifi.brussels" for Brussels metro stations and public spaces - I could go and dig a couple airports from my NM history I think handling the login procedure automatically needs consideration from the legal point of view because the user needs to accept the terms & conditions. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 464380] Connect to WiFi
https://bugs.kde.org/show_bug.cgi?id=464380 --- Comment #2 from Louis Moureaux --- I thought Importance: Wishlist was for wishlist items (ie feature requests). Please correct me if I'm wrong and point me to the appropriate channel. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 464380] New: Connect to WiFi
https://bugs.kde.org/show_bug.cgi?id=464380 Bug ID: 464380 Summary: Connect to WiFi Classification: Applications Product: KDE Itinerary Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- SUMMARY It would be great if Itinerary would know WiFi SSIDs for common carriers and airports/stations, offer to connect automatically when it detects them, and open the login page in the browser. ADDITIONAL INFORMATION Common pitfalls could also be reported, for instance Docker conflicts with DB ICE WiFi (the Docker virtual network eats requests to wifionice.de). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 464309] New: Occasional crash when saving
https://bugs.kde.org/show_bug.cgi?id=464309 Bug ID: 464309 Summary: Occasional crash when saving Classification: Applications Product: kate Version: 22.12.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- Application: kate (22.12.1) Qt Version: 5.15.8 Frameworks Version: 5.101.0 Operating System: Linux 5.15.0-58-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: Kate crashed when saving a document. This happens from time to time, albeit rarely. In case it matters, the following plugins are enabled: * Tree view * Search & replace * LSP client * Document switcher * Filesystem explorer * Text filter * Git blame * Project plugin * External tools * Terminal view The crash can be reproduced sometimes. -- Backtrace: Application: Kate (kate), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140717676504064) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140717676504064) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140717676504064, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7ffb6817f476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7ffb681657f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7ffb681c66f6 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffb68318b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #10 0x7ffb681ddd7c in malloc_printerr (str=str@entry=0x7ffb68316764 "free(): invalid pointer") at ./malloc/malloc.c:5664 #11 0x7ffb681dfac4 in _int_free (av=, p=, have_lock=0) at ./malloc/malloc.c:4439 #12 0x7ffb681e24d3 in __GI___libc_free (mem=) at ./malloc/malloc.c:3391 #13 0x7ffb68698757 in QHashData::free_helper (this=0x55846d6cf720, node_delete=0x7ffb68e40a10 ::deleteNode2(QHashData::Node*)>) at tools/qhash.cpp:573 #14 0x7ffb68ef82a0 in QHash::freeData (x=, this=0x55846ea64ab0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:617 #15 QHash::~QHash (this=0x55846ea64ab0, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qhash.h:250 #16 QMultiHash::~QMultiHash (this=0x55846ea64ab0, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qhash.h:1020 #17 QTextFormatCollection::~QTextFormatCollection (this=0x55846ea64aa0, __in_chrg=) at text/qtextformat.cpp:3828 #18 0x7ffb68edcc1b in QScopedPointerDeleter::cleanup (pointer=0x55846ea64aa0) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:52 #19 QScopedPointer >::~QScopedPointer (this=0x55846d473fa0, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:107 #20 QTextEngine::SpecialData::~SpecialData (this=0x55846d473f80, __in_chrg=) at text/qtextengine_p.h:607 #21 QTextEngine::~QTextEngine (this=0x5584708db570, __in_chrg=) at text/qtextengine.cpp:1992 #22 0x7ffb68eebdb0 in QTextLayout::~QTextLayout (this=, __in_chrg=) at text/qtextlayout.cpp:389 #23 0x7ffb67e3963c in std::default_delete::operator() (this=, __ptr=0x55846e96bcb0) at /usr/include/c++/11/bits/unique_ptr.h:79 #24 std::default_delete::operator() (__ptr=0x55846e96bcb0, this=) at /usr/include/c++/11/bits/unique_ptr.h:79 #25 std::unique_ptr >::~unique_ptr (this=0x5584705a0140, __in_chrg=) at /usr/include/c++/11/bits/unique_ptr.h:361 #26 KateLineLayout::~KateLineLayout (this=0x5584705a0110, __in_chrg=) at ./src/render/katelinelayout.h:26 #27 QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer (this=, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qshareddata.h:184 #28 QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer (this=, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qshareddata.h:184 #29 0x7ffb67f0551d in QPair >::~QPair (this=0x55846e44db10, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpair.h:49 #30 std::_Destroy > > (__pointer=0x55846e44db10) at /usr/include/c++/11/bits/stl_construct.h:151 #31 std::_Destroy_aux::__destroy >*> (__last=, __first=0x55846e44db10) at /usr/include/c++/11/bits/stl_construct.h:163 #32 std::_Destroy >*> (__last=, __first=) at /usr/include/c++/11/bits/stl_construct.h:196 #33 std::_Destroy >*, QPair > > (__last=, __first=) at /usr/include/c++/11/bits/alloc_traits.h:848 #34 std::vector >, std::allocator > > >::_M_erase_at_end (__pos=0x55846e44da50, this=0x55846ea82648) at /usr/include/c++/11/bits/stl_vector.h:1796 #35 std::vector >, std::allocator > > >::clear (this=0x55846ea82648) at /usr/include/c++/11/bits/stl_vector.h:1499 #36 KateLineLayoutMap::clear (this=0x55846ea82648) at ./src/render/katelayoutcache.cpp:33 #37 KateLayoutCache::clear (this=0x55846ea82630) at ./src/render/katelayoutcache.cpp:483 #38
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 Louis Moureaux changed: What|Removed |Added CC||m_loui...@yahoo.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Louis Moureaux --- I was affected by the same issue, however I can no longer reproduce since I upgraded to KMail 5.22.1 (Frameworks 5.101). Could you please confirm that you still see the bug in the new version? I'm setting this bug as NEEDSINFO/WAITINGFORINFO; please set it back to REPORTED if you can still reproduce with the new version, or RESOLVED/FIXED otherwise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462396] New: KWin allows (and sometimes creates) nearly invisible 1-sized windows
https://bugs.kde.org/show_bug.cgi?id=462396 Bug ID: 462396 Summary: KWin allows (and sometimes creates) nearly invisible 1-sized windows Classification: Plasma Product: kwin Version: 5.26.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- Created attachment 154138 --> https://bugs.kde.org/attachment.cgi?id=154138=edit Here I moved the window on top of the Submit Bug button SUMMARY [Sorry if wrong component or product.] KWin on X11 allows windows to be extremely small, and window decorations follow suit, resulting in nearly invisible windows. Haven't tried on Wayland. STEPS TO REPRODUCE 1. Execute the following PyQt code, preferably on a high-res or large display: import sys from PyQt5 import QtWidgets as w app = w.QApplication(sys.argv) wdg = w.QWidget() wdg.resize(1, 1) wdg.show() 2. Try to find the window you just opened OBSERVED RESULT The window is extremely small, making it very hard to find and interact with. EXPECTED RESULT Window decorations remain visible around the window. Not sure what to do with windows that have no decorations. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-52-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-10310U CPU @ 1.70GHz Memory: 15.3 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Latitude 7410 ADDITIONAL INFORMATION KWin sometimes resizes a window to such a size by itself, which seems to be associated with switching between two screens with vastly different resolutions and a layout combining those. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 380335] Problems closing activities when applications ask for confirmation before closing
https://bugs.kde.org/show_bug.cgi?id=380335 Louis Moureaux changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Louis Moureaux --- Even though the behavior has changed, this is still not handled correctly. Nowadays, the confirmation dialog isn't shown to the user and the app (Kate in the original example) asking for confirmation keeps running. I expect to see the confirmation dialog and only stop the activity if I confirm. I suspect the running app will be killed on logout and the unsaved data will be lost, but I didn't dare to try. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 461466] Kde for Kids: GCompris text is unreadable
https://bugs.kde.org/show_bug.cgi?id=461466 --- Comment #2 from Louis Moureaux --- This appears to be caused by Firefox being configured in dark mode. Switching to a light theme makes the text readable. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461887] libpoppler-glib8 as shipped in Neon breaks Inkscape PDF import
https://bugs.kde.org/show_bug.cgi?id=461887 Louis Moureaux changed: What|Removed |Added Summary|libpoppler-glib8|libpoppler-glib8 as shipped |22.04.0-1+20.04+focal+relea |in Neon breaks Inkscape PDF |se+build4 breaks Inkscape |import |PDF import | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461887] libpoppler-glib8 22.04.0-1+20.04+focal+release+build4 breaks Inkscape PDF import
https://bugs.kde.org/show_bug.cgi?id=461887 --- Comment #1 from Louis Moureaux --- My bad, that version actually works. Though it is definitely broken in 22.04. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461887] New: libpoppler-glib8 22.04.0-1+20.04+focal+release+build4 breaks Inkscape PDF import
https://bugs.kde.org/show_bug.cgi?id=461887 Bug ID: 461887 Summary: libpoppler-glib8 22.04.0-1+20.04+focal+release+build4 breaks Inkscape PDF import Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: m_loui...@yahoo.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY The version of libpoppler-glib8 shipped by Neon (22.04.0-1+20.04+focal+release+build4) breaks PDF import in Inkscape. This is also the case on another machine that uses Neon based on Ubuntu 22.04. Please see https://gitlab.com/inkscape/inbox/-/issues/7834. I couldn't find a KDE package that would depend on libpoppler-glib8. The other major rdep of libpoppler-glib8, Gimp, seems to import the same document just fine. STEPS TO REPRODUCE 1. Install inkscape (in this case from the 20.04 backports) 2. Follow the instructions from the aforementioned issue. OBSERVED RESULT Inkscape deadlocks. EXPECTED RESULT Inkscape works. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-52-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 461467] New: Kde for Creators: French translations are terrible
https://bugs.kde.org/show_bug.cgi?id=461467 Bug ID: 461467 Summary: Kde for Creators: French translations are terrible Classification: Websites Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- SUMMARY Many French translations on the Kde for Creators page are incorrect (some even grammatically). STEPS TO REPRODUCE 1. Learn French if needed 2. Read https://kde.org/fr/for/creators/ OBSERVED RESULT The following are simply incorrect: - "For Artists Using KDE Applications." -> "Pour les artistes utilisant les Applications de KDE": French doesn't use Title Case, should be lowercase "applications" - "Fund it" -> "Financer le" (correct: simply "Financer") - "Learn More" -> "Plus d'informations" (correct: "Plus d'information", it's uncountable) - "Join the krita-artists.org community to share your art with other artists." -> there is a Markdown error in the translation - Kdenlive's slogan in French is "Gérez vos photos comme un professionnel grâce à la puissance de l'Open Source", not "Gestion professionnelle de photos avec le pouvoir du monde « Open source »" (unless the Kdenlive translation was changed recently) - "Quickly find your best images using labels" -> "Trouver rapidement vos meilleures images par utilisation d’étiquettes": missing article before "utilisation" (better: "...avec des étiquettes") - "Capture color from your screen and keep track of them" -> "Capturer une couleur sur votre écran et mémoriser la": "la mémoriser" or "Capturez... et mémorisez-la", but mixing them is incorrect (the first suggestion is in line with the rest of the page) - "Artwork by X" (in the Krita carroussel) -> "Œuvre artistique par X": several problems here: * One says "Œuvre d'art" and not "artistique" * One says "Œuvre de X" and not "par X" * "Œuvre" implies a qualitative judgment and sounds pretentious. Maybe simply use "Tableau par X" or "Peinture par X" (here it's "par" and not "de", French is complicated). "Peinture numérique par X" would fit Krita very well but is no longer a simple translation. The following are convoluted and could be simplified: - "Digital Painting for Human Beings" -> "Peinture numérique pour les êtres humains": I think what's meant here is "Peinture numérique pour les gens normaux" or "pour tous" - "Neutral color support" -> "Prise en charge de la couleur neutre" is unnecessarily long, sugg. "Couleurs neutres" - "Obtenir un aperçu pour la prise en charge de toutes vos images" -> "Un aperçu pour toutes vos images" - "Afficher un aperçu de vos fichiers de Krita directement depuis le gestionnaire de fichiers et l'afficheur d’images" -> "Prévisualisez vos fichiers Krita directement depuis..." EXPECTED RESULT It looks like the text was written in French in the first place. SOFTWARE/OS VERSIONS Firefox 106.0.2 on Plasma ADDITIONAL INFORMATION Page advertised by Nate in his weekly review (https://pointieststick.com/2022/11/04/this-week-in-kde-big-brain-krunner/) -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 461466] New: Kde for Kids: GCompris text is unreadable
https://bugs.kde.org/show_bug.cgi?id=461466 Bug ID: 461466 Summary: Kde for Kids: GCompris text is unreadable Classification: Websites Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- Created attachment 153496 --> https://bugs.kde.org/attachment.cgi?id=153496=edit Screenshot showing the bug SUMMARY In at least the French, German, English, Dutch, and Spanish versions of the Kde for Kids page, the text describing GCompris is unreadable. STEPS TO REPRODUCE 1. Navigate to https://kde.org/fr/for/kids/ 2. Scroll down to "GCompris" (it's the first entry) OBSERVED RESULT See attachment EXPECTED RESULT Maybe the text should use color: black, but even then it looks blurry. SOFTWARE/OS VERSIONS Firefox 106.0.2 on Plasma ADDITIONAL INFORMATION Page advertised by Nate in his weekly review (https://pointieststick.com/2022/11/04/this-week-in-kde-big-brain-krunner/) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 435090] No error is reported when the SSL handshake fails
https://bugs.kde.org/show_bug.cgi?id=435090 --- Comment #1 from Louis Moureaux --- SSL errors are still not handled correctly as of 5.21.2 (22.08.2). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 461184] The Kate session runner reuses the current Kate instance
https://bugs.kde.org/show_bug.cgi?id=461184
--- Comment #6 from Louis Moureaux ---
It indeed does work as intended when you type "kate" in the KRunner search box
and select one of the results. The bug appears only if you search for your
session by name.
I made a recording where I have a session open ("fcweb") and I open another one
("pyciv") twice: the first time by typing "kate" in the search field, the
second time by typing "pyciv". The first attempt works as expected, the second
shows the bug.
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 461184] The Kate session runner reuses the current Kate instance
https://bugs.kde.org/show_bug.cgi?id=461184 --- Comment #5 from Louis Moureaux --- Created attachment 153335 --> https://bugs.kde.org/attachment.cgi?id=153335=edit Screencast demonstrating the bug -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 461184] New: The Kate session runner reuses the current Kate instance
https://bugs.kde.org/show_bug.cgi?id=461184 Bug ID: 461184 Summary: The Kate session runner reuses the current Kate instance Classification: Plasma Product: krunner Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m_loui...@yahoo.com CC: alexander.loh...@gmx.de Target Milestone: --- SUMMARY Using the Kate session runner to open a session when Kate is already running closes the currently open Kate session and replaces it with the requested session. It should open a new Kate instance instead. STEPS TO REPRODUCE 1. Create two sessions in Kate 2. Close Kate 3. Open the first session 4. Open the second session directly from KRunner OBSERVED RESULT The open Kate instance switches to the second session. EXPECTED RESULT A new Kate window appears with session 2. The window with session 1 isn't affected. SOFTWARE/OS VERSIONS KDE Plasma: 5.26.2 (Arch Linux) KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Wayland ADDITIONAL INFORMATION There's a 10-years-old bug reporting the same issue (https://bugs.kde.org/show_bug.cgi?id=222987), but I doubt it's related. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 460589] New: Rare crash in KateLayoutCache::textLayout when duplicating lines
https://bugs.kde.org/show_bug.cgi?id=460589 Bug ID: 460589 Summary: Rare crash in KateLayoutCache::textLayout when duplicating lines Classification: Applications Product: kate Version: 22.08.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: m_loui...@yahoo.com Target Milestone: --- Application: kate (22.08.1) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-46-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.25 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Kate crashed on me while editing, more precisely: * I had selected multiple lines of text * I triggered the action "Duplicate selected lines below" using a custom keyboard shortcut Despite using this action very often, it is the first time I see this crash. The crash can be reproduced sometimes. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [New LWP 932684] [New LWP 932701] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f611c86599f in __GI___poll (fds=0x7ffd57890138, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f6117a889c0 (LWP 932683))] Thread 3 (Thread 0x7f60f0870700 (LWP 932701)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e1280214a8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e128021458, cond=0x55e128021480) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e128021480, mutex=0x55e128021458) at pthread_cond_wait.c:647 #3 0x7f60f0c355eb in cnd_wait (mtx=0x55e128021458, cond=0x55e128021480) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55e128019d50) at ../src/util/u_queue.c:294 #5 0x7f60f0c351eb in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f611b5eb609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f611c872133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f6116c98700 (LWP 932684)): #0 0x7f611c86599f in __GI___poll (fds=0x7f6110015010, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f611aa3536e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f611aa354a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f611ce36b6b in QEventDispatcherGlib::processEvents (this=0x7f611b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f611cddab0b in QEventLoop::exec (this=this@entry=0x7f6116c97bb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f611cbf4342 in QThread::exec (this=this@entry=0x7f611e070d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f611dfecf4b in QDBusConnectionManager::run (this=0x7f611e070d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #7 0x7f611cbf5543 in QThreadPrivate::start (arg=0x7f611e070d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:330 #8 0x7f611b5eb609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f611c872133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f6117a889c0 (LWP 932683)): [KCrash Handler] #4 std::__atomic_base::operator++ (this=0x0) at /usr/include/c++/9/bits/atomic_base.h:318 #5 QAtomicOps::ref (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:283 #6 QBasicAtomicInteger::ref (this=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:118 #7 QExplicitlySharedDataPointer::QExplicitlySharedDataPointer (adata=0x0, this=0x7ffd57890e80) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qshareddata.h:285 #8 KateLineLayout::viewLine (this=0x0, viewLine=viewLine@entry=0) at ./src/render/katelinelayout.cpp:169 #9 0x7f611c510402 in KateLayoutCache::textLayout (this=this@entry=0x55e12b194750, realLine=, _viewLine=_viewLine@entry=0) at ./src/render/katelayoutcache.cpp:305 #10 0x7f611c56a813 in KateViewInternal::nextLayout (this=this@entry=0x55e12aa56540, c=...) at ./src/include/ktexteditor/cursor.h:199 #11 0x7f611c579fef in KateViewInternal::cursorDown (this=0x55e12aa56540, sel=false) at ./src/include/ktexteditor/cursor.h:87 #12 0x7f611ce132c2 in QtPrivate::QSlotObjectBase::call (a=0x7ffd578910f0, r=0x55e12b24f830, this=0x55e12578de40) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x55e12578dba0, signal_index=4,
[marble] [Bug 378885] Marble crashes sometime when using the vector map theme
https://bugs.kde.org/show_bug.cgi?id=378885 --- Comment #15 from Louis Moureaux --- Could not reproduce using Marble 22.08.1 from Flathub. Tried navigating, zooming in and out several times, getting directions. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423691] Recipients are sometimes merged
https://bugs.kde.org/show_bug.cgi?id=423691 Louis Moureaux changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Louis Moureaux --- Haven't had this problem in a while. Probably PEBKAC -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 319418] Freeciv animations don't work
https://bugs.kde.org/show_bug.cgi?id=319418 Louis Moureaux changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #9 from Louis Moureaux --- Freeciv for Gtk2 is no longer supported. It does work with Breeze in Gtk3.22. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 403504] Printer model crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=403504 Louis Moureaux changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Louis Moureaux --- Can't recall seeing this crash in a long time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453975] New: Missing find_package(Qt5 COMPONENTS WaylandClientPrivate)
https://bugs.kde.org/show_bug.cgi?id=453975 Bug ID: 453975 Summary: Missing find_package(Qt5 COMPONENTS WaylandClientPrivate) Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m_loui...@yahoo.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 148941 --> https://bugs.kde.org/attachment.cgi?id=148941=edit Complete configure+generate log SUMMARY Plasma apparently requires WaylandClientPrivate, but its availability isn't checked with a find_package call. This causes a failure when generating the build system. STEPS TO REPRODUCE Use Kde Neon. 1. Make sure "qtwayland5-private-dev" is not installed 2. Configure plasma-workspace through kdesrc-build, using system Qt (I also used Neon packages for other dependencies) 3. See it fail, read the log OBSERVED RESULT CMake fails to generate with (full log in attachment): CMake Error at /usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsMacros.cmake:182 (add_library): Target "appmenu" links to target "Qt::WaylandClientPrivate" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? Call Stack (most recent call first): appmenu/CMakeLists.txt:16 (kcoreaddons_add_plugin) EXPECTED RESULT find_package() reports a missing component. Note that qtwayland5-private-dev doesn't provide WaylandClientPrivateConfig.cmake so we may need to write a find module. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kde Neon user (available in About System) KDE Plasma Version: master = c0cb9f9929cfca683313252ebe95a0ac2b62f6e8 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 as in Neon -- You are receiving this mail because: You are watching all bug changes.
