Bug 372155 - Channel topic always collapsed
Summary: Channel topic always collapsed
Status: CONFIRMED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.6.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-06 18:47 UTC by Elvis Angelaccio
Modified: 2020-12-05 20:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elvis Angelaccio 2016-11-06 18:47:57 UTC
Somehow the following settings got saved in my ~/.config/konversationrc:

[Appearance]
ChannelSplitterSizes=1021,129
TopicSplitterSizes=0,500

This results in a channel topic always collpased when opening Konversation (despite "Show channel topic" being checked in the settings).

Workaround (non persistent): the channel topic can be shown again by making it bigger with the mouse.

Steps to reproduce:
1. Add the following to yakuakerc

[Appearance]
ChannelSplitterSizes=1021,129
TopicSplitterSizes=0,500

2. Open Konversation

Expected result: channel topic is visible
Actual result: channel topic is hidden
Comment 1 Elvis Angelaccio 2016-11-06 18:48:44 UTC
(In reply to Elvis Angelaccio from comment #0)
> 
> Steps to reproduce:
> 1. Add the following to yakuakerc

Ops, that was supposed to be konversationrc
Comment 2 Justin Zobel 2020-11-30 03:27:17 UTC
I'd be more inclined to try figure out how it got in there but with the age of this bug report I doubt we'll figure it out.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 3 Elvis Angelaccio 2020-12-05 19:04:04 UTC
I don't use konversation anymore, but I doubt this got fixed.

Feel free to close it anyway.
Comment 4 argonel 2020-12-05 20:22:51 UTC
I've seen this intermittently over the years. I think it may have something to do with the splitter's minimum height calculation.