[plasmashell] [Bug 467835] On login, containment for left-most screen places on right-most screen, and left-most screen gets a black background
https://bugs.kde.org/show_bug.cgi?id=467835 --- Comment #6 from mira...@mirandastreeter.com --- I've had similar issues occur on wayland, but I haven't looked through the kscreen output or anything for a true comparison. And for the config: [ScreenConnectors] 0=DP-2 1=HDMI-A-1 2=HDMI-0 3=DP-3 4=HDMI-1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468191] Backup hanging
https://bugs.kde.org/show_bug.cgi?id=468191 --- Comment #2 from Guy --- That's cool.thanks for the feedback, if backing up manually works, I can deal with that. I'll check for an update and see if it Corrects the problem but to answer your question, I'm just saving to a local drive - either the same filesystem or another physical drive in the same chassis. Appreciate the rapid response . Guy On Wed, Apr 5, 2023, 10:15 PM Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=468191 > > Jack changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Jack --- > First, 5.0.6 is really old. Please try a more recent version - 5.1.3 is > current. > For your problem, what happens if you do not tick the box to mount the > backup > directory? Where are you trying to back up the file? To a local > directory or > a network share? > For your last question, yes, simply making a copy of the .kmy file is all a > backup does, so that is sufficient - but you should use some naming > convention > so each backup does not simply overwrite the previous one. > Let us know if any of this helps. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462054] Normalize (2 pass) doesn't work. Analyze gives empty result
https://bugs.kde.org/show_bug.cgi?id=462054 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467678] Messaging acting up
https://bugs.kde.org/show_bug.cgi?id=467678 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466886] Keyboard shortcuts are not displayed in the latest stable kde
https://bugs.kde.org/show_bug.cgi?id=466886 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 467597] Filelight crashes
https://bugs.kde.org/show_bug.cgi?id=467597 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 468162] Deployments appearing in all searches
https://bugs.kde.org/show_bug.cgi?id=468162 --- Comment #1 from Bailey Hollis --- (In reply to Bailey Hollis from comment #0) > Created attachment 157859 [details] > Screenshot of behavior > > SUMMARY > Any search with the rpm-ostree backend enabled seems to always include the > current deployments near the top of the list, whether the search has to do > with OS terms or not. > > STEPS TO REPRODUCE > 1. Start from Discover home > 2. Search for anything, even non-existent packages or gibberish > > OBSERVED RESULT > The current deployments appear as results to the search, despite not having > any relation to the search. > > EXPECTED RESULT > Programs/deployments that do not have relevance to the search do not appear > in the search results. > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: > Fedora Linux 37 Kinoite > KDE Plasma Version: 5.27.3 > KDE Frameworks Version: 5.104.0 > Qt Version: 5.15.8 > > ADDITIONAL INFORMATION > None Hmm. The behavior seems to be gone now. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468191] Backup hanging
https://bugs.kde.org/show_bug.cgi?id=468191 Jack changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Jack --- First, 5.0.6 is really old. Please try a more recent version - 5.1.3 is current. For your problem, what happens if you do not tick the box to mount the backup directory? Where are you trying to back up the file? To a local directory or a network share? For your last question, yes, simply making a copy of the .kmy file is all a backup does, so that is sufficient - but you should use some naming convention so each backup does not simply overwrite the previous one. Let us know if any of this helps. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 466853] Marble crashes on exit.
https://bugs.kde.org/show_bug.cgi?id=466853 --- Comment #1 from Rick Smegal --- The above error no longer occurred following installation of the package marble-qt. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468191] New: Backup hanging
https://bugs.kde.org/show_bug.cgi?id=468191 Bug ID: 468191 Summary: Backup hanging Classification: Applications Product: kmymoney Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: guy.cleme...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. File >> Backup 2. Select directory and check mount dir checkbox. 3. Click OK and mounting just hangs so backup never starts. OBSERVED RESULT Mounting hangs and backup never happens EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I manually backed up my *.kmy file but noit sure that's sufficient. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468190] New: plasma-workspace ships with wrong version for 5.27.4
https://bugs.kde.org/show_bug.cgi?id=468190 Bug ID: 468190 Summary: plasma-workspace ships with wrong version for 5.27.4 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: voncl...@gmail.com Target Milestone: --- SUMMARY *** Downloaded plasma-workspace-5.27.4 the Cmake version states 5.27.3 Wont allow kde-cli-tools to install *** STEPS TO REPRODUCE 1. Download plasma-workspace 5.27.4 2. extract and install 3. try to install kde-cli-tools OBSERVED RESULT kde-cli-tools fails to install due to 5.27.3 plasma-workspace being found EXPECTED RESULT get correct version of plasma-workspace SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 468189] New: Browsing opened big Vault (6Gb) is really slow especially with Dolphin and its Open file dialog
https://bugs.kde.org/show_bug.cgi?id=468189 Bug ID: 468189 Summary: Browsing opened big Vault (6Gb) is really slow especially with Dolphin and its Open file dialog Classification: Plasma Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- Created attachment 157885 --> https://bugs.kde.org/attachment.cgi?id=157885=edit Browsing opened big Vault is really slow especially with Dolphin and Open file dialog See attached video for more info. Operating System: Manjaro Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.21-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 oldherl changed: What|Removed |Added CC||oldh...@gmail.com --- Comment #15 from oldherl --- *** Bug 468188 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 468188] Can not open local font file
https://bugs.kde.org/show_bug.cgi?id=468188 oldherl changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from oldherl --- *** This bug has been marked as a duplicate of bug 439470 *** -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 468188] New: Can not open local font file
https://bugs.kde.org/show_bug.cgi?id=468188
Bug ID: 468188
Summary: Can not open local font file
Classification: Applications
Product: kfontview
Version: 5.27.3
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: oldh...@gmail.com
Target Milestone: ---
Created attachment 157884
--> https://bugs.kde.org/attachment.cgi?id=157884=edit
Error message: Could not read font.
SUMMARY
Can not open local font file.
STEPS TO REPRODUCE
1. Run kfontview from a terminal
2. Click "Open" button
3. Select a local font file.
OBSERVED RESULT
Pops up a message dialog says "Could not read font." and prints an error
message "kf.kio.core: Url
QUrl("file:///home/oldherl/.fonts/opensans/OpenSans-Bold.ttf") already
represents a local file, cancelling job." in the terminal that runs kfontview.
EXPECTED RESULT
Should open the font file and view its content.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-arch1-1 (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- Hi Steve, So, this file can be closed ? Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468157] Digikam is crash when use slideshow
https://bugs.kde.org/show_bug.cgi?id=468157 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||8.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468131] 1px wide border at the sides of xwayland maximized windows
https://bugs.kde.org/show_bug.cgi?id=468131 dofficialg...@gmail.com changed: What|Removed |Added Summary|1px wide border at the |1px wide border at the |sides of xwayland |sides of xwayland maximized |fullscreen windows |windows -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468131] 1px wide border at the sides of xwayland fullscreen windows
https://bugs.kde.org/show_bug.cgi?id=468131 --- Comment #2 from dofficialg...@gmail.com --- I mean maximized. there is no issue with fullscreen. the problem is only apparent on non-integer scaling factors (100%, 200%, etc work fine) with maximized windows. for example, I use 150% scaling factor on a native 3840x2160 monitor where the issue is present. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] Wayland desktop wrong size after sleep
https://bugs.kde.org/show_bug.cgi?id=468159 --- Comment #2 from Beyley Thomas --- (In reply to Nate Graham from comment #1) > How bizarre. When this happens, can you paste the output of `kscreen-doctor > -o`? Output: 1 DP-4 enabled connected priority 2 DisplayPort Modes: 0:1280x1024@60! 1:1280x1024@75* 2:1280x800@60 3:1152x864@75 4:1280x720@60 5:1024x768@75 6:1024x768@60 7:800x600@75 8:800x600@60 9:640x480@75 10:640x480@60 11:720x400@70 12:1280x1024@60 13:1024x768@60 14:1280x800@60 15:1280x720@60 Geometry: 5360,0 1024x1280 Scale: 1 Rotation: 2 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 2 HDMI-A-5 enabled connected priority 3 HDMI Modes: 0:1920x1080@60*! 1:1920x1080@60 2:1920x1080@60 3:1920x1080@30 4:1920x1080@30 5:1920x1080@24 6:1920x1080@24 7:1600x1200@60 8:1680x1050@60 9:1280x1024@75 10:1280x1024@60 11:1440x900@75 12:1440x900@60 13:1280x960@60 14:1360x768@60 15:1280x800@60 16:1152x864@75 17:1280x720@60 18:1280x720@60 19:1280x720@60 20:1024x768@75 21:1024x768@70 22:1024x768@60 23:832x624@75 24:800x600@75 25:800x600@72 26:800x600@60 27:720x480@60 28:720x480@60 29:720x480@60 30:720x480@60 31:640x480@75 32:640x480@73 33:640x480@67 34:640x480@60 35:640x480@60 36:720x400@70 37:1280x1024@60 38:1024x768@60 39:1280x800@60 40:1920x1080@60 41:1600x900@60 42:1368x768@60 43:1280x720@60 Geometry: 0,100 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 3 DP-3 enabled connected priority 1 DisplayPort Modes: 0:3440x1440@165*! 1:3440x1440@100 2:3440x1440@60 3:2560x1440@165 4:2560x1440@100 5:2560x1440@60 6:1920x1200@165 7:1920x1080@165 8:1920x1080@100 9:1920x1080@60 10:1920x1080@60 11:1920x1080@60 12:1920x1080@50 13:1600x1200@165 14:1680x1050@60 15:1600x900@60 16:1280x1024@75 17:1280x1024@60 18:1440x900@60 19:1280x800@60 20:1152x864@75 21:1280x720@60 22:1280x720@60 23:1280x720@60 24:1280x720@50 25:1024x768@75 26:1024x768@70 27:1024x768@60 28:832x624@75 29:800x600@75 30:800x600@72 31:800x600@60 32:800x600@56 33:720x576@50 34:720x480@60 35:720x480@60 36:640x480@75 37:640x480@73 38:640x480@67 39:640x480@60 40:640x480@60 41:720x400@70 42:1600x1200@60 43:1280x1024@60 44:1024x768@60 45:1920x1200@60 46:2560x1440@60 47:1920x1080@60 48:1600x900@60 49:1368x768@60 50:1280x720@60 Geometry: 1920,100 3440x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown video of it occurring here https://www.youtube.com/watch?v=h_h6Higv_Mg -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 313210] Ability to open a new tab with a specific profile
https://bugs.kde.org/show_bug.cgi?id=313210 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468187] New: Add option to enable/disable tooltips for each used widget
https://bugs.kde.org/show_bug.cgi?id=468187 Bug ID: 468187 Summary: Add option to enable/disable tooltips for each used widget Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Tooltips are an additional way to access quickly more information without clicking on items, but they can be very intrusive and non-intuitive in some cases : 1) For example, If I want to enable tooltips only on Desktop and disable them everywhere, it cannot be done because tooltips in System Tray items, Kickoff, Pager, Minimize All... are automatically enabled with global tooltips settings which is needed for Desktop tooltips. 2) If I want to enable thumbnails (preview and selection) only for grouped items in Task Manager while disabling tooltips everywhere, it cannot be done. It would be great to have an option in Plasma settings where we can check the activation/deactivation of tooltips in each used widgets (which doesn't have its own tooltips settings), because some tooltips really have no meaning and bring no additional/new information to user like the one for Kickoff, Minimize All, Calendar, Keyboard layout. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 366599] Add kipi-plugins to dolphin
https://bugs.kde.org/show_bug.cgi?id=366599 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC||felixer...@kde.org --- Comment #2 from Felix Ernst --- kipi support was dropped from Gwenview a year ago. The reasons for this are mentioned in the commit https://invent.kde.org/graphics/gwenview/-/commit/0f39bcc72b9078f16e343749f56aa8dff55a14dc: >KIPI offers export functionality for various external services > >However it has been abandoned from its original authors and receives no real >development any more > >A lot, if not all of its providers are defunct and it severly lacks UI polish > >Gwenview already has integration with Purpose which offers a similar >(albeit theoretically reduced) functionality with a much more polished >experience It was also discussed on Phabricator and a mailing list IIRC. For these reasons it is most likely not a good idea to put any more work into kipi support. >pictures can be uploaded to *service* directly. For many *service* there are context menu plugins which can be installed from the settings that allow direct upload. That's probably good enough for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467727] Resizing application windows glitches when using a gif background on Wayland (Nvidia)
https://bugs.kde.org/show_bug.cgi?id=467727 --- Comment #4 from teslastormga...@gmail.com --- (In reply to Nate Graham from comment #3) > imgur turned it into an mp4 video! Any chance yo can find somewhere to host > it that will preserve the file type? My apologies, heres a google drive link of the file: https://drive.google.com/file/d/1_TMcxlkx3c-IdJxhzfgVzlIQZwiz51ds/view?usp=sharing The file should be a gif file and easy to download. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468157] Digikam is crash when use slideshow
https://bugs.kde.org/show_bug.cgi?id=468157 --- Comment #2 from mag...@gmail.com --- (In reply to caulier.gilles from comment #1) > This must be fixed in current Windows installer available here : > > https://files.kde.org/digikam/ > > Please try and report > > Gilles Caulier I´ve just donwload and install the version you recomended me and the issue was solved! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468186] New: Audio level does not go lower than -24db
https://bugs.kde.org/show_bug.cgi?id=468186 Bug ID: 468186 Summary: Audio level does not go lower than -24db Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: tbrown120...@gmail.com Target Milestone: --- Using the audio mixer, trying to use the audio level arrows or nob to go lower than -24db does not change audio level below that point, even though it shows your desired value. Trying to adjust lower than -24db does not yield a lower level of volume, but still displays your desired volume even though it does not go lower. For example, I was trying to lower the volume to -32db, but there was no difference in audio volume for the track. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 468185] KAdressbook crashes when opened
https://bugs.kde.org/show_bug.cgi?id=468185 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 468185] New: KAdressbook crashes when opened
https://bugs.kde.org/show_bug.cgi?id=468185 Bug ID: 468185 Summary: KAdressbook crashes when opened Classification: Applications Product: kaddressbook Version: 5.19.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ma...@trunzerweb.de CC: to...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Opening KAddressbook from KMail menu 2. KAddessbook crashes 3. It also crashes immediately after displaying the window when calling from command line of a shell OBSERVED RESULT Crash EXPECTED RESULT No Crash ;-) Application: kaddressbook (5.19.3 (21.12.3)) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.14.21-150400.24.46-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.4" DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Opening KAddressbook from KMail menu I think I scrolled a little bit through the contacts, but it crashes also just after opning. I assume it has to do with the contacts and otentially with contact groups that are stored. The crash can be reproduced every time. -- Backtrace: Application: KAddressBook (kaddressbook), signal: Aborted [KCrash Handler] #4 0x7fb1f1842c6b in raise () from /lib64/libc.so.6 #5 0x7fb1f1844305 in abort () from /lib64/libc.so.6 #6 0x7fb1f1cb5675 in ?? () from /usr/lib64/libstdc++.so.6 #7 0x7fb1f1cc0d0c in ?? () from /usr/lib64/libstdc++.so.6 #8 0x7fb1f1cc0d77 in std::terminate() () from /usr/lib64/libstdc++.so.6 #9 0x7fb1f1cc0fd8 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #10 0x7fb1ef212946 in Akonadi::Item::throwPayloadException(int, int) const () from /usr/lib64/libKF5AkonadiCore.so.5 #11 0x7fb1f4f33cb3 in Akonadi::Item::payloadImpl (this=0x7fb19c05d6b8) at /usr/include/KF5/AkonadiCore/akonadi/item.h:793 #12 0x7fb1f4f3ca52 in Akonadi::Item::payload (this=this@entry=0x7fb19c05d6b8) at /usr/include/KF5/AkonadiCore/akonadi/item.h:768 #13 0x7fb1f4f382d3 in ContactInfoProxyModel::ContactCacheData::setData (this=0x55c35ce0b6c8, item=...) at /usr/src/debug/kaddressbook-21.12.3-bp154.1.22.x86_64/src/contactinfoproxymodel.cpp:365 #14 0x7fb1f4f3a0a2 in ContactInfoProxyModel::slotFetchJobFinished (this=0x55c35cd35630, job=) at /usr/src/debug/kaddressbook-21.12.3-bp154.1.22.x86_64/src/contactinfoproxymodel.cpp:292 #15 0x7fb1f234c1c7 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc2165790, r=0x55c35cd35630, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x55c35cf97dc0, signal_index=6, argv=0x7ffcc2165790) at kernel/qobject.cpp:3886 #17 0x7fb1f2345782 in QMetaObject::activate (sender=sender@entry=0x55c35cf97dc0, m=m@entry=0x7fb1f42736e0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffcc2165790) at kernel/qobject.cpp:3946 #18 0x7fb1f4020f7c in KJob::result (this=this@entry=0x55c35cf97dc0, _t1=, _t1@entry=0x55c35cf97dc0, _t2=...) at /usr/src/debug/kcoreaddons-5.90.0-150400.3.2.3.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #19 0x7fb1f4022481 in KJob::finishJob (this=0x55c35cf97dc0, emitResult=) at /usr/src/debug/kcoreaddons-5.90.0-150400.3.2.3.x86_64/src/lib/jobs/kjob.cpp:98 #20 0x7fb1f2342d9b in QObject::event (this=0x55c35cf97dc0, e=0x55c35cf99310) at kernel/qobject.cpp:1314 #21 0x7fb1f32c73bc in QApplicationPrivate::notify_helper (this=this@entry=0x55c35c752860, receiver=receiver@entry=0x55c35cf97dc0, e=e@entry=0x55c35cf99310) at kernel/qapplication.cpp:3632 #22 0x7fb1f32ce1a0 in QApplication::notify (this=0x7ffcc2165e20, receiver=0x55c35cf97dc0, e=0x55c35cf99310) at kernel/qapplication.cpp:3156 #23 0x7fb1f230ec23 in QCoreApplication::notifyInternal2 (receiver=0x55c35cf97dc0, event=0x55c35cf99310) at kernel/qcoreapplication.cpp:1064 #24 0x7fb1f230edfe in QCoreApplication::sendEvent (receiver=receiver@entry=0x55c35cf97dc0, event=event@entry=0x55c35cf99310) at kernel/qcoreapplication.cpp:1462 #25 0x7fb1f2311641 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55c35c7304b0) at kernel/qcoreapplication.cpp:1821 #26 0x7fb1f2311bc8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680 #27 0x7fb1f2371983 in postEventSourceDispatch (s=0x55c35c8a1530) at kernel/qeventdispatcher_glib.cpp:277 #28 0x7fb1ea07582b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #29 0x7fb1ea075bd0 in
[okular] [Bug 467603] Okular crashed when using the 'Save Form' button in a PDF form
https://bugs.kde.org/show_bug.cgi?id=467603 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/okular/commit/c62dc60e |hics/okular/commit/91bcb4cc |ad273b1eb285bdb5665fa14769d |21d6701ce266073a4194c94f2d7 |59888 |35a7d --- Comment #5 from Albert Astals Cid --- Git commit 91bcb4cc21d6701ce266073a4194c94f2d735a7d by Albert Astals Cid. Committed on 05/04/2023 at 22:24. Pushed by aacid into branch 'release/23.04'. Fix crash when executing the Save action Detecting aboutToClose is not enough because savingAs doesn't always go through aboutToClose it can go through swapBackingFile (cherry picked from commit c62dc60ead273b1eb285bdb5665fa14769d59888) M +29 -4core/document.cpp https://invent.kde.org/graphics/okular/commit/91bcb4cc21d6701ce266073a4194c94f2d735a7d -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467603] Okular crashed when using the 'Save Form' button in a PDF form
https://bugs.kde.org/show_bug.cgi?id=467603 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/c62dc60e ||ad273b1eb285bdb5665fa14769d ||59888 Status|ASSIGNED|RESOLVED --- Comment #4 from Albert Astals Cid --- Git commit c62dc60ead273b1eb285bdb5665fa14769d59888 by Albert Astals Cid. Committed on 05/04/2023 at 22:06. Pushed by aacid into branch 'master'. Fix crash when executing the Save action Detecting aboutToClose is not enough because savingAs doesn't always go through aboutToClose it can go through swapBackingFile M +29 -4core/document.cpp https://invent.kde.org/graphics/okular/commit/c62dc60ead273b1eb285bdb5665fa14769d59888 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 389887] Default settings of K3b point to notification sounds that don't exist
https://bugs.kde.org/show_bug.cgi?id=389887 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://invent.kde.org/mult |https://invent.kde.org/mult |imedia/k3b/commit/7e1b31d7f |imedia/k3b/commit/361048ce6 |13b19e01d32553e35b0fd94d48a |bb151394efb722f6d69e02f068a |1e59|f7b1 --- Comment #5 from Albert Astals Cid --- Git commit 361048ce6bb151394efb722f6d69e02f068af7b1 by Albert Astals Cid. Committed on 05/04/2023 at 22:22. Pushed by aacid into branch 'release/23.04'. Use proper sound names (cherry picked from commit 7e1b31d7f13b19e01d32553e35b0fd94d48a1e59) M +3-3src/k3b.notifyrc https://invent.kde.org/multimedia/k3b/commit/361048ce6bb151394efb722f6d69e02f068af7b1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467852] Form: Numbers concatenated rather than summed (UK IHT407)
https://bugs.kde.org/show_bug.cgi?id=467852 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/okular/commit/09038f4f |hics/okular/commit/3cd7a780 |b52b97a9b82cc8dc14ea0d962ad |949e716fbf248b3b08049cf4433 |6b0f1 |89c28 --- Comment #4 from Albert Astals Cid --- Git commit 3cd7a780949e716fbf248b3b08049cf443389c28 by Albert Astals Cid. Committed on 05/04/2023 at 22:07. Pushed by aacid into branch 'release/23.04'. JS: Make field.value return a number if possible Quoting the Adobe documentation 'for a field with a value of “020”, value returns the integer 20' (cherry picked from commit 09038f4fb52b97a9b82cc8dc14ea0d962ad6b0f1) M +8-1core/script/kjs_field.cpp https://invent.kde.org/graphics/okular/commit/3cd7a780949e716fbf248b3b08049cf443389c28 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468184] Kwin moving windows and resizing them very poorly to unusable states on multi-monitor setups during unplug events
https://bugs.kde.org/show_bug.cgi?id=468184 --- Comment #1 from Michael Butash --- Some additional feedback, not all windows will get resized, or not all the time. Mostly commonly affected resizing tends affect firefox, libreoffice, konsole, ksettings, pluma, others, but NOT keepassxc, okular, dolphin, telegram/signal electron apps, again others. It's enough varieties it's not prone to any one UI like QT vs. GTK or like. As well the resizing after clearing settings only started after 2 weeks, where originally it was perfect restoring my windows to the right places, but slowly gets worse in moving/resizing over time. Each time now seems to bring stranger and stranger placements where windows are moved or resized to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465639] High CPU usage after starting Plasma
https://bugs.kde.org/show_bug.cgi?id=465639 --- Comment #7 from Tareque Md Hanif --- Fixed by removing picom. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468184] New: Kwin moving windows and resizing them very poorly to unusable states on multi-monitor setups during unplug events
https://bugs.kde.org/show_bug.cgi?id=468184 Bug ID: 468184 Summary: Kwin moving windows and resizing them very poorly to unusable states on multi-monitor setups during unplug events Classification: Plasma Product: kwin Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: mich...@butash.net Target Milestone: --- SUMMARY KDE in general has been bad at dealing with windows placements for some time for me in using 4x displays is my normal, but every time geometry changes with undocking (or a power hit/glitch simulating one), removing 3x displays then moves windows and resizes them to unusable and unfindable widths, and never restores them to proper placement/geometry upon restoration of desired kscreen arrangement. STEPS TO REPRODUCE 1. Configure 4x displays in extended mode right to left in a 15360x2160 display set 2. Arrange various applications such as firefox, konsole, okular, steam, keepassxc, libreoffice, and other applications across all 4 displays. 3. Disconnect the Thunderbolt 4 dock adding the 3x external ports/displays to the unit 4. Watch KDE move windows the laptop display normally the far left-most display, adjusting placement to the right left of the screen, and resizing them horizontally to a much smaller with (5-100px wide), but not vertically. 5. Reconnect thunderbolt dock, observe KDE restore 3x additional displays and arrangement. 6. Observe some of the moved windows are replaced back to their original placement, but typically only a small subset 7. Observe others are left on the far left-most laptop display with poorly resized horizontal pixel width OBSERVED RESULT Using 4x displays, 1x built-in on a laptop, and 3x external connected to a Thunderbolt 4 dock, when dock is disconnected, kwin shuffles applications to the remaining laptop display, but in doing so commonly will mangle horizontal window geometry of most, but not all open applications, and often overlap them very non-optimal ways. Once the dock is reconnected/restored, kscreen restores the display arrangement, but kwin is not restoring all the windows to their proper placement or geometry. Even stranger is it's almost random where it moves things each time, when it happens moving things small and small widths when resizing, and moving some displays half off different parts of the screens. Seeing as this can happen at times several times a day, shuffling my applications about each time, resizing them so small horizontally even finding them on a tiny 15" laptop displays is extremely difficult where the 3x other displays are 50" TV's. Even stranger is it gets incrementally worse each time it happens. EXPECTED RESULT At bare minimum, seeing these are all the same 3840x2160 displays, it should have no reason to resize the horizontal widths between across different resolutions, and once kscreen re-applies its given screen profile for the given displays to restore geometry, those displays should be replaced across the original set of displays. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, kernel 6.2.5-arch1-1 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION This has been happening for some time across prior and new laptops for years now commonly, where recently clearing kscreen, plasmascreenrc, desktop-appletsrc files from home .config/.local files helped this this initially, but each time is incrementally regressing worse in worse in moving/resizing different apps in different places/sizes. It seems if it needs to resize a window, it should never consider resizing a something from 2000px wide to only 5px wide. As well, it would be nice if when it does move all my windows to a single display to at least tile them in some rough fashion vs. a dogpile into the left and bottom-most corner on the display. I have attempted to add using the kwin script "restoreToScreen" to help this, but with or without doesn't seem to matter. Feedback on this script's github is that kwin has taken this feature on, but seems to do so poorly with or without the script. https://github.com/Hegemonia123/restoreToScreen/issues I am unsure where to look for troubleshooting anything related windows placement state tracking, but would happy to provide requested information. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467852] Form: Numbers concatenated rather than summed (UK IHT407)
https://bugs.kde.org/show_bug.cgi?id=467852 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/09038f4f ||b52b97a9b82cc8dc14ea0d962ad ||6b0f1 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Albert Astals Cid --- Git commit 09038f4fb52b97a9b82cc8dc14ea0d962ad6b0f1 by Albert Astals Cid. Committed on 05/04/2023 at 21:19. Pushed by aacid into branch 'master'. JS: Make field.value return a number if possible Quoting the Adobe documentation 'for a field with a value of “020”, value returns the integer 20' M +8-1core/script/kjs_field.cpp https://invent.kde.org/graphics/okular/commit/09038f4fb52b97a9b82cc8dc14ea0d962ad6b0f1 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 449540] Open Tab in New Profile with Yakuake
https://bugs.kde.org/show_bug.cgi?id=449540 Ken Rushia changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@kenrushia.com Status|REPORTED|RESOLVED --- Comment #2 from Ken Rushia --- *** This bug has been marked as a duplicate of bug 313210 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 313210] Ability to open a new tab with a specific profile
https://bugs.kde.org/show_bug.cgi?id=313210 Ken Rushia changed: What|Removed |Added CC||tste...@protonmail.com --- Comment #3 from Ken Rushia --- *** Bug 449540 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 464977] Add option to start new session with specific profile in tab bar, plus keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=464977 Ken Rushia changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@kenrushia.com Resolution|--- |DUPLICATE --- Comment #1 from Ken Rushia --- *** This bug has been marked as a duplicate of bug 313210 *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 313210] Ability to open a new tab with a specific profile
https://bugs.kde.org/show_bug.cgi?id=313210 Ken Rushia changed: What|Removed |Added CC||firlaevhans.fiete@protonmai ||l.com --- Comment #2 from Ken Rushia --- *** Bug 464977 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 389887] Default settings of K3b point to notification sounds that don't exist
https://bugs.kde.org/show_bug.cgi?id=389887 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/mult ||imedia/k3b/commit/7e1b31d7f ||13b19e01d32553e35b0fd94d48a ||1e59 Status|ASSIGNED|RESOLVED --- Comment #4 from Albert Astals Cid --- Git commit 7e1b31d7f13b19e01d32553e35b0fd94d48a1e59 by Albert Astals Cid. Committed on 05/04/2023 at 21:20. Pushed by aacid into branch 'master'. Use proper sound names M +3-3src/k3b.notifyrc https://invent.kde.org/multimedia/k3b/commit/7e1b31d7f13b19e01d32553e35b0fd94d48a1e59 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465869] Unable to add Google account
https://bugs.kde.org/show_bug.cgi?id=465869 --- Comment #5 from Nate Graham --- Unfortunately the presence or absence of that package doesn't affect your ability to connect to the Google account in the Accounts KCM in the first place. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 93087] KTextEditor plugin: highlight web links and urls + make them clickable
https://bugs.kde.org/show_bug.cgi?id=93087
Nate Graham changed:
What|Removed |Added
Version Fixed In||23.08
--- Comment #22 from Nate Graham ---
Note that this feature has been implemented in the form of an off-by-default
plugin ("Open Link"). To get this functionality, you need to enable that plugin
first.
If you would like it to be enabled by default, please make your opinion known!
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 462347] Kate asks me to save an empty Untiled file before closing
https://bugs.kde.org/show_bug.cgi?id=462347 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kate/-/merge_requests/1185 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438308] Subpar UX when opening the terminal panel but Konsole is not installed
https://bugs.kde.org/show_bug.cgi?id=438308 Nate Graham changed: What|Removed |Added Version Fixed In||23.08 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465869] Unable to add Google account
https://bugs.kde.org/show_bug.cgi?id=465869 abusleh...@gmail.com changed: What|Removed |Added CC||abusleh...@gmail.com --- Comment #4 from abusleh...@gmail.com --- Did installed the necessary kio library ? In Debian it is called"kio-gdrive". Without you will not be able to make a connection to your google-drive. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356436] Rightclick on folder/file: "copy/move" to other split view tab
https://bugs.kde.org/show_bug.cgi?id=356436 Nate Graham changed: What|Removed |Added Version Fixed In||23.08 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 467638] discover doesn't recognize a fixed broken package problem
https://bugs.kde.org/show_bug.cgi?id=467638 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457234] crash when closing signed file
https://bugs.kde.org/show_bug.cgi?id=457234 Albert Astals Cid changed: What|Removed |Added CC||aleix...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457234] crash when closing signed file
https://bugs.kde.org/show_bug.cgi?id=457234 --- Comment #3 from Albert Astals Cid --- This is mostly a poppler bug, it needs not to call shutdownNss from an exit handler -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457234] crash when closing signed file
https://bugs.kde.org/show_bug.cgi?id=457234 Albert Astals Cid changed: What|Removed |Added CC||mav...@gmail.com --- Comment #2 from Albert Astals Cid --- *** Bug 467642 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467642] Okular crashes on quit
https://bugs.kde.org/show_bug.cgi?id=467642 Albert Astals Cid changed: What|Removed |Added Resolution|--- |DUPLICATE CC||aa...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 457234 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466307] Okular crashes after, and sometimes when, opening signed PDF files
https://bugs.kde.org/show_bug.cgi?id=466307 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Albert Astals Cid --- Please provide the requested information -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467642] Okular crashes on quit
https://bugs.kde.org/show_bug.cgi?id=467642 Albert Astals Cid changed: What|Removed |Added CC||aleix...@kde.org --- Comment #1 from Albert Astals Cid --- *** Bug 468152 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468152] Crash on exit after signing with a smart card
https://bugs.kde.org/show_bug.cgi?id=468152 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED CC||aa...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 467642 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468183] New: Plasmashell crashes on external screen re-connect
https://bugs.kde.org/show_bug.cgi?id=468183
Bug ID: 468183
Summary: Plasmashell crashes on external screen re-connect
Classification: Plasma
Product: plasmashell
Version: 5.27.3
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: cemkaya.b...@gmail.com
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
Application: plasmashell (5.27.3)
Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.9-arch1-1-g15 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.3 [KCrashBackend]
-- Information about the crash:
When I remove the external screen, and re-connect it, plasma shell crashes.
The crash can be reproduced every time.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fe22285ddbb in QArrayData::data() (this=,
this=) at /usr/include/qt/QtCore/qarraydata.h:62
#7 QTypedArrayData::data() (this=) at
/usr/include/qt/QtCore/qarraydata.h:209
#8 QTypedArrayData::begin(QQuickPointerEvent**)
(this=) at /usr/include/qt/QtCore/qarraydata.h:212
#9 QVector::realloc(int,
QFlags) (this=0x557047c92b20, aalloc=, options=...) at /usr/include/qt/QtCore/qvector.h:710
#10 0x7fe22284a99a in QVector::detach()
(this=0x557047c92b20) at /usr/include/qt/QtCore/qflags.h:121
#11 QVector::detach() (this=0x557047c92b20) at
/usr/include/qt/QtCore/qvector.h:397
#12 QVector::begin() (this=0x557047c92b20) at
/usr/include/qt/QtCore/qvector.h:210
#13 QQuickWindowPrivate::queryPointerEventInstance(QQuickPointerDevice*,
QEvent::Type) const (this=this@entry=0x557047c92980, device=0x7fe222b3bca0
<(anonymous namespace)::Q_QGS_g_genericMouseDevice::innerFunction()::holder>,
eventType=eventType@entry=QEvent::None) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickwindow.cpp:2515
#14 0x7fe22284ad14 in QQuickWindow::mouseGrabberItem() const
(this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickwindow.cpp:1745
#15 0x7fe22284e92f in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool,
bool) (this=0x557047c92980, grabber=0x55704618c090, mouse=,
touch=true) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickwindow.cpp:1007
#16 0x7fe222833ce7 in QQuickItemPrivate::derefWindow()
(this=this@entry=0x557049b91730) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:3035
#17 0x7fe2228352ab in QQuickItem::setParentItem(QQuickItem*)
(this=0x55704618c090, parentItem=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:2717
#18 0x7fe222933230 in QQuickRepeater::clear() (this=0x55704469a430) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickrepeater.cpp:377
#19 0x7fe222939f69 in QQuickRepeater::setModel(QVariant const&)
(m=, this=0x55704469a430) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickrepeater.cpp:203
#20 QQuickRepeater::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) (_o=0x55704469a430, _c=, _id=,
_a=) at .moc/moc_qquickrepeater_p.cpp:228
#21 0x7fe3c85e in QQmlPropertyData::writeProperty(QObject*, void*,
QFlags) const (this=,
target=, value=, flags=...) at
../../include/QtQml/5.15.8/QtQml/private/../../../../../../qtdeclarative/src/qml/qml/qqmlpropertydata_p.h:391
#22 0x7fe999d0 in QQmlBinding::slowWrite(QQmlPropertyData const&,
QQmlPropertyData const&, QV4::Value const&, bool,
QFlags) (this=this@entry=0x55704469a8b0, core=...,
valueTypeData=..., result=..., isUndefined=isUndefined@entry=false, flags=...,
flags@entry=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlbinding.cpp:474
#23 0x7fe90ba1 in GenericBinding<0>::write(QV4::Value const&, bool,
QFlags) (this=0x55704469a8b0, result=...,
isUndefined=, flags=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlbinding.cpp:335
#24 0x7fe978fe in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) (this=0x55704469a8b0,
watcher=..., flags=..., scope=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlbinding.cpp:258
#25 0x7fe98f73 in
QQmlBinding::update(QFlags) (this=0x55704469a8b0,
flags=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlbinding.cpp:194
#26 0x7fe7647f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) (endpoint=, a=0x0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlnotifier.cpp:104
#27 0x7fe220cbe740 in doActivate(QObject*, int, void**)
(sender=0x55704465c100, signal_index=61, argv=0x0) at kernel/qobject.cpp:3815
#28 0x7fe31fcb in QQmlVMEMetaObject::metaCall(QObject*,
[digikam] [Bug 467912] Image Editor ignores former window size at startup
https://bugs.kde.org/show_bug.cgi?id=467912 --- Comment #5 from Maik Qualmann --- Git commit 303f96df39fc1f9a3ce0755d08d7a641bb2f2739 by Maik Qualmann. Committed on 05/04/2023 at 21:07. Pushed by mqualmann into branch 'master'. next try to fix window size #3 M +1-1core/app/main/digikamapp_setup.cpp M +0-18 core/libs/widgets/mainview/dxmlguiwindow.cpp M +0-5core/libs/widgets/mainview/dxmlguiwindow.h M +3-1core/utilities/imageeditor/main/imagewindow.cpp M +1-1core/utilities/imageeditor/main/imagewindow.h M +3-1core/utilities/lighttable/lighttablewindow.cpp M +1-1core/utilities/lighttable/lighttablewindow.h https://invent.kde.org/graphics/digikam/commit/303f96df39fc1f9a3ce0755d08d7a641bb2f2739 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467855] On X11, Rectangular Region captures the wrong area with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=467855 --- Comment #5 from András Manţia --- Created attachment 157883 --> https://bugs.kde.org/attachment.cgi?id=157883=edit Screen layout -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442379] When using Natural Scrolling, scrolling direction to change volume is inverted
https://bugs.kde.org/show_bug.cgi?id=442379 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442379] When using Natural Scrolling, scrolling direction to change volume is inverted
https://bugs.kde.org/show_bug.cgi?id=442379 Nate Graham changed: What|Removed |Added Version Fixed In||6.0 Latest Commit||https://invent.kde.org/plas ||ma/plasma-pa/-/commit/4578f ||4fef52bac4f87aad2fc148c2d9a ||6e191be2 --- Comment #9 from Nate Graham --- Fixed by Vlad Zahorodnii with https://invent.kde.org/plasma/plasma-pa/-/commit/4578f4fef52bac4f87aad2fc148c2d9a6e191be2 in Plasma 6.0! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 467884] SwipeListItem swiping is broken
https://bugs.kde.org/show_bug.cgi?id=467884 Nate Graham changed: What|Removed |Added Version Fixed In||5.105 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467325] bad french date format in tooltip.
https://bugs.kde.org/show_bug.cgi?id=467325 Nate Graham changed: What|Removed |Added Summary|bad french date format |bad french date format in ||tooltip. --- Comment #4 from Nate Graham --- For some reason, the line of code that contains Qt.formatDate(tzDate, Locale.LongFormat) returns a string that isn't actually the long date, but a shortened version of it. I haven't figured out why that is yet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465484] System Settings Crashes While Importing A OpenVPN Config
https://bugs.kde.org/show_bug.cgi?id=465484 Nicolas Fella changed: What|Removed |Added CC||c...@gogospace.cz --- Comment #10 from Nicolas Fella --- *** Bug 468182 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468182] Crash trying import ovpn config file
https://bugs.kde.org/show_bug.cgi?id=468182 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 465484 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465484] System Settings Crashes While Importing A OpenVPN Config
https://bugs.kde.org/show_bug.cgi?id=465484 Nicolas Fella changed: What|Removed |Added CC||dirtydo...@gmail.com --- Comment #9 from Nicolas Fella --- *** Bug 467521 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467521] Crash in OpenVpnUiPlugin::importConnectionSettings(
https://bugs.kde.org/show_bug.cgi?id=467521 Nicolas Fella changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||nicolas.fe...@gmx.de --- Comment #2 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 465484 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467726] Secondary Monitor Connected to eGPU does not Wake from Sleep
https://bugs.kde.org/show_bug.cgi?id=467726 --- Comment #8 from Robin --- I am unable to reproduce it on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413896] crash application when trying to use uim anthy
https://bugs.kde.org/show_bug.cgi?id=413896 Waqar Ahmed changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||waqar@gmail.com Status|CONFIRMED |NEEDSINFO --- Comment #8 from Waqar Ahmed --- Is this still reproducible? Wayland support has matured a lot and 2 years have passed so maybe this is no longer a crash. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #75 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1246 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468182] New: Crash trying import ovpn config file
https://bugs.kde.org/show_bug.cgi?id=468182 Bug ID: 468182 Summary: Crash trying import ovpn config file Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: c...@gogospace.cz Target Milestone: --- Application: systemsettings (5.27.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-7-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: System settings > connections > + > Import VPN connection... > + Create > my.ovpn > Open > System Settings Closed Unexpectedly The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fba2b7726ae in OpenVpnUiPlugin::importConnectionSettings(QString const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/network/vpn/plasmanetworkmanagement_openvpnui.so #5 0x7fba4a526972 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings_qwidgets/kcm_networkmanagement.so #6 0x7fba8f0e8f7c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fba8cc6eb78 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fba8ccc6c93 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fba8cba3521 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fba8cba53e0 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fba8cbc1cb6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fba8cbc53df in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7fba8cb57c2e in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fba8cce144d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7fba8cc92baf in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7fba8cc942f8 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7fba8ccc677f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7fba8f0e8a8d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fba8cc6eb78 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7fba8ccc6c93 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7fba8cba3521 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7fba8cba53e0 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7fba8cbc1cb6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7fba8cbc53df in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7fba8cb57c2e in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7fba8cce144d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #27 0x7fba8cc92baf in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7fba8cc942f8 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7fba8ccc677f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7fba8f0e8a8d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7fba8d2be9c2 in QQuickMouseArea::doubleClicked(QQuickMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #32 0x7fba8d2c1573 in QQuickMouseArea::mouseDoubleClickEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #33 0x7fba8d2550e8 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #34 0x7fba8fd62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x7fba8f0b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7fba8d2729da in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #37 0x7fba8d2740dd in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #38 0x7fba8f5493f5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #39
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 --- Comment #74 from David Faure --- Git commit a304840cff15e3324010da7877b53c2f6fa7e594 by David Faure, on behalf of Méven Car. Committed on 05/04/2023 at 11:16. Pushed by meven into branch 'master'. KCoreDirLister: AutoUpdate wasn't incremented when a new lister opened an already listed dir * Adds a test demonstrating the bug * adds a cache eviction test for good measure * clean a little tests M +92 -32 autotests/kdirlistertest.cpp M +2-0autotests/kdirlistertest.h M +7-2src/core/kcoredirlister.cpp https://invent.kde.org/frameworks/kio/commit/a304840cff15e3324010da7877b53c2f6fa7e594 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467325] bad french date format
https://bugs.kde.org/show_bug.cgi?id=467325 Nate Graham changed: What|Removed |Added Keywords|regression | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468169] Option to delete or to edit flatpak permissions added by the user
https://bugs.kde.org/show_bug.cgi?id=468169 --- Comment #1 from ratijas --- Unchecking them would mark them for deletion. It will work the same way for Filesystems, D-Bus services and Environment variables, once https://invent.kde.org/plasma/flatpak-kcm/-/merge_requests/91 is merged. Additionally I want to replace checkboxes with icon-only "delete" buttons, and markup text with strike-through attribute and maybe faded text color. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467325] bad french date format
https://bugs.kde.org/show_bug.cgi?id=467325 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466294] [Request] Option to show time with seconds in expanded calendar view
https://bugs.kde.org/show_bug.cgi?id=466294 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Version Fixed In||6.0 --- Comment #4 from Nate Graham --- My mistake, the feature got added to Plasma 6. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464798] Second monitor is always black on startup. Have to lock the screen to SDDM to have a chance at fixing it
https://bugs.kde.org/show_bug.cgi?id=464798 --- Comment #10 from Carlo --- update: enabling Wayland on SDDM in the alpha version seems to be another valid fix. In /etc/sddm.conf.d/kde_settings.conf I set: [General] DisplayServer=wayland GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell [Wayland] CompositorCommand=kwin_wayland --no-lockscreen --inputmethod qtvirtualkeyboard -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468181] some french accentuated characters are not possible
https://bugs.kde.org/show_bug.cgi?id=468181 Mickaël B. changed: What|Removed |Added Summary|accentuated characters not |some french accentuated |possible|characters are not possible -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468181] New: accentuated characters not possible
https://bugs.kde.org/show_bug.cgi?id=468181 Bug ID: 468181 Summary: accentuated characters not possible Classification: Plasma Product: kscreenlocker Version: 5.27.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mb-kde+zalfd...@kittycat.fr Target Milestone: --- Hello, kscreenlocker seems to have a problem with accentuated characters. I have a generic 104-key PC keyboard, with the default french layout. Characters generated in combination with the "^ ¨" key, like ê â ï ë, etc. are not detected. As a comparison, I have no such problem on login screen. I tested with alternate french layouts to check, without success. Thanks for your help (and your great work) :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468180] New: Plasmashell crashed after closing a notification
https://bugs.kde.org/show_bug.cgi?id=468180 Bug ID: 468180 Summary: Plasmashell crashed after closing a notification Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: groszdaniel...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.8-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: Plasmashell occasionally crashes when closing an e-mail notification from KMail. It has happened at least three times, once in a few days. The backtrace is very similar to Bug 461072. But it still happens on plasmashell 5.27.3 (and it only started happening in the last few weeks, or at least it became more frequent), while that bug was fixed/worked around in January. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f5fd8e9364d in QScopedPointer >::operator->() const (this=0x8) at /usr/include/qt5/QtCore/qscopedpointer.h:118 #5 qGetPtrHelper > >(QScopedPointer >&) (ptr=...) at /usr/include/qt5/QtCore/qglobal.h:1149 #6 QQmlEngine::d_func() (this=0x0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/qml/qqmlengine.h:172 #7 QQmlEnginePrivate::get(QQmlEngine*) (e=0x0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/qml/qqmlengine_p.h:424 #8 QtQml::qmlExecuteDeferred(QObject*) (object=object@entry=0x563a12a8ee70) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qml/qml/qqmlengine.cpp:1592 #9 0x7f5fd9378a99 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) (this=this@entry=0x563a12a8ee70, actions=..., after=..., manager=manager@entry=0x7f5fc403b860, defaultTarget=defaultTarget@entry=0x563a12b36340) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/util/qquicktransition.cpp:259 #10 0x7f5fd936e2d7 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) (this=0x7f5fc403b860, list=, transition=0x563a12a8ee70, defaultTarget=0x563a12b36340) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/quick/util/qquicktransitionmanager.cpp:207 #11 0x7f5fd7918d2b in QObject::event(QEvent*) (this=0x563a12b36340, e=0x7ffec425bd10) at kernel/qobject.cpp:1369 #12 0x7f5fd85a52ce in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x563a12b36340, e=0x7ffec425bd10) at kernel/qapplication.cpp:3640 #13 0x7f5fd78ecb28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x563a12b36340, event=0x7ffec425bd10) at kernel/qcoreapplication.cpp:1064 #14 0x7f5fd79454a9 in QTimerInfoList::activateTimers() (this=0x563a0c853860) at kernel/qtimerinfo_unix.cpp:643 #15 0x7f5fd7945d8c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #16 idleTimerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at kernel/qeventdispatcher_glib.cpp:230 #17 0x7f5fd6359f96 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #18 0x7f5fd635a358 in () at /lib64/libglib-2.0.so.0 #19 0x7f5fd635a3ec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #20 0x7f5fd79460b6 in QEventDispatcherGlib::processEvents(QFlags) (this=0x563a0c853cb0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f5fd78eb5cb in QEventLoop::exec(QFlags) (this=this@entry=0x7ffec425bf50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f5fd78f3a50 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x7f5fd7d6fe4c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1870 #24 0x7f5fd85a5245 in QApplication::exec() () at kernel/qapplication.cpp:2832 #25 0x563a0c56447d in main(int, char**) (argc=, argv=) at /usr/src/debug/plasma-workspace-5.27.3/shell/main.cpp:235 [Inferior 1 (process 13998) detached] The reporter indicates this bug may be a duplicate of or related to bug 461072, bug 462715, bug 463956, bug 465706. Reported using DrKonqi -- 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 #15 from mrantonsae...@gmail.com --- Created attachment 157882 --> https://bugs.kde.org/attachment.cgi?id=157882=edit when scrolling over plasma widget. -- 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 #14 from mrantonsae...@gmail.com --- No, I think it does not matter, but u just tried scrolling over it, and it fixes the problem, everything shows like it should. -- 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 #13 from Ismael Asensio --- I cannot fully reproduce, but found a small quirk that might or might not be related. Does this only happen with the volume buttons, or also if you change the volume by scrolling over the plasma applet (mouse wheel-scrolling or touchpad equivalent)? Also, does it make a difference if you change the profile in the Audio settings page (full dialog) vs changing it in the applet? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437210] Removed and then restored Plasma panel is positioned in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=437210 Eric changed: What|Removed |Added CC||m...@ericvanblokland.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467726] Secondary Monitor Connected to eGPU does not Wake from Sleep
https://bugs.kde.org/show_bug.cgi?id=467726 --- Comment #7 from Nate Graham --- Sure but can you test it for the purposes of this bug report? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467605] Plastik decorations have scaling artifacts on window title text
https://bugs.kde.org/show_bug.cgi?id=467605 Marco Rebhan changed: What|Removed |Added Component|decorations |aurorae -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467726] Secondary Monitor Connected to eGPU does not Wake from Sleep
https://bugs.kde.org/show_bug.cgi?id=467726 --- Comment #6 from Robin --- Testing on Wayland is difficult, as the eGPU has to copy what it draws over to the CPU resulting in subpar performance (10-13 FPS). I'll be using X11 long term until Wayland works well with secondary or external GPUs in the future. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458487] Share Plugin: URLs with titles should be shared as plain URLs
https://bugs.kde.org/show_bug.cgi?id=458487 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/kdeconnect-android/-/merge_requests/339 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466566] Kickoff button too large with super thick panel
https://bugs.kde.org/show_bug.cgi?id=466566 --- Comment #11 from Eric --- (In reply to Ismael Asensio from comment #10) > > 2. Add per-widget settings for 1st-party widgets to control the maximum icon > > size as needed. For some reason people only ever seem to complain about this > > issue as it applies to their launcher menu widgets, so maybe it will be > > enough to do this for Kickoff, Kicker, and Application Dashboard. Cons: lots > > of code duplication if we end up implementing it for multiple widgets; worse > > UX if you want to make this change for all the affected widgets on your > > panel; universality would still be elusive since 3rd-party widgets have to > > implement the same code. > > We might explore this solution, a "per-applet size setting", but implemented > as a sizing handle on the panel edit mode (not as a specific configuration > the applet has to provide). If only, some properties or hints would be > required for the applets to "opt-in". That would be similar to what we do > now with applet pop-ups resizing. > > It would act as a Layout.Preferred/Maximum size, and potentially also solve > the sizing problem with two full-width competing widgets on the same panel > (ex. Menubar + Taskmanager). > > Ideally it should be useful but not overwhelming, that is, defaults should > still suffice for the majority of the cases. This solution would be the Rolls Royce in my opinion. Actually, one of the first things I checked for when I was confronted with my new Kickoff button was whether I was allowed to resize it in edit mode by dragging its edge. So there is at least some intuitivity with this. Implementing this could also benefit other widgets. For me it would be a "nice to have" if I could increase the size of "Pager" as an example. (don't consider this a feature request, I'm just brainstorming) While consistency is important, it might be worth considering this as a preferred size instead of a maximum. If we look at the "System Tray" for example, it would be a "nice to have" if it could be set as a minimum size. Here's why: it has happened several times to me that my Task Manger is "pixels away" from scaling down. Then I'm in a browser tab that starts playing media and the System Tray expands its size because of that extra icon. This causes the Task Manager to scale down and up again. Since the number of System Tray items is rather constant for me, just reserving space for those one or two extra icons would be nice. (again, not a feature request, just brainstorming) In the end I think everyone would benefit, if I were to put my launcher on a horizontal panel again I would appreciate that I could make the "clickable surface" wider than my panel height. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465516] kwin-wayland crash Failed to recreate shadow for PlasmaQuick
https://bugs.kde.org/show_bug.cgi?id=465516 Pawel changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465516] kwin-wayland crash Failed to recreate shadow for PlasmaQuick
https://bugs.kde.org/show_bug.cgi?id=465516 --- Comment #6 from Pawel --- Created attachment 157881 --> https://bugs.kde.org/attachment.cgi?id=157881=edit gdb wayland kwin Reopening as this crash happened earlier today. This time thee was nothing about failing to recreate shadow for PlasmaQuick. I have a backtrace but it appears useless and I am noticing a strange pattern. Whenever this crash occurs, > $ coredumpctl list --reverse > > > shows the backtrace of kwin_wayland is "inaccesible". Executing the above command with su privileges, I do get the attached. Any ideas? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467074] When returning from screen energy saving, Plasma forgets that an external screen is connected and doesn't assign it a containment
https://bugs.kde.org/show_bug.cgi?id=467074 Celeste Liu changed: What|Removed |Added CC||coelacanthus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467726] Secondary Monitor Connected to eGPU does not Wake from Sleep
https://bugs.kde.org/show_bug.cgi?id=467726 Celeste Liu changed: What|Removed |Added CC||coelacanthus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 468178] plasma-mobile crashes after unlocking with "kwin_core: Detected a touch move that never has been down, discarding"
https://bugs.kde.org/show_bug.cgi?id=468178 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467620] Cannot open encrypted USB drive from systray
https://bugs.kde.org/show_bug.cgi?id=467620 --- Comment #5 from Nate Graham --- Software stacks can works differently from one another. If you can pinpoint exactly what change needs to be made, we may be able to investigate whether it's something that could be improved on the KDE side. Still, it's your distro's job to perform this kind of integration work, regardless of what special requirements KDE apps may have here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468179] Assistants snap to the wrong center.
https://bugs.kde.org/show_bug.cgi?id=468179 --- Comment #3 from comfysoft...@proton.me --- Created attachment 157880 --> https://bugs.kde.org/attachment.cgi?id=157880=edit After -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468179] Assistants snap to the wrong center.
https://bugs.kde.org/show_bug.cgi?id=468179 --- Comment #2 from comfysoft...@proton.me --- Created attachment 157879 --> https://bugs.kde.org/attachment.cgi?id=157879=edit Before -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468179] Assistants snap to the wrong center.
https://bugs.kde.org/show_bug.cgi?id=468179 --- Comment #1 from comfysoft...@proton.me --- Created attachment 157878 --> https://bugs.kde.org/attachment.cgi?id=157878=edit System info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468179] New: Assistants snap to the wrong center.
https://bugs.kde.org/show_bug.cgi?id=468179 Bug ID: 468179 Summary: Assistants snap to the wrong center. Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: comfysoft...@proton.me Target Milestone: --- Created attachment 157877 --> https://bugs.kde.org/attachment.cgi?id=157877=edit Usage Log SUMMARY Created assistants snap to the wrong center lines for the document. STEPS TO REPRODUCE Open a new file. A smaller file might make the effect easier to measure the pixels, but the effect occurs for any file size. Create a new assistant. It is most easily obvious with rulers and ellipses, but it happens for any assistant. Drag it around! You'll notice the assistants snap to the "center" lines of the document. Except, they are not. These center lines are off from the real document center, and as you pan and zoom around the canvas, the snapping positions will change. Turning off View > Snap to > Image center disables the snapping of the assistants. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 468084] Calculator memory leak
https://bugs.kde.org/show_bug.cgi?id=468084 --- Comment #3 from Yeshi --- (In reply to Yeshi from comment #2) > (In reply to Fushan Wen from comment #1) > > Please report the bug to libqalculate > > I believe a timeout after a few seconds would go a long way here. > Perhaps even setting a memory limit could work. > > Both of these solutions should be better than having plasmashell restart. Forgot to mention, I have reported this bug to libqalculate. -- You are receiving this mail because: You are watching all bug changes.
