'bzr explore' unexpectedly throwing MS Visual C++ runtime error at startup

Can you provide us your explorer.conf?

we have to test that upgrading explorer from 0.11 to 1.0 won't break the things

It seems this may have been triggered by changing preferences in Tools/Options.

Simon Kersey observed on the Bazaar ML that deleteing explorer.conf allows Explorer to start up again.

David Roberts wrote:
> Public bug reported:
>
> [This may NOT be an Explorer issue at base, but here seems a good place
> to log it.]
>
> WinXP, with bzr-2.1.0rc1-1-setup.exe installer has been running
> happily for several days. This morning, on trying to run bzr-explorer,
> I get a Microsoft Visual C++ runtime error. The console reports
> "QVariant::load(QDataStream &s): type list unknown to QVariant."
> Nothing is written in .bzr.log

I'd like like to know whether I can trap this at the Python level. Could
you try with -Derror and see if a stacktrace comes out?

Ian C.

Tried with bzr-explorer r406

steps to reproduce

Tools/Options/Appearance/contents: change 'kind-specific' to 'classic'

 [note: during this run, console reports "QVariant::load: unable to load type 430." several times

on restart, fails as reported.

> bzr -Derror explore ( or > bzr explore -Derror ) does not produce any additional logging.

this is .bzr.log -

Thu 2010-02-04 11:14:44 +0000
0.062 bazaar version: 2.1.0rc1
0.062 bzr arguments: [u'explore', u'-Derror']
0.078 looking for plugins in C:/Documents and Settings/djr/Application Data/bazaar/2.0/plugins
0.078 looking for plugins in C:/localapp/Program Files/Bazaar/plugins
0.157 encoding stdout as sys.stdout encoding 'cp850'

Thu 2010-02-04 11:17:39 +0000
0.079 bazaar version: 2.1.0rc1
0.079 bzr arguments: [u'-Derror', u'explorer']
0.094 looking for plugins in C:/Documents and Settings/djr/Application Data/bazaar/2.0/plugins
0.094 looking for plugins in C:/localapp/Program Files/Bazaar/plugins
0.172 encoding stdout as sys.stdout encoding 'cp850'

This is the content of explorer\explorer.conf saved by the previous 'steps to reproduce'
With this file in place bzr-explorer will not start.

[Preferences]
advanced-commands-terminal=false
app-suite=qbzr
bags-to-blacklist=@Variant(\0\0\0\x7f\0\0\0\x5list\0)
bind-branches-by-default=false
clothes-to-wear=@Variant(\0\0\0\x7f\0\0\0\x5list\0)
custom-dialog-branch=true
custom-dialog-checkout=true
custom-dialog-init=true
custom-dialog-switch=true
location-selector-style=tabs
status-auto-refresh=true
toolbar-contents=classic
toolbar-style=text-under-icon
toolbox-on-repository-view=false
toolbox-on-status-view=true
toolbox-on-welcome-view=false
workingtree-default-to-edit=false
workingtree-style=qbrowse
workspace-model=feature-branches

[ .conf file ENDS DJR ]

If EITHER of the lines containing @Variant...list is present in the .conf file, the startup bug is triggered.

If BOTH of the lines containing @Variant...list are removed, explorer starts normally.

David Roberts пишет:
> This is the content of explorer\explorer.conf saved by the previous 'steps to reproduce'
> With this file in place bzr-explorer will not start.
>
> [Preferences]
> advanced-commands-terminal=false
> app-suite=qbzr
> bags-to-blacklist=@Variant(\0\0\0\x7f\0\0\0\x5list\0)
> bind-branches-by-default=false
> clothes-to-wear=@Variant(\0\0\0\x7f\0\0\0\x5list\0)

Ian, I think we should use our own serializer here and don't rely on QT
one. Bencode seems good enough for this preferences, and it supports
many type of data. Why not use it?

Fixed in rev 407

CONFIRM that this appears to fix the bug I reported.

But is this correct?

"clothes-to-wear=Bazaar support|Register on Launchpad"

Sorry - ignore prev. comment - I can see now where this is configured and the default selections are reflected here OK.