GNOME Bugzilla – Bug 795815
Can no longer use three-panel mode
Last modified: 2018-09-21 16:06:10 UTC
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
And today, on Thursday May 17, it just as mysteriously started working again. If there's anything I can do to provide diagnostic informatino next tie this happens, please let me know.
And on the next day, Friday May 18, it failed again. It started up properly in three-panel mode. I saw ony one panel, but there is an adjustment bar that was all the way to the left, s that's what I could expect. The adjustment bar worked, and I got the usual three panels. Thing worked properly for a while, until suddenly it failed and showed only one panel. I tried using the adjustment bar again, but it wouldn't work. It showed me the usua two-headed arrow, and I could move the arrow to where I wanted it, but the panel boundary wouldn't move and I remained stuck with just one panel. Oh, In addition, when it left three-panel mode it also widened the whole window to about twice the width of my screen. The moment it failed was during a mouse action; I believe that was a scrolling action in the 'body' panel using the middle button on the mouse. But my mouse is hyper-sensitive; it could have been an accidental mouse-button press instead. The first time pan went into broken mode (described a few messages ago in this thread) I had also used a mouse gesture near the upper right corner of the 'body' panel. A coincidence? Maybe. Switching to tabbed mode worked, but it's not the way I want to read news. Terminating Pan using the window manager's close button worked, but when I restarted Pan, it started in the broken mode I'm getting used to. It's clear that the whole thing sometimes works properly, and sometimes not at all. The problem seems to remain even on shutting down and restarting Pan. I wonder (1) where it remembers that it's supposed to start up broken, and (2) why it sometimes loses this information and works properly. -- hendrik
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/pan/issues/86.