New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quodlibet throws an exception when going to Paned Browser #1903

Closed
am4c130d opened this Issue Mar 27, 2016 · 7 comments

Comments

Projects
None yet
3 participants
@am4c130d

am4c130d commented Mar 27, 2016

Dump_20160327_184028.txt

My paned view uses the recently added conditional sorting to display album info etc. However, I cannot get in to it to disable this due to the exception and Quodlibet needing to be restarted.

Thanks

@lazka lazka added the bug label Mar 28, 2016

@lazka

This comment has been minimized.

Member

lazka commented Mar 28, 2016

Open ~/.quodlibet/config. Please post the line starting with panes = and to make it work again delete it (all while QL is not running9

@lazka

This comment has been minimized.

Member

lazka commented Mar 29, 2016

I can reproduce: <~#disc>

@Negirno

This comment has been minimized.

Negirno commented Mar 29, 2016

It also crashes with <~#track>. This issue also affect me.

My dump files:
Dump_20160329_223740.txt
MiniDump_20160329_223740.txt

@lazka

This comment has been minimized.

Member

lazka commented Mar 29, 2016

Thanks.

@am4c130d

This comment has been minimized.

am4c130d commented Mar 30, 2016

Apologies for the slow response. My panes section:

panes = genre <genre=Audiobook|: |<genre=Classical|<conductor|<composersort||>: [small][i] conducted by [/i][/small]| [small][i]<originaldate||>[/i][/small] >| [small][i]<originaldate||>[/i][/small] >> <discsubtitle|: |><~#disc>: <title>:(<~length>)

I note I have #disc - I replaced <#disc> with and I can get to the paned browser now.

Thanks!

lazka added a commit that referenced this issue Mar 30, 2016

@lazka

This comment has been minimized.

Member

lazka commented Mar 30, 2016

Thanks. Will be fixed in 3.6.1

@lazka lazka closed this Mar 30, 2016

lazka added a commit that referenced this issue Mar 30, 2016

@lazka

This comment has been minimized.

Member

lazka commented Apr 6, 2016

3.6.1 is out now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment