Can no longer use three-panel mode
Submitted by hen..@..oq.com
Assigned to pan..@..e.bugs
Link to original bug (#795815)
Description
I'm running Pan 1.44 on Devuan ascii, which corresponds to Debian stretch, and am having trouble. uname identifies the processor as an i686. My window manager is xfce.
Yes, I know that Devuan ascii and Debian Stretch provide only 1.41. See below.
I had been using Pan 1.41, the version that came with the release, but I usually use three-panel mode, and that was misbehaving. I discovered that was a known bug that had been fixed in a later release, and decided to upgrade Pan.
I switched aptitude into beowulf (=buster) mode by updating my apt-sources and running aptitude update, and installed that releases's Pan, and then switched aptitude back to ascii.
That updated version of Pan has worked reliably for a few months.
But today ,in the middle of my normal three-panel browsing session, it suddently switched into one-panel mode and stayed there. Shutting down Pan and restarting it did not help. I can choose, using the view->layout submenu, to turn the groups, headers, and body panes on and off, but all I get to see is the first one in the menu I have turned on.
That is, in three-panel mode. I'm aware that there should be widgets that can move the boundaries between the panels, and that sliding them to the wiindow boundaries can give the appearance of one panel even in three-panel mode. Those widgets are not present, and so I cannot adjust the boundaries to reasonable positions.
Now I can select tabbed mode, which works. It does at least lets me choose which of the three panels I get to see with a few clicks, but it is not convenient to leaf through large numbers of news items.
Three-panel mode has become unusable.
Evidently I have done something that has messed up the configuration, because the trouble persists after shutting Pan down and restarting it. I don't remember what, but I vaguely remember clicking near the top right corner of the rightmost panel)
What information would help you diagnose the problem?
Is there a known recovery method, such as hand-editing a configuration file?
-- hendrik