[plasma-nm] [Bug 470667] Allow storing wifi password for all users by default
https://bugs.kde.org/show_bug.cgi?id=470667 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 166521] Allow default directory for saving attachments to be customised based on both sender and file-type
https://bugs.kde.org/show_bug.cgi?id=166521 Marc Mezzarobba changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 CC||marc+b...@mezzarobba.net --- Comment #3 from Marc Mezzarobba --- I think it is still valid. Alternatively (or in addition), it would be great if kmail would remember the last directory used for saving an attachment from a given sender and use it as a default location in the Save As... dialog. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 325571] option to delete all attachments
https://bugs.kde.org/show_bug.cgi?id=325571 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 465825] mail viewer crashes on this message
https://bugs.kde.org/show_bug.cgi?id=465825 --- Comment #3 from Marc Mezzarobba --- Thanks a lot for taking a look! You mean that the bug is *fixed* in zxing-cpp 2.0, right? (or should I report it there?) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 465825] mail viewer crashes on this message
https://bugs.kde.org/show_bug.cgi?id=465825 --- Comment #1 from Marc Mezzarobba --- Created attachment 156294 --> https://bugs.kde.org/attachment.cgi?id=156294&action=edit bracktrace -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 465825] New: mail viewer crashes on this message
https://bugs.kde.org/show_bug.cgi?id=465825 Bug ID: 465825 Summary: mail viewer crashes on this message Classification: Applications Product: kmail2 Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: marc+b...@mezzarobba.net Target Milestone: --- Created attachment 156293 --> https://bugs.kde.org/attachment.cgi?id=156293&action=edit testcase SUMMARY kmail crashes when opening the attached message. I am not sure where to report the bug as the backtrace suggests that KItinerary is involved. STEPS TO REPRODUCE 1. kmail --view spam_crashing_kmail (alternatively, put the message in some kmail folder and click on it from the message list) SOFTWARE/OS VERSIONS debian sid kmail2 5.22.2 (22.12.2) itinerary 22.12.1 zxing 1.4.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Marc Mezzarobba changed: What|Removed |Added CC|marc+b...@mezzarobba.net| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #146 from Marc Mezzarobba --- I too have had a similar issue for a few months. In addition to the suspend/resume scenario described in other comments, very similar symptoms sometimes occur when launching applications such as Firefox and Okular. This makes me suspect that it may be related to some kind of initialization or state change of hardware acceleration. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447203] startplasma-wayland overwrites $XKB_DEFAULT_*
https://bugs.kde.org/show_bug.cgi?id=447203 --- Comment #2 from Marc Mezzarobba --- (In reply to Nate Graham from comment #1) > Would you like to submit a merge request to fix it? I suppose I could try, but (a) I am not sure what the right thing to do would be (just skip importing the values from systemd-localed when any of the XKB_* envvars is set?), and (b) I have zero experience with KDE development. Where should I start? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447206] New: kwin_wayland ignores $XDG_CONFIG_HOME/xkb
https://bugs.kde.org/show_bug.cgi?id=447206 Bug ID: 447206 Summary: kwin_wayland ignores $XDG_CONFIG_HOME/xkb Product: kwin Version: 5.23.4 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: marc+b...@mezzarobba.net Target Milestone: --- SUMMARY kwin_wayland supports getting its xkb configuration from the environment variables XKB_DEFAULT_LAYOUT, and libxkbcommon's default include paths include $XDG_CONFIG_HOME/xkb. This should make it possible to load a custom keymap from ~/.config/xkb when launching kwin as a wayland compositor, even though kcm_keyboard only supports keymaps from the system-wide xkb library. However, on my system, kwin only looks in /usr/share/X11/xkb/ and /etc/xkb when loading the keymap, not in the other standard locations $HOME/.xkb and $XDG_CONFIG_HOME/xkb. STEPS TO REPRODUCE 1. put a custom keymap "mylayout" in $HOME/.config/xkb 2. create .config/plasma-workspace/env/setkeymap.sh containing export QT_LOGGING_RULES="kwin_*.debug=true" export XKB_LOG_VERBOSITY=10 export KWIN_XKB_DEFAULT_KEYMAP=yes export XKB_DEFAULT_LAYOUT=mylayout 3. launch plasma session OBSERVED RESULT The custom keymap is not used. The logs in .local/share/sddm/wayland-session.log confirm that libxkbcommon only searched /usr/share/X11/xkb/ and /etc/xkb. ADDITIONAL INFORMATION Possibly related to #388249? On a single-user machine, a possible workaround is to put one's custom keymaps in /etc/xkb. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447203] New: startplasma-wayland overwrites $XKB_DEFAULT_*
https://bugs.kde.org/show_bug.cgi?id=447203 Bug ID: 447203 Summary: startplasma-wayland overwrites $XKB_DEFAULT_* Product: plasmashell Version: 5.23.4 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: marc+b...@mezzarobba.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY startplasma-wayland sets the environment variables XKB_DEFAULT_MODEL, XKB_DEFAULT_LAYOUT, XKB_DEFAULT_VARIANT, and XKB_DEFAULT_OPTIONS with values supplied by systemd-localed, possibly overwriting values set by a particular user with system-wide default. STEPS TO REPRODUCE 1. export XKB_DEFAULT_LAYOUT=favorite_layout in .profile 2. launch plasma wayland session OBSERVED RESULT After session launch: $echo $XKB_DEFAULT_LAYOUT EXPECTED RESULT $echo $XKB_DEFAULT_LAYOUT favorite_layout ADDITIONAL INFORMATION It is possible to set these variables in ~/.config/plasma-workspace/env instead as a workaroud, but it took me a lot of time to realize that! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422336] kmail: the access and reading of the received messages is often very slow
https://bugs.kde.org/show_bug.cgi?id=422336 --- Comment #14 from Marc Mezzarobba --- Another, possibly more informative, perf report on the akonadi_maildir_resource process. (I don't understand why perf no longer manages to resolve the symbols are those from libQt5Core; I tried purging the buildid cache, to no avail.) 99.62%99.11% SessionThreadlibQt5Core.so.5.12.5 | |--92.11%--QApplication::notify | QApplicationPrivate::notify_helper | QReadNotifier::event | QAbstractSocketPrivate::canReadNotification | QAbstractSocketPrivate::emitReadyRead | 0x7effbccc1385 | 0x7effbccc14e3 | Akonadi::Connection::handleIncomingData | | | --92.05%--0x7effbccc3bd2 | | | --92.05%--0x7effbccc3240 | |--2.16%--0x7effbcc956d6 | 0x7effbccec7bc | g_main_context_iteration | | | --2.16%--0x7effbb02519b | g_main_context_dispatch | 0x7effbcced3c0 | 0x7effbcc96a50 | QApplication::notify | QApplicationPrivate::notify_helper | QReadNotifier::event | QAbstractSocketPrivate::canReadNotification | | | --2.15%--QAbstractSocketPrivate::emitReadyRead |0x7effbccc1385 || | --2.15%--0x7effbcbd9560 | |--1.99%--g_main_context_iteration | 0x7effbb02519b | g_main_context_dispatch | 0x7effbcced3c0 | 0x7effbcc96a50 | QApplication::notify | QApplicationPrivate::notify_helper | QReadNotifier::event | QAbstractSocketPrivate::canReadNotification | QAbstractSocketPrivate::emitReadyRead | 0x7effbccc1385 | 0x7effbccc14e3 | Akonadi::Connection::handleIncomingData | 0x7effbccc3bd2 | 0x7effbccc3240 | |--1.77%--Akonadi::Connection::handleIncomingData | 0x7effbccc3bd2 | 0x7effbccc3240 | --1.08%--0x7effbcc96a50 QApplication::notify QApplicationPrivate::notify_helper QReadNotifier::event QAbstractSocketPrivate::canReadNotification QAbstractSocketPrivate::emitReadyRead 0x7effbccc1385 0x7effbccc14e3 Akonadi::Connection::handleIncomingData | --1.08%--0x7effbccc3bd2 0x7effbccc3240 97.82% 0.00% SessionThreadlibQt5Widgets.so.5.12.5 | ---QApplication::notify QApplicationPrivate::notify_helper QReadNotifier::event QAbstractSocketPrivate::canReadNotification | --97.82%--QAbstractSocketPrivate::emitReadyRead 0x7effbccc1385 | |--95.66%--0x7effbccc14e3 | | | --95.66%--Akonadi::Connection::handleIncomingData | | | --95.45%--0x7effbccc3bd2 || | --95.44%--0x7effbccc3240 | --2.15%--0x7effbcbd9560 97.82% 0.00% SessionThreadlibQt5Network.so.5.12.5 | --97.82%--QReadNotifier::event QAbstractSocketPrivate::canReadNotification | --97.81%--QAbstractSocketPrivate::emitReadyRead 0x7effbccc1385 | |--95.66%--0x7effbcc
[kmail2] [Bug 422336] kmail: the access and reading of the received messages is often very slow
https://bugs.kde.org/show_bug.cgi?id=422336 --- Comment #4 from Marc Mezzarobba --- Dear kdepim developers, I'm seeing a similar issue with kmail on debian. My setup is close to that of the original reporter: I also just upgraded from kmail (+ dependencies) 19.08.3 to 20.04.1, and I'm using POP3 with a few dozens local maildir folders. My attempt to post more details was blocked by a spam filter. Please see the attachment above for the full version of this message. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422336] kmail: the access and reading of the received messages is often very slow
https://bugs.kde.org/show_bug.cgi?id=422336 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net --- Comment #3 from Marc Mezzarobba --- Created attachment 129030 --> https://bugs.kde.org/attachment.cgi?id=129030&action=edit message -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 369570] calendar selector for new events defaults to last selected calendar
https://bugs.kde.org/show_bug.cgi?id=369570 --- Comment #4 from Marc Mezzarobba --- Fair enough I suppose. There is one major downside to remembering the default calendar though: it makes it very easy to put private events in a public calendar. It would be great if one could have an “active” calendar instead (a natural choice would be the one currently selected in the calendar manager) and new entries would go there by default instead. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource
https://bugs.kde.org/show_bug.cgi?id=360834 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 318049] Message list gets blank after deleting message
https://bugs.kde.org/show_bug.cgi?id=318049 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 331539] All messages disappear after deleting one
https://bugs.kde.org/show_bug.cgi?id=331539 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384209] Confusing error message when mmap() fails
https://bugs.kde.org/show_bug.cgi?id=384209 --- Comment #2 from Marc Mezzarobba --- It wasn't intentional. Baloo was failing to start, and it took me a while to understand what was going on. It is a minor point in any case. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 392105] Editing message list themes doesn't work
https://bugs.kde.org/show_bug.cgi?id=392105 --- Comment #4 from Marc Mezzarobba --- Created attachment 111538 --> https://bugs.kde.org/attachment.cgi?id=111538&action=edit screenshot (In reply to Laurent Montel from comment #3) > normal as it's default theme. > We don't have method for restoring them so you need to clone them and modify > them. I fear I don't understand what you mean, sorry. I am trying to edit a clone of one of the default themes, not the default theme itself. Here is a screenshot to try to clarify what happens. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 392105] Editing message list themes doesn't work
https://bugs.kde.org/show_bug.cgi?id=392105 --- Comment #2 from Marc Mezzarobba --- Thanks for having a look! (In reply to Laurent Montel from comment #1) > did you select the new theme ? Yes, I did. And I'm able to edit the properties of the items in the new themes, or to remove items, but not to add new contents item nor to move existing ones. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 392105] New: Editing message list themes doesn't work
https://bugs.kde.org/show_bug.cgi?id=392105 Bug ID: 392105 Summary: Editing message list themes doesn't work Product: kdepim Version: 5.7.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: messagelist Assignee: kdepim-b...@kde.org Reporter: marc+b...@mezzarobba.net Target Milestone: --- Adding or moving items in custom message list themes no longer seems to work with kmail / messagelib 17.12.2. Steps to reproduce: 1) View > Message List > Theme > Configure 2) Clone Theme 3) Attempt to drop a "Content Item" on the preview of the newly created theme. Expected result: the content item is added to the theme. Actual result: the mouse cursor indicates that the item cannot be dropped there, even after releasing the button. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 392018] Contact group resolution can go crazy due to recursively resolving on a part of the group name
https://bugs.kde.org/show_bug.cgi?id=392018 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384209] Confusing error message when mmap() fails
https://bugs.kde.org/show_bug.cgi?id=384209 Marc Mezzarobba changed: What|Removed |Added Component|balooctl|general -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384209] Confusing error message when mmap() fails
https://bugs.kde.org/show_bug.cgi?id=384209 Marc Mezzarobba changed: What|Removed |Added Component|general |balooctl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384209] New: Confusing error message when mmap() fails
https://bugs.kde.org/show_bug.cgi?id=384209 Bug ID: 384209 Summary: Confusing error message when mmap() fails Product: frameworks-baloo Version: 5.37.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: pinak.ah...@gmail.com Reporter: marc+b...@mezzarobba.net Target Milestone: --- It would be nice it the following could give a more helpful error: $ ulimit -Sv $((6*1024*1024)) $ balooctl enable Failed to create database, removing corrupted database. Failed to create database after deleting corrupted one. (Probably related to bug 364042.) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 369570] New: calendar selector for new events defaults to last selected calendar
https://bugs.kde.org/show_bug.cgi?id=369570 Bug ID: 369570 Summary: calendar selector for new events defaults to last selected calendar Product: korganizer Version: 5.2.3 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: korganizer-de...@kde.org Reporter: marc+b...@mezzarobba.net With older versions of korganizer, the dropdown list used to choose in which calendar to put a new event used to default to the calendar marked as “Default calendar” in the Calendar Manager. With 5.2.3, there is still an option called “Use as default calendar” in the Calendar Manager, but it seems to have no effect. Instead, the dropdown list seems to default to the item selected last time it was opened. -- You are receiving this mail because: You are watching all bug changes.
[kdepimlibs] [Bug 307144] LDAP credentials saved wrongly if password cotains a colon
https://bugs.kde.org/show_bug.cgi?id=307144 --- Comment #5 from Marc Mezzarobba --- I can no longer easily test if the bug is still valid, but please consider keeping it open until someone confirms it to be solved, since it could be hard to track down again for new affected users... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 281797] kmail2/akonadi handels maildir incorrect
https://bugs.kde.org/show_bug.cgi?id=281797 --- Comment #11 from Marc Mezzarobba --- (In reply to Denis Kurz from comment #10) > This bug has only been reported for versions before 4.14, which have been > unsupported for at least two years now. Can anyone tell if this bug still > present? Something like this still happens to me with KMail 5.2.3: at least the majority of messages (both received and sent) moved from inbox to maildir folders appear to stay in the new/ directory. However, the names are correct afaict. A few examples from yesterday: $ ls -l --sort=time new/ | head -5 total 3520 -rw-r--r-- 1 marc marc 3642 sept. 24 20:29 1474741744.R502.tramontane:2,S -rw-r--r-- 1 marc marc 1003 sept. 24 19:35 1474738555.R217.tramontane:2,S -rw-r--r-- 1 marc marc 4891 sept. 24 17:57 1474732623.R961.tramontane:2,S -rw-r--r-- 1 marc marc 3057 sept. 24 17:38 1474731481.R842.tramontane:2,S -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311496] Contacts Autocompletion list is difficult to use
https://bugs.kde.org/show_bug.cgi?id=311496 --- Comment #2 from Marc Mezzarobba --- (In reply to Denis Kurz from comment #1) > This bug has only been reported for versions before 4.14, which have been > unsupported for at least two years now. Can anyone tell if this bug still > present? It is, under KMail 5.2.3 / KF 5.25.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355696] Plasmashell hangs at icon removeing from panel
https://bugs.kde.org/show_bug.cgi?id=355696 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net --- Comment #2 from Marc Mezzarobba --- It looks like I may be experiencing the same problem. Here are few backtraces obtained by interrupting plasmashell at a few seconds' interval FWIW. #0 0x7f9c65baea56 in __GI___libc_malloc (bytes=bytes@entry=108) at malloc.c:2907 #1 0x0034fb6a6ee8 in QArrayData::allocate (objectSize=objectSize@entry=2, alignment=alignment@entry=8, capacity=capacity@entry=42, options=options@entry=...) at tools/qarraydata.cpp:101 #2 0x0034fb733d43 in QTypedArrayData::allocate (options=..., capacity=42) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:216 #3 QString::QString (this=0x7ffcbd867d00, size=41) at tools/qstring.cpp:1497 #4 0x003505676c51 in QStringBuilder, QString>, QLatin1Char>, QLatin1Char>, QString>::convertTo (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringbuilder.h:106 #5 QStringBuilder, QString>, QLatin1Char>, QLatin1Char>, QString>::operator QString (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstringbuilder.h:125 #6 Plasma::SvgPrivate::cacheId (this=this@entry=0x44b1790, elementId=...) at ../../../src/plasma/svg.cpp:165 #7 0x00350567a4d6 in Plasma::SvgPrivate::elementRect (this=0x44b1790, elementId=...) at ../../../src/plasma/svg.cpp:512 #8 0x00350567ad00 in Plasma::Svg::hasElement (this=, elementId=...) at ../../../src/plasma/svg.cpp:883 #9 0x00350566da70 in Plasma::FrameSvgPrivate::updateSizes (this=0x44b0400) at ../../../src/plasma/framesvg.cpp:1039 #10 0x003505670f90 in Plasma::FrameSvg::resizeFrame (this=0x44b0b70, size=...) at ../../../src/plasma/framesvg.cpp:380 #11 0x7f9c614a308b in Plasma::FrameSvgItem::geometryChanged (this=this@entry=0x44afe30, newGeometry=..., oldGeometry=...) at ../../../../src/declarativeimports/core/framesvgitem.cpp:401 #12 0x003504f82414 in QQuickItem::setSize (this=0x44afe30, size=...) at items/qquickitem.cpp:6387 #13 0x003504f782c6 in QQuickAnchorsPrivate::setItemSize (v=..., this=0x44b2fe0) at items/qquickanchors.cpp:400 #14 QQuickAnchorsPrivate::fillChanged (this=this@entry=0x44b2fe0) at items/qquickanchors.cpp:177 #15 0x003504f7a0e2 in QQuickAnchorsPrivate::itemGeometryChanged (this=0x44b2fe0, newG=..., oldG=...) at items/qquickanchors.cpp:441 #16 0x003504f7d68a in QQuickItem::geometryChanged (this=this@entry=0x44aecc0, newGeometry=..., oldGeometry=...) at items/qquickitem.cpp:3521 #17 0x003504f82414 in QQuickItem::setSize (this=0x44aecc0, size=...) at items/qquickitem.cpp:6387 #18 0x003504f782c6 in QQuickAnchorsPrivate::setItemSize (v=..., this=0x44b8a40) at items/qquickanchors.cpp:400 #19 QQuickAnchorsPrivate::fillChanged (this=this@entry=0x44b8a40) at items/qquickanchors.cpp:177 #20 0x003504f7a0e2 in QQuickAnchorsPrivate::itemGeometryChanged (this=0x44b8a40, newG=..., oldG=...) at items/qquickanchors.cpp:441 #21 0x003504f7d68a in QQuickItem::geometryChanged (this=this@entry=0x44ad650, newGeometry=..., oldGeometry=...) at items/qquickitem.cpp:3521 #22 0x003504f81c86 in QQuickItem::setHeight (this=0x44ad650, h=) at items/qquickitem.cpp:6253 #23 0x00350503ac98 in QQuickLoaderPrivate::_q_updateSize (this=0x449a180, loaderGeometryChanged=loaderGeometryChanged@entry=true) at items/qquickloader.cpp:894 #24 0x00350503ae3a in QQuickLoader::geometryChanged (this=this@entry=0x449c840, newGeometry=..., oldGeometry=...) at items/qquickloader.cpp:922 #25 0x003504f82414 in QQuickItem::setSize (this=0x449c840, size=...) at items/qquickitem.cpp:6387 #26 0x003504f782c6 in QQuickAnchorsPrivate::setItemSize (v=..., this=0x449a4b0) at items/qquickanchors.cpp:400 #27 QQuickAnchorsPrivate::fillChanged (this=this@entry=0x449a4b0) at items/qquickanchors.cpp:177 #28 0x003504f7a0e2 in QQuickAnchorsPrivate::itemGeometryChanged (this=0x449a4b0, newG=..., oldG=...) at items/qquickanchors.cpp:441 #29 0x003504f7d68a in QQuickItem::geometryChanged (this=this@entry=0x449b2a0, newGeometry=..., oldGeometry=...) at items/qquickitem.cpp:3521 #30 0x003504f82414 in QQuickItem::setSize (this=0x449b2a0, size=...) at items/qquickitem.cpp:6387 #31 0x003504f782c6 in QQuickAnchorsPrivate::setItemSize (v=..., this=0x44a3640) at items/qquickanchors.cpp:400 #32 QQuickAnchorsPrivate::fillChanged (this=this@entry=0x44a3640) at items/qquickanchors.cpp:177 #33 0x003504f7a069 in QQuickAnchorsPrivate::update (this=0x44a3640) at items/qquickanchors.cpp:431 #34 0x003504f7a0c5 in QQuickAnchorsPrivate::updateMe (this=) at items/qquickanchors.cpp:411 #35 0x003504f7d58d in QQuickItem::geometryChanged (this=this@entry=0x449b2a0, newGeometry=..., oldGeometry=...) at items/qquickitem.cpp:3505 #36 0x003504f81916 in QQuickItem
