Bug 105857 - MultiSelection list box not working with Dropdown > Yes
Summary: MultiSelection list box not working with Dropdown > Yes
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.1.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-08 13:02 UTC by tim
Modified: 2017-08-02 13:01 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Test database (23.93 KB, application/vnd.oasis.opendocument.database)
2017-02-08 13:02 UTC, tim
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tim 2017-02-08 13:02:45 UTC
Created attachment 131014 [details]
Test database

At some point since libreoffice ubuntu 5.2.2.2 multi-selection list boxes that are not linked to a data field have stopped working.  I tried on Windows 10 5.2.5.1 and Ubuntu 5.3.0.3 and they don't display any data.  

The data is definitely there, since if you type a first letter the list box content for that one does display.

The use-case for me is that I use such list boxes to refine a selection list of items that I want to do something with.  So I use the multi-selection list box to select items, and I then populate a grid control below with a summary of all the items that match my selection.

The attached odb is just a test one I use for trying to determine where errors may lie and demonstrate to people that there is a problem.  Open the form table1 and look and the top right had list box.

If you edit the box and turn off multi-selection, the list is populated correctly.
Comment 1 Robert Großkopf 2017-02-08 19:47:13 UTC
Could confirm this buggy behavior. If you set "Dropown" > "No" the content will be shown and will be selectable.

First version I found with this bug:
Version: 5.1.0.3
Build-ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737
CPU Threads: 4; OS Version: Linux 4.1; UI Render: default; 
Gebietsschema: de-DE (de_DE.UTF-8)
Last version without this bug: LO 5.0.5

Tested with OpenSUSE 64bit rpm Linux
Comment 2 tim 2017-02-08 21:30:19 UTC
Thanks for that tip.  It now works - I think I can live with that.

Now all I need is checkboxes working (#105463) :-)
Comment 3 tim 2017-02-08 21:36:21 UTC
Having said I can live with it, I just tried it on my real-life form and it does make life difficult.  My lists are really rather long (sometimes hundreds of entries).

If it can't be fixed moderately soon (within a month or 2) in a pre-release I'll need to redesign the form with much bigger boxes.

I'm happy to test a dev (non-ubuntu) version.
Comment 4 tim 2017-02-23 16:09:39 UTC
Just to say this is still an issue in Version: 5.3.1.1
Build ID: 1:5.3.1~rc1-0ubuntu1~yakkety0 

I've changed my listboxes to single selection for now, which means I've lost functionality, but it's the best compromise for me for the time being.
Comment 5 tim 2017-03-18 21:20:42 UTC
The problem is still present in Version: 5.3.1.2
Build ID: 1:5.3.1-0ubuntu1~yakkety0
CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: x11; Layout Engine: new; 
Locale: en-GB (en_GB.UTF-8); Calc: group
Comment 6 tim 2017-03-31 12:42:19 UTC
Is there any chance this will get looked at?  I appreciate no one else seems to have commented that they have problems against this bug report.

The use case is that I want to assemble a list of items from a database that match several criteria, and quite often that means more than one variable from the same list.  Redesigning my application to find another user-friendly way of doing this is giving me a few problems.

The problem is still present in Version: 5.3.2.2
Build ID: 1:5.3.2~rc2-0ubuntu1~yakkety0
CPU Threads: 8; OS Version: Linux 4.8; UI Render: default; VCL: x11; Layout Engine: new; 
Locale: en-GB (en_GB.UTF-8); Calc: group
Comment 7 Julien Nabet 2017-07-24 18:53:56 UTC
On pc Debian x86-64 with master sources updated today, I can see values when clicking on the arrow of the dropbox.
I can then select several values (not very easily I must recognize) with Ctrl+left click
How was the behaviour in old version?
Comment 8 tim 2017-07-25 08:10:26 UTC
In my current version if I have multi-selection and drop-down selected, I see no values at all.  If I don't have drop-down I see the values and can select, but it's very difficult to use since I have many dozen entries in each box and I can't have the boxes big enough.

A few days ago I decided that this problem probably wouldn't be fixed any time soon, so I spent a couple of days redesigning the application that used this feature so that I don't really need it any more.  As I was doing this I thought "Now I've started to redesign this I bet it gets fixed soon".  And sure enough..... :-)

Which version will this fix likely get into?
Comment 9 tim 2017-07-25 13:16:28 UTC
I just installed Version: 5.4.0.3

Build ID: 92c2794a7c181ba4c1c5053618179937228ed1fb
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: gtk2; 
Locale: en-GB (en_GB.UTF-8); Calc: group

(as an additional 'opt' installation on ubuntu).  This problem has definitely been fixed.  As I said earlier I knew that as soon as I got around to putting the work in to circumvent it the problem would be fixed!

I hope this pre-release becomes available soon on ubuntu as a snap or ppa, along with the associated mysql connector (or is there one somewhere in the pre-release directory?).
Comment 10 Julien Nabet 2017-07-25 13:47:09 UTC
Thank you for your feedback Tim.
Let's put this one to WFM.

About resolution of bugs, there are different priorities and even in devs, some contribute with their spare time.
Now I must recognize that Base seems a module for which I know only 1 expert dev only.

By any chance, can you program? If yes and if you have some time, you may contribute in dev (see https://wiki.documentfoundation.org/Development/GetInvolved)
Comment 11 Alex Thurgood 2017-07-25 14:15:44 UTC
(In reply to tim from comment #9)


> I hope this pre-release becomes available soon on ubuntu as a snap or ppa,
> along with the associated mysql connector (or is there one somewhere in the
> pre-release directory?).

Snaps don't provide the mysql-connector to my knowledge (in fact, they only seem to provide the basic office suite without any extras, and jailed to boot).

You might be luckier with PPAs, but they definitely have a certain je-ne-sais-quoi-c'est-du-n'importe-quoi, oh, whoops, did I let that huge regression in there?" about them, IMO, YMMV.
Comment 12 tim 2017-07-25 15:29:35 UTC
Thanks for the information.

My programming skills are sadly limited these days so I fear I can't help with development.  I lost track sometime around 1985, and just tinker with bits of VB (for LO), and occasional other languages when I really have to (looking everything up on t'web). 

BTW this change of status is a definite 'fix' - robert confirmed it was misbehaving previously and I retried it only days ago on 5.3.5.1 before developing my now unnecessary workaround :-)
Comment 13 Alex Thurgood 2017-07-25 16:01:49 UTC
(In reply to tim from comment #12)
> Thanks for the information.
>

> BTW this change of status is a definite 'fix' - robert confirmed it was
> misbehaving previously and I retried it only days ago on 5.3.5.1 before
> developing my now unnecessary workaround :-)

It might well be fixed, but without an identifiable commit our triaging rules don't allow us to set it to fixed, just WFM. The aim of that rule is to be able to trace back a commit in the event that something it was supposed to fix breaks something somewhere else so we can decide whether or not the fixing commit is to be reverted or replaced with another fix ;-)
Comment 14 tim 2017-07-25 16:31:35 UTC
(In reply to Alex Thurgood from comment #13)
> (In reply to tim from comment #12)
> > Thanks for the information.
> >
> 
> > BTW this change of status is a definite 'fix' - robert confirmed it was
> > misbehaving previously and I retried it only days ago on 5.3.5.1 before
> > developing my now unnecessary workaround :-)
> 
> It might well be fixed, but without an identifiable commit our triaging
> rules don't allow us to set it to fixed, just WFM. The aim of that rule is
> to be able to trace back a commit in the event that something it was
> supposed to fix breaks something somewhere else so we can decide whether or
> not the fixing commit is to be reverted or replaced with another fix ;-)
Makes sense.
Comment 15 tim 2017-07-27 08:05:44 UTC
Version 5.4.0.3 was recently made available via the ubuntu pre-release ppa:

Version: 5.4.0.3
Build ID: 1:5.4.0~rc3-0ubuntu0.17.04.1~lo0
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: x11; 
Locale: en-GB (en_GB.UTF-8); Calc: group

In that version multi-select still doesn't work.



I downloaded the latest 5.4.0.3 version from libreoffice (to /opt):

Version: 5.4.0.3
Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: gtk2; 
Locale: en-GB (en_GB.UTF-8); Calc: group

and that still works.

So it seems there's an ubuntu problem. I'm not entirely clear how to report that.  Can you help?
Comment 16 Julien Nabet 2017-07-27 08:09:19 UTC
(In reply to tim from comment #15)
> ...
> So it seems there's an ubuntu problem. I'm not entirely clear how to report
> that.  Can you help?

I never did it since I don't use Ubuntu, but https://help.ubuntu.com/community/ReportingBugs may help.
Comment 17 tim 2017-07-27 08:17:06 UTC
OK - thanks.  

It may be that this has always been an ubuntu packaging issue.  I'll try to remember to test your versions directly before raising any future reports here.
Comment 18 tim 2017-08-02 13:01:43 UTC
It turns out that I needed to install libreoffice-gtk3.  Having done so, multi-select boxes now work using the ubuntu ppa version.

Thanks for the help and advice.