Bug 145033 - Assertion when reselecting entry in a form property
Summary: Assertion when reselecting entry in a form property
Status: CLOSED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.3.0.0 alpha0+
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Caolán McNamara
URL:
Whiteboard: target:7.3.0 target:7.2.3
Keywords: haveBacktrace
Depends on:
Blocks: Crash-Assert
  Show dependency treegraph
 
Reported: 2021-10-10 08:24 UTC by Julien Nabet
Modified: 2021-10-11 18:58 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
bt with debug symbols (6.77 KB, text/plain)
2021-10-10 08:24 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Nabet 2021-10-10 08:24:38 UTC
Description:
On pc Debian x86-64 with master sources updated I got a assertion when putting back initial value in a form entry.

Steps to Reproduce:
1. Retrieve https://bugs.documentfoundation.org/attachment.cgi?id=170164 from tdf#140749
2. Launch file
3. Right click on the formular "Teilnehmer" -> Edit
4. In the lower section right click in "Sportart". Click on "column ..."
5. Choose "Data" - and in the middle change the type from "SQL" to "anything else/value list/SQL native/Query".
5. Choose "Data" again and select again "SQL"


Actual Results:
Assertion

Expected Results:
No assertion


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 633e8c98cbcf8f41b8f8394a5e1f396bf6f7138f
CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: fr-FR (fr_FR.UTF-8); UI: en-GB
Calc: threaded
Comment 1 Julien Nabet 2021-10-10 08:24:57 UTC
Created attachment 175617 [details]
bt with debug symbols
Comment 2 Julien Nabet 2021-10-10 08:26:14 UTC
Caolán: since it's vcl related and that you had already modified the assertion, thought you might be interested in this one.
Comment 3 Julien Nabet 2021-10-10 08:37:16 UTC
I don't know if it's related but another thing I noticed is just when opening the form is:
warn:legacy.osl:21944:21944:svl/source/items/poolitem.cxx:610: There is no implementation for QueryValue for this item!
#0  SfxPoolItem::QueryValue(com::sun::star::uno::Any&, unsigned char) const (this=0x77737c0) at svl/source/items/poolitem.cxx:610
#1  0x00007fd4fd2eeaea in SfxDispatchController_Impl::StateChanged(unsigned short, SfxItemState, SfxPoolItem const*, SfxSlotServer const*) (this=
    0x3f1b8f0, nSID=10636, eState=SfxItemState::DEFAULT, pState=0x77737c0, pSlotServ=0x77fb868) at sfx2/source/control/unoctitm.cxx:867
#2  0x00007fd4fd27049f in SfxStateCache::SetState_Impl(SfxItemState, SfxPoolItem const*, bool) (this=0x77fb840, eState=SfxItemState::DEFAULT, pState=0x77737c0, bMaybeDirty=false)
    at sfx2/source/control/statcach.cxx:429
#3  0x00007fd4fd270171 in SfxStateCache::SetState(SfxItemState, SfxPoolItem const*, bool) (this=0x77fb840, eState=SfxItemState::DEFAULT, pState=0x77737c0, bMaybeDirty=false)
    at sfx2/source/control/statcach.cxx:326
#4  0x00007fd4fd1de9ba in SfxBindings::UpdateControllers_Impl(SfxFoundCache_Impl const&, SfxPoolItem const*, SfxItemState) (rFound=..., pItem=0x77737c0, eState=SfxItemState::SET)
    at sfx2/source/control/bindings.cxx:1214
#5  0x00007fd4fd1ddf80 in SfxBindings::Update_Impl(SfxStateCache&) (this=0x783a500, rCache=...) at sfx2/source/control/bindings.cxx:270
#6  0x00007fd4fd1df782 in SfxBindings::NextJob_Impl(Timer const*) (this=0x783a500, pTimer=0x783a618) at sfx2/source/control/bindings.cxx:1274
#7  0x00007fd4fd1e3c7d in SfxBindings::NextJob(Timer*) (this=0x783a500, pTimer=0x783a618) at sfx2/source/control/bindings.cxx:1219
#8  0x00007fd4fd1dc2e0 in SfxBindings::LinkStubNextJob(void*, Timer*) (instance=0x783a500, data=0x783a618) at sfx2/source/control/bindings.cxx:1217
#9  0x00007fd4f8680778 in Link<Timer*, void>::Call(Timer*) const (this=0x783a638, data=0x783a618) at include/tools/link.hxx:111
#10 0x00007fd4f86805b5 in Timer::Invoke() (this=0x783a618) at vcl/source/app/timer.cxx:75
#11 0x00007fd4f8621e80 in Scheduler::CallbackTaskScheduling() () at vcl/source/app/scheduler.cxx:471
Comment 4 Commit Notification 2021-10-11 15:10:46 UTC
Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/8fb4889840a6c79f6bad7bb7a322d86b751cdd93

Related: tdf#145033 don't print "There is no implementation..." warning

It will be available in 7.3.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 5 Commit Notification 2021-10-11 16:22:27 UTC
Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/83cadf937ff9a0fd4ca24627673d45d1bab8c914

tdf#145033 remove old focus handler so no double-connect attempt is made

It will be available in 7.3.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 6 Julien Nabet 2021-10-11 18:56:56 UTC
I confirm I don't reproduce the bug now after having updated local sources.
Thank you Caolán!
Comment 7 Commit Notification 2021-10-11 18:58:02 UTC
Caolán McNamara committed a patch related to this issue.
It has been pushed to "libreoffice-7-2":

https://git.libreoffice.org/core/commit/61ef0a842b42ac998a533e8e1ba1e00e02cd973d

tdf#145033 remove old focus handler so no double-connect attempt is made

It will be available in 7.2.3.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.